Results for “settle_require_vrfy_flag”

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

Overview

The IBY.IBY_FNDCPT_SYS_EFT_PF_B table is a core configuration object within the Oracle Payments (IBY) module of Oracle E-Business Suite. It stores System Electronic Funds Transfer (EFT) Payment Profiles, which define how a payment system processes EFT instructions for a given payment system, communication method, and formatting arrangement. Each row represents a distinct EFT payment profile identified by SYS_EFT_PROFILE_CODE, and the profile governs the lifecycle of an electronic payment: instruction formatting, transmission protocol selection, verification, acknowledgement handling, follow-up querying, bundling rules, and payer notification behavior.

In Oracle EBS 12.1.1 and 12.2.2, this table is populated and maintained primarily through the Payments Administrator responsibility, where Payment System EFT profiles are configured alongside payment formats and transmission protocols. The _B suffix denotes the base (non-translated) table; translation or descriptive information is held in associated _TL and _VL objects where applicable.

From a Data Vault modeling perspective, the heuristic classification of this table is link, since it is a configuration record with no natural business key of its own and whose primary role is to associate existing reference entities (payment systems, formats, and transmission protocols). This classification should be considered a modeling suggestion rather than a formal Oracle designation.

Key Information Stored

The primary key is a surrogate key defined by the unique index IBY_FNDCPT_SYS_EFT_PF_B_PK on SYS_EFT_PROFILE_CODE. A second unique index, IBY_FNDCPT_SYS_EFT_PF_B_U1, covers (SYS_EFT_PROFILE_CODE, ZD_EDITION_NAME) and serves as the documented business-key candidate. The most significant columns include:

• SYS_EFT_PROFILE_CODE — the surrogate identifier for the EFT profile.
• PAYMENT_SYSTEM_ID — FK to IBY_BEPINFO, the payment system to which this profile is bound.
• VERIFY_FORMAT_CODE, VERIFY_TRANS_PRTCL_CODE, VERIFY_ACK_RDR_CODE — the format, transmission protocol, and acknowledgement reader used for the verification step.
• FUNDS_XFER_FORMAT_CODE, FUNDS_XFER_TRANS_PRTCL_CODE, FUNDS_XFER_ACK_RDR_CODE — the corresponding artifacts for the funds transfer step.
• QUERY_FORMAT_CODE, QUERY_TRANS_PRTCL_CODE, QUERY_ACK_RDR_CODE — the format, protocol, and acknowledgement reader for enquiry/query follow-up.
• SETTLE_REQUIRE_VRFY_FLAG and SETTLEMENT_COMPLETE_POINT — control when a payment is considered settled.
• GROUP_BY_ORG, GROUP_BY_LEGAL_ENTITY, GROUP_BY_INT_BANK_ACCOUNT, GROUP_BY_SETTLEMENT_CURR, GROUP_BY_SETTLEMENT_DATE — bundling rules that determine how individual payments are grouped into EFT instruction batches.
• LIMIT_BY_AMT_CURR, LIMIT_BY_TOTAL_AMT, LIMIT_BY_SETTLEMENT_NUM — threshold rules controlling batch size and value limits.
• PAYER_NOTIFICATION_FORMAT, PAYER_NOTIFICATION_DEL_METHOD, PAYER_NOTIFICATION_CONDITION, AUTOMATIC_PN_SUBMIT_FLAG, PN_COND_NUM_OF_RECEIPTS — payer notification configuration.
• OVERRIDE_PAYER_DELIVERY_FLAG and ACCOMPANY_LETTER_FORMAT — delivery override and accompanying remittance letter format.
• INACTIVE_DATE, OBJECT_VERSION_NUMBER, plus the standard audit columns CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical reporting and administration scenarios involve identifying active EFT profiles for a given payment system, tracing which format and transmission protocol combination is used for each processing step, and auditing profile-level grouping or notification rules.

To list active profiles for a payment system:

• SELECT SYS_EFT_PROFILE_CODE, PAYMENT_SYSTEM_ID, FUNDS_XFER_FORMAT_CODE, FUNDS_XFER_TRANS_PRTCL_CODE FROM IBY.IBY_FNDCPT_SYS_EFT_PF_B WHERE PAYMENT_SYSTEM_ID = :payment_system_id AND (INACTIVE_DATE IS NULL OR INACTIVE_DATE > SYSDATE);

To resolve format descriptions for a profile, join to IBY_FORMATS_B on each format column. To determine the transmission protocol in use for the funds transfer step, join IBY_TRANSMIT_PROTOCOLS_B on FUNDS_XFER_TRANS_PRTCL_CODE. This table is also useful for reporting the batch grouping strategy (the GROUP_BY_*) and limits (LIMIT_BY_*) applied per payment system, which directly affect settlement timing and instruction volume.

Related Objects

The table is heavily reference-oriented, with foreign keys into several core IBY configuration tables. The most significant related objects are:

• IBY_BEPINFO — joined on PAYMENT_SYSTEM_ID; identifies the payment system.
• IBY_FORMATS_B — referenced by PAYER_NOTIFICATION_FORMAT, ACCOMPANY_LETTER_FORMAT, VERIFY_FORMAT_CODE, FUNDS_XFER_FORMAT_CODE, and QUERY_FORMAT_CODE.
• IBY_TRANSMIT_PROTOCOLS_B — referenced by VERIFY_TRANS_PRTCL_CODE, FUNDS_XFER_TRANS_PRTCL_CODE, and QUERY_TRANS_PRTCL_CODE.
• Acknowledgement reader objects referenced by VERIFY_ACK_RDR_CODE, FUNDS_XFER_ACK_RDR_CODE, and QUERY_ACK_RDR_CODE (the metadata shows these resolved to a pattern match, indicating a reader configuration entity).

Downstream, the EFT profile identifier is used by the Payment Process Request (PPR) and instruction formatting/transmission logic to drive the actual creation and delivery of EFT payment files, making this table a prerequisite for any configured electronic payment system.