Results for “demand_bucket_type_code”

50+ results




Overview
Explore in AI Chat

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

Overview

RLM_OE_ORDER_LINES_V is a Release Management (RLM) reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents a consolidated, aggregated picture of shippable order line demand drawn from Oracle Order Management, organized by ship-from organization, ship-to organization, customer item, inventory item, and event date. The view is a core data source for Release Management workflows, providing the quantities required to plan and release picking and shipping activities.

The view is specifically designed to answer the question: how much of each item needs to ship from a given warehouse to a given destination on a given date, and how much has already shipped? It exposes the SHIP_FROM_ORG_ID column prominently, which is the attribute most frequently used by planners and by report queries to filter demand at the warehouse level. Because the view aggregates at the organization-to-organization and item-to-item level, it is well suited to capacity planning, demand visibility reporting, and downstream integration into warehouse management or third-party logistics systems.

Underlying Base Objects

Per the documented 12.2.2 metadata, RLM_OE_ORDER_LINES_V is defined over two referenced base objects:

  • OE_ORDER_LINES_ALL (SYNONYM) — the primary source of order line demand, quantities, dates, UOMs, and shipping flags.
  • INV_CONVERT (PACKAGE) — invoked through INV_CONVERT.INV_UM_CONVERT to normalize shipped quantities across differing order and shipping units of measure.

The view text confirms that OE_ORDER_LINES_ALL is filtered to ITEM_IDENTIFIER_TYPE = 'CUST', SHIPPABLE_FLAG = 'Y', and LINE_CATEGORY_CODE <> 'RETURN'. Two branches are combined with UNION ALL: one aggregating ordered quantities and open quantities by TRUNC(SCHEDULE_SHIP_DATE), and a second aggregating shipped quantities by TRUNC(ACTUAL_SHIPMENT_DATE). Both branches are grouped by SHIP_FROM_ORG_ID, SHIP_TO_ORG_ID, ORDERED_ITEM_ID (aliased CUSTOMER_ITEM_ID), INVENTORY_ITEM_ID, the truncated date, AUTHORIZED_TO_SHIP_FLAG, DEMAND_BUCKET_TYPE_CODE, and ORDER_QUANTITY_UOM.

Key Columns

  • SHIP_FROM_ORG_ID — the warehouse or inventory organization from which goods are released; the principal planning dimension.
  • SHIP_TO_ORG_ID — the destination organization for the shipment.
  • CUSTOMER_ITEM_ID — the customer-facing item identifier (ORDERED_ITEM_ID).
  • INVENTORY_ITEM_ID — the internal inventory item identifier used for UOM conversion and inventory joins.
  • EVENT_DATE — TRUNC of either the scheduled ship date (demand) or actual shipment date (supply).
  • AUTHORIZED_TO_SHIP_FLAG — decodes to 1 when authorized ('Y') and 2 otherwise, supporting prioritization.
  • DEMAND_BUCKET_TYPE_CODE — the demand classification bucket.
  • UOM_CODE — the order quantity unit of measure.
  • ORDERED_QTY, SHIPPED_QTY, OPEN_QTY, TOLERANCE_QTY — aggregated quantities derived via DECODE over the FLG column and NVL handling for nulls.

Common Use Cases and Queries

The view is typically queried to report open demand by warehouse, to compare ordered versus shipped quantities, and to feed release planning logic. A representative query filtering on the searched attribute is:

  • SELECT ship_from_org_id, ship_to_org_id, inventory_item_id, event_date, ordered_qty, shipped_qty, open_qty FROM apps.rlm_oe_order_lines_v WHERE ship_from_org_id = :org_id AND event_date BETWEEN :from_date AND :to_date ORDER BY event_date, inventory_item_id;
  • Aggregated open demand: SELECT ship_from_org_id, SUM(open_qty) FROM apps.rlm_oe_order_lines_v GROUP BY ship_from_org_id;
  • Authorization filtering: restrict results using AUTHORIZED_TO_SHIP_FLAG = 1 to isolate lines cleared for release.

Because quantities are pre-summed by UOM conversion, consumers can trust the view for cross-UOM comparisons without reapplying INV_CONVERT logic.