Results for “ahl_doc_title_assos_b”

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

Overview

AHL_DOC_TITLE_ASSOS_B is a transactional table in the AHL schema, which supports the Complex Maintenance Repair and Overhaul (CMRO) module of Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. The table stores association records that link a document or a document revision to an ASO (Asset/Service Object) entity. An ASO object may be a route, a master configuration, a unit configuration, or a comparable maintainable asset structure. The table therefore acts as the junction between the document management model and the asset configuration model, enabling technicians and engineers to attach controlled documentation (procedures, drawings, work instructions, specifications) to the maintainable items they describe.

The entity is registered as VALID in the ETRM metadata and contains 31 documented columns. It carries the standard EBS audit columns (WHO columns) and the multi-organization security column SECURITY_GROUP_ID, which indicates it participates in the Applications security group model. Based on the mined foreign key topology, the heuristic Data Vault classification is satellite-leaning. In modeling terms this suggests AHL_DOC_TITLE_ASSOS_B behaves less like a pure hub of unique business keys and more like a satellite of descriptive relationship state attached to the document and ASO hubs, with its own surrogate identity.

Key Information Stored

The surrogate primary key is DOC_TITLE_ASSO_ID, enforced by the index AHL_DOC_TITLE_ASSOS_B_PK. A separate unique index, AHL_DOC_TITLE_ASSOS_B_U1, also constrains DOC_TITLE_ASSO_ID, so the surrogate key doubles as the sole documented business-key candidate. The most operationally significant columns are:

• DOC_TITLE_ASSO_ID — surrogate primary key identifying each association row.
• DOCUMENT_ID — foreign key to AHL_DOCUMENTS_B; identifies the parent document (title) record.
• DOC_REVISION_ID — foreign key to AHL_DOC_REVISIONS_B; pinpoints the specific revision when the association applies to a revision rather than the document header.
• ASO_OBJECT_ID — polymorphic foreign key pointing to the associated asset object, resolved through AHL_ROUTES_B, AHL_OPERATIONS_B, or other ASO entity tables.
• ASO_OBJECT_TYPE_CODE — discriminator that determines which entity the ASO_OBJECT_ID refers to, such as route, master configuration, or unit configuration.
• USE_LATEST_REV_FLAG — indicates whether the association should always resolve to the latest revision of the document.
• SERIAL_NO — optional serial number qualification for the associated object, useful in unit-level configuration scenarios.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, controlling row visibility by security group.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the OAF/ADF framework for concurrent update detection.
• 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 descriptive flexfield (DFF) segment columns for customer-defined extensions.
• SOURCE_REF_CODE — identifies the originating source system or reference for the association, supporting data migration and integration traceability.

Common Use Cases and Queries

The principal use case is document-to-asset traceability: determining which documents or revisions are approved for a given route, configuration, or operation, and conversely which assets a document governs. This supports compliance reporting, maintenance procedure validation, and revision control audits. A representative query joins the association to the document header:

• SELECT a.DOC_TITLE_ASSO_ID, a.DOCUMENT_ID, a.DOC_REVISION_ID, a.ASO_OBJECT_TYPE_CODE, a.ASO_OBJECT_ID, a.USE_LATEST_REV_FLAG FROM AHL.AHL_DOC_TITLE_ASSOS_B a WHERE a.ASO_OBJECT_TYPE_CODE = :type AND a.ASO_OBJECT_ID = :object_id;
• To resolve document titles, join AHL_DOCUMENTS_B on DOCUMENT_ID and AHL_DOC_REVISIONS_B on DOC_REVISION_ID.
• To list associations that always follow the latest revision, filter on USE_LATEST_REV_FLAG = 'Y'.
• Security group scoping is applied by joining FND_SECURITY_GROUPS on SECURITY_GROUP_ID.

Report consumers typically drive these queries from the ASO master configuration or route side, since maintenance planners start from the asset and ask which documentation applies.

Related Objects

• AHL_DOCUMENTS_B — parent document header; joined via DOCUMENT_ID.
• AHL_DOC_REVISIONS_B — document revision detail; joined via DOC_REVISION_ID.
• AHL_ROUTES_B — route definitions referenced through ASO_OBJECT_ID.
• AHL_OPERATIONS_B — operation definitions also referenced through ASO_OBJECT_ID.
• AHL_DOC_TITLE_ASSOS_TL — translated/child table referencing AHL_DOC_TITLE_ASSOS_B via DOC_TITLE_ASSO_ID.
• FND_SECURITY_GROUPS — security group reference for SECURITY_GROUP_ID.

Collectively these relationships establish AHL_DOC_TITLE_ASSOS_B as the central linkage point between CMRO document control and asset configuration data.