SO Deleted but appears in MD04

1) Please check any Open delivery is exist for the order, if yes delete the Delivery
2) Close the order by order rejection
3) run SDRQCR21 in SE38 with data transfer , planning file entry and processing per material tick
4) This will remove the planning file entry and demand and run MRP
5) If problem still exist , then raise a Question to SAP with the help of Basis
https://archive.sap.com/discussions/thread/1863626

Data transfer

This parameter will be selected in order to update Sales and Delivery Requirements in Database by applying the Correction.
Comparison
This parameter will be used to improve the performance and run-time execution and will not reconstructs the Database for all Materials/Plant in the selection.
Planning Entry
If this parameter is selected then the report creates entries for the planning run for the affected Materials/Plant in order to make sure that the material should be included in next MRP run.
Processing per Material

This parameter if selected saves the requirements for every Material/Plant one by one instead of saving all of them in a single step.
https://archive.sap.com/discussions/thread/3440249

MD04 - Inconsistencies after PGI - SDRQCR21
What is the use of SDRQCR21 (SAP note 1166713) standard SAP program?
I have got a issue with this program.  The issue (problem) stated is as follows:
Program SDRQCR21 was ran on material XYZ for plant ABC. It did not work. The item is still on MD04. Unable to use material as it is being held on the MD04 screen.
This program is used for to regenerate the sales/delivery requirements.
Example: sales order 1000 is created on some date.
Now may be you have put the reason for rejection to the sales order but the stock requirement list MD04 is still holding the qty against to the sales document.
Execute SDRQCR21 program by selecting data Transfer option.
MD04 will remove the Hold qty against to the sales order.
 
I have a sales order, sales order is fully delivered and MD04 doesn’t have this record displayed. You can see it has no sales orders by using the Find in List function (Cnt-F) in mdo4. The find MRP Elements tab shows you no sales orders exist for this material plant (sales order item ). So don’t understand why it shows up as an error. Why does the program think it needs to delete this sales order entry from md04, when it has nothing in MDO4 .
Run the program SDRQCR21 in SA38.
In the ensuing selection screen, Give the inputs of material number, plant and if possible document number, and execute.
You have to schedule this job before MRP run at plant level (creating variant from SE38).
After executing this, the completed delivery will disappear and MD04 will have real data only.
 
SDRQCR21 report doesn't update MD04 result.
We had quite a lot customer orders be re-scheduled everyday for some reason.  According to OSS note : 25444 & 998102 we have to run the report SDRQCR21 with option "data transfer" to correct stock /requirement list.  But nothing happen after run the report.
Go through the OSS Note: 547277
It may be useful.
From the OSS Note:25444
Below write-up may be useful:
Item Material Index
If you enter the 'Material' or 'Plant' selection criteria, the report returns correct results only if the document items affected are contained correctly in the relevant material index (VAPMA, VLPMA). This prerequisite is usually met. Only if you have good reason to suspect that the index is inconsistent, that the report has returned incorrect results because of inconsistencies, or that the report terminated with SAPSQL_ARRAY_INSERT_DUPREC because of inconsistencies, check the TVIND Customizing table and see Note 128947 and/or 33267 for information about correctly reconstructing the material index.

https://www.erpgreat.com/production/md04-inconsistencies-after-pgi-sdrqcr21.htm

to start of metadata

/SAPAPO/SDRQCR21- Correction report for delivery req. and sales req.

This report corrects incorrect sales order and delivery (requirements) in SAP R/3 / ECC and SAP APO/SCM.
  • Checks precisely the SD order tables
  • Doesn't check inactive integration models. Therefore, it is not a perfect substitute for /SAPAPO/CIF_DELTAREPORT3
  • SAP recommends to schedule the report /SAPAPO/SDRQCR21 on a weekly basis. Since the report /SAPAPO/SDRQCR21 can't be run during operation hours, its long runtime might be a bottleneck
  • Setting the flag read requirements from table VBBE can significantly improve the performance. It should be used only you have reliable VBBE table
To further improve the runtime of the report, you might use different variants:
  1. Execute the report without data transfer and without the selection criteria 'Material/Plant', but with 'Compare' and 'processing for material'. This can be done during production operating.
  2. Outside production operation, execute the report with 'data transfer' only for those materials for which step 1 logged requirement errors.
If backorder processing (BOP) is used, you should use this report to check the consistency of the SD job tables (/SAPAPO/POSMAPN, /SAPAPO/ARDADM_I, /SAPAPO/SCHEDLIN, /SAPAPO/SDQTVB...), since BOP relies on these tables being consistent.

https://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=233412430


Comments

Post a Comment

Popular posts from this blog

Common CIF Errors

Most common error messages that we face when analyzing CIF execution. For every error message we have a few recommended actions and possible root causes. 1. Order version __ __ not valid at date __ . Root causes:  PPM/PDS or production version is no longer valid at order date of execution.  No available PPM/PDS orPV at order’s date of execution.  PPM or PDS has not been ciffed correctly to APO. Solution: Check production version status is not locked. Update new validity dates for production version. Cif changes to APO in order to update the PPMs or PPDs. Re-explode the orders where necessary. 2. Product ____ doesn’t exist in an active integration model. Root causes:  Material intergation model is not active.  Product has cross-plant status as blocked.  Material has MRP type different than X_*. Solution:  Check and correct the cross-plant status of the product..  Check and correct the MRP type of the product (X_).  Activate the integration model and C
Read more

Automating CIF Delta Report Reprocessing

Image
CIF is the standard interface between APO and ECC used to transfer master data (uni-directional) and transaction data (bi-directional). But very often due to some master data issue transaction data does not flow through and gets stuck in CIF queue. SAP provides CIF Delta Reconciliation Report (commonly know as CCR) that compares transaction data for given product-location between APO & ECC to list the differences. This output result is typically reviewed by production support team and necessary processing action (one of Send to ECC, Send to APO, Delete in ECC and Delete in APO action button) executed to reconcile the transaction data differences. Any APO consultant doing CIF monitoring on regular basis knows the effort required and also over time turns monotonous. However the choice of action to be taken is limited (most of the cases only 1 of the 4 actions possible) based on the transaction data object type (like Purchase Requisition, Purchase / Stock Transfer Order, Planned Ord
Read more