| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| WMB 6.1 BAPI inbound processing. SAP doesn't receive answer. |
« View previous topic :: View next topic » |
| Author |
Message
|
| salvador.wbi |
 Posted: Tue Oct 20, 2009 1:00 pm Post subject: WMB 6.1 BAPI inbound processing. SAP doesn't receive answer. |
 |
|
Novice
Joined: 10 Jul 2009
Posts: 18
Location: Monterrey, Mexico
|
Hi guys, 
We have a message flow which is using the nodes of WebSphere® Adapter for SAP, we need an inbound processing (from the SAP server to the adapter) for simple BAPIs, The point is that everything works fine except for the thing of we cannot return any responses to the SAP server, i mean, we receive the petition from SAP server, then we do everything we have to do with that message, but when we try to return the result to SAP server it doesn't receive anything!, the message flow doesn't throw any exceptions, and if there's something that we have seen that is that the request made from SAP Server doesn't give any transactions IDs. We used to do this kind of projects with the WebSphere Adapter for mySAP, it was a simply RCF call,the id was the correl id and object event id, now we want to use the SAP nodes, but it is getting a pain in the !"··$3.
In the message flow, theres an inbound SAP node which receives the SAP petition, then there's a compute node which read the message and make a message for invoke a webservice, the webservice answers the petition, then we have to return the response to SAP Server RFC so we have made a message for an outbound SAP node which will return the answer of WBM, at the end, the message flow finishes and in the SAP server the function ends, but the fields with the answer doesn't have anything!.
Is there an example of how to do this? I mean, what do we have to do in order of receiving a RFC from SAP and return an answer!? 
We think the clue is the transaction ID. |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Wed Oct 21, 2009 1:15 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
In terms of SAP what you have is an asynchronous process.
- The IDOC call gets sent to your system
- your system receives the Idoc and assigns it a number that gets returned to SAP (msgid?)
- your system processes the IDOC
- your system notifies the SAP system of the IDOC Status using the msgid identifier of the IDOC in your system.
If you were to use a true synchronous BAPI call from SAP to your system, you need to be able to assign a success information to the process calling out to your system and not in a second async call to SAP.
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Gaya3 |
| Posted: Wed Oct 21, 2009 1:25 am Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
i am adding one more point to fjb_saper comments
if you are sending IDoc response(s) to SAP Server, you have to populate the IDoc Control Header part properly well, else it wont hit the SAP System.
The IDoc Control Header contains, IDoc No, RFC ID, Sender Port number, Reciever Port no etc etc.
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| salvador.wbi |
| Posted: Wed Oct 21, 2009 6:36 am Post subject: It is a bapi call! |
|
|
Novice
Joined: 10 Jul 2009
Posts: 18
Location: Monterrey, Mexico
|
| Quote: |
| if you are sending IDoc response(s) to SAP Server, you have to populate the IDoc Control Header part properly well, else it wont hit the SAP System. |
We are not using IDOCS, it is a simple Bapi RFC call that SAP Server have to do to the WMB, it is not an ALE, is a BAPI,
| Quote: |
If you were to use a true synchronous BAPI call from SAP to your system, you need to be able to assign a success information to the process calling out to your system and not in a second async call to SAP.
|
How do we do this?
we need to be able to assign a success information to the process calling out to our system!
help us!!!!! |
|
| Back to top |
|
|
| salvador.wbi |
| Posted: Wed Oct 21, 2009 8:42 am Post subject: SAP BAPI Inbound |
|
|
Novice
Joined: 10 Jul 2009
Posts: 18
Location: Monterrey, Mexico
|
It seems to be that in asynchronous processing, the SAP application does not wait for a response and the adapter does not have to be available when the SAP application makes the function call, i don't know if it means that there's no way to reply the request made from SAP Server.
What a shame! 
Websphere Business Integrator Adapter for mySAP rules with its RFC Server Module.
 |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Oct 21, 2009 10:39 am Post subject: Re: It is a bapi call! |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| salvador.wbi wrote: |
| Quote: |
If you were to use a true synchronous BAPI call from SAP to your system, you need to be able to assign a success information to the process calling out to your system and not in a second async call to SAP.
|
How do we do this?
we need to be able to assign a success information to the process calling out to our system!
help us!!!!! |
Well normally the SAP transaction scope would hold the FunctionHandler during the BAPI call (SAP JCO). The FunctionHandler would do a synchronous update of the variables and tables and at the end of the call go to the commit. Then controll would revert to SAP.
As you are using WMB to process you do have essentially an asynchronous process. I believe the SAP adapter is happy once the request has been dispatched to the queue.
You can always write your own JCO program to handle the Request, put it as XML to the queue and wait for the response from the broker. You can then fill the return structures of the call and release the synchronous call from SAP.
JCO 3.x is markedly different from the 2.x version but I believe the same principles will apply.
Have fun
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| salvador.wbi |
| Posted: Wed Oct 21, 2009 11:03 am Post subject: WMB inbounds need to be improved |
|
|
Novice
Joined: 10 Jul 2009
Posts: 18
Location: Monterrey, Mexico
|
| Quote: |
You can always write your own JCO program to handle the Request, put it as XML to the queue and wait for the response from the broker. You can then fill the return structures of the call and release the synchronous call from SAP.
|
The point is that we thought we could do this kind of things using the SAP nodes, as i wrote, for this projects we work with the WBI Adapter for mySAP which allow us to handle RFC just as we want, so for this project at least we won't have to do so much to get what we need. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Oct 21, 2009 11:08 am Post subject: Re: WMB inbounds need to be improved |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| salvador.wbi wrote: |
| Quote: |
You can always write your own JCO program to handle the Request, put it as XML to the queue and wait for the response from the broker. You can then fill the return structures of the call and release the synchronous call from SAP.
|
The point is that we thought we could do this kind of things using the SAP nodes, as i wrote, for this projects we work with the WBI Adapter for mySAP which allow us to handle RFC just as we want, so for this project at least we won't have to do so much to get what we need. |
Did you read up on the limitations of the adapter?
Keep in mind that you are not calling an inbound BAPI to SAP but an outbound BAPI from SAP to your system.
Open a PMR and ask clarification from IBM.
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| salvador.wbi |
| Posted: Wed Oct 21, 2009 11:50 am Post subject: |
|
|
Novice
Joined: 10 Jul 2009
Posts: 18
Location: Monterrey, Mexico
|
| Quote: |
Did you read up on the limitations of the adapter?
|
Yes, i did, but everything is confused, we've done our message flow using the old technique with the WBI Adapter for mySAP.
We haven't still found how to return the response to SAP using the SAP nodes, and everything tell us it is not possible, at least not in the last WMB version.
Maybe later we'll send a PMR.
tnks!  |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
