cancel
Showing results for 
Search instead for 
Did you mean: 

Accepted Solutions (1)

Accepted Solutions (1)

former_member42743
Active Contributor
0 Kudos

In QA07 you need to specify the "initial run in days" as 1.

It won't execute that portion of the program without a value.

FYI - The blocking piece of expired batches is always done before the re-inspection, therefore expired batches never get re-inspected.

If you want to re-inspect at expiration date you can't. Not unless you have a process to keep your next inspection date in-sync with your expiration date. And then you would need to use an initial run in days for re-inspection as 2 and for expired batches as 1.

Craig

Answers (2)

Answers (2)

Caetano
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hello

If you know a little bit of ABAP, then it is easier to check it debug.

The program behind QA07 is RQAAAS10 and almost the whole logic to select the batches is directly in this program. There is a form called chargen in the program where the batches will be selected and checked where you will probably find the root cause of the problem.

Regards,
Caetano

rupesh_brahmankar3
Active Contributor
0 Kudos

Hello,

For "No batches have been found for processing" (QV509) when using t-code QA07 to do stock inspection

Please refer SAP KBA on it,

2533694 - "No batches have been found for processing" in QA07

The batch master data corresponds to the selection conditions.
Only those batches that fulfill the following conditions are examined:

  • The batch status is "released".
  • The unrestricted-use stock is greater than zero.
  • The stock is not in an HU storage location.
  • The stock is not special stock.

Best Regards,

R.Brahmankar