Results for “sys_eft_profile_code”

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

Overview

The table IBY.IBY_FNDCPT_USER_EFT_PF_B is a foundational configuration object within the Oracle Payments (IBY) module of Oracle E-Business Suite, documented as VALID in both release 12.1.1 and 12.2.2. It stores user-defined Electronic Funds Transfer (EFT) payment format profiles. In Oracle Payments, a payment format is the template that determines how an outbound payment instruction file is constructed and transmitted to a bank or payment system. This table holds the customer- or implementation-specific EFT profile definitions that extend, override, or refine the seeded system EFT profiles delivered by Oracle.

Each row represents a single user EFT profile, keyed by USER_EFT_PROFILE_CODE. The profile references a seeded system profile via SYS_EFT_PROFILE_CODE, a bank account via BEP_ACCOUNT_ID, and three transaction configuration identifiers that govern verification, funds transfer, and query behavior. The table is maintained by the Payments Administrator and is critical to the Payment Process Request (PPR) pipeline: when a payment instruction is formatted, the application resolves the applicable user EFT profile to determine formatting rules, transmission settings, and associated bank account behavior.

From a dimensional modeling perspective, the metadata's heuristic Data Vault classification of this object is a link. This suggests modeling it as a relationship table that associates independent business entities — specifically the user EFT profile, the system EFT profile, the BEP account, and the transaction configuration records — rather than as a standalone hub or a descriptive satellite.

Key Information Stored

The documented physical schema exposes 13 columns. The most significant are:

• USER_EFT_PROFILE_CODE — The primary key of the table (via constraint IBY_FNDCPT_USER_EFT_PF_B_PK) and simultaneously the business-key candidate confirmed by the unique index IBY_FNDCPT_USER_EFT_PF_B_U1. It uniquely identifies each user-defined EFT profile.
• SYS_EFT_PROFILE_CODE — Foreign key linking the user profile to its underlying seeded system EFT profile. This establishes the inheritance chain from delivered Oracle definitions to customer customizations.
• BEP_ACCOUNT_ID — Foreign key to IBY_BEPKEYS, identifying the bank exchange profile account associated with the EFT arrangement.
• VERIFY_TRANS_CONFIG_ID — Transaction configuration reference controlling verification processing for the profile.
• FUNDS_XFER_TRANS_CONFIG_ID — Transaction configuration reference governing the funds transfer step.
• QUERY_TRANS_CONFIG_ID — Transaction configuration reference for query or status-check operations.
• INACTIVE_DATE — Effective end date used to retire a profile without deleting it.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the Oracle Application Framework to detect concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns recording the user, timestamp, and login session responsible for each insert or update.

The surrogate primary key is the single-column key on USER_EFT_PROFILE_CODE; no separate numeric surrogate identifier is documented, so the business code itself serves as the key. The four foreign-key columns (SYS_EFT_PROFILE_CODE, BEP_ACCOUNT_ID, and the three transaction configuration identifiers) define the link relationships.

Common Use Cases and Queries

Typical uses center on payment format administration and payment instruction diagnostics:

• Listing active user EFT profiles for configuration review: select profiles where INACTIVE_DATE IS NULL or is in the future.
• Profile-to-system inheritance mapping: join user profiles to their system profile definitions to identify customization coverage.
• Bank account association reporting: join to IBY_BEPKEYS on BEP_ACCOUNT_ID to confirm which bank accounts each EFT profile targets.
• Audit and change tracking: query LAST_UPDATED_BY and LAST_UPDATE_DATE to review who modified profiles and when.
• Transaction configuration verification: confirm that VERIFY_TRANS_CONFIG_ID, FUNDS_XFER_TRANS_CONFIG_ID, and QUERY_TRANS_CONFIG_ID are populated consistently across profiles.

A representative query pattern is:

• SELECT p.USER_EFT_PROFILE_CODE, p.SYS_EFT_PROFILE_CODE, p.BEP_ACCOUNT_ID FROM IBY_FNDCPT_USER_EFT_PF_B p WHERE p.INACTIVE_DATE IS NULL;
• SELECT p.USER_EFT_PROFILE_CODE, b.* FROM IBY_FNDCPT_USER_EFT_PF_B p JOIN IBY_BEPKEYS b ON p.BEP_ACCOUNT_ID = b.BEP_ACCOUNT_ID;

Related Objects

The FK metadata identifies the following significant relationships and dependencies:

• IBY_BEPKEYS — joined via IBY_FNDCPT_USER_EFT_PF_B.BEP_ACCOUNT_ID = IBY_BEPKEYS.BEP_ACCOUNT_ID; the bank exchange profile account master.
• System EFT profile definition — referenced via SYS_EFT_PROFILE_CODE, providing the seeded profile that the user profile derives from.
• Verify transaction configuration — referenced via VERIFY_TRANS_CONFIG_ID.
• Funds transfer transaction configuration — referenced via FUNDS_XFER_TRANS_CONFIG_ID.
• Query transaction configuration — referenced via QUERY_TRANS_CONFIG_ID.

Together these objects form the configuration backbone that the Oracle Payments payment formatting and transmission engine consults when processing EFT payment instructions.