Question:
Hi,
A dumb question:
Are the process chains need to be transported from dev. system or we need to create in the production directly. The question is because the infopackage names etc are different and not all source system properly connected in the dev. system
thanks in advance.
Answer:
Hi:
It depends on the support pack. We ran into a bug in the earlier
releases. If you're rather current, you should be able to
do this in the Transport Connection (See process chains there).
Best of luck,
Becca
Answer:
Hi
Ideally you should create your process chains in DEV box and move them
across to PROD box. I ran into the same problem some time ago and found the solution as follows:
1. Include all required infopackages in your transport (you may need to create a separate transport for this and move all the infopackages into PROD prior to transporting the process chain).
2. Do not include any source systems in your transport (you should be able to de-select them in transport connection). You may need to expand all nodes in order to see the source systems within the transport connection.
I hope this helps.
Cheers,
Srac01
Answer:
Even though SAP idealogy is to transport everything, there are certain BW things which you cannot or may not really want to transport.
In the case of Process Chains, I initially started out transporting them, but I have sinced moved away from that and maintain PC's in each box. I still transport the InfoPackages.
Mostly it became a huge task to maintain PC's via transport as what I wanted to do with them in my Production Box is always different then in my Dev Box. In production, I want chains which run and do complete daily or weekly tasks. In Dev I am running chains to test, debug, or load test different scenario's and schemes.
Also, anytime I executed a PC' in DEV it wants to create a transport for it, even though it is really something for just Dev.
My .02
- Stephen
Answer:
Thank you all.
I think I will go with SBobcat's suggestion as I have many systems connected in the prod, but not all those currently connected in Dev.
Thanks.