Results for “user_deal_type”

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

Overview

XTR_TY_SUB_PRD_COMBIN_V is a security-filtered Oracle EBS Treasury (XTR) view owned by the APPS schema. Its name reflects its purpose: it presents the combinations of Treasury deal types, deal subtypes, and product types that the currently logged-in user is authorized to work with. Rather than exposing all deal type/subtype/product combinations defined in the system, the view restricts the result set to those rows in XTR_AUTH_TYPE_SUBTYPE_PROD where the AUTHORISED flag is 'Y' and the authorized user matches the dealer code assigned to the session user. This makes it a key building block for row-level authorization in Treasury deal entry, inquiry, and reporting. The view is defined with SELECT DISTINCT, so each unique combination of deal type, deal subtype, and product type appears only once, even if multiple dealer code rows would otherwise satisfy the join.

Underlying Base Objects

The view is defined over five documented objects. XTR_AUTH_TYPE_SUBTYPE_PROD (referenced through a synonym) is the primary authorization table; it supplies DEAL_TYPE, DEAL_SUBTYPE, PRODUCT_TYPE, AUTHORISED, and USER_NAME. XTR_DEAL_TYPES and XTR_DEAL_SUBTYPES provide the user-facing descriptions, joined on DEAL_TYPE and, for the subtype, on DEAL_TYPE plus DEAL_SUBTYPE. XTR_DEALER_CODES maps the EBS application user to a dealer code, and the join to FND_GLOBAL.USER_ID (an FND package rather than a table) restricts the results to the dealer codes associated with the current session user. In a 12.1.1 or 12.2.2 environment all of these base objects reside in APPS and are normally accessed via synonyms; the view itself would typically be granted to Treasury responsibility users or consumed by forms and concurrent programs running under the APPS schema.

Key Columns

• DEAL_TYPE — the internal code for the Treasury deal type; joins to XTR_DEAL_TYPES.
• USER_DEAL_TYPE — the translated, user-facing name for the deal type (from XTR_DEAL_TYPES.USER_DEAL_TYPE).
• DEAL_SUBTYPE — the internal code for the deal subtype; joins to XTR_DEAL_SUBTYPES on both DEAL_TYPE and DEAL_SUBTYPE.
• USER_DEAL_SUBTYPE — the translated, user-facing name for the deal subtype (from XTR_DEAL_SUBTYPES.USER_DEAL_SUBTYPE).
• PRODUCT_TYPE — the Treasury product type associated with the authorized combination (e.g., the instrument or product classification).

Common Use Cases and Queries

This view is most often used to drive list-of-values (LOVs) and validation logic so that a user can only select deal types, subtypes, and products they are authorized to transact. A typical lookup for the current user:

SELECT DISTINCT deal_type, user_deal_type,
       deal_subtype, user_deal_subtype, product_type
FROM   apps.xtr_ty_sub_prd_combin_v
ORDER  BY user_deal_type, user_deal_subtype;

Because the view already applies the authorization filter internally, callers do not need to know the dealer code mapping — the WHERE clause effectively becomes "rows authorized for FND_GLOBAL.USER_ID." A common second pattern is filtering to a specific deal type when populating a dependent subtype or product LOV:

SELECT deal_subtype, user_deal_subtype, product_type
FROM   apps.xtr_ty_sub_prd_combin_v
WHERE  deal_type = :p_deal_type;

Integration and reporting scenarios include generating audit reports of authorized combinations per dealer, reconciling the AUTHORISED flag in XTR_AUTH_TYPE_SUBTYPE_PROD against user access, and feeding downstream Treasury processing that must respect the same authorization rules. Because access depends on FND_GLOBAL.USER_ID, any report or interface querying this view must run in a session where the correct application user context is established; running it as SYSADMIN or a background program without a user context will typically return no rows.