vmd_ei_api=>maintain
When the company view is expanded when called continuously.
If the company code already exists, there is no problem.
If the company code does not exist, BUPA_TAX_SAVE_TABS will be called to update the tax number (first insert the tax number of CN1 and then delete the tax number of CN0). When calling continuously, the inserted internal table IT_TAX_INSERT will not be cleared, which will result in the first update of partner 1 , Partner 1 and 2 will be updated for the second time. Since partner 1’s tax number has been updated, the second commit will trigger BUPA_TAX_SAVE_TABS and dump due to the insertion of duplicate data.
Solution: use
call function 'BAPI_TRANSACTION_COMMIT'
exporting
wait = 'X'.
Cannot commit work. However, the problem that CN0 becomes CN1 still cannot be solved. If you continue to expand, it will still be CN1 (if you already have CN1, there will be no problem). Use LSMW to change it again.
2. Check the returned supplier, be sure to write the customer, otherwise the front desk will dump
Update BP
