Results for “as_ref_deliverables”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AS_REF_DELIVERABLES is a table within the Oracle E-Business Suite Release 12.1.1 and 12.2.2 Sales Foundation (AS) product family. According to Oracle ETRM documentation, the table is classified as "No Longer Used," and the same metadata indicates it is "Not implemented in this database." This designation is significant for implementers and support analysts: the object is a legacy artifact retained in the ETRM data dictionary for historical and referential completeness rather than as an active component of the shipped R12 schema. The table historically modeled reference deliverables associated with trade management or sales foundation reference data, and its structure survives in documentation primarily so that dependency chains and upgrade scripts referencing it can be understood.

From a data modeling perspective, the metadata’s heuristic Data Vault classification is hub-leaning. This suggests the table functioned as a hub entity, defined by a single surrogate primary key and referenced by multiple dependent tables. In practice, this means DELIVERABLE_ID served as a durable business identifier for a deliverable concept, with downstream transactional and attribute detail distributed across satellite-style tables such as AS_REF_ASSETS, AS_REF_RESTRICTIONS, and AS_REF_ACT_SCHEDULES.

Key Information Stored

The documented metadata exposes a deliberately small set of columns, consistent with a hub-leaning structure:

• DELIVERABLE_ID — the surrogate primary key, enforced by constraint AS_REF_DELIVERABLES_PK. It is the sole documented column and the join anchor for all child tables.
• REFERENCE_ID — a foreign key column referencing HZ_REFERENCES, tying each deliverable record to a Trading Community Architecture (TCA) reference entity. This linkage places the table within the customer and reference-data model rather than an independent sales domain.

No unique business-key index is documented beyond the primary key, so DELIVERABLE_ID should be treated as both the surrogate and the effective business identifier in any surviving script. Because the table is marked "No Longer Used," no additional descriptive columns — such as deliverable name, status, or effective dates — are enumerated in the current ETRM entry. Implementers should not assume the presence of columns beyond those documented, particularly in upgraded environments where the object may exist as a stub or may be entirely absent.

Common Use Cases and Queries

Because the table is not implemented in current databases, direct querying is unlikely. The principal use cases are diagnostic and migration-related:

• Verifying whether the object exists in a specific environment during upgrade analysis, typically via ALL_TABLES or DBA_TABLES lookups.
• Tracing foreign-key dependencies when deprecating or dropping legacy AS objects, since child tables AS_REF_ASSETS, AS_REF_RESTRICTIONS, and AS_REF_ACT_SCHEDULES still reference DELIVERABLE_ID.
• Reconstructing historical data lineage for reporting extracts that predate the deprecation.

A representative existence check follows:

SELECT table_name, num_rows FROM dba_tables WHERE table_name = 'AS_REF_DELIVERABLES';

A dependency trace joining the primary key to the child tables would resemble:

SELECT d.deliverable_id, d.reference_id, a.asset_id FROM as_ref_deliverables d LEFT JOIN as_ref_assets a ON a.deliverable_id = d.deliverable_id;

Related Objects

The documented foreign-key relationships identify the following significant dependent objects:

• HZ_REFERENCES — referenced by AS_REF_DELIVERABLES.REFERENCE_ID; supplies the TCA reference context.
• AS_REF_ACT_SCHEDULES — references DELIVERABLE_ID; holds activity scheduling detail.
• AS_REF_ASSETS — references DELIVERABLE_ID; holds asset-related attributes of a deliverable.
• AS_REF_RESTRICTIONS — references DELIVERABLE_ID; holds restriction or eligibility data.

Together these tables formed the reference-deliverable constellation within Sales Foundation. In R12.2.2 environments, functional equivalents are generally found elsewhere in the AS or trade management schema, and AS_REF_DELIVERABLES should be treated strictly as a deprecated legacy object.