SAP Business Workflow Guidelines On Transporting Workflow From One Server To Another Server
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 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 Business Workflow: Transporting Workflow from one server to another server
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 Business Workflow: Transporting Workflow from one server to another server
SAP Business Workflow: Transporting Workflow from one server to another server
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).
Transaction code swetypv will have the entry maintained as shown below:
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:
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.
SAP Business Workflow: Transporting Workflow from one server to another server
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 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 Business Workflow: Transporting Workflow from one server to another server
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 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 Business Workflow: Transporting Workflow from one server to another server