SAP - Organisational Change Management History

Having been involved in many SAP Projects as a change management specialist, I have often wondered how either the consulting house I am contracting to, or the client get their ideas about change management in SAP projects.
Some believe it lies in the domain of industrial psychologists who want to help people 'embrace change'. Others believe that it is mainly about communications.
I would love to hear different viewpoints about how SAP Change Management developed over the years and why people have gotten so confused about the role change management plays in SAP projects.
For me SAP ASAP details the Change Management deliverables, however very few people actually know how to execute these plans or what they are supposed to achieve.
I think the problem with how people view change management, is that it is a soft subject and is therefore highly flexible and can be done by anyone.
I listed the Change Management deliverables in my blog /people/swen.conrad/blog/2006/06/01/business-analyst-133-aris-for-netweaver-133-business-process-expert-133 .
Why is it that people do not adhere or use these deliverables?
With Kindest Regards
Paul Wilson

Hi Paul
Brilliant topic and one that in my experience is still not understood completely by clients and SI companies alike. My fundamental belief is that until an ERP implementation is viewed as a business transformation initiative, then change management is always going to be a 'nice to have' work-stream heavily focused on project communication and training. This is only the 'tip of the iceberg' in change terms and often projects start stalling or experiencing difficulties across the stakeholder landscape as other key areas of change management have been completely neglected. My experience in developing and executing the CM work-stream for an ERP project is outlined below:
1. Defining the scope of the ERP change programme and clearly articulating why the ERP implementation is taking place.
2. Starting Business Engagement and Business Readiness activities at the beginning of the ERP implementation is a key success factor. In many instances I have seen this activity either done poorly or not done at all until later on the project, creating a completely dis-engaged Key User community.
3. Developing a detailed definition of the changes that the new ERP system will introduce into the organisation and conducting a high level Change Impact Analysis to determine the degree of change coming in respect to people, processes, technology and infrastructure.
4. Designing and building the ERP solution so that it can deliver the strategic goals of the organisation. At this stage it is vital to involve the business in designing a 'fit for purpose' ERP solution.
5. Vitally important is getting the business to work with the ERP core project team to prepare adequately for go live. Making sure that all activities for cutover are completed in a timely manner, the business is engaged and the end users are aware of post go live support arrangements is a key role of the change management function.
6. CM is then fully involved in supporting post go live activities. Working closely with the business to identify business as usual owners is an important activity for the CM team. Measuring the system performance and ensuring business benefits are being realised is an ongoing task of the CM function until handover to the BAU teams.
7. Documenting the lessons learnt and manage the transition from the Programme to business as usual is the concluding stage for CM activities.
These CM themes are fundamental in making the ERP change programme a true success but can only happen if there is total commitment from top leadership to run the initiative as a proper business transformation effort..

Similar Messages

SAP PLM change management

Hello All,
Have two questions to understand latest trends in PLM.
1. What is the recommended tool we need to use for Engineering change management
as per latest trends in PLM. Is ECR/ECO CC31/CC32 still considered
part of best practice or has been Obsoleted ??
2. For Cad Integration, is CDESK obsolete. Has Engineering
Desktop overtaken CDESK. I used to work with CDESK in the past.
Thanks,
Sachin

Hi Sachin
Please find the replies for the query you have asked.
1. What is the recommended tool we need to use for Engineering change management
as per latest trends in PLM. Is ECR/ECO CC31/CC32 still considered
part of best practice or has been Obsoleted ??
It is still used in industries. But with PLM 7.02 you have more robust mechanism of Engineering
Records which has better capablities than ECR/ECO.
2. For Cad Integration, is CDESK obsolete. Has Engineering
Desktop overtaken CDESK. I used to work with CDESK in the past.
SAP Engineering Center Control is used .
Thanks & Regards
Satish

Change Management & Change Transport Process in GRC AC RAR

