Search Results containee_id

Overview

APPLSYS.BISM_AGGREGATES is a transactional data table in the Oracle E-Business Suite Applications schema (APPLSYS). It is registered against the FND design data object FND.BISM_AGGREGATES and resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10. The table is part of the Oracle EBS Business Intelligence / shipping container model that underpins the aggregation of container-level information used by the Warehouse Management and shipping (WSH) components of the supply chain stack. Its purpose is to record the relationship between shipping containers by capturing how one container (the containee) is nested within or associated with another container (the container), together with a numeric aggregate attribute.

The table is narrow by design: it holds only three documented columns — CONTAINER_ID, CONTAINEE_ID, and AGGREGATE_INFO — and functions as an associative structure linking two instances of the same domain (containers). Heuristic analysis of its foreign-key structure classifies APPLSYS.BISM_AGGREGATES as a standalone object for Data Vault modeling purposes. In Data Vault terms, this shape most closely resembles a link table (an associative table resolving a many-to-many relationship between container instances) rather than a hub or satellite; that classification is offered as a modeling suggestion only, since the column set is dominated by raw identifiers rather than descriptive attributes.

Key Information Stored

The table contains three documented columns, of which two are RAW(16) identifiers and one is a NUMBER(16):

• CONTAINER_ID (RAW(16)) — The surrogate key identifying the outer or parent container. Its RAW(16) datatype is characteristic of EBS global unique identifiers (GUIDs) used for container identity across the WSH schema.
• CONTAINEE_ID (RAW(16)) — The surrogate key identifying the inner or member container that is contained within CONTAINER_ID. This column is central to the user's search and defines the containment relationship; it is the second component of the composite unique index and participates in a foreign key back to BISM_OBJECTS.
• AGGREGATE_INFO (NUMBER(16)) — A numeric aggregate value associated with the container/containee pair, used to carry a summary measure attached to the relationship (for example a rolled-up quantity or count maintained by the BI aggregation process).

The primary key BISM_AGGREGATES_PK is a UNIQUE NORMAL index in APPS_TS_TX_IDX defined over all three columns (CONTAINER_ID, CONTAINEE_ID, AGGREGATE_INFO), making the full tuple the business-key candidate for uniqueness. A second index, BISM_AGGREGATES_UK, is NONUNIQUE and defined over CONTAINEE_ID and CONTAINER_ID, providing an efficient access path for lookups driven by the containee-to-container direction — the typical traversal when resolving what a given container resides within. There is no separately documented single-column surrogate key beyond the composite primary key. The mandatory flag is not documented for these columns in the available metadata.

Common Use Cases and Queries

Typical usage centers on resolving container hierarchy and nesting relationships during shipping, packing, and BI aggregation reporting. A common pattern is to locate all containees held within a parent container, or to determine the parent of a given containee using the nonunique index:

• Lookup by containee: SELECT CONTAINER_ID, CONTAINEE_ID, AGGREGATE_INFO FROM APPLSYS.BISM_AGGREGATES WHERE CONTAINEE_ID = :p_containee_id;
• Lookup by container: SELECT CONTAINEE_ID, AGGREGATE_INFO FROM APPLSYS.BISM_AGGREGATES WHERE CONTAINER_ID = :p_container_id;
• Direct join to container master data to resolve physical container identifiers.

These queries support packing-hierarchy reports, container roll-up reconciliations, and BI extracts that aggregate content across nested containers. Because both identifier columns are RAW(16), comparisons should pass bound variables or RAW literals rather than implicit character conversions, as implicit conversion can defeat index usage on BISM_AGGREGATES_UK and BISM_AGGREGATES_PK.

Related Objects

The documented dependencies tie this table to the container and object metadata structures in APPLSYS and WSH:

• APPLSYS.BISM_OBJECTS — Referenced twice via foreign keys: BISM_AGGREGATES.CONTAINEE_ID → BISM_OBJECTS and BISM_AGGREGATES.CONTAINER_ID → BISM_OBJECTS. This is the principal parent table and is used to validate both container identifiers.
• APPLSYS.WSH_PACKED_CONTAINERS — Associated via the CONTAINER_ID relationship, providing the physical container context for aggregation.
• APPLSYS.BISM_AGGREGATES# — The documented dependency variant (# table) referencing this object.
• Indexes BISM_AGGREGATES_PK and BISM_AGGREGATES_UK — Dependent index objects in APPS_TS_TX_IDX used for uniqueness enforcement and access paths.

No documented database objects are referenced by APPLSYS.BISM_AGGREGATES beyond the foreign keys listed above. Reporting and extraction typically begin from BISM_OBJECTS and join downward into BISM_AGGREGATES using the CONTAINER_ID and CONTAINEE_ID columns.