Search Results default_datatype_name




Overview
Explore in AI Chat

Overview

APPS.FND_DOC_CATEGORIES_ACTIVE_VL is a multilingual (language-resolved) view in the Oracle E-Business Suite APPS schema that presents document categories defined in the Oracle Application Object Library. Its central purpose is to resolve two distinct issues: which language-specific translation of a document category name should be returned to the calling session, and which categories are currently active based on their Start Date Active and End Date Active values. The suffix "VL" designates a "Value List" or language-resolved view, which is the standard naming convention Oracle uses for views that join a base (_B or _S) table with its translation (_TL) table and screen out expired rows.

Because it filters out inactive and not-yet-active categories, this view is the preferred access point for reporting, forms, and integrations that need only currently valid document categories. It is a runtime convenience layer: it handles the language joining logic so that each session automatically receives the appropriate translated USER_NAME, rather than forcing every consumer to replicate the translation join.

Underlying Base Objects

The documented ETRM metadata identifies three referenced base objects for this view, all referenced through APPS synonyms:

The view therefore performs a language join between the base category table and its translation table, filters rows whose effective dates make them inactive, and resolves the datatype name through a lookup join. The row identifier is exposed as ROW_ID and the primary key as CATEGORY_ID, sourced from the FND_DOCUMENTS_CATEGORIES_S sequence.

Key Columns

  • CATEGORY_ID (NUMBER) — unique identifier for the category, sourced from the FND_DOCUMENTS_CATEGORIES_S sequence.
  • NAME (VARCHAR2(30)) — the developer name for the category, language-independent.
  • USER_NAME (VARCHAR2(255)) — the language-dependent user-facing category name.
  • START_DATE_ACTIVE / END_DATE_ACTIVE (DATE) — the effective date range; the view uses these to exclude inactive categories.
  • DEFAULT_DATATYPE_ID (NUMBER) — identifier of the default datatype for the category.
  • DEFAULT_DATATYPE_NAME (VARCHAR2(80)) — the internal name for the default datatype, which is the column most relevant to the search term "default_datatype_name".
  • APPLICATION_ID (NUMBER) — the application that owns the category.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — Descriptive Flexfield segments that carry customer-defined attributes.
  • Standard Who columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical uses include populating category LOVs, driving document management integration interfaces, and reporting on which datatype is associated with each category. Because the view filters expired rows, querying it yields only categories valid for the current date.

To list active categories and their default datatypes:

  • SELECT category_id, user_name, name, default_datatype_id, default_datatype_name FROM apps.fnd_doc_categories_active_vl ORDER BY user_name;

To restrict results to a specific owning application:

  • SELECT category_id, user_name, default_datatype_name FROM apps.fnd_doc_categories_active_vl WHERE application_id = :app_id AND default_datatype_name IS NOT NULL;

To find categories lacking a default datatype (useful during configuration audits):

  • SELECT category_id, user_name FROM apps.fnd_doc_categories_active_vl WHERE default_datatype_id IS NULL;