The Process of the muD Logic

Hereinafter a summary of the MUD logic, if MUD are handled by the MUD monitor:

Determination of Usage

• Depending on the function, the material masters are determined by the current usage (versioning, replace, remove) or acc. selection.

  • Usages are determined by standard CFM functionality (/PRONOVIA/PRM_GET_DOC_MAT).

  • Material master records with status Ignore are ignored. In case of  a mass operation they will be listed with a certain message.

• In case of a versioning also ignored muD control sets will be included, e.g. the former muD version will be replaced by the newest.

Registry in MUD

• Only usages suitable to the control group acc. customizing are transferred (DPTYP and ORGKY).

• Only usages of the newest data package version will be used.

Determination of status of action (extract)

• Header (muD)

  • If a new version of a muD exists (both in case of Replace) this action is ignored (Obsolete). For actions to a new version (exchange new version in usages), this action is still possible, if the new version has not be listed for action.

• Usages

  • No more action possible

    • If the relevant objects have a deletion flag  (data package, material, organization units).

    • If the relevant object has status Ignore.

    • If a new data package version exists (obsolete). Exception: Add is possible.

    • If the MUD is no longer part of the data package. Exception: Add is possible.

  • When adding, it is checked, whether the muD is already part of the data package (added manually).

  • The reason, why usage can not be changed is indicated with a status icon.

  • For all other cases, the possible actions are determined acc. status, processing scenario etc.

  • The checks are performed

    • before display on the muD monitor.

    • On the usage just before the execution. As a consequence it is possible a user selects and performs an option, but another option is selected, because the data was changed in the meantime (e.g. release).

Start of a change on a usage registered for processing

An exchange is always performed when the processing scenario allows Usage in DP   filter proc. scenario exch./use flag acc. muD customizing  and the relevant data package is involved.