Choosing and Configuring Blitz Upload Type

Both API and Interface Table methods are efficient data upload solutions fully integrated with Oracle EBS. The ‘Type’ field in the Upload section determines which method is used. If you choose API, the process will call a custom PL/SQL wrapper procedure that handles the data insertion and validation logic. If you select Interface Table, the data is loaded directly into a staging table, and typically a subsequent post-procedure is used to submit a standard Oracle import concurrent request.

Your custom wrapper procedure is required to define three parameters: `action_` (input), `status_` (output), and `message_` (output). The upload framework passes input values like `xxen_upload.action_create` or `xxen_upload.action_update` via `action_`. Your procedure must populate `status_` with either `xxen_upload.status_error` or `xxen_upload.status_success` based on the processing outcome, and `message_` should contain any resultant message to display in the Excel output.

To correctly display success and error records, you must define the ‘Error SQL’ and ‘Success SQL’ under the Upload SQLs tab, which are appended dynamically to the report SQL post-processing. These SQLs must select the same number of columns in the same sequence as the main report SQL. Critically, they should query the dedicated Data View, which provides the uploaded data along with the status and message returned by the API (e.g., `xu.status_`, `xu.message_`). You should also use utility functions like `xxen_upload.action_meaning` and `xxen_upload.status_meaning` to display user-friendly status descriptions.

Yes, for Interface Table-based uploads, the main retrieval SQL must contain four specific columns in the first four positions: `action_`, `status_`, `message_`, and `row_id_`. The `row_id_` column specifically identifies the row in the interface table using the syntax `

Yes, Blitz Upload supports ‘Excel Validation’, which allows you to execute validations directly on the server from the Excel file when the file is saved. This is configured by entering a validation PL/SQL function call, mapping its parameters to the relevant SQL columns. The key requirement for this function is that it must return a message only in the case of validation failure; otherwise, it must return null.