Search Results archive_timestamp

Overview

The view RLA_DEMAND_HEADERS_ARCHIVE belongs to the RLA product family — Release Management Integration Kit, which is documented as obsolete in Oracle EBS 12.1.1 and 12.2.2. The view is classified as a SINGLE-ORG view, meaning it is designed to expose data for a single operating unit (organization) context rather than the multi-org security model used by _ALL tables. It presents archived demand header records, preserving the header-level detail of demand transactions that have been moved out of the active transaction tables into an archive structure for historical reporting, reconciliation, and integration with external release management or order fulfillment processes.

The view text confirms that it is a thin projection over the archived base table, filtering rows by the current organization derived from the session context (USERENV('CLIENT_INFO')). This is the classic pre-12.2 single-org pattern in which the ORG_ID is resolved through a 10-character client info string. Its primary role is to allow queries against archived demand data with the same column layout as the live demand headers, supporting retention and audit requirements without exposing multi-org logic.

Underlying Base Objects

The view is defined over a single underlying table named in the WHERE clause: RLA_DEMAND_HEADERS_ARCHIVE_ALL. No other base objects are documented. The _ALL suffix indicates that the table stores rows for all organizations, and each row carries an ORG_ID. The view applies an org filter using the following predicate:

• NVL(ORG_ID, NVL(TO_NUMBER(DECODE(SUBSTRB(USERENV('CLIENT_INFO'),1,1),' ',NULL,SUBSTRB(USERENV('CLIENT_INFO'),1,10))),-99)) equated to the same expression, matching the stored organization to the session organization, defaulting to -99 when the client info is blank.
• This confirms that RLA_DEMAND_HEADERS_ARCHIVE_ALL is the sole documented base object and that the view inherits its column structure directly.

Because the view simply selects every column from the archive table, its definition is identical to the archive table's column list. No joins, aggregations, or derived columns are present.

Key Columns

The column list mirrors the archived demand header structure. Notable columns include:

• ASN_SEQ_NUMBER — the Advanced Shipment Notice sequence number associated with the demand header; this is the column the user searched for, and it links the archived demand to shipment notification records.
• DEMAND_HEADER_ID — the primary identifier of the demand header record.
• ORDER_HEADER_ID, ORDER_NUMBER, ORDER_TYPE_ID — order-level linkage to the originating sales or return order.
• CUSTOMER_ID, CUSTOMER_NUMBER, BILL_TO_ADDRESS_ID, BILL_TO_SITE_USE_ID — customer and billing address context.
• PURCHASE_ORDER_NUMBER — the customer purchase order reference.
• ORG_ID — the organization identifier used by the single-org filter.
• ARCHIVE_TIMESTAMP — when the record was archived, distinct from CREATION_DATE and LAST_UPDATE_DATE.
• Standard audit and context columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE, REQUEST_ID.
• Descriptive flexfield columns: ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15.

Common Use Cases and Queries

Typical uses include historical reporting on demand headers, reconciling archived shipments using ASN sequence numbers, and supporting release management integration audits. A representative query follows:

• SELECT DEMAND_HEADER_ID, ORDER_NUMBER, CUSTOMER_NUMBER, ASN_SEQ_NUMBER, ARCHIVE_TIMESTAMP FROM RLA_DEMAND_HEADERS_ARCHIVE WHERE ORG_ID = :org_id AND ORDER_NUMBER = :order_number;
• SELECT ASN_SEQ_NUMBER, COUNT(*) FROM RLA_DEMAND_HEADERS_ARCHIVE GROUP BY ASN_SEQ_NUMBER;
• SELECT * FROM RLA_DEMAND_HEADERS_ARCHIVE WHERE PURCHASE_ORDER_NUMBER = :po_number ORDER BY ARCHIVE_TIMESTAMP DESC;

Because the product is obsolete and the view is not implemented in all databases, availability should be verified against the database dictionary before reliance in production reporting.