MMS Execution Monitor – Functions

Control of deletions

In this area it can be defined, after how many days registered execution records will be deleted. Depending on the record status different values can be defined. Newly registered records which are not yet executed can't be deleted.

If one of the settings has no value (empty) corresponding records will not be deleted.
Changes of any values must be saved using the push button "Save control data".

Batch job control

To execute this functions a user needs besides the ProMaterialData authorities (see ProMaterialData Integration & Enhancement manual) also standard SAP authorities to create and delete batch jobs.

Registered ProMaterialData records will only be executed, if the ProMaterialData batch job is running. In this area the state of the batch job is displayed and the job can be started and stopped. By stopping, the job will be deleted from the batch queue.
Relevant fields for batch jobs

Field	Description
Background User	The execution of the actions runs under the user name entered in this fields. This means that the ProMaterialData actions will run under this user with the authorities of this user.
No. of jobs	Defines how many jobs / processes is ProMaterialData allowed to run in parallel. This is important, when executing mass updates triggering ProMaterialData batch actions. The absolut max. amount of processed is defined by the running batch processes on the system / server. This value should always be set that not all batch processes are used by ProMaterialData.
ServerName	Defines the server to be used by ProMaterialData. Without entry the SAP batch system any free batch server.

If already records are registered for execution when the batch job is started, by executing the function Trigger event this records can be processed. Else they will not be processed until next time a material master change triggers ProMaterialData actions.|

Functions on execution records

Depending on status and authorities various functions on the execution records are available using the context menu or the links.

Area	Function	Description

Area	Function	Description
D.2	Click on material number	Calls the transaction MM02. If for a material master record an execution record with status "Not yet executed" or "Error" exists and editing is locked by ProMaterialData settings, this material master record can only be edited using this function. For example if after an error the data should be corrected and the ProMaterialData action then be re-executed, the data maintenance has to be called using this function.
D.3	Click on	For records with status error, normally more than one message line is stored. Use this function to display all messages.
Context Menu	Re-execute after error	Re-executes the registered ProMaterialData action after an execution error. Depending on the error, it can be necessary to correct the data before re-executing. Note that any change at the customizing will not affect registered ProMaterialData action records. Re-executing an action does not reprocess the rules and redefine the actions to execute, but only process the fields and views saved in the action record. If an error occurs because of invalid customizing data, the action must be marked to ignore and the data has to be fixed manually.
Context Menu	Execute action	Runs the registered but not yet executed ProMaterialData action. This is mostly for testing, when the ProMaterialData batch job is not started.
Context Menu	Execute ignored action	Even if a ProMaterialData action is marked to be ignored, with this function the action can be executed.
Context Menu	Mark to be ignored after error	If a ProMaterialData action should not be re-executed after an error and the material master record should be released for editing, the record can be marked to be ignored with this function.
Context Menu	Mark to be ignored	If a newly registered record should not be executed, it can be marked to be ignored with this function. This is only to be used when testing without ProMaterialData batch job.