Search Results deal_type_error

Overview

APPS.XTR_DEALS_INTERFACE_V is a public view in the Oracle E-Business Suite Treasury (ETRM) module. As documented in the ETRM metadata, it is described as "A public view which may be useful for custom reporting or other data requirements." The view is created in association with the base table XTR_DEALS_INTERFACE, a staging table designed to hold as much common deal information as possible. In Oracle EBS 12.1.1 and 12.2.2, this interface table serves as the inbound landing zone for deals imported into Treasury from external systems, spreadsheets, or other feeder applications prior to validation and transfer into the core deal tables. The view therefore exposes a reporting-friendly projection of the interface records, allowing technical consultants and report developers to inspect the state of imported deals without querying the underlying table directly.

Underlying Base Objects

The documented view metadata lists four referenced base objects:

• XTR_DEALS_INTERFACE (SYNONYM) — the primary source object; the interface (staging) table that stores common deal information.
• XTR_PARTIES_V (VIEW) — a party-related view, likely used to resolve counterparty or party attributes.
• XTR_PARTY_INFO (SYNONYM) — a synonym referencing party information used for enrichment or validation.
• XTR_USER_ACCESS (PACKAGE) — a Treasury security package that enforces user access restrictions, consistent with Treasury's data-security model.

Because XTR_DEALS_INTERFACE is the anchor object, the view inherits the WHO audit columns and the interface-specific control columns from the base table, while joining to party and access objects to present a consolidated, secured dataset.

Key Columns

• EXTERNAL_DEAL_ID (VARCHAR2 240) — the externally supplied unique primary identifier for each deal. This is the column most commonly implicated when a user searches for duplicate_deal_id.
• DEAL_TYPE — code identifying the deal or instrument type.
• LOAD_STATUS_CODE (VARCHAR2 30) — transfer status of the deal record. Values include NEW or null (new deal), UPDATED, ERROR, SUBMIT, DEAL_TYPE_ERROR (unsupported deal type), and DUPLICATE_DEAL_ID (duplicate imported deal). This column is central to diagnosing import failures.
• BROKERAGE_CODE and BROKERAGE_CURRENCY — brokerage reference and its currency.
• ACCOUNT_NO_A (20), ACCOUNT_NO_B (80) — first and second account numbers.
• CLIENT_CODE, COMPANY_CODE, CPARTY_CODE — client, company, and counterparty identifiers. CPARTY_CODE also stores THIRDPARTY_CODE for EXP deals.
• CPARTY_ACCOUNT_NO (20), CPARTY_REF (80) — counterparty bank account and reference.
• CURRENCY_A, CURRENCY_B (15) — the deal's two currency fields, supporting FX-style deal structures.
• DEALER_CODE (10), DEAL_LINKING_CODE, DEAL_SUBTYPE, COMMENTS (255) — dealer, deal grouping, subcategory, and internal comments.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.

Common Use Cases and Queries

The most frequent reporting need is identifying records that failed import. The DUPLICATE_DEAL_ID status is raised when the loader detects that EXTERNAL_DEAL_ID already exists, indicating a duplicate imported deal. A typical diagnostic query is:

• SELECT external_deal_id, deal_type, load_status_code, creation_date FROM apps.xtr_deals_interface_v WHERE load_status_code = 'DUPLICATE_DEAL_ID';
• SELECT external_deal_id, deal_type, load_status_code FROM apps.xtr_deals_interface_v WHERE load_status_code IN ('ERROR','DEAL_TYPE_ERROR');
• SELECT external_deal_id, COUNT(*) FROM apps.xtr_deals_interface_v GROUP BY external_deal_id HAVING COUNT(*) > 1; — to detect duplicate external identifiers within the interface itself.
• Standard WHO filtering, such as WHERE creation_date >= TRUNC(SYSDATE), to review today's inbound deals.

Note that access is enforced through XTR_USER_ACCESS, so results returned may be filtered according to the responsibility's Treasury security profile. The view is best used for read-only reconciliation, error triage, and audit reporting rather than for direct data maintenance.