...
| Expand | ||||||
|---|---|---|---|---|---|---|
| ||||||
bind
|
...
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/warehouseCloseLot/effectiveDate – mapped to TRADESDBO.DISPOSAL_LOTS.EFFECTIVE_DATE
- Entity Id: warehouseTransaction/warehouseCloseLot/entityId (or warehouseTransaction/warehouseCloseLot/xrefAccountId and warehouseTransaction/warehouseCloseLot/xrefAccountIdType) – mapped to TRADESDBO.DISPOSAL_LOTS.ENTITY_ID
- Source Name: warehouseTransaction/warehouseCloseLot/sourceName
- Number of Lots: warehouseTransaction/warehouseCloseLot/numberofLots – mapped to TRADESDBO.DISPOSAL_LOTS.NBR_OF_LOTS
- Master Ticket Number: warehouseTransaction/warehouseCloseLot/masterTicketNumber – mapped to TRADESDBO.DISPOSAL_LOTS.MASTER_TICKET_NUMBER
- Security Identifiers: to resolve the Security Alias (see the section 'Security Resolution Logic'), Security Alias mapped to TRADESDBO.DISPOSAL_LOTS.SECURITY_ALIAS
...
<securityAlias> should not be specified in the incoming EagleML message. Refer to Security Resolution for Warehouse Objects
Entity Resolution Logic
Refer to Entity Resolution for Warehouse Objects
...