...
The following elements are required in the EagleML message: Effective Date, Entity Id (or Entity Identifiers), Source Name, Lot Number, identifiers for to resolve Security Alias.
- Effective Date: warehouseTransaction/warehouseTrade/effectiveDate – mapped to TRADESDBO.TRADE.EFFECTIVE_DATE
- Entity Id: warehouseTransaction/warehouseTrade/entityId (or warehouseTransaction/warehouseTrade/xrefAccountId and warehouseTransaction/warehouseTrade/xrefAccountIdType) – mapped to TRADESDBO.TRADE.ENTITY_ID
- Source Name: warehouseTransaction/warehouseTrade/sourceName
- Lot Number: warehouseTransaction/warehouseTrade/lotNumber – mapped to TRADESDBO.TRADE.LOT_NUMBER
- Master Ticket Number: warehouseTransaction/warehouseTrade/masterTicketNumber – mapped to TRADESDBO.TRADE.MASTER_TICKET_NUMBER
- Security Identifiers for resolve the Security Alias (see the section 'Security Resolution Logic'), Security Alias mapped to TRADESDBO.TRADE.SECURITY_ALIAS
...
<securityAlias> should not be specified in the incoming EagleML message.
...
| title | More details about Security Resolution for Warehouse Objects |
|---|
...
Read more on Security Resolution - Warehouse Objects
Entity Resolution Logic
...
| title | More details about Entity Resolution for Warehouse Objects |
|---|
...
You will find more details on Entity Resolution for Warehouse Objects
Modes of Data Loading
The Warehouse Trade inbound interface has 2 modes for loading data into the DB table:
...