Home › Discussions › Questions & Answers › SQL Requirements for Interface Table Upload

SQL Requirements for Interface Table Upload

Avatar photoCustomer Questions & Answers 7 replies

We are creating a Blitz Upload that writes data directly into a standard Oracle interface table for a subsequent import process. When configuring the main extraction SQL, what mandatory columns must be included for an Interface Table based upload, and in what order?

7 replies

  • Support Enginatics

    For Interface Table based uploads, your main extraction SQL is required to contain four specific columns in the first four positions , . These columns must be: `action_`, `status_`, `message_`, and `row_id_` , . You typically initialize these columns with `null` values, for example: `null action_, null status_, null message_,

    .rowid row_id_` , .
  • How is the `row_id_` column specifically derived in the SQL to correctly identify the rows?

  • Support Enginatics

    The `row_id_` column must explicitly identify the row in the underlying interface table . You derive it using the syntax: `

    .rowid row_id_` . For example, if your table is `XXEN_INT_T`, the column entry would be `XXEN_INT_T.rowid row_id_` . This is crucial for tracking individual records during the upload process.
  • If I were using an API based upload instead, what would the mandatory columns be?

  • Support Enginatics

    For API based uploads, the SQL requirements are slightly simpler, requiring only the first three columns . The SQL must contain `action_`, `status_`, and `message_` columns in the first three positions . The format is typically `null action_, null status_, null message_` . The `row_id_` column is not mandatory in this scenario .

  • After the data is loaded into the interface table, how do I configure the upload to submit the standard Oracle import concurrent program automatically?

  • Support Enginatics

    You configure the submission of the standard Oracle import concurrent request using the Post Procedure feature . Under the Upload setup tab, you define a post procedure that is executed after the primary upload processing is complete, typically responsible for submitting the subsequent concurrent request that consumes the data from the interface table , .

  • You must be logged in to reply to this post.