Search Results document_level

Overview

PO_UDA_AG_TEMPLATES_VL is a multilingual (VL) view owned by the APPS schema in Oracle E-Business Suite, belonging to the Purchasing (PO) product family. It is part of the User-Defined Attributes (UDA) and Attribute Grouping framework that underpins Oracle Purchasing extensibility, allowing implementers to define custom attribute templates that are validated and rendered against purchasing documents such as requisitions, purchase orders, and agreements. The view presents a language-specific, translated rendition of attribute grouping templates by joining the base template definition table with its translation table and filtering on the session language via USERENV('LANG'). Because it is a VL view, it exposes the display name and comments in the language of the connected user while preserving the language-independent technical attributes of each template. This makes it the canonical read interface for reports, concurrent programs, and integrations that must present attribute template metadata in a user's preferred language rather than the base or translation table's raw content.

Underlying Base Objects

The view is defined over two documented base objects: PO_UDA_AG_TEMPLATES (referenced as a synonym) and PO_UDA_AG_TEMPLATES_TL (also referenced as a synonym). PO_UDA_AG_TEMPLATES holds the language-independent definition of each attribute grouping template, including its template identifier, entity code, functional area, document-level and document-type classification, document style, revision, effective dating, the database view name used to materialize the attributes, source template reference, and the compiled flag. PO_UDA_AG_TEMPLATES_TL is the translation table that stores the translatable display name and comments keyed by template identifier and language. The view joins the two on TEMPLATE_ID and restricts the translation side to the current session language through T.LANGUAGE = USERENV('LANG'), so each template row returned reflects the user's language context. All columns are drawn from these two synonyms; no additional base tables are referenced in the documented view text.

Key Columns

• TEMPLATE_ID — Primary identifier of the attribute grouping template; the join key between the definition and translation tables.
• ENTITY_CODE — The entity the template applies to, identifying the owning business object within the UDA framework.
• FUNCTIONAL_AREA — The functional area grouping to which the template belongs.
• DOCUMENT_LEVEL / DOCUMENT_TYPE / DOCUMENT_STYLE_ID — Classify the purchasing document level, type, and style the template governs, controlling where the attribute group is applied.
• REVISION — Revision identifier of the template definition.
• EFFECTIVE_FROM / EFFECTIVE_TO — Effective dating range that determines the template's validity window.
• DATABASE_VIEW_NAME — The generated database view that exposes the attributes defined by this template.
• SRC_TEMPLATE_ID — Reference to a source template from which this one was derived or copied.
• COMPILED_FLAG — Indicates whether the template has been compiled, i.e., whether its underlying database view has been generated and is available for use. This column is directly relevant to the user's search and is central to diagnosing template readiness.
• DISPLAY_NAME / COMMENTS — Translatable text from the TL table, presented in the session language.
• Standard WHO columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, and CREATED_BY provide audit and concurrency information.

Common Use Cases and Queries

Typical uses include validating whether attribute templates are compiled before relying on their generated views, listing active templates within an effective date range, and joining to translations for language-specific reporting. A representative query to identify uncompiled templates is:

SELECT template_id, display_name, entity_code, functional_area, compiled_flag
FROM po_uda_ag_templates_vl
WHERE compiled_flag = 'N'
ORDER BY template_id;

To review currently effective templates by functional area:

SELECT template_id, display_name, functional_area, database_view_name, effective_from, effective_to
FROM po_uda_ag_templates_vl
WHERE TRUNC(SYSDATE) BETWEEN effective_from AND NVL(effective_to, TRUNC(SYSDATE))
ORDER BY functional_area, display_name;

Because the view filters on USERENV('LANG'), results are returned in the session language, making it suitable for localized concurrent reports and integration extracts that must respect the user's language preference while still exposing the compiled flag and other technical attributes needed for administration and troubleshooting.