Question:
Hi Team
When we are running the process chain system throws a mesaage
Status change of process PSAPROCESS UPDATE_WBS_ATTR(while loading 0wbselmnt object) save status and trigger events if appropriate.
when I click yes the chain used to continue.
The main problem is if i just start meta chain and do not monitor the chain used to stuck in the middle due to this reason at that object. we are using meta chains like first run attributes chain, next text chaina nd next hierarchies and transaction.
Due to the above problem the following chians after attribute chain (text,hierarchy and tranasction)are also stuck,because unless one chain is completed the other one wont start.
I think we are missing some entry in a table for either RSPROCESS OR PSAPROCESS. Has any one experienced this type of problem???
Any help is highly appreciated.
we are on 3.OB patch 12.
Best Regards
Mihika
Answer:
Hi Team
Can anyone help pleaseeeeeee
Thanks
Mihika
Answer:
can't help you with this one
Answer:
Hi El Belgio
Regards
Mihika
Answer:
Did you already checked OSS. I'm on BIW 30b SP11 and had some problems with loading and process chains. So far, all my problem are documented in OSS with notes from SP 12 and SP 13. Maybe contact OSS, with a message
Answer:
Mihika,
I guess this reply will be too late to answer your question now, but my limited experience of process chains may be able to give you at least a little help.
Clearly, as you stated, if one process chain does not complete then the susequent local process chain in the meta-chain is not triggered. The only way I know of getting around this is to use the red/green (succeed or fail) type of link between processes so that every process is run even if it fails and goes red.
The only things that can stop a process chain built like that is a chain problem (e.g. missing variant, missing info packages, inactive rules, etc) or a repeated failed delta load. If the previous delta failed, and is not manually QA'd to fail from the monitor screen (and removed from targets) - then the fail is terminal and the package won't run next time. The consequence of this is that the next event is not triggered, and the metachain will stop right there.
Also, be sure to use the red/green type link between all the processes in the metachain.
The SP is important too, check OSS and see if your problem is there. Finally, if all that is too obvious, then time the master-data loads and leave what will run in the metachain!