About the Warehouse Position EDS Load

Owned by Nancy Cohn (Deactivated)
Last updated: Oct 23, 2024 by Kinga Huszno
1 min read

The EDS Load warehouseposition is available as part of EagleML modernization effort as a metadata driven interface. This change introduces 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.

For a CM example, see Warehouse Position EDS Load RTR Example. For a sample file with all available for load fields, see Warehouse Position EDS Load Example. 

The Warehouse Position EDS Load is available with February 2021 EagleML version or later.

Tables Affected

With the Warehouse Position EDS load, the interface uploads information into following tables:

  • HOLDINGDBO.POSITION

  • HOLDINGDBO.POSITION_DETAIL

  • HOLDINGDBO.POSITION_COST_DETAIL

  • HOLDINGDBO.POSITION_DETAIL_ANL_USER

  • HOLDINGDBO.POSITION_PLEDGE_DETAIL

  • HOLDINGDBO.POSITION_DETAIL_ANL

  • HOLDINGDBO.POSITION_DETAIL_ANL_EQ

  • HOLDINGDBO.POSITION_DETAIL_ANL_FI

  • HOLDINGDBO.POSITION_DETAIL_ANL_KRD

  • HOLDINGDBO.REAL_ESTATE_POSITION_DETAIL

  • HOLDINGDBO.POSITION_INCOME_DETAIL 

  • HOLDINGDBO.POSITION_COST_DETAIL_USER

Resolution Logic

For a successful load, the following minimal resolutions should be done:

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.