Search Results party_confo_file_name




Overview
Explore in AI Chat

Overview

XTR_CONFIRMATION_DETAILS_V is a reporting and inquiry view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the XTR – Treasury product family. Its purpose is to expose confirmation processing details for treasury deals, including the flow of outgoing and incoming confirmations between the organization and its counterparties. The view consolidates the attributes required to monitor whether a deal confirmation has been printed, transmitted, received, reviewed, validated, and re-printed, together with the responsible users and timestamps for each of those activities.

In the context of Oracle EBS 12.1.1 and 12.2.2, the view functions as a read-only presentation layer over the confirmation detail records maintained by the Treasury module. It is commonly consumed by Treasury inquiry forms, concurrent reporting programs, and downstream integration extracts. Because the view exposes a single, denormalized row per confirmation activity, it simplifies the construction of operational dashboards and audit reports. The column PARTY_CONFO_CHECKED_BY, which corresponds to the search term "party_confo_checked_by," records the user who reviewed the counterparty-side confirmation, making the view particularly valuable for tracking review accountability during the confirmation lifecycle.

Underlying Base Objects

According to documented ETRM 12.2.2 metadata, the view is defined over the object XTR_CONFIRMATION_DETAILS, which is referenced as a SYNONYM in the APPS schema. The view text is a direct projection of columns from that base object:

SELECT ... FROM XTR_CONFIRMATION_DETAILS

No joins, unions, or aggregations are present in the documented definition; the view inherits its filtering of confirmation records entirely from the base table. This means that the view reflects the base table one-to-one at the row level, with no derived columns other than the NVL expression applied to CONF_PARTY_CODE. This characteristic is important for performance tuning: predicates and indexing strategies applied to the base table remain effective, and no hidden transformations invalidate the execution plan. Row-level security, if configured on the underlying table through Treasury security profiles, remains in effect for the view.

Key Columns

Common Use Cases and Queries

A frequent requirement is to identify all counterparty confirmations reviewed by a specific user or still awaiting review. The following pattern supports audit and operational follow-up:

SELECT DEAL_NO, CPARTY_CODE, PARTY_CONFO_CHECKED, PARTY_CONFO_CHECKED_ON, PARTY_CONFO_CHECKED_BY
FROM APPS.XTR_CONFIRMATION_DETAILS_V
WHERE PARTY_CONFO_CHECKED_BY = :p_user
AND PARTY_CONFO_CHECKED = 'Y';

Other common scenarios include reconciling confirmations that were reprinted after initial generation, listing deals where the confirmation has not yet been validated, and producing extracts of confirmation status by counterparty for a given period. Because the view is a passthrough to XTR_CONFIRMATION_DETAILS, queries should filter on indexed base-table columns such as DEAL_NO, TRANSACTION_NO, or COMPANY_CODE to maintain acceptable response times in high-volume Treasury environments.