on 05-22-2007 3:24 PM
Hi everybody!
In my scenario I post an RFC call to a BAPI (BAPI_GOODSMVT_CREATE). The call succeeds (empty RETURN parameter, material document numer is returned). However, the resulting material document is not available in MB03 - I assume this is due to a missing COMMIT after the RFC call.
However, our system has SP 18 - and I have read that the RFC adapter is able to add a COMMIT after a successful call automatically starting from SP 14. What confuses me is the fact that the descriptions in the online sources state that I should check the "Extended Mode" checkbox in the RFC adapter config screen and then I should check the "Commit..." option. However, when I set the checkbox for extended parameters, I only get a simple table where I can enter property/value pairs.
Has something gone wrong with the upgrade and my RFC adapter doesn't have SP 18 yet? Or am I doing something wrong?
Regards, Joerg
Hi,
we have SP 18 as well. And we have a checkbox for "Commit Handling for Single BAPI Calls".
Check Help->Information in the Integration Direcotry to see which SP level your Java Stack has.
Maybe you just patch the ABAP Part.
As well you have to use RFC Client Parameter Advanced Mode.
There is also a Adavaced Mode Checkbox on "RFC Metadata Repository Paramter" There you see only a Table.
Regards,
Robin
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I just updated my post:
You have to use RFC Client Parameter -> Advanced Mode.
There is also a Adavaced Mode Checkbox on "RFC Metadata Repository Paramter" when you use the checkbox "Use Alternative Metadata Repository" There you see only a Table.
So maybe you use the wrong advanced mode?
regards,
Robin
To check your Adapter Version go to SLD.
Than Technical System Browser.
Technical System Type you choose Exchange Infrastructure.
There you see Adapter Engine on .... select the Application System where the Engine is running.
On Deployed Objects you can select there services.
there you see SAP XI Adapter: RFC with a version 3.0.<b>18</b>20060911124231.0000
regards,
Robin
Hi Joerg,
Check in your Repository if you imported the newest adapter metadata.
Check Software Component SAP BASIS - > SAP BASIS 6.40 -> http://sap.com/xi/XI/System
There Adapterobjects -> Adaptermetadata -> RFC
search after the attribute ..<b>singelBapiCommit</b>
Because you dont see a SP version there.
Maybe its better to search afer the label:
<b>Commit handling for singel BAPI-calls</b>
When you dont find the attribute .. try to reimport your BASIS 6.40 Software Componenent.
Regards,
Robin
User | Count |
---|---|
70 | |
26 | |
9 | |
9 | |
7 | |
6 | |
4 | |
4 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.