on 08-29-2006 3:47 PM
HI All,
I am getting error in sych send in BPM.
My BPM steps are :
Receive->Transformation-><b>sync Send</b>->transformation->syncSend->syncSend->transformation->Send
I am getting error in d step mentioned in bold.
There im making a synch call to a RFC using RFC receiver adapter.Adapter is workin fine in messagemapping.
In Monitoring the error im getting is
<b><i>CL_SWF_XI_MSG_BROKER method SEND_SYNCHRON cannot
be executed
Empty container element specified during save</i></b>
Regards,
Sumit
Hi,
Have a look into these SAP Notes: 830803,710445.
Check the transformation/and Send Sync step once again and try to activate the BPM and check the scenario, after Cache Refresh in SXI_CACHE.
Regards,
Moorthy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
I mentioned the wrong message types in the abstract interface created for RFC. Itz working now.
Can anyone explain ...
When we create a Sync Inbound Message Interface
We have to specify:
Input Message ---here input is input to RFC(import para)
Output Message --here output is export parameters
So if we create a Abstract Inbound MI
We specify this way...
<i>Input Message ---here input is export from RFC
Output Message --here output is import parameters</i>
<b>Why is it so ??</b>
I know we use AI in BPM..ie they dont have any direction.
Bhavesh,
<i>So, take the output of the Trasnformation Step from MONI and then test your RFC call with this data and see if it returns valid data.</i>
How to test after taking Data from transformation step??
from the test button in browser?? or test in messge mapping..
Regards,
Sumit
Message was edited by: Sumit Khetawat
Hi Sumit,
<i>Why is it so ??</i>
you are mapping Input message to Output message in each step.So they have to be designed to select your message mappings in Interface Mapping.
and also for map test
/people/michal.krawczyk2/blog/2005/09/16/xi-how-to-test-your-mapping-in-real-life-scenarios
Sekhar
Bhavesh,
what i meant was...
<i>When we create a Sync Inbound Message Interface
We have to specify:
Input Message ---here input is input to RFC(import para)
Output Message --here output is export parameters
So if we create a Abstract Inbound MI
We specify this way...
Input Message ---here input is export from RFC
Output Message --here output is import parameters</i>
Now for ABs Inbound MI,
why dont we give the Input message as input to RFC?
Regards,
Sumit
Hi Sumit,
<i>Now for ABs Inbound MI,
why dont we give the Input message as input to RFC?</i>
Request Mapping :
OutputMessage Type(<i>here output is import parameters</i>
) to Input Message Type(import para)
Response Mapping :
Output Message type (here output is export parameters)to Input Message Type(here input is export from RFC)
I think it clarifies your doubt..
Sekhar
Hi,
this might measn that your transformation step
is not mapping correctly and you're trying to post an empty RFC call
check the transformation step log in BPM logs
if it maps anything as output (technical workflow log)
Regards,
michal
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
10 | |
10 | |
10 | |
7 | |
6 | |
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.