Updated: 15.04.2025

Setup

This section describes the setup of the TRASER DMS 365 x AGCO interface. It is required to import configurations created for AGCO products.

AGCO Configuration Import

Configurator Interface Setup

To perform the AGCO configurator setup, please proceed as follows:

  • Open the Interface Card page via the quick search (ALT+Q), and open the AGCOCONFIGIMP entry.
    For more information about the Interface Card page, please check this site.
  • In the General FastTab:
    • optional Customize the Description to make it easier to identify, if needed.
  • The Authorization FastTab can be ignored for now.
  • In the Parameters FastTab, enter the following information in the Value field to prepare the interface:
    • DefaultCostType: Select the cost mapping to be used to import the costs from the configuration into the system. Maybe you need to create the cost mapping code first.
    • DefaultDiscountType: Select the discount mapping to be used to import the discount from the configuration into the system. Maybe you need to create the discount mapping code first.

When all requirements are met (green Parameter values in the Parameters FastTab), enable the interface via the Activate Interface button in the menu bar.

Manufacturer Config Mapping

To finalize the cost and discount type setup, the values must be mapped as follows:

  • Open the Manufacturer Config Mapping table via the quick search (ALT+Q), and create new entries for costs and discounts:
    • In the Manufacturer Code column, select the configurator manufacturer.
    • In the Addition Type column, select Cost for costs and Purchase for discounts.
    • In the Code column, enter a unique code, e.g.: AGCOCOST for costs and AGCODISCOUNT for discounts.
    • In the Business Central Code column select the relevant calculation type, e.g.: FREIGHT for costs and DISCOUNT for discounts.

The costs will now be mapped to the Costs > Cost Type column and the discounts to the Purchase Discounts > Discount type column of forecasts with the loaded configuration.

Configurator Setup

To perform the configurator setup, please proceed as follows:

  • Open the Configurator List table via the quick search (ALT+Q), and open the entry of the configurator manufacturer.
  • In the General FastTab:
    • In the Interface Type field, select AGCOCONFIGIMP.
    • Leave the Manufacturer field empty as there are several possible manufacturers. The selection is made at the import of a configuration file (see Loading configurations).
    • In the Vendor No. field, select the default manufacturer vendor for AGCO configurations.
  • Activate the interface via the Activate button in the menu bar.

Tip

If you do not select a default value Vendor No. field, it has to be manually selected for each configurator import.

You can now load manufacturer configurations as described in the Loading configurations section.

AGCO Purchase Order Import

PPR Interface Setup

To perform the PPR (Parts Planning and Replenishment) setup for AGCO MDI (Managed Dealer Inventory), please proceed as follows:

  • Open the Interface Card page via the quick search (ALT+Q), and open the AGCOMDIPPR entry.
    For more information about the Interface Card page, please check this site.
  • In the General FastTab:
    • optional Customize the Description to make it easier to identify, if needed.
  • The Authorization FastTab can be ignored for now.
  • In the Parameters FastTab, enter the following information in the Value field to prepare the interface:
    • ArchiveFolder: Define the Azure Blob Storage folder for the archive.
    • AzureContainerName: Define the Azure Blob Storage container for MDI.
    • AzureSharedAccessKey: Define the shared access key of above defined Azure Blob Storage account.
      The value is encrypted when being entered.
    • AzureStorageAccount: Define the Azure Blob Storage account used for MDI.
    • BlobFileName: Define the Blob file name to be searched for during import.
    • CsvSeparator: Define the separator for CSV files.
    • DealerName: Define the AGCO dealer account to be used for reconciliation.
    • DecimalSeparator: Define the decimal separator used for decimal values during import.
    • DefaultBinCode: Define the bin code in the purchase order lines.
    • DefaultCurrencyCode: Define the currency with which the purchase order is to be created.
    • DefaultLocationCode: Define the location in the purchase order lines.
    • DefaultManufacturer: Define the manufacturer which is required for the vendor item number search.
    • DefaultPurchaseCode: Define the purchase type code when the purchase order is created via the interface.
    • ExportFolder: Define the Azure Blob Storage folder for the export.
    • ImportFolder: Define the Azure Blob Storage folder for the import.
    • PostingDateFormula: Define which sales invoice lines and purchase invoice lines have to be delivered for AGCO, so that the lines can be set to "CLOSED" status at AGCO.
    • PrefixCustomerOrderLines: Define the prefix for customer order line files.
    • PrefixInventoryUnits: Define the prefix for inventory unit files.
    • PrefixPurchaseOrderLines: Define the prefix for purchase order line files.
    • PrefixStockKeepingUnits: Define the prefix for stock keeping unit files.
  • In the Mapping Setup FastTab, fill all relevant objects with the currently required values. When the table is filled, select the Completed checkbox:
    • MDI PPR Item Cat. Filter: Enter all item categories for which sales lines, purchase lines, item data, and inventory data should be sent to AGCO during PPR export. Only these items and item categories are considered for export.
      It is possible to use the asterisk (*) as a wildcard character.
    • MDI PPR Locations: Enter all locations for which sales lines, purchase lines, item data, and inventory data should be sent to AGCO during PPR export. Only these locations are considered for export.
    • MDI PPR Manufacturer Filter: Enter all manufacturers for which sales lines, purchase lines, item data, and inventory data should be sent to AGCO during PPR export. Only these manufacturers are considered for export.
    • MDI PPR Supplier Filter Entries: Enter all vendors for which sales lines, purchase lines, item data, and inventory data should be sent to AGCO during PPR export. Only these suppliers are considered for export.
      Select the Vendor for MDI Order checkbox for the vendor to be used for purchase order creation.
      (Only one vendor can be selected!)

