Results for “hz_trans_functions_vl”

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

Overview

HZ_TRANS_FUNCTIONS_VL is a multilingual (VL) view owned by the APPS schema in Oracle E-Business Suite, registered under the Receivables (AR) product family. It exposes the transformation functions used by Oracle Trading Community Architecture (TCA) and related customer/party data-processing logic, including transformation procedures, their associated attribute bindings, and staging configuration metadata. The view presents a language-resolved, human-readable form of the underlying transformation function definitions by joining the base table to its translation table using the session language.

In reporting and integration terms, the view provides a read-only, denormalized projection suitable for queries, concurrent programs, and interfaces that need to enumerate available transformation functions and determine whether each is active, primary, or tied to staged attribute processing. Because it resolves the TRANSFORMATION_NAME and DESCRIPTION columns against USERENV('LANG'), it returns text in the runtime language of the querying session.

The reference to STAGED_FLAG in the view text corresponds directly to the user's search term: this column indicates whether the transformation function participates in the staged attribute mechanism used during bulk transformation and data-quality processing.

Underlying Base Objects

Per the documented view definition, HZ_TRANS_FUNCTIONS_VL is defined over two base objects, both exposed to APPS as synonyms:

• HZ_TRANS_FUNCTIONS_B — the base (non-translated) table holding the functional and technical attributes of each transformation function, aliased as B.
• HZ_TRANS_FUNCTIONS_TL — the translation table holding language-specific TRANSFORMATION_NAME and DESCRIPTION values, aliased as T.

The join is performed on T.FUNCTION_ID = B.FUNCTION_ID with the additional predicate T.LANGUAGE = USERENV('LANG'), which is characteristic of the _VL view pattern. The select list includes B.ROWID projected as ROW_ID, permitting row-address-based operations against the base record.

Key Columns

• ROW_ID — the ROWID of the underlying HZ_TRANS_FUNCTIONS_B row.
• FUNCTION_ID — primary identifier for the transformation function; the join key across B and TL.
• ATTRIBUTE_ID — identifier of the attribute to which the function applies.
• TRANSFORMATION_NAME — language-resolved name of the transformation.
• PROCEDURE_NAME — the PL/SQL procedure invoked to perform the transformation.
• DESCRIPTION — language-resolved description text.
• ACTIVE_FLAG — indicates whether the function is currently enabled.
• PRIMARY_FLAG — marks the function as the primary transformation for its context.
• STAGED_ATTRIBUTE_TABLE / STAGED_ATTRIBUTE_COLUMN — the staging table and column used when staged processing applies.
• STAGED_FLAG — flags whether the function uses the staged attribute mechanism.
• INDEX_REQUIRED_FLAG — indicates whether an index is required on the staged attribute.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE, LAST_UPDATED_BY, and OBJECT_VERSION_NUMBER support concurrency control and auditing.

Common Use Cases and Queries

Typical scenarios include enumerating active transformation functions, identifying which functions require staging, and auditing function configuration by language. The following query returns functions flagged for staged attribute processing:

SELECT FUNCTION_ID, TRANSFORMATION_NAME, PROCEDURE_NAME, STAGED_ATTRIBUTE_TABLE, STAGED_ATTRIBUTE_COLUMN FROM APPS.HZ_TRANS_FUNCTIONS_VL WHERE STAGED_FLAG = 'Y' AND ACTIVE_FLAG = 'Y';

To list all transformations for a specific attribute with their primary indicator:

SELECT FUNCTION_ID, TRANSFORMATION_NAME, PRIMARY_FLAG, INDEX_REQUIRED_FLAG FROM APPS.HZ_TRANS_FUNCTIONS_VL WHERE ATTRIBUTE_ID = :p_attribute_id ORDER BY PRIMARY_FLAG DESC;

The view is also useful for integration lookups that must resolve a PROCEDURE_NAME at runtime, and for exception reporting on functions lacking staged configuration. All access should be performed with the APPS schema context or via a synonym, and due to the USERENV('LANG') predicate, results are constrained to the session language.