Results for “port_name”

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

Overview

XTR_IRS_ACTUALS_V is an APPS-owned database view within the Oracle E-Business Suite Treasury (XTR) module. It exposes interest rate sensitivity (IRS) actuals data used for treasury analysis, reporting, and downstream integration. The view is registered as VALID and is available in both EBS 12.1.1 and 12.2.2 environments.

The view presents a frozen, denormalized snapshot of interest rate risk measurement results at the portfolio, company, and currency level. It combines calculated amounts, weighted-average figures, coverage metrics, and policy limits into a single queryable structure. Because the object is a view rather than a table, no data is physically stored within it; consumers query it as a read-only logical layer over the actuals data. This makes it suitable for BI Publisher reports, Discoverer workbooks, custom concurrent programs, and ad hoc SQL used by treasury analysts.

The presence of the FUND_INVEST column is directly relevant to the user's search term. This column identifies the funding or investment classification associated with each actuals record, allowing segregation of results by the nature of the underlying treasury position.

Underlying Base Objects

The documented view metadata identifies a single referenced base object: XTR_IRS_ACTUALS, accessed via a synonym. The view text confirms this relationship with a simple projection:

• SELECT ... FROM XTR_IRS_ACTUALS
• No joins, unions, or aggregations are present in the documented view text.
• The view therefore inherits the row granularity, filtering behavior, and security characteristics of the synonym it references.

Because the definition is a straight projection, the view serves primarily as a stable, named access point. Any change to the base table structure that removes or renames a projected column will invalidate the view. The UNIQUE_REF_NUMBER column suggests the base table carries a unique identifier per actuals record, which is preserved unchanged in the view.

Key Columns

The view exposes approximately fifty columns. The most significant are summarized below.

• UNIQUE_REF_NUMBER — Unique identifier for each actuals record; useful as a join key.
• COMPANY_CODE / COMPANY_NAME — Legal entity or company context for the measurement.
• CURRENCY — Currency in which amounts are denominated.
• PORTFOLIO_CODE / PORT_NAME — Treasury portfolio attribution.
• FUND_INVEST — Funding versus investment classification of the position.
• INC_IG — Inclusion indicator used to control whether the row participates in sensitivity aggregation.
• AMOUNT_UNIT — Unit of measure for the reported amounts.
• FROM_DATE / TO_DATE — Effective date range of the actuals record.
• PF_AMT, PX_AMT, PT_AMT — Principal-related interest rate sensitivity amounts, with corresponding _DAYS and weighted _WAMT variants.
• SF_AMT / SX_AMT / ST_AMT / STW_AMT / ST_DAYS — Secondary or supplementary sensitivity amount series.
• PFA_AMT, PXA_AMT, PTA_AMT, SA_AMT and their _DAYS counterparts — Averaged sensitivity measures across the measurement horizon.
• PF_COVER, PX_COVER, PT_COVER, S_COVER — Coverage ratios applied to the respective sensitivity buckets.
• ACTUAL_FIXED — Portion of the position that is fixed-rate.
• FLOATING_LESS — Floating-rate exposure adjustment.
• POLICY_MAX / POLICY_MIN, VARIANCE_MAX / VARIANCE_MIN, MAX_WAMT / MIN_WAMT, MAX_AMT / MIN_AMT — Policy thresholds and permitted variance bands against which actual results are compared.
• DAY_ADJUST — Day-count adjustment factor applied in the calculation.
• CREATED_ON / CREATED_BY — Standard audit columns recorded when the actuals row was generated.

Common Use Cases and Queries

The view is typically consumed for policy compliance reporting, interest rate risk dashboards, and reconciliation between actual and policy bounds. The FUND_INVEST column supports filtering by funding or investment activity, which matches the user's search intent. The following examples illustrate practical access patterns.

• List all actuals for a given company and currency:

SELECT unique_ref_number, company_code, currency, portfolio_code, fund_invest, from_date, to_date, actual_fixed
FROM apps.xtr_irs_actuals_v
WHERE company_code = :p_company
  AND currency = :p_currency;

• Identify records breaching policy maximums:

SELECT unique_ref_number, portfolio_code, pt_amt, policy_max, variance_max
FROM apps.xtr_irs_actuals_v
WHERE pt_amt > policy_max
  OR pt_amt < policy_min;

• Segment results by funding versus investment using the searched column:

SELECT fund_invest, currency, SUM(pt_amt) total_pt_amt
FROM apps.xtr_irs_actuals_v
WHERE from_date >= :p_start_date
GROUP BY fund_invest, currency;

Because all logic resides in the base table, common tuning guidance applies: restrict on indexed base columns such as COMPANY_CODE, CURRENCY, PORTFOLIO_CODE, and the date range columns, and avoid wrapping the projected columns in functions where indexes on the base table can be used.