Analyzing and documenting issues in Grid values

IPW always displays the current material plan. To ensure data accuracy, you must compare the grid values in IPW with those in the BE Material Plan (MMS080) and the relevant API transactions, which are recorded in the IPW log file:

  • The base function of IPW is to present the material plan exactly as shown in MMS080.
  • IPW provides options to deviate from the MMS080 material plan based on specific parameter settings.

Understanding grid cell tooltips

Each key grid cell in IPW displays a tooltip that shows the available values used in the calculation:

  • Grayed out fields: Available but not used in the calculation because of the IPW parameter settings.
  • Active fields: Used to calculate the cell value.
Note: You can enable the tooltip in Actions > User Settings.

You can always analyze the tooltip details for these three primary cells:

  1. On-hand balance
  2. Demand
  3. Supply

You must begin your analysis by comparing the material plan values with the cell values and their corresponding tooltip information.

Working with the Log File

To enable logging, select Actions > User Settings > Write details to log file.

Note: Logging affects system performance. You must enable logging only during issue analysis. For daily operations, do not enable logging to optimize performance.

The log file contains all IPW parameters and MI-program transactions, including API calls like MMS080MI > SelMtrlTrans.

When you click Update, the IPW version and build details are recorded in the Log File tab.

Records in the log file:

  • Timestamp
  • Log level records in priority. You must fix or understand log levels 1–3:
    1. [FATAL]
    2. [ERROR]
    3. [WARNING]
    4. [INFO]

      Information that helps you understand values displayed in IPW

    5. [DEBUG]

      Enable this in Actions > User Settings > Write details to log file

  • Origin where IPW creates records with Origin = [InventoryPlanningWorkbench]
  • Message

Analyzing MI-Transactions in the Log File

All MI-program transactions related to IPW data import and export decisions are recorded in the log file.

One example is the Warehouses Import Analysis transaction. Warehouses are imported using the transaction MMS005MI > Select, which is recorded in the log file. To retrieve all warehouses, the MI-program uses:

Program=MMS005MI,Transaction=Select,Keys=CONO;780;WHGR;IPW;

This shows a typical record returned by the system:

Receiving record,Program=MMS005MI,Transaction=Select,Keys=CONO;780;DIVI;AAA;FACI;A01;WHLO;001;MAIW;1

These are the steps for troubleshooting:

  • If no records are returned, check the MI-program for errors. You can use Metadata Publisher to test the API with the same parameters that IPW uses.
  • If records are retrieved but IPW does not display any data, investigate the IPW parameters and settings,

You can also export the log file content into an external text file for documentation and further analysis.

Example:

[INFO][MIServiceCore]..........returned error

The MI program cannot find any records to transfer and displays an INFO message.

Documenting and reporting IPW issues

If the issue is still unresolved after thorough analysis, report it as an incident through the Infor Customer Portal.

  1. Export the entire log file. To export a log file:
    1. Open the log file.
    2. Press Ctrl + A to select all text.
    3. Copy and save the content to a blank text file.
  2. Attach the log file text to your incident report.
  3. You must include all relevant screenshots and detailed descriptions of the issue, ensuring they correspond to the same dataset as the log file.
  4. Specify whether the issue involves a difference between IPW and the material plan or concerns options for deviating from the material plan.