Results for “xtr_trans_validations_v”

34 results




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

Overview

XTR_TRANS_VALIDATIONS_V is a Treasury (XTR) module view owned by the APPS schema and classified as VALID. It is the primary data source behind the Transaction Validation form, which confirmation and operations staff use to review, authorize, and validate treasury transactions such as confirmations and rollovers before they are settled. The view presents a filtered, security-scoped result set rather than a raw table image: only non-cancelled confirmation records, only transactions the requesting user is authorized to act upon, and only those instrument type/sub-type/product combinations flagged as validation-authorized in Treasury setup.

Because the view embeds FND_GLOBAL.USER_ID and dealer-code lookups in its WHERE clause, its output is inherently user-dependent. Two users querying the same underlying data can legitimately receive different row sets. This design makes the view unsuitable as a bulk extraction source, but ideal for form-driven inquiry and for personalized reporting where row-level access control must mirror the application's own authority model.

Underlying Base Objects

The view's defining query selects from XTR_CONFIRMATION_DETAILS, aliased XD. The remaining objects appear in correlated sub-queries and joins that constrain the result set:

All base tables are accessed through APPS synonyms, consistent with standard EBS view construction.

Key Columns

The projection exposes the following columns, drawn principally from XTR_CONFIRMATION_DETAILS:

Common Use Cases and Queries

The view supports transaction validation inquiries, pending-confirmation worklists, and rollover confirmation review. A typical query lists validations awaiting action for the current user:

  • Filter by STATUS_CODE to isolate open versus validated confirmations.
  • Filter by DEAL_TYPE = 'ONC' to examine rollover transactions specifically, since the view branches its authorization logic for that type.
  • Join back to XTR_CONFIRMATION_DETAILS on TRANSACTION_NO and DEAL_NO for columns not projected.

Sample SQL:

SELECT deal_no, transaction_no, deal_type, status_code, currency, amount,
       confirmation_validated_on
  FROM apps.xtr_trans_validations_v
 WHERE status_code != 'CANCELLED'
   AND deal_type = 'ONC';

Because authorization predicates depend on FND_GLOBAL.USER_ID, ad hoc queries executed outside the EBS session (for example via a generic reporting login) may return no rows or an unexpected set. For scheduled reports, run the query under a session that initializes the correct user context.