With RAR not being able to leverage the SAP ABAP Change Management Process (CTS) what is the best practise for controlling the changes for RAR rule set ?
How do we acheive job segregation from
1. Making Changes to Rules in Dev RAR
2. Transporting (Importing) them to RAR Prod
How do we make sure the 'Import Rules' functionality is restricted. ? (Can we remove Action 'ImportRules' from all the roles and restrict that to one role & restrict the administrator from making role assignments directly in RAR (Only from CUP) )
Thanks

Hi Prashanth,
You can restrict the access by removing the action ImportRules from the customized role that you can create in UME for RAR.
Thanks,
Darshan

Software Change Management - usage in SAP

Hi,
Please anybody can -
Are we using version control tools like ration rose, SCM Software configuration Management in SAP?
Thanks in advance
Swamy

Hi,
Version Management is there in SAP also. SAP maintains Change history for most of its transactions.
*Version Management *
Use
Version management in the Integration Repository permits versioning as follows:
· The Integration Builder manages multiple versions of a software component in an Integration Repository. In this way, different product versions can communicate with each other. Each design object is created in the context of a software component version that represents a unit of a product that can be shipped.
· Objects can also have new object versions when changes are made within a software component version. You also have the option of releasing changes to multiple objects simultaneously.
Versioning in the Integration Repository ensures that objects are shipped consistently, and as part of a product.
However, there are no software component versions in the Integration Directory, because the configuration content is not shipped. Nevertheless, you can also release changes to the configuration for the entire runtime environment here. When you release the objects, the Integration Server updates the directory runtime cache.
Integration
You can also export objects of an Integration Repository or an Integration Directory to import them into another repository or directory (for example, during system relocation). In doing so, versioning of the corresponding software component version is taken into account.
Features
Change Lists
The Integration Builder supports object versioning for both the repository and for the directory using the user-specific change lists. When an object is saved for the first time, a new object version is created, which is added to the change list. When an object in the change list is activated, the object version is closed and is made visible for other users.
Products and Software Component Versions
A product can have multiple versions. Each product version is a shipment unit visible for customers. The software component versions used in a product version can be called in the System Landscape Directory.
In the context of SAP Exchange Infrastructure, the products and software component versions that are of interest are those that are to exchange messages with each other. When development starts they must be imported from the System Landscape Directory into the Integration Builder.
Release Transfer
In the transition from one software component version to a new software component version, you can either transfer all, or just some of the design objects from the previous version. This release transfer also enables you to transfer objects to older software component versions.
Regards,
Renjith Michael.

SAP ChaRMs vs HP PPM change management

Hi Guru's,
I would like to know the comparision between SAP Change request management and HP PPM Change management.
Request you to please provide information on the above.
Regards,
Vinod

Hi Sanjana,
There are 3 different options fro Test Management using Solution Manager. HP QC is used in the Test Management Option 2. You can also avoid HPQC if you go for Test Option 1 (CBTA, ECATT, QTP..). The third option is to use IBM Rational tools for testing. All the info you are looking for is given in this wiki http://wiki.scn.sap.com/wiki/display/SM/SAP+Solution+Manager+WIKI+-+Test+Management
Regards,
Vivek

BO Data Services Change Management with SAP Charm Functionality

HI Gurus,
We have been tasked with automating the Change Management activity for Business objects data Services. The same is currently performed as a manual task which could be prone to errors. We have researched all over the place and we have not been able to find any documentation on in order to carry out this activty through Solution Manager ChaRm functionality.
So, Can SAP Solution manager perform the LCM (Life Cycle management) for Business objects Data Services via means of it CHaRm functionality?
Right now we know that the components for BO are present on Solution manager within the SMSY transaction. We have also been able to create the complete landscape within the same and create a project template for it.
Now the challenge is how do we configure ChaRm in order to move the DI code from one repository to the next?
here are the requirements we are trying to implement:
1. Create a full landscape for Business Objects Data Services within SMSY in Solution manager
2. Create Project template for Business objects Data Services
3. Create RFC connections to Database and BODS Client Servers
4. Configure Charm in order to automate Change Management for Data Service
Please advice.
Thanks,
Nat Hernandez
SAP BO/BW Technical Architect

