Download processes

Basic data download - MHS630MI/635MI/640MI

Item, alias and supplier downloads deliver basic data from M3 to the warehouse system. This only needs to be performed if that basic data has been changed. All basic data must be changed in M3 and downloaded to the external system. No basic data changes from the external system can be processed by the interface. Basic data should only be maintained by one system.

See function programs for generating data:

• MHS630 generates the data in the MHITMA (Item master download data) file, and MHS630MI is used to retrieve the data.
• MHS635 generates the data in the MHIPOP (Alias number download data) file, and MHS635MI is used to retrieve the data.
• MHS640 generates the data in the MHDMAS, MHDVEN, and MHDADR (Supplier download data) files, and MHS640MI is used to retrieve the data.

You can run these functions manually by using selection criteria, or you can schedule them. When you run the download manually by using the selection programs, the M3 basic data records that have been deleted are not captured; only new and changed records are included. The manual routine provides a refresh or a snapshot view based on the selections.

You can use the Change date field to schedule the download data.

An MBM initiator is created when records in M3 have been changed and must be retrieved by the external system. The initiator for alias and supplier downloads is available only in Java.

Expected receipts download - MHS800MI

Expected receipts include Purchase Order Receipts, Distribution or Requisition Order Receipts, Customer Order Returns, and Manufacturing Order Receipts. The purpose of downloading receipts is to provide the external system visibility of inbound transactions and to enable the external system to use the information from the issued receipts.

MHS800, MHS801, and MHS803 are M3 functions where the expected receipts retrieve and download files from MHEXRH, MHEXRD, and MHFRNS. The data added to these files are created by the function programs, MMS910 (Planning overview) and OIS390 (Customer return) if the warehouse parameter 'Planned receipts' on (MMS005/H) is set to 1. MHS800MI is used to list the expected receipts.

Package details for Inbound Distribution Orders are saved in MHFRNS and are displayed in 'Package Details Download. Display' (MHS803).

The rule of thumb is that any change that affects the material plan in M3 also updates the expected receipts files. As a result, only changes at the line level are captured.

However, some changes are filtered so that only the relevant data is downloaded. The command field (CMND) follows the updates in the material plan (MITPLO) and is used when the external system builds logic. The Purchase order (PO) transaction event table shows how the command field reacts to different events. The table describes normal events, and exceptions can occur depending on the M3 configuration. The download flag (DOWN) is always set to zero (0) after M3 writes or updates a record. The external system can set the flag to one (1) to indicate that it has read the record.

This table shows all Purchase Order (PO) transaction events:

This table shows all Distribution Order (DO) transaction events:

This table shows all Manufacturing Order (MO) transaction events:

This table shows all Customer Order (CO) transaction events:

Expected receipts create MBM initiators

This function creates MBM initiators for the selected expected receipt records so that the expected receipts can be downloaded to Infor Enterprise Collaborator.

You can use the MBM initiator to trigger the process that requests updated records through the API programs. The initiator contains the information that is required to use the API transactions.

MBM initiators are created when picking lists are printed (MHPICL, MWS435), when item information is downloaded (MHITMA, MHS630), when alias information is downloaded (MHIPOP, MHS635), when supplier information is downloaded (MHDMAS, MHS640), and when expected receipt information is downloaded (MHEXRH, MHS815).

Preallocation download - MHS805MI

Downloading preallocation data provides the external system with the information that it requires to make decisions during receiving, such as decisions about cross‑docking and put‑away locations.

The preallocation download file (MHPREA) mirrors the data of the M3 core preallocation file (MPREAL), maintained in (MWS120), for the warehouses where Planned receipts download parameter on (MMS005/H) is set to 1. You can access the MHPREA data in (MHS805). You can list the preallocation data by using MHS805MI.

The four download files MHPICL (pick header), MHPICD (pick details), MHPICA (addresses), and MHPICT (text blocks) are populated. You can access the pick ticket header and detail data in (MHS810) and (MHS811), and the address in (MHS813). You can list pick header data (LstPickList), pick detail data (LstPickDetail), address data (LstPickListAdr), and text block data (LstPickLstTxt) by using MHS810MI. Use PrcPickList to mark the pick list header and lines as read from the external system. This prevents the data from being listed again. Use PrcPickListDet to mark lines individually as read.

Using MHS810MI, you can list pick details for a specific wave number by using the LstDetByWave transaction.

After a pick ticket is downloaded, the external system controls the process. Because of this, users must not report or delete picking lists within M3. When you open the M3 core pick reporting program for a warehouse that is externally controlled, a warning message is displayed. You can configure this message as a hard validation to prevent users from continuing in the program. When an order line is changed, the change does not update the existing pick ticket. Instead, M3 creates a new delivery and picking list suffix for the additional quantity.

Request for movement task download

This function can, for example, be used after quality inspection of received goods is performed in M3, when a movement from a non‑allocable location to an allocatable stock location in the WMS is required.

The movement task is created in M3 and can be downloaded to the external system. The WMS retrieves the movement request and reports the movement to M3 after the task is completed.

