Hi Andreas,
Thanks for your reply.
Agree with your comments only at the next statement commit work in SAP process code the BAPI_BILLINGDOC_CREATEMULTIPLE related SAP tables get updated and the BAPI returns either sucess or error messages, but at this point of time my Zprogram execution already completed and in my custom program the BAPI error/success message handling is not working due to that.
How can we do these kind of scenarios.
when I do the same in online (added BAPI_TRANSACTIONAL_COMMIT) it is perfectly working and my error/success messages handling executing based on the BAPI returns.
So the main problem, what I could see here is the custom program is in background so I am not able to use the Commitwork or BAPI Transactional commit after the BAPI, due to that the BAPI_BILLINGDOC_CREATEMULTIPLE related tables are not getting updated and not returning the error/success messages while executing the custom program ....it all happens after the custom program and inside the sap code at the commit work..
My observation...if I could find where is the SAP commit work statement in sap standard, after this code if I get my BAPI return success/error messsages using SAP Memory, will this help me any chance....
Any thoughts how to proceed on this.
Thanks a lot for your contribution on this.
Best Regards - Naresh Kumar.