SAP Production Versions

Study Material Contributed by Ulhas Kavle - Senior SAP Consultant

SAP Production Versions

Production Versions:

When you come across scenarios where you have multiple Bill of Materials (BOMS) for a material and/or Multiple Routings/Recipes (task lists) for a Material then it becomes impossible for the system to choose a BOM and task list for your production order/Process order/Run Schedules; in such cases SAP has provided Production versions to solve your problems.

Here you can define the BOM number/Usage and the Routing Group/Group Counter for a material which will be used for production of the material under the criteria of lot sizes and validity dates. This also helps the system, in picking the predefined BOM and Routing/Recipe rather than going mad on which to pick in the automatic MRP run.

Every Production version for a material at a plant has a alphanumerical number assigned to it.

You can also assign Rate-based Routing for repetitive Manufacturing and Rough cut Planning.

Along with BOM and Routings, Production Versions also have the following:

a) Production line on which production is carried out.

b) Scheduling work center, if this is not the production line, but a specific work center on the production line, for which scheduling is to be used. For this, you must have maintained a line hierarchy, from which the system automatically determines the scheduling work center.

c) Receiving storage location: this is the storage location to which the manufactured product is posted at goods receipt.

d) Proposal issue storage location: this is the storage location from which the components required are withdrawn and which is proposed when back flushing.

e) REM Allowed indicator: If you want to use the Production Version in Repetitive Manufacturing you have to select this indicator.

Automatic Selection of Production versions

Production Versions are selected automatically by the system with the help of the lot size and the validity dates maintained for them. If you are using Production Version as a criterion for deciding the BOM and Routings for Production then in that case you should maintain the “BOM explosion selection procedure field” in MRP 4 as “2” or “3”.

Maintaining 2: Will allow Selection of BOM (and Routing) in the order through production versions and if a valid version is not found, it can still go ahead and give you option to choose BOM (and Routings) through other manual selections and build one yourself in the order.

Maintaining 3: Will allow Selection of BOM (and Routing) in the order through Production versions only and if a valid production version is not found according to a lot size and validity date it will abort the creation of the order.

Automatic Selection Procedure

For example if you create only one Production Version for a lot size of 0 – 10000 Units and Validity date of 25th Dec 2010 to 25th Dec 2020 and if you create a Production order for a qty of 20000 Units on 1st Jan 2011, then there will be Production version selected as the lot sizes do not match the criteria i.e., no BOM and Routing selected, on the contrary if you create an order for 9999 units on 24th Dec 2010, in such a case also there will be no Version selected as validity dates do not match the criteria.

But if you end up having one production lot size and one validity date range with different BOMS and Routings for the material, then SAP (MRP and Production) would always choose the first defined Production version according to the number range of the Production version or the first maintained production version.

If the lot size of the product does not govern the selection of a bill of material and routing {recipe}, we can keep it as 0 – 99999999999 units. And if the dates of production do not govern the selection of bill of material and routing, we can keep the validity dates as “today – 12/31/9999 {MM/DD/YYYY}”.

Production Version Status

You can lock a production order for use or release it for use in orders.

All the site contents are Copyright © and the content authors. All rights reserved.

All product names are trademarks of their respective companies. The site is in no way affiliated with SAP AG. Every effort is made to ensure the content integrity. Information used on this site is at your own risk.

The content on this site may not be reproduced or redistributed without the express written permission of or the content authors.

Sitemap Sitemap