Results for “applicable_type_code”

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

Overview

IBY_APPLICABLE_PMT_PROFS is a Payments (IBY) module table in Oracle E-Business Suite 12.1.1 and 12.2.2. It functions as a mapping table that links payment methods to payment process profiles. Because administrators may independently define both payment methods and payment process profiles, this table captures the administrative decisions about which payment process profiles are applicable to each payment method, and under which conditions those associations take effect.

From a Data Vault modeling perspective, the ETRM heuristic classification of this table is satellite-leaning. It sits beneath a higher-level entity and records the qualifying attributes that describe applicability rules rather than acting as an independent hub of business keys. The table carries 13 documented columns in the 12.2.2 physical schema and is owned by the IBY schema.

Key Information Stored

The following columns carry the substantive business meaning of the table:

• APPLICABLE_PMT_PROF_ID — the surrogate primary key, defined by the IBY_APPLICABLE_PMT_PROFS_PK constraint. It distinguishes each applicability rule row.
• SYSTEM_PROFILE_CODE — identifies the payment process profile. This is the foreign key column referencing IBY_SYS_PMT_PROFILES_B.
• APPLICABLE_TYPE_CODE — classifies the type of applicability relationship, controlling how the method-to-profile mapping is interpreted.
• APPLICABLE_VALUE_FROM and APPLICABLE_VALUE_TO — define the lower and upper bounds of the applicability range, allowing a single profile to apply across a value band (for example, a payment amount range).
• SEEDED_FLAG — indicates whether the row was delivered as seeded Oracle data or added by an administrator.
• OBJECT_VERSION_NUMBER — supports optimistic locking on concurrent updates.
• ZD_EDITION_NAME — the editioning column used by EBS online patching in 12.2.x.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN capture the standard WHO audit trail.

The unique index IBY_APPLICABLE_PMT_PROFS_U1 spans (APPLICABLE_PMT_PROF_ID, ZD_EDITION_NAME). This composite serves as the edition-aware business-key candidate, while APPLICABLE_PMT_PROF_ID alone is the operational surrogate key.

Common Use Cases and Queries

Typical queries retrieve the set of process profiles available for a given payment method, or validate that a chosen profile is permitted for a method. A representative pattern joins the mapping to the profile definition:

• SELECT a.APPLICABLE_PMT_PROF_ID, a.SYSTEM_PROFILE_CODE, a.APPLICABLE_TYPE_CODE FROM IBY_APPLICABLE_PMT_PROFS a WHERE a.SYSTEM_PROFILE_CODE = :profile_code;
• Reporting on applicability ranges using APPLICABLE_VALUE_FROM and APPLICABLE_VALUE_TO to audit amount-band rules.
• Filtering by SEEDED_FLAG to separate delivered mappings from custom administrative configuration during upgrade or troubleshooting.

These queries support payment configuration diagnostics, profile setup validation, and reporting on how payment methods are governed across the enterprise.

Related Objects

The most significant related object is the profile master table referenced by the documented foreign key:

• IBY_SYS_PMT_PROFILES_B — joined on IBY_APPLICABLE_PMT_PROFS.SYSTEM_PROFILE_CODE = IBY_SYS_PMT_PROFILES_B.SYSTEM_PROFILE_CODE. It supplies the profile header and its translated name.
• IBY_PAYMENT_METHODS_B — the payment method definitions that applicability rules qualify.
• IBY_PMT_INSTR_USES_ALL and related instrument tables — consume the resulting method/profile decisions at transaction time.
• IBY_FD_PAYMENT_PROFILES and Payments setup views — present the combined method/profile configuration to administrators.

Because the mapping constrains which profiles can be used with which methods, it participates directly in the Payments configuration and payment processing chain.