Results for “iby_fndcpt_sys_eft_pf_vl”

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

Overview

IBY_FNDCPT_SYS_EFT_PF_VL is a seeded, VALID view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the IBY — Payments product family and exposes the definition of System Electronic Funds Transfer (EFT) profiles used by Oracle Payments. A system EFT profile controls how a payment system transmits, verifies, and settles electronic funds transfers, including the transaction protocols, file formats, acknowledgement readers, and grouping and limit attributes applied during payment instruction creation and settlement.

The suffix "_VL" denotes a "view with translation, language-sensitive" construct. The view joins the base table to its translation table and filters the translated rows by the session language, so consumers see descriptive text in the runtime language. It is the primary supported read interface for system EFT profile configuration and is consumed by payment processing logic, setup validation, and reporting. Users searching on funds_xfer_trans_prtcl_code typically reach this view because it is the profile-level attribute that identifies the transaction protocol used to transmit the funds transfer request to the payment system.

Underlying Base Objects

The view is defined over two documented base objects, both referenced through APPS synonyms:

• IBY_FNDCPT_SYS_EFT_PF_B — the base (non-translated) table holding all functional attributes of the system EFT profile, aliased as B in the view text.
• IBY_FNDCPT_SYS_EFT_PF_TL — the translation table holding language-specific descriptive columns such as SYS_EFT_PROFILE_NAME and DESCRIPTION, aliased as T.

The join is performed on SYS_EFT_PROFILE_CODE, and the translation row is restricted by T.LANGUAGE = USERENV('LANG'). Because the view merges translated and non-translated data, it provides a single, language-aware row per profile without requiring callers to join the tables themselves.

Key Columns

The projection includes the ROWID (as ROW_ID), WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN), OBJECT_VERSION_NUMBER for optimistic locking, and the descriptive columns SYS_EFT_PROFILE_NAME and DESCRIPTION sourced from the translation table.

Functional attributes include:

• FUNDS_XFER_TRANS_PRTCL_CODE — the transaction protocol used for the funds transfer transmission step, the column most commonly searched.
• FUNDS_XFER_FORMAT_CODE and FUNDS_XFER_ACK_RDR_CODE — the transmission file format and acknowledgement reader.
• QUERY_TRANS_PRTCL_CODE, QUERY_FORMAT_CODE, QUERY_ACK_RDR_CODE — attributes for the query (status inquiry) step.
• VERIFY_TRANS_PRTCL_CODE, VERIFY_FORMAT_CODE, VERIFY_ACK_RDR_CODE — attributes for the verification step.
• SYS_EFT_PROFILE_CODE and PAYMENT_SYSTEM_ID — the profile identifier and its associated payment system.
• GROUP_BY_* flags — GROUP_BY_ORG, GROUP_BY_LEGAL_ENTITY, GROUP_BY_INT_BANK_ACCOUNT, GROUP_BY_SETTLEMENT_CURR, GROUP_BY_SETTLEMENT_DATE — controlling how payment instructions are aggregated into transmissions.
• LIMIT_BY_* attributes — LIMIT_BY_AMT_CURR, LIMIT_BY_EXCH_RATE_TYPE, LIMIT_BY_TOTAL_AMT, LIMIT_BY_SETTLEMENT_NUM.
• SETTLE_REQUIRE_VRFY_FLAG, AUTOMATIC_PN_SUBMIT_FLAG, OVERRIDE_PAYER_DELIVERY_FLAG, PAYER_NOTIFICATION_FORMAT, PAYER_NOTIFICATION_DEL_METHOD, SETTLEMENT_COMPLETE_POINT, ACCOMPANY_LETTER_FORMAT — settlement and payer notification controls.
• Fifteen ATTRIBUTE columns plus ATTRIBUTE_CATEGORY for extensibility, and INACTIVE_DATE for end-dating a profile.

Common Use Cases and Queries

Typical uses include auditing which transaction protocol a profile employs, reconciling format and acknowledgement reader setup, and driving custom reporting on payment transmission configuration. All queries should filter on the profile code or payment system and exclude retired rows via INACTIVE_DATE.

SELECT sys_eft_profile_code,
       sys_eft_profile_name,
       payment_system_id,
       funds_xfer_trans_prtcl_code,
       funds_xfer_format_code,
       funds_xfer_ack_rdr_code,
       settle_require_vrfy_flag
FROM   apps.iby_fndcpt_sys_eft_pf_vl
WHERE  inactive_date IS NULL
ORDER  BY sys_eft_profile_code;

To locate the protocol assignment for a specific profile:

SELECT sys_eft_profile_name,
       funds_xfer_trans_prtcl_code,
       query_trans_prtcl_code,
       verify_trans_prtcl_code
FROM   apps.iby_fndcpt_sys_eft_pf_vl
WHERE  sys_eft_profile_code = :p_profile_code;

Grouping and limit configuration can be reviewed in the same pass:

SELECT sys_eft_profile_code,
       group_by_org,
       group_by_legal_entity,
       group_by_int_bank_account,
       limit_by_total_amt,
       automatic_pn_submit_flag
FROM   apps.iby_fndcpt_sys_eft_pf_vl
WHERE  payment_system_id = :p_payment_system_id;

Because the view already resolves the session-language translation, no additional join is required for descriptive output in custom reports.