Results for “container_id”

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

Overview

BISM_AGGREGATES is a table owned by the APPLSYS schema within the Oracle E-Business Suite FND (Application Object Library) product family. It is classified as VALID in both Oracle EBS 12.1.1 and 12.2.2 environments. The table supports the Business Intelligence Sales Management (BISM) subsystem of EBS, which underpins the aggregation and roll-up logic used by shipping and container-management reporting.

From a Data Vault modeling perspective, the heuristic classification for BISM_AGGREGATES is standalone, meaning the mined foreign-key structure does not naturally resolve into a hub, link, or satellite pattern. This is best treated as a modeling suggestion rather than a strict prescription. The table functions primarily as a junction-style aggregate that stores composite relationships between containers and the items they hold, along with aggregate descriptors used by BISM processing.

Key Information Stored

The documented physical schema in ETRM 12.2.2 contains three columns, and the unique index BISM_AGGREGATES_PK spans all three:

• CONTAINER_ID — Part of the composite unique key and a foreign key referencing WSH_PACKED_CONTAINERS. Identifies the packed container that acts as the aggregate grouping parent.
• CONTAINEE_ID — Part of the composite unique key. Identifies the contained item (a container or handling unit) that is aggregated within the parent container.
• AGGREGATE_INFO — Part of the composite unique key and the descriptive payload of the row. Holds the aggregate attribute or measure used to summarize the container/containee relationship for BISM reporting.

Because the table lacks a single surrogate primary key, the natural business key is the composite of CONTAINER_ID, CONTAINEE_ID, and AGGREGATE_INFO, as enforced by BISM_AGGREGATES_PK. This composite uniqueness guarantees that a given aggregation descriptor for a parent-child container pairing appears only once.

Common Use Cases and Queries

BISM_AGGREGATES is typically consumed in shipping intelligence reporting where users need rolled-up views of container contents. A representative join pattern against the parent container table is:

• SELECT a.container_id, a.containee_id, a.aggregate_info FROM applsys.bism_aggregates a WHERE a.container_id = :p_container_id;
• SELECT w.container_id, w.container_name, a.containee_id, a.aggregate_info FROM wsh_packed_containers w JOIN applsys.bism_aggregates a ON a.container_id = w.container_id WHERE w.container_name = :p_name;
• Aggregation roll-ups: group by CONTAINER_ID to count or summarize containees per packed container for load planning and manifest reports.

Typical scenarios include verifying that every packed container has its expected aggregate entries, reconciling BISM-aggregated shipping metrics against base container data, and building custom BI Publisher or OBIEE extracts that flatten the container hierarchy for downstream analytics.

Related Objects

• WSH_PACKED_CONTAINERS — Referenced by BISM_AGGREGATES.CONTAINER_ID; the primary parent entity for the aggregation relationship.
• WSH_CONTAINERS — Underlying container definition used to resolve container attributes when enriching BISM_AGGREGATES rows.
• WSH_DELIVERY_DETAILS — Links container contents back to delivery lines for shipment reporting.
• WSH_TRIPS — Trip-level context for aggregated container data.
• BISM_AGGREGATES_PK — The unique index enforcing composite uniqueness across CONTAINER_ID, CONTAINEE_ID, and AGGREGATE_INFO.
• FND_APPLICATION / FND_TABLES — Metadata registries that catalog APPLSYS-owned tables such as this one.

Because no other foreign keys beyond CONTAINER_ID are documented, join paths to WSH_PACKED_CONTAINERS should be treated as the authoritative relationship when building queries or integration logic.