Search Results iby_remit_advice_setup
Overview
The IBY_REMIT_ADVICE_SETUP table is a core repository within the Oracle E-Business Suite Payments (IBY) module. It stores the configuration for generating and delivering remittance advice documents, which are detailed statements of payment information sent to a payee (e.g., a supplier) separately from the payment instrument itself. This separation is critical for electronic payments where remittance data is often transmitted via email, a web portal, or Electronic Data Interchange (EDI). The table's configuration is organized by the SYSTEM_PROFILE_CODE, linking remittance advice settings directly to a specific Payment Process Profile, which defines the rules for a payment batch. This setup enables businesses to automate and tailor the delivery of remittance information according to the payment method and payee requirements.
Key Information Stored
The table's primary function is to define the format and delivery mechanism for remittance advices per payment process profile. While the full column list is not detailed in the provided metadata, the documented relationships and context indicate several critical data points. The SYSTEM_PROFILE_CODE serves as the primary key, uniquely identifying the setup for a specific profile. The REMITTANCE_ADVICE_FORMAT_CODE is a foreign key that determines the output format (e.g., a specific XML, text, or PDF layout) by referencing the IBY_FORMATS_B table. Other columns likely control delivery methods (e.g., email, printing), delivery addresses, triggering events, and whether advice generation is enabled for the profile.
Common Use Cases and Queries
This table is central to troubleshooting and reporting on remittance advice configurations. A common administrative task is verifying the setup for a known payment process profile. A typical query would join to the profile and format tables to present a readable summary:
SELECT ras.system_profile_code, prof.profile_name, fmt.format_name FROM iby_remit_advice_setup ras, iby_sys_pmt_profiles_b prof, iby_formats_b fmt WHERE ras.system_profile_code = prof.system_profile_code AND ras.remittance_advice_format_code = fmt.format_code;
Another critical use case is during the implementation or upgrade of payment processes, where this table is populated or updated via the Oracle Payments Manager user interface to define how remittances are generated for different payee groups and payment methods.
Related Objects
The IBY_REMIT_ADVICE_SETUP table has defined relationships with other key Payments tables, as per the provided metadata:
- IBY_SYS_PMT_PROFILES_B: The table is child to this parent table via the
SYSTEM_PROFILE_CODEforeign key. This enforces that remittance advice setup is defined for a valid, existing payment process profile. - IBY_FORMATS_B: The table references this master list of document formats via the
REMITTANCE_ADVICE_FORMAT_CODEforeign key. This determines the technical structure of the generated advice document.
As the central configuration point, this table is also referenced by various internal Payment APIs and likely underpins key views used in the Oracle Payments Manager interface for setup and inquiry.
-
Table: IBY_REMIT_ADVICE_SETUP
12.2.2
owner:IBY, object_type:TABLE, fnd_design_data:IBY.IBY_REMIT_ADVICE_SETUP, object_name:IBY_REMIT_ADVICE_SETUP, status:VALID, product: IBY - Payments , description: IBY_REMIT_ADVICE_SETUP stores information on creating and delivering remittance information, or remittance advice, for a payee separately from the payment itself. Remittance advice setup is organized by payment process profile. Each payment , implementation_dba_data: IBY.IBY_REMIT_ADVICE_SETUP ,
-
Table: IBY_REMIT_ADVICE_SETUP
12.1.1
owner:IBY, object_type:TABLE, fnd_design_data:IBY.IBY_REMIT_ADVICE_SETUP, object_name:IBY_REMIT_ADVICE_SETUP, status:VALID, product: IBY - Payments , implementation_dba_data: IBY.IBY_REMIT_ADVICE_SETUP ,
-
APPS.IBY_FD_POST_PICP_PROGS_PVT dependencies on IBY_REMIT_ADVICE_SETUP
12.2.2
-
APPS.IBY_PAYINSTR_PUB dependencies on IBY_REMIT_ADVICE_SETUP
12.2.2
-
APPS.IBY_FD_USER_API_PUB dependencies on IBY_REMIT_ADVICE_SETUP
12.1.1
-
APPS.IBY_PAYGROUP_PUB dependencies on IBY_REMIT_ADVICE_SETUP
12.1.1
-
APPS.IBY_FD_USER_API_PUB dependencies on IBY_REMIT_ADVICE_SETUP
12.2.2
-
APPS.IBY_FD_EXTRACT_GEN_PVT dependencies on IBY_REMIT_ADVICE_SETUP
12.1.1
-
APPS.IBY_PAYGROUP_PUB dependencies on IBY_REMIT_ADVICE_SETUP
12.1.1
-
APPS.IBY_UPG_PPP_PKG dependencies on IBY_REMIT_ADVICE_SETUP
12.2.2
-
APPS.IBY_DISBURSE_UI_API_PUB_PKG dependencies on IBY_REMIT_ADVICE_SETUP
12.1.1
-
APPS.IBY_UPG_PPP_PKG dependencies on IBY_REMIT_ADVICE_SETUP
12.1.1
-
APPS.IBY_DISBURSE_UI_API_PUB_PKG dependencies on IBY_REMIT_ADVICE_SETUP
12.2.2
-
APPS.IBY_PAYGROUP_PUB dependencies on IBY_REMIT_ADVICE_SETUP
12.2.2
-
APPS.IBY_PAYINSTR_PUB dependencies on IBY_REMIT_ADVICE_SETUP
12.1.1
-
APPS.IBY_FD_POST_PICP_PROGS_PVT dependencies on IBY_REMIT_ADVICE_SETUP
12.1.1
-
APPS.IBY_PAYGROUP_PUB dependencies on IBY_REMIT_ADVICE_SETUP
12.2.2
-
APPS.IBY_FD_EXTRACT_GEN_PVT dependencies on IBY_REMIT_ADVICE_SETUP
12.2.2
-
APPS.IBY_DISBURSE_UI_API_PUB_PKG dependencies on IBY_SYS_PMT_PROFILES_B
12.2.2
-
APPS.IBY_DISBURSE_UI_API_PUB_PKG dependencies on IBY_SYS_PMT_PROFILES_B
12.1.1
-
VIEW: IBY.IBY_REMIT_ADVICE_SETUP#
12.2.2
owner:IBY, object_type:VIEW, object_name:IBY_REMIT_ADVICE_SETUP#, status:VALID,
-
TRIGGER: APPS.IBY_REMIT_ADVICE_SETUP+
12.2.2
owner:APPS, object_type:TRIGGER, object_name:IBY_REMIT_ADVICE_SETUP+, status:VALID,
-
APPS.IBY_PAYGROUP_PUB dependencies on FND_APPLICATION_ALL_VIEW
12.1.1
-
TRIGGER: APPS.IBY_REMIT_ADVICE_SETUP+
12.2.2
-
SYNONYM: APPS.IBY_REMIT_ADVICE_SETUP
12.1.1
owner:APPS, object_type:SYNONYM, object_name:IBY_REMIT_ADVICE_SETUP, status:VALID,
-
SYNONYM: APPS.IBY_REMIT_ADVICE_SETUP
12.2.2
owner:APPS, object_type:SYNONYM, object_name:IBY_REMIT_ADVICE_SETUP, status:VALID,
-
APPS.IBY_PAYGROUP_PUB dependencies on IBY_BANK_INSTRUCTIONS_VL
12.2.2
-
VIEW: IBY.IBY_REMIT_ADVICE_SETUP#
12.2.2
-
APPS.IBY_PAYGROUP_PUB dependencies on FND_APPLICATION
12.1.1
-
APPS.IBY_DISBURSE_UI_API_PUB_PKG dependencies on IBY_PAYMENT_PROFILES
12.1.1
-
APPS.IBY_PAYGROUP_PUB dependencies on CE_BANK_BRANCHES_V
12.1.1
-
APPS.IBY_UPG_PPP_PKG dependencies on IBY_INSTR_CREATION_RULES
12.2.2
-
FUNCTION: APPS.IBY_REMIT_ADVICE_SETUP=
12.2.2
-
APPS.IBY_PAYGROUP_PUB dependencies on IBY_EXT_BANK_ACCOUNTS
12.1.1
-
TABLE: IBY.IBY_REMIT_ADVICE_SETUP
12.1.1
owner:IBY, object_type:TABLE, fnd_design_data:IBY.IBY_REMIT_ADVICE_SETUP, object_name:IBY_REMIT_ADVICE_SETUP, status:VALID,
-
FUNCTION: APPS.IBY_REMIT_ADVICE_SETUP=
12.2.2
owner:APPS, object_type:FUNCTION, object_name:IBY_REMIT_ADVICE_SETUP=, status:VALID,
-
APPS.IBY_FD_USER_API_PUB dependencies on IBY_FORMATS_VL
12.2.2
-
APPS.IBY_DISBURSE_UI_API_PUB_PKG dependencies on IBY_PAYMENT_PROFILES
12.2.2
-
APPS.IBY_FD_USER_API_PUB dependencies on IBY_FORMATS_VL
12.1.1
-
TABLE: IBY.IBY_REMIT_ADVICE_SETUP
12.2.2
owner:IBY, object_type:TABLE, fnd_design_data:IBY.IBY_REMIT_ADVICE_SETUP, object_name:IBY_REMIT_ADVICE_SETUP, status:VALID,
-
Table: IBY_SYS_PMT_PROFILES_B
12.1.1
owner:IBY, object_type:TABLE, fnd_design_data:IBY.IBY_SYS_PMT_PROFILES_B, object_name:IBY_SYS_PMT_PROFILES_B, status:VALID, product: IBY - Payments , implementation_dba_data: IBY.IBY_SYS_PMT_PROFILES_B ,
-
APPS.IBY_UPG_PPP_PKG dependencies on IBY_ACCT_PMT_PROFILES_TL
12.2.2
-
APPS.IBY_UPG_PPP_PKG dependencies on IBY_INSTR_CREATION_RULES
12.1.1
-
12.2.2 DBA Data
12.2.2
-
PACKAGE BODY: APPS.IBY_UPG_PPP_PKG
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:IBY_UPG_PPP_PKG, status:VALID,
-
12.2.2 DBA Data
12.2.2
-
APPS.IBY_UPG_PPP_PKG dependencies on IBY_PMT_CREATION_RULES
12.2.2
-
PACKAGE BODY: APPS.IBY_UPG_PPP_PKG
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:IBY_UPG_PPP_PKG, status:VALID,
-
APPS.IBY_FD_USER_API_PUB dependencies on IBY_PAY_INSTRUCTIONS_ALL
12.1.1
-
PACKAGE BODY: APPS.IBY_FD_USER_API_PUB
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:IBY_FD_USER_API_PUB, status:VALID,