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.

These functions can be executed manually using selection criteria or they can be scheduled. When performing the download manually using the selection programs mentioned above, M3 basic data records that might have been deleted will not be captured, only new and changed records. The manual routine gives a refresh or a snapshot view according to the selections.

The 'Change date' field is used to schedule when the download should be performed.

Note: A new record will appear with the command (CMND) *UPD or *CHG depending on how the record is created.

An MBM initiator can be created if there are records that have been changed in M3 and should be retrieved by the external system. The initiator for alias and supplier download is only available in Java.

Expected receipts download - MHS800MI

Expected Receipts is composed of Purchase Order Receipts, Distribution/Requisition Order Receipts, Customer Order Returns and Manufacturing Order Receipts. The aim of the transaction is both to give the external system visibility of inbound transactions and enable the receipt to be performed by the external system, using this information.

MHS800/801/803 is the M3 functions where the expected receipts download files MHEXRH, MHEXRD and MHFRNS can be monitored in MHS800/801 and MHS803. The data is written to these files by the MMS910 and OIS390 functions if the warehouse parameter 'Planned receipts' in MMS005/H is set to 1. MHS800MI is used to list the expected receipts.

Expected Receipts Package Details for Inbound DO MHS803 - goods receipt of a DO line if it consists of several lots. A view program over MHFRNS exists, called MHS803. This is accessed by selecting option 11 from MHS801.

A good rule is that any change that would affect the material plan in M3 will also update the expected receipts files. One result is that only changes on the line level are captured.

However, some changes are filtered so M3 only downloads relevant data. The command field (CMND) follows the update of the material plan (MITPLO) and can be used when building logic into the external system. Please see the table below for how the command field reacts for different events. (Please note the table describes the normal events and there could be exceptions depending on how M3 is configured.) The download flag (DOWN) is always set to zero (0) after M3 has written or updated a record.

Purchase order (PO) Transaction event:

Expected receipts header (MHEXRH, MHS800)

Expected receipt details (MHEXRD, MHS801)

Add a PO with lines

*ADD

*ADD

Change quantity or date

*CHG

*CHG

Partial receipt

*PRC

*PRC

Fully receipt

*CLS

*CLS

Deleted order

*DLT

*DLT

Close PO

*CLS

*CLS

Note: Shipment advice (PPS260) and transportation notification (PPS270) are filtered from download. Confirmation (PPS250) updates the download files and can lead to order lines being split via the purchase line suffix. Quality inspection (PPS310) will not update the download files. Close PO via function (PPS350) will result in a *CHG on the PO header and *CLS on the lines.

Distribution order (DO) Transaction event:

Expected receipts header (MHEXRH, MHS800)

Expected receipt details (MHEXRD, MHS801)

Order with one line

Order with several lines

For changed line

For unchanged lines if exists

Add an order with lines

*ADD

*ADD

*ADD

*ADD

Change date on order head

*CHG

*CHG

 

*CHG

Change date on order line

*CHG

*CHG

*CHG

Same as before

Change quantity

*CHG

*CHG

*CHG

Same as before

Partial receipt

*PRC

*PRC

*PRC

Same as before

Full receipt

*CLS

*PRC

CLS*

Same as before

Delete order header

*DLT

*DLT

 

*DLT

Delete order line

*DLT

Depends on flag for rest of the lines

*DLT

Same as before

Note: Delivery number (DLIX) is used for DO receipt and the final (DLIX) is downloaded when the picking list from the 'from warehouse' is reported. Requisition orders (RO) will follow the same logic.

Manufacturing (MO) Transaction event:

Expected receipts header (MHEXRH, MHS800)

Expected receipt details (MHEXRD, MHS801)

Add a MO with lines

*ADD

*ADD

Change quantity or date

*CHG

*CHG

Partial receipt

*PRC

*PRC

Fully receipt

*CLS

*CLS

Deleted order

*DLT

*DLT

Note: Expected receipt for by-products and co-products (PMS080, PMS090) is not supported.

