cancel
Showing results for 
Search instead for 
Did you mean: 

BAPI_ENTRYSHEET_CREATE

0 Kudos

Hi,

We are developing a proxy where data will come from external service and will create SES via BAPI_ENTRYSHEET_CREATE. There will be multiple SES data in one call and proxy has to validate all the data for create and acceptance.

The requirement is that if all the whole data looks good, SES should be created and accepted (for all the SES's came in Proxy) and then only the commit work should happen. If any one of the multiple SES data has issues, the transaction should not be committed and no SES should be created and accepted.. It is like All or none..

For this we call in loop, BAPI_ENTRYSHEET_CREATE and set the flag for acceptance in create itself. We also set NO_COMMIT flag to true so no auto commit happens inside the BAPI. And we commit after checking any error message coming out of the loop. The issues we are facing is follows..

When there are multiple SES Data (each one have diff PO nos), BAPI is able to create SES and accept SES ( 2 Messages in return) for first line item is created ( no commit) but inside the loop when second line items comes, it is throwing error " error in update". For the subsequent calls to BAPI, it is showing created and some I000 with text message with no errors.....

When the No commit flag is take off from BAPI (for same data) SES’s are getting created and accepted without error. However since the commit has already been done, if any error occurs in subsequent data, we lose the ability to un commit it.

Please advice how to handle this situation..!!

PS: We are not using ay release strategy for SES.

View Entire Topic
myra_zhao
Active Participant
0 Kudos

As mentioned in the KBA 2468660 , it cannot be avoided.

2468660 - BAPI_ENTRYSHEET_CREATE Number Range Issue

Best regards,

Myra