Results for “folio_type”

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

Overview

AP_CC_TRX_DETAILS is a Payables (AP) module table in the Oracle E-Business Suite 12.1.1 / 12.2.2 schema. It stores detail-level credit card transaction information, capturing the line-by-line breakdown of individual credit card charges within the broader credit card transaction framework. Where the parent credit card transaction record represents the transaction as a whole, this table provides the underlying detail components — such as travel segments, folio items, fare information, and billed amounts — that comprise a single credit card transaction.

The documented physical schema in ETRM 12.2.2 shows the table owned by the AP schema, containing 25 columns. The primary key is AP_CC_TRX_DETAILS_PK, defined on the TRX_DETAIL_ID column, and a unique index (AP_CC_TRX_DETAILS_U1) also exists on TRX_DETAIL_ID, confirming it as the business-key candidate and sole unique row identifier.

The metadata provides a heuristic Data Vault classification of satellite-leaning, mined from the foreign key structure. Modeled in Data Vault terms, this suggests the table functions primarily as a satellite attached to its parent credit card transaction hub/link: it carries descriptive, transaction-specific attributes (dates, amounts, travel codes) keyed by a surrogate detail identifier and linked upward via TRX_ID. It is not itself a hub of independent business entities.

Key Information Stored

The table's 25 documented columns cluster into identification, amount, and travel-detail attributes.

• TRX_DETAIL_ID — Surrogate primary key (AP_CC_TRX_DETAILS_PK) and unique business-key candidate (AP_CC_TRX_DETAILS_U1). Uniquely identifies each detail line.
• TRX_ID — Foreign key to AP_CREDIT_CARD_TRXNS_ALL. Links the detail line to its parent credit card transaction.
• TRANSACTION_AMOUNT — The monetary amount of the detail-level charge.
• BILLED_AMOUNT — The amount billed, which may differ from the transaction amount for reconciliation purposes.
• ITEM_SEQ_NUMBER and ITEM_DESCRIPTION — Sequence and descriptive text for the detail item.
• TRANSACTION_DATE — Date the underlying charge occurred.
• FOLIO_TYPE and EXT_FOLIO_TYPE — Folio classification codes, typically associated with lodging/travel transactions.
• LEG_NUMBER — Travel leg identifier, useful for multi-segment itineraries.
• DEPARTURE_DATE, DEPARTURE_CITY_CODE, ARRIVAL_DATE, ARRIVAL_CITY_CODE — Travel routing attributes.
• CARRIER_CODE, SERVICE_CLASS_CODE, FARE_BASIS_CODE — Airfare-specific attributes (carrier, class of service, fare basis).
• STOPOVER_CODE, DOMESTIC_FLAG, CONJUNCTION_TICKET_NUMBER — Additional travel/ticketing attributes.
• Standard WHO columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN for audit and concurrency control.

The mix of generic amount fields and travel-specific attributes indicates the table is designed to decompose travel and expense-type credit card charges into granular, reportable components.

Common Use Cases and Queries

Typical uses include credit card reconciliation, travel expense analysis, and integration with expense reporting. Query patterns generally join the detail table to its parent transaction table via TRX_ID.

• Detail retrieval for a transaction: SELECT d.trx_detail_id, d.item_description, d.transaction_amount, d.billed_amount FROM ap.ap_cc_trx_details d WHERE d.trx_id = :trx_id;
• Travel spend analysis: aggregate TRANSACTION_AMOUNT by CARRIER_CODE, SERVICE_CLASS_CODE, or origin/destination city codes.
• Reconciliation: compare TRANSACTION_AMOUNT to BILLED_AMOUNT to identify discrepancies between charged and billed amounts.
• Period reporting: filter by TRANSACTION_DATE for monthly credit card spend trending.

Because the table is child to AP_CREDIT_CARD_TRXNS_ALL, most reporting joins the two to combine transaction-header context (e.g., card holder, merchant) with detail-level attributes.

Related Objects

• AP_CREDIT_CARD_TRXNS_ALL — The parent table; joined on AP_CC_TRX_DETAILS.TRX_ID = AP_CREDIT_CARD_TRXNS_ALL.TRX_ID. This is the primary documented foreign-key relationship and the principal dependency.
• AP_CC_TRX_DETAILS_PK — Primary key constraint on TRX_DETAIL_ID.
• AP_CC_TRX_DETAILS_U1 — Unique index on TRX_DETAIL_ID.
• AP credit card transaction processing / Payables invoice workflows — Processes that consume detail records to build or validate payables invoices and expense lines.
• AP invoice and expense reporting views/APIs — Downstream reporting and integration interfaces that reference credit card transaction details.

The dominant relationship remains the TRX_ID link to AP_CREDIT_CARD_TRXNS_ALL; all other dependencies derive from that parent-child association.