Skip to Content

Usage of Revision Level for PP Masters -BOM and Routing

This Blog details the usage of revision levels for creation and change of PP masters like BOM and Routing. It gives an insight on how master data is tracked with different revision levels.


In a public sector client, there was requirement to map the drawing number and its alteration index in SAP PP process. Design department who owns the ownership for product designs creates design drawing and sends to planning department with some alteration index like ‘a’ or ‘A’ etc. Planning department identifies, defines structure, executes product manuafcturing based on the drawing and its aleration index. Even quality department tracks the inspection with respective to drawing number and its alternation index. Another challenge  is there will be changes for the intial design where in the alteration index will be changed from ‘a’ to ‘b’ or ‘b’ to ‘c’ etc. This change can happen during planning or while executing the production.Finally at the end of the day, report is required to see the history of changes.

Approach used:

Engineering Change Management(ECM) is used to track and control all the changes with reference to Material master, BOM, Work Center & Routing. Mapped drawing number as material number and alteration index as revision level.

Configuration Used:

ECM Control Data ( OS54)

Change Master Number Ranges (OS53)

Standard config used.

Define Revision Levels (OS55) – Revision levels defined as required.


Define Modification Parameters for BOM (OS27)


Profile PP000001:


OP5A: PP task lists: initial screen -> Change number -> Transaction code -> Tick Req

While creating the routing revision level field should be mandatory. Below is the config

Steps followed for creating and changing the master data:

  1. Create change number(CC01)
  2. Assign change number to Material (CC11) with initial revision level
  3. Create BOM (CS01) and Routing (CA01) with revision level
  4. Create new change number with different validity date (CC01) and assign to material with new revision level (CC11)
  5. Display revision levels (CC12)
  6. Change BOM(CS02) and Routing with new revision level (CA02)

Step 1: Create change number( Tcode CC01) – Select the profile created PP000001 as displayed below. Maintain the change number description, valid from date. On save change number gets created.


Step 2: Assign Revision level to Material (CC11) – Against the material change number and revision is entered.

Before assigning the revision level in MM02 for the material M-800 there is no revision level as displayed below


Go to CC11, enter material number, change number and select the revision level A and enter. System will copy the valid date of the revision level A. Then SAVE.


If we now go to MM03 and check revision level gets assigned to materia las given below


Step 3: Create BOM with respect to revision level – CS01

Enter material number, plant, BOM usage as 1 and put F4 on revision level. System will display the available revision level and its change number as displayed below. In order to make the Revision level field as mandatory used transaction variant for CS01/CS02.


Select the change revision level A. System will copy the change number and valid from date as displayed below.


Once we click enter system displays BOM general item overview screen. Maintain the BOM materials. Component T-T029 maintained with qty as 2 pc as given below. Revision level will be displayed besides the Material number and change number displayed towards right of the BOM items. Now the present BOM is valid for revision level A only.


Step 4: Create Routing with respect to revision level – CA01

Enter Material number, Plant and Put F4 on revision level. Based on config set in OP5A revision level is mandatory as displayed below.


Revision level and change number along with valid date is copied as displayed below.


On enter routing operation screen is displaed where operations are maintained as displayed below.


In BOM only one component is available and is assigned to operation 0010 as displayed below.


As displayed below routing is created against the revision level A and its change number can be seen below.


Step 5 : Changes to Master Data with revision level B (BOM and Routing):

New change number 500000000078 created with valid date as 24.02.2014 for change in revision level from A to B. Revision level B assigned in CC11. After assigning in material master new revision level B will be displayed as given below.


System now displays both revision levels in CC12 as displayed below.


BOM:  BOM is now to be changed with revision level B. In CS02 under revision level two revision levels A and B will be displayed. Latest is the new revision level given for the material.


With revision level B BOM is changed as below.Item 0010 component qty chnaged from 2 to 4 pc and new bom item 0020 added. Here we can see the new revision level B for the

header material displayed besides material number.

  Routing: Similarly routing changed with new revision level B as displayed below.

In Revision level B, material number T-T029 is re-assigned to operation 0020 and new material which was added in BOM was assigned to operation 0010.

Transaction Data:

Created production order, system picked revision level A for the Master data. In order BOM as per revision level A only one BOM item is available and displayed below.


