Search Results item_organization

Overview

The view RHX_DP_SHIPMENTS_V is a custom reporting object delivered under the MRP – Master Scheduling/MRP product family within Oracle E-Business Suite. The ETRM metadata identifies it as "Retrofitted," indicating the view was authored or modified to preserve legacy behavior after an upgrade, and that it is not part of the standard Oracle application schema. The metadata further states that the object is "Not implemented in this database," meaning the view exists only as a deployment definition and has not been instantiated in the environment where the documentation was captured.

The view aggregates shipped and cancelled quantities from shipping details and joins them to address, territory, item, organization, order, lookups, and a custom weekly calendar view. Its principal analytical contribution is the pairing of ship-to and bill-to addresses with their respective RA_TERRITORIES entries — the object most directly associated with the user search term "ra_territories." Territories in Oracle Receivables describe geographic or sales segmentation, and this view exposes them on both the ship-to and bill-to sides, enabling segmentation of shipment demand by territory rather than by raw address alone.

Underlying Base Objects

The ETRM metadata lists no formally documented base objects, but the view text reveals the complete set of source objects. The primary fact source is WSH_SHIPPING_DETAILS_V (WSHSDV), joined to RA_ADDRESSES_ALL twice (as SHIP_ADDRESS and BILL_ADDRESS), RA_SITE_USES_ALL twice (SHIP and BILL), and critically RA_TERRITORIES twice (as SHIP_TERRITORY and BILL_TERRITORY) via the TERRITORY_ID from the respective site uses. Item and organization context come from MTL_SYSTEM_ITEMS_KFV and MTL_PARAMETERS, order context from OE_ORDER_HEADERS_ALL, and demand-class decode values from FND_COMMON_LOOKUPS. A custom calendar source, RHX_DP_L_WEEKS_V, supplies the week bucket, and the helper function RHX_DP.GET_PARAMETER supplies a configurable delimiter string used to concatenate descriptive fields.

The territory joins to RA_TERRITORIES are outer joins (TERRITORY_ID=SHIP_TERRITORY.TERRITORY_ID(+)), so shipments remain visible even when territory data is absent, and FCL.LOOKUP_TYPE(+) is likewise outer-joined for demand class decoding.

Key Columns

• Ship Address — ADDRESS_ID concatenated with the delimiter and ADDRESS1, derived from the ship-to RA_ADDRESSES_ALL row.
• Ship Territory — TERRITORY_ID and NAME from RA_TERRITORIES, conditionally joined with the delimiter.
• Bill Address / Bill Territory — the equivalent invoice-to address and territory pair.
• WEEK — the weekly time bucket from RHX_DP_L_WEEKS_V for period-based reporting.
• Item / Organization — concatenated item segments (CONCATENATED_SEGMENTS) with organization code, plus raw INVENTORY_ITEM_ID and ORGANIZATION_ID.
• Shipped Quantity — SUM(NVL(SHIPPED_QUANTITY,0) - NVL(CANCELLED_QUANTITY,0)), the net shipped quantity.
• Demand Class Meaning — decoded from FND_COMMON_LOOKUPS.
• CONTEXT and ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield values carried from the shipping details.

Common Use Cases and Queries

Typical applications include shipment reporting segmented by sales territory, net-shipped-quantity trending by week and organization, and territory-driven demand analysis. A representative query:

SELECT ship_territory, week, inventory_item_id, SUM(shipped_quantity)
FROM rhx_dp_shipments_v
WHERE week BETWEEN :start_week AND :end_week
GROUP BY ship_territory, week, inventory_item_id;

Because the object is documented as not implemented, deployment teams should verify existence in the target schema before relying on it in concurrent programs or BI Publisher data templates.