2016 Apr 05 9:16 AM
Hi Experts,
We are currently experiencing an intermittent error when posting in background using BAPI_ACC_DOCUMENT_POST. This is not replicable in the development box, only in the QA system. The error is '(RW 002) No item information transferred into Accounting'.
Can you provide some causes for this kind scenario?
Thanks,
Trixa
2016 Apr 06 12:10 AM
The message seems to be saying that something necessary for the bapi to process is not present. Not all the required input to the bapi has been passed in. Was there a short dump in ST22. If so you should be able to dig around and see the data passed into the BAPI and then you should be able to work out a method to intercept this type of scenario and stop the bapi being called with incomplete input data.
2016 Apr 05 4:51 PM
2016 Apr 05 11:03 PM
Hi,
Did you try debugging? Did you do a where-used on the error message in SE91?
Did you search for that message code in the SAP Support Portal?
cheers
Paul
2016 Apr 06 6:47 AM
Yes I know where the message was triggered but I can't identify why it's happening intermittently.
2016 Apr 06 12:10 AM
The message seems to be saying that something necessary for the bapi to process is not present. Not all the required input to the bapi has been passed in. Was there a short dump in ST22. If so you should be able to dig around and see the data passed into the BAPI and then you should be able to work out a method to intercept this type of scenario and stop the bapi being called with incomplete input data.
2016 Apr 06 6:51 AM
I'm confused because we don't have any issues in the development system. We only encountered the error in the QA system. Usually, we can post again after we refresh the custom transaction multiple times.
2016 Apr 06 7:21 AM
yes but there is often a wider variety of data in QA and more scenarios get tested. If you can't work in QA I would suggest trying to simulate the issue by running in debug in DEV and gradually removing different items of the data sent into the bapi to see if you can get the same message appearing. If you succeed you can then wrap code around the bapi and don't call it if the offending data is missing.
2016 Apr 12 10:04 AM
After a lot of fixing and testing, we found out the root cause was the export/import statement used in passing data (variable and internal tables) from foreground to the SUBMIT program.
Previously, I used the following:
EXPORT f1 = f1
itab = itab
TO SHARED BUFFER indx(st) ID 'ZTEST'.
IMPORT f1 = f1
itab = itab
FROM SHARED BUFFER indx(st) ID 'ZTEST'.
And changed to:
EXPORT f1 FROM f1
itab FROM itab
TO DATABASE indx(st) CLIENT sy-mandt ID 'ZTEST'.
IMPORT f1 TO f1
itab TO itab
FROM DATABASE indx(st) CLIENT sy-mandt ID 'ZTEST'.
Thanks everyone.