For a CM example, see Warehouse Open Lot EDS Load RTR Example. For a sample file with all available for load fields, see Warehouse Open Lot EDS Load Example.
The Warehouse Position EDS Load is available with February 2021 EagleML version or later.
Tables Affected
With the Warehouse Open Lot EDS load, the interface uploads information into following tables:
HOLDINGDBO.LOT_LEVEL_POSITION
HOLDINGDBO.POSITION_COST_LOT
HOLDINGDBO.REAL_ESTATE_POSITION_LOT
HOLDINGDBO.POSITION_INCOME_LOT
HOLDINGDBO.POSITION_COST_LOT_USER
Resolution Logic
For a successful load, the following minimal resolutions should be done:
Entity Resolution. For details, see Entity Resolution for Warehouse Objects.
Security Resolution. For details, see Security Resolution - Warehouse Objects.
Source Name Resolution.
Effective Date Check. Use the correct date format and cannot be empty,
Update Source. Update source is a required field for load.
EDS load requires that incoming data files are valid by Eagle ML XSD validation (fields order should be correct). Incorrect fields order leads to missing column values in the DB.
In order to improve loading time, the load occurs via Dynamically generated SQL requests that involve only populated fields/tables from the incoming data file.
Control Message Setup
For a CM example, see DRAFT Warehouse Open Lot EDS Load RTR Example.
For a sample file with all available for load fields, see DRAFT Warehouse Open Lot EDS Load RTR Example.
On this page
toc