Hi Natanael
I am also looking for the same
Would you please let me know how did you implement this

Typical example of SAP change management in SD scenerio....

Dear All,
Is there anybody who can provide me with typical example of SAP Change Management scenerio in manufacturing industry OR in consumer industry.
I am looking for some example that has improved a business process tremendiously OR made the business process simpler to use. At the end stakeholder got benefited with that change.
Thanks you all in advance.

Dear All,
I am putting my query once again....to see if I can get some expert help.
I would like to know any particular example of any manufacturing OR consumer goods industry where SAP software itself had made a great changes in change management prospective( ex -any business process change which had to make to make present process more smoother or cost effective).
Hope to hear from some of few.
Thanks in advance,
Cheers!

Error in solution manager; no active task list exists in sap change manager

Hi,
i have created a correction in Solution manager but when i want to set it in status in development i receive the message below
No active task list exists in SAP Change Manager
could you please help me?
thanks
C.

cmarrone wrote:Hi,
This says taht your ChaRM configuration is not complete. You need to rectify these errors to work in ChaRM.
>
> listed below the detail of the errors:
> Error in background job for program RSGET_SMSY error message No active job found
1. Please activate the Landscape fetch job for RSGET_SMSY from SPROSolution ManagerBasic Settings-- Schedule Bgd jobs.
> No RFC connection for system CIA client '000'
Please maintain a connection from solution manager to the transport domain system . I belive this is CIA.
> No CTS projects found for project ARC_AM_001
Recheck the transport configurations.
Rajeev

Does SAP keep change history for program variants?

Hi,
Does anybody know whether SAP keep change history for program variants, like it does for PO, Material etc?
If so, how could I get this information? If not, does it mean there is no way we could find the changes made to the variant?
Thanks
steven

Hello Steven,
I see that this is your first post to the forums here and I would like to welcome to SDN and BPX. I hope you will find these communities very helpful for learning and sharing information about SAP Products and Technologies.
Regarding your question, I think the best place to find the answer would be the ABAP Development.
However, being an experienced ABAP developer myself, I do not think program variants have change history. And yes, there is no way to retrieve the old values of the variants .
Regards.
Anand Mandalika.

Typical example of SAP change management..

Dear All,
I am not sure whether I should be putting this question here or not....
But if I may ............Is there anybody who can provide me with typical example of SAP change management in manufacturing industry OR in any other scenerio.
Thanks in advance.

Thanks Jacqueline,
These are excellent examples.......
I guess batch processing is most commonly used in pharmacuetical industry. Let me know if you can elaborate more on delivery creation scenerio I.E what you have mentioned earlier.
Unfortunately I have not worked in batch processing.
If you remember anything in terms of any other change management example please do add on this.
Thanks again,
I am forwarding points to you for helping me.

SAP certifications for E2E RCA, change management

Hi,
I wanted to find out if the skill sets required for implementing E2E RCA and Change management really require training and certification. I am being asked to do it.
Is this a hot skill set to acquire, are many people implementing RUN SAP for Support.

Hi, yes, its going to be a hot skill considering the facts about the Run SAP and the tool being under the methodology is the Solution manager. It provides functionality and support operation tools that will assist in operations of large sap solutions quickly and efficiently.
http://download.sap.com/services/bysubject/support/brochures/download.epd?context=A868467FD491523D39B275AEAFD72EAED1F5B2A981D54AD33AF85A62DF0CCB8D7E73D3A29D48B6C0D62F2C64D8543DB62F259430DECDB024
Regards,
Debasis.

SAP MDM7.1 Change Management CTS+ Queries

Hi.
I have few doubts on Change management CTS+ , Kindly please suggest!
1) Is it based on ABAP Stack / or do we need ABAP System for this ?
2) How transport can be handled ? from PI to MDM system?
3) What can we transport ? is it everything or some limitation are there during transport?
4) Can we transport the changes for repository?
Please suggest !
Regards,
Harmony

