Diagnosing System Issues

Objective

After completing this lesson, you will be able to understand how to troubleshoot business user logs.

Master Data Quality Checks

When the inventory operators run, they perform a master data quality check. If there are issues within the master data, they are logged in the business logs. The following table lists the errors the master data quality check looks for, which operator runs the check, and the message logged if the check fails:

Master Data Check ErrorOperatorLog Message
MOTID attribute not configured in the SOURCELOCATION master data type when it is configured in the SOURCELOCATIONVALIDITY master data type.Global (multi-stage) inventory optimization

Missing NULL MOTID from SOURCELOCATION master data.

SOURCELOCATIONVALIDITY / MOTID ignored. Incompatible with SOURCELOCATION.

MOTID attribute not configured in the SOURCELOCATIONVALIDITY master data type when it is configured in the SOURCELOCATION master data type.Global (multi-stage) inventory optimizationSOURCELOCATIONVALIDITY ignored. Incompatible with SOURCELOCATION / MOTID.
MOTID attribute is not configured in required planning levels.Global (multi-stage) inventory optimization

Missing MOTID from WKPRODLOCLOCFR planning level.

Missing MOTID from WKPRODLOCLOCTO planning level.

IOFORECAST key figure not included in version.Global (multi-stage) inventory optimizationMissing required key figure IOFORECAST.
CUTSGROUP attribute does not have input data in CUSTOMER master data.Global (multi-stage) inventory optimizationCUSTGROUP data missing in Customer master data
Calculate Target Inventory Components
Decomposed (single-stage) inventory optimization
The figure describes the Master Data Quality Checks.

Diagnosis of System Issues

The figure describes the Visibility to Business User Logs for Cyclical Sourcing in Transportation and Production.

Visibility to business user logs for cyclical sourcing in transportation and production

  • Before release 2411 a global parameter for loop handling was available. When using Parameter Value ENABLE in Parameter Name LOOP_HANDLING, the inventory algorithm detected transportation and production cyclical sourcing (loops) and logs them as warnings.

  • The warning logs are visible in both Excel UI and Web UI.

  • The WARNINGs will have detailed information about loop such as:

    – Type of loop: Transportation or Static Supply Ratio.

    – Level of loop: the lanes involved in a loop.

    – Index number for Transportation loop logs: index number associated in a loop.

  • Number of warning logs limited to 500 per type of loop.

    SAP has replaced the loop handling parameter with cycle 2411.

The figure describes the Improved Job Resiliency when Processing Erroneous Input Data in SAP IBP for Inventory.

Improved job resiliency when processing erroneous input data in SAP IBP for inventory

  • SAP IBP for inventory algorithm prevents interruption of inventory planning cycles by completing optimization runs in presence of partial erroneous input data.

  • The algorithm excludes the partial erroneous input data related to a sub-network or sub-networks and continues the optimization run for inputs of remaining sub-networks.

  • If erroneous input data exist for all networks, the algorithm will fail.

  • User logs are exposed indicating:

    – Warnings for sub-networks with erroneous input data.

    – Errors when all networks have erroneous input data.

  • Examples of user logs:

    – "No outputs for exception in network for Product ID 1 and Location ID 2"

    – "Inputs for all networks could not be processed. No outputs returned"

  • Job resiliency is supported by planning operators:

    – Global (multi-stage) inventory optimization

    – Calculate Target Inventory Components

    – Decomposed (single-stage) inventory optimization

The figure describes the usage of Planning Filters in Excel UI Planning View for Inventory Optimization Simulation.

Use planning filters in Excel UI Planning View for Inventory Optimization Simulation

  • Improve run time and memory usage for Simulation when an Excel UI Planning View includes a Sub-network selection in Planning Scope and Attribute-Based Filters.

  • Feature links IO Network ID(s) with selected Planning Scope and Attribute-Based Filter values and then algorithmically solves for the resulting unique IO Network ID values.

  • Requirements:

    – Planning area configuration must include the IO Network ID attribute, including planning levels with LOCATIONPRODUCT master data.

  • Feature does not apply when:

    – No Attribute-Based Filter is selected.

    – Planning Scope selections do not match with Attribute-Based Filter selections.

  • Supported Functions:

    – Global (multi-stage) inventory optimization

    – Calculate Target Inventory Components

The figure describes the usage of Attribute Filter in Excel UI Batch Mode for Inventory Optimization Scenario.

Use attribute filter in Excel UI Batch Mode for Inventory Optimization Scenario

  • Improve run time and memory usage for scenario runs in batch mode.

  • Feature links IO Network ID(s) with selected attributes in the Filter tab of the Inventory Optimization window of the Application Jobs and algorithmically solves for the resulting unique IO Network ID values.

  • Requirements:

    – Planning area configuration must include the IO Network ID attribute, including planning levels with LOCATIONPRODUCT master data.

    – A baseline batch run of Global (multi-stage) inventory optimization planning must be completed successfully.

  • Feature does not apply when:

    – No Attribute filter is selected

    – Planning Scope selections do not match with Attribute filter selections

  • Supported Functions:

    – Global (multi-stage) inventory optimization

    – Calculate Target Inventory Components

The figure describes the Global Configuration Settings and Log Messages.

Global Configuration Settings and Log Messages

  • An Information log message indicating attribute filters are not applied to a batch run when:

  • The warning logs are visible in both Excel UI and Web UI.

    – A baseline batch run has not been completed.

    – Filter selections result in more than 200 linked IO Network IDs

    – IO Network ID attribute is not configured in planning area.

    – Filter selections do not match with assigned IO Network ID output values.

  • An SAP IBP: Error pop-up window will display when a planning view contains invalid combination of planning scope and attribute-base filter for a simulation run.

  • For technical users, a global configuration setting is available for support cases when users are not sure or satisfied with results:

    – Parameter group: INVENTORY

    – Parameter name: USE_PLANNING_VIEW_FILTER

    – Parameter value: NO, YES. If setting not configured, or any other value provided, default Parameter Value: YES

Learning

SAP FacebookSAP YoutubeSAP LinkedIn