Search Results iby_trxn_types_b




Overview
Explore in AI Chat

Overview

The IBY_TRXN_TYPES_B table is a core reference table within the Oracle Payments (IBY) module of Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It serves as the master repository for defining and managing payment process transaction types. These transaction types categorize the nature of payment-related operations, such as payments, refunds, or stop payments, that are initiated from various source applications within the EBS ecosystem. The table's role is critical for the proper routing, processing, and validation of payment instructions, ensuring that transactions are handled according to their specific business rules and workflows. Its structure, which includes an APPLICATION_ID, indicates its design to support transaction types specific to individual EBS applications, enabling a centralized yet flexible payment framework.

Key Information Stored

The table stores the unique combinations that define a valid payment transaction type for a given application. Based on the provided metadata, the primary key columns are the most critical fields. The APPLICATION_ID column links the transaction type to a specific Oracle EBS application, such as Payables (AP) or Receivables (AR). The PAY_PROC_TRXN_TYPE_CODE column holds the internal code that identifies the transaction type itself (e.g., 'PAYMENT', 'REFUND'). While the full column list is not detailed in the excerpt, typical supplementary columns in such a table would include a user-facing NAME, a DESCRIPTION, and control attributes like ENABLED_FLAG and CREATION_DATE. The compound primary key ensures that the same transaction type code can be reused across different applications with potentially different meanings or processing requirements.

Common Use Cases and Queries

This table is primarily referenced for validation and reporting. When a payment document or transaction is created, the system validates that the provided APPLICATION_ID and PAY_PROC_TRXN_TYPE_CODE pair exists in IBY_TRXN_TYPES_B. Common queries involve listing all valid transaction types for a specific application or joining to transactional tables for detailed reporting. For instance, to audit all payment process transaction types available for Oracle Payables (APPLICATION_ID = 200), a DBA or developer might use:

  • SELECT pay_proc_trxn_type_code, name FROM iby_trxn_types_b WHERE application_id = 200 AND enabled_flag = 'Y';

Another critical use case is troubleshooting data integrity issues in payment batches, where joins to IBY_DOCUMENTS_PAYABLE_H are used to verify that all documents reference a valid, defined transaction type.

Related Objects

As indicated by the foreign key relationships in the metadata, IBY_TRXN_TYPES_B is a parent table to several key transactional tables in the Payments module. The IBY_DOCUMENTS_PAYABLE_H table, which stores headers for payable documents, references it via the CALLING_APP_ID and PAY_PROC_TRXN_TYPE_CODE columns to classify each document. Similarly, the IBY_TRANSACTION_ERRORS table references it to categorize errors by the transaction type during which they occurred. These relationships underscore the table's foundational role: it provides the master definition that ensures consistency and referential integrity across the payment transaction lifecycle, from document creation to error handling.