In the batch mode the multiple rows could be loaded into the database from the one EagleML message. In this mode the element warehouseTransaction should be contained several complex elements warehouseTrade. Data from every element will be loaded into the database row.
See the example of incoming EagleML message to load data in Batch Mode:
Child pages (Children Display) |
---|
Batch Key Element
When using the batch mode, the data from the complex elements warehouseTrade should contain the same set of of element’s values: Entity Id + Effective Date + Source Name. The set of values for grouping should be specified in the element warehouseTransaction/batchKey.
The format of Batch Key (warehouseTransaction/batchKey element): entityId^effectiveDate^sourceName
entityId – the element warehouseTransaction/warehouseTrade/entityId. It should be specified if it mapped from the EagleML message directly (in the warehouseTransaction/warehouseTrade/entityId). If the value of entityId is defined by the warehouseTransaction/warehouseTrade/xrefAccountId and warehouseTransaction/warehouseTrade/xrefAccountIdType elements, the first part of warehouseTransaction/batchKey could be any. The batch key will be updated by calculated entityId element.
effectiveDate – the element warehouseTransaction/warehouseTrade/effectiveDate. It should be specified in data format YYYYMMDD.
sourceName – the element warehouseTransaction/warehouseTrade/sourceName.
Examples of a valid Batch Key:
Code Block | ||
---|---|---|
| ||
<batchKey>COMPTST1^20140120^EAGLE PACE</batchKey> |
Code Block | ||
---|---|---|
| ||
<batchKey>entity^20140120^EAGLE PACE</batchKey> |
Insert/Update
The stored procedure for the batch mode supports only only the inserting data into the database.
...