Mcf-En-Public Sap

© 2022 SAP SE or an SAP affiliate company. All rights reserved.
PUBLIC
2022-10-04
Comprehensive Functions
THE BEST RUN

Content
1 Comprehensive Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.1 Task Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Creating Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Maintaining Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Tasks Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Additional Comments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
User Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.2 Resubmissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Maintaining Resubmissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Resubmission Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
1.3 Comment Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Creating Comments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1.4 Tasks, Resubmissions, and Comments on the Results Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
1.5 Individual Material Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Creating Individual Material Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Editing Individual Material Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Deleting Individual Material Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
1.6 Alerts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Creating and Editing Alerts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Creating and Editing Alert Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Using the Alert Profile in the MRP Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Combined Alerts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Formula-Based Alerts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
1.7 Formulas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Creating and Editing Formulas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Creating and Editing Formula Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Using the Formula Profile in the MRP Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
1.8 Planning with Key Figures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Programming the BAdI Interface for Key Figure Calculation. . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Working with the Formula Editor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Creation of Key Figure Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
1.9 Layout Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Using Layout Group Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Creating Layout Profiles and Configuring Layout Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Translation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
1.10 Layout Sets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
2 PUBLIC Content
1.11 Enhanced Navigation Profile Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Jump to Executable Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Conditional Branching. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Navigation by Double-Clicking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
1.12 Save current stock/requirements list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Save Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Delete Obsolete Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
1.13 Protection of ALV Layouts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
1.14 Solution Feedback. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
1.15 Default variants. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
1.16 Autostart. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
1.17 Report for Order Relation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57
Flow Logic. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58
1.18 Unified Planning Center. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58
1.19 Excel Upload/Download. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
1.20 Action Flows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Concept. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Available Action Steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Include Action Steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
1.21 Proposals Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68
Execute Rule Book Check. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Include Rule Book Check. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
2 Material Master Update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

2.1 Overview of Update Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72
2.2 Flexible Material Master Update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
2.3 Rule-Based Material Master Update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
2.4 Two-Step Rule-Based Material Master Data Update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
2.5 Flexible Rule-Based Material Master Update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
2.6 Two-Step Flexible Rule-Based Material Master Update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
2.7 Dialog or Background Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
2.8 Maintaining Rule Sets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
3 Enhanced Material Master View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

3.1 Material Assignment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
3.2 Central Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Comments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Change Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Date of Last Update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Where-Used List for Fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Content PUBLIC 3
S/4: Force Classic MRP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
3.3 Customizing Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Displaying Fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Exception Indicators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97
Production/Procurement Principle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
3.4 MRP Area Level. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
3.5 Storage Location Level. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
3.6 Logging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
3.7 Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .104
4 Material Document Aggregation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

4.1 Technical Implementation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
General Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
"Settings" Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113
4.2 System Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Delete Old Analyses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Working with Jobs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Best Practice - Job Chain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Optimizing Performance Using the Package Size. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
4.3 Organizational Information for Material Document Aggregation. . . . . . . . . . . . . . . . . . . . . . . . . . 131
4.4 Manual Corrections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
4 PUBLIC Content
1 Comprehensive Functions
Using the comprehensive functions, you can document and coordinate objects to be processed.
These are primarily the following functions:
• Tasks and resubmissions

• Comment functions
• Defining and selecting individual material groups
The functions listed above are explained using the example of the SCM Consulting Solution lot size
simulation. The explanations are also valid for all other SCM Consulting Solutions.
 Caution
Before you can use the tasks functionality in the MRP monitor, you need to select the Re-read tasks and
resubmission date checkbox on the Result tab in the MRP monitor when displaying or reading a saved
result.
If Re-read tasks and resubmission date is not selected, the pushbuttons Tasks, Resubmission, and
Comment are inactive on the result screen and therefore cannot be used.
Zusätzlich sind folgende SCM-Beratungslösungen Bestandteil der Comprehensive Functions:
• Materialstamm-Update
• Enhanced Material Master View
• Material Document Analysis
• Excel Up-/Download
• Flexibles Materialstammupdate
Das Materialstamm-Update ermöglicht Ihnen das Speichern von Daten in SAP Standard Feldern und in Feldern
des Enhanced Material Master View. Sie können die Materialstammdaten direkt aus der Ergebnisliste Ihrer
SCM-Beratungslösungen heraus bearbeiten.You can use the enhanced material master view to access the
material master data fields of the SCM Consulting Solutions.
 Note
Bitte beachten Sie, dass Sie bei der Ausführung von SCM-Beratungslösungen jeder Transaktion /n/
SAPLOM/ voranstellen müssen.
Related Information
Material Master Update [page 72]

Enhanced Material Master View [page 83]
Material Document Aggregation [page 105]
Stock Development
Comprehensive Functions PUBLIC 5
1.1 Task Function
You can use the task function to document various tasks for an object. These are mainly used for inventory
reduction purposes. You can use these functions with numerous SCM Consulting Solutions. In this way, you
can see whether there is an open task that corresponds to the combination of plant, material, and SCM
Consulting Solution.
1.1.1 Creating Tasks
Context
After you have started the lot size simulation, for example, you can perform the following steps to display or
edit tasks for rows in the result list.
Steps to Create/Display Tasks
Procedure
1. Select the relevant data records

2. Choose the Tasks pushbutton.
The “Tasks” screen appears.

3. In the upper part of the screen, you can filter the object and task IDs of the task, comment, and/or
resubmission data records to be selected or created. You can use the checkboxes to define which data
records (tasks, resubmissions, and/or comments) are to be displayed or created.
• When you click Select Tasks , all existing task, resubmission, and/or comment data records with this
object ID combination are selected.
6 PUBLIC Comprehensive Functions
• When you click Create Object Measures, the new task, resubmission, and/or comment data records are
created directly without you first having to save. If, in addition to the resubmission and/or comments
checkboxes, the checkbox for the task was also selected, the newly created resubmission and/or
comment data records are linked at the database level. Linked tasks, resubmissions, and/or
comments are always selected and displayed together.
You can change tasks on the screen in both cases.

4. Save the changes.
1.1.2 Maintaining Tasks
Use the ALV standard toolbar to process ALV lines.
ALV Standard Toolbar
The Duplicate Row pushbutton creates a new row as a duplicate of the selected row.
If you change data, the date and time of the change and the user who makes the change are saved in the
corresponding fields.
You can use the Assign Attributes pushbutton to map field values for the selected rows for the following:
• Task ID
• Completed indicator
• End Date
• Comment
• Additional fields for comments
Assigning Attributes
When you have finished maintaining the data, you can use the Save ( ) pushbutton to save all changes to the
following database tables: /SAPLOM/X_MEASUR for task data records, /SAPLOM/X_RESUBM for
resubmission data records, and /SAPLOM/X_COMM for comment data records.
Close the dialog box by choosing the Cancel pushbutton or the Esc key on the keyboard. In the following
prompt, you can save before the dialog box closes.
Related Information
Configuration of the comprehensive functions
1.1.3 Tasks Overview
With the tasks overview, you can manage all tasks centrally.
You can access this overview by calling transaction /SAPLOM/X_MEAS or via the result screen by choosing the
Overview of Tasks pushbutton.
The selection screen is divided into four different criteria blocks:
• Analysis Scope
• Additional Selection Criteria
• Analysis Period
• Restriction 2
Analysis Scope
In the analysis scope, you can further restrict the search to a specific material number, plant, and so on.
Analysis Scope
Analysis Period
In the analysis period, you first specify whether you want to analyze a five-day or seven-day week. You can also
select by creation date and resubmission date. The pushbuttons offer various preset analysis periods. If you
select the creation date, the system analyzes the past period up to the current date, whereas if you select the
resubmission date, the system analyzes the future period as of the current date. You can also enter the analysis
period manually.
Analysis Period
Restriction 2
Under Restriction 2, you can choose between open or finished tasks, or display both. In addition, you can also
display linked objects.
Restriction 2
Result Screen
Result Screen: Overview of Tasks
You can change the following columns on the result screen:
• Task ID
• Finish Date
• Finished
• Comment
• Additional Comments
After processing the fields, you adopt this change using the pushbutton Save.
You can also use the pushbutton Finish to select one or more rows and identify the tasks as finished, or remove
the identification.
If you remove the "complete" step, the calculated and displayed value remains in the two columns Stock new
and Stock value new.
If you end a task, the columns Stock new and Stock value new are calculated and displayed.
You can use the Tasks pushbutton to create and edit new tasks, comments, and resubmissions.
1.1.4 Additional Comments
You can add up to ten additional comment columns for tasks. You can maintain the column headings for the
additional comments in various languages.
 Restriction
Column headings for additional comments may have a maximum length of 30 characters.
1.1.4.1 Entering Additional Comments
You can use up to ten additional comment columns.
Prerequisites
• Tasks must already exist in the system.

• The column headings for the additional comments must already be entered.
Context
You can use the task function dialog boxes to maintain the additional comments.
Entering Additional Comments
Related Information
Configuration of Comprehensive Functions

Task Function [page 6]
1.1.5 User Parameters
Numerous user parameters are available for the functions of tasks, resubmissions, and comments. These are
listed below, together with their function and possible values:
User Parameters
Parameter ID Description Values Function
/SAPLOM/MEA_ADD_FLDS Display additional comment 1 = 5 additional fields Depending on the parameter

fields for tasks value, 5, 10, or no additional
2 = 10 additional fields
comment fields are initially
displayed on the task screen.
/SAPLOM/MEA_FIN_DATE Default end date (today + x Number of days (CD) The number of days entered
days) here is added to the current
date and the End Date field
on the task screen is preset
accordingly.
/SAPLOM/MEA_FIX_CMON Fixed default monitor for Any monitor ID The fixed value specified here
comment is used to preset the Monitor
field when creating or dis
playing comments.
/SAPLOM/MEA_FIX_COBJ Fixed default comment ob Fixed default comment ob The fixed value specified here
ject ject is used to preset or select the
Object field or an object from
the object list when creating
or displaying comments.
/SAPLOM/MEA_FIX_RMON Fixed default monitor for re Fixed default monitor for re The fixed value specified here
submission submission is used to preset the Monitor
field when creating or dis
playing resubmissions.
/SAPLOM/MEA_FIX_ROBJ Fixed default resubmission Fixed default resubmission The fixed value specified here
object object is used to preset or select the
Object field or an object from
the object list when creating
or displaying resubmissions.
/SAPLOM/MEA_FIX_TOBJ Fixed default task object Fixed default task object The fixed value specified here
is used to select an object
from the object list when cre
ating or displaying tasks.
/SAPLOM/MEA_FMODE Mode for resubmission and 2 = Dialog box for resubmis If the value 2 is specified
comment function key sion and comments here, the dialog box variant is
executed when resubmis
sions or comments are cre
ated. The "large" task screen
is then only accessed using
the Tasks function.
Parameter ID Description Values Function
/SAPLOM/MEA_MEM_COBJ Activation of memory ID for X = active If the memory ID is active,

comment object the last comment object
used is noted when com
ments are created. This value
is then preset during the next
create action.
/SAPLOM/ Activation of memory ID for X = active If the memory ID is active,

MEA_MEM_RMON resubmission monitor the last monitor used is
noted when resubmissions
are created. This value is
then preset during the next
create action.
/SAPLOM/MEA_MEM_ROBJ Activation of memory ID for X = active If the memory ID is active,

resubmission object the last resubmission object
used is noted when resub
missions are created. This
value is then preset during
the next create action.
/SAPLOM/MEA_MEM_TOBJ Activation of memory ID for X = active If the memory ID is active,

task object the last task object used is
noted when tasks are cre
ated. This value is preset dur
ing the next create action.
/SAPLOM/MEA_SELECT_I Tasks user parameter ID X = active If this user parameter is ac

tive, all task IDs that are dis
played in the current layout
are preselected.
/SAPLOM/MEA_SELECT_O Tasks user parameter object X = active If this user parameter is ac
tive, all task objects that are
displayed in the current lay
out are preselected.
1.2 Resubmissions
You use the function resubmission to define a new resubmission date to mark an object for further processing
in the future.
1.2.1 Maintaining Resubmissions
Context
You use the resubmission function to create a new resubmission data record with information about the next
processing run. The resubmission date can also be saved.
 Note
Technically, the ‘resubmission’ function is saved as a new resubmission data record in the database table /
SAPLOM/X_RESUBM.
To create a new resubmission data record, you must perform the following steps:
Procedure
1. Choose the row in the result list.

2. Click the Resubmission pushbutton.
The steps for creating a resubmission depend on the user parameter /SAPLOM/MEA_FMODE:
Case 1: If the user parameter /SAPLOM/MEA_FMODE has the value 2 and you choose the Resubmission
pushbutton, the system displays a dialog box for creating resubmissions.
Resubmission
Case 2: If the value of the user parameter /SAPLOM/MEA_FMODE is not 2 and you click the Resubmission
pushbutton, the screen below for the creation of common tasks, resubmissions, and comments is called
and the Resubmission checkbox is selected there.
Display/Create Tasks
3. In case 1, the user enters values for the object level, resubmission date, and resubmission note, and then
chooses the Save pushbutton. In case 2, the user enters the values for Monitoring, Resubmission Date, and
Resubmission Note and then chooses the Create Object pushbutton.
 Note
At least one resubmission data record is created in database table /SAPLOM/X_RESUBM.
1.2.2 Resubmission Process
If an open resubmission exists for a material-plant combination, you see a date in the Resubmission Date
column. A checkmark is only set in the Open Tasks field if there is an unfinished common task for this material-
plant combination.
If there are multiple incomplete resubmission data records, the task with the smallest (= earliest) date is
displayed in the Resubmission Date column. Alternatively, you can create a new resubmission data record in
the task catalog yourself.
1.3 Comment Function
You can use the Comment function to create individual comment data records for multiple objects.
Comments can be displayed, edited, and deleted using the Comments pushbutton or the Task function.
Another option is to use transaction /SAPLOM/X_MEAS.
Related Information
Creating Comments [page 16]
1.3.1 Creating Comments
Context
You can use the Comment function to create individual comment data records for multiple objects.
Procedure
1. Select a row in the result list.
2. Choose the Comment pushbutton. (You can also create comments using the Task function.)
The result depends on the user parameter /SAPLOM/MEA_FMODE:
Case 1: If the user has the user parameter /SAPLOM/MEA_FMODE with the value "2", a dialog box for
creating comments is displayed.
Comments with User Parameters
Case 2: In all other cases, the screen for creating common tasks, resubmissions, and comments is called
and the Comment checkbox is selected in it when the user chooses the Comments pushbutton.
Comments in General
3. In case 1, the user enters the object level and comments and then clicks the Save pushbutton to create one
or more comment data records. In case 2, the user enters values for the monitoring and comment note
and then chooses the Create Object pushbutton to create one or more comment data records.
Related Information
Configuration of the comprehensive functions
1.4 Tasks, Resubmissions, and Comments on the Results

