Search Results as_import_interface_pk

Overview

The AS_IMPORT_INTERFACE table is a core staging table within the Oracle E-Business Suite Sales Foundation (AS) module, specifically in versions 12.1.1 and 12.2.2. Owned by the OSM schema, its primary function is to serve as a temporary data repository for information queued for import into the application's transactional tables. This table is fundamental to the batch data import processes, particularly for sales-related entities such as leads and opportunities. It acts as the initial point of entry for external or bulk data, enabling validation, transformation, and subsequent processing by dedicated concurrent programs before the data is finalized in the main application tables.

Key Information Stored

While the provided metadata does not list specific columns, the table's structure is defined by its primary and foreign key relationships. The central column is IMPORT_INTERFACE_ID, which serves as the unique primary key (AS_IMPORT_INTERFACE_PK) for each record or batch of data staged in the interface. This identifier is critical for tracking the import process lifecycle. Other columns typically found in such interface tables include control and status attributes, such as BATCH_ID, PROCESS_STATUS, ERROR_MESSAGE, CREATION_DATE, and REQUEST_ID, which manage the execution and error handling of the import job. The table holds the raw imported data until it is successfully processed and purged.

Common Use Cases and Queries

The primary use case for AS_IMPORT_INTERFACE is the bulk import of sales leads and related data via Oracle's standard import programs. Administrators or integration tools populate this table, and a concurrent request (e.g., "Import Leads") is submitted to validate and transfer the data. Common operational queries include monitoring pending imports and diagnosing failures. For instance, to identify unprocessed records, one might query: SELECT IMPORT_INTERFACE_ID, CREATION_DATE FROM OSM.AS_IMPORT_INTERFACE WHERE PROCESS_STATUS = 'PENDING';. To investigate errors from a specific batch, a join with the related AS_LEAD_IMPORT_ERRORS table is typical: SELECT aii.*, alie.ERROR_MESSAGE FROM OSM.AS_IMPORT_INTERFACE aii, OSM.AS_LEAD_IMPORT_ERRORS alie WHERE aii.IMPORT_INTERFACE_ID = alie.IMPORT_INTERFACE_ID AND aii.REQUEST_ID = :req_id;.

Related Objects

The AS_IMPORT_INTERFACE table has a central relationship with several child interface tables, as documented by its foreign keys. The IMPORT_INTERFACE_ID column is referenced by the following tables, forming the complete staging structure for a sales import:

• AML_INTERACTION_LEADS: Links imported data to customer interaction records.
• AS_IMP_CNT_PNT_INTERFACE: Holds staged contact point information for the import.
• AS_IMP_CNT_ROL_INTERFACE: Holds staged contact role information for the import.
• AS_IMP_LINES_INTERFACE: Holds staged line item details, often for opportunities.
• AS_IMP_SL_FLEX_INTERFACE: Holds staged descriptive flexfield data for sales objects.
• AS_LEAD_IMPORT_ERRORS: Captures validation and processing errors for records originating from this interface table.

These relationships indicate that a single import batch in AS_IMPORT_INTERFACE can have associated detail records across multiple specialized interface tables, all linked via the IMPORT_INTERFACE_ID.