We are working on SCM 5.1 and using BAPI_PIRSRVAPS_SAVEMULTI to create planned independent requirements.
Unfortunately we are having problems with the COMMIT execution (only 155 of the 500 requirements are saved) even if we have tried in many different ways to solve the problem:
- 100 requirements per time are processed (now even turned down to 50)
- - BAPI_TRANSACTION_COMMIT added after à ‘commit control’ parameter in the PIR SAVEMULTI set to ‘E’ or ‘3’.
Has someone other ideas?
your request underlined the weak point of my program.
The BAPI was called with a background job and the return messages were not saved anywere.
Now we have added this part, but yet no error messages are saved in our new Z-table.
Anyway looking better at the BAPI input parameters, I discovered that the forecast not saved is the one which falls in the days with a closed calendar.
I have been lucky I have noticed it, but how is it possible that the execution of the BAPI does not return an error message for this?