Results for “xtr_deal_types_v”

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

Overview

XTR_DEAL_TYPES_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 exposes deal type configuration data used by Oracle Treasury to govern how financial deals and instruments are created, processed, and accounted for. A deal type acts as a template that drives downstream behavior: which date rules apply, how amounts are validated, whether accrual and amortisation are performed, and which accounting method is followed.

The view is a thin projection over the XTR_DEAL_TYPES synonym and contains no joins, filters, or aggregation logic. Its principal role is to present an application-facing, read-consistent interface to the deal type definition table so that reports, concurrent programs, and integration extracts can reference a stable object name without depending directly on the base synonym. Because the view is declared VALID in the data dictionary, it can be relied upon for query and reporting purposes within the EBS instance. The column FX_MM_EXP_FLAG, which is the term the user searched for, is one of the configuration flags surfaced by this view and is used to control exposure handling for foreign exchange and money market deal types.

Underlying Base Objects

The view is defined with a single-referenced-object dependency on XTR_DEAL_TYPES, which is a SYNONYM in the APPS schema. The SELECT list projects every documented column from that base object without transformation, joining, or filtering. The view text is:

• SELECT DEAL_TYPE, USER_DEAL_TYPE, NAME, FX_MM_EXP_FLAG, AUTHORISED, FROM_DATE_TYPE, TO_DATE_TYPE, AMOUNT_TYPE, ACCRUE_AMORTISE, METHOD, SEEDED_DESCRIPTION, UPDATED_BY FROM XTR_DEAL_TYPES

Because the relationship is one-to-one and unfiltered, row counts and row identity between XTR_DEAL_TYPES_V and XTR_DEAL_TYPES are identical. Each row in the view corresponds to exactly one deal type definition. From a maintenance perspective, the view inherits the security, grants, and indexing characteristics of the underlying synonym and base table; it adds no independent storage. The dependency documented in ETRM 12.2.2 metadata confirms the synonym as the sole referenced object, meaning there are no hidden outer joins to lookup or translation tables within the view definition itself.

Key Columns

• DEAL_TYPE — The internal identifier or code for the deal type. This is the primary key value used to associate deals with their configuration.
• USER_DEAL_TYPE — The user-defined deal type classification, allowing installations to distinguish customised variants of seeded deal types.
• NAME — The descriptive name of the deal type presented to users in Treasury forms and reports.
• FX_MM_EXP_FLAG — Indicates whether the deal type participates in FX and money market exposure processing. This is the column most relevant to searches on exposure configuration.
• AUTHORISED — Flag controlling whether the deal type is authorised for use in transaction entry and processing.
• FROM_DATE_TYPE / TO_DATE_TYPE — Define the date-basis rules used for the start and end dates of deals created under this type.
• AMOUNT_TYPE — Specifies the amount handling or validation basis applied to the deal type.
• ACCRUE_AMORTISE — Determines whether accrual and amortisation processing is enabled for deals of this type.
• METHOD — The accounting or valuation method associated with the deal type.
• SEEDED_DESCRIPTION — The seeded descriptive text shipped by Oracle for the deal type.
• UPDATED_BY — Audit column identifying the user who last modified the record.

Common Use Cases and Queries

Typical usage involves validating deal type configuration, auditing exposure flags, and feeding downstream extracts. A common query lists all authorised deal types and their exposure and accrual settings:

• SELECT deal_type, name, fx_mm_exp_flag, authorised, accrue_amortise FROM xtr_deal_types_v WHERE authorised = 'Y';
• SELECT deal_type, user_deal_type, name FROM xtr_deal_types_v WHERE fx_mm_exp_flag = 'Y';
• SELECT deal_type, method, amount_type FROM xtr_deal_types_v WHERE accrue_amortise = 'Y';

Integration and reconciliation routines frequently select the entire view to populate staging tables or to compare configuration across environments before and after a patch. Reporting against the view is preferred over direct access to the base table because the view name is the documented interface exposed to the APPS schema.