Search Results misc_credit




Overview
Explore in AI Chat

Overview

APPS.XTR_BIS_CASHFLOWS_V is a Treasury (ETRM) reporting view in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents a consolidated, presentation-ready feed of Treasury cash flows by unioning three distinct data sources: cash-flow rows sourced from XTR_CASHFLOWS_V, deal date/amount rows derived from XTR_DEAL_DATE_AMOUNTS (restricted to DEAL_TYPE = 'CA'), and intra-statement lines from CE_INTRA_STMT_LINES joined to CE_INTRA_STMT_HEADERS. A defining characteristic is that it returns only rows with a transaction date on or after the current system date (ca.TRX_DATE >= trunc(SYSDATE)), making it a forward-looking cash-flow view rather than a historical ledger.

The view carries a "BIS" prefix, indicating it is part of the Business Intelligence / reporting layer of ETRM, intended for exposure to BI Publisher reports, dashboards, and downstream integration. It exposes deal number, deal type and subtype, transaction rate, status, currency, transaction date, amount, bank, company, counterparty, and client attributes in a uniform column structure across all three contributing legs.

Underlying Base Objects

The view is defined over a documented set of Treasury and Cash Management synonyms and views, including XTR_CASHFLOWS_V, XTR_DEAL_DATE_AMOUNTS, XTR_DEAL_TYPES, XTR_DEAL_SUBTYPES, XTR_AMOUNT_TYPES, XTR_BANK_ACCOUNTS, XTR_PARTIES_V, XTR_PARTY_INFO, CE_BANK_ACCOUNTS, CE_INTRA_STMT_HEADERS, CE_INTRA_STMT_LINES, CE_LOOKUPS, GL_LEDGER_LE_V, HR_OPERATING_UNITS, FND_LOOKUPS, FND_GLOBAL and XTR_USER_ACCESS. The first leg joins XTR_CASHFLOWS_V to XTR_PARTIES_V on COMPANY_CODE = PARTY_CODE. The second leg joins XTR_DEAL_DATE_AMOUNTS to XTR_DEAL_TYPES, XTR_DEAL_SUBTYPES, XTR_AMOUNT_TYPES, XTR_PARTIES_V and XTR_BANK_ACCOUNTS to resolve user-facing deal/amount type descriptions and bank/account details. The third leg resolves intra-day bank statement lines into Treasury receipt/payment semantics using the statement header and a DECODE mapping over intra.TRX_TYPE. This design allows the view to combine Treasury deal transactions with bank statement activity in a single result set.

Key Columns

Common Use Cases and Queries

The view is commonly used to drive Treasury cash-flow forecasting, liquidity reporting and BI Publisher extracts where only future-dated flows are of interest. Because it normalises Treasury and intra-day bank statement data into one column structure, it is well suited to consolidated position reports and reconciliation dashboards.

Typical query for MIS_CREDIT-related receipts:

  • SELECT DEAL_NUMBER, DEAL_SUBTYPE, CURRENCY_CODE, TRX_DATE, AMOUNT FROM APPS.XTR_BIS_CASHFLOWS_V WHERE DEAL_SUBTYPE = 'RECEIPT' ORDER BY TRX_DATE;
  • SELECT COMPANY_CODE, CURRENCY_CODE, SUM(AMOUNT) FROM APPS.XTR_BIS_CASHFLOWS_V WHERE TRX_DATE BETWEEN :from_date AND :to_date GROUP BY COMPANY_CODE, CURRENCY_CODE;

The 'MISC_CREDIT' token appears in the third union leg, where intra-statement transaction types are decoded—'MISC_CREDIT' maps to 'RECEIPT'—so searches for misc_credit resolve to receipt-type rows within intra-day statement cash flows. Note that the documented excerpt shows the third leg's decode only partially, so the full mapping of all TRX_TYPE values should be confirmed against the actual view text in the instance.