How does ProMaterialData operate?
After a change of one or more field entries, the ProMaterialData changes values in the material view or classification or will create complete new views.
The material master data update can run directly after the data change and therefore by the actual user in the actual process or via the ProMaterialData batch execution, which can run under a specific batch user (See View Control and MMS | ProMaterialData | User Manual).
The following components will be active during an entire ProMaterialData process:
Control groups
Selection Rules
Verification of field values
Dependencies
Control data is always assigned to a control group. Control groups consist of the following main elements:
Selection rules: Selection Rules and its filters will control whether a control group will become active for a certain material and on a specific time.
Verification of field values: Depending on the control group it is possible to verify fields for certain values.
Dependencies: If activated, dependencies will control the setting of dependent values after field value changes.
In general ProMaterialData processes will be activated by saving the data after maintenance of the material master.
Schematic drawing of the ProMaterialData process flow
Execution order
The execution of the ProMaterialData action is made using a defined order. Depending on the relations between the material views to maintain, it's important to keep attention to this order:
Value Handler sort order:
Each value handler is called in the order of the sort sequence.
MVIEW Handler:
A1 | Create views / update views | Defines the execution order of the value groups. |
A2 | Name of Control Group | |
A3 | Number of Dependency within the Control Group | |
B | Handle tables and fields | Data for MARA, MAKT, MARM, MARC, MLAN (for MARC), QMAT, MPOP, MFHM, MARD, MLGN, MLGT, MBEW, MVKE, MLAN (for MVKE) are setup. Note that depending on the requested maintenance status a field can be ignored (see customizing table T130F). |
C1 | Grouping from "Values to be Set" | Defines the order oft the views and values within a value group. This is only relevant, if in one run more than one view is addressed (example: creating data for two storage locations). |
C2 | Run No. from "Values to be Set" |
CLASS Handler:
First all required class assignments are made
For each class the classification values are set
When using MMS with IDOC / ALE, please observe the notes in Usage of MMS with IDOCs.
© ProNovia AG | Imprint | Data Protection