Screen
On the result screens of most of the SCM Consulting Solutions, information on the tasks, resubmissions, and
comments is displayed directly in the ALV list, if the related object is MP - material/plant.
Result List
The following information is displayed:
• Resubmission Date
• Open Task Icon
• Comment (always the most recent comment)
• Number of open tasks for the current monitor + "XXX" – general. The column "Number of Open Tasks" has
a hot-spot function. When you click on the number, the tasks overview with preselection of object "MP",
and all the current associated task IDs + IDs of XXX is called for the current row.
• ID of the next open task
• Description of the next open task
• "Due Date" date of the next open task
On the result screens of some SCM consulting solutions, the object level of the displayed tasks, comments, and
resubmissions can be changed using a dedicated pushbutton.
The available object levels are derived from the underlying table. If, for example, the Purchase Order Item
object level is selected, tasks, comments, and resubmissions that were created with reference to the
corresponding purchase order items are displayed.
1.5 Individual Material Groups
Using your own criteria, you can create individual material groups that can contain multiple materials.
Grouping materials in this way serves to make your work easier.
 Example
You can assign all of the materials for which you want to perform a lot size simulation to a group and give
this group the name LGS Group.
Using transaction /n/SAPLOM/X_IND_MGROUP, you can either create new individual material groups and
assign multiple materials to the material group in one step using an import function (see section Creating
Individual Material Groups [page 19]), or you can edit existing individual material groups.
The selection screens of multiple SCM Consulting Solutions contain a corresponding search field. Using the
field's input help, you can see an overview of the material groups already created.
 Example
Using the Individual Material Group from Lot Size Simulation
Upon execution, the system selects only those materials that are assigned to the selected individual
material group.
Related Information
Creating Individual Material Groups [page 19]

Editing Individual Material Groups [page 20]
Deleting Individual Material Groups [page 21]
1.5.1 Creating Individual Material Groups
Context
You can create new individual material groups as follows:
Procedure
1. Call transaction /n/SAPLOM/X_IND_MGROUP.

2. Enter your selection criteria in the Analysis Area section.
3. Enter a name for the material group to be created.
4. Choose Import Data.
A dialog box is displayed in which you can enter a description for the new individual material group.
5. Enter a description and choose the green checkmark.
The preview of the materials to be imported is displayed.
 Caution
The materials and the individual material group displayed are not yet saved in the database at this
point.
6. If the control view displays the desired result set, choose the Import pushbutton.
The import to the database takes place.
1.5.2 Editing Individual Material Groups
Context
You can edit existing individual material groups as follows:
Procedure
1. Call transaction /n/SAPLOM/X_IND_MGROUP.

2. Enter your search parameters.
To do this, you can use the upper selection area, or enter the individual material group to be edited directly
at the bottom.
3. Confirm your selection by choosing Execute ( ).
The editing screen is displayed with the selected data.
Screen for Editing an Individual Material Group
4. Make the relevant changes to the data.
5. Save your changes.
Results
 Caution
If you delete all of the items for an individual material group, the material group key (/n/SAPLOM/
X_MGP_C) is deleted automatically.
1.5.3 Deleting Individual Material Groups
Procedure
1. Open the editing transaction /n/SAPLOM/X_IND_MGROUP.

2. In the lower area, specify the individual material group that you want to delete.
3. Choose the Delete Material Group button.
Deleting Individual Material Groups
1.6 Alerts
Using alerts enables you to extend the information displayed in the SCM Consulting Solutions to include your
own exception-based information (alerts). In the following, the definition and use of alerts is shown using the
example of the MRP Monitor.
1.6.1 Creating and Editing Alerts
You can use transaction /SAPLOM/XKI_ALERT to define alerts and edit existing alerts.
Procedure for Creating Alerts
1. In the Alert Name field, enter the technical name for your alert.
2. In the Alert Description field, enter a corresponding short text
3. You can use the Intended monitor field to assign the alert to an SCM monitor, for example, the MRP Monitor
4. In the fields Condition table and Condition field, you can define the source from which the alert condition is
determined.
5. You can use the Comparison condition button to define whether
1. A comparison value or
2. A comparison field
is used as the basis for the alert condition
6. When you click the Create button, a maintenance dialog opens on the right of the screen, in which you can
define the actual alert conditions
Defining Alert Conditions
After you have opened the maintenance dialog for the alert conditions by clicking the Create button, you can
create new alert conditions.
Defining Alerts
Procedure
1. Use the Append Row or Insert Row functions to add a new alert condition
2. In the Flag column, you specify which traffic light icon is to be used for the relevant alert conditions
3. In the Coloring Option column select whether
1. There is to be no coloring
2. Only individual cells are to be colored or
3. The entire row should be colored
4. In the Option column, specify the comparison criterion; for example, GT – Greater Than (>).
5. If you have selected the Comparison condition 'Comparison value' in the alert definition, you specify the
comparison values in the Value (low) or Value (high) field. If you have selected the comparison condition
'Comparison field', you can define the relevant comparison fields using the fields Table of lower value and
Field of lower value or Table of higher value and Field of higher value.
6. Then maintain the tasks linked to the alert in the fields Task ID and Task Object.
7. In the Comment field, you can enter a comment.
8. In the Date field, specify a date for the tasks add-in.
9. Save the alert and the associated alert conditions by clicking the Save Alert button.
Defining Alert Conditions
Add other alert conditions, as required (for example, red, yellow, green).
Comparison Value:
Selecting the Comparison condition 'Comparison value' when defining an alert enables you to specify the
comparative values with which the system compares the field value of the field specified in the condition table
directly in the alert conditions.
Comparison Field:
If you have selected the Comparison condition 'Comparison field', you specify a table field in the alert
conditions. The system then compares the value of the specified comparison field with the value of the field
defined in the condition table.
Maintaining Existing Alerts
To maintain an alert that has already been created, double-click the relevant alert.
Maintaining Alerts
This selection displays the detailed information on the alert in the upper part of the screen, where it can be
maintained. After you have made the desired changes, save them by clicking the Save Alert button.
1.6.2 Creating and Editing Alert Profiles
You can use transaction /SAPLOM/XKI_PROFIL to define new alert profiles or maintain existing alert profiles.
Creating an Alert Profile
To define a new alert profile, use the New Entries (F5) function and enter the technical name (key) in the Alert
Profile column and the short description of the alert profile in the Alert Description column and press the Enter
key.
Creating an Alert Profile
Assigning Alerts to the Alert Profile
Select the defined alert profile and double-click on the Alerts folder. Using the New Entries (F5) function, you
can now assign alerts to your alert profile.
Changing Alerts
In the Alerts column, you specify the alerts used in the profile. In the Bgnd Proc. column, you define whether
the relevant alert is to be checked during background processing.
Editing Existing Alert Profiles
You can use the Change (Ctrl+F4) function to maintain existing profiles. Use the same procedure as you would
to create a new alert profile.
Connection to the SAP Transport System
Creating/changing alert profiles is a configuration activity. Consequently, there is a connection to the SAP
transport system. Depending on the settings in your system, you will therefore be prompted to select a
transport request when you save the settings.
1.6.3 Using the Alert Profile in the MRP Monitor
On the selection screen of the MRP Monitor, you can specify an alert profile in the Alerts section on the Result
tab. This profile is used for the analysis.
Using an Alert Profile
You can use the radio button Collect all alerts to one column or one column for each alert to specify whether a
separate column is displayed for each alert in the results displayed or whether all alerts are to be displayed in
one column. In the example, the one column for each alert option was selected.
Alert Profile in the MRP Monitor
In the output table, multiple columns are displayed with the heading Alerts. By double-clicking on the individual
alerts, you receive detailed information on the relevant alerts.
Alerts in the MRP Monitor
1.6.4 Combined Alerts
Combined Alerts
Besides the two alert options
• comparison of field content with a threshold value and

• comparison of two field contents,
you can also combine existing alerts as of Release 2022. A third comparison option with "Combined Alert" is
available for this purpose.
You can use this comparison option to link existing alerts using AND or OR conditions, and create a new alert
on this basis. You can also use parentheses to group the alerts with regard to the conditions.
 Example
You have defined one alert for the range of coverage and another for the replenishment lead time. You can
use the "combined alert" comparison option to link the two alerts using an AND condition.
1.6.5 Formula-Based Alerts
Formula-Based Alerts
You can use a formula-based alert to display an alert in the result view based on a formula result.
 Example
You use formulas in an SCM consulting solution that contains the following two columns:
• Replenishment Lead Time
• Average Daily Usage
You create a formula in which you determine the expected demand within the replenishment lead time
using the following calculation:
Replenishment lead time * average daily usage
You also create an alert for which you compare the formula result, which in this case is the expected
demand within the replenishment lead time, with the current stock.
If you assign this alert to an alert profile and the formula to a formula profile and store both profiles in the
aforementioned SCM consulting solution on the selection screen, the formula-based alert is displayed in
the result list of the SCM consulting solution.
1.7 Formulas
Using formulas and formula profiles enables you to extend the information displayed in the SCM Consulting
Solutions to include your own calculated formula values In the following, the definition and use of formulas is
shown using the example of the MRP monitor.
1.7.1 Creating and Editing Formulas
You can use transaction /SAPLOM/XMM_FORMULA to define new formulas and edit existing formulas.
Procedure for Creating Formulas
1. Choose the Change pushbutton to switch to edit mode.

2. Add a new formula line.
3. You can now enter a unique formula key and add a description. The description is visible in the logon
language. To add a further description, log on in the relevant language.
4. Select the appropriate result category.
1. Quantity type for numeric formula results with decimal places
2. Numeric type for numeric formula results without decimal places
3. Currency type in the currency selected for results of formulas
4. Blank is only available when entering the formula.
 Caution
Note that you must select one of the three categories a - c.
5. Define your formula. To do this, you can use the following elements:
1. Mathematical operators for addition, subtraction, multiplication, and division. To do this, use the
characters: + - * /
2. Numeric operands: You can use number values such as 1, 2, 3 for your formula.
3. Material master fields as operands: For your formula, you can use the result values of the consulting
solutions for the further calculation. Examples of this are: EISBE for the safety stock, EXINDI1 for the
content of the special case indicator 1 on the SCM CS tab of the material master, or SCHNITG for the
average consumption per day. An example of the result structure of a consulting solution is /SAPLOM/
MRP_S_RESMAX of the MRP monitor.
 Caution
Note that a space must be set between the individual expressions.
6. Then save your entries using the pushbutton in the header bar.
Procedure for Editing Formulas

2. Select the cell whose content is to be adjusted.
3. Perform the desired modification.
Procedure for Deleting Formulas

2. Select the column of the formula that is to be deleted.
Sample Formula Definitions
1.7.2 Creating and Editing Formula Profiles
You can use transaction /SAPLOM/XMM_FORMPRF to define new formula profiles or maintain existing
formula profiles.
Creating a Formula Profile
To define a new formula profile, use the function New Entries (F5) and enter the technical name (key) in the
column Formula Profile, and the short description in the Formula Profile Description column. Then choose the
Enter key.
Create Formula Profile
Assignment of Formulas to Formula Profile
Select the defined formula profile and double-click on the Formula folder. Using the New Entries (F5) function,
you can now assign formulas to your formula profile.
Assign Formulas
Editing Existing Formula Profiles
You can use the Change (Ctrl+F4) function to edit existing formula profiles. Use the same procedure as you
would to create a new formula profile.
Connection to the SAP Transport System
Creating/changing formula profiles is a configuration activity. Consequently, there is a connection to the SAP
transport system. Depending on the settings in your system, you will therefore be prompted to select a
transport request when you save the settings.
1.7.3 Using the Formula Profile in the MRP Monitor
On the selection screen of the MRP monitor, you can specify a formula profile in the Formulas section on the
Result tab. This profile is used for the analysis.
Apply Formula Profile
The output table displays the relevant columns with the formula name as the heading.
Formulas in the MRP Monitor
1.8 Planning with Key Figures
With the 2022 release, a very extensive enhancement has been introduced in the tool: Planning with flexible key
figures. The advantage of using key figures is that additional rows are available per planning unit (for example,
material and plant), in addition to the normal forecast result. Here you can, for example, enter manual
corrections for the forecast, as well as perform calculations. Users can create simple calculations with a
formula module; for complex calculations, a BAdI is also available, with which calculations can be programmed.
It is also possible to display different historical and forecast values in the key figures. All sources that are also
supported by FMO are possible here.
1.8.1 Programming the BAdI Interface for Key Figure
Calculation
If you want to perform a calculation using a BAdI, a separate BAdI implementation must be written for each key
figure profile. This has the advantage that key figures that happen to have the same name in different key figure
profiles can still be calculated differently. In some cases, more factors may have to be taken into account for
the calculation in one profile than in another. The BAdI is called /SAPLOM/XKI_BADI_KEYFIGURE_CAL and an
implementation can be created using transaction SE18 or using FMO Customizing. It is important to set the
filter for the parameter KEYFIGURE_PROFILES, and to select the profile name of the desired key figure profile
as the filter value. This is the only way to make an assignment.
The BAdI has two calculation methods.
CALC_WHOLE_TABLE
The method is used to calculate all key figures in the selected key figure profile that have been assigned the
calculation method “BAdI”. The following values can be transferred to the method:
Parameter Type Content
IM_TOOL Importing Abbreviation of the SCM Consulting

Solution. Here “FMO”
IM_STRUCTURE Importing Structure of the output table in FMO,

here /SAPLOM/FMO_S_DISPLAY
IM_PERIODS Importing Contains the period information of the

columns, here type /SAPLOM/
XT_PERIODS_IN_COLUMNS
T_TABLE Changing Contains the complete output table

with all values. All values can be used
and changed in the BAdI. However, only
the values for which the key figure cal
culation was set to "BAdI" are transfer
red in FMO.
ON_DOUBLE_CLICK
You can use the method ON_DOUBLE_CLICK to program a method for if someone double-clicks on a line. In
the key figure profile, you can define for which key figure this double-click is to have an effect.
Parameter
IM_TOOL Importing Abbreviation of the SCM Consulting

Solution. Here “FMO”
IM_STRUCTURE Importing Structure of the output table in FMO,

here /SAPLOM/FMO_S_DISPLAY
IM_PERIODS Importing Contains the period information of the

columns, here type /SAPLOM/
XT_PERIODS_IN_COLUMNS
IM_ROW Importing Contains the line number in which the

double-click was made
T_TABLE Changing Contains the complete output table

with all values. The BAdI can then be
programmed individually, to, for exam
ple, read the material number of the se
lected line, select the corresponding
sales orders for the period, and display
them in a dialog box.
1.8.2 Working with the Formula Editor
If you want to include key figures that are calculated mathematically, you have the option of using predefined
formulas with a formula editor. Alternatively or in addition, a BAdI can be programmed. Both options can be
used simultaneously within a key figure profile, but you must restrict yourself to one option for each key figure.
The FMO tool first processes the calculations using the formula editor, then the calculations using the BAdI.
The calculations are performed after each entry in the planning table, for example, by choosing the "Enter" key.
You can use transaction /SAPLOM/XKI_KPIMAINT to call the formula editor.
You can now enter new formulas or change existing ones. The following points must be taken into account:
Basic Semantics:
• Space between arithmetic operators and statements and formulas

