on 01-26-2009 11:16 AM
Hi Experts
I want Execute the commite transaction after Trigeering the Standred BAPI through XI.
We haveAdvance Mode option in Reciver RFC Adapter . Any one explain me how to implment this.
Regards
Upendra.V
Edited by: upendra v on Jan 26, 2009 1:47 PM
Hi,
If you want to use this communication channel to call BAPIs as remote-enabled function modules that change data in the database, set the indicator.
If executed successfully, the transaction is written to the database by calling the function module BAPI_TRANSACTION_COMMIT explicitly. If an error occurs, the transaction is rolled back by BAPI_TRANSACTION_ROLLBACK.
The result is determined by the value of the field TYPE in parameter RETURN. If successful, the tables are empty and the values u201Cu201D, u201CSu201D, u201CIu201D, and u201CWu201D are displayed. All other values are regarded as errors.
To change this setting, set the indicator BAPI Advanced Mode.
In the Successful RETURN-TYPE Values table, enter the values that should lead to a successful execution.
Above is the explaination from help.sap.com.
http://help.sap.com/saphelp_nw04/helpdata/en/c8/e80440a832e369e10000000a155106/content.htm
Regards,
Sarvesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hmmmm.. I guess you are just practising & exploring all the featers of RFC.. isn't it?
Anyway upto what I know is here..
>If you want to use this communication channel to call BAPIs as remote-enabled function modules that change data in the database, set the indicator.
First of all you need to write an ABAP program in R3, there you will call your RFC/BAPI to update the database entries.
In XI, under your receiver RFC adapter check the box "Commit Handiling for Single BAPI Calls". Once you click you will get another check box called "BAPI Advanced Mode".
>If executed successfully, the transaction is written to the database by calling the function module BAPI_TRANSACTION_COMMIT explicitly. If an error occurs, the transaction is rolled back by BAPI_TRANSACTION_ROLLBACK.
Once you send the data from XI to R3, then in R3 function module BAPI_TRANSACTION_COMMIT will be called explicitly (you need to define/call this BAPI after the ABAP code for database update). This will commit the work and return the result success or failur in a parameter called RETURN.
And after this BAPI you should call BAPI_TRANSACTION_ROLLBACK, so that in case of errors the transaction will be rolled back.
>The result is determined by the value of the field TYPE in parameter RETURN. If successful, the tables are empty and the values u201Cu201D, u201CSu201D, u201CIu201D, and u201CWu201D are displayed. All other values are regarded as errors.
As described above.
>To change this setting, set the indicator BAPI Advanced Mode.
In the Successful RETURN-TYPE Values table, enter the values that should lead to a successful execution.
Once you check the box "BAPI Advanced Mode" a table will appear, there you can write your own values e.g.u201Cu201D, u201CSu201D, u201CIu201D, and u201CWu201D.
I can not provide a better solution then this... you have to do a work around, but above are the basic steps which can be considered before implementing the solution.
Regards,
Sarvesh
User | Count |
---|---|
80 | |
9 | |
9 | |
7 | |
7 | |
6 | |
6 | |
6 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.