Global Process Route Template

 

A global process route template enables you to transport global process route templates between systems and clients in your system landscape via Customizing requests. In the destination system and client, you can activate the global process route template and make it available as a process route template, which, in turn, serves as the basis for a process route.

Implementation Considerations

  • Note that global process route templates and all associated features are available for use in the Engineering Record (component PLM-WUI-OBJ-ECR) only.

  • The business function Engineering Record Development on PLM Web UI (/PLMU/ER_1) is a prerequisite and must be activated.

  • The sample role Maintain and Transport Global Process Route Template (SAP_PLMWUI_PRT_MAINTAIN) can be copied and provides users assigned to the role with authorization to create, display, change, activate, delete, and transport global process route templates on the PLM Web UI.

Features

  • Access to Global Process Route Templates

    You can access individual global process route templates directly in create, change, or display mode. All options are available directly on the Web user interface (Web UI) of SAP Product Lifecycle Management (SAP PLM).

  • Global Process Route Template Workbench

    You can access the workbench on the Web user interface (Web UI) of SAP Product Lifecycle Management (SAP PLM). In the workbench, you can:

    • Search for existing global process route templates

      The system displays a list of global process route templates based on your specified search criteria. In the table, you have a quick overview of which global templates exist, and whether or not they have been activated or changed since their last activation.

    • Activate global process route templates

      The Activate button activates the global process route template or templates you selected in the table. This either creates new or updates existing process route templates that are based on this global process route template in the current system and client. Note that process routes already created based on these process route templates prior to the change are not changed automatically. You can, however, create new process route instances based on the activated process route templates.

      When you choose Activate, you access a guided activity with two steps:

      1. In Step 1 (Verify), the system checks the consistency of the data in the global process route template. If there are inconsistencies, these are displayed in the Detailed Log in the lower screen area. You must resolve any issues that appear in the log and ensure that the statuses for all messages is Success (green) before you can continue with the activation.

      2. When you click Next, you access Step 2 (Activate), where you can check your global templates and click Activate to complete the process.

    • Transport global process route templates

      The Transport button adds the global process route template or templates you have selected in the table to a Customizing request. The global templates you have selected are then transported, via this request, to all other systems and clients that are connected to this system in your system landscape. Note that to initiate the transport, you must release the related request. You can check whether or not a suitable request exists or release a request in the Transport Organizer (transaction SE09) in the backend system.

    • Import global process route templates via RFC

      You can import global process route templates to your current system and client using an RFC connection. To do so, chooseStart of the navigation path  Additional Functions Next navigation step Import via RFC End of the navigation path from the workbench. Note that you must maintain an RFC destination in your user-specific parameters to use this feature. You can also access the user-specific parameters via Additional Functions. RFC connections are maintained in Configuartion of RFC Connections (transaction SM59) in your backend system.

  • Agent Mapping

    When you activate a global process route template, you can create a mapping between agents maintained in your global templates coming from other systems and clients (Source Agent) to agents in your current system and client (Target Agent). This may be necessary if, for example, a source agent does not exist or does not have the same ID in the current system and client. If a relationship between source and target agent has been mapped once, this will be available for all global template activations. You do not have to maintain each mapping for each global template.

    We recommend that you perform agent mapping as a part of the activation step – see Activate global process route templates above. If an agent doesn’t exist, a corresponding message will appear in the Detailed Log of the guided activity. If there are messages to be resolved, choose Agent Mapping at the top of the screen. The agent type and source agent are defaulted, based on the template or templates selected for activation. You can add the corresponding target agent in the current system and client, and choose Save.

    You can view and maintain agent types in Customizing under Start of the navigation path SAP NetWeaver Next navigation step Application Server Next navigation step Basis Services Next navigation step Records Management Next navigation step Customizing for Process Route Next navigation step Specify Object Types and Assign Activity Types End of the navigation path.