• Basic arithmetic operations are allowed
• Numbers can be written normally, but with spaces before and after
• Addressing a single cell: KPI line in apostrophes
• If parentheses are used, leave a blank space before and after the parenthesis
Example: 5 + 10 – 8
Example: 15 * 'CONSUMPTION' - 3
Example: 10 * ( MOVEAV ( 'FORECAST' , 1 , 2 ) + 5 * 'CONSUMPTION' )
Formula Semantics:
Moving Average: The moving average of the selected KPI is calculated; the
first number indicates the number of past periods to be in
Moveav ( KPI Row, Number of Columns Looking Back, Num cluded and the second number indicates the periods in the
ber of Columns Looking Forward ) future that are to be included
MOVEAV ( 'FORECAST' , 1 , 2 )
Year to Date: All periods of the mentioned KPIs of a year are summed up
until the current period is reached
YEARTODATE ( KPI Column )
YEARTODATE ( 'CONSUMPTION' )
Year to Year: All periods of the last 12 months of the KPI are summed up
YEARTOYEAR ( KPI Column )
YEARTOYEAR ( 'CONSUMPTION' )
Accumulation: All periods of the KPI are totaled, up to the current period
ACC ( KPI Column )
ACC ( 'CONSUMPTION' )
Negation: Negation of KPI column
NEW ( KPI Column )
NEG ( 'FORECAST' )
MARA: The system checks whether the 'MATNR' of the KPI exists in
MARA. If so, the column specified in the formula is inserted
MARA ( Column name from MARA ) into the formula
MARA ( 'MATKL' )
MARC: The system checks whether the 'MATNR' of the KPI exists in
MARC. If so, the column specified in the formula is inserted
MARC (Column Name from MARC ) into the formula.
MARC ( 'PLIFZ' )
MARD: The system checks whether the 'MATNR' of the KPI exists in
MARD. If so, the column specified in the formula is inserted
MARD (Column Name from MARD ) into the formula
MARD ( 'LFMON' )
WORKDAYS: The working days of the current period are to be counted

and a factory calendar of choice can be selected for this
WORKDAYS ( ID of the factory calendar followed )
WORKDAYS ( 'ZJ' )
MOVE KPI: A selected KPI row is copied to the new KPI and shifted by
the specified number of periods
MOVE_KPI ( KPI column to be shifted, by how many periods
it is to be shifted )
MOVE_KPI ( 'FORECAST' , '12' )
COPY The content of a KPI is copied to a new KPI, provided that

the KPI name exists in the specified database column.
COPY (‘Key figure to be copied if its KPI is in the following
field’, ‘Name of the database and the field for the compari
son’)
COPY ( 'ACTUAL SALES' , 'MARC-DISPR' )
1.8.3 Creation of Key Figure Profile
Create a key figure profile if one does not yet exist, or if you want to create another key figure profile. This is
done using transaction /SAPLOM/XKF_MAINT - /SAPLOM/X – Kennzahlprofile, or in FMO directly, by
clicking on Key Figure Profile at the top of the switch strip.
On the entry screen, you can now click New Entry to create a new profile. This opens a small window in which
you enter the name of the new key figure profile. Later, this name is also on the left in the Profile Name column,
and you must also select this name on the FMO selection screen if you want to work with this key figure profile.
The new name is then saved and, above the table, you can click on the icon for creating a new line to add the
first key figure to the profile. You can do this until there are sufficient key figures in the profile.
Make the following settings in the key figure profile:
Description This description is later displayed as a key figure description in FMO. It helps the user understand the purpose of the
Calculation You can enter the following values here:
• Formula calculation with /SAPLOM/XMM_FORMULA (FORMULA)

• In this case, the key figure is to be calculated using a formula. You can use transaction /SAPLOM/MD04 to c
tered in the column “Formula”
• Calculation using BAdI (BAdI)
• In this case, the key figure content is calculated using a BAdI, which must be programmed by the customer
• Tool-specific display/calculation of contents (TOOL_SPE)
• Key figures can also display additional historical or forecast data. For example, in FMO a forecast could be ca
also wants to view the sales orders in the past and the future in an additional key figure.
• No calculation, free input, and saving (NONE)
• No key figure is calculated place here, but manual entries are possible. These are also saved in a database ta
• No calculation, only read from the database (READ_ONL)
• No entries are possible here and nothing is calculated. The key figure is useful if an independent customer p
displayed here.
Formula Here you can specify a formula for calculating the key figure. This is only necessary if the calculation logic is set to "Fo
Tool-Specific Here you can select which historical or forecast data is to be displayed. An entry is only necessary if the calculation of
calculation of key figures, the tool-specific values are only taken from the database once and then displayed. If there a
executed again to display them.
Version If the calculation logic is set to TOOL_SPE, and if you have selected a data source in the column “Tool-Specific”, for wh
here. This is necessary, for example, for info structures, or for requirements in PBED (MD62), or for history numbers
Double Click If you select the field, if it exists and has been programmed, a BAdI is called when you double-click on the key figure, t
what should happen in the BAdI. For example, a popup with information about sales orders for the selected material c
the subsection “Calculation of Key Figures – Programming the BAdI Interface for Key Figure Calculation”.
DO_SUM If you select this, the values of this key figure are added together in a separate totals column at the end.
AVERAGE If you select this, the average of the values of this key figure is displayed at the end in a separate average column.
Color Here, you can select different colors that the key figure will have later.
1.9 Layout Groups
Layout groups allow specific adjustment of the layout in many SCM Consulting Solutions.
1.9.1 Using Layout Group Profiles
Layout group profiles allow specific adjustment of the layout in many SCM Consulting Solutions. In the
following, the use of the layout profile groups is shown using the example of the MRP monitor. On the initial
screen of the MRP Monitor, a layout group profile can be selected in the Output control section of the
Materials select tab.
Layout Group Profile
In the result view of the MRP Monitor, you can adjust the layout. You can use the Change Layout function to
select the fields displayed in the result table.
Result List
You can now use the filter to select the field groups defined in the layout group profile and include the
corresponding fields in the layout.
Filter Options
1.9.2 Creating Layout Profiles and Configuring Layout Groups
You can define and configure layout profiles using transaction /SAPLOM/X_LAYOUTGRP. You first create a
layout group profile, to which you then assign one or more layout groups. Next, you assign the fields to be used
within the layout to the individual, defined layout groups.
Creating/Changing a Layout Group Profile
You use transaction /SAPLOM/X_LAYOUTGRP to display the maintenance dialog for the layout group profiles.
On the left of the screen, select the Profile folder. You can use New Entries to define a new layout group profile,
or you can use Change to adjust an existing layout group profile. Because maintaining the layout group profile
involves configuration settings, it is connected to the SAP transport system. Layout group profiles should
therefore be maintained in the development system and transported to the follow-on system via the SAP
transport system.
Creating a Layout Group Profile
Specify the technical description of the layout group profile in the Layout group profile field and enter the
desired profile description in the Profile Description field. Then use the dropdown list in the Monitor field to
assign the layout profile to the relevant monitor and use the F4 selection help in the Table Name column to
select the relevant table for the MRP Monitor or the MRP Exception Monitor.
New Entries
Save your entries. Depending on the setting in your system, you may be prompted to select an SAP transport
request.
Changing an Existing Layout Group Profile
To change an existing profile, select Change to maintain the entry you selected earlier.
Creating and Changing Layout Groups
Select the row with your layout group profile and double-click the Groups folder. This takes you to the dialog for
creating/maintaining the layout groups.
Changing Layout Groups
You can define new groups and/or maintain existing groups. In the Group Key column, enter the relevant
technical name of the group (group key) and enter a short text to described the layout group in the Group
Description column. Save your entries. If necessary, you will be prompted to select an SAP transport request.
Assigning Layout Fields to a Layout Group
To assign the desired layout fields to a layout group, select the corresponding layout group and double-click the
Group Fields folder. This takes you to the maintenance dialog for assigning group fields to layout groups. Select
the relevant database table in the Table Name column and select the corresponding field from the table in the
Field Name column. Repeat this process until you have assigned all the desired fields to your group and save
your entries.
1.9.3 Translation
It is possible to translate the layout group profile description and the description of the layout group into other
languages. Select the relevant layout group profile and then select Translation in the Goto menu. You can select
the desired target language and enter the relevant description in that language.
Translation
Use the same procedure as you would to translate the layout groups.
1.10 Layout Sets
Layout sets enable users to set up your work area with predefined variants and sort criteria. This can be for all
users and user-specific.
This function is included in various consulting solutions. The following is an example of the setting in the MRP
monitor.
The variant must first be created in the relevant consulting solution.
Creating a Variant
This step does not apply if existing variants are integrated.
In the next step, create a layout set in transaction /SAPLOM/X_LS.
Creating a Layout Set
Choose the name and select the related consulting solution program name. In the MRP monitor example,
choose /SAPLOM/MRP.
Defining a New Layout Set
Assign variants to the layout set. In the Order column, you can define the sort order of the layouts on the result
screen.
Assigning Variants to Layout Sets
You can select the created layout sets in the selection screen of the consulting solution.
Selecting Layout Sets
The stored variants appear in the folder structure of the results screen. Double-clicking sorts the results list
with the variant.
Layout Set on the Results Screen
1.11 Enhanced Navigation Profile Functions
By incorporating the class /SAPLOM/XAF_NAVP, the standard navigation profile functions can be enhanced
with the following features:
• Jump to Executable Reports

• Conditional Branching
• Navigation by Double-Clicking
Prerequisites In the authorization object C_NAV_PROF Navigation Profile, in the field ACTVT (Activity) you
define whether users are allowed to carry out the following functions:
• 23 - Edit user-independent navigation profiles

• 01 - Create or change class calls
Related Information
Navigation Profiles
1.11.1 Jump to Executable Reports
To branch to an executable report such as the MRP monitor, create an entry in the navigation profile under the
folder toolbar or context menu as follows:
• 1. You create a new entry and choose class call.
Class Call
• 2. In the Text field, enter the text of the pushbutton or the context menu entry. Under Quick Info, enter the
name of the report to which you want to navigate. In the field Implementing Class, enter /SAPLOM/
XAF_NAVP. Under function parameters, you can define an optional selection variant that is to be used
when you jump to the report. Specifying a selection variant is required, when certain settings should or
must be used that cannot be determined automatically via the content of the output table for which the
navigation function is created.
Properties
• 3. You continue and save the changed navigation profile. Saving is mandatory.
 Note
When you jump to the report, all selection fields of the report that can be prefilled are prefilled. These are all
selection fields that have a SET/GET parameter and can be supplied with values via the output table for
which the navigation function was created.
If you only want to prefill certain selection fields, proceed as follows:
• 1. Under the folder Context Menu, you create a new entry and choose transaction call.
Transaction Call
• 2. In the field Text and Transaction, you enter the name of the report to which you want to navigate. Under
SET/GET Parameter ID, enter the name of the selection fields that are to be supplied with values. Under
Field Name, enter the name of the corresponding fields from the output table which provide the values.
Alternatively, enter a fixed value.
SET/GET Parameter
• 3. You continue and save the changed navigation profile. Saving is mandatory.
1.11.2 Conditional Branching
Conditional branching is required if, depending on the values of a field in the output table, you want to prefill the
selection fields of the report to which you branch with different values. For example, if you have an output table
with different MRP elements, that is, purchase orders, purchase requisitions, production orders, sales
documents, and so on, the type of the MRP element in a column DELKZ is defined, and with the purchase
requisitions and purchase orders you want to branch to a report to analyze purchasing documents, you can
proceed as follows:
1. Under the folder context menu, you create a new entry and choose transaction call.
2. In the field Text and Transaction, you enter the name of the report to which you want to navigate. Under
SET/GET Parameter ID, enter the name of the selection fields that are to be supplied with values. Under
Field Name, enter the name of the corresponding fields from the output table which provide the values. In
the field Parameter Fixed Value, you enter the condition. In the example: If a row of the output table has the
value BA in the column DELKZ, the selection field P_BANFN should be prefilled with the value from the
column DELNR (contains the purchasing document number); if the column DELKZ has the value BE, the
selection field P_EBELN should be prefilled with the value from the column DELNR.
3. You continue and save the changed navigation profile. Saving is mandatory.
SET/GET Parameter
1.11.3 Navigation by Double-Clicking
You can install navigation via double-clicking for selected columns of the output table. For example, if you want
to jump to MD04 when double-clicking on the plant, you can proceed as follows:
• 1 You create a transaction call or class call under the folder Context Menu.
Example: Transaction Call
Example: Class Call
• 2. You continue and save the changed navigation profile as a default. It is mandatory to save the navigation
profile as a default.
 Note
If you implement the double-click navigation via the class call, you can navigate using multiple entries,
provided that the report to which you navigate supports multiple selection. For this, select several rows in
the output table. While holding the CTRL key on your keyboard, double-click on the column header.
Multiple Selection
1.12 Save current stock/requirements list
Save the current stock/requirements list for one or more materials. This makes it possible to create a history of
the planning situation and calculate key figures based on this data.
This function is part of the comprehensive functions of SCM Consulting Solutions. To save the current stock/
requirements list, start transaction /SAPLOM/XMD.
Related Information
Data Processor
1.12.1 Save Data
To save the data, choose the action Save. You also have additional input options available for the planning
scenario, selection rule, and display filter.
 Note
You can create selection rules and display filters in system Customizing under the following path: Materials
Management → Consumption-Based Planning → Evaluation → Filter
Save Data
These options allow you to define the data basis of the stock/requirements list. For further technical settings
for saving, see the Settings [page 50] tab page.
Related Information
Settings [page 50]
1.12.1.1 Material Selection
In the material selection, you define the criteria used to determine the materials. You can choose from different
material master fields, and other fields of the SCM CS material master tab. You can also select all materials with
an SCM planning file entry.
Material Selection
The option Only mat with SCM PFcauses only materials with an existing SMC CS planning file entry to be
selected. If the IQR enhancement is active, you can also restrict the material selection to specific networks. For
more information, see Inventory Quality Ratio in the documentation for the inventory controlling cockpit
consulting solution.
In addition to the standard fields of the material master, additional fields are available for selection on the
Material Enhanced tab page. Here, you can restrict the material selection further, using the fields of the
enhanced material master.
Related Information
Documentation for the inventory controlling cockpit consulting solution

Inventory Quality Ratio
1.12.1.2 Settings
On the Settings tab page, you define additional technical settings.
Settings
Profile: Customer-specific extensions or other adjustments can be determined by a profile. This profile is
defined in XMD Customizing. You can select this in the settings, so it is considered during execution.
Delete Old Data: Activate this option if you only want to keep the most current stock/requirements list. If this
option is active, old data is deleted automatically, so that a separate deletion job is not necessary.
Import Options/Data Storage: Depending on the use case, not all possible data of the stock/requirements list
needs to be determined. If possible, only the data that is actually required/saved should be saved. This allows
the runtime to be kept as low as possible. You can find out which data is required from the corresponding
description of the data processor. Many data processes enrich the raw data of the stock/requirements list. If
you use the save function as an addition/replacement for the classic MRP list, you should determine and save
at least the raw data and the formatted data. To keep the volume of data to be saved as low as possible, you can
deactivate data parts that are not required. For example, in many cases it is not necessary to save the period
totals. It is also possible to store the data in compressed form in the database. If your system is based on a
HANA database, you should, however, do without the compressed data storage since in this case the integrated
compression of the HANA database is the better alternative.
You can also assign a job name. The job name is displayed in the input help for the historical data. If this field
remains empty, the actual name of the background job (if available) is used. This allows you to see which data
was created with which job. Note, however, that the data continues to be selected with the creation date of the
historical data, regardless of the job name.
No dep. MRP elements (only CB): If this function is active, no dependent requirements are taken into account
for materials with reorder point planning, forecast-based planning, or time-phased planning.
Force BAdI Execution: If you have implemented the BAdI MD_ADD_COL_EZPS and thereby enable optional
additional columns, you can force execution of the BAdI. This is necessary if your implementation only has
optional execution. In this case, you can activate the checkbox to force the execution, so that the values of the
additional columns are available.
Package Size: For large volumes of data or in the event of performance issues, it may be necessary to process
the materials in smaller packages. Since the optimum package size depends on a number of factors, there is no
general recommendation for a value. It may be necessary to start several attempts to reach an optimum
package size.
Utilization & Logon / Server Group: The data in the stock/requirements list can be determined in parallel
processes. In the case of parallel processing, enter at least one server group (or 'NONE'), otherwise
synchronous processing is used automatically to prevent the system from being overloaded without regulation.
Check & Delete: Deactivate this function if you can ensure that no data exists for the selected materials on the
current day. This can cause some runtime-intensive functions to be skipped.
Type of Output: Defines the type of output at the end of processing in dialog mode:
• Show application log

