Search Results rla_demand_headers_archive_pk

Overview

RLA_DEMAND_HEADERS_ARCHIVE_ALL is an archived demand header table belonging to the RLA - Release Management Integration Kit, a module classified in Oracle E-Business Suite documentation as obsolete. In EBS 12.1.1 and 12.2.2 the table retains its definition for backward compatibility only; it is shipped as a dormant seed object and is not populated or maintained by the core application. Its purpose, as reflected in its name, is to preserve historical release-management demand header records once they are removed from active transaction tables.

From a Data Vault modeling perspective, the mined relationship structure classifies this object heuristically as a standalone construct. Because no foreign keys are documented against it, it behaves as a self-contained historical snapshot rather than a hub-and-satellite or link structure. Practitioners modeling legacy RLA data should treat it as an isolated archive entity rather than an integrated component of a conformed data warehouse.

Key Information Stored

Documented metadata for this table is intentionally sparse, consistent with its obsolete status. The following attributes are documented:

• DEMAND_HEADER_ID – Surrogate identifier for the archived demand header, inherited from the operational demand header table.
• ARCHIVE_TIMESTAMP – The point in time at which the demand header record was moved into the archive.

The composite primary key is enforced through the index RLA_DEMAND_HEADERS_ARCHIVE_PK, defined on (DEMAND_HEADER_ID, ARCHIVE_TIMESTAMP). This composite structure is significant: it means a single demand header may legitimately appear multiple times if it was archived more than once across successive purge cycles. DEMAND_HEADER_ID functions as the business-key candidate carried over from transactional processing, while ARCHIVE_TIMESTAMP supplies the temporal or versioning component. Because the EBS repository reports the object as not implemented in the database, no additional functional columns are documented, and any further attributes can only be inferred by inspecting a live installation where the object has been deliberately created.

Common Use Cases and Queries

Realistic use cases are limited. The primary scenario is historical traceability: confirming whether a given demand header was ever archived, and under which purge cycle. A typical verification query takes the form:

• SELECT DEMAND_HEADER_ID, ARCHIVE_TIMESTAMP FROM RLA_DEMAND_HEADERS_ARCHIVE_ALL WHERE DEMAND_HEADER_ID = :id ORDER BY ARCHIVE_TIMESTAMP DESC;
• Count of archived headers per purge batch: SELECT TRUNC(ARCHIVE_TIMESTAMP), COUNT(*) FROM RLA_DEMAND_HEADERS_ARCHIVE_ALL GROUP BY TRUNC(ARCHIVE_TIMESTAMP);
• Existence check before a repeat purge: joining the composite key back to the live header table on DEMAND_HEADER_ID.

Because the table is obsolete and absent from the shipped schema, these patterns are relevant only where a customer has custom code or a legacy release-management integration that creates and populates it. Standard RLA reporting and reconciliation routines do not depend on it, and no supported concurrent program maintains it in current releases.

Related Objects

The documented relationship data identifies no foreign keys, so related objects are inferred from the RLA demand-header lineage rather than from constraints:

• RLA_DEMAND_HEADERS_ALL – The operational demand header table; DEMAND_HEADER_ID is the shared join column.
• RLA_DEMAND_LINES_ARCHIVE_ALL – Archived demand lines that would link to the header on DEMAND_HEADER_ID.
• RLA_DEMAND_LINES_ALL – Live demand lines, the purge source for the archived equivalent.
• RLA_DEMAND_HEADERS_ARCHIVE_PK – The composite primary key index on (DEMAND_HEADER_ID, ARCHIVE_TIMESTAMP).

No RLA public API or concurrent program is documented against this archive table, which further confirms its dormant, retention-only role. Administrators encountering the object during schema review should treat it as a legacy artifact eligible for documentation rather than active integration.