Search Results trx_detail_id

Overview

The AP_CC_TRX_DETAILS table is a core data object within the Oracle E-Business Suite Payables (AP) module. It functions as the detailed transactional repository for corporate credit card expenses. While header-level information for a credit card transaction is stored in the AP_CREDIT_CARD_TRXNS_ALL table, this table holds the granular, line-item details of those transactions. Its primary role is to enable the accurate reconciliation, auditing, and accounting of credit card expenditures by capturing specific expense items, such as individual purchases or line-level tax and merchant details, that collectively make up a single credit card statement line.

Key Information Stored

The table's structure is designed to itemize credit card charges. Its primary key, TRX_DETAIL_ID, uniquely identifies each detail line. The most critical foreign key is TRX_ID, which links each detail record to its parent transaction header in the AP_CREDIT_CARD_TRXNS_ALL table. Other significant columns typically include fields for the expense amount, description, merchant information, tax amounts and codes, and expense account assignments (such as CODE_COMBINATION_ID). This detailed breakdown allows organizations to move beyond lump-sum credit card charges and allocate expenses accurately to specific accounts, projects, or cost centers.

Common Use Cases and Queries

This table is central to processes involving credit card expense management and reporting. A common use case is generating detailed audit reports for credit card statements, matching imported transaction lines to employee expense reports. System administrators and functional consultants often query this table to troubleshoot data issues or validate the integrity of imported credit card feeds. A fundamental query pattern involves joining to the header table to get a complete view of a transaction.

• Sample Query: To retrieve all detail lines for a specific credit card transaction, one would use: SELECT * FROM AP_AP_CC_TRX_DETAILS WHERE TRX_ID = <header_id>;
• Reporting Use Case: Creating a report that summarizes credit card expenses by general ledger account, which requires joining AP_CC_TRX_DETAILS to AP_CREDIT_CARD_TRXNS_ALL and then to GL_CODE_COMBINATIONS.

Related Objects

AP_CC_TRX_DETAILS has a defined, dependent relationship with a key Payables table, as documented in the provided metadata. The primary relationship is established through its foreign key constraint.

• AP_CREDIT_CARD_TRXNS_ALL: This is the parent header table. The foreign key AP_CC_TRX_DETAILS.TRX_ID references a transaction in this table. All detail records must correspond to a valid header record. This is the most critical join for any comprehensive query.

While not listed in the provided excerpt, this table is also commonly related to GL_CODE_COMBINATIONS (for the expense account) and may be referenced by various Payables interfaces and reconciliation reports.