Managing Mismatches for Item per Warehouse

Outcome

This function makes it possible to check that:

• The allocated quantities in transaction files and stock balance files are synchronized with each other for a specific combination of item and warehouse.
• The records in the Material Plan are synchronized against order lines quantities and dates. All types of order categories are included in the check.

If an error is detected, the item/warehouse combination is recorded in a message file.

This routine is used to repair mismatches for allocation, inventory, and planning data in the database.

This diagram illustrates the analyze flow in this routine.

• MWASHE - Allocation Synchronization Rounds
• MWASLN - Allocation Synchronization Errors
• MWASMG - Allocation Synchronization Messages

Solution overview

1. (MWS980) - Analyze allocations and inventory

   (MWS980) enables selections of warehouse/item and submits an analyze round. One record is created in MWASHE for each round.

2. (MWS981) - Analyze errors

   (MWS981) displays all identified errors. Records are created in MWASLN.

3. (MWS982) - Analyze messages

   (MWS982) displays error messages. Records are created in MWASMG.

4. MWASHI - History file

   The MWASHI history file is updated by the function MWMNGASY (Manage synchronization). It is only the repairable errors that are logged in the history file.

Description of involved programs and error messages

• (MWS984) aggregates MITALO records based on MITLOC.
• (MWS985) aggregates MITALO records based on XXLINE.
• (MWS986) checks orders and matches them to allocations XXLINE->MITALO.
• (MWS987) checks MITBAL and matches them to MITLOC.
• (MWS988) checks the records in the Material Plan (MITPLO) against order lines quantities and dates. All types of order categories are included in the check.
• (MWS989) checks order lines (different files depending on the order category) against material plan MITPLO.

Recommendations

• The panel sequence must be filled in for (MWS981), but the program does not contain any other panels than the B panel. The valid panel sequence is therefore 2 (option 12) and 4 (option 14), according to M3 standard programming.
• When you have submitted an analyze, you can check the error file (MWS981) while the job is running. By pressing F5, it will build up the sub file with the errors as they occur. Once one error has occurred, you can check the error messages (MWS982) for that record while the job is running.
• Option 7 in (MWS980) pauses an analyze round. When you have used this option, there is no job running in the background. In (MWS980/F), the last warehouse and last item number is displayed which indicates at what record the analyze round was paused.
• The analyze round does not perform any updates except on the analyze files.
• The option Repair by result only repairs the errors that have severity level 20.
• In (MWS980/E), you have different parameters to choose from. We also recommend to not overlap your selections for item/warehouse because of timing and performance issues. For example, you should not run whs 001- 001 item 1000 – 3000 in two different rounds at the same time.
• Take note of the text in the (MWS980) sub file when you have a round paused. The text indicates which option the round was paused with. This is the same option you will use to start the analyze round again. You also have a status that indicates which status the job is in.
• The history file is not emptied automatically, we recommend that you check the size of this file so that it does not becomes too large. The history file displays errors that have been repaired.
• Using the event file settings in (CRS701) and (MWS980/E) nets the changed transactions, which in turn makes the program faster since the amount of records will be fewer. Compared to not using the event file, the whole database for the selection made is used.