Generate a request for movement task to a WMS

The M3 user generates a request by using (MHS177). The function program, MMCRTMOV is created to manage the movement task that is initiated in (MHS177). The system checks whether another request for the same balance ID is already waiting to be reported. M3 generates a task number (TASN) that is used as a unique identifier. The WMS must return this identifier to M3 when reporting the progress of the request. MMCRTMOV calls MMMNGMOV to validate the request. If the validation is successful, MMCRTMOV writes the request to the MHTASK download file, which can then be retrieved by the external system.

Create and download movement task:

Report back the performed movement task to M3 - MMS850MI

MMS850MI manages situations in which M3 initiates the movement task, as opposed to cases where the WMS initiates the movement. The M3 programs that update the M3 files are not executed until the movement is reported back. The function program MMCRTMOV is called by MMMNGMOV to delete the record in MHTASK.

Picking list download - MHS810MI

Upload, execute and delete movement task:

On the download side, a new download file, MHTASK, is used. The physical movement that is managed by the external system is triggered by the information in the download file and is then reported back in the same way as the current process. The difference is that the M3 user selects the items to move. The task number (TASN) that is downloaded from M3 must also be reported back. The reference order category and number are included in the download file. This enables solutions in which movement tasks that are initiated by related transactions, such as goods receipts, can be handled differently by the WMS.

If the WMS fails to carry out the movement, it must still report back to M3, with the reported quantity set to 0.

Exception management

If a quantity other than the quantity downloaded in MHTASK is reported, different results can occur. These exceptions must be treated in the same way as full reporting. The quantity reported by the operator through WMS must be the quantity used in the M3 transactions. The record in MHTASK must also be deleted when the transaction is processed.

As described in Picking list download – MHS810MI, if the WMS fails to carry out the movement, it must still report back to M3, with the reported quantity set to 0.

If a quantity smaller than expected is reported, it may indicate that there were not enough goods at the 'From location'. In that case, stock remains at the From location in M3 and in the WMS (if applicable) even though it does not exist. A manual balance adjustment is required.

If a quantity larger than expected is reported, there may not be enough available stock from which to take. In this situation, the upload message does not pass validation and receives status 45. The balance at the 'From location' must be adjusted before the upload message is executed again.

Mass deletion of downloaded data

Use the mass delete program to delete general data that you downloaded to WHI: 'Download Data. Mass Delete' (MHS090).

We recommend this program for customers who manage large data volumes through WHI. It provides these main functions:

1. Deletion of downloaded data for different download tables at the same time.
2. Deletion of downloaded basic data.

This program provides the same functionality as selecting the F10/MASSDE() action in download programs for transaction data, such as MHS800. It applies to the download tables for basic data and transaction data, similar to these instances:

1. Basic data download
   • MHS630/Item Download: Table MHITMA
   • MHS635/Alias Download: Table MHIPOP
   • MHS640/Supplier Download: Table MHDMAS, MHDVEN, and MHDADR
2. Transaction data download
   • MHS800/Expected receipts: Table MHEXRH, MHEXRD, MHFRNS, and MHPRNS
   • MHS805/Preallocation Download: Table MHPREA
   • MHS810/Picking List Download: Table MHPICL, MHPICD, MHPICA, and MHPICT

Selection of download programs/tables to mass delete

On the E panel of the program, a check box is available to the right of each download program. When you select a check box, the download tables for the current program are selected for mass deletion.

Selection of data in download tables to mass delete

The mass delete program uses criteria that specify which data to delete from the tables for the selected download programs. These criteria includes the 'Download flag' field (DOWN) and the 'Days before mass delete' field, DBDE.

The DOWN field has a default setting. By default, the mass delete process removes only data with DOWN set to 1, which indicates that the external system marked the data as processed. To include downloaded data with DOWN set to 0, which indicates unprocessed data, select the Include unprocessed data check box. When you select this check box, the mass delete process removes all downloaded data, regardless of the value in the DOWN field.

The DBDE field is used as a selection criterion for mass delete in the existing F10 = Mass Delete option in the download programs for transaction data, such as (MHS800/B). In these programs, the field is set using F13 = Settings. In the new mass delete program, the DBDE field provides the same functionality and applies to both basic data and transaction data. Mass delete selection based on DBDE works as follows: the entered number of days in DBDE is compared with the change date of the data included in the files to be deleted. Data with a change date older than the specified number of days, counted from the current date, is deleted. Only the programs that are currently selected in each of the two groups are affected by the DBDE setting. Locally defined DBDE values in the transaction data download programs are not considered when the new mass delete program is used.

To run the mass delete program, the DBDE field must be correctly set. If the field is left blank when you press Enter or Next, an error message is displayed and you must specify a value in Days bef delete. To select zero days before deletion, you must set the DBDE field to 0.

Perform check before executing mass delete

When you select Mass Delete on the E panel within a program, the system displays a confirmation dialog. Use this dialog to either cancel or confirm the deletion. This prompt prevents unintended data loss. The mass delete occurs only after you confirm the action. If you cancel it, the system returns you to the E panel with all original settings unchanged.