sap business workflow –transport task attributes from one server to another

SAP Business Workflow –Transport Task Attributes from one Server to Another

Applies to: SAP 4.7, ECC 6.0

For more information, visit the Business Process Modeling homepage in SDN.

Summary SAP Business Workflow – Transport task attributes from one server to another Server. This is useful for SAP workflow development.

Author: Arghadip Kar

Company: IBM India

Created on: 18 February 2009

Author Bio Arghadip is working as a SAP Workflow Expert in IBM India for the last 3 years. He has been the Top Contributor in SAP NetWeaver Platform in the Year 2007-2008.

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com © 2009 SAP AG 1

http://sdn.sap.com/irj/sdn/nw-processmodeling


Table of Contents Transporting Task attributes from development server to subsequent servers. ................................................3 What is the Problem? .........................................................................................................................................3 How to Get it? ...................................................................................................................................................12 Related Content................................................................................................................................................19 Copyright............................................................................................................ Error! Bookmark not defined.



Transporting Task Attributes from Development Server to Subsequent Servers After doing a SAP Workflow Development it is necessary to transport the Task attributes of the SAP Workflow Template as well as the Standard Task. If this attributes is not transported we have to manually change the attributes which can be very critical to the business as the Workflow instance will all be stuck.

What is the Problem?

After going to the Workflow design by from PFTC transaction code we have to click on the relevant step that has a Dialog(User Interaction) Task. Here we have to click on the Red Drum Button.



On Clicking on this button (Red Drum Button in the Previous screenshot) we are presented with this screen. Here we have to click on the Task Attribute Button.



On Clicking on the Task Attribute Button we are presented with the following options. By default General Forwarding allowed is chosen. Suppose we want the make this task as General Task which means this Task is executable by all Users.



We have chosen General Task and we will click on the Transfer Button.



Now the Task is classified as General Task



On returning back to the Workflow Builder screen we can see the Agent Assignment with green colour indicator.



Lets check this same Workflow Template in another client RS6(810).



The Agent Assignment is not having a Green Indicator which suggest Task attribute not reflected lets check by clicking on the Red Drum button.



The Task attribute is not General hence the attribute did not get reflected.



How to get it? There is a program RHMOVE30 (Transaction Code: RE_RHMOVE30) that we need to check.

Lets give the Report name and execute.



We are presented with this screen.



We have to Provide the Plan Version as 01 this depends upon the Plan version that is configured in system. Here it is 01. We have to give Object Type as TS and the Object Id as 90001451. We have to Uncheck Test and With Lock and just check Transport Objects and then Execute.



On Execution we are provided with this screen. We have to click on this button and then click on Transport/Delete button on clicking on this button we are presented with following screen.



Click on Create Button and create a Customizing Request.



On saving this we get the Request number.



If we release this transport the Task attribute will get transported will get reflected.

After Releasing the Transport we check again and find the Attribute as General.



Related Content Reference 1: Maintenance of Agent Assignment

Reference 3: Creating and Maintaining Tasks

SAP Business Workflow page in SDN


http://help.sap.com/saphelp_47x200/helpdata/en/c5/e4b535453d11d189430000e829fbbd/frameset.htm

http://help.sap.com/saphelp_47x200/helpdata/en/5f/5b0aa2b5cb11d2b476006094b9ea0d/frameset.htm

http://sdn.sap.com/irj/sdn/nw-processmodeling?rid=/webcontent/uuid/10ff0453-ae33-2a10-7984-9d8df609d8f9



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 document, 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 content of this document.

sap business workflow –transport task attributes from one server to another

Documents

sap ag

sap workflow development

sap workflow template

sap workflow expert

transporting task attributes

general task

sap community network

standard task