Results for “fnd_document_datatypes_vl”

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

Overview

FND_DOCUMENT_DATATYPES_VL is a translation-enabled (VL, or "view language") database view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the FND — Application Object Library product family, which supplies the shared infrastructure used across all EBS application modules. As its documented description states, the view presents data from the base table FND_DOCUMENT_DATATYPES "for translation purposes," exposing only the rows and columns relevant to the session's current language environment.

Document data types define the categories of attachments or documents that can be associated with EBS entities — for example, file-based documents, URL-based documents, or Oracle-native document types used by the Attachments (FND Attachments) framework. This view provides a language-specific, active-date-filtered projection of those definitions, making it suitable for reporting, integration, and lookup purposes where only currently valid, session-language document data types should be returned.

Underlying Base Objects

The view is defined over a single documented base object: the FND_DOCUMENT_DATATYPES table, referenced in ETRM 12.2.2 through a synonym in the APPS schema. The view text selects from FND_DOCUMENT_DATATYPES with two defining predicates:

• Language filter: LANGUAGE = USERENV('LANG'), restricting rows to the language of the current database session. This is the mechanism that makes the view a "VL" (translated) view.
• Active-date filter: NVL(START_DATE_ACTIVE, SYSDATE-1) <= SYSDATE and NVL(END_DATE_ACTIVE, SYSDATE+1) > SYSDATE, which returns only data types that are currently effective based on their start and end activation dates. Rows with null start dates are treated as always started, and rows with null end dates as never expired.

Because the view is read-only over its base table, it carries no independent storage and inherits the base table's data integrity and translation model.

Key Columns

• DATATYPE_ID — The unique identifier (primary key) of the document data type. This is the column most commonly referenced in foreign-key joins and the term the user searched for.
• NAME — The internal name of the data type, typically in the session language.
• USER_NAME — The user-facing (translated) display name of the data type, suitable for presentation in reports and lists of values.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS "Who" audit columns recording creation and last-update timestamps, the responsible application user, and the login context.

Common Use Cases and Queries

The view is typically used to resolve a DATATYPE_ID to its human-readable, translated name for a given session language, or to list all currently active document data types. A representative query is:

• SELECT datatype_id, name, user_name FROM fnd_document_datatypes_vl ORDER BY user_name;
• SELECT datatype_id, user_name FROM fnd_document_datatypes_vl WHERE datatype_id = :p_datatype_id;

Common scenarios include joining to attachment or document-usage tables on DATATYPE_ID to display meaningful type descriptions in custom concurrent programs, OAF pages, or BI Publisher reports; populating a list of values restricted to active, translated types; and integrating attachment metadata with external systems. Because the view already enforces language and active-date filtering, developers can rely on it instead of duplicating those predicates against the base table. All access is subject to the standard APPS schema grants and Oracle proprietary and confidentiality terms.