• List output
• No output
1.12.1.3 Optional Data
In addition to determining the stock/requirements list, you can also read or process additional data. Various
data processors are available for this purpose. You can bundle these in a profile as you wish, taking into account
the relevant use case. If such a profile is specified, the functions set for it are executed in addition to the data
determination.
To set up such a profile, see the relevant sections in the configuration.
Related Information
Data Processor
Documentation on the consulting solution comprehensive functions
1.12.2 Delete Obsolete Data
You can remove old or unnecessary data by selecting the Delete action.
If you enter a creation date, you restrict the data. You can also use the material criteria. In the Settings, you
should also specify the same profile that was active when the data was created. This enables data possibly
stored in customer-specific tables to be deleted as well.
1.13 Protection of ALV Layouts
You can use transaction /SAPLOM/XAF_P to prevent your ALV table layouts from being overwritten. To do this,
you call the above transaction, enter the report name and the names of the layouts within this report, and
execute the report.
 Note
Only layouts beginning with / are taken into account. From a technical perspective, the selected layouts are
copied, and the first character of the copied layouts, that is, the slash /, is replaced by ~. These new layouts
beginning with ~ can be deleted but not overwritten.
1.14 Solution Feedback
You can send feedback on a consulting solution to the SAP SCM Consulting Solutions team. On the results
screen of a solution, you use the navigation profile to include the following class call.
Change Navigation Profile
Create Class Call I
Create Class Call II
After you choose the green checkmark, a new pushbutton Solution Feedback is added to the application
toolbar. When you click this new pushbutton, a new Outlook email opens, in which the addressee, subject, and
transaction from which you called the solution feedback are prefilled. Enter your feedback and send the mail.
Solution Feedback Email
1.15 Default variants
You can save a default variant for the transaction of the consulting solution. This variant will be loaded
automatically every time you open the tool. There are two types of default variants available:
System-wide variant, valid for all users
If a variant exists with the same name as the transaction code (including /SAPLOM/), this variant will be the
default for all users who start the tool, unless they have a user-specific variant saved on the same system.
Normally system-wide variants are used to provide a predefined set of values that can enhance usability if, for
example, certain fields like plant, currency or time will be pre-populated. The user can change these values any
time before executing the program.
User-specific variants
If a variant exists with the following naming convention U_<username>, then this variant will be defaulted for
this specific user if they start the tool.
 Example
A user with a logon name of JSMITH would save his own variant like this: U_JSMITH
This, too, can enhance usability, because certain fields like plant, currency or time can be pre-populated for a
specific user. The user can change these values any time before executing the program. Although each user
can have only one predefined variant per system, the variant can be overwritten with new values.
1.16 Autostart
You can create one or more autostart transactions for each executable /SAPLOM/ transaction with a selection
screen. An autostart transaction is a copy of the original /SAPLOM/ transaction with specific naming. You link
an autostart transaction to a selection variant that follows the naming of the autostart transaction. When an
autostart transaction is called, the selection variant is loaded automatically and the transaction is executed
automatically.
You use transaction /n/SAPLOM/XAF_A to create one or more autostart transactions initially. To do so, you
define the transaction(s) to be copied, for example, /SAPLOM/ERM, and the number of autostart transactions
to be generated, for example, 2.
Autostart Transaction Generator
Run the program. Two autostart transactions are created: /SAPLOM/ERM_AS01 and /SAPLOM/ERM_AS02.
Call the original transaction /n/SAPLOM/ERM and define a variant with the ID 01. If you now call the
transaction /n/SAPLOM/ERM_AS01, the variant 01 is used automatically and the transaction is run
automatically. For /SAPLOM/ERM_AS02 you define the variant 02.
In addition to a global variant, which has the numbers from an autostart transaction (after the "AS"), you can
also define a user-specific variant that overrides the global variant. Say user XYZ wishes to call transaction /
SAPLOM/ERM_AS01 with a user-specific variant. User XYZ calls /n/SAPLOM/ERM and defines the variant 01
here, followed by their SAP logon name, for example, 01XYZ. If they now call transaction /n/SAPLOM/
ERM_AS01, variant 01XYZ is used instead of variant 01.
1.17 Report for Order Relation
You can access the preliminary report for order relation by calling transaction /SAPLOM/XCL.
Generate and Save Order Relation
XCL supports two levels of analysis.
Work Center Analysis Level:
You define the plants and work centers for which you determine orders that you want to check for missing
parts. You can also define whether the stocks are available depending on the storage location with the
corresponding time offset and whether partial lots are to be created for requirements and receipts. XCL
analysis results at work center level are used, for example, in the production supervisor view of the MRP
exception monitor, where planned orders and production orders with and without missing parts are displayed
for each work center.
Material Analysis Level:
You define the materials whose requirements you want to link to stock and receipts. XCL analysis results at
material level are used, for example, in the Transport Planner, where available quantities from the issuing plant
are displayed in a stock transfer scenario.
By specifying a selection rule, you can restrict the selection of the MD04 data by time. You can also use the
selection rule to define which MRP elements you want to take into account and whether you want to consider
the safety stock.
You can also define whether the stocks are available depending on the storage location with the corresponding
time offset and whether partial lots are to be created for requirements and receipts.
1.17.1 Flow Logic
In the first step, the system uses the selected work centers and their capacity requirements for planned and
production orders to read the reservations and determine the related material numbers. This first step is
omitted at Material analysis level.
In the second step, the MD04 is read for each material according to the predefined selection rule, and receipts
and requirements are determined. At Work Center analysis level, depending on the setting, the receipts (that is,
supplying orders) and requirements (consuming orders) of each material are divided up into partial lots.
The assignment logic is then applied. First, open requirements are assigned to stocks. If the time offset for
storage location option is active, stocks are only available with the corresponding time offset (see configuration
for time offset). After the stocks have been used up, the requirement quantities that are still open are assigned
to the receipts according to the first-in first-out principle, that is, the earliest requirement is assigned to the
oldest receipt. If the receipt date is later than the requirement date, the relevant assignment is assigned a
backward edge alert.
Based on the assignment table /SAPLOM/XCL_PEGG, the component table /SAPLOM/XCL_KOMP and order
operation table /SAPLOM/XCL_AFVO are determined.
1.18 Unified Planning Center
The Unified Planning Center (UPC) allows you to display data stored in the S/4HANA database from the SCM
CS or other SAP tables in a central app in the Fiori Launchpad. For the display of data, you can define hierarchy
levels that can be used as part of a drilldown in the detail data of an analysis.
The XAC profiles form the basis for displaying data in the UPC; these XAC profiles are grouped and
hierarchized in a UPC profile in the administration app of the UPC. For more information about XAC profiles,
see the Configuration Guide for the comprehensive functions of SCM CS at Cross-Application Data
Acquisition.
To be able to use UPC, the following minimum system requirements are necessary:
SCM CS Release 2021
S/4HANA Release (OnPremise) 1709

or higher
SAP Gateway Component 752
(SAP_GWFND)
SAP Fiori Front End Server 4.0
SAPUI5 Version 1.66.0
UPC Admin App
Unified Planning Center (UPC)
For more information about the UPC, see the PDF documentation provided with the delivery.
Related Information
Cross-Application Data Acquisition

Documentation on the consulting solution comprehensive functions
1.19 Excel Upload/Download
Download and upload editable ALV to Excel
An ALV that can be edited with the Excel download and upload has two corresponding buttons in the ALV
toolbar.
If you choose the Excel Download button, the current ALV is downloaded to an Excel file. To do this, you must
first define a storage location and a file name.
The fields can then be edited in Excel. After saving and closing the file, you can use the Excel Upload button to
reload the data to the ALV.
This simplifies the function of the editable ALV.
Important:
• Only cells that can be edited in the ALV are changed during the reupload. All other cells are ignored.
• Cells that are filled outside the table in Excel are ignored.
• It is not possible to create a new line.
• If formulas or references to other cells are used in Excel, the formula must be replaced by the result for a
correct upload. The easiest way to do this is to copy the affected cells and reinsert them in the same place,
but use the "Values (W)" insertion option. The Excel upload can then identify the results of the calculations
without problems.
• The Excel table must not be resorted between download and upload. Neither the columns nor the rows
may be resorted, otherwise no exact assignment can be made during the upload.
• If a data record is changed in a standard transaction during downloading, this change remains and the
Excel upload will not overwrite this change, unless the relevant column is also edited and changed in
parallel in the Excel upload.
1.20 Action Flows
Action flows form the basis for individual cross-tool functions and can be integrated in various ways. They offer
a high degree of reusability and adaptability. You can change or enhance existing action flows, and create your
own flows.
1.20.1 Overview
The general action flows provide a way of making functions available across tools. An action flow always
consists of several individual steps. Each of these steps can be configured and changed separately. This
enables the entire action flow to be adapted to your own requirements. This allows you to include additional
steps, for example, to insert special authorization checks. You can access predefined steps, or develop new
steps by implementing the interface.
An action flow that has been defined can be included at various points. It is possible to include it in the ALV Grid
toolbar of a tool, and to link it to a defined solution proposal from proposal management. Since an action flow
can also execute a different flow, an existing flow can also be extended for a specific application area, without
having to change the original action flow. The flexible reuse options mean that a flow can be adapted and
enhanced specifically for each usage area.
Depending on the application, the log can be viewed after the action flow has been completed.
1.20.2 Concept
An action flow consists of at least one or more action steps. Only one action flow is executed as a whole; the
individual action steps are executed automatically in the specified sequence, but they cannot otherwise be
executed individually. Action flows, in turn, can be grouped in action profiles. These form logical groups of flows
and can be included in a supporting tool to make the action flows contained therein available to the user.
When an action flow is executed, a distinction is made between two modes:
• Single-line execution
• Multiline execution
The mode is defined for each action flow in Customizing, and can have more or less of an effect, or no effect at
all, depending on the flow.
The single-line execution executes an action flow once for each selected row. If three lines are selected, a flow
is executed three times in total. Execution is separate for each line and, above all, in isolation.
The multiline execution always executes an action flow once only, but for all selected rows.
The differences between the different execution modes are explained below using scrapping as an example.
The underlying action flow has only one step and creates a goods movement for scrapping stock quantities. In
single-line execution for which three lines are selected, three separate material movements are posted and
therefore three material documents are also entered. In multiline execution, the three selected lines are
combined as three items in one material movement, and only one material document is entered. This means
that when you enter material movements, the mode has less of an effect on how the document is entered.
Other action steps, such as the creation of a report folder, only support multiline execution. And other steps are
affected only minimally or not at all by the respective mode, for example, executing an MRP run.
1.20.3 Available Action Steps
The following is a list of the default action steps available. In principle, all action steps can be used in any
combination and sequence. However, note the specific dependencies and special features. Any details can be
found in the respective description of the action step.
In addition to the default action steps available, there may also be other tool-specific or customer-specific
steps. Self-developed action steps can also be used.
1.20.3.1 Support Functions
Overview of the action steps available in the support functions area.
Authorization Check (/SAPLOM/CL_XAC_ACT_AUTH_CHECK)
Performs an authorization check on a predefined authorization object. The result of this check (authorization
exists: Yes/No) can then be processed by a subsequent action step (for example, termination of further
execution). In the case of multiline processing, each line is checked individually. The check only counts as
passed if there is authorization for all rows.
Execute Calculation (/SAPLOM/CL_XAC_ACT_CALCULATE)
Performs any calculation and provides the result for subsequent action steps. The calculation is specified as a
formula. This does not necessarily have to be a mathematical formula; various data can also be merged or
logical conditions checked. If this action step is executed as part of multiline processing, the result must be
aggregated according to a method to be specified.
Execute Commit (/SAPLOM/CL_XAC_ACT_COMMIT)
Executes a COMMIT.
Cancel Action Flow or Skip Step (/SAPLOM/CL_XAC_ACT_COND_EXIT)
Cancels the current action flow or skips the next X steps if the specified condition is met. In multiline
processing, only one row must fulfill the condition to abort or skip. If a complex condition is required, this can
also take place as a separate calculation step in advance (see Execute Calculation).
Make Conditional Change to Data in Action Flow (/SAPLOM/CL_XAC_ACT_COND_MD)
This action step behaves in the same way as the action step Change Data in Action Flow. However, you can
also define a condition here. The new value is only stored if the condition is fulfilled.
Change Data in Action Flow (/SAPLOM/CL_XAC_ACT_CONTENT_MDF)
Stores a value for later use.
Display Cross-Application Data (/SAPLOM/CL_XAC_ACT_DISP_CADATA)
Using Cross-Application Data Provisioning, it is possible to make any data available (see Cross-Application
Data Acquisition). This data can then be called with the corresponding XAC profile ID, and is displayed in a
popup by this action step. In addition, an action profile can be assigned to each XAC profile so that different
actions can be executed there in relation to the context. This step is not possible during background
processing.
Output Message Log (/SAPLOM/CL_XAC_ACT_DISP_PROTO)
Displays all messages that have been raised so far in the action flow. This step is not possible during
background processing.
Display Cross-Application Report Folder (/SAPLOM/CL_XAC_ACT_DISP_XBR)
TBD This step is not possible during background processing.
Execute Action Flow (/SAPLOM/CL_XAC_ACT_EXEC_ACTION)
Executes a predefined action flow. This makes it possible to encapsulate smaller action flows in a large action
without having to adjust the smaller flows where applicable. The log of the execution is transferred to the log of
the calling action flow.
Grid Filter (/SAPLOM/CL_XAC_ACT_GRID_FILTER)
Adapts the current ALV Grid filter and thus allows you to make predefined complex filter criteria available
quickly. This step is not possible during background processing and is only possible in connection with an ALV
Grid.
Grid Layout (/SAPLOM/CL_XAC_ACT_GRID_LAYOUT)
Adjusts the current ALV Grid layout. This step is not possible during background processing and is only
possible in connection with an ALV Grid.
Grid Sorting (/SAPLOM/CL_XAC_ACT_GRID_SORT)
Adjusts the current ALV Grid sorting. This step is not possible during background processing and is only
possible in connection with an ALV Grid.
Save Message Log (/SAPLOM/CL_XAC_ACT_SAVE_PROTO)
Saves the messages that have been raised so far in the application log.
User Input (/SAPLOM/CL_XAC_ACT_USER_INP)
Opens a popup to query any user input. The values entered are then available for subsequent steps and can be
processed further. This step is not possible during background processing.
Related Information
Cross-Application Data Acquisition
1.20.3.2 Comprehensive Functions
Overview of the action steps available in the comprehensive functions area.
Check Rule Book (/SAPLOM/CL_XAC_ACT_CHK_RBOOK)
Performs a rule book check. For more information about rule book checks and the default system, see
Proposals Management [page 68]. This step does not directly display the result of the check. To do this, use
the step Display Rule Book Result below.
Display Rule Book Result (/SAPLOM/CL_XAC_ACT_CHK_RBOOK_D)
Displays the result of a previous rule book check. For this, it is essential that the "Check Rule Book" step has
been executed beforehand. This step is not possible during background processing.
Create Task (/SAPLOM/CL_XAC_ACT_TASK)
Creates a task. For more information on tasks, see Task Function [page 6].
Call Task Overview (/SAPLOM/CL_XAC_ACT_TASK_CALL)
Calls the task overview. For more information on the task overview, see Tasks Overview [page 8]. This step is
not possible during background processing.
Create Report Folder (/SAPLOM/CL_XAC_ACT_XBR)
Creates a report folder. If no report folder profile is specified, the data is downloaded as a simple Excel file. For
more information on the report folder, see the configuration guide, under General Report Folder. This step can
only be used for a multiline execution.
Related Information

