Results for “industry_attribute1”

50+ results




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

Overview

The SO_LINE_ATTRIBUTES_INTERFACE table resides in the OE (Order Entry) schema and is classified as VALID in Oracle EBS 12.1.1 and 12.2.2. It stores additional attributes of imported order line information — the supplementary descriptive data that accompanies order lines as they are staged for import into Oracle Order Management through the Order Import concurrent program. Where the primary order line interface holds the core transactional fields, this table carries the extended attribute segments: industry-specific flexfields and global descriptive flexfields.

Functionally, the table is an open interface (staging) structure. Records are populated externally — by external systems, legacy migrations, or EDI/XML feeds — and then consumed by Order Import, which validates each row and moves it into the operational order line tables. It is not a transactional table used at runtime.

Under the heuristic Data Vault classification mined from its foreign key structure, the metadata identifies this object as standalone. As a modeling suggestion, this indicates it functions in isolation from the core hub-and-link web rather than acting as a conformed hub, link, or satellite. Its uniqueness is enforced through a defined interface key rather than through a referenced parent entity.

Key Information Stored

The table contains 52 documented columns, dominated by attribute and flexfield segments. The most significant columns are:

Regarding the primary key: the heuristic model designates SO_LINE_ATTRIBUTES_INT_PK as the primary key. Notably, the documented primary key columns (ORIGINAL_SYSTEM_REFERENCE, ORDER_SOURCE_ID, ORIGINAL_SYSTEM_LINE_REFERENCE) are identical to those of unique index SO_LINE_ATTRIBUTES_INT_U1. There is therefore no distinct surrogate key separate from the business-key candidate; the natural interface identifier itself serves as the uniqueness constraint. Standard Who columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY) and concurrent-program audit columns (REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID) are also present.

Common Use Cases and Queries

Typical scenarios include diagnosing failed Order Import runs, reconciling source-system lines against imported orders, and auditing flexfield payloads delivered by external feeds.

To locate an interface row by its originating line reference:

  • SELECT * FROM oe.so_line_attributes_interface WHERE original_system_line_reference = :line_ref;

To identify failed rows for reprocessing:

  • SELECT original_system_reference, original_system_line_reference, interface_status, error_flag FROM oe.so_line_attributes_interface WHERE error_flag = 'Y' OR interface_status = 'ERROR';

To inspect flexfield payloads delivered for a given source document:

  • SELECT original_system_line_reference, global_attribute_category, global_attribute1, global_attribute2 FROM oe.so_line_attributes_interface WHERE original_system_reference = :src_ref;

Reporting leans on joining this table to the main line interface via the composite key (ORIGINAL_SYSTEM_REFERENCE, ORDER_SOURCE_ID, ORIGINAL_SYSTEM_LINE_REFERENCE).

Related Objects

Because the metadata classifies the table as standalone, no foreign keys are documented against it; related objects are therefore identified by shared interface key columns and functional dependency. The most significant are:

  • SO_LINES_INTERFACE — the primary order line staging table, joined on ORIGINAL_SYSTEM_REFERENCE, ORDER_SOURCE_ID, and ORIGINAL_SYSTEM_LINE_REFERENCE.
  • SO_HEADERS_INTERFACE — the header-level staging table, joined on ORIGINAL_SYSTEM_REFERENCE and ORDER_SOURCE_ID.
  • SO_ORDER_SOURCES — reference table resolving ORDER_SOURCE_ID.
  • OE_ORDER_LINES_ALL — the destination operational table populated after successful import.
  • OE_ORDER_HEADERS_ALL — header destination linked via the order identifier.
  • FND_DESCR_FLEX_COLUMN_USAGES — flexfield context metadata for INDUSTRY_CONTEXT and GLOBAL_ATTRIBUTE_CATEGORY.
  • Order Import concurrent program (ORDER IMPORT) — the processing engine that consumes and clears these interface rows.
  • FND_REQUEST / FND_CONCURRENT_REQUESTS — audit linkage via REQUEST_ID.