Block requirement transfer to MD04

[Former Member]

Hi

Is it possible to stop the transfer of requirement to MD04 for ceratin conditions.

Transfer of requirement is controlled by the Schedule line category field BEDSD ( Req. / Assembly)

If this field is marked the Requirement is tranferred immediately to MD04 and a PR is generated for the Sales ORder.

We have alredy proposed the option of stopping the TOR for the scehdule line category CP by using the field fixed date and quantity to the client, but it is not acceptable as MRP is re triggered when V_V2 is used.

Do we have any User exit / enhancement point around feild BEDSD, which can be modified for ceratin conditions, and we can stop the TOR?

Regards

Trupti

[Former Member]

Hi Trupti ,

Assign two Schedule line Category(SLC) to the Item Category where one is "relevant for requirement" and other is Not "Relevent for Requirement". Based on the condition you want, control the SLC using user-exit.

By the way, can you explain what is TOA (Table of Authority) ?

Regards

Vinu

[eduardo_hinojosa]

Hi Trupti

You can also do it (if you don't find how to do it with customizing tools or with your own VOFM in OVB5/OVB8 as Shiva suggests) with the BADI MD_CHANGE_MRP_DATA. Remember this BADI works for MD04 and for MD01 and MD02.

I hope this helps you

Regards

Eduardo

[Shiva_Ram]

Check t.codes OVB5 and OVB8, here you can add requirements with logics to fulfill the business requirements.

Regards,

[Lakshmipathi]

Just assign Reason for Rejection to the line items.

G. Lakshmipathi

[Former Member]

Hi Lakshmipathi,

If we use Reason for Rejection, definitely Requirement is not generated, but then document is also not caught in to the table of Authority ( TOA ), which is an issue.

Requirement is to just block the Transfer of requirement for particular time, may be based on some block at the header level of the sales order. Hence finding a way out.

Regards

Trupti