Search Results rla_demand_lines

Overview

The RLA_DEMAND_LINES view belongs to the RLA - Release Management Integration Kit, a module classified in Oracle EBS Release 12.1.1 and 12.2.2 as obsolete. It is documented as a SINGLE-ORG view, meaning it is designed to present demand line information scoped to a single operating unit / organization rather than across multiple organizations. Its principal purpose was to expose demand line records, typically originating from order management or shipping integration flows, in a form suitable for release management processing and external integration consumption.

The view is relevant to the search term intermediate_ship_to_id, which appears as an exposed column. This column identifies an intermediate ship-to party or location associated with a demand line, supporting scenarios where goods are routed through an intermediary before reaching the final ship-to destination. Note that the ETRM metadata records this object as "Not implemented in this database," indicating the view may not be instantiated in the customer's environment despite its documented definition.

Underlying Base Objects

The view is defined over the base table RLA_DEMAND_LINES_ALL, which serves as the multi-organization source of demand line data. The single-org view filters this base table using the standard Oracle Multi-Org access mechanism, comparing the ORG_ID column against the organization identifier derived from the USERENV('CLIENT_INFO') session value. The WHERE clause applies NVL logic so that records with a null or unresolvable organization context default to a sentinel value of -99, preserving rows that lack a specific org assignment.

No referenced base objects beyond RLA_DEMAND_LINES_ALL are documented in the ETRM metadata. The "_ALL" suffix on the base table confirms the underlying data model supports multiple organizations, and the view narrows that scope to the currently accessed organization.

Key Columns

• INTERMEDIATE_SHIP_TO_ID — Identifies the intermediate ship-to party or site, enabling routing of demand through an intermediary location.
• DEMAND_HEADER_ID / DEMAND_LINE_ID — Primary identifiers for the demand header and its constituent lines.
• SHIP_TO_ADDRESS_ID / SHIP_TO_SITE_USE_ID — Final destination address and site-use references.
• SHIP_FROM_ORGANIZATION_ID — Organization from which the demand is sourced.
• INVENTORY_ITEM_ID / CUSTOMER_ITEM_ID / ITEM_TYPE_CODE — Item identification across internal and customer numbering.
• QUANTITY / UOM_CODE — Demand quantity and its unit of measure.
• PLANNED_SHIPMENT_DATE / DATE_REQUESTED_CURRENT — Scheduling dates for the demand line.
• DOCUMENT_TYPE / REQUIREMENT_TYPE / DISPOSITION — Classification attributes describing the nature and status of the demand.
• REQUIREMENT_EXT / LINE_REFERENCE / ORIGINAL_SYSTEM_LINE_REFERENCE — External system references supporting integration traceability.
• PO_CUM_KEY / MATCH_KEY / ASN_SEQ_NUMBER / TRANSMISSION_NAME — Integration keys used to correlate demand with purchasing, matching, and advance ship notice data.
• ATTRIBUTE1–15 / ATTRIBUTE_CATEGORY — Flexfield descriptive attributes for extensibility.
• ORG_ID — Organization identifier used by the single-org filter.

Common Use Cases and Queries

The view was intended for release management integration, where demand lines must be extracted and reconciled against shipping and order data. A typical query retrieves intermediate ship-to routing information alongside core demand attributes:

• SELECT DEMAND_LINE_ID, DEMAND_HEADER_ID, INTERMEDIATE_SHIP_TO_ID, SHIP_TO_ADDRESS_ID, INVENTORY_ITEM_ID, QUANTITY, UOM_CODE FROM RLA_DEMAND_LINES WHERE INTERMEDIATE_SHIP_TO_ID IS NOT NULL;
• SELECT DEMAND_LINE_ID, REQUIREMENT_TYPE, DISPOSITION, PLANNED_SHIPMENT_DATE, SHIP_FROM_ORGANIZATION_ID FROM RLA_DEMAND_LINES WHERE PROCESS_STATUS = 'READY';
• SELECT DEMAND_LINE_ID, LINE_REFERENCE, ORIGINAL_SYSTEM_LINE_REFERENCE, TRANSMISSION_NAME, MATCH_KEY FROM RLA_DEMAND_LINES WHERE ORG_ID = :p_org_id;

Integrators commonly join the view to shipping or order tables on DEMAND_LINE_ID or MATCH_KEY to reconcile demand against actual shipments and ASN records. Because the module is obsolete, environments upgrading from 12.1.1 to 12.2.2 should confirm whether the view remains instantiated before relying on it in custom code.