When we use Read Master data( Case -Only order is relased no other movement are done) there will be option to select the revision level as displayed below. Revision level B selected. Now BOM and Routing of revision level B will get copied on order.


Now Order BOM shows two BOM items as per new revision level B


BOM items are also accordingly assigned to the respective oprations as per revision level B as displayed below.



CS11 : Report displayed based on revision level.

Revision level A report with only one BOM material


Revision level B report with two BOM materials.


Difference between revision level A and B. When we go to tcode CS14 BOM comparision then difference between the revision levels is displayed as given below.



  1. Changes to the BOM and Routing are tracked perfectly through revision level provided revision level field is made mandatory in both BOM and Routing.
  2. Based on the latest revision level and validity date master like BOM and Routings gets copied to order.
  3. BOM materials which are added with new revision level will be greyed out incase trying to change the BOM with older revision level
  4. Order information data(COOIS) will be displayed with historical revision level data for the respective orders.
You must be Logged on to comment or reply to a post.
  • good one. What if we have an engineering BOM and want to keep it at a seperate revision level compared to the manufacturing BOM. Right now if I rev a mBOM to rev C then the eBOM also gets rev'ed to rev C. I want to have the ability to rev both BOMs independantly. Is that possible ?

    • Hi GS,


      Thanks for your compliment.


      Yes its possible to maintain both the BOM's( Production and Engineering BOM's) seperately under different revision levels.


      Eg: Production BOM with revision level B and Design BOM with revision level C.


      Thanks & Regards,


        • Hi GS,


          For BOM with usage 1 assume BOM is changed with revision level as B. Now BOM with usage 2 is changed with revision level C. When you try to check the usage 1 BOM with revision level C, system will display revision level as C at BOM header but the componenets and its quantity will be of revision level B only since you have done any changes with revision level C. Similarly for usage 2 BOM system will display the componenets and its quantity pertaining to revision level C.


          At Material level revision level latest is C but changes to production BOM usage 1 are at revision level B and changes to Engineering BOM usage 2 is at revision level C. Hope its clear.


          Thanks & Regards,


          • I ran a test and it works like you described. I was expecting a situation where the mtl is at rev C, production BOM is at rev C and the engineering BOM cannot be displayed for revision C as I never made any changes to the EBOM. Is there a way I can have the system show me an error message in case I try to display engineering BOM with rev C saying "Revision C not applied to EBOM" or something like that. Right now I can see Rev C on the matl and production BOM (which I want) and Rev C on EBOM (which I dont want). The system applies rev C to all the 3 objects.


            Is this the way SAP works ? Is this a process issue ? What is your recommendation ?

          • Hi GS,

            You are right system will display the EBOM though changes are not made for rev c. Since material is active at rev c its displaying the BOM with components quantity of prior rev level. But, system will display an information message "No changes made to object with change number xyz". We can explore on this area to make this message as Error message.

            Thanks & Regards,


  • /
  • Excellent presentation Ramagiri,

    Pl suggest on the above context, what if some deletion of items needed to made in BOM, i.e.Whether to choose revision level.or without it before deletion any items in BOM, kindly throw some light on that, thanks in advance.

  • /
  • dear all

    please help regarding below issue i have to change multiple BOM revision levels in SAP one shot example i have 1000 boms & i have to change 1 part no revision level in 1000 boms

    is it possible ?

    If yes please let me know the T-CODE



  • Hi all,

    Great article Ramagiri!

    A query here:

    We have to mBOMs in 2 different plants. Plant A & Plant B.

    Plant A is responsible for engineering changes to the BOM.

    (But the Material is manufactured in both the Plants simultaneously, hence Plant level BOMs)

    With every engineering change is versioned using a change number.


    Issue now is when Plan A creates a new Material revision and makes changes to its BOM.

    Plan be in CS03, sees the new version of the Material but dot see the changes. (since they were done in Plant A)


    How can we make sure that Plant B consequently sees the changes and accordingly adapts their BOM.

    Showing the latest Material version in the BOM Header is misleading. Since Plant B can very easily be misleaded to believe they are using the latest verison of the BOM. Even when this is not the case.


    Has anyone encountered the same problem?

    What would be the best solution here to handle such changes in the BOMs on plant level?