Hi Harmony,
1) Is it based on ABAP Stack / or do we need ABAP System for this ?
You need an SAP NetWeaver AS Java and an SAP NetWeaver AS ABAP. SAP recommend that you use the SAP Solution Manager. The systemu2019s Support Package Stack must be NetWeaver 7.0 EHP1 or higher.
2) How transport can be handled ? from PI to MDM system?
I didn't get you here exactly. If you mean how to transport MDM in the system landscape, then it works as: The deployment of MDM specific transport orders in the current version is done with provisioning the change files to the CTS+ outbox folder defined for the MDM target system, where the MDM administrator has to pick it up for manual MDM deployment.
3) What can we transport ? is it everything or some limitation are there during transport?
With MDM 7.1 the following data model objects can be transported from a source system to a target repository:
1. Tables & Fields
2. Relationships
3. Languages
4. Roles
5. URLs (Web Links)
6. XML Schemas
7. Remote Systems
8. Ports
9. Validations and Calculations
10. Assignments
11. Workflows (new with MDM 7.1)
12. Import Maps (new with MDM 7.1)
13. Syndication Maps (new with MDM 7.1)
14. Matching Rules including Matching Strategies (new with MDM 7.1)
4) Can we transport the changes for repository?
Yes, we can manage the transport changes for a repository using Change Extraction Process. It consists of following steps:
1. Defining a basic reference before starting to perform the data model changes (this basis will later be referenced to extract the changes done).
2.Extracting the changes to a MDM change file (.xml file).
3.With The Change extraction automatically a new reference is created to be able to calculate the next set of changes to be extracted.
For complete details, Please refer the below guide:
[Setup and Use the MDM Change Transport with CTS+ Transport Management Environment|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d0dd1ae0-36e5-2b10-f8b4-e6365e643c0b?quicklink=index&overridelayout=true]
Regards,
Mandeep Saini

Order Change Management(OCM) in SAP

Dear All,
OCM is applicable in MTO Scenario.
Kindly let me know the steps involved to activate OCM n how to proceed
further.

Hi Bagchi,
Order Change Management is applicable for MTO/MTS Scenario,
First:-
In WorkScheduling View of Material Master (FERT/HALB or Any Defined for Production) you need to maintain "Overall Profile"
This Overall profile should be configured in SPRO > PRoduction>Shop Floor Control > Operations>Change Management for Production Orders-->Define Overall Change Profile.
Process of OCM follows this way:
Create a Change Number CC01 with Release Key
In Object Types select/tick "Actv", "object", "MgtRec",
You get the Change Number by Saving .
Use this Change Number to Change BOM or Routings
Then Release the Change Number useing Release Key till then you don't find the Change of BOM in Production Order.
Then go to Oder Change Process T Code :- COCM
Tick Change Number and Select the Change Number & Execute
Select the Production Order, click on Procurement element icon you get another screen select and execute again.
You get an Pop-Up screen. "Determine changes, Check changes, Change Original Order.
you see the changes in BOM for Production Order i.e. after COCM.
Then Confirm the Changes in Production Order then New changes will be Active in production Order.
Regards
Rehman
Reward Your Points If Useful

BOM change with history requirement

hello,
requirement: CS02 must input Change Number
configuration:OS25: BOM Usage-BOM status -history requirement flag selected
issue: CS02 change BOM, only warning message: Enter change number -BOM has history requirement
how to meet my demand? any other configuration?
pls give me some help, thanks
best regards
lee

