Order Change Management

8/9/2019 Order Change Management

http://slidepdf.com/reader/full/order-change-management 1/19

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

© 2009 SAP AG 1

Order Change Management (OCM)

Appl ies to:

SAP Shop Floor Control (Production Orders) – R/3 and ECC 6.0

For more information, visit the Product Lifecycle Management homepage.

Summary:

This is an article explaining the application of Order Change Management component in the manufacturingprocess. In this article, required configuration settings and process are explained with an example.

Author : Rajarao Chitturi

Company: Intelligroup Asia Pvt Ltd

Created on: 25 August 2009

Author Bio:

Rajarao Chitturi has 11 years of experience in planning & manufacturing sector whichincludes 4 ½ of years of SAP experience in Production Planning Module. Currently he isworking with Intelligroup Asia Pvt Ltd as a Consultant.

https://www.sdn.sap.com/irj/bpx/plm

https://www.sdn.sap.com/irj/bpx/plm




Table of Contents

Introduction ......................................................................................................................................................... 3

Configuration Settings ........................................................................................................................................ 3

Master Data Settings .......................................................................................................................................... 8

Process Flow Steps ............................................................................................................................................ 9

Restrictions ....................................................................................................................................................... 18

References........................................................................................................................................................ 18

Disclaimer and Liability Notice .......................................................................................................................... 19


© 2009 SAP AG 2




Introduction

Engineering Change Management (ECM) allows us to change various master data in a coordinated mannerwhen they have to be changed together within a change process. Future procurement elements (For Ex:Production Orders) can thus be created directly with a changed product structure.

Using Order Change Management (change management for production orders), in short OCM, it is possibleto include existing procurement elements (production orders, planned orders, purchase orders) that arealso affected by a change, in the change process. The change process begins when a sales order or master

data is changed.

• The change process in OCM is based on Initiating Objects. These initiating object records refer tochanges in sales orders or in master data, which, in turn, necessitate changes to production orders.

• The initiating object determines which procurement elements are affected by a change and aProcurement Element Change Record is created for each one.

• On the basis of the procurement element change records, a controlled change of production orderstakes place. In detail, changes are determined, checked and executed. The change process iscompleted when the production order has been changed.

This article focuses only on the changes related to master data.

Configuration Settings

Create Change Profile (T-Code OPL7)

SPRO Production Shop Floor Control Operations Change Management for Production Orders(OCM) Define Change Profile

In this profile we make settings to handle conflict situations.

We can specify whether particular actions in change management represent a conflict depending on theprocessing state of the order or the objects involved. The objects, actions and conflicts involved are:

• Objects: Operations, Sub operations, components, directly produced components, PRTs

• Actions: Change, Delete, Create, Reassign

• Level of Conflict: No conflict, information, Warning, Error.

For each object and action there are various situations for which we can specify which level of conflict shouldapply. The following are examples of possible settings:

• Change a released operation : Information

• Delete a released operation : warning


© 2009 SAP AG 3




In the general tab, flag “when warning appears, execute and mark changes” and “individual change stepscan be executed” and select components check box under “Do not delete manually added objects”.

