Search Results ship_territory




Overview
Explore in AI Chat

Overview

RHX_DP_BOOKINGS_V is a custom reporting view associated with the MRP – Master Scheduling/MRP product family in Oracle E-Business Suite 12.1.1 and 12.2.2. The ETRM metadata labels the object as "Retrofitted," indicating that it was originally developed and later re-applied to a subsequent release. The documentation further notes that the view is "Not implemented in this database," meaning it may exist only in specific customer environments or custom schemas where the RHX_DP prefix convention has been deployed.

The view consolidates booked order demand across order headers, order lines, ship-to and bill-to addresses, territories, inventory items, and weekly time buckets. It derives its name from "DP" (likely a demand planning or distribution planning convention) and serves as a flattened reporting source for demand analytics by ship and bill territory. Because ship_territory is a key column, the view is well suited to geographic demand analysis, territory-based shipment reporting, and integration feeds that must resolve ship-to and bill-to territory context for booked orders.

Underlying Base Objects

The view text references a set of core Oracle EBS tables joined in a single SELECT statement. These include:

The documentation lists no formally registered base objects for this view, so the join logic in the view text is the authoritative source for lineage. Row granularity is weekly and item/organization-based.

Key Columns

  • Ship Address Identifier — concatenation of SHIP_ADDRESS.ADDRESS_ID and ADDRESS1, delimited by RHX_DP.GET_PARAMETER('RHX_DP_P_DELIMITER').
  • Ship Territory — concatenation of SHIP_TERRITORY.TERRITORY_ID and TERRITORY.NAME, the column of primary interest to ship_territory searches.
  • Bill Address Identifier and Bill Territory — equivalent constructs for the invoice-to side.
  • WEEK — the weekly bucket from RHX_DP_L_WEEKS_V used for time-based aggregation.
  • Inventory Item / Organization — MSIK.CONCATENATED_SEGMENTS, MSIK.INVENTORY_ITEM_ID, and MP.ORGANIZATION_ID.
  • QUANTITY — SUM(NVL(SLA.ORDERED_QUANTITY,0)) across the grouped demand lines.
  • MEANING — the demand class description from FND_COMMON_LOOKUPS.
  • SLA.CONTEXT and ATTRIBUTE1 through ATTRIBUTE15 — reserved order line attributes available for custom reporting extensions.

Common Use Cases and Queries

Shortcut view (preferred when territories are populated):

SELECT ship_territory, week, quantity
FROM   rhx_dp_bookings_v
WHERE  ship_territory LIKE '%NORTH%'
ORDER BY week;

Because raw territory names are delimited by a configurable parameter, the LIKE predicate should account for both the ID and name portions.

SELECT ship_territory, inventory_item_id, organization_id, SUM(quantity) qty
FROM   rhx_dp_bookings_v
GROUP BY ship_territory, inventory_item_id, organization_id;

Typical applications include territory demand dashboards, booked-order extracts for distribution planning, and integration feeds that push weekly demand by ship-to geography into downstream planning systems. If RHX_DP_BOOKINGS_V returns no rows, confirm that RHX_DP.GET_PARAMETER and RHX_DP_L_WEEKS_V are deployed in the same schema, since the view depends on both custom objects.