Results for “so_entity_uses”
21 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
SO_ENTITY_USES is a reference and cross-reference table in the Oracle E-Business Suite Order Entry (OE) schema. It records the usage classifications assigned to entities defined in the SO_ENTITIES table, providing the attribute layer that describes how a given entity may be employed within order capture, fulfillment, and pricing logic. Because the table carries a composite key and depends entirely on SO_ENTITIES for its identity, its heuristic Data Vault classification is satellite-leaning. In Data Vault modeling terms, SO_ENTITIES would serve as the parent hub for entity identity, while SO_ENTITY_USES functions as a satellite carrying descriptive and qualifying attributes keyed to that parent, with ENTITY_ID acting as the link to the hub. This classification should be treated as a modeling suggestion rather than a normative statement, since the table also exhibits link-like characteristics through its composite key structure.
Key Information Stored
The table is defined in the OE schema with 23 documented columns. Its primary key, SO_ENTITY_USES_PK, is composed of ENTITY_ID and ENTITY_USE_CODE. The same column pair is enforced by the unique index SO_ENTITY_USES_U1, making it the business-key candidate for the table. The most significant columns are:
- ENTITY_ID — Surrogate reference to the parent entity row in SO_ENTITIES; forms part of the composite primary key and the foreign key relationship.
- ENTITY_USE_CODE — The usage classification code describing how the entity is applied; the second component of the composite primary key and the discriminator across multiple uses per entity.
- LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit columns tracking the most recent modification and the responsible user session.
- CREATION_DATE, CREATED_BY — Standard audit columns capturing row insertion time and originating user.
- CONTEXT — The descriptive flexfield context identifier, determining which attribute columns are active for the row.
- ATTRIBUTE1 through ATTRIBUTE15 — The descriptive flexfield segment columns used for customer-specific or localization-specific extension data. These are populated only when the CONTEXT value defines the corresponding segment.
The surrogate primary key (SO_ENTITY_USES_PK) and the business-key unique index (SO_ENTITY_USES_U1) are structurally identical here, which is typical of simple reference tables in the OE schema. The audit and flexfield columns are not part of either key.
Common Use Cases and Queries
The dominant use case is retrieving all usage codes associated with a specific entity, typically for validation during order entry or for display in setup and inquiry forms. A representative query joins the table to its parent:
SELECT u.ENTITY_ID, u.ENTITY_USE_CODE FROM OE.SO_ENTITY_USES u WHERE u.ENTITY_ID = :p_entity_id;SELECT e.ENTITY_ID, e.ENTITY_NAME, u.ENTITY_USE_CODE FROM OE.SO_ENTITIES e, OE.SO_ENTITY_USES u WHERE e.ENTITY_ID = u.ENTITY_ID AND u.ENTITY_USE_CODE = :p_use_code;- Reporting on usage distribution:
SELECT ENTITY_USE_CODE, COUNT(*) FROM OE.SO_ENTITY_USES GROUP BY ENTITY_USE_CODE ORDER BY 2 DESC; - Auditing recent changes:
SELECT ENTITY_ID, ENTITY_USE_CODE, LAST_UPDATE_DATE, LAST_UPDATED_BY FROM OE.SO_ENTITY_USES WHERE LAST_UPDATE_DATE > SYSDATE - 30;
These patterns support setup validation, exception reporting, and migration reconciliation when entity configurations are moved between instances.
Related Objects
The most significant relationship is to the parent table that owns the referenced identity:
- SO_ENTITIES — Referenced through SO_ENTITY_USES.ENTITY_ID → SO_ENTITIES.ENTITY_ID. This is the defining foreign key and the primary join path for any query resolving entity descriptions.
- SO_ENTITY_USES_PK — The composite primary key constraint over (ENTITY_ID, ENTITY_USE_CODE); referenced by any child table or dependent constraint.
- SO_ENTITY_USES_U1 — The unique index over (ENTITY_ID, ENTITY_USE_CODE) supporting business-key lookups and enforcing cardinality.
- OE order capture and pricing setup views and concurrent programs that resolve entity usage flags depend indirectly on this table through SO_ENTITIES.
Because the documented FK graph lists only SO_ENTITIES, the table should be treated as a leaf satellite in the OE entity model; any additional referencing objects should be confirmed against the application's actual constraint inventory before being relied upon in custom development.
-
Entity uses
-
Entity uses
-
TABLE: OE.SO_ENTITY_USES 12.2.2
-
SYNONYM: APPS.SO_ENTITY_USES 12.2.2
-
SYNONYM: APPS.SO_ENTITY_USES 12.1.1
-
TABLE: OE.SO_ENTITY_USES 12.1.1
-
VIEW: OE.SO_ENTITY_USES# 12.2.2
-
VIEW: OE.SO_ENTITY_USES# 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 FND Design Data 12.1.1
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.2.2 FND Design Data 12.2.2
-
View: OEBV_DISCOUNT_LINES 12.1.1
- Retrofitted
Not implemented in this database·Explore OE module →
-
View: OEBV_DISCOUNT_LINES 12.2.2
- Retrofitted
Not implemented in this database·Explore OE module →
-
eTRM - OE Tables and Views 12.2.2
Temporary table
-
eTRM - OE Tables and Views 12.1.1
Temporary table
-
eTRM - OE Tables and Views 12.2.2
Temporary table
-
eTRM - OE Tables and Views 12.1.1
Temporary table
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1