Dependent requirement still remained even I deleted the subcontract PO

Symptom:

Requirement remian unchange after subcontract PO was deleted ( 195650 / 2010 )

Refer to SAP note: Note 115899 - Correction report for subcontractor requirements

Symptom

In the customer system, inconsistencies occur for dependent requirements for subcontracting purchase order proposals (planned orders, purchase requisitions, purchase orders, schedule lines).
This can result from different program errors.
Required is a central report with which these inconsistencies can be discovered and corrected. (AFTER the cause of the error has been found and eliminated!)

You need an OSS account to access this note.If you have create a RFC connection to SAP OSS ,you may use transaction code SNOTE to download and implement it.

Another situation ,when the parent planned order was delete ,the dependent requirements still exist ,please refer to this note :

Note 633119 - Dependent requirements without parent planned order

Summary

Symptom
Dependent requirements (DepReqs) exist in the Stock/Requirements list (MD04) for which no parent planned order exists.
Simulative dependent requirements (DepReqs) exist in the Stock/Requirements list of long-term planning (MS04) for which no parent planned order exists.
Dependent requirements for subcontracting (SubReqs) still appear in the Stock/Requirements list (MD04) after the completion or deletion of the pegged requirements.

These erroneous requirements cause the creation of unnecessary receipt
elements during the planning run.

Other terms
orphaned dependent requirement, missing planned order, deleted planned
order, zombie report, 61003, 61 527, 61527, MD05, MS05, RESB

Reason and Prerequisites
Depending on the particular situation, the problem may be caused by
a handling error in the R/3 system, or possibly by an SAP program error.

Solution
Occurences of this problem generally fall into one of 3 categories:

1. Deleted planned order (for Standard or Simulative DepReqs)
              In this case, the parent planned order has been deleted but the dependent requirement still exists.  The planned order number is displayed in the MRP element data of the dependent requirement, but the planned order itself cannot be displayed or changed.  Attempting to do this generates the error message 61 003, 'Planned order ... does not exist'.

              Solution

              Try to determine the cause of the inconsistency.  How was the parent planned order created/changed/deleted?  Can the problem be reproduced? Then create an OSS message in the component PP-MRP containing all the relevant information.  On analysis of the issue, SAP Support can provide you with an ABAP report to safely remove the erroneous dependent requirements.

2. Reprocessing record from REM (Repetitive Manufacturing) backflush (for Standard DepReqs)
              In this case, no planned order number is displayed in the MRP element data of the dependent requirement.  Instead, the string 'NProc' is displayed.  This means that the dependent requirement is a reprocessing record for a goods movement that failed during an REM backflush.

              Solution

              These reprocessing records can be processed (removed) using transaction MF47 or COGI (see note 61144.)  If these transactions cannot locate the reprocessing records, they can be removed by following the instructions in note 95307.

3. Completed/deleted pegged requirements (for SubReqs)
              There is a possibility that a program error exists which has caused the inconsistency in this case.

              Solution

              If such requirements appear in your system for which no pegged requirements exist, you should consult note 128061. This is a collective note which lists any corrective notes currently existing in this regard.  You should apply any corrective notes that could be related to the problem and are valid for your current release and patch level.  Then create an OSS message in the component PP-MRP, outlining the problem in detail and listing any notes that have been applied.  At that point, SAP Support can provide you with an ABAP report to remove any outstanding erroneous requirements.



Good luck .