Search Results ahl_doc_file_assoc_v




Overview
Explore in AI Chat

Overview

Within Oracle E-Business Suite, the view APPS.AHL_DOC_FILE_ASSOC_V belongs to the AHL product family — Complex Maintenance Repair and Overhaul (CMRO), a module used extensively in aerospace, defense, and heavy-asset maintenance environments. The view exposes the association between uploaded files and the documents and revisions they belong to. Its documented description states that it "stores the File uploaded with Document ID and Revision," which positions it as the reporting and integration layer over the storage of document file attachments maintained inside the AHL document repository.

The object is registered in the ETRM metadata with Owner/Schema APPS, Object Type VIEW, and Status VALID. Because it is a view rather than a base table, all access is read-only by design. It is intended for query, reporting, and interface extraction rather than direct DML. In both 12.1.1 and 12.2.2 the object remains a documented, valid member of the AHL schema footprint.

Underlying Base Objects

The view is defined over two documented sources:

  • AHL_DOC_FILE_ASSOC_VL (VIEW) — the "VL" (view language) layer, which supplies the translatable and base file-association columns.
  • FND_LOOKUP_VALUES_VL (VIEW) — the standard Oracle lookup view, joined to translate the datatype code into a user-facing meaning.

The join is an outer join on the lookup table, expressed as FND.LOOKUP_CODE (+) = ADB.DATATYPE_CODE, filtered by FND.LOOKUP_TYPE (+) = 'AHL_DI_UPLOAD_FILE_TYPE'. The outer-join syntax preserves file rows that have no matching lookup entry, returning a null MEANING in that case. The lookup type AHL_DI_UPLOAD_FILE_TYPE is the AHL reference list that classifies the uploaded file's datatype.

Key Columns

  • ASSOCIATION_ID — unique identifier of the file-to-document/revision association row.
  • FILE_ID — reference to the stored file entity.
  • FILE_NAME — the name under which the file was uploaded.
  • REVISION_ID — the document revision the file is attached to, tying the file to a specific revision of a document.
  • DATATYPE_CODE — coded upload file type, drawn from lookup type AHL_DI_UPLOAD_FILE_TYPE.
  • MEANING — the translated, display-friendly description of DATATYPE_CODE.
  • FILE_DESC — free-text description of the uploaded file.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard Oracle DFF (descriptive flexfield) columns, allowing client-specific metadata to be captured without schema changes.

Common Use Cases and Queries

Typical usage includes reporting on files attached to AHL documents, auditing which revisions carry which uploads, and extracting file metadata for downstream DMS or archival feeds. Because MEANING is already resolved from the lookup, reports avoid a second lookup join.

List all file associations for a given revision:

SELECT association_id, file_id, file_name, datatype_code, meaning, file_desc
FROM apps.ahl_doc_file_assoc_v
WHERE revision_id = :p_revision_id;

Report files grouped by upload datatype:

SELECT datatype_code, meaning, COUNT(*)
FROM apps.ahl_doc_file_assoc_v
GROUP BY datatype_code, meaning;

Retrieve descriptive flexfield context values for integration:

SELECT association_id, attribute_category, attribute1, attribute2
FROM apps.ahl_doc_file_assoc_v
WHERE attribute_category IS NOT NULL;

Because the view is read-only and in the APPS schema, access should be granted through standard AHL responsibility and menu structures rather than direct grants, and queries should be run with the appropriate MO or operating unit context where the underlying association rows are secured.