Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

Intermittent Issue when Background Posting

Former Member
0 Kudos
373

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

1 ACCEPTED SOLUTION

former_member186741
Active Contributor
0 Kudos
264

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.

7 REPLIES 7

Former Member
0 Kudos
264

Is there a long text for the message?

Rob

paul_bakker2
Active Contributor
0 Kudos
264

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

0 Kudos
264

Yes I know where the message was triggered but I can't identify why it's happening intermittently.

former_member186741
Active Contributor
0 Kudos
265

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.

0 Kudos
264

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.

0 Kudos
264

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.

0 Kudos
264

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.