Warehouse Close Lot - Batch Mode of Data Loading

In batch mode multiple rows can be loaded into the database by one EagleML message. In this mode the element warehouseTransaction can contain several warehouseCloseLot complex elements. The data from each element will be loaded into a separate database row.

Batch Key Element

The group of complex elements (so-called 'batch') is given a specific set of values - a batch key (warehouseTransaction/batchKeyelement).

For WarehouseCloseLot it is Entity Id, Effective Date and Source Name formatted as entityId^effectiveDate^sourceName

• entityId – the element warehouseTransaction/warehouseCloseLot/entityId. Should be specified if it mapped from the EagleML message directly (in the warehouseTransaction/warehouseCloseLot/entityId). If the value of entityId is defined by the warehouseTransaction/warehouseCloseLot/xrefAccountId and warehouseTransaction/warehouseCloseLot/xrefAccountIdType elements, the first part of warehouseTransaction/batchKey could be any. The batch key will be updated with the entityId calculated from xref Ids.

• effectiveDate – the element warehouseTransaction/warehouseCloseLot/effectiveDate. Should be specified in DATE format: YYYYMMDD.

• sourceName – the element warehouseTransaction/warehouseCloseLot/sourceName.

Examples of correct WarehouseCloseLot batch key:

Insert/Update

The stored procedure for batch mode supports only inserting data into the database.

To update a database row please use single row mode.