Results for “ahl_documents_b”

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

Overview

AHL_DOCUMENTS_B is the base (non-translated) table that stores information about documents within the AHL – Complex Maintenance Repair and Overhaul (CMRO) product in Oracle E-Business Suite 12.1.1 and 12.2.2. It is owned by the AHL schema and holds operational header data for documents managed through the CMRO document management functionality, which supports controlled aviation and MRO document lifecycles such as maintenance manuals, work instructions, and technical publications.

The table is the anchor of a broader document model. A paired translation table (AHL_DOCUMENTS_TL) supplies language-specific descriptive columns, while revisions, title associations, recipient mappings, subscriptions, and supplier mappings all reference the document header through the same surrogate key. Based on the foreign-key topology, the object behaves as a hub in a Data Vault modeling sense: it carries a single, stable business entity key and is referenced by multiple downstream tables rather than referencing them itself. This classification is a heuristic modeling suggestion, not a physical constraint.

Key Information Stored

The table contains 32 documented columns. The most significant include:

• DOCUMENT_ID – surrogate primary key, enforced by AHL_DOCUMENTS_B_PK and also present as unique index AHL_DOCUMENTS_B_U1. This is the value propagated to all child tables.
• DOCUMENT_NO – the user-facing business document number; unique index AHL_DOCUMENTS_B_U2 and unique key AHL_DOCUMENTS_B_UK1 mark it as the principal business-key candidate.
• SOURCE_PARTY_ID – foreign key to HZ_PARTIES, identifying the party that originated or owns the document.
• DOC_TYPE_CODE and DOC_SUB_TYPE_CODE – classification of the document by type and subtype.
• OPERATOR_CODE and PRODUCT_TYPE_CODE – operator and product context to which the document applies.
• SUBSCRIBE_AVAIL_FLAG and SUBSCRIBE_TO_FLAG – flags governing whether the document may be subscribed to and whether it is currently subscribed.
• SECURITY_GROUP_ID – foreign key to FND_SECURITY_GROUPS, supporting multi-org / security-group access control.
• OBJECT_VERSION_NUMBER – optimistic-locking column used by the Oracle framework during concurrent updates.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN – standard EBS audit ("WHO") columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 – the reserved DFF (descriptive flexfield) columns.

Common Use Cases and Queries

Typical reporting and integration scenarios resolve a document number to its surrogate identifier, filter documents by type or source party, or join the header to its translated description and revision history.

• Retrieve a document header for a given business number:

  SELECT document_id, document_no, doc_type_code, source_party_id
  FROM   ahl.ahl_documents_b
  WHERE  document_no = :p_document_no;

• Enumerate documents for a specific source party, joining to the trading partner:

  SELECT d.document_id, d.document_no, p.party_name
  FROM   ahl.ahl_documents_b d, hz_parties p
  WHERE  d.source_party_id = p.party_id;

• Report documents available for subscription:

  SELECT document_id, document_no, doc_type_code
  FROM   ahl.ahl_documents_b
  WHERE  subscribe_avail_flag = 'Y';

• Join the header to its translated description using AHL_DOCUMENTS_TL.DOCUMENT_ID for language-aware reporting.

Related Objects

The following objects depend on or reference AHL_DOCUMENTS_B, joined through DOCUMENT_ID unless noted:

• AHL_DOCUMENTS_TL – translation table supplying language-specific descriptive columns.
• AHL_DOC_REVISIONS_B – stores chronological revisions of each document.
• AHL_DOC_TITLE_ASSOS_B – associates documents with titles.
• AHL_RECIPIENT_DOCUMENTS – maps recipients to documents.
• AHL_SUBSCRIPTIONS_B – records subscriptions against documents.
• AHL_SUPPLIER_DOCUMENTS – links supplier records to documents.
• HZ_PARTIES – referenced via SOURCE_PARTY_ID to identify the originating party.
• FND_SECURITY_GROUPS – referenced via SECURITY_GROUP_ID for security-group access.