Results for “query_trans_config_id”

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

Overview

IBY_FNDCPT_USER_CC_PF_B is a foundational configuration table within the Oracle Payments (IBY) module. It stores user-defined credit card processing profiles, which govern how credit card transactions are authorized, settled, and queried through payment system transaction configurations and associated BEP (Back-End Payment) account keys. Functionally, the table acts as a registry of named profile definitions that a payee or operating unit can assign to specific business flows so that appropriate transaction processing behavior is applied at runtime.

In the ETRM 12.2.2 physical schema, the table resides in the IBY schema and comprises 13 documented columns. Based on the Data Vault classification derived heuristically from the foreign key structure, this object is best modeled as a link table. This classification reflects its role in connecting multiple reference entities — system credit card profiles, BEP account keys, and three distinct transaction configuration identifiers — within a single associative record.

Key Information Stored

The most important columns in this table are summarized below.

• USER_CC_PROFILE_CODE — Serves as the primary key (IBY_FNDCPT_USER_CC_PF_B_PK) and is also the single documented unique index candidate (IBY_FNDCPT_USER_CC_PF_B_UPC_U1). It represents the business identifier for the user-defined credit card profile.
• SYS_CC_PROFILE_CODE — The system credit card profile to which the user profile is associated, establishing the base processing template.
• BEP_ACCOUNT_ID — Foreign key to IBY_BEPKEYS, linking the profile to the applicable BEP account key configuration.
• ONLINE_AUTH_TRANS_CONFIG_ID — Transaction configuration identifier used during online authorization.
• SETTLEMENT_TRANS_CONFIG_ID — Transaction configuration identifier used during settlement processing.
• QUERY_TRANS_CONFIG_ID — Transaction configuration identifier used when querying payment status.
• INACTIVE_DATE — Effective end date after which the profile is no longer active for use.
• OBJECT_VERSION_NUMBER — Optimistic locking column supporting concurrent updates.
• CREATED_BY / CREATION_DATE — Standard audit columns recording the creating user and timestamp.
• LAST_UPDATED_BY / LAST_UPDATE_DATE / LAST_UPDATE_LOGIN — Audit columns for the most recent modification.

The surrogate primary key is BUSINESS-key oriented here: USER_CC_PROFILE_CODE serves both as the PK and as the unique business identifier, while the remaining ID columns act as foreign references to related configuration tables.

Common Use Cases and Queries

Typical use cases include reporting on active credit card profiles, validating that profiles reference appropriately configured transaction types, and auditing profile changes over time. A common query retrieves all active profiles with their associated system profile and BEP account:

• Listing profiles where INACTIVE_DATE is null, joined to IBY_BEPKEYS on BEP_ACCOUNT_ID, to confirm active processing configurations.
• Joining the three transaction configuration ID columns to their respective transaction configuration tables to validate that online authorization, settlement, and query settings are present.
• Auditing profiles created or modified within a period by filtering on CREATION_DATE or LAST_UPDATE_DATE.
• Reconciling profile usage against payment transaction records to identify which profiles drive the highest transaction volume.
• Verifying data integrity by detecting orphaned foreign key values in BEP_ACCOUNT_ID or the transaction configuration columns.

A representative pattern: SELECT u.USER_CC_PROFILE_CODE, u.SYS_CC_PROFILE_CODE, u.BEP_ACCOUNT_ID FROM IBY_FNDCPT_USER_CC_PF_B u WHERE u.INACTIVE_DATE IS NULL;

Related Objects

• IBY_BEPKEYS — Referenced via BEP_ACCOUNT_ID; supplies the back-end payment key configuration for the profile.
• System credit card profile table (SYS_CC_PROFILE_CODE reference) — Provides the underlying system-level template.
• Online authorization transaction configuration (ONLINE_AUTH_TRANS_CONFIG_ID) — Defines authorization processing behavior.
• Settlement transaction configuration (SETTLEMENT_TRANS_CONFIG_ID) — Defines settlement behavior.
• Query transaction configuration (QUERY_TRANS_CONFIG_ID) — Defines status query behavior.
• IBY_FNDCPT_USER_CC_PF_B_PK / IBY_FNDCPT_USER_CC_PF_B_UPC_U1 — Primary key constraint and unique index enforcing USER_CC_PROFILE_CODE uniqueness.

These relationships confirm the table's role as a central associative link tying user profiles to their transactional and account-level processing definitions within Oracle Payments.