Tasks Overview [page 8]
General Report Folder
Proposals Management [page 68]
1.20.3.3 Branching
Overview of the action steps available for program branching and calls.
Call Program (/SAPLOM/CL_XAC_ACT_CALL_PROG)
Calls the specified program. If set and possible, the selected data is transferred such that context-based
branching is possible.
Call SCM SAC Analysis Story (/SAPLOM/CL_XAC_ACT_CALL_SCMSAC)
Opens a preconfigured SAP Analytics Cloud story based on the analysis key. For multiline execution, only the
first line is evaluated. This step is not possible during background processing.
Call Transaction (/SAPLOM/CL_XAC_ACT_CALL_TX)
Calls the specified transaction. If possible, the selected data is transferred such that context-based branching
is possible. This step cannot be used during multiline processing.
1.20.3.4 Production Planning
Overview of the action steps available in the production planning area
Status Change for Prod./Process Order (/SAPLOM/CL_XAC_ACT_CHNG_STATUS)
Sets or deletes a user or system status in a production order or process order.
Confirm. Prod./Process Order Header Level (/SAPLOM/CL_XAC_ACT_CONF_PORDER)
Creates a confirmation at header level for a production order or process order. This step executes a COMMIT
independently.
Convert Planned Order to Prod./Process Order (/SAPLOM/CL_XAC_ACT_CONV_PLAF)
Converts a planned order to a production order or process order. The order number of the newly created order
is then available to the subsequent action steps. In the case of multiline execution, only the last order number
created is available. This step executes a COMMIT independently.
Check Material Availability for Prod./Process Order (/SAPLOM/CL_XAC_ACT_MAAV_PORDER)
Executes the material availability check of a production order or process order. This step executes a COMMIT
independently.
1.20.3.5 MRP
Overview of the action steps available in the MRP area
Check Material Availability of Planned Order (/SAPLOM/CL_XAC_ACT_MAAV_PLAF)
Performs the material availability check of a planned order. This can be done with or without BOM explosion.
This step executes a COMMIT independently.
Create Planning File Entry (/SAPLOM/CL_XAC_ACT_PLAN_FILE)
Creates a planning file entry for a material.
Execute MRP Run (/SAPLOM/CL_XAC_ACT_RUN_MRP)
Executes an MRP run for a material. This step executes a COMMIT independently.
Change/Create/Delete MRP Elements
The following is a list of different action steps for changing, creating, or deleting MRP elements. The MRP
elements supported and the changes that can be made differ depending on the function and element type.
Also note that depending on the element type, a COMMIT may be executed independently, depending on the
underlying element BAPI.
Basically, a change to the MRP element always takes place according to the same procedure. First, a logical
processing chain must be started. You can then make any number of changes to one or more MRP elements.
Finally, the processing chain is ended, with which all changes (if this has not already been done) are finally
updated. This ensures that several different changes are either only updated together or not updated at all.
Make sure that no more than one processing chain is active at any time. Therefore, complete a processing
chain before starting a new one.
Start Processing Chain (/SAPLOM/CL_XAC_ACT_XLUW_START)
Starts a processing chain. This is mandatory for all further action steps.
Close Processing Chain (/SAPLOM/CL_XAC_ACT_XLUW_CLOSE)
Completes a processing chain. This step executes a COMMIT independently. You can then start a new
processing chain again.
Change Date (/SAPLOM/CL_XAC_ACT_XLUW_DATE)
Changes the requirement/receipt date of an MRP element.
Delete Element (/SAPLOM/CL_XAC_ACT_XLUW_DELETE)
Deletes an MRP element.
Change Element (/SAPLOM/CL_XAC_ACT_XLUW_FLD)
Changes an MRP element.
Change Quantity (/SAPLOM/CL_XAC_ACT_XLUW_QTY)
Changes the requirement/receipt quantity of an MRP element.
Create New Element (/SAPLOM/CL_XAC_ACT_XLUW_NEW)
Creates a new MRP element.
1.20.3.6 Materials Management
Overview of the action steps available in the materials management area.
Display Material Document (/SAPLOM/CL_XAC_ACT_CALL_MIGO)
Calls transaction MIGO for an existing material document.
Post Goods Movement (/SAPLOM/CL_XAC_ACT_GOODSMVT)
Creates a goods movement. The number of the resulting material document is then available for subsequent
action steps. In multiline execution, the different lines are grouped as items in one material document. This
means that only one material document is ever created for each execution.
Check Material Availability (/SAPLOM/CL_XAC_ACT_MAAV)
Executes a general material availability check for a material. The result can then be viewed in the action flow
log. In the case of single-line execution, the result can also be made available as an indicator for subsequent
action steps.
Material Master Change (/SAPLOM/CL_XAC_ACT_MM_UPD)
Makes a material master change for a material. You can make changes at the level of plant, MRP area, and
storage location.
1.20.3.7 Purchasing
Overview of the action steps available in the purchasing area.
Convert Purchase Requisition (/SAPLOM/CL_XAC_ACT_CONV_PURREQ)
Converts a purchase requisition into a purchase order. In the case of multiline execution and multiple selected
purchase requisitions, they are grouped into a single purchase order. The system checks that the necessary
data (vendor, contract, supplying plant, purchasing organization, purchasing group) is compatible. If this data
for the purchase requisitions differs, processing is terminated. In single-line processing, each purchase
requisition is converted into a separate purchase order. The purchase order number is then available for
subsequent action steps.
Additional data, such as the document type, can be defined in the action step settings. An additional check of
the standard authorization objects is not required because they are already included.
1.20.4 Include Action Steps
Any number of steps can be added to an action flow. Each step contains an implementation in the form of a
class, which implements the specific instructions. It is irrelevant whether it is a class delivered in advance or a
self-programmed class. For an overview of existing classes, see the section “Available Action Steps”. For
explanations on implementing your own action step classes, see the section “Develop Custom Action Steps”.
The sequence is defined by the corresponding step ID. When you create custom action flows, it is
recommended that you leave gaps rather than numbering the individual steps consecutively. This makes it
easier to insert additional interim steps at a later stage if necessary.
Each action step, if necessary, can still be adjusted using parameters and mappings. Parameters are values
that are defined in Customizing when the action step is created. Changing the parameter value requires a
change in Customizing. Mappings, on the other hand, are dynamic values that are determined and evaluated
only at the runtime of the step. This enables you to take values from the selected data record, for example, the
material number. Each step defines whether and which parameters and mappings need to be defined for an
action step. The value help for parameters and mappings shows whether an entry is required or optional. When
posting a material movement, for example, it is necessary to define a transaction assignment. This is fixed and
must therefore be specified as a parameter. All other information (material, quantity, and so on) is defined
using mappings.
If an action flow is ready for use, there are various ways to integrate it into an existing application.
Include Using Action Profile
To make a set of predefined action flows available to the users of a tool, action flows can be grouped in action
profiles and integrated into a tool together. Various triggers are available for selection, which are used to
determine how an individual action flow can be called. For information about setting up action profiles, see the
Configuration Guide under Action Flows and Profiles Configuration Guides.
Include Using Navigation Profile
If an application uses the navigation profile and supports class calls, individual action flows can be included. For
this, create a new entry as a class call in your navigation profile. Text, icon, and quick info can be assigned
freely. Enter "/SAPLOM/CL_XAC_NAVP_ACT_FLOW" as the implementing class. The function parameter then
corresponds to the action flow ID.
Related Information
Action Flows and Profiles
1.21 Proposals Management
Proposals management allows any data records to be checked for existing problems. You can assign one or
more solution proposals directly to the problems found. The proposals contain both a description of the
solution and the option to solve the problem directly, if possible. For this, an action flow can be assigned to a
solution, which can be executed by the user. To perform a check, problems and solutions are summarized in a
rule book, which is then evaluated for checking.
1.21.1 Execute Rule Book Check
In principle, a rule book check can be executed in two ways:
• Directly when the consulting solution is executed (if supported)
• Interactively by the user using the ALV Grid
For direct execution, the rule book is specified directly on the selection screen. The specified rule book is also
evaluated during execution and the result of the check is displayed accordingly. This makes it possible to
identify the number of problems found, and the severity of the problems (for example, error, warning, and so
on). You can then click on the number of problems to view the details of the check.
If the check is carried out interactively, only the selected data records are checked. The result of the check is
displayed in the dialog box directly. Note that the underlying rule book is different from the one specified on the
selection screen. This depends on how the check is incorporated (see Include Rule Book Check [page 70]).
Related Information
Include Rule Book Check [page 70]
1.21.2 Include Rule Book Check
An interactive rule book check can be integrated in two ways:
• Integration using the navigation profile (if supported)

• Integration via action flows (if supported)
Navigation Profile
The navigation profile allows simple inclusion in each ALV Grid, which supports the navigation profile
accordingly. Proceed as follows:
1. Add a new class call in the navigation profile
2. Define desired texts and symbols

3. Select the class /SAPLOM/CL_XAC_NAVP_PPP_CHK
4. Specify the required rule book as a function parameter
Action Flow
The integration using action flows allows a deeper integration of the check than the navigation profile. However,
action flows are not available in every consulting solution. Therefore, first check whether this method is
relevant. If integration is possible using the action flows, the rule book check can be integrated into one. For
more information, see the section Comprehensive Functions [page 63].
Related Information
Comprehensive Functions [page 63]
2 Material Master Update
Save the results of your analyses in the material master.Das Materialstamm-Update ermöglicht Ihnen das
Speichern von Daten in SAP Standard Feldern und in Feldern des Enhanced Material Master View. Sie können
die Materialstammdaten direkt aus der Ergebnisliste Ihrer SCM-Beratungslösungen heraus bearbeiten.
Administration of the material master data from the results list of an SCM Consulting Solution is one of the
comprehensive functions.
If you want to adjust the material master data, select the relevant materials on the result screen and,
depending on the type of update you require, select the Flexible, Rule-Based, 2-Step, Rule-Based, Flexible Rule-
Based, or Flexible Rule Based 2-Step radio button.
If the update is to take place in the foreground, the log is displayed after the material master data has been
updated. If the update takes place in the background, you can find the log in the application log.
The following sections provide more information about how these update types work and about the results log.
Related Information
Documentation of SCM Consulting Solution MRP monitor
2.1 Overview of Update Options
The SCM consulting solutions provide different update functions. The following tables provide an overview of
the update options. For more information, see the following detail chapters for each option.
72 PUBLIC Material Master Update
Update Options 1
Material Master Update PUBLIC 73
Update Options 2
Update Options 3
2.2 Flexible Material Master Update
Using the Flexible radio button in your SCM consulting solution, you can call up the dialog box for the flexible
material master update. This gives you the option of updating or initializing selected fields by entering values
manually.
First select the materials to be updated from the result list. Then select the Flexible radio button. Using the
dialog box for the flexible material master update, you can update different fields. The fields are arranged on
tab pages in the same way as in the material master. The values entered here are filled accordingly or initialized
for all selected materials. A selection box is available for initialization, to enable a field that is not filled to be
distinguished from a field that is to be initialized.
The documentation on configuring the comprehensive functions contains a section on configuring the dialog
box for the flexible material master update.
Dialog Box for Material Master Update
Some SCM consulting solutions already offer the option of specifying an Update Profile on the selection screen.
You can create this profile in the configuration of the comprehensive functions.
There is also a Function Profile. There, you can define which columns from the results table are available for
updating selected material master fields. These are then displayed in the dialog box next to the field as a
dropdown box.
Related Information
Configuration of comprehensive functions
2.3 Rule-Based Material Master Update
You can update material master data automatically using defined rules. This function is available as a radio
button in the result lists.
First select the materials to be updated from the result list. Then select the Rule-Based radio button. The
program searches for a suitable rule for each result line selected. If a rule is found, the values maintained in this
rule are adopted for the corresponding material.
The rule is selected based on the evaluation sequence.
 Example
If a material fulfills the conditions of rules 3 and 5, the rule with the lower number is used, in this case rule 3.
This rule is evaluated and the material master is updated according to the rule.
You can decide whether processing takes place in the Dialog or Background Mode [page 80].
For instructions on how to maintain rules, see the documentation on Maintaining Rule Sets [page 81].
Related Information
2.4 Two-Step Rule-Based Material Master Data Update
Here you have the option to check the rules proposed by the program and preview the new values before the
update.
If you select the 2-Step, Rule-Based radio button, rules are found for each selected result line based on the
conditions defined in transaction /SAPLOM/XMM_RULE. These rules are displayed to you in a dialog box. The
system proposes the rule with the smallest evaluation sequence. This rule would also be used for the rule-
based material master update.
In the right-hand section of the table, the system color codes the fields that are changed when this rule is
executed. You can now select the suitable rule for each material, or retain the current setting. If you specify a
change reason, this is later displayed in the log.
 Example
The figure below shows that the two-step rule-based material master update was started for multiple
materials.
Two-Step Rule-Based Material Master Update
If you have selected the rule you require, the data is updated in exactly the same way as the automatic update.
In a subsequent dialog box, you can choose Dialog or Background Mode [page 80].
For instructions on how to maintain rules, see the documentation on Maintaining Rule Sets [page 81].
Related Information
2.5 Flexible Rule-Based Material Master Update
You can update material master data automatically using defined rules. This function is available as a radio
button in the result lists. In contrast to the rule-based material master update, for which the rules are selected
using the evaluation sequence or the rule restriction on the results tab of the selection screen, you can restrict
the relevant rules again during the flexible rule-based material master update.
First select the materials to be updated from the result list. Then select the Flexible Rule-Based radio button. A
window for selecting the rules opens. You can make a selection according to the rule key, evaluation sequence,
and rule validity.
Flexible Rule-Based Update
The system uses the evaluation sequence to determine the valid update rule from the rules that correspond to
the selection.
 Example
