Page Comparison

The EDS Load exchangeprice is available as part of the EagleML modernization effort as a metadata driven interface. Exchange Price EDS in-flow and out-flow interfaces are supported. 

The Exchange Price EDS Load and Extract are available with the March 2021 EagleML version or later.

Tables Affected

The Exchange Price EDS resource utilizes the following table: 

SECURITYDBO.PRICE_EXCHANGE

Also, the in-flow interface updates the table, RULESDBO.PRICE_STATUS, for a specific price if the record already exists and the price is different than the price existing in the table.

Resolution Logic 

For a successful load, the following minimal resolutions should be done: 

• Security resolution
• Source name resolution
• Effective date check

Exchange Price In-Flow Interface

The exchangeprice resource in-flow interface, the exchangePrice EDS EDS exchangePrice resource, utilizes the same stored procedures as the MC exchangePrice object, ESTAR.INS_UPD_PRICE_EXCHANGE, for loading the main record
and PACE_MASTERDBO.PRICING_PACE.PRICE_UPLOAD for the update status of a specific price.

The Insert and Update methods are supported for the in-flow interface with the following limitations:

• priceExchangeCode is required in the incoming message.
• The extended update option is currently not supported for compatibility within all v17.R2.x versions.

The EDS load requires incoming data files to be valid by Eagle ML XSD validation (fields order should be correct). Incorrect fields are expected to have the elements aligned with the order of elements defined by the ontology or EagleML XSD. Incorrect order will lead to missing column values in the DB.

For a CM example, see Exchange Price EDS Load RTR Example. 

Exchange Price Out-Flow Interface

For an extract RTR example, see Exchange Price EDS Extract RTR Example.