Linkage between the reservation and the requisition is lost in case of MRP

[Former Member]

Input data:

2 reservation documents are created from PS:

reserv. 1212, Mat. 11111, quant. 50, date 01.08.08

reserv. 2121, Mat. 11111, quant. 100, date 01.08.08

after performing MRP and processing reservation 1 document is generated at MRP output -

purchase requisition Mat. 11111, quant. 150, date 01.08.08.

Task: how to disable uniting similar requirements during MRP run, i.e.

according to the above mentioned example there should be 2 requisitions at the output:

purchase requisition 333, Mat. 11111, quant. 50, date 01.08.08

purchase requisition 334, Mat. 11111, quant. 100, date 01.08.08

Task 2:

How can the analyst add to the newly generated requisition the number of reservation based on which this requisition has been generated or how to set (how not to lose) linkage between reservation and requisition:

E.g.: purchase requisition 333, Mat. 11111, quant. 50, date 01.08.08, reservation 1212.

Probably it may be done with BADI MD_PURREQ_CHANGE, but it is not clear how to define the implementation point.

Thank you.

Regards, Victor.

[Former Member]

Hi Victor

The 1st part of your question:

The requirement of reservation is on same date ,hence sigle PR is generated.you have not mentioned what is lot size key being used.

Probably you can try with Lot size key "EX" ( I am not sure).

The second question:

you can analyse like this:

Got MD04 & see the pegged requirements . This way you can know what is the origin of requirement for a particular PR.

Regards

YMREDDY