PIR deletion

[Former Member]

What is the diff between transaction codes MD74,MD75 & MD76.

Which one should be used for deletion of PIR and what is the use of field " Key Date" in all these transaction code.

Thanks

rkumar

[Former Member · Accepted solution]

Dear Ravi,

MD74 is to remove PIR's from MD62 screen but still remains in data base

MD75 will totally remove PIR's form data base

Key date - from date given ( key date ) system removes old PIR's ( i.e if we give today date then system

will remove all PIR's upto today's date

Added

Check this link

[;

Regards

Madhu

Edited by: K.Madhu Kumar on Sep 23, 2010 12:21 PM

[Former Member · Accepted solution]

What is the use of MD76 and when one should use MD74 0r MD75.

thanks

rkumar

[Former Member · Accepted solution]

Dear Ravi,

when you run MD74 planned qty ( PIR qty will set to Zero )

Where as if you run MD75 then withdrawal qty in schedule line which will be shown in MD62 will

also get removed

Coming to MD76 Never i worked on that

Regards

Madhu

[Former Member · Accepted solution]

Transactions MD74, MD75 and MD76 are PIR reorganization transactions. It is advisible to use these transactions in step by step, here you follow:

Step 1. Transaction MD74 - Adjusting Requirements

This transaction can be used to adjust PIR. When adjusting requirements, the system checks whether customer requirements exist for active PIRs that lie before the key date and the quantity of customer requirements that are assigned. The planned independent requirement quantities that are not assigned are set to zero and are flagged for reorganization.

In this step, you can also setup background execution job using program RM60RR20 with appropriate variant, so that it deletes all inactive planned indepenent requirements. It is recommended that to adjust out-of-date PIR Once in a month.

Step 2. Transaction MD75 - Reorganization

This transaction can be used to delete old PIR, the system checks which planned independent requirements were set to zero - either by reduction or consumption or by "requirements adjustment". Requirements records that lie before the key date and that have the quantity zero are deleted from the database.

In this step, you can also setup background execution job using program RM60RR30 with appropriate variant, so that it deletes all old PIR. It is recommended that you reorganize out-of-date PIR once in a month.

Step 3. Transacion MD76 - Deleting Histories

This transaction can be used to delete history of PIR, Once the system has completed the reorganization process, the histories can also be deleted for the same period. The key date for deleting histories can differ from the key date of reorganization.

In this step, you can also setup background execution job using program RM60RR40 with appropriate variant, so that it deletes history of PIRs. It is recommended that you delete PIR history once in a month.

Note : Key date - In case if you defined "Default values for re-organization interval" for plant in customization transaction OMP8, 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.

In case no key date specified in customization, manual input can be considered as key date, usually 30days minus current date will be the key date.

Regards,

Balaji NG