Attempting to do this generates the error message 61 003, 'Planned order. 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. In this case, the parent planned order has been deleted but the dependent requirement still exists. Deleted planned order (for Standard or Simulative DepReqs) Occurences of this problem generally fall into one of 3 categories:ġ. Order, zombie report, 61003, 61 527, 61527, MD05, MS05, RESBĭepending on the particular situation, the problem may be caused byĪ handling error in the R/3 system, or possibly by an SAP program error. Orphaned dependent requirement, missing planned order, deleted planned These erroneous requirements cause the creation of unnecessary receipt Simulative dependent requirements (DepReqs) exist in the Stock/Requirements list of long-term planning (MS04) for which no parent planned order exists.ĭependent requirements for subcontracting (SubReqs) still appear in the Stock/Requirements list (MD04) after the completion or deletion of the pegged requirements. Note 633119 - Dependent requirements without parent planned orderĭependent requirements (DepReqs) exist in the Stock/Requirements list (MD04) for which no parent planned order exists. 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.Īnother situation ,when the parent planned order was delete ,the dependent requirements still exist ,please refer to this note :
0 kommentar(er)
