Search Results user_deal_type




Overview
Explore in AI Chat

Overview

APPS.XTR_HEDGE_DEAL_TYPES_V is a reporting and integration view within the Oracle E-Business Suite Treasury (ETRM) module. It exposes the set of deal types that may be applied to hedge transactions, presenting them through a consolidated list that combines the deal types configured in the Treasury deal-type setup with a specific lookup value drawn from the Oracle Application Object Library. The view is owned by the APPS schema and is available in both EBS 12.1.1 and 12.2.2.

Rather than storing data itself, the view acts as a read-only projection that unifies two sources into a single, consistently shaped result set. This makes it suitable for LOV (list of values) definitions, concurrent program parameters, discoverer reports, and inbound or outbound interface logic that needs to validate or display a hedge deal type. Because it includes the user-facing user_deal_type description alongside the internal code, it is frequently the object referenced when a user searches for "user_deal_type" in the context of Treasury hedges.

Underlying Base Objects

The view is defined by a UNION of two SELECT statements. The first branch selects from XTR_DEAL_TYPES_V, itself a Treasury view over the deal-type definitions, projecting the columns DEAL_TYPE, USER_DEAL_TYPE, NAME, and AUTHORISED. The second branch selects from FND_LOOKUPS, the Oracle Application Object Library lookup view, restricting the result to LOOKUP_TYPE = 'XTR_HEDGE_MISC' and LOOKUP_CODE = 'HEDGE'.

The documented base objects referenced by the view are FND_GLOBAL (PACKAGE), FND_LOOKUPS (VIEW), and XTR_DEAL_TYPES_V (VIEW). FND_GLOBAL is the standard EBS package that supplies session context such as the current user, responsibility, and application, and is typically relied upon by the security predicates applied through FND_LOOKUPS and related Treasury views. The union ensures that the standard hedge deal types are always represented, even where the underlying Treasury configuration is incomplete.

Key Columns

  • DEAL_TYPE — The internal code identifying the deal type. From XTR_DEAL_TYPES_V this is the deal type code; from FND_LOOKUPS it is the LOOKUP_CODE, which for the second branch is the literal value 'HEDGE'.
  • USER_DEAL_TYPE — The user-facing description of the deal type. From XTR_DEAL_TYPES_V this is the display value; from FND_LOOKUPS it is the MEANING column. This is the column most often queried by users searching on "user_deal_type".
  • NAME — A descriptive name for the deal type. In the FND_LOOKUPS branch this is populated from the DESCRIPTION column.
  • AUTHORISED — An enabled/authorised indicator. In the XTR_DEAL_TYPES_V branch it reflects the authorised status of the deal type; in the FND_LOOKUPS branch it is drawn from the ENABLED_FLAG of the lookup, so that only enabled lookup values are surfaced.

The four columns form a uniform structure regardless of which branch produced the row, so consumers can query the view without branching logic.

Common Use Cases and Queries

The primary use is to populate selection lists for hedge deal types and to validate a deal type supplied through an interface. A typical query retrieves all available deal types:

  • SELECT deal_type, user_deal_type FROM apps.xtr_hedge_deal_types_v ORDER BY user_deal_type;
  • SELECT user_deal_type FROM apps.xtr_hedge_deal_types_v WHERE deal_type = :p_deal_type;
  • SELECT deal_type FROM apps.xtr_hedge_deal_types_v WHERE authorised = 'Y';

Because the second union branch hard-codes the lookup type 'XTR_HEDGE_MISC' and lookup code 'HEDGE', the view guarantees a consistent hedge entry alongside any configured Treasury deal types. Integrations and reports should therefore treat the view as the authoritative, read-only source for hedge deal-type codes and their user-facing descriptions, and should not attempt to insert or update through it.