Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Please see also manual „Tips and Tricks", chapter „Multiple Usage" regarding the different way of handling multiple used documents (MUD).
This chapter will describe the required settings for the newer method multiple used documents (muD) using the MUD muD monitor.

General settings to link documents are described in chapter Data Packages (group), the display of the MUD muD monitor is described in the User Manual (CFM | ProConfiguration | SAP Solution PLM Configuration Manager) muD Monitor.

Info

ProNovia strongly recommends using this new option for multiple used documents as described in this chapter.

Info

The handling of the MUD muD is only possible for data packages, which do have a document info record with a structure.

Info

For more information about the MUD logic to determine usage, action and status please refer to manual „Tips and Tricks" in chapter "Multiple Usage".

...

Changes based on configuration scenario („old")

  • A change is started on a usage and the MUD will be marked for versioning.

  • Depending on the settings, all other usages will also be included in the change process.

...

muD are created and changed independently

...

of the

...

usages and

...

then

...

exchanged ("new") via the muD handling of the ProConfiguration

...

in

...

the usages

...

.

  • The usages and the

    MUD

    mvD can be

    handled

    maintained independently of each other.

  • After a MUD has been released all usages will be shown on the MUD monitor.

  • The MUD monitor allows the handling
  • of the new version in all its

    When a new mvD version is released, all usages are entered into the mvD monitor for editing.

  • Via the mvD monitor the new version can be handled in the usages:

    • Exchange

      , when

      if the usage is currently

      under

      in a change.

    • Exchange

      after a

      via the start of a change on the usage.

    • Mark

      Marking for the next change of the usage.

    • Ignore this version of

      MUD

      the mvD for a usage.All

  • The necessary actions can be

    executed

    performed online or

    batch wise.

    in batch.

  • Usage of such objects in the data packages:

    • Either these should be entered with an object relevance in the data package, which does not allow versioning and creation (option Without new creation/vs. in object relevance activated).

    • Or this is allowed, but then the option Use OBJ validities should be activated in the object definition for the mvD, so that the validity of the mvD is not handled/moved by the ProConfiguration configuration.

  • The handling of muD with this functionality is only possible for distinct data packages with document info record and BOM.

A muD can be handled with the functionality with the muD Monitor as soon as the corresponding object types for the corresponding functionality are entered in the Customizing.

Subordinate items:

Child pages (Children Display)
depth2