Search Results fv_pb_seq_assignments_all




Overview
Explore in AI Chat

Overview

The FV_PB_SEQ_ASSIGNMENTS_ALL table is a core data object within the Oracle E-Business Suite Federal Financials (FV) module. It serves as the primary repository for defining and storing payment batch sequence assignments. These assignments are critical for configuring the automated sequencing of payments within federal financial operations, ensuring compliance with specific disbursement rules and workflows. The table functions as the underlying base table for the Payment Batch Sequence Assignments application form, meaning any configuration performed through that user interface is persisted directly to this table. Its role is integral to the setup and execution of controlled payment batch processes in government-centric implementations of Oracle EBS.

Key Information Stored

While the provided ETRM metadata does not list specific columns, the table's description and foreign key relationships define its key data elements. The table stores assignment records that link payment sequencing rules to relevant organizational and payment parameters. A critical column is PAYMENT_REASON_CODE, which establishes a direct foreign key relationship to the IBY_PAYMENT_REASONS_B table. This indicates that each assignment record associates a payment reason with a specific sequencing configuration. Other columns typically found in such assignment tables include identifiers for the assigned payment batch sequence, the operating unit (suggested by the "_ALL" suffix), and effective date ranges to control the assignment's validity period.

Common Use Cases and Queries

The primary use case is the administrative setup and maintenance of payment batch sequencing rules via the dedicated application form. Functional users utilize this configuration to ensure payments are grouped and processed in a mandated order based on criteria like payment reason. From a reporting and auditing perspective, common queries involve listing all active sequence assignments for an operating unit or validating the setup for a specific payment reason. A typical SQL pattern would join this table with IBY_PAYMENT_REASONS_B to get the descriptive meaning of the reason code.

SELECT fv_assg.sequence_id,
       fv_assg.payment_reason_code,
       ipr.payment_reason_name
FROM   fv.fv_pb_seq_assignments_all fv_assg,
       iby.iby_payment_reasons_b ipr
WHERE  fv_assg.payment_reason_code = ipr.payment_reason_code
AND    fv_assg.org_id = :org_id
AND    SYSDATE BETWEEN fv_assg.start_date_active AND NVL(fv_assg.end_date_active, SYSDATE);

Related Objects

The most significant related object, as explicitly defined in the metadata, is the IBY_PAYMENT_REASONS_B table. This is a master table in the Oracle Payments (IBY) module that holds the valid list of payment reason codes. The foreign key from FV_PB_SEQ_ASSIGNMENTS_ALL.PAYMENT_REASON_CODE to this table ensures data integrity. The Payment Batch Sequence Assignments form is the primary application interface dependent on this table. Furthermore, this table is likely referenced by various Federal Financials batch processes and programs that execute payment batch creation, relying on the assigned sequences to order the generated payments correctly.