A material fulfills the conditions of the rules with evaluation sequence 2, 6, and 8. The dialog box is used to
select update rules with the key MRP 1. This applies to the rules with keys 6 and 8. This means that the rule
that corresponds to the selection and has the smallest evaluation sequence takes precedence, that is, rule
6.
The material master is updated for the selected materials. You can decide whether processing takes place in
dialog or background mode. For instructions on how to maintain rules, see the documentation on maintaining
rule sets.
2.6 Two-Step Flexible Rule-Based Material Master Update
This option allows you to check the proposed update rules before updating, and to preview the new values. The
function with an additional restriction on relevant rules is available with the Flexible Rule Based 2-Step radio
button.
If you choose this option, the system opens a dialog box for selecting according to the rule key, the evaluation
sequence, and the rule validity. The valid rules are then displayed. The system proposes the rule with the
smallest evaluation sequence. This rule would also be used for the rule-based material master update. In the
right-hand section of the table, the system color codes the fields that are changed when this rule is executed.
You can now select the suitable rule for each material, or retain the current setting. If you specify a change
reason, this is later displayed in the log.
2.7 Dialog or Background Mode
Depending on the volume of data to be updated, you can choose between two execution modes.
For all three update types (flexible, rule-based, and rule-based 2-step), a dialog box appears before the update,
in which you can specify whether the update is to run in the background, or whether you want to wait for the
result in dialog mode.
Query for Background Mode or Dialog Mode
The differences are described below.
Edit Now and Wait for Result
The update starts immediately here and the results are displayed straight away in the current dialog box in
transaction SLG1. Use the Back button to return to the result screen.
Log for Material Master Update
Edit and Continue in the Background
The material master is updated in the background. You are informed of this via a message. Later on, you can
check the result of the update using transaction SLG1.
Message on Background Processing
You also receive an email when the background job is completed. The result of the material master update is
attached to this email.
 Tip
As an alternative to transaction SLG1, you can also use transaction /SAPLOM/LOG to display the log.
 Tip
When using the transactions SLG1 and /SAPLOM/LOG, you can filter the search by user, date, and object (/
SAPLOM/X). This allows you to find the logs without log number and email.
 Tip
If an error message appears, refer to section Configuration of Rule-Based Material Master Update.
2.8 Maintaining Rule Sets
Using transaction /SAPLOM/XMM_RULE, you can create, change, or delete rules for the rule-based material
master update.
When you call the transaction, existing rules are displayed in a table. The first part of the table contains the
keys for the rules (dark blue), the second part contains the conditions (light blue), and the third part contains
the values to be updated (gray area).
Accessing Rule Maintenance
You create a rule by choosing the New Rule pushbutton. To delete rules, select the rules to be deleted and then
choose Delete Rule(s). You can edit a rule by double clicking it.
Maintaining the Policy Table
A rule is divided into three areas.
Rule area
In this rule area, you describe the rules and sort them into an evaluation sequence. If multiple rules can be used
for the update because their conditions are met, the evaluation sequence determines which rule is applied. You
can also specify a planning scenario.
Conditions area
In this area, you define the conditions that must be fulfilled so that a rule can be used to update the material
master.
The conditions have a restrictive and cumulative effect. This means that if you do not make any entries in the
fields, all of the values are relevant. If you make multiple restrictions, these restrictions are linked by a logical
AND.
Update values area
In this area, you specify the fields that are to be set in the material master for those materials that match the
conditions stated above. If you want to initialize a field, select the Initialize indicator.
Save the created or changed rule by choosing the Save Rule button.
3 Enhanced Material Master View
Within the portfolio of SCM Consulting Solutions, the enhanced material master view represents the central
instance for saving key figures such as the ABC/XYZ classification or other results from different Consulting
Solutions. This increases transparency, and the information is arranged in a clear manner. The enhanced
material master view also serves as the basis for exchanging data between the individual SCM Consulting
Solutions.
The additional tabs are fully integrated into the standard SAP material master and have a separate database
table in which all of the values are saved. This encapsulation ensures that the application runs smoothly,
without impacting the standard SAP code. The integration is performed using standard Customizing and offers
the following advantages:
• Central instance for saving key figures such as the ABC/XYZ classification or other results of the SCM
Consulting Solutions
• Full integration into the SAP standard material master
The component for messages is XX-PROJ-CON-MEH.
3.1 Material Assignment
In terms of content, the enhanced material master view is normally linked to the MRP views of the standard
SAP material master. Once these are available, the additional tab is also visible. This means that the enhanced
Enhanced Material Master View PUBLIC 83
material master view cannot be added to a material individually. The group of tabs to which the view is linked
depends on which category (maintenance status) you choose. The following selection options are available:
Possible Categories (Maintenance Status)
This selection is made in Customizing for the material master. For more information, contact your IT contact
person who oversees the material master, and refer to the configuration of comprehensive functions. The
configuration is located under the Enhanced material master view node in the sections Initial Setup and Step
2a: Create a Data Screen.
Related Information

Initial Setup
Step 2a: Create a Data Screen
84 PUBLIC Enhanced Material Master View
3.2 Central Functions
The upper area of the enhanced material master view provides some central functions, which are explained in
the following subsections. In addition, a where-used list is provided for the individual fields, which is dealt with
in a separate section.
Overview of Central Functions
3.2.1 Comments
The comment function is a comprehensive function that is available in numerous SCM Consulting Solutions.
For more information, see section Comment Function [page 15]. In the enhanced material master view itself,
you can display or edit both the cross-monitor and monitor-specific comments.
The dropdown menu offers those SCM consulting solutions that generally support the functionality for
selection.
Comment function in the enhanced material master view
Although the comments cannot be edited in transaction MM03, the different SCM Consulting Solutions can
be selected from the dropdown menu and the comments can be displayed. If a comment has been changed in
transaction MM02 and has not yet been saved, the system asks you whether you want to save when switching
the SCM Consulting Solution. Only the comment is saved or discarded. All other fields in the material master
remain unaffected by this process.
Multiple comments with different dates can be created for an SCM Consulting Solution. In general, only the
entry with the most recent creation date is displayed in the enhanced material master view. This means that if
you delete a comment here, only the most recent comment is deleted. As a result, there may be cases where
you delete an entry and when reloading the enhanced material master view for the same SCM Consulting
Solution, a different (older) comment is displayed. To delete all of the comments for an SCM consulting
solution completely, you need to use the tasks dialog box.
 Tip
For this, familiarize yourself with the functionality of tasks in general.
Deleting Comments in the Tasks Dialog Box
In the tasks dialog box, you can display the relevant comments to then select and delete all of the rows.
Related Information
3.2.2 Change Documents
The system creates change documents for all of the fields of the enhanced material master view. However,
you cannot access them in transaction MM02 or MM03 by choosing Environment Display Change
Documents because this is not supported in the standard SAP system.
You can, however, access the change documents directly in the enhanced material master view. To do this,
you can use pushbuttons to select the desired display option. In general, the documents can be displayed
either as a list or by field.
Pushbuttons in the Enhanced Material Master View
The Change Documents (List) button lists all of the field changes for the enhanced material master view. Here
you can use the standard SAP functions to configure your own layout.
Change Documents as a List
The Change Documents (Field) button lists the changed fields without values. You can show a field-specific
listing of the changes by double-clicking on the relevant field.
Change Documents for Each Field
3.2.3 Tasks
Using the enhanced material master view, you can create tasks.
Tasks in the enhanced material master view
These functions are used by multiple SCM Consulting Solutions. Therefore, the corresponding section is
referenced here. It explains in detail how you can create and use tasks.
Related Information
3.2.4 Date of Last Update
To ensure a high degree of transparency regarding material master updates from the individual SCM
Consulting Solutions, the enhanced material master view contains the date of the last material master data
update. To display the date of this update, choose the Date of Last Update button.
Date of Last Update
A dialog box containing the specific update data is displayed:
Dialog Box with Update Data
For each tool, two dates are displayed here. The left column contains the date on which the respective SCM
Consulting Solution updated standard SAP fields such as the safety stock or the lot size. The right column
displays the date on which one of the fields in the enhanced material master view, such as the ABC or XYZ
classification, was last updated. This date is not field specific but applies to the update in general.
3.2.5 Where-Used List for Fields
For each field in the enhanced material master view, you can display a where-used list within the SCM
consulting solutions. Right-click the relevant field to open a context menu with two options:
Context Menu for Where-Used List
On the one hand, the usages can only be displayed for the selected field. On the other hand, you can also
display the usages of all fields at once in the enhanced material master view:
Where-Used List for All Fields
 Example
Depending on the selected option, the list of usages is restricted to a single field or is fully defined. The list
in the figure above can be interpreted using the field ABC(D) Indicator as follows:
• The field ABC(D) Indicator is the output of the MRP monitor. This means that it is determined or
calculated there and can be saved in the enhanced material master view.
• The field ABC(D) Indicator is processed by the safety stock simulation. This means that it is used in
further calculations and influences the result within the safety stock simulation.
 Note
If a field is only used as a selection criterion within a consulting solution, it is not included in the Used By
area in the where-used list. The option of updating a field in a consulting solution using the Material Master
Update [page 72] is not evaluated as an output and is not taken into account in the where-used list. Rather
this list includes consulting solutions where the field is taken into account specifically in a calculation or
determined as the result of a calculation.
Filter Options in Where-Used List
If the where-used list is restricted to one field, you can remove this filter by choosing the Delete Filter
pushbutton in the upper toolbar. The list is then fully defined.
You can use the Filtern By… pushbutton to display all relevant fields of a consulting solution. You can also
choose from consulting services that you have not licensed. Since the enhanced material master view is
always delivered in full, no distinction is made here.
Related Information
Material Master Update [page 72]
3.2.6 S/4: Force Classic MRP
The S/4 HANA system enables you to execute MRP Live planning instead of the classic planning run. This type
of planning offers many advantages, but currently does not cover all scenarios that are supported by the
classic planning run. For more detailed information, see SAP Note 1914010 .
Under certain circumstances, it makes sense to assign partial quantities of the materials to be considered in
MRP Live planning to the classic planning run. This can be maintained using the standard SAP transaction
MD_MRP_FORCE_CLASSIC. Alternatively, the use of this function can also be controlled directly from the
material master using the SCM consulting solutions. There is a corresponding checkbox in the enhanced
material master view.
If the user sets this field using transaction MM02 or via a mass update from an SCM consulting solution, a
corresponding entry is created in transaction MD_MRP_FORCE_CLASSIC when saving. If you deselect the
indicator, the entry in the specified transaction is also removed. In this way, you can monitor the functions of
the forced use of the classic planning run in S/4 HANA transparently using the SCM consulting solutions in the
material master, and organize them for a large number of materials using the mass maintenance functions.
Transaction MD_MRP_FORCE_CLASSIC
3.3 Customizing Options
In the enhanced material master view area, you can define certain configurations using Customizing (for
example, you can display and hide individual fields). For details, see the following subsections.
3.3.1 Displaying Fields
You have the option to show or hide all fields in the enhanced material master view. A distinction can be made
here between the plant, MRP area, and storage location levels.
You can also specify the editability of each individual field in transaction MM02. This can also be defined
differently for different levels. This allows you to configure the enhanced material master view in detail to suit
your requirements.
For detailed instructions on how to make these settings, see the configuration guide for the enhanced material
master view.
Related Information
Displaying Fields
3.3.2 Exception Indicators
The enhanced material master view provides a number of highly customizable fields. These "exception
indicators" are technically predefined fields for which you can adjust the field name as well as the selection
options in the input help to suit your requirements. You can configure different settings at plant, MRP area, and
storage location levels.
For details, see the configuration guide for the enhanced material master view.
Related Information
Exception Indicators
3.3.3 Production/Procurement Principle
The field Production/Procurement Principle is located in the area of the stocking level.
Production/Procurement Principle Field
In the standard system, an F4 input help is delivered for this field. However, this can be adjusted to suit your
requirements. This means that you can add new entries and hide existing standard entries.
Standard F4 Input Help for the Production/Procurement Principle
For details on this configuration option, see the section Production/Procurement Principle.
Related Information
Production/Procurement Principle
3.4 MRP Area Level
You can access the level of the MRP area directly using the enhanced material master view. As with the MRP
Area button in the MRP 1 view, a dialog box is displayed in which you can select the area you require. However,
you cannot reassign or delete MRP areas here. To do this, use the standard functions in the MRP 1 view.
Dialog Box for Selecting the MRP Area
The dialog box for the MRP area provides similar features as the enhanced material master view at plant level.
However, you cannot create and edit comments or tasks at this level.
Dialog Box for the MRP Area
This dialog box behaves in a similar way to the configuration of the enhanced material master view. For
example, if the Classification screen is hidden at plant level, it is also hidden at MRP area level.
A special case is the Min. Safety Stock field. At plant level, the standard field shipped by SAP is referenced. In
contrast, the MRP area level provides a separate field without reference for this purpose.
 Caution
Saving in the dialog box for the MRP area is decoupled from the standard process of transaction MM02.
This means, if you choose the save button in the dialog box, the changes are stored directly in the database.
This happens even if you afterwards exit transaction MM02 without saving.
3.5 Storage Location Level
In the same way that data can be stored at the MRP area level, it can also be stored at the storage location level.
When you choose the corresponding pushbutton, a dialog box appears with the selection options for the
storage locations.
Dialog Box for Selecting the Storage Location

Once you have selected the storage location, the relevant field contents are displayed.
Dialog Box for the Storage Location
 Caution
Please note that all special features such as the save logic or the restrictions on tasks and comments apply
in the same way as for the MRP area level.
Related Information
MRP Area Level [page 98]
3.6 Logging
You can view general information about the progress of material master updates (that is, whether updates are
completed successfully) in the standard SAP application log. You access the log in transaction SLG1 using
object /SAPLOM/MEH.
Application log enhanced material master view
3.7 Help
If you have further questions regarding the enhanced material master view of the SCM Consulting Solutions
or require help with configuration, create a customer message on SAP Service Marketplace under the
component XX-PROJ-CON-MEH.
4 Material Document Aggregation
Create a custom consumption and inventory history for the SCM Consulting Solutions. You can use material
document aggregation to create customized consumption and inventory histories that you can use for the
analyses in the MRP monitor, inventory controlling cockpit, and safety stock simulation.
The material document aggregation combines consumption data from a range of material documents to
provide figures that can be analyzed. For this purpose, all material documents that are deemed relevant for the
analysis are read. The program calculates stock, dead stock, and consumption and writes this data to tables.
This information forms the data basis for the MRP monitor. Based on this consumption data, the MRP
monitor can create standard and reference analyses for the inventory controlling cockpit.
General information
Sie können Fehlermeldungen unter dieser Komponente anlegen: XX-PROJ-CON-MDA
Zu dieser SCM-Beratungslösung gibt es den folgenden Hinweis: 1333018
 Note
