Search Results iby_fndcpt_sys_eft_pf_b
Overview
The table IBY_FNDCPT_SYS_EFT_PF_B is a core data object within the Oracle E-Business Suite Payments module (IBY). It serves as the master definition table for system-level Electronic Funds Transfer (EFT) profiles. These profiles are foundational configurations that define the technical and operational parameters for how the system communicates with external payment systems or banks for EFT transactions. The table stores the setup that governs critical processes such as funds transfer initiation, payment verification, and status queries, acting as a central control point for EFT communication standards within the application.
Key Information Stored
The table's primary key, SYS_EFT_PROFILE_CODE, uniquely identifies each system EFT profile. The structure, as indicated by its foreign key relationships, stores references to various supporting setup entities. Key columns include PAYMENT_SYSTEM_ID, linking to a specific banking entity (BEP). Crucially, the table holds format and protocol codes for different EFT operations: FUNDS_XFER_FORMAT_CODE and FUNDS_XFER_TRANS_PRTCL_CODE for payment files, VERIFY_FORMAT_CODE and VERIFY_TRANS_PRTCL_CODE for verification messages, and QUERY_FORMAT_CODE and QUERY_TRANS_PRTCL_CODE for inquiry processes. It also stores codes for acknowledgment handling (e.g., FUNDS_XFER_ACK_RDR_CODE) and references to document formats for payer notifications and accompanying letters.
Common Use Cases and Queries
This table is primarily referenced during the execution and monitoring of automated payment batches. When a payment process request is submitted, the system references the active system EFT profile to determine the correct file format, transmission protocol, and destination for generating the payment instruction file. Common queries involve joining this table with related setup tables to audit or report on the EFT configuration.
- Listing all configured system EFT profiles with their linked payment systems:
SELECT pf.sys_eft_profile_code, bep.bep_name FROM iby_fndcpt_sys_eft_pf_b pf, iby_bepinfo bep WHERE pf.payment_system_id = bep.bepid; - Identifying the format and protocol for funds transfer for a specific profile:
SELECT fnd_format.format_name, prot.protocol_name FROM iby_fndcpt_sys_eft_pf_b pf, iby_formats_b fnd_format, iby_transmit_protocols_b prot WHERE pf.funds_xfer_format_code = fnd_format.format_code AND pf.funds_xfer_trans_prtcl_code = prot.protocol_code AND pf.sys_eft_profile_code = 'PROFILE_CODE';
Related Objects
IBY_FNDCPT_SYS_EFT_PF_B has extensive dependencies, primarily as a parent table that references key setup entities via foreign keys. Major related objects include:
- IBY_BEPINFO: Provides the payment system (Bank/BEP) details via the PAYMENT_SYSTEM_ID foreign key.
- IBY_FORMATS_B: Referenced multiple times for defining the format of payment files (FUNDS_XFER), verification messages (VERIFY), queries (QUERY), and notification letters.
- IBY_TRANSMIT_PROTOCOLS_B: Referenced to define the transmission protocol (e.g., FTP, SFTP) for funds transfer, verification, and query operations.
- IBY_FNDCPT_SYS_EFT_PF_TL: The corresponding translation table for multilingual support of profile descriptions.
-
Table: IBY_FNDCPT_SYS_EFT_PF_B
12.2.2
owner:IBY, object_type:TABLE, fnd_design_data:IBY.IBY_FNDCPT_SYS_EFT_PF_B, object_name:IBY_FNDCPT_SYS_EFT_PF_B, status:VALID, product: IBY - Payments , implementation_dba_data: IBY.IBY_FNDCPT_SYS_EFT_PF_B ,
-
Table: IBY_FNDCPT_SYS_EFT_PF_B
12.1.1
owner:IBY, object_type:TABLE, fnd_design_data:IBY.IBY_FNDCPT_SYS_EFT_PF_B, object_name:IBY_FNDCPT_SYS_EFT_PF_B, status:VALID, product: IBY - Payments , implementation_dba_data: IBY.IBY_FNDCPT_SYS_EFT_PF_B ,
-
Table: IBY_FORMATS_B
12.2.2
owner:IBY, object_type:TABLE, fnd_design_data:IBY.IBY_FORMATS_B, object_name:IBY_FORMATS_B, status:VALID, product: IBY - Payments , description: Stores payment processing format types , implementation_dba_data: IBY.IBY_FORMATS_B ,
-
Table: IBY_FORMATS_B
12.1.1
owner:IBY, object_type:TABLE, fnd_design_data:IBY.IBY_FORMATS_B, object_name:IBY_FORMATS_B, status:VALID, product: IBY - Payments , description: Stores payment processing format types , implementation_dba_data: IBY.IBY_FORMATS_B ,
-
Table: IBY_TRANSMIT_PROTOCOLS_B
12.1.1
owner:IBY, object_type:TABLE, fnd_design_data:IBY.IBY_TRANSMIT_PROTOCOLS_B, object_name:IBY_TRANSMIT_PROTOCOLS_B, status:VALID, product: IBY - Payments , implementation_dba_data: IBY.IBY_TRANSMIT_PROTOCOLS_B ,
-
Table: IBY_TRANSMIT_PROTOCOLS_B
12.2.2
owner:IBY, object_type:TABLE, fnd_design_data:IBY.IBY_TRANSMIT_PROTOCOLS_B, object_name:IBY_TRANSMIT_PROTOCOLS_B, status:VALID, product: IBY - Payments , implementation_dba_data: IBY.IBY_TRANSMIT_PROTOCOLS_B ,
-
Table: IBY_BEPINFO
12.2.2
owner:IBY, object_type:TABLE, fnd_design_data:IBY.IBY_BEPINFO, object_name:IBY_BEPINFO, status:VALID, product: IBY - Payments , description: IBY_BEPKEYS stores information about the payment systems. , implementation_dba_data: IBY.IBY_BEPINFO ,
-
Table: IBY_BEPINFO
12.1.1
owner:IBY, object_type:TABLE, fnd_design_data:IBY.IBY_BEPINFO, object_name:IBY_BEPINFO, status:VALID, product: IBY - Payments , description: IBY_BEPINFO has a row for every BEP(Back End Payment System) configured in system. A BEP is a payment provider such as Cybercash, Verifone etc , implementation_dba_data: IBY.IBY_BEPINFO ,
-
View: IBY_FNDCPT_SYS_EFT_PF_VL
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:IBY.IBY_FNDCPT_SYS_EFT_PF_VL, object_name:IBY_FNDCPT_SYS_EFT_PF_VL, status:VALID, product: IBY - Payments , implementation_dba_data: APPS.IBY_FNDCPT_SYS_EFT_PF_VL ,
-
View: IBY_FNDCPT_SYS_EFT_PF_VL
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:IBY.IBY_FNDCPT_SYS_EFT_PF_VL, object_name:IBY_FNDCPT_SYS_EFT_PF_VL, status:VALID, product: IBY - Payments , implementation_dba_data: APPS.IBY_FNDCPT_SYS_EFT_PF_VL ,
-
View: IBY_TRXN_EXT_AUTHS_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:IBY.IBY_TRXN_EXT_AUTHS_V, object_name:IBY_TRXN_EXT_AUTHS_V, status:VALID, product: IBY - Payments , implementation_dba_data: APPS.IBY_TRXN_EXT_AUTHS_V ,
-
View: IBY_TRXN_EXT_AUTHS_V
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:IBY.IBY_TRXN_EXT_AUTHS_V, object_name:IBY_TRXN_EXT_AUTHS_V, status:VALID, product: IBY - Payments , implementation_dba_data: APPS.IBY_TRXN_EXT_AUTHS_V ,