Search Results ahl_di_upload_file_type

Overview

APPS.AHL_DOC_FILE_ASSOC_V is a reporting and integration view in the Oracle E-Business Suite Discrete Manufacturing / Enterprise Asset Management (EAM) product family, specifically within the AHL (maintenance and asset documentation) schema. It exposes document file associations together with the decoded meaning of each association's data type. The view is a joined, decoded presentation layer built on top of the AHL_DOC_FILE_ASSOC_VL base view, which itself carries the multilingual (VL) file-association records. By joining to FND_LOOKUP_VALUES_VL, the view resolves the coded lookup value DATATYPE_CODE into a translatable MEANING, so that concurrent programs, forms, and integrations can present readable file-type descriptions rather than raw codes. The lookup type driving this decode is AHL_DI_UPLOAD_FILE_TYPE, which is the subject of the user's search term "ahl_di_upload_file_type" — that lookup type governs the classification of files uploaded and associated with AHL documents.

Underlying Base Objects

Per the documented metadata, the view is defined over two referenced base objects:

• AHL_DOC_FILE_ASSOC_VL (VIEW) — the primary source, aliased ADB. It supplies the association identifier, file identifier, file name, revision, datatype code, description, and the full descriptive flexfield (DFF) attribute set (ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15).
• FND_LOOKUP_VALUES_VL (VIEW) — the lookup source, aliased FND, restricted to LOOKUP_TYPE = 'AHL_DI_UPLOAD_FILE_TYPE'. It supplies the decoded MEANING for each DATATYPE_CODE.

The join is expressed as an outer join on the lookup side: FND.LOOKUP_CODE (+) = ADB.DATATYPE_CODE AND FND.LOOKUP_TYPE (+) = 'AHL_DI_UPLOAD_FILE_TYPE'. Because the join is outer, every row from AHL_DOC_FILE_ASSOC_VL is preserved even when no matching lookup value exists, in which case MEANING is null. This design ensures that file associations are never dropped simply because the upload file type lookup has not been configured or has been end-dated.

Key Columns

• ASSOCIATION_ID — Unique identifier of the document/file association row; the primary key derived from the VL base view.
• FILE_ID — Identifier of the associated file record.
• FILE_NAME — The stored file name of the associated document.
• REVISION_ID — Revision context for the association, supporting versioned document management.
• DATATYPE_CODE — The coded upload file type; this is the column that joins to the AHL_DI_UPLOAD_FILE_TYPE lookup.
• MEANING — The decoded, translatable description of DATATYPE_CODE obtained from FND_LOOKUP_VALUES_VL.
• FILE_DESC — Free-text description of the file association.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — The descriptive flexfield segments available for customer-specific extensions of the association.

Common Use Cases and Queries

The view is typically used to report on files attached to AHL documents with their file types rendered in user-friendly form, and to validate that uploaded files carry correctly configured upload file type codes. A representative query lists associations with their decoded types:

• SELECT association_id, file_id, file_name, datatype_code, meaning FROM apps.ahl_doc_file_assoc_v WHERE datatype_code = :p_datatype_code;
• SELECT datatype_code, meaning, COUNT(*) FROM apps.ahl_doc_file_assoc_v GROUP BY datatype_code, meaning ORDER BY datatype_code;
• SELECT association_id, file_name, file_desc, attribute_category FROM apps.ahl_doc_file_assoc_v WHERE meaning IS NULL;

The third query is particularly useful: since the lookup join is an outer join, rows with a null MEANING reveal DATATYPE_CODE values that are not defined for the AHL_DI_UPLOAD_FILE_TYPE lookup, indicating configuration gaps in the upload file type setup. It is recommended that queries join with the lookup code rather than assuming MEANING is always populated, and that the view be referenced as APPS.AHL_DOC_FILE_ASSOC_V with appropriate grants for reporting and integration responsibilities.