Hello check this SPRO settings ;
Engineering Change Management Setup
This are the basic IMG settings in order to used the engineering change management
features.
x refers to a tick.
First setup the control data in OS54.
Revision sections
Fields :-
Revision level active            x
Ext. revision level              x
Higher revision level            x
Object Management Record sections
Fields :-
Object maintenance               x
Assign alternative date          x
Overide value/assignment date sections
Fields :-
Only with leading change mst.    x
Setting the Revision level active is to activate the engineering change management for
material master. If you do not want the engineering change management for materials,
remove the tick.
With a tick in "Higher revision level", the new revision level has to be always higher
than the old revision.
Secondly, setup the external number range in OS53.
If you use the internal number range, then remove the external number range.
Third, define the status for the change master records in transaction SM30 - V_T419S.
Change No.     Chg        Date Chg     Dist. Lock      Description
Status         Poss
1             x            x             ' '         Active
2            ' '          ' '            ' '         Inactive
3            ' '          ' '             x          Locked
Fourth, define modification parameters for the BOM in OS27.
Fields :-
BOM Validty Maint.               x
EC Management Active             x
History Requirement             ' '
Unit Piece                      PC
The rest of the fields are blank.
If the History Requirement is tick, every time during creation of the BOM, SAP will
prompt your for an ECN number as is compulsory.
Lastly, define fields selection for routing in OP5A.
PP task lists: initial screen -> Change number -> Transaction code -> Tick Req.
Setting the Transaction code fields Required indicate that you have make the ECN number
compulsory when changing the routing.
Finally, do a test by making changes to the Material Master, BOM and Routing.
Regards,
jaya Vimal

SAP Handling Unit Managment

Hi folks,
I very urgently need some documents about SAP HUM.
Can any one help me.
Laxmanan

SAP HU - SAP Handling Unit Management (HUM)
The SAP HU is used for tracking the handling units used by the materials. Some common handling units are packagings materials like cartons, pallets etc.
In the SAP system, the handling unit (HU) expands on the shipping unit. Handling units can be nested and you can also create new handling units from several handling units as often as you like. At the material item level, HUs contain the complete material identification, the quantity, and, in the case of serial numbers, the respective object list. Handling units have unique,
scannable identification numbers that can be developed according to standards such as EAN 128 or SSCC.
Handling units contain all inventory management information of the materials they contain that are maintained in Inventory Management. There are also status messages that you can call up at any time that indicate whether a handling unit is only planned or if the ship-to party has been notified of the arrival of this handling unit, or whether it is in the warehouse or has already been posted to goods issue. The integrated history function also records each business process in
the life cycle of each handling unit, meaning that you can track the handling units path and development at any time.
Refer to : Logistics -> Central Functions -> Handling Unit Management
In HU-managed storage locations, all goods movements are executed through the specification of the respective HUs, and Inventory Management is performed through the handling units. If you are working without HU-managed storage locations, you can work with handling units (without stock information) as before in the delivery and in the shipment.
In HU-managed storage locations, materials can be managed in HUs only. Mixed stock made up of packed and non-packed materials within the same storage location are not supported. HUs can also be managed in interim storage types. Unpacking a material from a HU means that the stock of the material is posted to a storage location that is not HU-managed.
If you call up normal material movements in connection with an HU-managed storage location, a delivery is created, rather than a direct material posting, which has been the procedure up to now.
Please note that if you want to use 311 to move the material already in stock, but in a non HUM Storage Location and you want to transfer those materials into a HUM Storage Location 304. If this is the case you can use the transaction VLMOVE with the destination plant and storage location. Before that you have to create the HU with the transaction code HU02 Storage location: where the material is and the status: in stock.
Handling units are unique at client level in at least one system. Using an indicator at client level, you can control whether you are going to work with the HU functions. Since the handling unit is a physical unit, the central logistics processes are controlled through the input of the handling unit identification. These processes include putaway, picking, and stock transfers, as well as goods receipts and goods issues.
A handling units mobility can be limited if quality checks are active. Changes in the stock category caused by a quality inspection are made using a posting change in the handling unit.
There is also a report available that you can use to find and display handling units using different selection criteria such as material, packing instruction, or storage location.
Although the handling unit is basically a unit that remains constant in the system, you can change it by repacking the materials it contains. All the packing functions, such as packing, repacking, and unpacking, are completely supported by the handling unit functionality. In this way, handling units can be created in production, during goods receipt, or in the packing areas of the warehouse. If you have automatic packing, the handling unit is created from the packaging proposals defined in the system (from the packing instructions, for example).
Regards,
Rajesh Banka
Reward points if helpful.

SAP - Organisational Change Management History

Similar Messages

Maybe you are looking for