Search Results so_line_attributes_pk

Overview

SO_LINE_ATTRIBUTES is a table in the OE (Order Entry) schema of Oracle E-Business Suite, documented as valid in ETRM for releases 12.1.1 and 12.2.2. Its stated purpose is to hold additional attributes of order lines — the descriptive, contextual, and extensibility columns that qualify an order line but are not part of the core transactional record. In the EBS order-to-cash architecture, the operative record for a sales order line lives in OE_ORDER_LINES_ALL, while SO_LINE_ATTRIBUTES carries the supplementary payload associated with that line, principally industry-specific context and the twenty-seat global descriptive flexfield. The table is owned by OE and exposes 47 documented columns in the 12.2.2 physical schema.

The ETRM metadata classifies this object, using a heuristic mined from its foreign-key structure, as standalone rather than as a hub, link, or satellite. As a modeling suggestion, this indicates the table is not a junction resolving many-to-many relationships, nor a purely dependent child; it is best treated as an extension of the order line entity itself. In Data Vault terms it most closely resembles a satellite keyed by the order line identifier, since its rows are functionally dependent on a single business key rather than representing an independent business concept.

Key Information Stored

The primary key is the constraint SO_LINE_ATTRIBUTES_PK, defined on LINE_ID. The same column is also the sole unique index candidate, SO_LINE_ATTRIBUTE_U1 (LINE_ID), which confirms LINE_ID as both the surrogate and the effective business key for this object. Because the column name matches the order-line identifier used throughout the OE schema, the table maintains a strict one-row-per-order-line cardinality.

• LINE_ID — primary key and unique business-key candidate; correlates one-to-one with the order line.
• INDUSTRY_CONTEXT — discriminator identifying which industry vertical's attribute set is populated on the row.
• INDUSTRY_ATTRIBUTE1 through INDUSTRY_ATTRIBUTE15 — flexible, context-dependent attributes reserved for industry-specific extensions.
• GLOBAL_ATTRIBUTE_CATEGORY — the flexfield structure/context designation governing which global segments are meaningful.
• GLOBAL_ATTRIBUTE1 through GLOBAL_ATTRIBUTE20 — the twenty descriptive flexfield segments available for customer-defined order-line data.
• WHO/audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.
• Concurrent program columns — PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID, used for request-level auditing.

Notably, the table stores no quantity, price, or item reference; those reside on the order line itself, reinforcing the extension role of this object.

Common Use Cases and Queries

The most frequent requirement is retrieving customer-defined order-line attributes for reporting, integration, or downstream fulfillment messages. A typical pattern joins the attribute table to the lines table on LINE_ID:

• Extract flexfield values for a set of orders: SELECT l.header_id, l.line_id, a.global_attribute_category, a.global_attribute1, a.global_attribute2 FROM oe_order_lines_all l, so_line_attributes a WHERE l.line_id = a.line_id AND l.header_id = :p_header_id.
• Locate lines using a specific flexfield context: filter on a.global_attribute_category to isolate lines populated under one descriptive flexfield structure.
• Industry-attribute reporting: constrain on industry_context and select the relevant industry_attribute columns to report vertical-specific order characteristics.
• Audit and reconciliation: use the WHO and program columns to trace which concurrent request or user last modified an order line's attributes.

Because the flexfield segment meanings are defined at runtime by the DFF configuration, reports should resolve segment labels rather than hard-coding column semantics.

Related Objects

The relationships below are the principal objects that reference or depend on SO_LINE_ATTRIBUTES, joined on the documented key column.

• OE_ORDER_LINES_ALL — the core order line table; join on LINE_ID. This is the dominant parent relationship.
• OE_ORDER_HEADERS_ALL — reached transitively via the line's HEADER_ID; supplies order-level context.
• OE_ORDER_LINES_V — the reporting view over order lines, commonly paired with this table for attribute-inclusive queries.
• OE_LINE_SETS and related OE line-extension objects — share the LINE_ID key space.
• OE_ORDER_PUB / OE_ORDER_LINES_PUB — the public PL/SQL APIs that insert and update order lines and their associated attribute rows.
• OE_ORDER_LINES_TL — translations for order lines, keyed indirectly through the same line identity.
• FND_DESCR_FLEX_COLUMN_USAGES — the flexfield metadata that defines the meaning of the GLOBAL_ATTRIBUTE and INDUSTRY_ATTRIBUTE segments.

Together these objects form the order-line extension layer through which EBS stores customer-configured and industry-specific order data on a one-to-one basis with the line.