Bitte beachten Sie, dass Sie bei der Ausführung von SCM-Beratungslösungen jeder Transaktion /n/
SAPLOM/ voranstellen müssen.
4.1 Technical Implementation
You can access material document aggregation using transaction /n/SAPLOM/MDA. You can use the
program to create new analyses.
4.1.1 General Tab
On the General tab, you can define the basic settings for the material document aggregation. You can also
obtain additional information and make settings here.
Material Document Aggregation PUBLIC 105
4.1.1.1 Settings for the Analysis Level
When executing analyses, you must make the following settings:
In the analysis level area:
Here you have the option to perform the analysis at plant, storage location, or MRP area level. To do this, select
the analysis level that you later require in the MRP monitor.
Using the Key for Selection field, you can distinguish between multiple analyses for the same period. For normal
usage, STANDARD is always entered here. In addition, further analysis runs of material document aggregation,
for example, for special applications or for test purposes, can be stored in the database under different keys.
Analysis Level
4.1.1.2 Calculation Types for Stocks
Total Stock is selected by default as the calculation type for stock. A time series is thereby created, in which all
documents starting from the initial stock are analyzed. Key figures such as consumption values, inventory
turnover, and dead stock are thereby calculated. Further settings allow you to specify whether documents that
contained a special stock indicator are to be excluded from this evaluation.
You can also create an invoice separated by special stock. This causes movements with a special stock indicator
to be assigned to the relevant special stock. The analysis then creates a separate time series for each special
stock, but also performs a calculation for the total stock at the same time.
You also have the option to analyze all special stock separately or to include only selected special stock in the
aggregation. For the latter option, you can select the individual special stock.
106 PUBLIC Material Document Aggregation
Calculation Types for Stocks
This enables you to restrict the analysis by special stock to the relevant time series.
A new function for determining special stock is available to you as of Release 2014.1. The stock quantities per
period of the individual special stock are determined in the background using transaction MB5B. To activate
the function, select the desired special stock in this area and the Without Special Stock option.
4.1.1.3 Settings for the Analysis Period
The analysis period is specified in periods, so that the date field is determined automatically. Always enter the
current date as the end date, so that material document aggregation has a correct starting point for all
calculations that take place backward from todays date.
Analysis Period
To run the analysis for the first time, choose a new or flexible historical aggregation. This enables you to define
the period to be aggregated more precisely.
 Tip
For a new aggregation, we recommended that you aggregate data that is at least two years in the past. Only
then is it possible to guarantee a meaningful data basis that can also be used to determine seasonal
materials in the MRP monitor.
You use the setting Historical aggregation one period to aggregate the last completely closed period. You can
also schedule this function as an automatic job in the system.
If you select the Historical aggregation three periods checkbox, the system aggregates the documents of the
last three periods.
 Caution
If you create a variant for historical aggregation, you need to ensure that the corresponding field without a
value is stored for the time frame and the periods. The system always uses the current date and calculates
the last period dynamically. You can use the selection variable to fill the field differently.
Bypassing Automatic Period Calculation
The analysis can be performed for the period category months, weeks, or posting periods, with specification of
the fiscal year variant and the period indicator.
In the Period Assignment of Documents area, you specify which date is to be used for the period assignment of
the documents. You can select either the creation date, posting date, or document date.
 Tip
We recommend that you perform period assignment using the posting date, which is the standard system
setting.
 Caution
Older versions of material document aggregation work with the creation date of the document. To avoid a
logical break between periods already aggregated (through an older version of material document
aggregation) and to generate a post-aggregated period, you should continue to use the creation date.
4.1.1.4 Settings for Analysis Scope
Analysis Scope
Under Analysis scope, you can restrict the analysis scope further by specifying the considered materials and
plants. By expanding the Additional select options option, you can restrict the materials to be aggregated. This
enables you to exclude unnecessary materials from the aggregation and improve system performance.
 Caution
All of the materials that are to be relevant for the MRP monitor need to be analyzed in material document
aggregation. Please note that the materials you have excluded from the selection in material document
aggregation are, in a later run of the MRP monitor, identified as materials without consumption.
4.1.1.5 Settings for Analysis Steps
To perform material document aggregation, you need to execute all analysis steps, but not necessarily in a
single aggregation run.
Analysis Steps
The material document analysis performs the following actions:
1. Determine stock
• The current stock of materials is read and saved in table /SAPLOM/X__STOCK.
• The initial stock is calculated and saved in table /SAPLOM/X__START.
2. Read material documents
• All material documents are read and saved in table /SAPLOM/X__BELEG.
3. Relevance check and consumption calculation
• The material documents are filtered by analysis-relevant documents and the relevant documents are
saved in table /SAPLOM/X__RELEV.
• Date range is determined: The date of the newest and oldest document (corresponds to first or last
consumption) is written to table /SAPLOM/X__DATUM.
• The consumption quantities and values are determined for each period based on the previously
determined documents and the data is stored in table /SAPLOM/X__PERIO.
4. Stock accounting
• Continuous stock changes that result from documents (receipts and issues) are determined and
stored in table /SAPLOM/X__BEWEG.
• The daily stock resulting from the documents is determined and stored in table /SAPLOM/X__DAILY.
• Stock is determined for each period and stored in table /SAPLOM/X__STAND.
For each individual analysis step, you must specify a package size. The package size determines how many
data records (materials in the first step, documents in the second step) are processed at the same time. The
individual steps vary in terms of performance intensity. Therefore, adjust the package sizes accordingly. For
default values for the new aggregation, see section Optimizing Performance Using the Package Size [page 130].
 Remember
