Reg.MIGO

[former_member305655]

Hi All,

I have a specific requirement wherein while doing GR against Purchase order the delivery note field should become mandatory and it should be based on some conditions like for eg. plant, movement type etc. for this I am planning to maintain these entries in Z table and if the condition is met like If GR against P.O is done for that plant then the field delivery note should become mandatory, if not satisfied it should not be an mandatory.

In order to achieve this I think I can make use of the BADI-MB_MIGO_BADI and this badi will get triggered only the condition maintained in the z table is met.

But my question here is since the MIGO transaction has many functionalities and many movement types like 101, 102 etc.,

I need to know which parameters I can maintain in z table other than mentioned above to make this delivery note field mandatory to be used as optimum for my requirement. I need this field to mandatory only for movement types 101, 102 and for few plants and not for all plants.

Also there could be the case that same plant will have scenario of delivery note mandate and non mandate case. In such scenario what parameters in Z table could exactly trigger the BADI. I hope plant and movement type will not be sufficient.

Kindly throw some light.

Regards,

MBN.

[mohsinabbasi007]

Dear M,

Don't get confused, go ahead, just focus on your requirement and keep in mind the movements type and plant only while making logic with the help of Abaper in Z Table. And sure you have Quality system as well to cross check once before transporting it to in PRD.

Best Regards

Mohsin Abbasi

[Prasoon]

Hi,

   As per initial comments, the movement type and plant will be sufficient in the Z table for validation. But if there is any case where same plant requires delivery not as mandatory in one scenario and not mandatory in another scenario for the same movement type, then you need identify the special scenario and include this criteria also in the Z table. This additional criteria could be item category, PO doc type etc, based on the scenario and your requirement.

Regards,

AKPT

[BijayKumarBarik]

Hi,

You have any issue, if you follow below step.

Use t.code: OMJN , Select Required for Delivery Note (RM07M-LFSNR) and save.

Now try creating MIGO with movement type 101

Regards,

Biju K

[sb_er]

hi

Last 3 lines cant understand. Be clear.

Regards

karan

[former_member233510]

I understand the intention behind making the field delivery note mandatory is to enter the Vendor invoice number if so then the movement types you've to consider are 101, 103 and 107. The reversal movements are no need to consider since the delivery note automatically copies from the reference document. The important parameters you've to consider to build the Z table are Transaction/event (Eg: Goods receipt), reference document (Eg: Purchase order) and Movement type.