Firmed Planned Order

[former_member209175]

Hi Team,

I would like to understand the difference between "Planned Order" & "Firmed Planned Order" in layman's language. I understand that the difference between these two is, during MRP run, the planned orders which has firming indicator will NOT be changed. In which business scenario this firming indicator will be helpful? Can anyone explain with some business example?

Qus2: When i create the planned order in MD11 with profile "LA- Stock order", the firming indicator & the conversion indicator is set automatically AFTER entering the order finish date. How the firming indicator & conversion indicator is set automatically after entering the order finish date?

Qus3: For example, i have created two planned orders, one planned order of "LA- stock order" type & another planned order of "KD-Individual customer order"

type. In OVZ9, for the availability checking group 02 (Individual) & Checking Rule A(Sale Order), if i maintain "X- Check All Planned Orders" in the field of "Incl. Planned Orders", will above created two (type LA & KD) planned order considered or ONLY the planned order with type KD will be considered?

Qus4: In OVZ9, in the field "Incl. Planned Orders", we have the option "B- Only check planned orders that are completely confirmed". Is this mean that consider ONLY the planned orders for which ALL the BOM components are FULLY COMMITTED after ATP check?

Thanks

[Former Member]

Hi,

Ans: Production plan should not get change automatically unless any manual intervention for certain period of time due to capacity bottleneck or commitment. In this case, firming indicator will be helpful.

Ans2: System sets firming indicator automatically because the planned order has been created manually. Means, we are over writing the plan by creating new planned orders. So, system sets firming indicator in planned order to avoid any change when run MRP.

Ans3 &4: Your understanding is right as per my view.

Regards,

Dharma

[former_member209175]

Hi Dharma,

The system automatically sets the firming indicator while creating the planned order in MD11. If i remove this indicator manually, how this planned order will be treated during MRP run? Please guide me with some example.

Thanks

[Former Member]

Hi,

System will check the requirement (PIR, sale order) on that particular unfirmed planned order date and try to satisfy those requirement with this planned order.  Planned order will get delete if no requirement exits on that particular date when run MRP.

System will not propose any rescheduling exception message since this unfirmed planned order can be changed or deleted by system when MRP runs.

Regards,

Dharma

[former_member209175]

Hi Dharma,

Case 1: The firming indicator is NOT set in Planned Order

Your statement is:

"System will check the requirement (PIR, sale order) on that particular unfirmed planned order date and try to satisfy those requirement with this planned order.  Planned order will get delete if no requirement exits on that particular date when run MRP".

Qus1: Planned order will get deleted, if no requirements exists on that particular date when MRP runs (assume requirement element in our will be ALWAYS sale order). So in this case, Do you mean that the "Requested Delivery Date (VBAK-VDATU)" of the sale order & the planned order finish date (PLAF-PEDTR) are NOT same, after MRP run, the planned order will be deleted if the firming indicator is NOT set. Am i right?

Case 2: The firming indicator is set in Planned Order:

Do you mean that the "Requested Delivery Date (VBAK-VDATU)" of the sale order & the planned order finish date (PLAF-PEDTR) are NOT same, after MRP run, the planned order will NOT be deleted if the firming indicator is set. Am i right?

Thanks

[Former Member]

Hi,

 Do you mean that the "Requested Delivery Date (VBAK-VDATU)" of the sale order & the planned order finish date (PLAF-PEDTR) are NOT same, after MRP run, the planned order will be deleted if the firming indicator is NOT set. Am i right?

Ans: Yes, system checks planned order finish date with sale order delivery date in case of backward scheduling. If it is forward scheduling, system checks the sale order date with planned order start date.

Do you mean that the "Requested Delivery Date (VBAK-VDATU)" of the sale order & the planned order finish date (PLAF-PEDTR) are NOT same, after MRP run, the planned order will NOT be deleted if the firming indicator is set. Am i right?

Ans: Yes, since it is a firmed planned order, system can not delete or modify. But system shows exception message to reschedule.

Regards,

Dharma

[former_member209175]

Hi Dharma,

I have tested the scenario in the system. Please find the test results below & request for your clarification.

Case 1:

Case 2:

I have created the PIR with the date 25.11.2013 for the qty 20. And executed the MRP (MD03-Single item, single level). The NEW planned order is created by the system with the order finish date as 25.11.2013. But the "Firming Indicator" is NOT set. Is the "Firming Indicator" not set, if the planned order is created through MRP?

Please guide me

Thanks

[former_member208398]

Hi SK,

For Q1: please check the tolerance value maintained in the Rescheduling setting (in OPPQ) and also whether Firmed planned order is subjected to rescheduling or not.

