PPR Export and Import (Parts Planning and Replenishment)
Important!
Before the functionalities described below can be used, the AGCO Purchase Order Import must be set up.
The AGCO MDI PPR Interface (AGCO Managed Dealer Inventory - Parts Planning and Replenishment) exports the purchase lines, sales lines, item data, and inventory data on a daily basis, taking into account various filter options.
The aim of this interface is to compare the purchase lines, sales lines and inventory data in such a way that a corresponding demand can be determined. AGCO provides a corresponding purchase requisition in its own portal, which can be modified and ultimately results in a purchase order from AGCO.
The data from the AGCO MDI portal is stored in the Azure Blob Storage so that this data can then be imported as a purchase order into TRASER DMS 365. This means that order lines do not need to be entered twice.
Both export and import are largely handled via job queue entries.
PPR Buffer Tables
During import and export, the data is temporarily stored in buffer tables, which are explained below:
| Buffer Table | Description |
|---|---|
| MDI PPR Stock Keeping Units Line Buffer | Export All lines that were transmitted to AGCO during the last export are listed in the stock keeping units line buffer (item data). This buffer table is intended to make it easier to filter for specific lines in order to resolve any discrepancies, as the CSV files that are exported to AGCO can only be accessed via Azure Blob Storage. |
| MDI PPR Inventory Line Buffer | Export All lines that were transmitted to AGCO during the last export are listed in the inventory line buffer. This buffer table is intended to make it easier to filter for specific lines in order to resolve any discrepancies, as the CSV files that are exported to AGCO can only be accessed via Azure Blob Storage. |
| MDI PPR Customer Order Line Buffer | Export All lines that were transmitted to AGCO during the last export are listed in the customer order line buffer. This buffer table is intended to make it easier to filter for specific lines in order to resolve any discrepancies, as the CSV files that are exported to AGCO can only be accessed via Azure Blob Storage. |
| MDI PPR Purchase Order Line Buffer | Export All lines that were transmitted to AGCO during the last export are listed in the purchase order line buffer. This buffer table is intended to make it easier to filter for specific lines in order to resolve any discrepancies, as the CSV files that are exported to AGCO can only be accessed via Azure Blob Storage. |
| MDI PPR PLO Imp. Buffer List | Import All lines that were transmitted during the last purchase order import from AGCO are listed in the purchase order line import buffer list. This buffer table is intended to make it easier to filter for specific lines in order to resolve any discrepancies, as the CSV files that are exported to AGCO can only be accessed via Azure Blob Storage. |
Importing Purchase Orders
Once the purchase requisition has been approved in the AGCO MDI portal, AGCO provides a CSV file in the Azure Blob Storage, which is processed by TRASER DMS 365. An open purchase order is automatically created from this CSV file.
Tip
Purchase orders can also be imported manually using the Actions > New Document Import AGCO Orders button.
The result of the import is a purchase order with the vendor that was defined in the MDI PPR Supplier Filter Entries table in the Mapping Setup FastTab from the PPR Interface Setup (vendor with selected Vendor for MDI Order checkbox).
The data that AGCO provides for the purchase orders is archived in the Azure Blob Storage archive directory (ArchiveFolder interface parameter). Re-processing files is possible at any time if the file is moved to the Azure Blob Storage import directory (ImportFolder interface parameter) and the import job queue is restarted.