Monitor Interface

The monitor interface consists oft two parts:

Upper part: selected MUDs.
Lower part: assigned usages and actions for actual selected MUD.

The monitor has been implemented with SAP Standard ALV Grid's; therefore all standard functions can be used. For details please refer to the standard help, using the resepctive push button. The following chapter describes specific functions and fields of the MUD-monitor only.

General Functions

In the function bar and the menu the following functions are available.

Menu / push button

Function / Description

Read data according selection

The current display data will be read newly, the status of the MUD-monitor entries will be determined and the display will be refreshed.

Additional information / key

Opens a list of all icons being used:

Upper Monitor Part

This section shows all selected MUD with different data and the monitor status.

Push button	Function / Description
Display object	Displays the marked objects with SAP-DMS standard display transaction (CV03N).
Change object	Changes the marked MUD with SAP-DMS standard change transaction (CV02N) Depending on the function, only single objects are selectable.
(Icon acc. customizing)	Calls additional transaction for marked MUD. Icon, tool tip text and transaction are according to customizing. With standard settings, ProNovia SAP PLM Client will be called, if installed). Depending on the function, only single objects are selectable.
	The selected function and all included detail lines will be deleted. The deletion has to be confirmed. Function requires authorization.
	Selection of the MUD and display of the usage in the lower section.
Function	The function (versioning, insert, replace, remove) according to the icon described in the legend, see General Functions.
Status	Status according key, see General Functions.

Lower Monitor Part

This section shows the usages of the selected MUD with all related data and the monitor state.

Which options are possible on the usage depends on the system settings.

Push Button / Fields	Functions / Description
	The selected or default actions will be processed on the usages. This can be done directly o as a batch job (background processing). If the multiple used document is locked when starting the batch job, the job is delayed for two minutes. It may be possible, that no selection is possible and one processing mode will automatically be executed.
	Display of the marked data package or material master record with SAP standard display transaction (CV03N / MM03).
	Change of the marked data package or material master record with SAP standard edit transaction (CV02N / MM02).
	Calls additional transaction for marked data package or material master record. Icon, tool tip text and transaction are according to customizing. Default and if installed, ProNovia SAP PLM Client will be called.
	The entry for the currently selected detail line is deleted. The deletion must be confirmed. This function is only available with the appropriate authorization.
Status	Status according key (Icons).
Change	When marked, option Start change was selected on the object acc. to field In control or the option was executed. (Depends on the status). This option is possible, if the target object has been released and starts a ProConfiguration change on the target object with a start of a processing scenario. The new MUD version will be added to the newly generated data package version.
Replace	If marked, option Replace in data package has been selected or executed on the object. This option is possible, if the target object is actually in a running change,
Mark for next change	If marked, option Marked for next change has been selected or executed. This option is possible, if target object is not in change and not released (e.g. control status), this is the only option to exchange the MUD with the target object. As soon as a change is started on the target object, the MUD version will be actualized in the data package.
Ignore	If marked, option Ignore has been selected or this option was executed. This MUD version will then be ignored for this version, e.g. not used or replaced. After another versioning and release, the use will be considered again for the MUD process.