Results for “validation_param_display_order”

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

Overview

The IBY_VALIDATION_PARAMS_VL view is a multilingual (ML) validation view owned by the APPS schema in Oracle E-Business Suite. It belongs to the IBY — Payments product family and is delivered with a status of VALID in both EBS 12.1.1 and 12.2.2. The view exposes the parameter definitions that govern payment validation sets used by Oracle Payments. Each validation set groups one or more parameters that determine how payment instructions, payment formats, and related records are validated before they are processed.

Functionally, IBY_VALIDATION_PARAMS_VL is the translated, user-facing representation of the underlying base and translation tables. It presents the validation set code, parameter code, parameter data type, display ordering, and the language-specific display name in a single row. This makes it the appropriate source for reports, LOVs, concurrent program lookups, and integration interfaces that require human-readable validation parameter descriptions rather than raw internal codes.

Underlying Base Objects

The view is defined over two documented base objects, both exposed through APPS synonyms:

• IBY_VALIDATION_PARAMS_B — the base table holding language-independent attributes such as the validation set code, parameter code, parameter type, display order, audit columns, and object version number.
• IBY_VALIDATION_PARAMS_TL — the translation table holding the language-specific display name (VALIDATION_PARAM_DISPLAY_NAME), keyed by language.

The view joins these two tables on the pair (VALIDATION_PARAMETER_CODE, VALIDATION_SET_CODE) and filters rows with the condition T.LANGUAGE = USERENV('LANG'). This restricts output to the session language of the querying user, which is the defining characteristic of an Oracle "_VL" view. The ROWID of the base table row is exposed as the ROW_ID column.

Key Columns

• ROW_ID — the ROWID of the base table record, used for direct row addressing.
• VALIDATION_SET_CODE — identifies the parent validation set to which the parameter belongs.
• VALIDATION_PARAMETER_CODE — the internal code for the individual parameter.
• VALIDATION_PARAMETER_TYPE — the data type or category of the parameter, governing how its value is interpreted.
• VALIDATION_PARAM_DISPLAY_ORDER — controls the sequence in which parameters are presented in the UI.
• VALIDATION_PARAM_DISPLAY_NAME — the translated, human-readable name for the parameter in the session language.
• OBJECT_VERSION_NUMBER — supports optimistic locking for concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns recording creation and modification history.

Common Use Cases and Queries

Typical uses include populating value sets for validation parameter selection, generating payment configuration documentation, and driving integration logic that must branch on parameter type or ordering. Because the view already resolves the session language, joins to the translation table are unnecessary.

Retrieve all parameters for a specific validation set:

SELECT validation_parameter_code,
       validation_parameter_type,
       validation_param_display_name,
       validation_param_display_order
FROM   apps.iby_validation_params_vl
WHERE  validation_set_code = :p_set_code
ORDER  BY validation_param_display_order;

List every parameter with its display name for a configuration audit:

SELECT validation_set_code,
       validation_parameter_code,
       validation_param_display_name
FROM   apps.iby_validation_params_vl
ORDER  BY validation_set_code, validation_param_display_order;

In 12.1.1 the structure and columns are consistent with the 12.2.2 documented metadata, so reports and integrations written against this view remain portable across both releases.