Search Results adjust_principal




Overview

APPS.XTR_TMM_SUMMARY_V is a reporting view within the Oracle E-Business Suite Treasury Management module (ETRM) that consolidates rollover transaction activity for the deal type 'RTMM' (Rollover Treasury Money Market). It presents a unified summary of principal flows, interest amounts, adjustments, and settlement balances across rollover life cycles, allowing treasury analysts and sub-ledger accountants to reconcile money market positions without querying the underlying transaction and amount-detail tables directly.

The view is defined as a UNION ALL of two branches, distinguished by an ORDER_COLUMN literal of 'A' and 'B'. Branch 'A' draws from the rollover transactions view joined to amount types, deal statuses, and amount actions, and is oriented toward principal actions driven by user-defined action codes. Branch 'B' focuses on settlement and deduction activity, deriving the REFERENCE value as 'ADJUSTMENT' or 'DEDUCTION' depending on whether a principal-and-interest amount was actually received. This design places the view squarely in ETRM reporting and reconciliation workflows, where it exposes a denormalized, deal-centric summary suitable for concurrent program output, BI Publisher reports, and integration extracts.

Underlying Base Objects

The documented base objects include XTR_ROLLOVER_TRANSACTIONS_V, XTR_AMOUNT_TYPES, XTR_DEAL_STATUSES, XTR_AMOUNT_ACTIONS, XTR_DEAL_DATE_AMOUNTS_V, and the XTR_USER_ACCESS package.

  • XTR_ROLLOVER_TRANSACTIONS_V — the primary driver for both UNION branches, supplying deal number, transaction number, dates, principal action, balances, interest accumulations, and status.
  • XTR_AMOUNT_TYPES — joined on DEAL_TYPE = 'RTMM' and AMOUNT_TYPE = NVL(PRINCIPAL_AMOUNT_TYPE,'PRINFLW') to resolve the AMOUNT_NAME and USER_AMOUNT_TYPE.
  • XTR_DEAL_STATUSES — provides USER_STATUS_CODE through the DEAL_TYPE and STATUS_CODE join.
  • XTR_AMOUNT_ACTIONS — supplies USER_ACTION_CODE by matching DEAL_TYPE, amount type, and PRINCIPAL_ACTION = ACTION_CODE; this join is present only in branch 'A'.
  • XTR_DEAL_DATE_AMOUNTS_V — referenced in the view definition, supporting derived date/amount values.
  • XTR_USER_ACCESS — an ETRM security package used for access control filtering in treasury reporting contexts.

Key Columns

  • ORDER_COLUMN — literal 'A' or 'B' identifying which UNION branch produced the row.
  • DEAL_NOS / TRANS_NOS — deal number and rollover transaction number.
  • SETTLE_DATESTART_DATE in branch 'A'; NVL(SETTLE_DATE, MATURITY_DATE) in branch 'B'.
  • REFERENCE — PRINCIPAL_ACTION for branch 'A'; 'ADJUSTMENT' or 'DEDUCTION' for branch 'B'.
  • AMOUNT / ADJUST_PRINCIPAL / ADJUST_INTEREST — signed principal and interest adjustments.
  • PRIN_DECRSE — the principal decrease calculated as the negative of (PI_AMOUNT_RECEIVED minus accumulated and current interest), returned only when the difference is positive; otherwise 0. This column is the specific object of the "prin_decrse" search.
  • NOS_DAYS / INTEREST_CFWD / BALANCE_CFWD / RATE — day count, carried-forward interest, carried-forward balance, and applied interest rate.
  • AMOUNT_TYPE / USER_AMOUNT_TYPE — amount classification from XTR_AMOUNT_TYPES.
  • STATUS_CODE / USER_STATUS_CODE — internal and user-facing status.

Common Use Cases and Queries

Typical usage includes principal reduction reporting, interest carry-forward analysis, and status-based reconciliation of rollover deals.

  • Principal decrease report: SELECT DEAL_NOS, TRANS_NOS, PRIN_DECRSE FROM APPS.XTR_TMM_SUMMARY_V WHERE PRIN_DECRSE > 0;
  • Adjustment versus deduction split: SELECT REFERENCE, SUM(AMOUNT) FROM APPS.XTR_TMM_SUMMARY_V WHERE ORDER_COLUMN='B' GROUP BY REFERENCE;
  • Status reconciliation: SELECT USER_STATUS_CODE, COUNT(*) FROM APPS.XTR_TMM_SUMMARY_V GROUP BY USER_STATUS_CODE;
  • Interest carry-forward extract for a date range, filtered on SETTLE_DATE and ordered by ORDER_COLUMN.

Because treasury security is enforced through XTR_USER_ACCESS, report queries are normally executed under the ETRM responsibility so that deal-level access controls apply.