Search Results entity_use_code

Overview

The SO_ENTITY_USES table is a core data object within the Oracle E-Business Suite (EBS) Order Entry (OE) module, specifically in versions 12.1.1 and 12.2.2. It functions as a child table to SO_ENTITIES, defining the various roles or purposes (uses) associated with a business entity. An entity, such as a customer or supplier, can have multiple uses, including bill-to, ship-to, sold-to, and remit-to addresses. This table enables the complex relationship management required for modern order processing, allowing a single entity to interact with the system in different capacities across different transactions. Its existence is fundamental to the flexibility of the Trading Community Architecture (TCA) model as implemented within the Order Management suite.

Key Information Stored

The table's structure is designed to map entity identifiers to specific use codes. The primary key is a composite of ENTITY_ID and ENTITY_USE_CODE, ensuring a unique definition for each role an entity can fulfill. The ENTITY_ID column is a foreign key that links directly to the SO_ENTITIES table, identifying the parent business entity. The ENTITY_USE_CODE column stores the specific role identifier, such as 'BILL_TO' or 'SHIP_TO'. While the provided ETRM metadata does not list all columns, typical implementations may also include audit columns (CREATION_DATE, LAST_UPDATE_DATE, etc.) and potentially a status flag to indicate if a particular use is active for the entity.

Common Use Cases and Queries

This table is central to operations involving customer and site data for sales orders. A primary use case is retrieving all valid ship-to addresses for a given customer entity when creating a new sales order. Similarly, during the invoicing process, the system queries this table to determine the correct bill-to entity use for an order. Common reporting needs include listing all entities with a specific role or auditing the assignment of entity uses. A sample query to find all bill-to uses for a specific entity would be:

• SELECT entity_id, entity_use_code FROM oe.so_entity_uses WHERE entity_id = <entity_id> AND entity_use_code = 'BILL_TO';

Another frequent pattern is joining this table with SO_ENTITIES and HZ_PARTIES (from TCA) to generate a comprehensive customer site list report.

Related Objects

SO_ENTITY_USES has a direct and critical foreign key relationship with the SO_ENTITIES table, which is its parent. The relationship is defined as:

• Foreign Key from SO_ENTITY_USES to SO_ENTITIES: The ENTITY_ID column in SO_ENTITY_USES references the primary key (presumably ENTITY_ID) in the SO_ENTITIES table. This enforces referential integrity, ensuring every entity use is linked to a valid master entity record.

While not listed in the provided metadata, SO_ENTITY_USES is also a foundational table for higher-level Order Management entities. It is typically referenced by transactional tables like OE_ORDER_HEADERS (for bill-to and ship-to site uses) and is integral to the data model supporting the Order Management APIs. Queries often join through SO_ENTITIES to the Trading Community Architecture (TCA) tables, such as HZ_PARTIES and HZ_PARTY_SITES, to retrieve full address and party information.