cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Requirement date of components in production order related to different operation

cw78
Explorer
0 Likes
776

Hi, 

I have the following requirement - components are assigned to operations in my routing. Lets say one component is assigned to operation 0200, because the consumption posting should be done via confirmation of operation 0200 and backflush setting. BUT the requirement date of the component should be the one of the operation 0100 just before? Is that possible in any way (also via badi or enhancement)? The offset time in BOM does not really help as it is a fixed value.

BR Christian

Accepted Solutions (0)

Answers (2)

Answers (2)

HakanHaslaman
Product and Topic Expert
Product and Topic Expert
0 Likes

Nice to hear you found a solution through an enhancement!

To answer your question, there isn't a standard SAP functionality that allows you to assign a different requirement date to a component than the operation it is assigned to. The requirement date is determined by the operation's scheduling and the component's lead time.

However, as you've discovered, BAdI or enhancement can used to manipulate this date. But be aware that any changes you make could potentially impact other areas of your production process, so it's important to thoroughly test any changes.

HakanHaslaman
Product and Topic Expert
Product and Topic Expert
0 Likes

The requirement date of a component is determined by the operation to which it is assigned. If a component is assigned to operation 0200, its requirement date will be based on the scheduling of operation 0200.

cw78
Explorer
0 Likes
Yes, clear for me, but my question was, how to give the components a different requirement date than the operation date they are assigned to. Anyhow, we already implemented an enhancement, when the order is save, where we can manipulate this date.
Kota_Miyakita1
Newcomer
0 Likes
Hi Hakan, thanks for your comment. current we face the issue that componnet requirement date is not calculated based on assigned operation 0200, but based on planned order start date(even included setup time). however in process order, it works fine. Issue only happen in planned order.