Search Results extract_id




Overview
Explore in AI Chat

Overview

The IBY_EXTRACTS_B table is a core data object within the Oracle E-Business Suite (EBS) Payments (IBY) module. It serves as the master definition table for payment data extracts, which are structured queries that select and format payment instruction data for subsequent payment file creation. Each record in this table defines a specific, versioned extract program that dictates the data selection logic and mapping required to generate payment files in various electronic formats (e.g., NACHA, SEPA, BACS) or printed checks. Its role is foundational to the payment execution process, acting as the bridge between approved payment instructions and the formatted output sent to banks or printers.

Key Information Stored

The table stores the technical and versioning metadata for each payment extract definition. The primary columns include EXTRACT_ID, which is the unique system-generated identifier serving as the primary key. The EXTRACT_CODE and EXTRACT_VERSION columns together form a unique key, defining the specific name and version of the extract program. Other critical columns typically include the EXTRACT_PROGRAM (the name of the concurrent program or PL/SQL package that executes the extract logic), the applicable PAYMENT_CHANNEL (e.g., Electronic, Printed), and STATUS. The table also contains columns for controlling parameters, such as the default output format and security attributes, which govern how the extract is executed within the payment process flow.

Common Use Cases and Queries

This table is primarily referenced during the setup and execution of the Payment Process Request. Administrators query it to review available extract definitions or to troubleshoot payment formatting issues. A common reporting need is to list all active extract definitions for a given payment channel. A typical SQL pattern would be:

  • SELECT extract_code, extract_version, extract_program, payment_channel FROM iby.iby_extracts_b WHERE status = 'ACTIVE' ORDER BY extract_code;

Another frequent use case involves tracing the configuration for a specific payment file generation error. Support personnel often join IBY_EXTRACTS_B with IBY_FORMATS_B and execution log tables (e.g., IBY_PAYMENTS_ALL) using EXTRACT_ID to diagnose mismatches between the extracted data and the expected file format requirements.

Related Objects

The IBY_EXTRACTS_B table has direct relationships with several key objects in the Payments schema, as indicated by the provided foreign key metadata. The IBY_EXTRACTS_TL table holds the translated descriptive names (e.g., in multiple languages) for the extract definitions, linked via the EXTRACT_ID. The IBY_FORMATS_B table, which defines the structure and formatting rules for payment files, references IBY_EXTRACTS_B.EXTRACT_ID to associate a specific data extract with one or more output formats. Furthermore, the extract definitions are invoked by the Payment Manager architecture, and their logic is often implemented in packages such as IBY_DISBURSE_UI_API_PUB, which uses the extract parameters to fetch and prepare payment data.