Search Results fv_pb_seq_assignments_all

Overview

The IBY_PAYMENT_REASONS_B table is a core lookup table within the Oracle E-Business Suite Payments (IBY) module, serving as the base table for a territory-specific payment reason code master. It stores standardized codes that categorize the purpose or nature of a payment, providing a critical control point for payment processing and reporting. Unlike generic lookup tables such as FND_LOOKUPS, this table is explicitly designed for the Payments module and includes a mandatory link to the FND_TERRITORIES table, enabling the definition and validation of payment reasons based on specific countries or legal jurisdictions. Its primary role is to supply valid, territory-aware lookup values for assignment to payee records, invoices, and payment documents throughout the payment lifecycle in both Oracle EBS 12.1.1 and 12.2.2.

Key Information Stored

The table's structure centers on the payment reason code and its associated territory. The primary key column, PAYMENT_REASON_CODE, holds the unique identifier for each payment reason. The TERRITORY_CODE column is a foreign key to FND_TERRITORIES, scoping the reason's validity to a specific country. While the provided ETRM excerpt does not list all columns, a typical implementation includes standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE) for auditing, and a column such as ENABLED_FLAG to control the active status of the reason code. The descriptive, translatable name for each code is stored in the related IBY_PAYMENT_REASONS_TL table, which joins via the PAYMENT_REASON_CODE.

Common Use Cases and Queries

This table is central to configuration and transactional validation. A common use case is the setup and maintenance of valid payment reasons for a country during system implementation. Analysts run queries to verify which reasons are active for a given territory or to troubleshoot payment validation errors. For reporting, the table is joined to transactional documents to categorize payment volumes by reason. Sample SQL patterns include retrieving all active reasons for a specific territory and joining to its translated description:

• SELECT b.PAYMENT_REASON_CODE, tl.MEANING FROM IBY.IBY_PAYMENT_REASONS_B b, IBY.IBY_PAYMENT_REASONS_TL tl, FND_TERRITORIES t WHERE b.PAYMENT_REASON_CODE = tl.PAYMENT_REASON_CODE AND b.TERRITORY_CODE = t.TERRITORY_CODE AND t.TERRITORY_CODE = 'US' AND b.ENABLED_FLAG = 'Y';
• SELECT dp.PAYMENT_ID, pr.PAYMENT_REASON_CODE FROM IBY.IBY_DOCS_PAYABLE_ALL dp, IBY.IBY_PAYMENT_REASONS_B pr WHERE dp.PAYMENT_REASON_CODE = pr.PAYMENT_REASON_CODE;

Related Objects

The IBY_PAYMENT_REASONS_B table has extensive foreign key relationships, underscoring its foundational role. It is referenced by major transactional and setup tables in the Payments (IBY), Financials for Venezuela (FV), and Payables modules. Key documented relationships include:

• IBY_DOCS_PAYABLE_ALL: Links payment reasons to invoices and other payable documents.
• IBY_EXTERNAL_PAYEES_ALL & IBY_TEMP_EXT_PAYEES: Associates a reason with internal or external payee records.
• IBY_PAYMENTS_ALL & IBY_PAYMENTS_H: Ties the reason code to actual payment records and their history.
• IBY_PAY_INSTRUCTIONS_ALL & IBY_PAY_INSTRUCTIONS_H: Associates the reason with payment instruction records.
• FV_PB_SEQ_ASSIGNMENTS_ALL & FV_TOP_EXCLUSION_CRITERIA_ALL: Used for Venezuelan localization features like payment book sequencing and treasury exclusion rules.
• IBY_PAYMENT_REASONS_TL: The translation table that provides language-specific descriptions for each reason code.
• FND_TERRITORIES: The parent table defining valid territories via the TERRITORY_CODE foreign key.