Search Results match_key

Overview

The RLA_DEMAND_LINES_ARCHIVE view belongs to the RLA — Release Management Integration Kit product in Oracle E-Business Suite, a module that Oracle has designated as Obsolete. In the ETRM 12.2.2 metadata this object is classified as a SINGLE-ORG view, meaning that it exposes organizational data filtered to a single operating unit or organization context rather than presenting a multi-org (MOAC) security profile. Its role is to present historical or stale demand line records that have been moved into an archive structure, allowing historical demand, forecast, and shipment-related information to be queried without scanning the live demand interface tables.

The view is defined over RLA_DEMAND_LINES_ARCHIVE_ALL, applying a WHERE clause that resolves the session’s organization through USERENV('CLIENT_INFO'). This construct effectively mirrors the behavior of a seeded single-org view and is intended to be used in environments where only one organization’s archived demand lines are relevant. The metadata records that the view is not implemented in the database in the documented instance, indicating that RLA objects are typically dormant or absent unless the legacy integration kit was explicitly installed and used.

Underlying Base Objects

The view text selects from the underlying archive table RLA_DEMAND_LINES_ARCHIVE_ALL. The documentation lists no further referenced base objects, and the _ALL suffix confirms that this table is the multi-org source of truth, while the view is a narrowed, single-org projection. The ORG_ID column is carried forward into the view but is not part of the predicate on the underlying table; instead, the filter is applied against USERENV('CLIENT_INFO'), which supplies the current organization context. If the client info segment cannot be parsed as a number, the comparison defaults to -99, effectively returning rows where ORG_ID is null or matches the sentinel value.

Because the RLA module is obsolete, no DBA-level implementation is documented for this view in the provided metadata. In practical EBS 12.1.1 or 12.2.2 installations, the view may not exist at all, and any dependency on it should be validated against the actual database before being referenced in custom code.

Key Columns

The view exposes a broad, flattened column set drawn from the archive table. The column most relevant to the user’s search term, ship_from_organization_id, identifies the warehouse or organization from which the demand line is to be shipped. This is the standard key used to link demand to inventory, shipping, and picking activities.

• DEMAND_HEADER_ID, DEMAND_LINE_ID, LINE_REFERENCE — identifiers for the parent demand header and the individual demand line.
• SHIP_FROM_ORGANIZATION_ID — the shipping organization for the archived demand line.
• SHIP_TO_ADDRESS_ID, SHIP_TO_SITE_USE_ID, INTERMEDIATE_SHIP_TO_ID — destination and intermediate ship-to references.
• INVENTORY_ITEM_ID, ITEM_TYPE_CODE, UOM_CODE, QUANTITY — item and quantity details for the archived demand.
• PLANNED_SHIPMENT_DATE, DATE_REQUESTED_CURRENT — scheduling columns used for demand and shipment timing.
• DISPOSITION, PROCESS_STATUS, DOCUMENT_TYPE, REQUIREMENT_TYPE — status and classification columns.
• ORG_ID — the operating unit/organization identifier carried into the single-org projection.
• ARCHIVE_TIMESTAMP — records when the row was archived.
• ATTRIBUTE1–ATTRIBUTE15 and INDUSTRY_ATTRIBUTE1–INDUSTRY_ATTRIBUTE15 — descriptive flexfield and industry attribute columns.

Common Use Cases and Queries

The primary use case is historical reporting: retrieving archived demand lines by shipping organization for analysis of fulfilled, cancelled, or aged demand. Because rows are archived, the view is suited to audit and reconciliation queries rather than transactional processing.

SELECT demand_line_id,
       demand_header_id,
       ship_from_organization_id,
       inventory_item_id,
       quantity,
       uom_code,
       planned_shipment_date,
       archive_timestamp
FROM   rla_demand_lines_archive
WHERE  ship_from_organization_id = :p_org_id
ORDER BY archive_timestamp DESC;

A second common pattern is aggregation of archived demand volume per item and organization, using SHIP_FROM_ORGANIZATION_ID and INVENTORY_ITEM_ID as grouping keys. This supports capacity and historical throughput reporting. A third pattern joins the view back to the live RLA demand lines on DEMAND_LINE_ID or LINE_REFERENCE to compare archived and current demand records. Given the obsolete status of the RLA module and the documented absence of this view in the instance, all such queries should be preceded by a metadata check confirming that RLA_DEMAND_LINES_ARCHIVE exists and is valid.