Workflow - Transport

Hi All,
Please let me know steps / checks to be taken care before and after Transport of Workflow across systems.
We have defined Business Objects, Workflow Definition, Organization Structure, Customizing Setting, Prefix Number Range under various tasks and TR.
1. Is there any sequence in which various task / TR is to be released?
2. What steps to be taken care after TR is released?
3. Will the Organization Structure, Assignment etc be transported after releasing of TR?
Appreciate your inputs.
Regards,
Ramesh

Hi Ramesh,
Normally you release the transports in the order they are created. If this is the first time anything's transported the sequence shouldn't be a problem. mostly because one object is in one transport, but double checking couldn't hurt.
After your transports are transported refresh the buffers so the changes will take effect. Also check your agent assignments. If you have defined any tasks as general tasks, you have to do this again on the target systems.
If the Organization Structure will be transported depends on your settings. Normally if you use HR the organizational Structure will not be transported because it is maintained on the Productive system.
These are some points I could give, but I don't think this is conclusive and others can maybe give some additions.
Regards,
Martin

Similar Messages

Problem in workflow transports

Hi guys,
I have a strange problem like I made some modifications in PO release wf. It is working fine in Development and it was working fine in Production also for a couple of wks. But I do not know what has happened suddenly, it is taking the oldest version of the workflow . Is there any specific way in transporting workflows.
Please reply back to me asap , as it is creating lot of problems to us.
Thanks
Bhaskar

hi,
i faced a similar issue, probably this should help u out :
Phenomenon:
You have changed your workflow template in client 000. If you look to the workflow definition in another client with SWDD, then you see the newest version as just maintained in client 000. But at runtime, the old (former) version of the workflow definition is used.
Cause:
When activating a workflow template, then also some client specific data is replicated from client 000 to the other clients. In this replication there is currently an error. I just talked to a workflow colleague. The problem we have observed seems to be just the tip of an iceberg ... . They are working on the issue(s) related to this.
Workaround:
Execute function module SWD_WFD_REPLICATE_FROM_9999 in the client, you need to have the newest template definition. Enter your workflow template ID (with pattern "WSxxxxxxxx") in parameter IM_TASK and execute. Make sure that you do not lock the template in SWDD.
Then you also (may) need to execute transaction SWU_OBUF to synchronize the buffer.
i hope this should work.
Regards,
Saujanya

Issues implementing "workflow transports"

hi all!
I am trying to configure a simple workflow for change requests (transport):
In stms, the workflow engine has beend define. For the moment no QA. RFC is fine and my user has been defined as approver for all request(system, projet, number ='*').
When an order is released the pop up appears and i can fill all the required information. Test is ok, i send the request. A message says that everything is fine, waiting for admin approval.
But i don't recieve anything in my stms inbox. However i can see it if i use the search tool.
I have a sap_all, do i need a special profile to do so?
Thank your help,
Regards,
Julien
Edit:
additional question: is there any way to know who is of charge of a proposal request approbation ?...
Edited by: Julien LE GAL on Feb 25, 2009 10:54 PM

finally the problem was because of an old rfc customizing..
Other question: we have two environemments where we can create transport request. From the controller, transport workflows are working fine.
From the other one, i can only send requests to the controller.
Any idea?
Regards,
Julien

Workflow transport dependencies

Hi ,
I am about the transport my workflow to quality system and I cant afford to miss out on dependencies etc as the testing demo is to start tomorrow.
Could you please advice me on the order of transports given the problems of dependent objects you faced ?
this is the order of transport planned :-
position in org staffing
extended BO
Function Module used in method
Rule used in workflow template
Tasks used in workflow template
Workflow template
agent assignment of the tasks
start events
start conditions
Any comment would be very useful,,........
thanks very much
R

example -
busines object method uses> function module
If FM go first, as it is standalone, I mean it is not calling BO method so wont search for it calling point. dont worry
task uses> busines object method
they can go together
workflow template uses> task
they can go together
so suppose a situation is that workflow template reaches when the task is not there in QA system then does it create error so much so that even after task is imported into QA, the workflow template will still be erroneous ? and will involve retransport of workflow template ?
Dont worry, just transport it nothing wrong will happen, if accidentally some thing goes wrong, you can always re transport it.
If you still think that it will create issue, talk to your Basis Admin he/she will create transport of requests for you and then you dont have to care about sequencing issue.
Cheers
Jai

Activate workflow transportable

Hi Gurus,
When generating the workflow, it is asking me for a workbench request. Is this transportable to other clients/server? Also, when activating event, it also asks for workbench req. Can I transport it as well? I tried it several times but it doesnt reflect in our QAS/PRD. How can I activate event/workflow?
Regards,
Paul

Hi Paul,
When you create a workflow template with tasks etc the system would ask for a workbench request. For all customizings like agane t assignment, start events, a customizing request is required. Both of these requests can be transported to other systems.
Please note to transport workbench request before the customizing requests.
Also synchronize the buffers after transporting the same using transaction SWU_OBUF.
Hope this helps!
Regards,
Saumya

Duplication of workflow, transport of workflow

Hi All,
In an application we use workflows for certain procedures.
We have workflows that are almost alike to each other. These we have to build one by one nbecause it is impossible to duplicate a workflow. (the function is greyed out).
Second. As we go from one environment to the other we use export repository but helas, the workflow is not exported. Is the only way to transport using archiving and unarchiving?
thanks in advance for your help
Harrie

Hi,
1. is it impossible to duplicate a workflow?
Ans:yes, till now in SP05 we dont have this functionality.
2.Is the only way to transport using archiving and unarchiving?
Ans: Yes, you are right. only archive and unarchive is only way to export repositories over the systems like:
development>quailty>production.
Pls reward if found helpful.
i think we are still on sameissue as Amol give steps, this is not the actual duplicate.
Duplicate always means to have same things in your record,
if you are changing names then how it remains dulicates.
BR,
Alok Sharma
Edited by: Alok Sharma on Jan 25, 2008 12:37 PM

Error while transporting the workflow object

Hi all,
Please be informed that while i transported the workflow changes to test system i encountered the sy-subrc 8 error as stated in below screen shots.

Hi Ranjith
Seems that the transport error is showing that your ID has locked the Workflow (user REDDYRAN).
Can you do a syntax check of the workflow transported in this transport - in pftc and swdd? Do we get any error?
Also see if you can execute FM SWD_WFD_REPLICATE_FROM_9999 in Quality (in SM37) - provide the IM_TASK = WSxxxxxxxx (your workflow number).
regards,
Modak

Incorrect Workflow version after transport

Hi,
A modification was made to the standard Booking Approval workflow (WS01200151). The changes were successful and a new runtime version was generated on the development system.
There seems to be a problem with the activation of Workflows transported to the QA system. After the transport no new version were activated on the QA system although the active version was included in the transport. (landscape: Development > QA > Production). I created a new version and also transported this, but the new version were not active. The status on QA was still "Runtime version, Saved".
I checked the transport log and there were no errors and all objects were moved to the QA system. However, when I check the workflow versions on QA, there are multiple inactive versions now QA. There are only 7 on development but there are about 60 on the QA system. The 2 workflows are not in-sync.
The QA system is not open for changes and it is not ideal to open it either because then we will have to open the Production system as well. Does anyone know why the active version were not transported and how to fix this besides opening the QA system for changes?
I am quite new to workflow and your help will be much appreciated.
Regards
Liza-Marie

Thanks for the feedback, I learnt something new.
The version in table HRS1205 on Development is 0007 and on QA it is 0006 and I executed function module SWD_WFD_REPLICATE_FROM_9999 but nothing is updated. I debugged the FM and found that it exits (without any exception) as the transport version details (date & time) is the same as the 9999 version (code line 91).
SWD_WFD_REPLICATE_FROM_9999 reads table SWDSHEADER and in this table the last version is 0182! I don't know how all the versions from 0007 and 0182 was created but this seems to be causing problems. I don't want to write a program to delete those redundant entries as I'm not sure what the impact would be. Do you know if there is a FM to delete the entries from table SWDSHEADER or any other table that would get rid of these versions?
To answer your question, I can view the WF in PFTC, there are no messages.
I will check OSS if I can find something.
Thanks for you help, it's much appreciated.
Liza-Marie

Condition doesn't work after transport to QAS system.

Hi all:
the condition doesn't work after the workflow transported to QAS system. the workflow designed has a constraint that only the creation of the document of Type M4 can trigger the workflow, but creation of Type M5 document can also trigger the workflow, could you please tell me the possible reason?
Thank you very much

Hi,
Once Try checking as pavan suggested whether the Customizing requested is transported.
To Maintain Workflow start conditions you can also maintain through SWB_COND and ensure its transported.
Regards
Narin

Urgent! Empty Workflow Template

Hi.
The Workflow template WS12300026 is empty in the latest SAP version... Anyone that knows why?
SAP delivers WS12300025 and WS12300026. The difference between the two is that with *26 the budget req. can be changed if rejected.
Best regards,
Eli-A.

Well I had a similar situation but that was with custom workflows.. anyways try implementing note 981295.. might be of help to you.
check out my Workflow Transport: Definition missing
for further info.
Best of Luck.!!
Anuj Sethi
Message was edited by:
Anuj Sethi

Folder for Transport-files

Hi,
want to get my transports from a SAP NW sneak to another NW sneak... but don't know where to find the transport files...
TIA,
Sebastian

Hai sebastian,
Just refer these links...
SAP Transports Workflow
Transports
Regards,
Srikanth.

PA40 hiring process - transport request

Hi All,
When hiring from PA40 transaction code in develepment server it will ask for transport request to create every time
if iam not selected the transport request to create it will save the record
but i need it will not ask any trasport request creation in hiring process from PA40 transcation code
we have other develepment server with same client settings in that server it will not ask any transport request when hiring
pls suggest
Regards,
Abdul Razzaq

client setting as showing below:
1.Automatic rec of changes
2.Changes to Rep and cross-client cust allowed
3.Protection level 0
the following entries in T77S0 table:
GrNam             SemID      Valueabbr        Text
TRSP     CORR          Transport Switch (X = No Transport)
TRSP     STOBJ          Redefinition: Standard Transport Object
TRSP     WFOBJ          Redefinition: Workflow Transport Object
The three fields of valueabbr are blank
Abdul Razzaq

Background task stays with status "in process" without creating any error

Hi all,
we created a two step approval workflow for parked documents based on the SAP WF templates WF WS10000051 (WF frame) and WS10000053 (two step approval sub WF). The problem now is, that after the two approvals have been given and the release flag is set the system should post the document. This is done in a background task. This task is started automatically but the status stays at "in process" and the document remains "parked" and not posted.
What we did so far to solve the problem:
1.) Check if shortdump has been created via ST22 --> not the case
2.) Refreshed buffer via SWU_OBUF
3.) Reacticvated/executed task with workitem id from log in SWIA
--> nothing solved the problem so far. Please help!
Thanks in advance. Johannes

Hello Johannes !
              You have asked "What do you mean with populate the value?"
                        Populating means conceiving the variable or container with valid value.In your scenario , with reference to your URL http://img851.imageshack.us/i/wflog2.jpg/ , POSTED_FLAG should be populated with value X.It should not be "Not Set".
                        With reference to your URL http://img717.imageshack.us/i/wfprotocol.jpg/, Set Release Flag step does not sets release flag.
                        It's evident from the URL http://img263.imageshack.us/i/flagreleasesetsw01.jpg/
            The solution for your problem is straight forward : Pass all the export or result parameters of RELEASE step to SET RELEASE FLAG step. Similarly , pass all the export or result parameters of SET RELEASE FLAG step to POST PARKED DOCUMENT STEP.
Answer for question 1 : After successful workflow transportation, it's version changes.Never mind the versions unless either of the versions are inactive or the version you require is inactive.
Answer for question 2 : The user WF-BATCH should have SAP_ALL and SAP_NEW profiles.
Regards,
S.Suresh

W/F not active in Prod.

Hi all,
I made some changes in a W/F in dev. and tested it as well, it worked fine.
All the BAPIs and BO used in the w/f were put into a TR. After transporting the TR to production, when I tried opening the workflow in production , i get a popup window showing active version.workflow type...etc. It does not find the active version of the workflow transported. My BAPI and BO changes have been reflected in Prod. but its unable to find active workflow. I tried re-transporting, but it still gives same message. What could be the cause of this and how to go about it?
As its on production, so the issue is on high priority for us. Would really appreciate your inputs.
Regards,
Divya

Hi,
(Following is may be one of the reason for this issue:)
1. Check if all the Agents and Roles you have used in workflow are available in PRD.
2. Do Syntax check in PRD you will come to know what is the error. (Sometime, you will get inactive version of workflow if your active version has any error in PRD).
Regards,
Salil

WF transorts: R3TR - SWFL

Hello all guru's,
Does anyone know what objects are R3TR- SWFL and R3TR- SWFP (WF: Logical Information Object and WF: Physical Information Object).
Worklfow was created for testing(prototype) purpose in training system, now I have to change workflow in DEV, I can't transport.
Does anyone has experience in this theme(with transport objects) ?
Many thanks in advance for quick answers !

Hello,
These are defeinitely not part of regular workflow transport objects (PDWS, PDTS etc.).
I suspect these are either related to the WIS or BW. Please always mention your system/version when asking questions, this is usually also relevant.
In any case, these transports would not be related to your problem. What exactly do you mean by 'can't transport'? Do you mean a training client? Though workflows are client-indepent, they can only be maintained in the original client. This is controlled by client-dependent prefix numbers in WF config (SWU3).
Hope that helps,
Mike

Workflow - Transport

Similar Messages

Maybe you are looking for