Results for “iby_val_assignments”

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

Overview

IBY_VAL_ASSIGNMENTS is a Payments (IBY) module table within the Oracle E-Business Suite 12.1.1 and 12.2.2 data model. It records the assignment of validation rules and validation sets to specific entities, entity types, territories, and payment methods used during payment processing. In effect, it is the configuration table that binds a given validation regime to the operational context in which payments are created, formatted, or transmitted. Each row identifies which validation set applies to a particular entity (such as a payment system, payment format, or internal party) so that the payments engine can apply the correct edit checks and rule evaluations at runtime.

The heuristic Data Vault classification mined from the foreign-key structure is satellite-leaning. This suggests that IBY_VAL_ASSIGNMENTS is best modeled as a satellite attached to a hub or link representing the underlying validation set, with the assignment rows carrying the descriptive and effective-dating attributes. The table is registered as VALID in the ETRM repository under the IBY schema.

Key Information Stored

The table contains fourteen documented columns. The most significant include the following.

• VALIDATION_ASSIGNMENT_ID — the surrogate primary key, enforced by the IBY_VAL_ASSIGNMENTS_PK constraint. This column uniquely identifies each assignment record.
• VALIDATION_SET_CODE — the code of the validation set being applied. This is the principal foreign key, referencing the parent validation-set definition table. Together with the entity context, it determines the rule set that governs payment validation.
• VAL_ASSIGNMENT_ENTITY_TYPE — the type of entity to which the validation set is assigned. This discriminates how ASSIGNMENT_ENTITY_ID should be interpreted.
• ASSIGNMENT_ENTITY_ID — the identifier of the specific entity receiving the assignment, keyed to the value of VAL_ASSIGNMENT_ENTITY_TYPE.
• TERRITORY_CODE and PAYMENT_METHOD_CODE — optional qualifiers that narrow the applicability of the validation set to a specific territory and payment method, enabling geography- and instrument-specific rules.
• INACTIVE_DATE — the date on which the assignment ceases to be effective, supporting temporal control of validation behavior without deleting historical rows.
• OBJECT_VERSION_NUMBER — the optimistic locking column used by the Oracle Applications Framework for concurrency control.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard audit columns present on whom columns.
• ZD_EDITION_NAME — the editioning column introduced in 12.2 for online patching support, also part of the unique business-key index IBY_VAL_ASSIGNMENTS_VAID_U1 (VALIDATION_ASSIGNMENT_ID, ZD_EDITION_NAME).

The unique index on (VALIDATION_ASSIGNMENT_ID, ZD_EDITION_NAME) is the documented business-key candidate; the primary key remains the single-column surrogate VALIDATION_ASSIGNMENT_ID.

Common Use Cases and Queries

Typical uses include diagnosing why a payment was rejected by a particular validation rule, auditing which validation sets are active for a given payment method, and reporting on the effective configuration of the payments engine. A common query pattern joins the assignment to its validation set and filters on active rows:

• SELECT a.VALIDATION_ASSIGNMENT_ID, a.VALIDATION_SET_CODE, a.VAL_ASSIGNMENT_ENTITY_TYPE, a.ASSIGNMENT_ENTITY_ID, a.PAYMENT_METHOD_CODE, a.TERRITORY_CODE FROM IBY.IBY_VAL_ASSIGNMENTS a WHERE a.INACTIVE_DATE IS NULL OR a.INACTIVE_DATE > SYSDATE;
• Join to the validation-set table on VALIDATION_SET_CODE to resolve rule definitions for a given payment method and territory.
• Group by PAYMENT_METHOD_CODE and TERRITORY_CODE to inventory coverage and detect assignments lacking qualifiers.
• Historical analysis using INACTIVE_DATE to reconstruct the validation regime in force at a past payment date.

Related Objects

The assignment links configuration data across the Payments module and other reference tables. Significant related objects include:

• The validation-set parent table referenced by IBY_VAL_ASSIGNMENTS.VALIDATION_SET_CODE (the foreign-key target), holding the set header definition.
• IBY_VALIDATION_SETS-family rule and rule-detail tables that expand each set into individual validations evaluated at runtime.
• IBY_PAY_SYSTEMS and payment format tables, which supply ASSIGNMENT_ENTITY_ID values when VAL_ASSIGNMENT_ENTITY_TYPE identifies a payment system or format.
• IBY_PAYMENT_METHODS, providing the values behind PAYMENT_METHOD_CODE.
• FND_TERRITORIES, the reference for TERRITORY_CODE.
• Payments engine and public APIs that read these assignments to determine applicable validation logic during payment creation and formatting.

Because the table is satellite-leaning, reporting solutions frequently model it alongside its parent validation set and the entity it qualifies, preserving effective-dating through INACTIVE_DATE and audit columns for full temporal traceability.