Customer order returns Transaction event:

Expected receipts header (MHEXRH, MHS800)

Expected receipt details (MHEXRD, MHS801)

Add a CO return with lines

*ADD

*ADD

Change quantity or date

*CHG

*CHG

Partial receipt

*PRC

*PRC

Fully receipt

*CLS

*CLS

Deleted order

*DLT

*DLT

Note: The CO return must be advised in M3 prior to receipt. (CO return in status 11). Two-step CO return with quality inspection is not supported. It is possible to exclude records that have been previously processed by entering 1 in the field Exclude processed before. This is useful in a scenario when the external system cannot manage multiple downloads of the same record. The process flag (0/blank = Unprocessed, 1 = Processed) is disregarded if 'Exclude processed before' is set.

Expected receipts create MBM initiators

This function creates MBM initiators for the selected expected receipts records so the expected receipts then can be downloaded to M3 e-Collaborator.

The MBM Initiator can be used to trigger the Infor Enterprise Collaborator (IEC) to ask for the updated records via the MI programs. The initiator contains all the necessary information that IEC needs to be able to use the MI 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 information so that the external system can make better decisions during the receiving process about cross-docking, put-away locations, and so on.

The preallocation download file (MHPREA) mirrors the data of the M3 core preallocation file (MPREAL - maintained from MWS120) for the warehouses where the download parameter 'Planned receipts' in MMS005/H is set to 1. The MHPREA data is accessible from the program MHS805. MHS805MI is used to list the preallocation data.

Note: The M3 cross-docking functionality with optional cross-docking cannot be used when M3 is integrated to an external WMS.

The four download files MHPICL (Pick header), MHPICD (Pick details), MHPICA (Addresses), and MHPICT (Text blocks) are populated. The pick ticket header and detailed data is accessible from MHS810/811 and the addresses from MHS813. MHS810MI is used to list pick header (LstPickList), pick details (LstPickDetail), addresses (LstPickListAdr), and text blocks (LstPickLstTxt). The transaction PrcPickList is used to mark the picking list header and lines as read from the external system, which means that it will not be listed again. PrcPickListDet is used to mark the lines one by one as read.

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

Once a pick ticket has been downloaded, the external system takes over. Therefore, no picking lists should be reported or deleted within M3. When entering the M3 core pick reporting program for an externally controlled warehouse, a warning message is displayed. This warning can easily be modified to a hard validation preventing the user from using the program for an externally controlled warehouse. A changed order line will not update the existing pick ticket but will create a new delivery and/or picking list suffix for the additional quantity.

Note: The parameter auto print on the dispatch policy (MWS010) must be set to 1 if the picking list should be automatically downloaded when it is released.

Request for movement task download

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

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

Generate a request for movement task to a WMS

The M3 user will generate a request by using the program MHS177. A function program (MMCRTMOV) will be created to manage the movement task initiated in MHS177. We also check if there is another request for the same balance ID already waiting to be reported. A task number (TASN) will be generated by M3 and used as a unique identifier that must be returned to M3 by the WMS when reporting the progress of the request. This function program calls the existing MMMNGMOV to validate the request. If the validation is successful, the request is written to a new download file (MHTASK) by MMCRTMOV and can thereafter be downloaded by the external system.

Create and download movement task:

Report back the performed movement task to M3 - MMS850MI

MMS850MI takes care of the situation in which M3 has initiated the movement task, as opposed to when the movement is initiated from the WMS. The M3 programs that actually 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

The pick ticket download is performed from MWS435 if the warehouse parameter 'Picking list' in MMS005/H is set to 1 or if the picking list parameter on warehouse equipment MWS023 is set to

1. The download based on warehouse equipment is meant for use when interfacing to material handling equipment (MHE). This can, for example, be used when only one part of the warehouse is automated.

You can also print and download a picking list if the parameter in MMS005 or MWS023 is set to

2. This solves the case when the picking is performed by MHE but the reporting is done by the user.

Upload, execute and delete movement task:

