Results for “ahl_document_sub_types”

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

Overview

The AHL_DOCUMENT_SUB_TYPES table resides in the AHL schema, which supports the Complex Maintenance Repair and Overhaul (AHL) product within Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to store association information between document types and document sub types. In practical terms, it acts as a controlled vocabulary or cross-reference table that enumerates the valid combinations of a higher-level document type and its subordinate document sub type, allowing AHL document management features to validate and categorize documents consistently across maintenance, overhaul, and repair workflows.

From a data modeling perspective, the mined Data Vault classification for this table is standalone. This is a heuristic suggestion rather than a formally declared classification. Because the table holds descriptive business-key pairs and has no documented foreign keys to other AHL tables (only a reference to FND_SECURITY_GROUPS), it behaves less like a hub or link and more like a reference or lookup structure. Modelers could treat it as a small reference dimension or satellite of allowable document type/sub type combinations, but the metadata does not mandate any Data Vault construct.

Key Information Stored

The table contains 26 documented columns. The most significant are summarized below, with the surrogate key and business-key candidates distinguished where documented.

• DOCUMENT_SUB_TYPE_ID — The surrogate primary key, enforced by AHL_DOCUMENT_SUB_TYPES_PK and also by unique index AHL_DOCUMENT_SUB_TYPES_U1. It uniquely identifies each association row.
• DOC_TYPE_CODE — The document type code, the higher-level classification in the type/sub type pairing.
• DOC_SUB_TYPE_CODE — The document sub type code, the subordinate classification. This is the column most commonly searched by users (the term doc_sub_type_code maps directly to this column).
• DOC_TYPE_CODE + DOC_SUB_TYPE_CODE — Together these form the business-key candidate enforced by unique index AHL_DOCUMENT_SUB_TYPES_U2, ensuring no duplicate type/sub type combination is defined.
• SECURITY_GROUP_ID — References FND_SECURITY_GROUPS, supporting multi-org or security-restricted data access.
• OBJECT_VERSION_NUMBER — Used for optimistic locking and concurrent update control.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard EBS WHO columns capturing audit and accountability information.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — The OAF-style descriptive flexfield (DFF) columns, provided for customer extensibility without schema changes.

Common Use Cases and Queries

Typical scenarios include validating user-entered document sub type codes, populating LOV (List of Values) for document classification, and reporting on which sub types are permitted for a given document type.

• Resolve a searched code to its parent type: SELECT document_sub_type_id, doc_type_code, doc_sub_type_code FROM ahl_document_sub_types WHERE doc_sub_type_code = :code;
• List all sub types for a type: SELECT doc_sub_type_code FROM ahl_document_sub_types WHERE doc_type_code = :type ORDER BY doc_sub_type_code;
• Confirm uniqueness prior to insert by checking the (DOC_TYPE_CODE, DOC_SUB_TYPE_CODE) pair against AHL_DOCUMENT_SUB_TYPES_U2.
• Extensibility reporting against ATTRIBUTE1–ATTRIBUTE15 when customers have configured the DFF.

Related Objects

• FND_SECURITY_GROUPS — Referenced by SECURITY_GROUP_ID; governs security group assignment for each row.
• AHL_DOCUMENT_TYPES — The higher-level table whose type codes are paired here; logically joined on DOC_TYPE_CODE.
• AHL_DOCUMENTS / AHL document base tables — Consume the type/sub type pairing to categorize actual document records.
• FND_LOOKUPS — If sub type values are driven from lookup codes, joined on LOOKUP_CODE matching DOC_SUB_TYPE_CODE.
• OAF/VO-based AHL document pages and AHL public APIs — Read this table when validating and displaying document classifications.

The table is compact, stable, and primarily reference-oriented, making it straightforward to query and low-risk to integrate into reporting and validation logic.