Search Results diary_note_details




Overview
Explore in AI Chat

Overview

XTR_MATURITIES_V is a Treasury (XTR) reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its purpose is narrowly defined: it exposes cashflows belonging only to those date and amount type combinations that have been flagged as relevant to the Treasury maturity reports. The driving filter is the MATURITY_REPORT flag on XTR_DATE_AMOUNT_TYPES, which means the view does not return every cashflow recorded against a deal. Instead, it returns the subset that Treasury has designated for maturity analysis, giving reporting users a pre-filtered, denormalised result set without needing to join the Treasury deal, party, and reference tables themselves.

Because the view resolves deal numbers, counterparties, clients, deal types, statuses, and user-defined code descriptions into a single row per qualifying cashflow, it functions as a reporting and integration layer over the core Treasury cashflow model. It is typically consumed by maturity ladder reports, gap analysis, and downstream extracts rather than by transactional processing.

Underlying Base Objects

The view is defined over a primary cashflow source, XTR_DEAL_DATE_AMOUNTS_V, aliased as A, joined to a set of reference and descriptive objects. The documented base objects are XTR_AMOUNT_TYPES, XTR_DATE_AMOUNT_TYPES, XTR_DATE_TYPES, XTR_DEAL_DATE_AMOUNTS_V, XTR_DEAL_STATUSES, XTR_DEAL_SUBTYPES, XTR_DEAL_TYPES, XTR_PARTY_INFO, and the XTR_USER_ACCESS package.

The join to XTR_DATE_AMOUNT_TYPES (D) is the restrictive one, combining DEAL_TYPE, DATE_TYPE, and AMOUNT_TYPE while requiring MATURITY_REPORT = 'Y'. Outer joins to XTR_PARTY_INFO, aliased P and Q, resolve counterparty and client short names and allow cashflows to survive when a party record is absent. Inner joins to XTR_DEAL_TYPES, XTR_DEAL_SUBTYPES, XTR_AMOUNT_TYPES, XTR_DEAL_STATUSES, and XTR_DATE_TYPES supply the user-facing descriptions for deal type, subtype, amount type, status, and date type respectively. XTR_USER_ACCESS is referenced for access control rather than row-level joining.

Key Columns

Common Use Cases and Queries

The primary scenario is maturity reporting: listing all qualifying cashflows by date bucket for liquidity and funding analysis. A second scenario is counterparty exposure review grouped by client or counterparty. A third is audit or reconciliation, where the diary note and authorisation columns are inspected alongside amounts.

A typical query groups maturities by date and currency:

  • SELECT amount_date, currency, SUM(cashflow_amount) FROM xtr_maturities_v WHERE amount_date BETWEEN :p_from AND :p_to GROUP BY amount_date, currency ORDER BY amount_date;

Counterparty-level aggregation, useful for concentration review, follows the same pattern using CLIENT_NAME or CPARTY_NAME as the grouping key. To retrieve supplementary detail such as diary notes for a specific deal:

  • SELECT deal_number, transaction_number, amount_date, user_amount_type, cashflow_amount, diary_note_details FROM xtr_maturities_v WHERE deal_number = :p_deal_number;

Because the view already enforces the MATURITY_REPORT filter and resolves descriptive columns, queries remain short and consistent between 12.1.1 and 12.2.2. Access is governed through XTR_USER_ACCESS, so results reflect the security profile of the querying responsibility.