on 07-22-2009 10:46 AM
Hi
Am working on following scenario:
#Two request files merged to map to RFC request ( 2:1mapping )
RFC response is split into two response messages( 1:2 ).
I have done the whole thing in BPM that looks somewhat like this :
Fork(Rec1 , Rec2)-> Transformation1(2:1 map) -> Send(Synchronous BAPI call) -> transformation(1:2 map) -> send(Response 1) -> send(Response 2)
1st part i.e File Merge(2:1) works fine and the request is formed as desired. Next step when synchronous call is made to the RFC the response recieved is where i am facing issues. I dont get the expected response and eventually the following steps fail.
When tested the same RFC(BAPI_SALESORDER_SIMULATE ) in tx SE37 with same data it works fine.
But when same data is sent from XI it returns a error message in place of the response.
Error Message states "Please enter SoldToParty or ShipToParty Number" .
Irony is sold-to-party is sent in the request message and can be seen in payload in monitoring.
Any kinda help is appreciated !!!
Soumen ,
Kindly use the bapi in below mentioned fashion :
1. Make sure that bapi commits...there will be a check box option in RFC receiver CC side for this.
2. Make sure that Sold to party/bill to party field is of 10 char before passing it to SAP.
Regards,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
> 1. Make sure that bapi commits...there will be a check box option in RFC receiver CC side for this.
>2. Make sure that Sold to party/bill to party field is of 10 char before passing it to SAP.
@ Santosh :
I checked the tab in CC but still the same issue...Do we need to add something to the Name/Value section below that?
And yeah I am sending 10 digits only..
BTW do we need something additional when we call a BAPI from XI apart from the data we normally use in tx SE37.
Can my Configuration be a problem?
For this synchronous call in BPM I have created :
a) 2 interface determinations...One from BPM to ECC and another from ECC to BPM. But both are without any operation mapping as the message types are same & both are synchronous...
b) 1 receiver determination i.e : from BPM to ECC.
c) 1 receiver agreement.
You must have created a Receiver determination from IP to ECC. Are you using sync RFC interface here. It seems that the output of first transformation is an abstract message interface which has to be mapped to RFC message type although it would be 1:1 mapping. Somehow the values are not passed to RFC properly.
Regards,
Prateek
Issue's solved...Configuration was fine...Issue was with data i was passing...
Actually its not necessary if a FM works with some data in SE37 it would do the same when data is sent from PI...that was the catch in here...hence had to change teh data that i was feeding...For example for Sold To Party initially I was sending 'SP' but thats not what would work...i had to send 'AG' instead...
Anyways , thanks for the inputs guys...
@ Santosh : The 'commit handling' checkbox needs to be checked when we are updating Database...but mine was BAPI_SALESORDER_SIMULATE ' hence here it was not applicable.
Error Message states "Please enter SoldToParty or ShipToParty Number"
I believe this is generated by the function module.
Can you check in the code for what condition this error is returned.
May be some extra checks done here..
And accordingly see if data sent from XI has no issues.
When tested the same RFC(BAPI_SALESORDER_SIMULATE ) in tx SE37 with same data it works fine.
Hope you are copy pasting the data from moni..I mean better copy paste than manually type.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Either all mandatory fields are not provided your BAPI related configuration has some problem.
Regards,
Prateek
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@ Prateek : As I already mentioned am using the same values (that i use while testing in SE37) hence I guess there's no scope for missing out on mandatory fields.
Secondly, This error is returned when we dont provide the Partner parameters i.e partner role and partner number (which am providing here)...
Copy/Paste from sxmb_moni :
<TYPE>E</TYPE>
<CODE>VP112</CODE>
<MESSAGE>Please enter sold-to party or ship-to party</MESSAGE>
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.