Results for “xtr_data_feed_codes_v”

16 results




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

Overview

XTR_DATA_FEED_CODES_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the XTR (Treasury) product family. The view presents market data feed code definitions maintained within Treasury, exposing the reference identifiers and pricing attributes that link external market data sources to instruments tracked by the application. Its status is documented as VALID in the ETRM repository, and it is available in both the 12.1.1 and 12.2.2 release lines.

Functionally, the view serves as a read-only projection of the underlying data feed code repository. Rather than introducing new business logic, transformation, or joins, it re-presents the base table's columns so that reporting tools, concurrent programs, and integration extracts can consume the data feed definitions without directly referencing the base table. This pattern is common in Oracle EBS, where a view acts as a stable, release-controlled interface for downstream consumers.

Underlying Base Objects

The documented metadata identifies a single referenced base object: XTR_DATA_FEED_CODES, accessed through a SYNONYM. The view is defined as a straight SELECT over that table, projecting the following columns without filtering, aggregation, or joins: RIC_CODE, PRICE_DESCRIPTION, LAST_FEED_UPDATE, LAST_ARCHIVE_TIME, SOURCE, REF_CCY_CODE_A, REF_CCY_CODE_B, MOVEMENT_INDICATOR, SELECTED_FOR_MONITORING, WHOLESALE_RETAIL_RATE, BID_PRICE, ASK_PRICE, RATE_ALERT_EXISTS, REF_NUMBER, and EXTERNAL_REF_CODE.

Because no WHERE clause is applied, the view exposes the complete set of rows held in XTR_DATA_FEED_CODES. Any row-level security, if required, must be applied by the calling report, extract, or query rather than by the view itself. The one-to-one column mapping means the view and the base table remain structurally aligned; changes to the base table's definition are reflected in the view.

Key Columns

RIC_CODE stores the Reuters Instrument Code or equivalent market data identifier used to subscribe to a specific price series. It is the principal key by which external feeds are recognized.

PRICE_DESCRIPTION provides the human-readable description of the price or rate being tracked. This is the column most often matched when users search for "price_description," since it labels each feed code with a business-friendly name.

LAST_FEED_UPDATE and LAST_ARCHIVE_TIME record the timestamps of the most recent feed refresh and archival action, supporting monitoring of feed latency and data currency.

SOURCE identifies the market data provider or feed origin, while REF_CCY_CODE_A and REF_CCY_CODE_B hold the reference currency codes associated with the quoted rate, typically forming a currency pair.

MOVEMENT_INDICATOR signals the direction or nature of rate movement, and SELECTED_FOR_MONITORING flags whether the code is actively watched. WHOLESALE_RETAIL_RATE distinguishes the rate category, and BID_PRICE and ASK_PRICE carry the quoted two-way prices.

RATE_ALERT_EXISTS indicates whether an alert condition is currently raised. REF_NUMBER and EXTERNAL_REF_CODE provide internal and external cross-reference identifiers for reconciliation with upstream systems.

Common Use Cases and Queries

Typical usage includes feed monitoring dashboards, audit extracts of configured market data codes, and integration queries that map external RIC codes to Treasury instruments. A common lookup returns the descriptive label for a known code:

  • SELECT RIC_CODE, PRICE_DESCRIPTION, SOURCE, BID_PRICE, ASK_PRICE FROM APPS.XTR_DATA_FEED_CODES_V WHERE RIC_CODE = :p_ric_code;
  • SELECT RIC_CODE, PRICE_DESCRIPTION, LAST_FEED_UPDATE FROM APPS.XTR_DATA_FEED_CODES_V WHERE SELECTED_FOR_MONITORING = 'Y' ORDER BY LAST_FEED_UPDATE DESC;
  • SELECT RIC_CODE, PRICE_DESCRIPTION, RATE_ALERT_EXISTS FROM APPS.XTR_DATA_FEED_CODES_V WHERE RATE_ALERT_EXISTS = 'Y';

Because the view is unfiltered, queries should always include selective predicates such as RIC_CODE, SOURCE, or SELECTED_FOR_MONITORING to limit result sets in production environments.