Search Results rla_demand_lines_pk

Overview

RLA_DEMAND_LINES_ALL is an Oracle E-Business Suite table belonging to the RLA — Release Management Integration Kit product. It stores Release Management Demand Lines, representing individual demand records generated within the release management integration flow. In Oracle EBS 12.1.1 and 12.2.2, the RLA module is documented as obsolete and, per the ETRM metadata, is not implemented in the database for the referenced environment. The table therefore exists primarily as a historical or compatibility artifact rather than an active transactional store in current releases.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign-key structure is standalone. This suggests the table functions as an independent entity rather than as a link or satellite within a hub-and-link network. In practical terms, no inbound or outbound linking tables are typically modeled around it; it holds its own demand-line grain without participating in shared business-key relationships.

Key Information Stored

The most significant column documented in the metadata is:

• DEMAND_LINE_ID — the surrogate primary key column. It is the single column constituting the primary key constraint RLA_DEMAND_LINES_PK.

Because the table is marked as not implemented, the metadata does not expose a full column listing or any alternate unique indexes that would identify business-key candidates. In analogous release-management and demand-tracking tables, columns of this nature typically store demand quantities, dates, source references and status flags, but none of those are confirmed for RLA_DEMAND_LINES_ALL in the supplied ETRM metadata. DEMAND_LINE_ID should be treated as the only documented, authoritative identifier.

Common Use Cases and Queries

Given the obsolete designation, direct querying of RLA_DEMAND_LINES_ALL is uncommon in production support. Where the object is encountered — for example during upgrades, data migration audits, or vestigial-schema analysis — the primary use case is confirming that no active rows exist and that no dependent processes still reference it.

A representative existence/volume check:

• SELECT COUNT(*) FROM RLA_DEMAND_LINES_ALL;

For integration traceability, a join with the staging table that references it:

• SELECT r.DEMAND_LINE_ID FROM RLA_DEMAND_LINES_ALL r, WMS_REPL_DEMAND_GTMP g WHERE r.DEMAND_LINE_ID = g.DEMAND_LINE_ID;

Reporting use cases are limited; the table is relevant mainly to legacy release-management reconciliation and to verifying that integration kit demand records have been fully superseded by supported WMS replenishment objects.

Related Objects

The documented foreign-key relationship identifies one dependent object:

• WMS_REPL_DEMAND_GTMP — references RLA_DEMAND_LINES_ALL via DEMAND_LINE_ID. This is a global temporary table (suffix _GTMP) used in WMS replenishment processing, and its dependency on the RLA demand line suggests the release-management demand data feeds replenishment staging.

Because the Data Vault classification is standalone, no hub or link parents are documented. Broader integration with Release Management objects, demand interfaces, or WMS replenishment APIs may exist in legacy deployments, but the ETRM metadata confirms only the WMS_REPL_DEMAND_GTMP reference as a reliable join path.