2008 Jan 02 10:28 AM
Hello
We have a program of expansion of materials that performs a CALL TRANSACTION to MM01 and we want to enable the chance to do in test mode, the problem is that after you make the CALL TRANSACTION the system makes a commit and we can not do rollback
Anybody has any solution?
Hello
We have a program of expansion of materials that performs a CALL TRANSACTION to MM01 and we want to enable the chance to do in test mode, the problem is that after you make the CALL TRANSACTION the system makes a commit and we can not do rollback
Anybody has any solution?
2008 Jan 02 10:33 AM
Hi,
Try using ROLLBACK WORK. After CALL Transaction.
Thanks,
Sriram POnna.
2008 Jan 02 11:46 AM
Hello Alberto and Happy New Year.
Instead of calling MM01, you should better do the following:
Use BAPI BAPI_MATERIAL_SAVEDATA to change-extend the material in the plants/storage locations you need and if running in test mode, DO NOT call the BAPI_TRANSACTION_COMMIT. In that case, the BAPI_MATERIAL_SAVEDATA, will return any messages as if it was commiting the changes.
In case you do a batch-input in MM01, you cannot rollback the commit of the standard MM01 transaction.
I have done exaclty the same program but using BAPIs.
Note that you can first read all data needed using the BAPI_MATERIAL_GET_ALL and then extend the various material views accordingly.
Check also the BAPI_MATERIAL_SAVEDATA documentation for further help.
Reward if helpful.
Regards,
George
2008 Jan 03 9:25 AM
The problem is i can't use BAPI because some userexit are filled
If i use CALL TRANSACTION with UPDATE = A should i have time to do the rollback?
Thanks and happy new year
| User | Count |
|---|---|
| 4 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |