Transport Issues on 1st WF

[Ronen Fox]

looks like the simplest solution is to build an org. structure in DEV that
has the same positions as in PROD, only org units and positions should be
used. If you can somehow (maybe with ALE) get the same structure in DEV,
make the assignment there, and then the workflow should be transported
without a problem. If you are planning to implement more workflows, may i
suggest that from now on build your company org. structure in DEV and
transport it just as you would do with standard customizing and development.
 
-----Original Message-----
From: Gordon Blackmore [mailto:gordon.blackmore at sasktel.sk.ca]
Sent: Wednesday, August 28, 2002 12:02 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Transport Issues on 1st WF
 
 
Our develop box has very little data in it and in no way reflects the
production data. Specifically it does not have the organization data. Our
production environment does not allow for creation of workbench change
requests. An agent for a task is a position and the valid positions do not
exist in development. When my workflow is transported to production the
task does not have agent.
 
I am looking for options. Our BASIS people say we can get permission to
"open up the system" but this a major issue in our firm. As well, we see
this WF as the 1st of many and do not want "open up the system" every time
I need to define an agent.
 
Just when I though I was away I meet workflow transport problems.
_____________________________
Gordon Blackmore
SAP Analyst
SaskTel