Search Results decision_maker_flag

Overview

AS_IMPORT_INTERFACE is a staging table owned by the OSM schema in Oracle E-Business Suite, classified under the AS – Sales Foundation product family. Its documented purpose is to hold inbound data prior to validation and promotion into the production Sales tables. In practice it functions as the landing and working area for lead and customer import activity: external files, legacy extracts, or third-party feeds are loaded here first, then processed by the standard import concurrent programs, with rows either promoted to the destination entities or flagged with errors.

The heuristic Data Vault classification mined from the foreign-key structure is hub-leaning. This suggests modeling AS_IMPORT_INTERFACE as a hub-style entity keyed on its surrogate identifier, with the surrounding interface tables (contact points, contact roles, lines, flexfield values, errors) behaving as satellite or dependent structures that qualify a single import attempt.

Key Information Stored

The table is physically wide, with 339 documented columns in the 12.2.2 schema, reflecting that a single row carries the flattened content of an entire lead or customer record together with its address, contacts, phone numbers, and up to ten interaction to-dos.

• IMPORT_INTERFACE_ID – the surrogate primary key, enforced by AS_IMPORT_INTERFACE_PK and duplicated by the unique index AS_IMPORT_INTERFACE_U1. This is the column referenced by every child interface table.
• LOAD_TYPE, LOAD_DATE, LOAD_STATUS, LOAD_ERROR_MESSAGE – control the batch semantics of the load: what kind of import is being performed, when it occurred, whether the row succeeded, and the diagnostic text if it failed.
• IMP_LIST_HEADER_NUMBER, BATCH_ID – group rows belonging to the same import list or batch.
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE – the standard concurrent program audit columns identifying the import run that touched the row.
• CUSTOMER_ID, CUSTOMER_NUMBER, CUSTOMER_NAME, CUSTOMER_KEY – the customer/party business identifiers used for deduplication and matching.
• LEAD_NUMBER, STATUS_CODE, LEAD_RANK_CODE, SOURCE_PROMOTION_ID – the lead business key and qualification attributes.
• SALES_LEAD_ID – foreign key to AS_SALES_LEADS; populated when the staged row has been matched or promoted to an existing lead.
• SALES_METHODOLOGY_ID – foreign key to AS_SALES_METHODOLOGY_B, driving the sales methodology applied during qualification.
• SECURITY_GROUP_ID – foreign key to FND_SECURITY_GROUPS, enforcing multi-org style data security on the staged row.
• PARTY_ID, PARTY_SITE_ID, CONTACT_PARTY_ID, ADDRESS_ID, PHONE_ID – TCA identifiers that result from or are resolved against party and location validation.
• IMPORT_FLAG, KEEP_FLAG, DELETED_FLAG, NEW_PARTY_FLAG, NEW_LOC_FLAG – workflow flags governing whether the row is processed, retained, or treated as a new entity.
• ORIG_SYSTEM_CODE, ORIG_SYSTEM_REFERENCE – source-system attribution for the inbound record.

Only IMPORT_INTERFACE_ID is a documented unique key; the remaining business identifiers (CUSTOMER_NUMBER, LEAD_NUMBER, BATCH_ID, ORIG_SYSTEM_REFERENCE) are candidates but are not enforced as unique.

Common Use Cases and Queries

The dominant use case is operational visibility into import runs. Support and integration teams query the table to isolate rows that have not yet been promoted, or that carry errors requiring correction and replay.

• Reviewing rows pending promotion: select IMPORT_INTERFACE_ID, LEAD_NUMBER, CUSTOMER_NUMBER, LOAD_STATUS from AS_IMPORT_INTERFACE where LOAD_STATUS is null or LOAD_STATUS = 'ERROR'.
• Auditing a specific concurrent request: filter on REQUEST_ID joined to FND_CONCURRENT_REQUESTS to confirm which volume of records the import program processed.
• Error triage: join to AS_LEAD_IMPORT_ERRORS on IMPORT_INTERFACE_ID to retrieve the messages written for a failed batch.
• Reconciliation: compare staged CUSTOMER_NUMBER and PARTY_NUMBER values against HZ_PARTIES to detect duplicates created by repeated imports.
• Reporting: aggregate counts by BATCH_ID, LOAD_TYPE, and SOURCE_SYSTEM to trend import throughput and failure rates over time.

Related Objects

AS_IMPORT_INTERFACE sits at the centre of a family of interface tables that all converge on IMPORT_INTERFACE_ID:

• AS_IMP_LINES_INTERFACE – line-level product interest and budget detail for the staged record (IMPORT_INTERFACE_ID).
• AS_IMP_CNT_PNT_INTERFACE – contact point (phone, email, address) rows staged alongside the parent import row.
• AS_IMP_CNT_ROL_INTERFACE – contact role assignments for the staged contacts.
• AS_IMP_SL_FLEX – descriptive flexfield values captured for the sales lead being imported.
• AS_LEAD_IMPORT_ERRORS – validation failures raised against the staged row.
• AML_INTERACTION_LEADS – interaction and activity records generated from the import.

Outbound references define the production anchors: AS_SALES_LEADS via SALES_LEAD_ID, AS_SALES_METHODOLOGY_B via SALES_METHODOLOGY_ID, and FND_SECURITY_GROUPS via SECURITY_GROUP_ID. These joins confirm the table's role as a transient hub whose children are discarded or archived once the parent row is successfully posted.