Results for “iby_fndcpt_sys_cc_pf_vl”

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

Overview

The view APPS.IBY_FNDCPT_SYS_CC_PF_VL is a seeded, VALID database object within the Oracle Payments (IBY) module of Oracle E-Business Suite, available in releases 12.1.1 and 12.2.2. It presents system-level credit card processing profile configuration, joining the base profile table with its translation table to deliver language-specific profile names and descriptions. The "_VL" suffix denotes a "view with translation" pattern common to EBS, where the view automatically restricts rows to the session's language through the USERENV('LANG') predicate. This makes the view the preferred access point for both reporting and integration logic, since it returns only one row per profile with the description text appropriate to the current language setting. The view is central to payment processing setup, exposing the format codes and protocol codes that govern how credit card authorizations, settlements, and queries are formatted and transmitted to payment processors.

Underlying Base Objects

The view is defined over two documented base objects, both referenced through APPS synonyms: IBY_FNDCPT_SYS_CC_PF_B, the base (non-translated) table holding the operating configuration, and IBY_FNDCPT_SYS_CC_PF_TL, the translation table holding SYS_CC_PROFILE_NAME and DESCRIPTION in each installed language. The join condition is B.SYS_CC_PROFILE_CODE = T.SYS_CC_PROFILE_CODE, combined with T.LANGUAGE = USERENV('LANG'). The view also exposes B.ROWID as ROW_ID and carries the standard WHO audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) plus OBJECT_VERSION_NUMBER for optimistic locking.

Key Columns

• SYS_CC_PROFILE_CODE — primary business key identifying the system credit card profile.
• ONLINE_AUTH_FORMAT_CODE — the format code defining the file/message layout used when transmitting an online authorization request; this is the column most directly relevant to the search term that surfaced this object.
• ONLINE_AUTH_TRANS_PRTCL_CODE and ONLINE_AUTH_ACK_RDR_CODE — the transmission protocol and acknowledgement reader used for authorization messages.
• SETTLEMENT_FORMAT_CODE, SETTLEMENT_TRANS_PRTCL_CODE, SETTLEMENT_ACK_RDR_CODE, and SETTLEMENT_COMPLETE_POINT — parallel configuration for the settlement phase.
• QUERY_FORMAT_CODE, QUERY_TRANS_PRTCL_CODE, QUERY_ACK_RDR_CODE — configuration for inquiry/status messages.
• PAYMENT_SYSTEM_ID — links the profile to the payment system definition.
• Grouping/limiting controls such as GROUP_BY_ORG, GROUP_BY_LEGAL_ENTITY, GROUP_BY_INT_BANK_ACCOUNT, GROUP_BY_SETTLEMENT_CURR, GROUP_BY_SETTLEMENT_DATE, LIMIT_BY_AMT_CURR, LIMIT_BY_EXCH_RATE_TYPE, LIMIT_BY_TOTAL_AMT, and LIMIT_BY_SETTLEMENT_NUM — govern how settlement batches are built and bounded.
• AUTOMATIC_PN_SUBMIT_FLAG, OVERRIDE_PAYER_DELIVERY_FLAG, PAYER_NOTIFICATION_FORMAT, PAYER_NOTIFICATION_DEL_METHOD — payer notification behavior.
• SYS_CC_PROFILE_NAME and DESCRIPTION — translated descriptive text.

Common Use Cases and Queries

Typical uses include configuration auditing, troubleshooting processor communication failures, and building extraction feeds for integration. The following query lists active profiles and their authorization and settlement formats:

SELECT sys_cc_profile_code,
       sys_cc_profile_name,
       online_auth_format_code,
       online_auth_trans_prtcl_code,
       settlement_format_code,
       settlement_complete_point
FROM   apps.iby_fndcpt_sys_cc_pf_vl
WHERE  inactive_date IS NULL;

To locate the profile associated with a specific payment system:

SELECT sys_cc_profile_code, sys_cc_profile_name
FROM   apps.iby_fndcpt_sys_cc_pf_vl
WHERE  payment_system_id = :p_payment_system_id;

Because the view already applies the language predicate, no additional language filtering is required in ad-hoc reporting, though customers with custom descriptive flexfield data may additionally select the ATTRIBUTE1..15 columns exposed by the view.