Search Results iby_bank_instructions_b




Overview
Explore in AI Chat

Overview

The IBY_BANK_INSTRUCTIONS_B table is a core reference data repository within the Oracle Payments (IBY) module of Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It serves as the master table for storing standardized bank instruction codes, which are critical for configuring and executing electronic payment processes. These codes represent specific instructions to a financial institution, such as handling charges or remittance advice delivery methods. The table's primary role is to provide a centralized, validated lookup source for payment process profiles, external payee setups, and individual payment transactions, ensuring consistency and accuracy in payment instructions across the application.

Key Information Stored

The table's structure is designed to manage unique, territory-specific bank instruction codes. The primary key is the BANK_INSTRUCTION_CODE column, which holds the unique identifier for each instruction. A critical column is TERRITORY_CODE, a foreign key to FND_TERRITORIES, which scopes the validity of a bank instruction to a specific country or region, as banking protocols vary geographically. While the provided metadata does not list all columns, typical attributes in such a base table would include CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and START_DATE_ACTIVE/END_DATE_ACTIVE for controlling the effective life of the code. Descriptive, translatable text for each code is stored in the related IBY_BANK_INSTRUCTIONS_TL table.

Common Use Cases and Queries

A primary use case is the setup and maintenance of bank instruction codes via the "Bank Instruction Codes" application page, which corresponds directly to this table. System administrators use this interface to define new codes required for specific payment formats or banking partners. From a reporting and operational perspective, common queries involve listing active instructions for a territory or tracing the usage of a specific code. For example, to identify all payment process profiles using a particular instruction, one might join IBY_BANK_INSTRUCTIONS_B to IBY_SYS_PMT_PROFILES_B. A basic query to audit active codes would be:

  • SELECT BANK_INSTRUCTION_CODE, TERRITORY_CODE FROM IBY.IBY_BANK_INSTRUCTIONS_B WHERE SYSDATE BETWEEN START_DATE_ACTIVE AND NVL(END_DATE_ACTIVE, SYSDATE+1);

Technical consultants often query this table to resolve data issues or validate configurations during payment process profile setup or troubleshooting payment failures related to bank instructions.

Related Objects

IBY_BANK_INSTRUCTIONS_B is a central hub referenced by numerous key objects in the Payments module. Its primary foreign key relationship is with IBY_BANK_INSTRUCTIONS_TL for translated descriptions. Crucially, its BANK_INSTRUCTION_CODE is referenced by two columns (BANK_INSTRUCTION1_CODE, BANK_INSTRUCTION2_CODE) in several major transactional and setup tables, demonstrating its importance in payment execution. These include the payment system profiles (IBY_SYS_PMT_PROFILES_B), external payee records (IBY_EXTERNAL_PAYEES_ALL and IBY_TEMP_EXT_PAYEES), and the payment history table (IBY_PAYMENTS_H). This extensive referencing underscores that the table's data is integral to defining payment rules, payee banking details, and the final instructions transmitted with each payment.