SAP Sourcing / CLM Webcast – Object Migration · PDF fileThere are several ways to manage changes in Sourcing / CLM Object Migration Configuration Workbooks CSV Manual Each approach

SAP Sourcing / CLM Webcast –

Object Migration

March 2012

© 2012 SAP AG. All rights reserved. 2

Agenda

Overview of Change Management in Sourcing / CLM

Object Migration Introduction to Object Migration Demo of Object Migration Requirements & Best Practices

Configuration Workbooks What are Configuration Workbooks? Requirements & Best Practices

Object Migration vs Configuration Workbooks General Guidelines

Overview of Change Management


Change Management

There are several ways to manage changes in Sourcing / CLM Object Migration Configuration Workbooks CSV Manual

Each approach has “best fit” and limitations

It is system administrator’s responsibility to keep track of changes made in the source system

It is system administrator’s responsibility to determine what objects need to be migrated and what the dependencies are


Change Management

Most On-Demand customers have 2 landscapes – Development and Production

On-Premise customers typically have 3 or more landscapes - Development , QA and Production. In this case, the QA system can be used to validate the migration packages

All configurations should be performed in source and then migrated to target

system. Migration path in a 3 landscape scenario should be: Development QA Development Production

Common Sourcing objects that are migrated includes: Localized Resources, Value Lists, Extensions, Page Customizations Queries / Reports Scripts, Workflows Doc Types, Phases Configurations Workbench configurations Libraries – Attachment, Information, Questions and Schedule Library Security Profiles


Change Management

Migration Strategy

Migration strategy should be finalized and

communicated with the implementation team prior to the start of realization phase

Examples: Page Customizations should be created using

configuration workbook and applied to Dev, QA and Prod. Page Customizations should not be created or updated manually in the UI

All custom Script Definition IDs should start with Z- All custom Query Definition IDs should start with Z-

All manual configuration changes should be tracked separately and a process should be put in place to ensure the manual steps are applied in the target system

Object Migration


Introduction to Object Migration

Object Migration is a technique designed to move objects from one Sourcing landscape to another

In simplistic view, the process involves exporting data from source system and

import it into the target system

Can be used for full import (during production cutover) and for partial imports (ongoing changes)

Whenever an object is being migrated, ensure any dependent objects already exist in the target system



•The first step is to create a object migration “package” in the source system •A package consists of one or more set of instructions to tell the object migration tool what to export •To create a package use Single Object or Object List or Dataset options depending on what you are trying to export

Determine what to export in source system

•Trigger the export. This step tells the system to export the data as per the instructions in the package defined in the previous step

•System will create an “export.oma” which contains the exported data

Trigger export from source system

•In the target system go to Setup System Administration tab Import •Import the oma file using the import functionality •When importing oma file there is no need to select the object type •Check import results for any errors

Import export file (oma file) to target system

Object Migration process



Export Types

Single Object Allows selection of a single object for export Useful when migrating a specific item. For example, a new column has been added to an existing

query and needs to be migrated

Object List Allows you to select an entire class of objects to export by selecting from a set of available queries

(OML queries) Custom OML Queries could be developed and used with this option Useful in cases where you want to apply your own selection criteria Example: A custom OML query to get all localized resources that are in the “custom” bundle

Dataset Allows you to select a very broad set of related objects Useful during production cutover but typically not for continued support


Demo of Object Migration

Demo of Object Migration


Roles

Who performs the export from Source system?

System Administrator who performs configurations such as Extensions, Page Customizations, etc.

Report Developer Script or Workflow Developer Security team It is important that the person performing the export have a good understanding of the

configuration objects and how they are related Who performs the import to the Target system?

In an On-Premise deployment typically the Basis team with the appropriate access Note: Import access + access to objects being imported is required for a successful import


Requirements & Best Practices

Requirements

Object Migration requires that each landscape is running the same version of software Object Migration also relies on supporting objects to be present Example: When migrating Workflows, all the dependent objects like Value Lists, Phase Configurations,

Workflow Definitions, Document Types should taken into account Ensure the context, cluster and directory configuration ids are same in both source and

target systems There are rare circular dependencies, in these cases rerunning the import usually does the

trick Generated OMA file should not be edited Make sure System property doc.numbering_table.token.deployment is set uniquely on

each landscape so no object collisions occur. Also make sure if production refreshes occur this property is reset.



Best Practices:

Object Migration should be performed from one direction. For example, once the data is migrated from Development to QA, it should not be migrated back to Dev system

There should be only one source system from where the object migration packages are created, typically Development system

By default, system creates “export.oma”. It is recommended to change the name to something more meaningful. Example: reports.oma, scripts.oma, etc.

For more details in Object Migration, refer to Software Change Management

