SDRQCR21 program on SAP R/3 4.6C
-What exactly does this program do and why is it crashing after we installed patch 50 on our SAP R/3 4.6C?
-When we run this without populating any fields, it takes less than 300 sec, but as soon as we specify "*" materials and plant 10, the program runs forever without end; is this normal?
-OSS does not provide a lot of detail on this program and when we run it on a part number, it doesnt suggest it does anything.
Software/Hardware used:
Software/Hardware used:
ASKED:
December 19, 2005 10:31 AM
UPDATED:
December 20, 2005 5:17 PM
Answer Wiki:
The program reorganizes the stock requirements list. I really don't know how it works but do know that it cleans up items that appear in the stock requirements list that should not be there (e.g. planned orders that have been deleted, deliveries that have been processed but still appear, etc). I recall running this program as far back at release 2.2 so it's been around a long time. I've been at two customers that have set it up as a batch job to run weekly just to clean things up. I never got a good explanation as to why the stock requirments list got messed up in the first place but do know that this fixed the problem.
I have no idea why it runs long when you specify * for the material and a plant. What happens if you leave the material field blank and just run it for a plant, does it still take a long time? It seems to me that blank in the material field is the same as * so I don't understand why you would run it that way.
Hope this helps
To see all answers submitted to the Answer Wiki: View Answer History.
Based on the OSS notes, selecting plant and leaving material selection blank is the same effect as running the program with both fields blank; in other words, the job is complete in less than 300 sec.
Before patch 50 on our R3 4.6C, the program took about 1400 sec on average to complete based on selection of “*” for material and “10″ for plant. Our run freq was set to run after the daily MRP job nightly.
Any shared experience with this program is appreciated.
There are so many OSS notes are there. You can see Note No.820790 and fixed the problem of dump.
If you want to know why this is taking so long time it can be monotor by using sm50 transaction or putting the trace on in ST05 transaction.
How can one validate this report has actually done any updates? How long does this report normally take on your system (yes, I realize there are many variables at play here)? Does 300 seconds seem reasonable as our MRP on our one plant is run daily afterhours?
Have you looked at note 25444 in OSS? It has a pretty good explanation of the purpose of the program and a pretty lengthy section on performance.