Search Results ahl_documents_b




Overview

The AHL_DOCUMENTS_B table is a core data entity within the Oracle E-Business Suite module for Complex Maintenance, Repair, and Overhaul (CMRO), designated by the AHL product code. It serves as the master repository for document header information, acting as the central reference point for all document-related data within the CMRO application. Its primary role is to store the fundamental metadata that defines a document, such as its identification numbers and source, while transactional details, revisions, and descriptive text are managed in related child tables. This structure supports the rigorous documentation requirements inherent in maintenance, repair, and regulatory compliance processes for complex assets.

Key Information Stored

While the provided metadata does not list all columns, the primary and foreign key relationships define the table's critical attributes. The central column is DOCUMENT_ID, the system-generated unique primary key (AHL_DOCUMENTS_B_PK) that identifies each document record. The DOCUMENT_NO column provides a unique business identifier or document number (enforced by the AHL_DOCUMENTS_B_UK1 unique key), which is likely used for external reference. Another significant column is SOURCE_PARTY_ID, a foreign key to the HZ_PARTIES table in the Trading Community Architecture (TCA) schema, which links the document to its originating organization or party. This establishes the document's source within the enterprise's unified party model.

Common Use Cases and Queries

This table is central to any process requiring document lookup, validation, or reporting within CMRO. Common use cases include retrieving a document's master record by its business number, generating a list of all documents sourced from a specific supplier or internal organization, or serving as the driving table for reports on document lifecycle and associations. A typical query would join AHL_DOCUMENTS_B to its descriptive translation table (AHL_DOCUMENTS_TL) to fetch the document title in a specific language. For example, to find a document by its number and retrieve its English title:

  • SELECT adb.DOCUMENT_ID, adb.DOCUMENT_NO, adtl.TITLE FROM AHL_DOCUMENTS_B adb, AHL_DOCUMENTS_TL adtl WHERE adb.DOCUMENT_ID = adtl.DOCUMENT_ID AND adtl.LANGUAGE = 'US' AND adb.DOCUMENT_NO = '<DOC_NUMBER>';

Another common pattern involves joining to HZ_PARTIES via SOURCE_PARTY_ID to include source party details in reports.

Related Objects

The AHL_DOCUMENTS_B table has a central role in the CMRO data model, with several key child tables referencing its primary key. As documented, the primary foreign key relationships are:

  • AHL_DOCUMENTS_TL: References DOCUMENT_ID to store translated descriptive information (e.g., TITLE) for the document.
  • AHL_DOC_REVISIONS_B: References DOCUMENT_ID to manage multiple revision records for a single document master.
  • AHL_DOC_TITLE_ASSOS_B: References DOCUMENT_ID to associate documents with specific item titles or configurations.
  • AHL_RECIPIENT_DOCUMENTS and AHL_SUPPLIER_DOCUMENTS: Reference DOCUMENT_ID to track document distribution to recipients and supplier-related document linkages.
  • AHL_SUBSCRIPTIONS_B: References DOCUMENT_ID to manage subscriptions or alerts related to the document.
  • HZ_PARTIES: Referenced by the SOURCE_PARTY_ID column to identify the document's source entity.