SAP Business Workflow: Guidelines on Transporting Workflow from One Server to another Server.

Applies to:
SAP 4.7, ECC 6.0.

Summary
This article describes the guidelines to transport Workflow from one server to another server, the common check points and miss outs post transportation & the procedure to rectify them. Author: Mehreen Nizar Dudhwalla

Company: Larsen & Toubro Infotech Limited Created on: 20 March 2010

Author Bio
Mehreen Dduhwalla is a Software Consultant in Larsen & Toubro Infotech Limited. She has three years of SAP experience. She has worked extensively in ABAP and Workflow.

SAP COMMUNITY NETWORK 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 1

SAP Business Workflow: Transporting Workflow from one server to another server

Table of Contents
Guidelines while Transporting Workflow from one server to another server: ................................................... 3 Common Checkpoints & Missouts Post Transportation .................................................................................. 5 Check Points: ............................................................................................................................................ 5 Miss Outs: ................................................................................................................................................. 6
Event Linkage and Start Events are active or inactive. ................................................................................................ 6 Agent Assignment not maintained: .............................................................................................................................. 7

Steps to Add Agent Assignment to a Transport Request: ........................................................................... 8 Creating Customizing Request to save Task Attributes (Agent Assignment) in case of Dialog Tasks: ......... 8 Related Content .......................................................................................................................................... 13 Disclaimer and Liability Notice ..................................................................................................................... 14

SAP COMMUNITY NETWORK 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 2

SAP Business Workflow: Transporting Workflow from one server to another server

Guidelines while Transporting Workflow from one server to another server:

After completing a SAP Workflow development, its important that the objects related to the Workflow Development are transported from one server (development) to another server (quality, production). This article will help users while transporting Workflow from one server to another server. 1. While Creating Workflow Template, Business Object, Stand ard Tasks etc its a good practice to have all workflow related objects stored under one common transport request. 2. While transporting to a new system it is absolutely necessary that Workflow Settings have been maintained in the transaction SWU3 in the new server especially the Configure RFC destination setting should be active. In case it is de-active, the basis team can active it.

3. The sequence of Transport Request moved from one server to another is absolutely important in case of Workflow transports too like any other transports especially when objects are stored in separate transport requests. Workbench Requests need to be transported first followed by Customizing Requests. For example : Business Object (BOR) which includes events, methods etc needs to be moved first followed by Standard Tasks, Rules, Class, function modules & Workflow Template. Customizing Request may include event binding, agent assignment etc. Workbench Request contain the remaining objects like Standard Tasks, Workflow Templates, Business Object Program, Business Object Types (BOR) as shown below:

SAP COMMUNITY NETWORK 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 3

SAP Business Workflow: Transporting Workflow from one server to another server

Business Object Name

Business Object Event Name

SAP COMMUNITY NETWORK 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 4

SAP Business Workflow: Transporting Workflow from one server to another server

Common Checkpoints & Missouts Post Transportation

Check Points: Once the Workflow is transported to the new server, the following are the checkpoints that need to be checked for the proper working of the workflow. 1. Business Object transported with active status & generated successfully. 2. Correct Workflow Template has been transported with proper version active. 3. If start conditions has been defined check if it is active. 4. Workflow Template & Standard Task transported along with their binding maintained properly. 5. Standard Task & Method Binding maintained properly. 6. Event binding is active. 7. Event Linkage is active & checked. 8. Agent Assignment in case of dialog tasks is active. 9. Ensure that dialog tasks are set as general task or maintained with the Possible agents explicitly. 10. Always check that once the workflow has been transported, new version is created in the target system.

SAP COMMUNITY NETWORK 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 5

SAP Business Workflow: Transporting Workflow from one server to another server

Miss Outs: The most common miss outs after workflow transports have been moved from one server to another are: Event Linkage and Start Events are active or inactive. There are cases post transportation from one server to another server that the event linkage and Start events appears Inactive in the new server. The reason could either be that the customizing request which had the event linkage or start event was not transported properly or the type linkage checkbox is still unchecked in the transaction swetypv (as shown below).

Should be active (green)

Should be active (green)

Transaction code swetypv will have the entry maintained as shown below:

SAP COMMUNITY NETWORK 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 6

SAP Business Workflow: Transporting Workflow from one server to another server

Should be checked

Agent Assignment not maintained: In case of dialog task, agent assignment is a must for the Work item s to go to the users inbox.There are cases after post transportation of dialog tasks to a new server that the agent assignment does not appear active as shown below:

Agent assignment inactive

SAP COMMUNITY NETWORK 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 7

SAP Business Workflow: Transporting Workflow from one server to another server

Users have to manually go and do the agent assignment in the new server which may be impossible at times.

Steps to Add Agent Assignment to a Transport Request:

While setting the dialog task attributes in development server, the settings are not always saved in a customizing request. The following steps can be used to make sure that Agent Assignment is saved to an appropriate Customizing Request which can be transported to the new server while transporting objects. Since this request is a Customizing Request, it should be sent after all Workbench request have been transported. Creating Customizing Request to save Task Attributes (Agent Assignment) in case of Dialog Tasks: Step 1: Go to transaction RE_RHMOVE30 or Execute Program RHMOVE30 Step 2: Select Plan version: 01 Select Object Type: TS Select Object ID Also, In the Transport section enter or create your change request Select "Transport Objects" and Deselect "Test" and "With Lock" : your 8 digit task id number e.g. 99900209

SAP COMMUNITY NETWORK 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 8

SAP Business Workflow: Transporting Workflow from one server to another server

Step 3: Execute and go to next screen.

Step 4: On the next screen select the row with your task id Press "Add to Transport" Then again select the row with your task id and press "Transport/Delete" this will bring up the prompt to create a customizing request as shown below. Remember: After clicking on Add to Transport you need to further click on Transport/Delete without doing this together you wont see anything happening on your screen.

SAP COMMUNITY NETWORK 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 9

SAP Business Workflow: Transporting Workflow from one server to another server

Step 5: Create the transport request to add the agent assignment in the transport by clicking on the create button.

SAP COMMUNITY NETWORK 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 10

SAP Business Workflow: Transporting Workflow from one server to another server

SAP COMMUNITY NETWORK 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 11

SAP Business Workflow: Transporting Workflow from one server to another server

Step 6: Go to SE09 and the Customizing Request will have the agent assignment as shown below.

This Request can now be transported to the new server. After transporting to new server always refresh the buffer using the Transaction SWU_OBUF.

SAP COMMUNITY NETWORK 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 12

SAP Business Workflow: Transporting Workflow from one server to another server

Related Content
http://forums.sdn.sap.com/thread.jspa?threadID=1504447 https://forums.sdn.sap.com/thread.jspa?threadID=1099553 https://forums.sdn.sap.com/thread.jspa?threadID=924761 https://forums.sdn.sap.com/thread.jspa?threadID=225491

SAP COMMUNITY NETWORK 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 13

SAP Business Workflow: Transporting Workflow from one server to another server

Disclaimer and Liability Notice

This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade. SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this do cument, and anyone using these methods does so at his/her own risk. SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the conte nt of this document.

SAP COMMUNITY NETWORK 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 14