Results for “validation_level_code”

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

Overview

IBY_VALIDATION_SETS_VL is a translatable (VL) view owned by the APPS schema within the Oracle Payments (IBY) product module. It presents validation set definitions used by the Payments engine to determine how payment data is validated before processing. A validation set groups one or more validation rules — implemented as PL/SQL package entry points — and associates them with a validation level that governs the scope at which validation is applied (for example, instruction, payment, or document level). The "_VL" suffix indicates that the view joins a language-independent base table with its translation table and filters rows to the session's language via USERENV('LANG'), returning the display name appropriate for the logged-in user. The view is marked VALID in ETRM 12.2.2 and is also present in 12.1.1. Because it is the language-resolved, user-facing representation of validation set metadata, it is the preferred access point for reports, extracts, and integrations that need to display or reference validation sets by their meaningful display name rather than by internal code alone.

Underlying Base Objects

The view text defines a two-table join over the following documented base objects, both referenced in the metadata as synonyms in the APPS schema:

• IBY_VALIDATION_SETS_B — the language-independent base table holding the core validation set attributes, including VALIDATION_SET_CODE, VALIDATION_LEVEL_CODE, the PL/SQL package and entry point used to execute the validation logic, audit columns, and OBJECT_VERSION_NUMBER.
• IBY_VALIDATION_SETS_TL — the translation table holding language-specific display names (VALIDATION_SET_DISPLAY_NAME).

The join is performed on VALIDATION_SET_CODE (B.VALIDATION_SET_CODE = T.VALIDATION_SET_CODE), and the translation side is restricted with the predicate T.LANGUAGE = USERENV('LANG'), so exactly one translated name row is returned per validation set for the current session language. The "_B" and "_TL" naming convention is standard for Oracle EBS translatable entities, and the "_VL" view is the canonical joined, language-filtered projection of that pair. The view also exposes B.ROWID as ROW_ID for row identification.

Key Columns

• VALIDATION_SET_CODE — the unique, language-independent identifier of the validation set; the primary join key between the base and translation tables.
• VALIDATION_LEVEL_CODE — the level at which the validation set is applied; this determines the scope of the validation rules within the Payments flow.
• VALIDATION_CODE_PACKAGE — the PL/SQL package that contains the validation logic invoked for this set.
• VALIDATION_CODE_ENTRY_POINT — the specific procedure or function within the package that the Payments engine calls to perform validation.
• VALIDATION_CODE_LANGUAGE — the programming language designation for the validation code (for example, PL/SQL).
• VALIDATION_SET_DISPLAY_NAME — the translated, user-facing name of the validation set, sourced from IBY_VALIDATION_SETS_TL for the session language.
• ROW_ID — the ROWID of the underlying base-table row, useful for row-level identification.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.
• OBJECT_VERSION_NUMBER — the optimistic locking version number carried from the base table.

Common Use Cases and Queries

Typical uses include documenting which validation rules are active for a given level, troubleshooting why a payment failed validation by tracing the code package and entry point, and building extracts that map validation sets to their executable logic. A basic listing of validation sets with their display names is shown below.

• List all validation sets with translated names: SELECT validation_set_code, validation_set_display_name, validation_level_code FROM iby_validation_sets_vl ORDER BY validation_set_display_name;
• Inspect validation logic for a given level: SELECT validation_set_code, validation_code_package, validation_code_entry_point FROM iby_validation_sets_vl WHERE validation_level_code = :level;
• Join to related Payments tables (for example, validation assignments or payment formats) using VALIDATION_SET_CODE to trace rule configuration end to end.

Because the view resolves display names for the session language, reports built on it automatically present the correct translated name without additional language handling in the query.