Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
The EDS Load warehouseopenload is available as part of the EagleML modernization effort as a metadata driven interface. It uses dynamically generated SQL requests to load data based upon the incoming data. Only the populated fields are used to generate insert and update requests. The additional data models and database tables are supported for load and extract only via EDS interface. The incoming files are expected to have the elements aligned with the order of elements defined by the ontology. The default partition is supported with the initial implementation.
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
| Table of Contents |
|---|