Search Results ap_paycard_trx_fee_header_all




Overview
Explore in AI Chat

Overview

The AP_PAYCARD_TRX_FEE_HEADER_ALL table is a core data structure within the Oracle E-Business Suite Payables (AP) module, specifically supporting the Payment Card functionality. It serves as a header-level repository for managing transaction fees or charges associated with corporate payment card programs. Its primary role is to consolidate key organizational and vendor context—such as operating unit, currency, and vendor details—for one or more related transaction fee detail records. This design enables the systematic tracking and accounting of card-related charges over distinct, non-overlapping periods, which is essential for accurate expense allocation and reconciliation between the organization and its card issuer or vendor.

Key Information Stored

The table's structure is designed to capture the foundational attributes that group and define a set of transaction fees. While the full column list is not provided in the excerpt, the documented description and primary key indicate critical fields. The TRX_FEE_HEADER_ID column is the unique primary key identifier. Crucially for the user's context of "vendor," the table explicitly stores Vendor and Vendor Site information, linking the fee structure to a specific supplier. It also holds the Operating Unit (ORG_ID) for multi-org security and reporting, and the Currency Code, which defines the monetary denomination for the associated fees. These columns collectively establish the contractual and organizational framework for the detailed fee calculations stored in related tables.

Common Use Cases and Queries

This table is central to processes involving the analysis and reporting of payment card program costs. A common use case is generating a summary of all active fee agreements by vendor to assess program expenses. For instance, a financial analyst may run a query to list all vendors with configured card fee structures within a specific operating unit. Another critical scenario is supporting the invoice creation process in Payables, where fee details linked to this header are used to generate supplier invoices for the charges. A typical reporting query might join this header to vendor tables to analyze fees by vendor name.

SELECT h.vendor_id, pv.vendor_name, h.vendor_site_id, pvs.vendor_site_code,
       h.org_id, h.currency_code
FROM ap_paycard_trx_fee_header_all h,
     po_vendors pv,
     po_vendor_sites_all pvs
WHERE h.vendor_id = pv.vendor_id
AND h.vendor_site_id = pvs.vendor_site_id
AND h.org_id = 123;

Related Objects

As a header table, AP_PAYCARD_TRX_FEE_HEADER_ALL has a direct foreign key relationship to detail tables that store the specific fee rates and rules. The primary key, TRX_FEE_HEADER_ID, is almost certainly referenced by a foreign key in a related detail table such as AP_PAYCARD_TRX_FEE_DETAILS_ALL (or similarly named), which holds the periodic charge percentages or amounts. It also has fundamental joins to standard EBS supplier tables: PO_VENDORS (on VENDOR_ID) and PO_VENDOR_SITES_ALL (on VENDOR_SITE_ID) to retrieve vendor names and addresses. The ORG_ID column links it to HR_OPERATING_UNITS for operating unit information.