Results for “ship_to_chain_id”

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

Overview

DDR_SV_MFG_SHIP_C_MV is a materialized view owned by the APPS schema in Oracle E-Business Suite, catalogued under the FND – Application Object Library product. The "DDR_SV" naming prefix indicates a data-mart reporting artifact, while the "_C_MV" suffix confirms it is a materialized view rather than a base transactional table. In practice, this object serves analytical and reporting workloads for manufacturing shipment data, aggregating shipment quantities, amounts, and costs across calendar, organization, ship-to, and item-classification dimensions. It is typically refreshed on a scheduled basis from underlying source tables and is consumed by dashboards, extracts, and dimensional reporting queries rather than by OLTP transaction processing.

From a Data Vault modeling perspective, the ETRM metadata provides no explicit classification, so a heuristic reading is offered here as a suggestion: the object behaves most like a satellite in Data Vault terms. It carries descriptive measures (quantities, amounts, costs) attached to a set of dimension keys and a grouping reference, rather than representing a hub (unique business entity) or a link (many-to-many relationship between hubs). The single foreign key to HR_DM_TABLE_GROUPINGS reinforces this reading, since grouping identifiers are commonly associated with classification and reporting metadata rather than with core transactional hubs.

Key Information Stored

The object exposes 20 documented columns. The most significant are the dimensional keys and the aggregated measures:

• CLNDR_MNTH_ID — the calendar month key, driving the time dimension of every shipment aggregate.
• ORG_CHAIN_ID and SHIP_TO_CHAIN_ID — organization and ship-to chain identifiers defining the supply-side and demand-side parties.
• MFG_ITEM_CLASS_ID — the manufacturing item classification key for product roll-ups.
• GROUPING_ID — foreign key to HR_DM_TABLE_GROUPINGS, associating rows with a reporting grouping definition.
• CLNDR_DIM_ID / CLNDR_DIM_LVL — calendar dimension member and level, supporting hierarchy-aware drill-down.
• ORG_DIM_ID / ORG_DIM_LVL — organization dimension member and level.
• MFG_ITEM_DIM_ID / MFG_ITEM_DIM_LVL — manufacturing item dimension member and level.
• SHIP_QTY_PRMRY and SHIP_QTY_ALT — shipped quantities in primary and alternate units of measure.
• SHIP_AMT and SHIP_COST — shipped amount and shipped cost measures.
• CNT_TOTAL, CNT_SHIP_QTY_PRMRY, CNT_SHIP_QTY_ALT, CNT_SHIP_AMT, CNT_SHIP_COST — count-of-distinct or count-of-record helpers paired with each measure.

The documented unique index I_SNAP$_DDR_SV_MFG_SHIP_C_ spans SHIP_TO_CHAIN_ID, ORG_CHAIN_ID, CLNDR_MNTH_ID, MFG_ITEM_CLASS_ID, and GROUPING_ID, using SYS_OP_MAP_NONNULL on each. This composite constitutes the business-key candidate for the materialized view. No conventional surrogate primary key is documented for this object; the composite unique index provides the de facto row identity.

Common Use Cases and Queries

Typical usage centers on shipment analysis by month, organization, customer, and item class. A representative aggregation pattern follows:

• Total shipped quantity by item class for a calendar month: SELECT MFG_ITEM_CLASS_ID, SUM(SHIP_QTY_PRMRY) FROM DDR_SV_MFG_SHIP_C_MV WHERE CLNDR_MNTH_ID = :p_month GROUP BY MFG_ITEM_CLASS_ID;
• Shipment cost versus amount variance by ship-to chain: SELECT SHIP_TO_CHAIN_ID, SUM(SHIP_AMT), SUM(SHIP_COST) FROM DDR_SV_MFG_SHIP_C_MV WHERE ORG_CHAIN_ID = :p_org AND GROUPING_ID = :p_group GROUP BY SHIP_TO_CHAIN_ID;
• Level-based roll-ups, leveraging CLNDR_DIM_LVL, ORG_DIM_LVL, and MFG_ITEM_DIM_LVL to aggregate only at a chosen hierarchy depth.
• Count validation and average shipment value, using CNT_SHIP_AMT as the denominator when computing mean amounts.

Because this is a materialized view, querying is generally directed at the summary rows without concern for source join logic; refresh timing, however, determines data staleness and should be considered when reconciling against base transactional reports.

Related Objects

The documented foreign key relationship identifies the principal dependency:

• HR_DM_TABLE_GROUPINGS — joined on DDR_SV_MFG_SHIP_C_MV.GROUPING_ID = HR_DM_TABLE_GROUPINGS.GROUPING_ID; supplies grouping and classification metadata that governs how aggregation rows are interpreted and reported.

Beyond this documented relationship, practical dependencies follow from the EBS integration model: the materialized view derives from manufacturing shipment source tables and interacts with FND reporting infrastructure. Its DBA footprint includes the APPS schema owner and the snapshot unique index I_SNAP$_DDR_SV_MFG_SHIP_C_, which must be maintained during refresh operations. Consult the ETRM documentation set for the corresponding base tables in FND and the manufacturing inventory modules when tracing lineage.