When all requirements are met (green Parameter values in the Parameters FastTab), enable the interface via the Activate Interface button in the menu bar.

Job Queue Setup

For proper processing of PPR Export and Import files, 2 job queue entries must be created as described in the following subsections:

MDI PPR Import Job Queue

This job queue is used to automatically import the PPR Import CSV file from AGCO MDI. The file is downloaded to the Azure Blob Storage (see ImportFolder parameter setting in the PPR Interface Setup section), and its content is copied to the PPR Buffer Tables. Afterwards, a purchase order is created based on the AGCO values.

The job queue entry is automatically created during the AGCO MDI PPR Interface setup, so it is not necessary to create it manually. When activating the AGCO MDI PPR Interface, a notification is displayed from where the job queue could be opened directly, if necessary.

In case the job queue was changed or reset, please follow below instructions to recreate the recommended settings:

  • Open the Job Queue Entries page in John Deere DBS 365 using the search (ALT+Q).
  • Click on the New button to create a new job queue entry.
  • In the General FastTab of the Job Queue Entry Card, do the following:
    • In the Object Type to Run field, select the Codeunit value.
    • In the Object ID to Run field, select the 70251265 value.
    • Optional In the Description field, enter a unique job queue description, if needed, e.g., AGCO MDI PPR Import.
    • Optional In the Earliest Start Date/Time field, enter the date and time the job queue should run the next time. If no value is selected, the job queue will run as soon as Status = Ready.
  • In the Recurrence FastTab of the Job Queue Entry Card, do the following:
    • Activate the toggle switches for all weekdays.
    • In the Starting Time field, select a time shortly before the usual business hours, so that the file import and processing is done when starting.
      Recommended value: 04:00:00 (04:00:00 AM).
    • In the Ending Time field, select a time after the usual business hours, so that no traffic is generated if it is not needed.
      Recommended value: 20:00:00 (08:00:00 PM)
    • In the No. of Minutes between Runs field, enter a value which suits your processes best. We recommend a value between 15 and 60.

The job queue entry is finished and has Status = On Hold.

MDI PPR Export Job Queue

This job queue is used to automatically export Parts Planning and Replenishment data collected from different purchase and sales documents. The export CSV file is sent to AGCO MDI for processing via the Azure Blob Storage (see ExportFolder parameter setting in the PPR Interface Setup section).

The job queue entry is automatically created during the AGCO MDI PPR Interface setup, so it is not necessary to create it manually. When activating the AGCO MDI PPR Interface, a notification is displayed from where the job queue could be opened directly, if necessary.

In case the job queue was changed or reset, please follow below instructions to recreate the recommended settings:

  • Open the Job Queue Entries page in TRASER DMS 365 using the search (ALT+Q).
  • Click on the New button to create a new job queue entry.
  • In the General FastTab of the Job Queue Entry Card, do the following:
    • In the Object Type to Run field, select the Codeunit value.
    • In the Object ID to Run field, select the 70251266 value.
    • Optional In the Description field, enter a unique job queue description, if needed, e.g., AGCO MDI PPR Export.
    • Optional In the Earliest Start Date/Time field, enter the date and time the job queue should run the next time. If no value is selected, the job queue will run as soon as Status = Ready.
  • In the Recurrence FastTab of the Job Queue Entry Card, do the following:
    • Activate the toggle switches for all weekdays.
    • In the Starting Time field, select a time after the usual business hours, as the PPR data is not changed anymore on the working day.
      Recommended value: 22:00:00 (10:00:00 PM).
    • Leave the Ending Time field empty as the job queue is intended to run only once per day.
    • Leave the No. of Minutes between Runs field empty as the job queue is intended to run only once per day.

The job queue entry is finished and has Status = On Hold.

You can now automatically export sales and purchase order lines and then import purchase requisitions from AGCO MDI as described in the PPR Export and Import section.