Results for “iby_validation_sets_b”

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

Overview

The IBY_VALIDATION_SETS_B table is a core configuration object within the Oracle Payments (IBY) module of Oracle E-Business Suite, available in releases 12.1.1 and 12.2.2. It stores the definition of validation sets — logical groupings that associate a payment flow and validation level with the PL/SQL validation logic executed against payment instructions, payment formats, or related payment entities. Validation sets act as the registration point that tells the Payments engine which validation package and entry point to invoke during processing, thereby enabling extensible, rule-based validation of payment data before funds disbursement.

The table resides in the IBY schema and is documented with thirteen physical columns in the ETRM 12.2.2 reference. Its primary key is defined by the constraint IBY_VALIDATION_SETS_B_PK, keyed on the VALIDATION_SET_CODE column. Based on the heuristic Data Vault classification provided in the metadata, this object is modeled as a standalone structure. In Data Vault terms it most closely resembles a hub-like or reference-satellite pattern, since no foreign key relationships to other tables were mined; however, this classification should be treated only as a modeling suggestion rather than a definitive architectural statement.

Key Information Stored

The most significant columns in IBY_VALIDATION_SETS_B are:

• VALIDATION_SET_CODE — the primary key and the business identifier of the validation set; it uniquely identifies each configured set and is the column referenced by dependent objects.
• PAYMENT_FLOW — indicates the payment flow (for example, disbursement, funds capture, or clearing) to which the validation set applies.
• VALIDATION_LEVEL_CODE — defines the level at which validation is performed, such as payment or document level.
• VALIDATION_CODE_PACKAGE — the name of the PL/SQL package containing the custom or seeded validation logic.
• VALIDATION_CODE_ENTRY_POINT — the specific procedure or function within that package that is invoked.
• VALIDATION_CODE_LANGUAGE — the language context under which the validation code executes.
• ZD_EDITION_NAME — the editioning column used by the EBS Online Patching (adop) architecture in 12.2.x, enabling edition-based redefinition.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns that track record provenance and change history.
• OBJECT_VERSION_NUMBER — supports optimistic locking during concurrent updates.

The surrogate primary key is VALIDATION_SET_CODE via IBY_VALIDATION_SETS_B_PK. The unique index IBY_VALIDATION_SETS_B_VSCID_U1 spans (VALIDATION_SET_CODE, ZD_EDITION_NAME), which is an editioning-aware business-key candidate unique to the 12.2.x data model.

Common Use Cases and Queries

Typical scenarios include auditing which validation packages are registered for a given payment flow, troubleshooting validation failures during payment processing, and documenting custom validation extensions. A representative query follows:

• SELECT validation_set_code, payment_flow, validation_level_code, validation_code_package, validation_code_entry_point FROM iby.iby_validation_sets_b WHERE payment_flow = :flow;
• Joining to validation set assignments to identify which payment formats or instruction configurations use a given validation set.
• Reporting on custom versus seeded validation packages by filtering on the VALIDATION_CODE_PACKAGE column.

Related Objects

The metadata identifies this table as standalone, with no mined foreign key relationships. In practice, the following IBY objects reference or depend on its VALIDATION_SET_CODE:

• IBY_VALIDATION_SETS_TL — the translated (multi-language) companion table sharing VALIDATION_SET_CODE.
• IBY_VALIDATION_ASSIGNMENTS — associates validation sets with payment process profiles or payment formats.
• IBY_PAYMENT_FORMATS_B — payment format definitions that consume validation logic.
• IBY_PAY_PROCESS_PROFILES_B — payment process profiles configured with validation behavior.
• IBY_FD_PAYMENT_INSTRUCTIONS — payment instructions validated at runtime.
• The Payments validation framework PL/SQL API (IBY_VALIDATION_PUB or equivalent) that resolves and executes the configured package and entry point.

Developers and DBAs should confirm exact join columns against the ETRM for their specific patch level, since the documented relationship data here is limited to the standalone classification.