With these settings, system will copy the changes to the production order with change indicators. It allows usto execute change process step wise (Determine changes, check changes and change original order.


© 2009 SAP AG 4




Manually added components will not be deleted automatically by the system instead system sets the status“Do not Execute”


© 2009 SAP AG 5




Under Order header, select the required radio buttons (conflicts) for a change action depending on the orderstatus.


© 2009 SAP AG 6





© 2009 SAP AG 7

42BSimilarly for component object, set the required conflicts those are to be displayed for different actions duringchange process.

43B

Define Overall Change Profile

44B

SPRO Production Shop Floor Control Operations Change Management for Production Orders Define Overall Change Profile

45B

Assign change profile to the overall change profile.





© 2009 SAP AG 8

46BMaintain Release Key

47BSPRO Logistics – General Engineering Change Management Release Key Define Release Key

48BDefine the release key with the flag checked for “Rel.OCM” check box. With this setting an initiating objectcan be written in order change management for basic data changes with this release key.

7BMaster Data Settings

49B

Assign this overall change profile Z00001 to finish material in the work scheduling view of the materialmaster.





© 2009 SAP AG 9

8BProcess Flow Steps

50B

I am simulating the process considering the changes in the BOM. Assume that we have already a productionorder (60003985) available for this FINISH2 material.

51B

Materials used are FINISH2 (Finish Product), RAW2, RAW3, RAW4 & RAW5 (Components)

52B

Currently, FINISH2 material BOM has three components RAW2, RAW3 & RAW4.

1.53B

Create Change master (T-Code CC01)

54B

Select type as “change master” and function as “with release key”

55BWith Release key function we will have the control to transfer the changes to a particular area for ex:Planning or production or costing.





© 2009 SAP AG 10

56B

Without Release Key function changes will be transferred automatically to all application areas.

57B

In the change header enter change number description, valid from date and set the change numberstatus as “01” (Active).

58B

After that click on object types and for BOM object, flag the check boxes actv., Object, MgtRec .

• 59B

Check box actv. indicates that this object type is active for this change number

• 60B

Check box Object indicates that an object management record is required for this object

• 61B

Check box MgtRec indicates that management records are created automatically for allobjects with these types that are processed using this change number.





© 2009 SAP AG 11

2. 62BMake changes to the BOM with reference to change number (500000000069)

63B

Enter the change number along with material, plant and usage

64B

In the BOM delete component RAW4 and add the component RAW5 and save the bill of material.





© 2009 SAP AG 12

3. 65BRelease the change master to Order Change Management (T-Code CC02)

66B

Set the release key as 04 (Release changes to OCM) and save the change master

67B

This means we are releasing the changes made with reference to this change number(500000000069) to OCM

68B

Note: Once we release the key to OCM, we can’t reverse it back.





© 2009 SAP AG 13

4. 69BSearch for Initiating Objects (T-Code COCM)

70B

Flag change number check box and enter corresponding change number and execute. System willdisplay all initiating objects for that change number.





© 2009 SAP AG 14

71BSelect the initiating object and click on procurement element to get the effected production orders.

72B

System will display all the effected production orders. Select the required production order andexecute for change process.





© 2009 SAP AG 15

73BSelect the required procurement element and execute change process.

74B

Here system will propose us to carryout the change process step wise. We can carry out the change

process step by step or we can process all the steps at a time.75B

Once the change process completed, we can see the following markings against each steps.





© 2009 SAP AG 16

76BBy clicking the changes push button we can see the changes which are going to be applied to theproduction orders.

77B

Negative indicator indicates “object still has to be deleted” and positive indicator indicates that “objectis added”.

5.78B

Confirm the changes in the production order (T-Code CO02)

79BIn the components overview of production order, we can see change symbols against thesecomponents.

80B

These changes will be affective only if these change actions are confirmed.





© 2009 SAP AG 17

81BTo confirm these changes, select these two components go to component menuChange action confirm.

82B

After confirming the changes, change symbols will be disappeared and deleted component will beshown in the blue color.

83BSave the production order.





© 2009 SAP AG 18

9BRestrictions

84B

We can carry out the full change process only for production orders. Fixed planned orders and purchaseorders cannot be changed in the change process, but they can be identified as affected procurementelements when changes to sales orders occur.

85B

The order change process does not support changes in

• 86B

Components for which a batch split has been executed

• 87B

Co-products

• 88B

Sequences

89B

With master data changes, the order change process does not support changes in

• 90B

Materials for which discontinued parts have been defined

• 91B

Alternative Items

• 92B

Trigger points

• 93B

Headers of phantom assemblies

• 94B

Production resources/tools

• 95B

The network structure in collective orders

• 96B

The usage of alternative dates in change numbers

10BReferences

97BH

Order Change Management

98BH

Engineering Change Management

99B

For more information, visit theH

Product Lifecycle Management homepageH

.




SAP COMMUNITY NETWORK SDN - sdn sap com | BPX - bpx sap com | BOC - boc sap com

11BDisclaimer and Liabili ty Notice

12B

This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is notsupported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade.

13B

SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document,and anyone using these methods does so at his/her own risk.

14B

SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article orcode sample, including any liability resulting from incompatibility between the content within this document and the materials andservices offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of thisdocument.

Documents

Order Change Management