Scribd Logo
Upload

Welcome to Scribd!

  • Delete Planned Independent Requirements using MD74, MD75 & MD76

    Uploaded by

    pooja
    715 views2 pages
    This document discusses a 3-step process for reorganizing planned independent requirements (PIRs) in SAP: 1. MD74 is used to delete PIRs before a specified key date and remove associated planning proposals. 2. MD75 deletes schedule lines where the quantity is zero before the key date due to consumption or reduction. 3. MD76 deletes the history of PIRs that were deleted in the previous steps once reorganization is complete. The key date for deleting histories can differ from the reorganization key date.

    Original Description:

    Reorganization of Planned Independent Requirements

    Original Title

    Reorganization of Planned IndependentRequirements

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    This document discusses a 3-step process for reorganizing planned independent requirements (PIRs) in SAP: 1. MD74 is used to delete PIRs before a specified key date and remove associated planning proposals. 2. MD75 deletes schedule lines where the quantity is zero before the key date due to consumption or reduction. 3. MD76 deletes the history of PIRs that were deleted in the previous steps once reorganization is complete. The key date for deleting histories can differ from the reorganization key date.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    715 views2 pages

    Delete Planned Independent Requirements using MD74, MD75 & MD76

    Uploaded by

    pooja
    This document discusses a 3-step process for reorganizing planned independent requirements (PIRs) in SAP: 1. MD74 is used to delete PIRs before a specified key date and remove associated planning proposals. 2. MD75 deletes schedule lines where the quantity is zero before the key date due to consumption or reduction. 3. MD76 deletes the history of PIRs that were deleted in the previous steps once reorganization is complete. The key date for deleting histories can differ from the reorganization key date.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    of 2

    Reorganization of Planned IndependentRequirements-MD74, MD75 & MD76

    Md74 - deletes PIR's before key date.


    MD75 - deletes records from the Total requirements screen
    Md76 - Deletes the history that this PIR ever existed/ created.
    SAP has this 3 step process to enable each customer to determine upto what level they need to delete PIR in their
    system.
    One cusomer may prefer to just delete unwanted PIR which are unconsumed before key date.
    Another customer may prefer to delete PIR & also it's history from the system.
    Actually you cannot execute MD75 until you execute MD74. On the same tone cannot run MD76 until you run
    MD75.

    With the reorganization function, you can delete planned independent requirements for which there are no sales
    orders in the database :The aim of Reorganizing is to delete the old PIRs from system.

    This reorganization is carried out in 3 steps:

    1. Adjust requirements (Transaction-MD74):

    MD74 tcode used to reorganise the PIR. You can delete the PIR for a particular material, for a particular version
    within particular period.
    By using MD74 you can remove unconsumed PIRs of a perticuller period or Version. System will also remove all the
    reference Planing Proposals which are generated to that PIRs during the next MRP run.

    The planned independent requirement quantities that have not been assigned before the specified reorganization
    key date ( This date can also be in future) are set to zero and are flagged for reorganization.In this step, you can
    also set the system so that it deletes all inactive planned independent requirements.

    2. Reorganization of schedule lines (Transaction MD75):

    The system checks which planned independent requirements were set to zero – either by reduction or consumption
    or by “requirement adjustment”.Schedule lines that have a quantity of zero before key date are deleted from
    database

    3. Deleting history (Transaction MD76):

    Once the reorganization process is completed, the history can also be deleted by determining a key date. The key
    date for deleting histories can differ from the key date of reorganization.

    Reorganization period:

    As an alternative to Key date we can maintain a reorganization period per plant in the customizing of Demand
    management which is calculated backwards from the current date. The system first checks whether a reorganization
    period is maintained for the plant to be reorganized. If this is the case, the system
    subtracts the interval from the current date to determine the key date.

    If no interval is maintained for the plant to be reorganized, the system checks whether intervals are maintained for
    other plants. The highest value is then used to determine the key date.

    It is recommended that reorganization should be carried out periodically for example once per month.

    CDHDR- Change document Header


    CDPOS- Change socument Item

    Reference:http://help.sap.com/erp2005_ehp_07/helpdata/en/cb/7f977b43b711d189410000e829fbbd/content.htm?fr
    ameset=/en/cb/7f9b7043b711d189410000e829fbbd/frameset.htm

    MD74.
    Let's say you have a demand of 100. This you will check in md62 or md63 and for that you have planned orders
    also. You want to delete the demand for a particular material and set the planned order to 0. When you run this
    transaction you set the demand to 0, and when you refresh md04 the planned orders will have exception message
    "26" Excess in individual segment. When you run the MRP these planned orders will be deleted. It is completely
    deleted form the data base.
    MD75
    Again let's say you have demand of 100 for a particular material and there is some withdrawal also. If you go the
    schedule line tab in t.code md62 or md63 you can see the withdrawal quantity. If you want to delete this withdrawal
    quantity from the data base you execute this transaction.
    So, Transaction MD75 is to delete the withdrawal quantity from schedule line. you provide the same material details
    as provided in the previous transaction ( including "ReqPlanNo" and Key date). We can check the result by running
    in the test mode
    and then run it again with the flag test mode unset. This will delete the withdrawal quantity in the schedule line.
    I hope it is clear now.

    You might also like