Results for “limit_by_exch_rate_type”

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

Overview

IBY_FNDCPT_SYS_DC_PF_VL is a bilingual (VL, "view language") view owned by the APPS schema in Oracle E-Business Suite Releases 12.1.1 and 12.2.2. It belongs to the IBY (Payments) product and exposes the configuration of system-level debtor and creditor payment profiles — the "system payment profile" definitions that drive how Oracle Payments communicates with a payment system, including the protocols, file formats, acknowledgment readers, and settlement rules used for each processing mode. The view joins the transactional base table to its translation table so that the profile name and description are returned in the session's language (resolved through USERENV('LANG')). Because it is a view rather than a table, it is read-only from the perspective of application code and is intended for reporting, inquiry, and integration lookups. The column settlement_trans_prtcl_code, which prompted the search, carries the transmission protocol used for the settlement phase of the payment process — for example the protocol governing how completed settlement instructions or settlement files are transmitted to and received from the payment system.

Underlying Base Objects

The documented base objects behind the view are two synonyms in the APPS schema: IBY_FNDCPT_SYS_DC_PF_B (the base table holding the actual profile configuration rows) and IBY_FNDCPT_SYS_DC_PF_TL (the translation table holding language-specific text such as SYS_DC_PROFILE_NAME and DESCRIPTION). These are joined on SYS_DC_PROFILE_CODE. The _B table supplies all operational attributes, while the _TL table supplies the translated name and description filtered by USERENV('LANG'). This B/TL structure is the standard Oracle EBS pattern for translatable reference entities; the _VL view encapsulates the join so callers do not need to replicate the language predicate.

Key Columns

• SYS_DC_PROFILE_CODE — the profile identifier and join key between the base and translation tables.
• SYS_DC_PROFILE_NAME / DESCRIPTION — human-readable profile name and description from the translation table, in the session language.
• SETTLEMENT_REQ_FLAG — indicates whether settlement is required for profiles using this configuration.
• SETTLEMENT_FORMAT_CODE — the file/message format used for settlement processing.
• SETTLEMENT_TRANS_PRTCL_CODE — the transmission protocol applied to settlement-phase messaging with the payment system.
• SETTLEMENT_ACK_RDR_CODE — the acknowledgment reader used to interpret settlement responses.
• ONLINE_DEB_* and QUERY_* columns — parallel protocol, format, and acknowledgment settings for online debit and query phases (e.g., ONLINE_DEB_TRANS_PRTCL_CODE, QUERY_TRANS_PRTCL_CODE, QUERY_ACK_RDR_CODE).
• PAYMENT_SYSTEM_ID — the payment system to which the profile is associated.
• GROUP_BY_* columns — control flags for grouping transmissions by organization, legal entity, internal bank account, settlement currency, and settlement date.
• LIMIT_BY_* columns — constraints on batch composition, such as amount currency, exchange rate type, total amount, and settlement number.
• SETTLEMENT_COMPLETE_POINT, AUTOMATIC_PN_SUBMIT_FLAG, OVERRIDE_PAYER_DELIVERY_FLAG, and the payer notification columns — behavior controls for settlement completion and payer notification.
• INACTIVE_DATE, OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit and concurrency columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — descriptive flexfield segments for extensibility.

Common Use Cases and Queries

Typical uses include auditing which transmission protocol is configured for settlement across payment profiles, diagnosing settlement failures by comparing settlement, query, and online-debit protocol settings, and driving integration or migration scripts that read profile configuration. A representative query filtering on the settlement protocol is:

SELECT profile.sys_dc_profile_code,
       profile.sys_dc_profile_name,
       profile.settlement_req_flag,
       profile.settlement_format_code,
       profile.settlement_trans_prtcl_code,
       profile.settlement_ack_rdr_code,
       profile.payment_system_id,
       profile.inactive_date
  FROM apps.iby_fndcpt_sys_dc_pf_vl profile
 WHERE profile.settlement_trans_prtcl_code IS NOT NULL
   AND (profile.inactive_date IS NULL OR profile.inactive_date > SYSDATE)
 ORDER BY profile.sys_dc_profile_name;

Because the view resolves the language at query time, it is well suited to multi-language reporting environments and to concurrent programs that must render profile names correctly for the logged-in user. When only a single profile is needed, the profile code can be substituted directly into the WHERE clause; joins to IBY_PAYMENT_SYSTEMS on PAYMENT_SYSTEM_ID supply the payment system name for consolidated reports.