On the download part, there is a new download file, MHTASK. The physical movement, managed by the external system, is triggered by the information in the download file and it is then reported back like as is currently done; the difference is that the M3 user decides which items to move. The task number (TASN) that has been downloaded from M3 must also be reported back. The reference order category and number are included in the download file. This opens up for solutions where movement tasks initiated by related transactions, for example goods receipts, can be treated in a different way by the WMS.

If the WMS fails to carry out the movement, the reporting back to M3 should still be performed but with the reported quantity set to 0.

Exception management

If a quantity other than the one downloaded in MHTASK is reported, different results can be expected. These types of exceptions should be treated exactly like full reporting. In other words, the quantity reported by the operator via the WMS should be the one used in the M3 transactions. The record in MHTASK should also be deleted when the transaction is processed.

As mentioned in the section above, if the WMS fails to carry out the movement, the reporting back to M3 should still be performed but with the reported quantity set to 0.

If a quantity smaller than expected is reported, it might be because there were not enough goods at the From location. In that case, there is stock on the From location in M3 and in the WMS (if applicable) that in fact does not exist and a manual adjustment of the balance is required. If a quantity larger than expected is reported, there might not be enough available stock from which to take. In that case, the upload message will not go through the validation and it will receive status 45. Then, the balance at the From location must be adjusted before executing the upload message again.

Mass deletion of downloaded data

A mass delete program has been created for the mass deletion of general data that has been downloaded to the WHI: 'MHS090 - Download Data. Mass Delete'.

This program is recommended for use by customers who handle large data volumes via the WHI. It enables two main things:

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

  2. Deletion of downloaded basic data.

The program has the same functionality as action F10/MASSDE() has in the download programs for transaction data, for example MHS800. It applies to the download tables for basic data and transaction data, as in the following 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 (MHTRND, not delivered yet?!)

Selection of download programs/tables to mass delete

On the E panel of the program a check box appears to the right of each of the download programs. The purpose of the check box is to enable the selection of the download data for a specific program to be mass deleted. If a check box is selected, the download tables for the current program are selected for mass deletion.

Selection of data in download tables to mass delete

There are two criteria in the mass delete program that are used to determine the data to delete from the tables for the selected download programs. The first one is the 'Download flag' field, DOWN. The second one is the 'Days before mass delete' field, DBDE.

The criteria for DOWN has a default setting. That is, by default only data with DOWN set to 1 (data that is marked as processed by the external system) will be deleted from the selected download tables. In order to also include downloaded data that has DOWN set to 0 (data that is marked as unprocessed), the check box 'Include unprocessed data' must be selected. When this check box is selected, all downloaded data will be mass deleted, regardless of the value in the DOWN field.

The DBDE field is already used as criteria for mass delete in the currently existing method for option F10='Mass delete' in the download programs for transaction data, for example MHS800/B. In these programs the field is set under option F13=Settings. The DBDE field has the same functionality in the new mass delete program and is applicable for both basic and transaction data. The selection of mass delete based on the DBDE field is done in the following way. The entered number of days in DBDE is compared to the change date of the data that is included in the files that should be mass deleted. The data with change date further back in time than the entered number of days in DBDE counted from today is deleted. Only those programs that are currently checked in each of the two groups will be affected by the setting of the field. The locally set DBDE fields in the download programs for transaction data will not be taken into consideration when the new mass delete program is used.

In order to execute the mass delete program, the DBDE field must be correctly set. If it is left blank when Enter or Next is pressed, this will result in an error message, ''Days before deletion' must be entered'. This also means that in order to be able to select zero days before deletion, 0 must be set in the DBDE field.

Perform check before executing mass delete

When the selection for mass delete has been done and Enter or Next is pressed on the E panel of the mass delete program, a pop-up field is displayed presenting options to either cancel or confirm the mass delete. This is used in order to avoid unintended delete of data. Only if confirm is selected the mass delete of the download data actually takes place. If instead cancel is selected, a jump is made back to the E panel of the program, where the earlier made settings still will remain.

Related topics