section of the Solutions Operations Guide. This guide can be found in SMP

https://websmp109.sap-ag.de/eso






Recommended Naming Conventions:

Object Name Recommended Naming Convention

Query Definition Use Id starting with “CUSTOM-” or “Z-”

Report Use Id starting with “CUSTOM-” or “Z-”

Script Definition Use Id starting with “CUSTOM-” or “Z-”

Workflow Definition Use Id starting with “CUSTOM-” or “Z-”

Localized Resource Use bundle name “CUSTOM”


Limitations of Object Migration

Limitations of Object Migration:

Not a fully automated way to push changes. Some level of manual effort involved Changes imported into the target system cannot be undone Unlike SAP ERP, Sourcing does not have extensive built-in versioning control Business Documents (transactional data) cannot be migrated using OMA In some cases, inactive objects will be migrated and there is no option to filter

them out. Example: migration of extensions Note: New tool to delete inactive extensions will be available in Sourcing 9.0

Configuration Workbooks



Configuration Workbook is a technique that allows creating and managing configurations in Sourcing

Configuration Workbook contains a Configuration sheet (first sheet of the workbook) that controls the import process. In the Configuration sheet the user can specify what object gets in imported into the system

Each object is in a separate sheet in the workbook

A Configuration Workbook can be created from the Enterprise Deployment Workbook available in the Reference Guide To get a copy of the Enterprise Deployment Workbook, click on Reference Guide Additional

Information Section



• Create a new Configuration workbook from the Enterprise Deployment workbook • On the Configuration sheet, list the objects that you want to manage using the workbook • Each object listed in the Configuration sheet should have a corresponding sheet in the

workbook

Creation of Configuration Workbook

• Add your configurations to the workbook • Make sure tabs are sequenced correctly based on the object dependency • Determine what tabs to import

Add Configurations

• In the target system go to Setup System Administration tab Import • Import the Configuration Workbook. Note: There is no need to select the object type • Check import results for any errors

Import

Configuration Workbook – process



Show sample Configuration Workbook




If you are using workbooks to manage configurations for a certain object, continue to use

the same process till the end. Try not to make changes directly on the UI. Example: You are using workbooks for Value Lists, continue to use the workbook to add a new Value

List or to make updates to existing Value Lists

It is best to keep a separate configuration workbook for each module Example: Project_Configurations.xls, MA_Configurations.xls, etc.

Do not mix objects from different classes in the same tab Example: Do not have extensions from Projects and extensions from Master Agreements in the same

sheet of the workbook



Requirements & Best Practices….contd

Reimport of workbook is ok in most cases

Keep the workbooks simple with just the required sheets

Use Solution Manager or similar tools to keep track of the versions of the workbooks. Also if multiple people are working on the configurations, ensure they are working with the latest version of the workbook

Object Migration Vs Configuration

Workbooks


Object Migration Vs Configuration Workbooks

Object Mechanism used to

create it in source

system

Migration

Technique

Localized Resource Manual or Workbook

OMA or Workbook

Value List Type Workbook Workbook

Value List Value Workbook Workbook

Extension Workbook Workbook

Page Customization Manual or Workbook

OMA or Workbook

Document Types Manual or Workbook

OMA or Workbook

Workbench related Manual or Workbook

OMA or Workbook

Document Security Templates Manual OMA

When to use what? Some general guidelines…


Object Migration Vs Configuration Workbooks

Object Mechanism used to

create it in source

system

Migration

Technique

RFx Questions Library Manual or Workbook OMA or Workbook

Attachment Library Manual OMA

Information Library Manual OMA

Query Definitions Manual OMA

Reports Manual OMA

Query Groups Manual OMA

Script Definitions Manual OMA

Workflow Definitions Manual OMA

Security Profiles Manual OMA

When to use what? Some general guidelines…

Thank You!


No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information c ontained herein may be changed without pr ior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software c omponents of ot her software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix ar e trademarks or r egistered trademarks of IBM Corporation.

Linux is the registered trademark of Linus T orvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are ei ther trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.Oracle is a registered trademark of O racle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or r egistered trademarks of C itrix Systems, Inc.HTML, XML, XHTML and W3C are trademarks or registered trademarks of W 3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer and other SAP products and services mentioned herein as well as their respective logos are trademarks or r egistered trademarks of SAP AG in Germany and other countries..

© 2012 SAP AG. All rights reserved

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or r egistered trademarks of Business Objects Software Ltd. in the United States and in other countries.

All other product and service names mentioned are the t rademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may var y.

The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of SAP AG.This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice.

SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the ac curacy or c ompleteness of the information, text, graphics, links, or ot her items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.

SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of t hese materials. This limitation shall not apply in cases of intent or gross negligence.The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of h ot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.