Results for “default_portfolio”

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

Overview

XTR_PORTFOLIOS_V is a Treasury (XTR) module view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents portfolio definition data used by Oracle Treasury for counterparty, deal, and settlement processing. A portfolio in Treasury represents a logical grouping of deals, positions, and accounting treatment configured for a company or legal entity within a specific company code. This view exposes the operational attributes that govern how Treasury identifies default portfolios, applies principal treatment, manages external party relationships, and drives interest and brokerage frequency cycles.

Because it is a simple projection over the XTR_PORTFOLIOS base table, XTR_PORTFOLIOS_V provides a read-oriented interface suitable for reporting, integration extracts, and custom concurrent programs that must reference portfolio configuration without directly querying the underlying table. The view is documented as VALID, indicating that its definition compiles cleanly against the referenced base object in the ETRM (Enterprise Treasury Management) data model, and it is surfaced in ETRM 12.2.2 metadata with the SYNONYM XTR_PORTFOLIOS as its sole referenced base object.

Underlying Base Objects

The view is defined exclusively over XTR_PORTFOLIOS, exposed in the APPS schema through the synonym of the same name. The view text is a direct SELECT of the columns listed below, with no joins, aggregations, filters, or transformations:

• COMPANY_CODE – identifies the company/legal entity context for the portfolio.
• PORTFOLIO – the portfolio identifier (primary business key).
• NAME – descriptive portfolio name.
• DEFAULT_PORTFOLIO – flag indicating the default portfolio for the company code.
• AS_PRINCIPAL – indicates principal-based deal processing behavior.
• EXTERNAL_PORTFOLIO – flags portfolios representing external counterparties.
• EXTERNAL_PARTY – external party or counterparty reference.
• INTEREST_FREQ, BROKERAGE_FREQ – frequency codes for interest and brokerage accrual/settlement cycles.
• LAST_INTEREST_SETTLEMENT, LAST_BROKERAGE_SETTLEMENT – most recent settlement dates.
• PHYSICAL_PORTFOLIO_ACCT – physical portfolio account reference.
• CMF_YN – Cash Management flag indicator.
• EXTERNAL_DEFAULT_PORTFOLIO – default flag for external portfolios.
• Audit columns: UPDATED_BY, UPDATED_ON, AUDIT_INDICATOR, CREATED_BY, CREATED_ON.

Key Columns

The JOIN between COMPANY_CODE and PORTFOLIO uniquely identifies a portfolio record. DEFAULT_PORTFOLIO and EXTERNAL_DEFAULT_PORTFOLIO are the two flags most frequently used to resolve defaulting logic in deal entry and settlement workflows. AS_PRINCIPAL and CMF_YN influence Treasury's accounting and cash management behavior, while INTEREST_FREQ and BROKERAGE_FREQ, together with LAST_INTEREST_SETTLEMENT and LAST_BROKERAGE_SETTLEMENT, drive periodic processing. Because the view is pass-through, all columns retain the datatypes and semantics of the underlying XTR_PORTFOLIOS table.

Common Use Cases and Queries

Typical scenarios include identifying the default portfolio for a company code, extracting external counterparty portfolios, and validating settlement frequency configuration before running interest or brokerage processes.

• Retrieve all portfolios for a company code:

SELECT company_code, portfolio, name, default_portfolio
FROM apps.xtr_portfolios_v
WHERE company_code = :p_company_code;

• Find the default portfolio for a company:

SELECT portfolio, name
FROM apps.xtr_portfolios_v
WHERE company_code = :p_company_code
AND default_portfolio = 'Y';

• List external portfolios with counterparties:

SELECT portfolio, name, external_party, external_default_portfolio
FROM apps.xtr_portfolios_v
WHERE external_portfolio = 'Y';