Search Results atchmt_document_type
Overview
APPS.FND_DOCUMENTS_VL is a multilingual (VL) reporting view in the Oracle E-Business Suite Applications (APPS) schema that consolidates document attachment metadata from a set of normalized base tables into a single, denormalized, translated projection. Its principal role is to expose attachment and document records together with their human-readable translated names, descriptions, category names, data-type names, and the meaning of the attachment usage type, so that forms, concurrent programs, and custom reports can query attachment information without performing the multi-table joins themselves. The view is defined so that each of the underlying translated tables is joined on the session language (USERENV('LANG')), guaranteeing that only rows corresponding to the current runtime language are returned and that translated columns reflect the user's language environment. Because it resolves language-dependent values transparently, FND_DOCUMENTS_VL is the preferred access point for consumers that display document or attachment data to end users, whereas the base FND_DOCUMENTS table is used when raw, untranslated storage is required.
Underlying Base Objects
The view is defined over six documented base objects, all referenced through APPS synonyms: FND_DOCUMENTS, FND_DOCUMENTS_TL, FND_DOCUMENT_CATEGORIES, FND_DOCUMENT_CATEGORIES_TL, FND_DOCUMENT_DATATYPES, and FND_LOOKUP_VALUES. FND_DOCUMENTS is the master (non-translated) table, aliased D, and supplies the primary document identifier, storage attributes, security attributes, and territory-related columns such as DM_NODE, DM_FOLDER_PATH, DM_TYPE, DM_DOCUMENT_ID, DM_VERSION_NUMBER, and URL. FND_DOCUMENTS_TL (aliased DL) is joined on DOCUMENT_ID and per-language, supplying DESCRIPTION, TITLE, DOC_ATTRIBUTE_CATEGORY, and the fifteen DOC_ATTRIBUTE1..15 flexfield columns. FND_DOCUMENT_CATEGORIES (aliased C) supplies the category's APPLICATION_ID, joined via CATEGORY_ID, while FND_DOCUMENT_CATEGORIES_TL (aliased CL) returns the translated category USER_NAME for the session language. FND_DOCUMENT_DATATYPES (aliased DD) provides the translated USER_NAME of the data type through DATATYPE_ID. FND_LOOKUP_VALUES (aliased L) supplies the MEANING for the attachment usage type, constrained by LOOKUP_TYPE = 'ATCHMT_DOCUMENT_TYPE'. All translated joins carry the condition LANGUAGE = USERENV('LANG'), enforcing the multilingual (VL) behavior.
Key Columns
- DOCUMENT_ID — Primary identifier of the document/attachment record; the join key to all related tables.
- DATATYPE_ID / USER_NAME (DD) — Identifier and translated name of the document data type.
- CATEGORY_ID / USER_NAME (CL) / APPLICATION_ID — Category identifier, its translated name, and owning application.
- USAGE_TYPE / MEANING — The attachment usage type lookup code and its meaning from the ATCHMT_DOCUMENT_TYPE lookup type.
- FILE_NAME, MEDIA_ID, STORAGE_TYPE, URL, IMAGE_TYPE — Physical storage and access attributes of the attachment.
- SECURITY_TYPE, SECURITY_ID, PUBLISH_FLAG — Access-control and publication attributes.
- DESCRIPTION, TITLE — Translated descriptive text from FND_DOCUMENTS_TL.
- DOC_ATTRIBUTE_CATEGORY, DOC_ATTRIBUTE1..DOC_ATTRIBUTE15 — Descriptive flexfield context and segment values.
- DM_NODE, DM_FOLDER_PATH, DM_TYPE, DM_DOCUMENT_ID, DM_VERSION_NUMBER — Document-management integration attributes.
- START_DATE_ACTIVE, END_DATE_ACTIVE — Effective dating of the document record.
- ROWID, CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Standard WHO and concurrent-program audit columns.
Common Use Cases and Queries
The view is commonly used to list attachments by usage type, to locate documents by category or filename, and to feed integration extracts that require translated labels. Because the ATCHMT_DOCUMENT_TYPE lookup drives the MEANING column, the view is a natural starting point when investigating how attachment usage types are surfaced, which corresponds directly to the search term "atchmt_document_type." A typical query selecting documents of a given usage type is:
SELECT document_id, file_name, title, meaning, category_id FROM apps.fnd_documents_vl WHERE usage_type = 'YOUR_USAGE_CODE' AND TRUNC(SYSDATE) BETWEEN start_date_active AND NVL(end_date_active, TRUNC(SYSDATE));
To enumerate all available attachment usage types with their translated meanings, join through the lookup:
SELECT DISTINCT usage_type, meaning FROM apps.fnd_documents_vl ORDER BY meaning;
To locate documents by descriptive flexfield segment values, filter on DOC_ATTRIBUTE1..15, and to trace document-management folders use DM_FOLDER_PATH or DM_NODE. When maximum performance is required for large extracts, query the base tables directly with explicit language predicates, since the view's multiple outer-language joins can add cost. In all cases, remember that the view returns only rows whose language matches the session, so cross-language reporting must set USERENV('LANG') accordingly or query the _TL tables directly.
-
Lookup Type: ATCHMT_DOCUMENT_TYPE
12.2.2
product: FND - Application Object Library , meaning: ATCHMT DOCUMENT TYPE , description: Attachment document type ,
-
Lookup Type: ATCHMT_DOCUMENT_TYPE
12.1.1
product: FND - Application Object Library , meaning: ATCHMT DOCUMENT TYPE , description: Attachment document type ,
-
VIEW: APPS.FND_DOCUMENTS_VL
12.1.1
-
VIEW: APPS.FND_DOCUMENTS_VL
12.2.2
-
View: FND_DOCUMENTS_VL
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:FND.FND_DOCUMENTS_VL, object_name:FND_DOCUMENTS_VL, status:VALID, product: FND - Application Object Library , description: Resolves viewed language of a document , implementation_dba_data: APPS.FND_DOCUMENTS_VL ,
-
View: FND_DOCUMENTS_VL
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:FND.FND_DOCUMENTS_VL, object_name:FND_DOCUMENTS_VL, status:VALID, product: FND - Application Object Library , description: Resolves viewed language of a document , implementation_dba_data: APPS.FND_DOCUMENTS_VL ,
-
12.1.1 FND Design Data
12.1.1
-
APPS.CSM_LOOKUP_EVENT_PKG SQL Statements
12.1.1
-
APPS.CSM_LOOKUP_EVENT_PKG SQL Statements
12.2.2
-
12.2.2 FND Design Data
12.2.2
-
APPS.FND_ATTACHMENT_UTIL_PKG SQL Statements
12.1.1
-
APPS.FND_ATTACHMENT_UTIL_PKG SQL Statements
12.2.2
-
PACKAGE BODY: APPS.CSM_LOOKUP_EVENT_PKG
12.2.2
-
PACKAGE BODY: APPS.CSM_LOOKUP_EVENT_PKG
12.1.1
-
APPS.BIL_TX_OPTY_DETL_RPT_PKG SQL Statements
12.1.1
-
PACKAGE BODY: APPS.FND_ATTACHMENT_UTIL_PKG
12.1.1
-
PACKAGE BODY: APPS.FND_ATTACHMENT_UTIL_PKG
12.2.2
-
APPS.FND_ATTACHMENT_UTIL_PKG dependencies on FND_LOOKUP_VALUES
12.2.2
-
APPS.FND_ATTACHMENT_UTIL_PKG dependencies on FND_LOOKUP_VALUES
12.1.1
-
PACKAGE BODY: APPS.BIL_TX_OPTY_DETL_RPT_PKG
12.1.1