Results for “as_imp_sl_flex_pk”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The AS_IMP_SL_FLEX table is a Sales Foundation (AS) interface table owned by the OSM schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to hold flex field information that is staged for import into the application. In practical terms, it functions as a transient holding area where descriptive flex field (DFF) attribute values and global attribute values are collected, validated, and subsequently consumed by the Sales Foundation import process. Rows are associated with a parent import run through the AS_IMPORT_INTERFACE table, allowing multiple flex field records to be batched under a single import batch identifier.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign key structure suggests this table is satellite-leaning. This is consistent with its role: it carries descriptive, attribute-style context that orbits a parent import entity rather than acting as an independent business hub or a pure associative link. The table is dense in descriptive columns and references two parents, which is characteristic of a satellite that captures point-in-time detail about an import event.

Key Information Stored

The table is physically documented with 61 columns, most of which are flex field value slots. The most significant columns include:

• IMP_SL_FLEX_ID — the surrogate primary key, enforced by the AS_IMP_SL_FLEX_PK constraint and also referenced by the unique index AS_IMP_SL_FLEX_U1.
• IMPORT_INTERFACE_ID — foreign key to AS_IMPORT_INTERFACE, tying each flex row to its parent import batch. Together with ENTITY_NAME it forms the business-key candidate unique index AS_IMP_SL_FLEX_U2.
• ENTITY_NAME — identifies the logical entity (for example, a sales or customer object) to which the flex field values apply.
• TARGET_OBJ_ID — the identifier of the target object into which the imported flex values will be applied.
• VALIDATED_FLAG — indicates whether the row has passed import validation.
• ATTR_VAL_CATEGORY and ATTR_VAL_1 through ATTR_VAL_24 — the contextual descriptive flex field value slots.
• GATTR_VAL_CATEGORY and GATTR_VAL_1 through GATTR_VAL_20 — the global descriptive flex field value slots.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, providing multi-org security scoping.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE — concurrent program audit context for the import run.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE — standard EBS WHO audit columns.

Common Use Cases and Queries

The primary use case is diagnostic and reconciliation reporting during Sales Foundation data imports. Support and implementation teams query this table to confirm that flex field values were staged correctly and to identify rows that failed validation. A typical query joins to the parent import interface:

• Locate staged flex rows for a batch: SELECT * FROM OSM.AS_IMP_SL_FLEX WHERE IMPORT_INTERFACE_ID = :batch_id;
• Identify unvalidated records: SELECT IMP_SL_FLEX_ID, ENTITY_NAME FROM OSM.AS_IMP_SL_FLEX WHERE VALIDATED_FLAG = 'N';
• Audit by concurrent request: SELECT * FROM OSM.AS_IMP_SL_FLEX WHERE REQUEST_ID = :request_id;
• Trace import lineage: join AS_IMPORT_INTERFACE on IMPORT_INTERFACE_ID to correlate staged flex values with the originating import control record.

Because the table is an interface table, rows are typically purged after a successful import, so it is not a durable reporting source. Extract-based reporting should capture data before the import process clears the staging rows.

Related Objects

• AS_IMPORT_INTERFACE — parent table, joined via AS_IMP_SL_FLEX.IMPORT_INTERFACE_ID = AS_IMPORT_INTERFACE.IMPORT_INTERFACE_ID.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID for security group scoping.
• AS_IMP_SL_FLEX_PK / AS_IMP_SL_FLEX_U1 / AS_IMP_SL_FLEX_U2 — the primary key and unique indexes that enforce row identity and the business key on IMPORT_INTERFACE_ID and ENTITY_NAME.
• FND_FLEX_VALUES / FND_DESCR_FLEX_COL_USAGE — flex field definition infrastructure that provides meaning to the ATTR_VAL and GATTR_VAL value slots.
• FND_CONCURRENT_REQUESTS — correlates REQUEST_ID to the concurrent program that processed the import.