atp修复程序 SDRQCR21

At some point in time sales and delivery requirements may get out of sync due to maintenance resulting in planning errors. Usually these errors are found when going through MD04. You will typically find deliveries (collective requirements) that cannot be traced back to original deliverydocuments.

The proper solution for this is to run report SDRQCR21 (via SE38):

Program SDRQCR21

• select the material and plant you wish to run the correction;
• select the option data transfer when you actually wish to run the correction on the database;
• select compare always in order to improve performance. Without selecting this the whole database for material/plant will be regenerated;
• select planning entry to ensure the material is included in the next MRP run;
• the option Processing per material results in a different log.

After this your MRP overview should be back in sync.

附：SAP NOTE 25444

Summary

Symptom

There are too many, too few or simply incorrect sales document (quotation, sales order, scheduling agreement) or delivery requirements. You can detect or check this using Transaction MD04 (Stock/Requirements List). These inconsistencies may trigger follow-on errors in planning, procurement (production, purchase order) or document processing (availability check).

Other terms

Sales document, sales requirements, outbound delivery, delivery, delivery requirement, reconstruction, reorganization, VBBE: Sales Requirements Individual Records; VBBS: Sales Requirement Totals Record, summation SUMBD, individual requirement, total requirement, daily requirement, weekly requirement, customer requirement, sales order requirement, ATP availability, batch input, collective processing, /SAPAPO/CIF_DELTAREPORT3: CIF - Comparision/Reconciliation of Transaction Data, VBUK: RFGSK, LFGSK, WBSTK, ABSTK; VBUP: RFGSA, LFGSA, WBSTA, ABSTA

Reason and Prerequisites

The problem may be caused by a program error or an operatin