Results for “debit_amount”

50+ results




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

Overview

XTR_IMPORT_TRAILER_DETAILS is a Treasury (XTR) module table in Oracle E-Business Suite, owned by the XTR schema and valid in both 12.1.1 and 12.2.2. It stores summary information describing the outcome of successful bank statement transfers processed through the Treasury bank statement import framework. Each row represents a trailer record that accompanies a completed statement import, capturing aggregated control totals — amounts, currency, transaction counts — that reconciliation and cash management processes use to validate the completeness of an imported statement file before downstream reconciliation begins.

From a Data Vault modeling perspective, the mined foreign key structure suggests this object is satellite-leaning: it hangs off a parent bank account usage entity and carries descriptive, point-in-time measurement attributes (amounts, counts, dates) rather than acting as an independent hub. It should be treated as a descriptive satellite of the bank account usage hub, keyed by a business-oriented import reference, rather than as a standalone transactional hub.

Key Information Stored

The table contains 11 documented columns. The most significant are:

  • IMPORT_REFERENCE — the primary key column (XTR_IMPORT_TRAILER_DETAILS_PK). It is the business key that uniquely identifies each import run and is the principal join path to reconciliation records.
  • BANK_ACCT_USE_ID — foreign key to CE_BANK_ACCT_USES_ALL, identifying the bank account usage against which the statement was imported.
  • ACCOUNT_NUMBER — the bank account number associated with the imported statement.
  • AMOUNT — the total monetary amount reported for the import.
  • CREDIT_AMOUNT and DEBIT_AMOUNT — the credit and debit control totals used to balance the statement load.
  • CURRENCY — the currency in which the amounts are denominated.
  • NUMBER_OF_TRANSACTIONS — the count of statement lines successfully transferred, a key reconciliation control figure.
  • SOURCE — the originating source system or channel of the import.
  • VALUE_DATE — the effective/value date of the summarized balances.
  • CREATION_DATE — the audit timestamp marking when the trailer record was written.

IMPORT_REFERENCE is the documented primary key (a business-key candidate rather than a generated surrogate); BANK_ACCT_USE_ID functions as the foreign-key link to the bank account model.

Common Use Cases and Queries

Typical uses include verifying that a bank statement import posted complete control totals, auditing import history for a given bank account, and reconciling Treasury imports against Cash Management reconciliation records. A common query joins the trailer to reconciliation data:

  • SELECT t.import_reference, t.account_number, t.currency, t.amount, t.number_of_transactions FROM xtr.xtr_import_trailer_details t WHERE t.bank_acct_use_id = :acct_use_id AND t.value_date BETWEEN :from_date AND :to_date;
  • Balancing check: compare CREDIT_AMOUNT minus DEBIT_AMOUNT against AMOUNT and confirm NUMBER_OF_TRANSACTIONS matches the detail lines loaded.
  • Reporting on import volumes by SOURCE, CURRENCY, and VALUE_DATE for cash positioning dashboards.

Related Objects

  • CE_BANK_ACCT_USES_ALL — parent bank account usage; joined on XTR_IMPORT_TRAILER_DETAILS.BANK_ACCT_USE_ID.
  • XTR_PAY_REC_RECONCILIATION — references this table via IMPORT_REFERENCE, linking import trailers to payment/receipt reconciliation records.
  • XTR_IMPORT_TRAILER_DETAILS_PK — the primary key constraint defining uniqueness on IMPORT_REFERENCE.
  • Related Cash Management statement and reconciliation objects (CE_STATEMENT_HEADERS, CE_STATEMENT_LINES) that consume imported statement data.
  • Treasury import/conversion programs that populate the trailer record upon successful statement transfer.