Search Results brokerage_amount




Overview
Explore in AI Chat

Overview

APPS.XTR_RTMM_ELIGIBLE_DEALS_V is a reporting view within the Oracle E-Business Suite Treasury module (ETRM), specifically associated with the Risk and Treasury Management functionality. Its name and structure indicate that it exposes deals eligible for revaluation processing — the "RTMM" prefix correlates with the RTMM deal type used in the underlying filter, and "ELIGIBLE" reflects that the view returns only those deals meeting the revaluation criteria defined in the view's WHERE clause. The view is owned by the APPS schema and serves as a denormalized, flattened projection of deal data joined with company-level parameter configuration, allowing downstream programs, reports, and integrations to consume eligible deal records without directly querying the base transaction tables.

For users searching on "brokerage_amount," this view is directly relevant: BROKERAGE_AMOUNT is one of the columns explicitly selected, mapped straight through from the XTR_DEALS table as BROKERAGE_AMOUNT BROKERAGE_AMOUNT. It is available alongside the full complement of deal attributes the view exposes.

Underlying Base Objects

The view is defined over two documented base objects, both referenced as synonyms in the APPS schema:

  • XTR_DEALS (SYNONYM) — aliased as D in the view definition; supplies the core deal record, including deal number, type, subtype, dates, amounts, and the BROKERAGE_AMOUNT column.
  • XTR_COMPANY_PARAMETERS (SYNONYM) — aliased as CP; supplies company-level configuration used both to filter the results and to derive the ELIGIBLE_DATE value.

The join is drawn on COMPANY_CODE across both objects. The view is restricted to records where D.DEAL_TYPE = 'RTMM', D.STATUS_CODE is not 'CANCELLED', D.PRICING_MODEL is not 'NO_REVAL', and CP.PARAMETER_CODE = 'ACCNT_TSDTM'. This confirms the view's purpose as a filtered set of live, revaluable RTMM deals for companies configured with the ACCNT_TSDTM parameter.

Key Columns

The view exposes a substantial column list. Notable columns include:

Common Use Cases and Queries

Typical uses include feeding revaluation engines, validating which RTMM deals will participate in a revaluation run, and auditing brokerage and premium amounts on eligible deals. A simple brokerage-oriented query is:

SELECT DEAL_NO, COMPANY_CODE, BROKERAGE_AMOUNT, ELIGIBLE_DATE, STATUS_CODE FROM APPS.XTR_RTMM_ELIGIBLE_DEALS_V WHERE BROKERAGE_AMOUNT IS NOT NULL;

To review eligibility timing by company and portfolio:

SELECT COMPANY_CODE, PORTFOLIO_CODE, DEAL_NO, ELIGIBLE_DATE, PRICING_MODEL FROM APPS.XTR_RTMM_ELIGIBLE_DEALS_V ORDER BY COMPANY_CODE, ELIGIBLE_DATE;

Because the view already enforces the RTMM, non-cancelled, and non-NO_REVAL restrictions, consumers should not expect cancelled deals or deals with NO_REVAL pricing models to appear. All access should be performed through the APPS synonym, and the view should be treated as read-only for reporting and integration purposes.