This WIKI provides an overview of the most common inconsistencies and display issues that may occur on transaction MD04.
MD04 is a key transaction for production planning and control, which displays the up-to date stock and requirements situation. Every time transaction MD04 is accessed, planning elements and documents from different areas are read from database, compiled and displayed to the user.
In some cases, these elements may be incorrectly displayed on MD04, and this is generally caused by database inconsistencies. Since planning elements are read directly from database and they may belong to different areas, there are several possible causes and corrections for such inconsistencies. The most common problems are listed on this WIKI.
Table of Contents
- Deleted or already completed sales order/delivery
- Sales order/delivery number is not displayed
- Inconsistent subcontracting dependent requirement
- Inconsistent “Nproc” dependent requirement
- Dependent requirement without parent planned order
- Field Available Quantity is blank
Deleted or already completed sales order/delivery
A deleted, already completed or simply inconsistent sales order, delivery, quotation or SD schedule agreement can be found on transaction MD04.
This is an inconsistency that can be corrected by the report SDRQCR21, which should be already available on your system. For more details about the report execution and the parameters, please refer to SAP Note 25444 .
In some cases, on a make-to-order scenario, the sales order is already completed, but the sales order stock is still displayed on MD04 because there is still a quantity linked to the sales order special stock. SAP Note 1723507 provides instructions to remove the stock and the sales order will not be displayed on MD04 anymore.
If you need further assistance to find the root cause of this issue, you may refer to question 1 of the SAP FAQ Note 547277 .
Sales order/delivery number is not displayed
A sales order, delivery, quotation or SD schedule agreement is displayed on transaction MD04 without any reference to the document number. Error message “61111 - Selected function cannot be used for the element” is displayed when you try to open the element.
This is not an inconsistency. It happens when “daily requirement” or “weekly requirement” is selected for the availability check in the material master. More information about this system is provided on SAP Notes 70408 and 1649669.
Inconsistent subcontracting dependent requirement
A subcontracting dependent requirement (planning element SubReq) for a purchase order or schedule agreement which was already processed or deleted is still displayed on transaction MD04.
This is an inconsistency that can be corrected by the report RM06C020, which should be already available on your system. You can find more details about this report and the source code (in case it is missing on your system) on SAP Note 115899 .
A known program error that can cause this inconsistency is corrected by SAP Note 1578969.
1578969 Active subcontracting requirement of deleted PReq
Inconsistent “Nproc” dependent requirement
“Nproc” dependent requirements are reprocessing records for goods movements that failed during a REM backflush. These records should be processed using transaction COGI or MF47, however, in some cases, they are inconsistent and they can’t be processed.
If the report can be found on MF47 or COGI, but they can’t be processed, it is an inconsistency that can be corrected by the report ZINCON_REPROC. This report is attached to SAP Note 383141 , which brings more information.
Otherwise, if this record can’t be found on COGI or MF47, it is a 'lost' reprocessing record, for which the planned order does not exist anymore. You should implement and run the report ZRMBF06, which is attached to SAP note 95307 or following the procedure from SAP note 901146 .
Dependent requirement without parent planned order
A dependent requirement is displayed on transaction MD04 for which the planned order has already been deleted. The planned order number is displayed in the MRP element data of the dependent requirement, however, this planned order can’t be accessed on transaction MD12 and it does not exist on table PLAF. When you try to access the planned order the error message “61 003 - Planned order XXX does not exist”.
Report Z_CHECKRESB can be used to clear this inconsistency. You should open an OSS message so that SAP Support can analyze the issue and provide you the report.
Field Available Quantity is blank
The field "available quantity" from transaction MD04 is empty for an specific planning element. There are several possible causes and you can find an overview on knowledge base article 1825187.
SAP Note 25444 : SDRQCR21: Recovery of sales and delivery
SAP Note 547277 : FAQ: Requirements in SD and in the delivery
SAP Note 70408 : No display of sales order number in MD04
SAP Note 115899 : Correction report for subcontractor requirements
SAP Note 383141 : RM887, RM757: Collect. note inconsistent postprocessing recs
SAP Note 95307 : Deletion report for 'lost' reprocessing records
SAP Note 901146 : NPROC dependent requirements can not be processed
SAP Note 1825187 : Available quantity incorrect on MD04/MD05
SAP Note 1578969 : Active subcontracting requirement of deleted PReq
SAP Note 1649669 - Sales order number or delivery number is not displayed in transaction MD04.
SAP Note 1723507 - Completed sales order displayed on MD04