Search Results load_status_code

Overview

XTR_DEALS_INTERFACE_V is a Treasury (XTR) module view owned by the APPS schema and defined over the XTR_DEALS_INTERFACE table. Oracle EBS documents the interface table as a staging structure designed to hold "as much common deal information as possible," allowing heterogeneous deal records — money market, FX, swap, and other Treasury instruments — to be loaded into a single, generalized column set. The view exposes that column set through a stable, read-only interface so that inbound load programs, validation routines, and integration reports can query staged deal data without coupling to the physical table layout.

The view is a pass-through projection of XTR_DEALS_INTERFACE columns; the additional base objects listed in the metadata (XTR_PARTIES_V, XTR_PARTY_INFO, XTR_USER_ACCESS) reflect dependent objects resolved during compilation rather than joined sources in the view text. In 12.1.1 and 12.2.2 the view is marked VALID, and it is typically consumed by the deal import/validation concurrent programs that populate the interface and subsequently transfer rows into the Treasury deal tables.

Underlying Base Objects

• XTR_DEALS_INTERFACE (SYNONYM) — the primary and only data source referenced in the view's SELECT list. All columns are qualified as XDI.*, confirming a single-table projection.
• XTR_PARTIES_V (VIEW), XTR_PARTY_INFO (SYNONYM), XTR_USER_ACCESS (PACKAGE) — documented dependencies that participate in the broader deal interface/validation flow, including counterparty resolution and user-level access checks applied during validation and transfer.

Because the view adds no joins or filters, row counts and column values match the base interface table exactly, subject to the querying user's privileges on APPS.

Key Columns

• EXTERNAL_DEAL_ID, INTERNAL_TICKET_NO — external and internal deal identifiers used for reconciliation and duplicate detection.
• DEAL_TYPE, DEAL_SUBTYPE, PRODUCT_TYPE, ACTION_CODE — classify the instrument and the action (new, amend, cancel) to be applied on transfer.
• LOAD_STATUS_CODE, STATUS_CODE, VALIDATION_FLAG — drive staging control; VALIDATION_FLAG and LOAD_STATUS_CODE indicate whether a row has passed validation and is eligible for import, which is the attribute most commonly searched for by users diagnosing failed loads.
• CPARTY_CODE, CPARTY_ACCOUNT_NO, PORTFOLIO_CODE, COMPANY_CODE, DEALER_CODE — counterparty, portfolio, entity, and dealer references.
• AMOUNT_A/B/C, RATE_A/B/C, DATE_A/B/C, NO_OF_DAYS, CURRENCY_A/B — generic numeric, rate, and date slots whose meaning depends on DEAL_TYPE.
• SETTLEMENT_FLAG, SETTLE_ACTION_REQD, BANK_CODE_FROM/TO, ROUNDING_TYPE, DAY_COUNT_TYPE, BASIS_TYPE, YEAR_CALC_TYPE — settlement and interest-basis attributes.
• ATTRIBUTE1..15, ATTRIBUTE_CATEGORY — the standard EBS descriptive flexfield segment set for deal-specific extensions.
• MIRROR_* columns — mirror deal linkage, portfolio, product, pricing model, and limit references.

Common Use Cases and Queries

The view is used to audit staged deals, troubleshoot validation failures, and reconcile inbound feeds before transfer. A typical check for unvalidated or failed rows:

• SELECT external_deal_id, deal_type, load_status_code, validation_flag FROM xtr_deals_interface_v WHERE validation_flag = 'N';
• SELECT cparty_code, portfolio_code, currency_a, amount_a FROM xtr_deals_interface_v WHERE load_status_code = 'ERROR';
• SELECT external_deal_id, deal_type, creation_date, created_by FROM xtr_deals_interface_v WHERE trunc(creation_date) = trunc(sysdate);

These queries support daily interface monitoring, duplicate detection by EXTERNAL_DEAL_ID, and pre-transfer completeness checks across the generic amount and date slots.