Search Results entity_use_code




Overview
Explore in AI Chat

Overview

The OE.SO_ENTITY_USES table is a core reference table within the Oracle E-Business Suite Order Management module (versions 12.1.1 and 12.2.2). It functions as a junction table that defines the specific purposes or applications for which an entity is utilized. As per the documented metadata, these uses include serving as textual notes, holds, or discount pricing columns. The table is fundamental to the flexible configuration of business rules and data associations in the order lifecycle, acting as a bridge between a defined entity and its various functional contexts within the system. It is stored in the APPS_TS_SEED tablespace, indicating its role as a seeded data repository that is typically populated during installation and patching.

Key Information Stored

The table's structure is composed of two primary business columns and standard Oracle EBS audit columns. The ENTITY_ID is a mandatory, system-generated number that serves as a foreign key, linking to a specific record in the SO_ENTITIES table. The ENTITY_USE_CODE is a mandatory 30-character string that identifies the particular functional use for the linked entity, such as 'NOTE' or 'HOLD'. The combination of these two columns forms the table's primary key (SO_ENTITY_USES_PK), ensuring a unique definition for each entity-use pairing. The table also includes a full set of 15 descriptive flexfield segments (ATTRIBUTE1-15) and a CONTEXT column, allowing for extensive custom attribute storage to meet unique business requirements. Standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) track all changes to the records.

Common Use Cases and Queries

This table is primarily queried in two contexts: configuration validation and transactional data joins. Administrators may query it to understand what functional uses are assigned to specific entities, which is critical for troubleshooting setup issues related to notes, holds, or pricing. For developers and report writers, it is essential for joining transactional data (e.g., order notes or applied holds) back to their entity definitions to retrieve meaningful descriptions. A fundamental query pattern retrieves all uses for a given entity or all entities for a specific use code.

  • Finding all uses for a specific entity: SELECT entity_use_code FROM oe.so_entity_uses WHERE entity_id = <ID>;
  • Joining to the entity definition for a report: SELECT e.name, u.entity_use_code FROM oe.so_entities e, oe.so_entity_uses u WHERE e.entity_id = u.entity_id;

Related Objects

The SO_ENTITY_USES table has a direct and critical relationship with the SO_ENTITIES table, which stores the master definition of entities themselves. As documented in the relationship data, a foreign key constraint exists where SO_ENTITY_USES.ENTITY_ID references SO_ENTITIES. This means every ENTITY_ID in SO_ENTITY_USES must have a corresponding parent record in SO_ENTITIES. The table is also indexed on ENTITY_USE_CODE (SO_ENTITY_USES_N1) to support efficient lookups by use type. While not listed in the provided metadata, this table is logically referenced by various transactional tables and views in Order Management that store actual note text, hold applications, or pricing modifiers, which would use the composite key of (ENTITY_ID, ENTITY_USE_CODE) to identify the applicable rule or context.