Production version Picking logic < Conceptual query>

[former_member2091]

Hi All,

I have read lot of threads and did multiple testing scenarios which has left me very confused about the concept of production version and how system will pick it in below cases

1. Creation of process order (COR1)

2,. conversion from plan order

3. MRP run

4. Cost run

In MRP 4 I have tried all scenarios ( 1,2 and 3) with locking and unlocking PVs but still I am not able to completely understand systems behaviour.

Also, what is the best practice to follow when I am creating a new PV should i name it as 0002 or delete 0001 first and create 0001 again because locking an existing PV has no impact and it does get picked up.

[lingaiahvanam · Accepted solution]

Hi Akash,

See the below answers.

1. Creation of process order (COR1)

Production version selection trigger from the configuration COR4 manual or automatic and MRP4 view selection method.

The user can maintain in configuration as manual and selection method 2 then the system will provide the pop up to choose which production version to be processed.

The user maintains configuration as automatic and selection method 1 then the system identifies the relevant production version validity dates and selected production version automatically (no pop-up selection window).

cor4.png

2,. conversion from plan order

During planned order to process order conversion system by default choose the first production version automatically (prerequisite is production version should be correct validity periods), If you maintain configuration automatic and selection method 2 also.

The user can manually maintain the production version in planned order after MRP run and during planned order to process order conversion updated production version carries to process order.

3. MRP run

Please refer to SAP note https://launchpad.support.sap.com/#/notes/2664737 - Production Version Selection Logic in MRP

4. Cost run

The user can maintain a primary version for costing purpose in Costing view 1.

mm03.png

Best practice to select production version based on validity dates.

Consider Brahmankar answer also for locked production version selection usage.

Best Regards,

Lingaiah

[former_member2091 · Accepted solution]

Hello Lingaiah,

Thanks for providing clarification, can you please comment on

1. I have marked PV as "locked for any usage" but still it gets picked up in CK11n with MRP4 all settings except "3". So, should we always set this field as "3"?

2. Our Users are not aware about PV and they cannot change it in plan order then what should be the best approach to avoid conflicts?

As you mentioned,I tried with validity dates and found that it can be used to avoid wrong selection of PV instead of locking. So, is this the best alternative ?

[lingaiahvanam · Accepted solution]

I would suggest instead of production version locking better to maintain proper validity dates, so planning runs easily identify the valid production version and updated in planned orders.

If you have multiple production versions for the same product then controller decision to choose which production version for costing and can be easily updated in costing view 1 as mentioned above.

[rupesh_brahmankar3]

Hello,

Please check the costing tab for production version assignment. You may assign the new PV in costing tab for standard product costing.

Also use setting Selection method - 3 Selection only by production version in MRP 3 view

If production version is not in used then you may delete it and then run the MRP again which will create new planned orders with new production version.

Also note if you delete PV 001 then you can create new PV with same number 001.

Best Regards,

R.Brahmankar

[former_member2091]

Hi Brahmankar,

Thanks again!!

[rupesh_brahmankar3]

Hello,

If you locked the production version system should not pick up this production version during the order creation as per the standard SAP system design.

If you want the locked production version can't be used under any situation, you need to choose lock status as "Locked for any usage".

Please refer SAP Knowledge Base Article 2570485 - Locked Production Version allowed to be selected in COR1

For demand managment (PIR) you should implement SAP note 2734432 - MD61/MD62: Assigning locked production version to PIRs

Best Regards,

R.Brahmankar

[former_member2091]

Hello Brahmankar,

Thank you.

Would really appreciate if you can comment on follow up queries posted below.