For Q2: MRP generates planned receipts to cater the net requirements so that they can be adjusted in subsequent MRP runs if the requirement situation is changed. That is the reason MRP generated planned order does not have the firmed indicator. If you change any planned receipt manually (planned order/ PR's etc) or create the planned receipts manually, the firming indicator is updated and MRP does not automatically change them.

Best Regards,

Rajen

[former_member208398]

Also, if you are using MRP group, you can check the tolerance values (forward and backward) in OMD1.

BR,

Rajen

[Former Member]

Hi,

Case1: Exception message should appear. Tolerence value can be set for exception messages to appear or not based on planned orders or procurement proposals are within short period ( 2 or 3 days based on our setting) from the requirement date(PIR,Sale order).  Check in OPPQ for plant parameter 'Rescheduling' function and OPPR if material is assigned with MRP group.

Case2: Yes.

Regards,

Dharma

[former_member209175]

Hi Dharma,

Thank you. The exception message is displayed as "10 - Bring Process Forward" if i create the planned order with finish date as 01.11.2013 & the PIR date as 21.10.2013 which is out of tolerance limit set in OMD1 / OPPQ/ OPPR.

As requested in beginning of the post, How the "Conversion Indicator" is set automatically while manually creating planned order in MD11 also this indicator is set automatically when MRP creates the planned order?

Thanks

[Former Member]

Hi,

Conversion indicator is set automatically by system and it is based on planned order type. System assign this indicator when new planned order created by MRP run.

Regards,

Dharma

[former_member209175]

Hi Dharma,

I have one more clarification.

Your statement is:

Do you mean that the "Requested Delivery Date (VBAK-VDATU)" of the sale order & the planned order finish date (PLAF-PEDTR) are NOT same, after MRP run, the planned order will be deleted if the firming indicator is NOT set. Am i right?

Ans: Yes, system checks planned order finish date with sale order delivery date in case of backward scheduling. If it is forward scheduling, system checks the sale order date with planned order start date.

QUS1: In which t.code, we are specifying that "Forward Scheduling" or "Backward Scheduling" to be carried out?

Note: I will maintain the scheduling type as 'Backward" while production order creation in CO01. Are you mentioning the same? Do we need to maintain the scheduling type (Forward / backward) in sale order as well?

QUS 2: You mentioned as "Sale Order Date". Is this sale order creation date (VBAK-ERDAT)?

Thanks

[Former Member]

Hi,

Scheduling types are maintained in config level. For planned order, Define scheduling parameter for planned order - OPU5. For production order, Define scheduling parameter for production order - OPU3. For you second question, I meant for requested delivery date.

Regards,

Dharma

[former_member209175]

Hi Dharma,

Your statement is:

System will check the requirement (PIR, sale order) on that particular unfirmed planned order date and try to satisfy those requirement with this planned order.  Planned order will get delete if no requirement exits on that particular date when run MRP.

System will not propose any rescheduling exception message since this unfirmed planned order can be changed or deleted by system when MRP runs.

But consider the below example.

[Caetano]

Hello

Your planned order start date was probably in the past, therefore, MRP automatically changed to forward scheduling considering today as the start date, and throw exception message 30 for this planned order, to inform the planner.

Exception message 30 can be also displayed for unfirmed MRP elements in this case.

BR

Caetano

[Caetano]

Hello

Check the following WIKI for more details:

http://wiki.scn.sap.com/wiki/display/ERPMan/The+causes+of+exception+message+30+in+transactions+MD04+...

BR

Caetano

[Former Member]

Hi SK,

Kindly check the MRP data maintained for that material. If you are not able to find the reason, provide all the details which you have used for testing.

Regards,

Dharma

[former_member209175]

Hi Caetano,

Thank you for the WIKI link. In the WIKI link, it is mentioned as below.

"MRP executes backward scheduling first from requirement date 08.10.2013 to calculates the release date of purchase requisition, this material has 30 days of planned delivery time only, so the release date is 08.10.2013 - 30 calendar days = 06.09.2013 which is in the past".

Is MRP ALWAYS does the scheduling by "Backward Scheduling" by default? If i want to change this to "Forward Scheduling", in t.code can i make the necessary settings?

Thanks

[Caetano]

Hello SK

MRP will always use backward scheduling, considering the requirement date as the basic finish date. System will only change to forward scheduling when the start date calculated is in the past and this is not allowed on customizing.

Please take a look on the following KBA for more details about forward scheduling on MRP:

https://service.sap.com/sap/support/notes/1913017

BR

Caetano

[former_member209175]

Super Caetano. Very useful link...I do not aware of the transaction CA97 / CA97N to update material master based on routing data.

Awarded Point

Thanks

[Caetano]

Hi SK

Thanks for your feedback!

BR

Caetano