Results for “ap_paycard_trx_fee_header_all”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AP_PAYCARD_TRX_FEE_HEADER_ALL is a transactional table in the Oracle Payables (AP) module that stores payment card transaction fee charge information. It captures the operating unit, currency code, card issuer, and card issuer site details associated with one or more transaction fee detail records spanning non-overlapping periods. In the context of Oracle EBS 12.1.1 and 12.2.2, this table acts as the header-level container for payment card fee agreements negotiated with card issuers, enabling Payables to compute and record the fees applied when corporate payment cards are used to settle supplier invoices.

The object resides in the AP schema and is registered as VALID in the ETRM data dictionary. Its primary key is AP_PCARD_TRX_FEE_HEADER_PK, defined on the TRX_FEE_HEADER_ID column. A second unique index, AP_PAYCARD_TRX_FEE_HDR_U1, also enforces uniqueness on TRX_FEE_HEADER_ID. The documented physical schema contains 26 columns. Based on the mined foreign key structure, the ETRM metadata classifies this object heuristically as standalone, suggesting a Data Vault modeling approach in which the table functions as an independent hub-like structure rather than a dependent link or satellite. This classification should be treated as a modeling suggestion, since the table carries both surrogate identity and descriptive attributes.

Key Information Stored

The most operationally significant columns documented for this table include:

• TRX_FEE_HEADER_ID — the surrogate primary key uniquely identifying each fee header record; also the business-key candidate via AP_PAYCARD_TRX_FEE_HDR_U1.
• ORG_ID — the operating unit that owns the fee agreement, supporting multi-org security and reporting.
• CURRENCY_CODE — the currency in which the transaction fees are denominated.
• CARD_ISSUER_ID — the identifier of the card issuer (typically a vendor) with whom the fee arrangement exists.
• CARD_ISSUER_SITE_ID — the specific issuer site used as the point of reference for the fee schedule.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard EBS WHO columns providing audit and concurrency tracking.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the DFF (descriptive flexfield) columns reserved for customer-specific extensions.

The descriptive business keys are the combination of ORG_ID, CURRENCY_CODE, CARD_ISSUER_ID, and CARD_ISSUER_SITE_ID, which together distinguish which fee schedules apply within a given operating unit and currency. The surrogate key TRX_FEE_HEADER_ID provides the stable internal reference used by dependent fee detail records.

Common Use Cases and Queries

Typical reporting scenarios include listing active fee agreements per operating unit, verifying card issuer coverage, and auditing fee configurations before reconciliation runs. A representative query joining to the card issuer vendor master might read:

• SELECT h.trx_fee_header_id, h.org_id, h.currency_code, h.card_issuer_id, h.card_issuer_site_id FROM ap_paycard_trx_fee_header_all h WHERE h.org_id = :p_org_id;
• Filtering by CURRENCY_CODE and CARD_ISSUER_ID to identify the correct fee schedule for a given transaction.
• Extracting headers with NULL or expired detail coverage by comparing header creation dates against the non-overlapping periods held in the detail table.
• Feeding fee calculations during payment card transaction processing in Payables, where the header defines the issuer context and the detail rows define rates and validity windows.

Because the table is secured by ORG_ID, reporting queries should always include operating unit predicates or use the Multi-Org views to avoid cross-OU data exposure.

Related Objects

The following objects are significant companions to AP_PAYCARD_TRX_FEE_HEADER_ALL. The header is parent to the transaction fee detail records that carry the actual rate and period information, joining on TRX_FEE_HEADER_ID:

• AP_PAYCARD_TRX_FEE_DETAIL_ALL — child detail table referencing TRX_FEE_HEADER_ID.
• AP_PAYCARD_TRX_FEE_HEADER — the Multi-Org secure view over this _ALL table.
• AP_PAYCARD_TRX_FEE_DETAIL — corresponding secure view for detail records.
• AP_CARD_ISSUERS / AP_CARD_ISSUER_SITES — issuer master data joined via CARD_ISSUER_ID and CARD_ISSUER_SITE_ID.
• AP_SUPPLIERS / AP_SUPPLIER_SITES_ALL — vendor master referenced when the card issuer is defined as a supplier.
• AP_PAYMENT_CARDS_ALL — the payment card definition referenced during fee computation.

These relationships allow the fee header to anchor configuration, while the detail records govern the effective-dated calculation logic applied to payment card transactions.