Results for “so_attribute_uses”

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

Overview

SO_ATTRIBUTE_USES is a table owned by the OE (Order Entry) schema in Oracle E-Business Suite, present and valid in both release 12.1.1 and 12.2.2. Its documented purpose is to store attribute uses associated with security rules and standard value rule sets. In practical terms, the table acts as the association layer that binds a defined order attribute — for example, an order type, a line category, or a fulfillment attribute — to a specific usage context, so that Order Management can enforce attribute-level security and default-value behavior consistently across the order capture flow.

The ETRM relationship metadata classifies this object, heuristically, as satellite-leaning within a Data Vault modeling convention. This reflects the fact that SO_ATTRIBUTE_USES carries descriptive and contextual attributes and depends on a parent attribute definition rather than acting as an independent hub of business keys. Treat this classification as a modeling suggestion for analytical or warehouse design, not as a statement of the physical schema in EBS.

Key Information Stored

The table contains 24 documented columns. The most significant are:

• ATTRIBUTE_USE_ID — the surrogate primary key, enforced by index SO_ATTRIBUTE_USES_PK and also by the unique index SO_ATTRIBUTE_USES_U1. It uniquely identifies each attribute-use record.
• ATTRIBUTE_ID — foreign key to SO_ATTRIBUTES. This is the link to the underlying attribute definition and is the column that establishes the satellite-to-parent relationship.
• ATTRIBUTE_USE_CODE — the business-meaningful code describing the context in which the attribute is used, such as a security rule application or a standard value rule set application.
• CONTEXT — the descriptive flexfield context, allowing client-specific extensions to the attribute-use record.
• ATTRIBUTE1 through ATTRIBUTE15 — the standard EBS descriptive flexfield segment columns, available for customer-defined information.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard EBS who-columns used for auditing.

The surrogate key (ATTRIBUTE_USE_ID) should be distinguished from business-key candidates. The documented unique index SO_ATTRIBUTE_USES_U1 is defined on ATTRIBUTE_USE_ID, confirming that the surrogate itself is the only documented uniqueness guarantee; no separate natural composite key is documented in the available metadata.

Common Use Cases and Queries

The primary reporting use case is determining which attributes participate in order security rules and standard value rule sets, and how those attributes are configured. A typical query joins the table to its parent attribute definition:

• Listing all attribute uses for a given attribute: SELECT attribute_use_id, attribute_use_code FROM oe.so_attribute_uses WHERE attribute_id = :attribute_id;
• Inventory of security-related configurations: SELECT sau.attribute_use_id, sau.attribute_use_code, sa.attribute_code FROM oe.so_attribute_uses sau, oe.so_attributes sa WHERE sau.attribute_id = sa.attribute_id;
• Audit of recent configuration changes: SELECT attribute_use_id, attribute_use_code, last_update_date, last_updated_by FROM oe.so_attribute_uses ORDER BY last_update_date DESC;
• Extracting descriptive flexfield data: SELECT attribute_use_id, context, attribute1, attribute2 FROM oe.so_attribute_uses;

These patterns support configuration audits, migration validation, and security troubleshooting where order entry behavior depends on attribute-level rules.

Related Objects

The documented relationship centers on the foreign key from SO_ATTRIBUTE_USES.ATTRIBUTE_ID to SO_ATTRIBUTES. That parent table holds the attribute definitions referenced by each use record and is the most significant related object. Additional related objects in the OE security and defaulting framework include the security rule definitions and standard value rule set tables that consume these attribute uses at runtime, together with the descriptive flexfield metadata associated with the CONTEXT column. Because the ETRM excerpt documents only the SO_ATTRIBUTES foreign key, joins to other Order Management configuration tables should be verified against the target instance before being relied upon in production reporting.