Data Download process data is downloaded from the ERP and exposed to Arkieva.
The Data Download business process loads the ERP data needed in the Supply Planning process, then the data is transformed to the format needed in Arkieva.
Figure 1. Process Overview
The Download Data business process contains 3 steps:
Figure 2. Process Overview – Download Data
Implementation is a process used by the Arkieva Connector, which generates an SSIS package to execute the process. The package is then scheduled to be executed each day.
Figure 3. Process Overview – Example of the Download Data Configuration process
This step loads the data from ERP into the staging area of the DataMart. The staging step is generated based on templates, which are then extended with additional tables and/or fields. Each template groups table information regarding a specific information object in ERP. The following templates are selected:
In addition to the selected templates the following information objects are also downloaded from ERP:
In the Arkieva Connector the download of each information object is grouped into a separate ETL package, which are then executed from within the staging step.
Address data is not available in a standard template, so this information is added by manual configuration in the Arkieva Connector.
Batch data is a standard template. Batch data is downloaded incrementally to limit the amount of data extracted from ERP. The initial download date is set to 2001-01-01, and the increment is set to 2 weeks.
Bill of Material data is a standard template. Bill of Material data is downloaded incrementally to limit the amount of data extracted from ERP. The initial download date is set to 2001-01-01, and the increment is set to 2 weeks.
Customer data is a standard template. Customer data is downloaded with full table downloads.
Delivery Orders data is a standard template. The below table contains the standard fields in the template. Additional fields are added.
The main tables of Delivery Orders data are downloaded incrementally to limit the amount of data extracted from ERP. The initial download date is set to 2017-01-01, and the increment is set to 2 weeks. The status tables are download by using Table Join queries.
Material Document data is a standard template. The below table contains the standard fields in the template. No additional fields are added. Material Document data is downloaded incrementally to limit the amount of data extracted from ERP. The initial download date is set to 2017-01-01, and the increment is set to 2 weeks.
Material Master data is a standard template. The below table contains the standard fields in the template. Additional fields are added. The tables of Material Master data are downloaded with full table downloads.
Planned Orders data is a standard template. Planned Orders data is downloaded with full table downloads.
Plant data is a standard template. Plant data is downloaded with full table downloads.
Process Orders data is a standard template. The below table contains the standard fields in the template. No additional fields are added. The main tables of Process Orders data are downloaded with full table downloads. The status tables is download by using a Table Join query.
Product Hierarchy data is a standard template. Product Hierarchy data is downloaded with full table downloads.
Purchase Orders data is a standard template. The tables of Purchase Orders data are downloaded with full table downloads. All tables have a where clause to limit the amount of data downloaded each time.
Purchase Requisition data is a standard template. Purchase Requisition data is downloaded with full table downloads.
Sales Orders data is a standard template. The main tables of Sales Orders data are downloaded incrementally to limit the amount of data extracted from ERP. The initial download date is set to 2017-01-01, and the increment is set to 2 weeks.
The tables are downloaded with full table downloads. Additionally the table has a where clause to limit the amount of data downloaded each time. The status tables are download by using Table Join queries.
Text data is not available in a standard template, so this information is added by manual configuration in the Arkieva Connector. The below table contains the selected tables and fields that are added manually. Both have a where clause to limit the amount of data downloaded each time.
Vendor data is a standard template. Vendor data is downloaded with full table downloads.
This step transforms and prepares the previously loaded data inside the DataMart.
Functionally the following information is prepared and used afterwards by the Supply Planning business process:
The following picture illustrates the dependencies between the loaded master data and the resulting prepared and enriched information.
Figure 5 ETL Overview – Transform Data inside DataMart
For each information object at least, the following steps are used:

The following picture puts the above steps on top of the layered architecture of the DataMart, as described in the Software Architecture Document.

The material information available in ERP is enriched with the address information. Only material information of a specific Material Type is selected. Also, some other country-specific filters are applied.
Currently only one specific data quality screening has been defined on DataStore[Country]1.ItemMaster.
In a next step palletization data is transformed. Only palletization data of a specific Warehouse and Plant is selected.
Currently only one specific data quality screening has been defined on DataStore[Country]1.ItemMaster.
In a next step palletization data is transformed. Only palletization data of a specific Warehouse and Plant is selected.
The bill of material information available in ERP is enriched with the address information. Only BOM Usage equal to ‘1’ and BOM Statuses equal to ‘01’ are selected.
The plant information available in ERP is enriched with the address information. No further filtering is applied.
The storage location information available in ERP is enriched with the plant information. No further filtering is applied.
The vendor information available in ERP is enriched with the address information. Only vendors of a specific Vendor Account Group are selected.
The customer information available in ERP is enriched with the address information. No further filtering is applied on the available customer information.
The customer sales information available in ERP is enriched with the customer information and the plant information. Only customer sales information of a specific Sales Organization and Distribution Channel are selected.

