on 04-24-2007 2:24 AM
Hi,
scenario: http-XI-RFC(<b>asynch</b>).
Receiver RFC adapter is configured and checked "<b>commit handling for single BAPI calls</b>" and "send confirm transaction".
BAPI creates the data in R/3 side. <b>Commit works fine if I have only one record and call BAPI once</b>.
Now, I have changed cardinality for source/target in <b>message mapping & interface mapping</b> <b>from 1 to "0 to unbounded"</b>.
I have invoked the scenario with 2 test records in input. I could see the message in MONI as success. But, the records are not created in R/3 table.
Is it right approach ? What happens if one transaction fails, would XI rollback all transactions ?
Does commit work with multiple BAPI calls in single RFC call ? Please suggest.
Do I need to use BPM or ABAP proxy ?
we are on PI 7.0 SPS 9.
Message was edited by:
mallik kancharla
hi mallik,
I think, here u have to call the function module BAPI_TRANSACTION_COMMIT to commit.
Can u try this?
regards
sreeni
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
I guess you will have to use BPM in your case.
If one transaction fails, then the rest would be executed, it will show in monitoring
Regards,
Samson Rodrigues.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.