2015 Sep 24 11:24 PM
I am using an API VMD_EI_API to maintain a Vendor. I am calling a method MAINTAIN_BAPI to create/change the vendor and it works fine.
Now the question is I have to execute this method twice where in the Vendor created in first call to be used in the second call.
I need a Vendor number created(COMMITTED) in first call to be used in second call to be used as a Remittance partner in Partner functions.
So if for some reason second call to this method fails I need to rollback the changes performed in the first call which was already committed.
Is there a way we can do this?
I am using an API VMD_EI_API to maintain a Vendor. I am calling a method MAINTAIN_BAPI to create/change the vendor and it works fine.
Now the question is I have to execute this method twice where in the Vendor created in first call to be used in the second call.
I need a Vendor number created(COMMITTED) in first call to be used in second call to be used as a Remittance partner in Partner functions.
So if for some reason second call to this method fails I need to rollback the changes performed in the first call which was already committed.
Is there a way we can do this?
2015 Sep 25 4:22 AM
Dear Venkat,
Please you can try the same by yourself.
Create the Vendor using BAPI and pass COMMIT= 'space' if exist.
after generating the vendor call the rollback and check standard Table.
If entry is generated means system already write the Commit work in the BAPI.
If entry is not there, you can try the same thing with the second bapi.
Thanks
Nishant
| User | Count |
|---|---|
| 3 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |