07-17-2020 5:12 AM - edited 02-03-2024 6:58 PM
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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:
Best Regards,
R.Brahmankar
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
92 | |
11 | |
11 | |
6 | |
6 | |
4 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.