Results for “merchant_reference”

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

Overview

APBV_CREDIT_CARD_TRXNS is an Oracle E-Business Suite business view owned by the APPS schema within the Oracle Payables (AP) product family. It exposes credit card transaction data captured during expense processing and is classified in the ETRM repository as a VALID view at both 12.1.1 and 12.2.2. The view presents a consolidated, read-oriented projection of corporate credit card activity, including transaction-level, billed, posted, merchant, and industry-specific detail. Its primary role is to serve as the reporting and integration surface for credit card feed data that has been staged, validated, and ultimately formatted for downstream expense workflows.

Because the view is not a table, it carries no independent storage. All attribute values are inherited at query time from its underlying base object. This design allows external systems, custom reports, and Oracle-provided components to consume credit card transaction facts through a stable, named view rather than querying the base table directly, insulating consumers from physical schema changes.

Underlying Base Objects

Per the documented ETRM view metadata, APBV_CREDIT_CARD_TRXNS is defined over a single referenced base object: AP_CREDIT_CARD_TRXNS_ALL, which appears in the metadata as a SYNONYM resolving to the underlying transactional table. The view text selects from this object using the alias ACCTA, mapping each column of the base table in order through an explicit column list.

This one-to-one projection means every row and column visible in APBV_CREDIT_CARD_TRXNS corresponds directly to a row and column in the base object. No joins, aggregations, filters, or derived expressions are applied. Consequently, row counts are identical, and the view does not supplement the base data with lookups to suppliers, employees, or accounting distributions.

Key Columns

• TRX_ID / CARD_ID / CARD_PROGRAM_ID — Identifiers for the transaction, the card, and the card program governing the feed.
• TRANSACTION_DATE, TRANSACTION_AMOUNT, DEBIT_FLAG, REFERENCE_NUMBER — Core transaction facts as reported by the card issuer.
• BILLED_DATE, BILLED_AMOUNT, BILLED_DECIMAL, BILLED_CURRENCY_CODE — The billing cycle date and amount as presented on the issuer statement, in the billed currency.
• POSTED_DATE, POSTED_AMOUNT, POSTED_DECIMAL, POSTED_CURRENCY_CODE — The posting date and amount recognized internally, which may differ from the billed figures.
• CURRENCY_CONVERSION_RATE, CURRENCY_CONVERSION_EXPONENT — Conversion factors applied between transaction and functional currencies.
• VALIDATE_CODE — Validation status for the staged transaction.
• MERCHANT_NAME1, MERCHANT_NAME2, MERCHANT_CITY, MERCHANT_COUNTRY, MERCHANT_REFERENCE, MERCHANT_TAX_ID — Merchant identification and location data.
• MIS_INDUSTRY_CODE, SIC_CODE — Industry classification used for spend analysis.
• TOTAL_TAX, LOCAL_TAX, NATIONAL_TAX, OTHER_TAX — Tax components at the transaction level.
• FOLIO_TYPE, ATM_* columns — Specialized attributes for lodging folios and ATM cash advances.
• RESTAURANT_*, CAR_RENTAL_*, CAR_*, HOTEL_* columns — Line-item detail captured for restaurant, rental car, and hotel expenses.
• ORG_ID — Operating unit identifier, the Multi-Org partitioning key.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY — Standard audit columns.

Common Use Cases and Queries

Typical usage includes reconciling issuer statements against posted amounts, reporting billed versus posted discrepancies, analyzing merchant spend, and feeding external expense systems. Because the user search term referenced billed_date, a frequent scenario is identifying transactions by billing cycle:

• Filtering by billing period to match issuer statements: SELECT TRX_ID, REFERENCE_NUMBER, BILLED_DATE, BILLED_AMOUNT, BILLED_CURRENCY_CODE FROM APPS.APBV_CREDIT_CARD_TRXNS WHERE BILLED_DATE BETWEEN :start_date AND :end_date AND ORG_ID = :org_id;
• Comparing billed and posted values: SELECT TRX_ID, BILLED_AMOUNT, POSTED_AMOUNT, BILLED_CURRENCY_CODE, POSTED_CURRENCY_CODE FROM APPS.APBV_CREDIT_CARD_TRXNS WHERE NVL(BILLED_AMOUNT,0) <> NVL(POSTED_AMOUNT,0);
• Merchant-level spend analysis grouped by city or country.
• Validating staged transactions prior to expense report generation using VALIDATE_CODE.

All queries should be constrained by ORG_ID to respect Multi-Org access, and callers should remember that the view performs no filtering or transformation of base data.