Results for “issue_number”

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

Overview

The AHL_DOC_REVISIONS_B table is a core base table within the Oracle E-Business Suite module AHL - Complex Maintenance Repair and Overhaul. It stores revision-level information for documents managed in the AHL document control framework, which supports configuration management, engineering documentation, and maintenance procedure control in complex MRO and aerospace/defense environments. Each row in this table represents a specific revision of a parent document, capturing revision identity, lifecycle dates, approval and effectivity information, media classification, and descriptive attributes.

The table holds 42 documented columns and is owned by the AHL schema. It carries an audit-compliant structure typical of EBS base tables, including the standard WHO columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN) and an OBJECT_VERSION_NUMBER for optimistic locking. A SECURITY_GROUP_ID column indicates multi-tenant or operating unit awareness via FND_SECURITY_GROUPS.

Based on a heuristic Data Vault classification mined from its foreign key structure, this table leans toward being a hub. That is a modeling suggestion: the table's declared identity is driven by a surrogate primary key and a business unique key referencing a parent document, making it a natural candidate for a hub entity in a Data Vault representation, though it also carries descriptive and date attributes that would typically be split into an associated satellite.

Key Information Stored

The most significant columns in AHL_DOC_REVISIONS_B include:

• DOC_REVISION_ID — The surrogate primary key of the table (AHL_DOC_REVISIONS_B_PK), which also serves as a unique index (AHL_DOC_REVISIONS_B_U1). It uniquely identifies each document revision.
• DOCUMENT_ID — Foreign key to AHL_DOCUMENTS_B, linking the revision to its parent document. Together with REVISION_NO, it forms the secondary unique index (AHL_DOC_REVISIONS_B_U2), a business-key candidate.
• REVISION_NO — The revision identifier or label assigned to this revision of the document.
• REVISION_TYPE_CODE and REVISION_STATUS_CODE — Classify the revision's nature and its lifecycle state (for example, draft, approved, obsolete).
• REVISION_DATE, APPROVED_DATE, EFFECTIVE_DATE, OBSOLETE_DATE, ISSUE_DATE, RECEIVED_DATE — Date attributes documenting the revision's lifecycle, from drafting through approval, effectivity, and obsolescence.
• APPROVED_BY_PARTY_ID — Foreign key to HZ_PARTIES, identifying the party responsible for approving the revision.
• URL and MEDIA_TYPE_CODE — Location and media classification of the revision's content.
• VOLUME, ISSUE, ISSUE_NUMBER — Publishing identifiers relevant to controlled documentation schemes.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, supporting security and data access partitioning.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — The standard EBS descriptive flexfield (DFF) columns for extensible, site-specific data.
• ENIGMA_DOC_ID and ENIGMA_MODEL_CODE — Integration columns linking the revision to external Enigma documentation or model systems.

Common Use Cases and Queries

Typical use cases include configuration-management reporting, effectivity tracking, approval audit trails, and integration with external documentation platforms such as Enigma. Common queries include:

• Listing all revisions for a given document:

  SELECT DOC_REVISION_ID, REVISION_NO, REVISION_STATUS_CODE, EFFECTIVE_DATE FROM AHL_DOC_REVISIONS_B WHERE DOCUMENT_ID = :document_id ORDER BY REVISION_DATE;

• Identifying currently effective revisions:

  SELECT * FROM AHL_DOC_REVISIONS_B WHERE EFFECTIVE_DATE <= SYSDATE AND (OBSOLETE_DATE IS NULL OR OBSOLETE_DATE > SYSDATE);

• Reporting approvals by approving party:

  SELECT APPROVED_BY_PARTY_ID, COUNT(*) FROM AHL_DOC_REVISIONS_B WHERE REVISION_STATUS_CODE = 'APPROVED' GROUP BY APPROVED_BY_PARTY_ID;

• Joining to parent documents to retrieve both revision and document context:

  SELECT d.DOCUMENT_ID, r.REVISION_NO, r.REVISION_STATUS_CODE FROM AHL_DOCUMENTS_B d JOIN AHL_DOC_REVISIONS_B r ON d.DOCUMENT_ID = r.DOCUMENT_ID;

These patterns support maintenance-engineering QA, change control, and regulatory compliance reporting.

Related Objects

• AHL_DOCUMENTS_B — Parent document table; joined via AHL_DOC_REVISIONS_B.DOCUMENT_ID.
• HZ_PARTIES — Party master; joined via APPROVED_BY_PARTY_ID to identify approvers.
• FND_SECURITY_GROUPS — Security grouping; joined via SECURITY_GROUP_ID.
• AHL_DOC_REVISIONS_TL — Translation table keyed on DOC_REVISION_ID, holding language-specific revision text.
• AHL_DOC_FILE_ASSOC_B — Associates uploaded files with revisions via REVISION_ID.
• AHL_DOC_REVISION_COPIES — Stores distribution or copy records linked by DOC_REVISION_ID.
• AHL_DOC_TITLE_ASSOS_B — Associates titles with revisions via DOC_REVISION_ID.

These relationships make AHL_DOC_REVISIONS_B a central junction point for document control, file storage, translation, and party approval data within the AHL module.