In the case of aggregation, not all table content is stored permanently. You therefore have no entries in the
database.
For stock accounting, there are additional functions for which special stock is not analyzed separately. You can
use these functions to deactivate saving of the special stock quantity in table /SAPLOM/X__STANS.
Deactivation reduces runtime and frees up storage space in the tables.
Determination of stock quantities for special stock can be replaced by the function Read Special Stocks as in
Transaction MB5B.
Related Information
Optimizing Performance Using the Package Size [page 130]
4.1.1.6 Expert Mode
In most use cases, you can correctly configure material document aggregation using the settings shown. The
expert mode is available for special cases.
Expert Mode
4.1.1.6.1 Display Technical Names
Using the Display Technical Names checkbox, you can show or hide additional information and the names of
tables for individual steps.
Technical Names in the "Analysis Steps" Area
4.1.1.6.2 Expert Switch
The Expert Switch makes further settings visible on the Settings tab. This allows you to define initial stock now
at table and column level.
To use special stock, you need to activate the expert switch. This setting is essential if you want to analyze
special stock or non-valuated stock.
This Expert Switch changes the view on the Settings tab (see section Analysis Rules for Stock Tables in Expert
Mode [page 114]. An extensive list of special stock and non-valuated stock is available for selection.
Related Information
Analysis Rules for Stock Tables in Expert Mode [page 114]
4.1.2 "Settings" Tab
On this tab, you can specify the rules for initial stock determination, consumption and receipt accounting, as
well as stock accounting.
4.1.2.1 Analysis Rules for Stock Tables Without Expert

Mode
The material document aggregation always calculates the individual stock starting from initial stock. This
initial stock is the stock that is available in the system at the time of analysis. The initial stock is thereby an
important basis for key figures such as dead stock and inventory turnover.
The initial stock can be read from either the "Material Valuation" table (MBEW) or from the "Statistics: Current
Stock and Grouping Terms" information structure (S032).
 Restriction
You can only use the S032 information structure if the data is correctly filled and maintained in your
system.
For analysis at plant level, use table MBEW, but for analysis at storage location or MRP area level, use table
S032. In table MBEW, stock is not separated by storage location and is therefore unsuitable for storage location
analysis.
Info structure S032 can contain detailed data, however it is not established and updated in every customer
system by default. Please ask your SAP Basis administrator about how you can use the S032 information
structure.
4.1.2.2 Analysis Rules for Stock Tables in Expert Mode
On the "General" tab, you can activate the Expert Switch for expert mode. For more information, see the section
Expert Switch [page 113].
The following options are then visible in the lower area of the Settings tab:
Valuated Stock in Expert Mode
In expert mode, the default setting is that the system reads the documents from table MBEW. Besides
selecting the table to be used for the analysis (MBEW or S032), you can also add valuated sales order stock
(table EBEW), subcontracting stock (OBEW), and valuated project stock (QBEW) to the initial stock.
First check whether valuated stock (tables MBEW, EBEW, QBEW, and OBEW) or only stock quantities are to be
relevant for the analysis.
Analysis Rules in Expert Mode
If an analysis separated by special stock is to be carried out, you can decide, for the respective special stock,
which stock is also to be included.
 Caution
Different tables in the SAP system contain similar information. The program offers the possibility of making
a selection from all these sources. However, make sure that you take relevant information only from a
source that is correct for you, and not the same information from different sources. Otherwise, this would
lead to duplicate and therefore incorrect information. For example, you receive duplicate stock if you use
the table S032 and MBEW. It is therefore important to check the scenario to be mapped in detail in
advance.
SAP Consulting offers a service for this. For more information, see the following SAP Note: 1492806
Related Information
Expert Switch [page 113]
4.1.2.3 Analysis Rules for Consumption and Receipt

Accounting
Analysis Rules for Consumption and Receipt Accounting
In this section of the entry screen, you can specify rules for consumption and receipt accounting. You can
include or exclude individual movement types. Make sure that you specify all of the movements types to be
used. For example, if you add a movement type without its respective reversal movement type, this can lead to
errors during aggregation. You can also select the required storage locations. Internally, material document
aggregation uses the debit/credit indicator to distinguish between a receipt (debit) or consumption (credit).
In addition, you can activate various other analysis rules. If you choose the pushbutton, you receive
information about which check actions are executed to classify the document as relevant or not relevant for the
analysis.
4.1.2.3.1 Checking Rule "Only Movement Types with

Consumption Indicator"
If this rule is active, only documents for which the consumption indicator (KZVBU) is set are considered. You
specify this in the Customizing settings for the movement types. You can view the current settings in
transaction OMJJ and in system table T156.
Change "Movement Type" View
If this rule is activated, as in the material consumption table (MVER), the consumptions are calculated.
4.1.2.3.2 Checking Rule "Valuated Movements Only"
If this rule is active, only valuated movements are regarded as relevant for consumption and receipt
accounting. A movement is regarded as non-valuated if the special stock indicator (SOBKZ) has the value E
(order stock), Q (project stock), M (returnable transport packaging), K (consignment stock), I (subcontracting
for returnable packaging of vendor), or O (parts provided by vendor), and the field KZBWS (valuation) is not
equal to A (valuation without reference to sales document). You can find all of the fields in the “Document
Segment: Material” table (MSEG).
 Note
This rule is usually only used for stock accounting.
4.1.2.3.3 Checking Rule "Only Movements with Source

Plant Not Equal to Target Plant"
If this rule is active, documents for which the source plant (WERK) is the same as the target plant (UMWRK) are
not considered. You can find all of the fields for the document in the “Document Segment: Material” table
(MSEG).
 Note
This rule is usually only used for stock accounting.
4.1.2.3.4 Checking Rule "Differentiated Evaluation of

Movement Type 101 and 102"
This checking rule refers to stock transfers with stock transport order. If materials are transferred from one
plant to another, this is done using the movement types 351 UL To Stock in Transit and 101 Goods Receipt. If
both documents are taken into account, this results in the receipts being counted twice. In the checking rule, it
is thereby determined whether the goods movement is performed with purchase order reference (KZBEW = B)
and whether this is a stock transport order (KZZUG = X) or whether posting is made directly to consumption
(KZVBR = V). You can find all fields in the “Document Segment: Material” table (MSEG).
 Note
This rule is used in the inventory and consumption calculation.
4.1.2.3.5 Checking Rule "Movements with Account

Assignment Not Relevant"
If this rule is active, movements with account assignments, that is, movements that are posted to consumption
directly (KZVBR = V), are excluded. You can find the consumption field (KZVBR) in the “Document Segment -
Material” table (MSEG).
 Note
This rule is used in the inventory and consumption calculation.
4.1.2.3.6 Checking Rule "Relevance Check Using Exclusion

Table"
If this checking rule is active, you can define additional exclusion criteria for movements. To do this, you create
rules in the exclusion table /SAPLOM/MDA_MTEX. If a document conforms with a rule defined there, the
system regards it as not relevant.
Table view maintenance for /SAPLOM/MDA_MTEX
4.1.2.3.7 Maintain Custom Rules
You can use transaction SM30 to maintain your own rules.
In the Stock Accounting or Consumption Calculation Indicator column, you define the validity period. Using the
Movement Type, the Debit/Credit Indicator, and the Consumption Posting column, you can define a
combination that is to be excluded.
The exclusion table can be used, for example, to exclude goods receipts that are posted directly to
consumption. These movements are characterized by the fact that the target document does not lead to an
increase in stock. Such movements must not be included in stock accounting to ensure that the stock is not
calculated incorrectly.
Rule for Analysis with "STANDARD" Key
4.1.2.4 Analysis Rules Stock Accounting
Stock accounting in material document aggregation is performed backwards, starting from the current initial
stock.
Stock Accounting Schema
Only the documents relevant for stock accounting are considered, which you define in the following section.
Analysis Rules for Stock Accounting
For stock accounting, you have the same rules available as for consumption and receipt accounting (section
Analysis Rules for Consumption and Receipt Accounting [page 116]). Note that the settings for a plant analysis
differ from those for a storage location or MRP area analysis. For a plant analysis with initial stock MBEW, you
are provided with default values together with the transport request for this SCM Consulting Solution.
The default setting for a plant analysis excludes the following 14 movement types:
• 103 GR in blocked stock

• 104 GR in blocked stock reversal
• 109 GR from val. blocked stock
• 110 GR from val. Bl. reversal
• 305 Put UL away in plant
• 306 Put UR away in plant
• 315 Put UL away in SLoc
• 316 Put UR away in SLoc
• 451 GI returns
• 452 WS returns reversal
• 455 UL transfer returns
• 456 UR transfer returns
• 651 GS goods return delivery returns
• 652 RE goods return delivery reversal
Movement types 103, 104, 451, 452, 455, and 456 are excluded since the blocked stock returns are not
managed in MBEW. Movement types 305 to 316 are excluded due to stock transfers in two steps. If the
movement types 303 and 305 or 315 were included, this would result in double counting and therefore produce
incorrect results.
Movement types 109 and 110 are excluded since the valuated goods receipt blocked stock (MARC-BWESB) is
also managed in the MBEW stock table. Goods receipts from the valuated goods receipt blocked stock and
their reversal postings are therefore to be excluded from the analysis.
 Note
In the dead stock transaction in the standard SAP system (transaction MC50), the valuated goods receipt
blocked stock is not taken into account. Therefore, the results of dead stock calculation in material
document aggregation differ from the results in the standard ERP system.
4.1.2.5 General Information on Movement Type and Special

Stock
The standard delivery of material document aggregation and the variants mentioned in the section Analysis
Rules Stock Accounting [page 119] contain default settings for some of the standard movement types.
However, SAP cannot guarantee the correctness of these settings. The relevant movement types and special
stock settings always need to be determined for the specific customer scenario. SAP Consulting can provide
support for this process as required.
 Caution
Both during the selection of corresponding selection criteria for material documents, such as movement
types, and during the selection of special stocks, the conceptual effort when initiating such a process must
be considered sufficiently during planning. Therefore, before using material document aggregation in
general and evaluating special stock specifically, SAP Consulting recommends that you have a
comprehensive, internal design phase, during which the company specifics are taken into account
sufficiently. In particular, consider the following points:
1. What is the specific customizing with regard to movements?

2. What is the posting behavior?
Which movement types are explicitly used and how, and are there person-dependent or area-
dependent deviations? Is a business event in a certain area of certain persons handled differently than
in other areas?
3. What is the aim of the analysis? What is going to be derived from the respective result?
Related Information
Analysis Rules Stock Accounting [page 119]
4.2 System Settings
This section describes how you delete analyses, work with jobs, and specify the package size for individual
aggregation steps.
4.2.1 Delete Old Analyses
To rebuild aggregations and to free up space in the database occupied by aggregations that are no longer
needed, you can use the additional program Deletion Program for MDA Tables. You call this program using
transaction /SAPLOM/MDA_X.
"Delete method / period" Area
Deletion Program: Delete method / period Area
In the Delete method / period area, you can choose between the modes "manual" and "automatic". In manual
mode, you yourself need to define the deletion criteria, which can be configured further down the selection
screen. With the automatic deletion method, the time-related deletion criteria such as period, entry date, and
so on are calculated by the program. In this case, you first need to specify the period type (months, weeks, or
posting periods) and the start date. You define the deletion period by selecting the previous periods.
Tables and Special Stock Tables Areas
In the Tables and Special Stock Tables areas, you can then select the tables that are to be emptied.
Deletion Program: Tables and Special Stock Tables Areas
Depending on the selected tables, the Deletion Criteria area appears with the relevant input fields.
If you choose the and pushbuttons, you get additional information about the deletion criteria for the
individual tables.
 Example
For example, if you select only the Current Stock (STOCK) table, the input fields for material, plant, storage
location, and special stock appear because only these are relevant. If you select a second table in addition
to the STOCK table, the number of deletion criteria is extended. Using the selection criteria, you can further
restrict the data to be deleted in the tables.
 Caution
Be careful when using the selection key as a criterion. For tables that do not have the selection key as
database key, it is easy to delete all of the data. For table /SAPLOM/X__BELEG in particular, it is easy to
lose a large amount of data this way. Other tables that do not have the Key2 field as a deletion criterion are
indicated by the button.
Therefore, delete data only based on clear rules, and ideally after consultation with SAP Consulting.
If you start the program with the “automatic” deletion method, certain deletion criteria are no longer ready for
input and are filled automatically.
Deletion Criteria - Filled Automatically
This method is particularly suitable if you schedule the deletion of material document aggregation tables as a
regular background job (see section Working with Jobs [page 125]).
 Note
Save the variant such that the From Start Date field is maintained without a value, or define a selection
variable if necessary.
Save Field Without Values
If you do not define selection variables and select the Save Field Without Values indicator, the current date is
used. Not all tables that are provided by the deletion program of material document aggregation are
enhanced in every analysis run.
 Recommendation
It is useful to perform deletion regularly for the following critical tables:
• /SAPLOM/X__BELEG
• /SAPLOM/X__RELEV
• /SAPLOM/X__PERIO
• /SAPLOM/X__STAND
If you perform an analysis separated by special stock, the following tables are enhanced with every
historical aggregation. Regular deletion is also advised here.
• /SAPLOM/X__PERIS
• /SAPLOM/X__STANS
Related Information
Working with Jobs [page 125]
4.2.2 Working with Jobs
Due to the scope of aggregations, they often cannot be performed in online mode. In this case, you should
create the settings as variants (button ) and perform the aggregation as a background job. You can then use
these variants to create the aggregation runs as jobs using transaction SM36. When doing so, you can define a
separate variant for each analysis step and then execute these variants successively as job steps.
 Note
The settings for the first variant would be as follows:
DEMO: Analysis step 1
For the second variant, choose analysis step 2 Read Material Documents and so on.
The corresponding job steps in transaction SM36 are then as follows:
DEMO: Job Steps in Transaction SM36
Alternatively, you can perform individual steps as a background job by saving a variant with all of the analysis
steps.
Variant with All Analysis Steps
This has the advantage that the same settings are used for each analysis step and only one variant per analysis
is stored in the system. In contrast, splitting into individual steps increases the stability of the aggregation and
makes the progress of the jobs more visible than is the case for a single large job.
If you want to further subdivide the jobs mentioned above, you always need to do this by material number.
Subdividing by period is not allowed.
4.2.3 Best Practice - Job Chain
Material document aggregations and MRP monitor analysis that are not required should be deleted on a
regular basis to avoid a constantly increasing data volume.
It is recommended that you use a rolling horizon. To calculate this you need to determine the maximum
number of historical periods that you want to analyze in the SCM consulting solutions such as MRP monitor,
inventory controlling cockpit, and safety stock simulation. A typical value is two years of historical data.
 Caution
Do not delete data that you still need for analyses.
Rolling Job Sequence

Sequence Analysis Step Transaction
1 Post aggregation of the last period in the material document /SAPLOM/MDA

aggregation.
 Note
Note that the period must be completed.
 Example
The month 12/2018 is aggregated again.
Sequence Analysis Step Transaction
2 Analysis of the current data in the SCM Consulting Solutions, /SAPLOM/MRP

such as the MRP monitor.
 Example
Analysis with the period 01/2017 to 12/2018 is performed.
3 Delete the no longer required aggregation in the material /SAPLOM/MDA_DEL

document aggregation.
 Example
The aggregated data of month 12/2016 is deleted.
4 Delete the no longer relevant analyses in the SCM Consulting Sol /SAPLOM/MRP_DEL
utions, such as the MRP monitor.
If an old analysis is overwritten with the new data, this step is

omitted.
 Example
Analysis with the period 12/2016 to 11/2018 is deleted.
 Note
If you do not work with material documents as the data source, you can only delete the MRP monitor
results periodically.
Sequence of Jobs
For the deletion run in transaction /SAPLOM/MDA_DEL, the following settings are recommended:
• Select the automatic deletion method for rolling job scheduling.

• Choose the desired number of historical periods: If you want to retain 2 years and have selected month as
the period, the 25th period is to be deleted on a rolling basis.
• Selection of tables to be deleted: If the analysis is executed for special stocks, you also need to delete the
special stock tables. The table that stores the first/last consumption may not be deleted. This information
is required for the new and slow-moving materials analysis.
• As required, the objects to be deleted can be restricted further using the selection criteria.
• Before executing, check that the periods to be deleted are determined correctly. In the event that you do
not assign documents to the periods based on the creation date, extend the selection to the date used -
posting date or document date.
Selection of MDA Deletion Program
 Example
Before deletion, the results table contains the data for the material document aggregation from 12/2016 up
to and including 11/2018.
Old Dataset of the MDA Results Table
In the following month, the new period is post aggregated and the oldest period is deleted.
Results Log for MDA Deletion Program
The results table shows the new dataset from 01/2017 up to and including 12/2018.
New Dataset of the MDA Results Table
4.2.4 Optimizing Performance Using the Package Size
If the analysis is very complex, there may not be enough working memory. In this case, you can have the
system work in package mode, whereby only the specified number of materials is processed at once and the
interim result is saved for each pass.
 Recommendation
Since each SAP system has different hardware properties, it is not possible to specify an optimum package
size. The optimum package size must be determined for each customer.
So far, the average values are as follows:
Empirical values for package sizes
Package size new aggre Package size historical ag

Step/job Description gates gregates
1 Determine stocks 5000 5000
2 Read material documents 1000-5000 5000
3 Relevance check and con 100 500

sumption calculation
4 Stock accounting 5 5
4.1 Read special stock as in 50 50

transaction MB5B
SAP Consulting recommends starting with these package sizes and gradually reaching the optimum
package size in small steps.
 Note
Determining special stock using transaction MB5B is very runtime intensive and can increase the runtimes
of the background jobs when new aggregates and historical aggregates are created. If the stock quantities
of special stock are not required for every period in the analysis period of new aggregates, we recommend
that you determine the stock using transaction MB5B for the last analysis period only.
4.3 Organizational Information for Material Document

Aggregation
Before using material document aggregation for the first time, you need to establish, for the range of
materials in question, aggregation for the entire period that is possible for the downstream analyses by the
MRP monitor and inventory controlling cockpit.
Period of Analysis and Analysis Scope with Selection "New or flex. add. aggregation"
To do this, use the New or flex. add. aggregation option and set the time period accordingly, for example, the
last three years.
If you then continually work with the solution, additional movement data is periodically added to the selected
range of materials. To be able to perform the MRP monitor analyses and inventory controlling cockpit analyses
in each case, you need to post-aggregate the values added periodically. To do this, execute the aggregation for
each newly added area again.
Schema of Aggregation Periods
In the course of time, the data basis for the MRP monitor and inventory controlling cockpit grows continuously.
If you perform post-aggregation, the analysis values between the last fully aggregated period and the date of
the post-aggregation are deleted and then reconstructed. This ensures that post-aggregation for a period does
not need to be started right at the end of the period.
You can choose post-aggregation for one or three periods (see image above) or flexible post-aggregation with a
custom-defined number of periods.
All of the analysis steps described in section Settings for Analysis Steps [page 110] must be performed again
for the mentioned, reduced period of post-aggregation.
The runtime of the initial analysis can be longer due to the large number of documents processed, whereas
periodic post-aggregation has shorter lead times.
See also Delete Old Analyses [page 122]. This section describes how you delete aggregation values that are no
longer needed so that database space becomes free. To delete legacy data periodically in the background, you
need to create a corresponding variant and set up the job for the program /SAPLOM/MDA_DELETE.
Related Information
Settings for Analysis Steps [page 110]

Delete Old Analyses [page 122]
4.4 Manual Corrections
You can use transaction /SAPLOM/MDA_R to manually correct existing MDA entries.
Selection
The selection determines which material, plant, MRP area, or storage location is to be changed.
The table entries for special stocks can also be changed if the option for displaying special stocks is selected.
This option is relevant only if the original MDA consumption history also analyzes special stocks separately.
Tab for consumption / receipt per period
The tab for consumption / receipt per period presents the values of the table /SAPLOM/X__PERIO.
All fields that have a white background color are released for changes. Only consumptions and receipts with the
corresponding columns can be modified in transaction MDA_R. The column for manually changed data records
indicates whether a manual change has been made. The user name, date, and time of the change are updated
in the tables.
 Note
Manually changed values can be overwritten by the periodic MDA background job. To avoid this, you need
to manually change only periods that are no longer changed by the periodic background job.
Tab for first / last date
The tab for the first / last date displays the values of the table /SAPLOM/X__DATUM.
All fields that have a white background color are released for changes. Only the date of the consumption and
receipts can be adjusted. The periodic background job regularly updates the columns for the newest retirement
date and the newest receipt date as soon as there is a new receipt or consumption.
Important Disclaimers and Legal Information
Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:
• Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your
agreements with SAP) to this:
• The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.
• SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.
• Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such
links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this
information.
Videos Hosted on External Platforms

Some videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any
advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within
the control or responsibility of SAP.
Beta and Other Experimental Features

Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by
SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use
the experimental features in a live operating environment or with data that has not been sufficiently backed up.
The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your
feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.
Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax
and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of
example code unless damages have been caused by SAP's gross negligence or willful misconduct.
Bias-Free Language
SAP supports a culture of diversity and inclusion. Whenever possible, we use unbiased language in our documentation to refer to people of all cultures, ethnicities,
genders, and abilities.
Important Disclaimers and Legal Information PUBLIC 135
www.sap.com/contactsap
© 2022 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form

or for any purpose without the express permission of SAP SE or an SAP
affiliate company. The information contained herein may be changed
without prior notice.
Some software products marketed by SAP SE and its distributors

contain proprietary software components of other software vendors.
National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for

informational purposes only, without representation or warranty of any
kind, and SAP or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP or
SAP affiliate company products and services are those that are set forth
in the express warranty statements accompanying such products and
services, if any. Nothing herein should be construed as constituting an
additional warranty.
SAP and other SAP products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP
SE (or an SAP affiliate company) in Germany and other countries. All
other product and service names mentioned are the trademarks of their
respective companies.
Please see https://www.sap.com/about/legal/trademark.html for

additional trademark information and notices.
THE BEST RUN

Mcf-En-Public Sap

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Mcf-En-Public Sap

Uploaded by

Copyright:

Available Formats

© 2022 SAP SE or an SAP affiliate company. All rights reserved.

THE BEST RUN

2 Material Master Update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

3 Enhanced Material Master View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

4 Material Document Aggregation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

These are primarily the following functions:

• Tasks and resubmissions

Zusätzlich sind folgende SCM-Beratungslösungen Bestandteil der Comprehensive Functions:

Material Master Update [page 72]

1.1.1 Creating Tasks

Steps to Create/Display Tasks

1. Select the relevant data records

The “Tasks” screen appears.

You can change tasks on the screen in both cases.

1.1.2 Maintaining Tasks

Use the ALV standard toolbar to process ALV lines.

ALV Standard Toolbar

Configuration of the comprehensive functions

1.1.3 Tasks Overview

The selection screen is divided into four different criteria blocks:

Result Screen: Overview of Tasks

You can change the following columns on the result screen:

1.1.4.1 Entering Additional Comments

You can use up to ten additional comment columns.

• Tasks must already exist in the system.

Entering Additional Comments

Configuration of Comprehensive Functions

/SAPLOM/MEA_ADD_FLDS Display additional comment 1 = 5 additional fields Depending on the parameter

/SAPLOM/MEA_MEM_COBJ Activation of memory ID for X = active If the memory ID is active,

/SAPLOM/ Activation of memory ID for X = active If the memory ID is active,

/SAPLOM/MEA_MEM_ROBJ Activation of memory ID for X = active If the memory ID is active,

/SAPLOM/MEA_MEM_TOBJ Activation of memory ID for X = active If the memory ID is active,

/SAPLOM/MEA_SELECT_I Tasks user parameter ID X = active If this user parameter is ac­

1. Choose the row in the result list.

At least one resubmission data record is created in database table /SAPLOM/X_RESUBM.

1.2.2 Resubmission Process

1.3 Comment Function

Creating Comments [page 16]

1. Select a row in the result list.

Comments with User Parameters

Configuration of the comprehensive functions

1.4 Tasks, Resubmissions, and Comments on the Results

The following information is displayed:

1.5 Individual Material Groups

Grouping materials in this way serves to make your work easier.

Using the Individual Material Group from Lot Size Simulation

Creating Individual Material Groups [page 19]

1.5.1 Creating Individual Material Groups

You can create new individual material groups as follows:

1. Call transaction /n/SAPLOM/X_IND_MGROUP.

The preview of the materials to be imported is displayed.

The import to the database takes place.

1.5.2 Editing Individual Material Groups

You can edit existing individual material groups as follows:

1. Call transaction /n/SAPLOM/X_IND_MGROUP.

3. Confirm your selection by choosing Execute ( ).

The editing screen is displayed with the selected data.

1.5.3 Deleting Individual Material Groups

1. Open the editing transaction /n/SAPLOM/X_IND_MGROUP.

1.6.1 Creating and Editing Alerts

Procedure for Creating Alerts

Defining Alert Conditions

/SAPLOM/MEA_SELECT_I Tasks user parameter ID X = active If this user parameter is ac