on 05-29-2008 5:39 AM
Hi,
I am working in a scenario where I need to receive messages from multiple publishers on different fork branch and sequence it. I have configured the scenario as mentioned in basis namespace example. I but it looks like even in parallel branches fork expects one of the receives step needs to be configured for start process and remaining with start process flag unchecked. If I mark all the receive process as start process it expects only the last branch to be sent first. If other message arrives first it shows scheduled to be delivered and doesnu2019t get processed.
Did any face this issue? Any help appreciated in advace.
Hi
This should not happen. If you mark all receive steps as start of process then if any message will arrive it will trigger the BPM and then other will receive to same BPM instance based on correlation.
Check correlation you defined for those receive steps are correct and including all three messages in correaltion.
One other reason also can be queue to show ur message in sheduled state. Refer folllowing pdf:
[https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e0ff0006-3901-2a10-9e97-a71b423da545]
Regards
Sami
Reward points if helpful.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
As I mentioned earlier. I if I check all the receivers to be the tsart process it expects the last branch or if I check one of those to be the start process it works fine. But I can't define any one of those to be the first message. so the problem still exists
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes it is the same one. But it is always initiating the correlation on the last branch, remaining all branch it shows parmanent error in starting the process. This is irrespective of the receiver. If I swap the receiver in the fork it works for the one which is in the last branch.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi ,
I donu2019t see any cache issue because what ever changes I make BPM works according to that also SXI_CAHCE is giving 00 status for the BPM. And also it shows all start flag option as it is in parallel branches not in sequence.
I have different Abstract class for each message but same message structure as it is a CIM. Can that be problem but the scenario in basis namespace also has same configuration. Did anyone executed this example?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
HI,
The start process flag in Receiver step indicates that this will be the starting point, thus in other Receiver steps which are not in loop or in Fork will not get this flag option.
Then the sequence of these messages will be imp else it will go in scheduled step.
You can either use the Wait step for the secondary message before the receiver step or have to serialize the messages to maintain the sequence.
Thanks
Swarup
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Looks like your latest BPM scenario is not cached properly.
Delete work flow items created by your BPM using SWWL TCODE.
Then, in SXI_CACHE tcode try to delete/reactivate your BPM process and execute your scenario.
Thanks,
Gujjeti
Edited by: Praveen Gujjeti on May 29, 2008 6:59 AM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
101 | |
13 | |
13 | |
11 | |
11 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.