Cbu Struc Win 080407

PUBLIC
Upgrade Guide
Customer-Based
Upgrade on Windows
Based on Support Releases 1 to 3 of SAP
Enterprise Core Component 6.00
Target Audience
n Customer-Based Upgrade Consultants

n Technology Consultants
Document version: 2.00 ‒ 04/07/2008

SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
T +49/18 05/34 34 34
F +49/18 05/34 34 20
www.sap.com
© Copyright 2008 SAP AG. All rights reserved. JavaScript is a registered trademark of Sun Microsystems,
Inc., used under license for technology invented and
No part of this publication may be reproduced or
implemented by Netscape.
transmitted in any form or for any purpose without the
SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge,
express permission of SAP AG. The information contained
ByDesign, SAP Business ByDesign, and other SAP products
herein may be changed without prior notice.
and services mentioned herein as well as their respective
Some software products marketed by SAP AG and its
logos are trademarks or registered trademarks of SAP AG in
distributors contain proprietary software components of
Germany and in several other countries all over the world.
other software vendors.
All other product and service names mentioned are the
No part of this publication may be reproduced or trademarks of their respective companies. Data contained
transmitted in any form or for any purpose without the in this document serves informational purposes only.
express permission of SAP AG. The information contained National product specifications may vary.
herein may be changed without prior notice. These materials are subject to change without notice.
Some software products marketed by SAP AG and its These materials are provided by SAP AG and its affiliated
distributors contain proprietary software components of companies ("SAP Group") for informational purposes
other software vendors. only, without representation or warranty of any kind, and
Microsoft, Windows, Excel, Outlook, and PowerPoint are SAP Group shall not be liable for errors or omissions with
registered trademarks of Microsoft Corporation. respect to the materials. The only warranties for SAP Group
IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, products and services are those that are set forth in the
MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, express warranty statements accompanying such products
pSeries, xSeries, zSeries, System i, System i5, System p, and services, if any. Nothing herein should be construed as
System p5, System x, System z, System z9, z/OS, AFP, constituting an additional warranty.
Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix,
This document was created using stylesheet 2006-12-31
i5/OS, POWER, POWER5, POWER5+, OpenPower and
(V5.1beta [= 6.0 for E3]) and XSLT processor SAXON 6.5.2
PowerPC are trademarks or registered trademarks of IBM
from Michael Kay (http://saxon.sf.net/), XSLT version 1.
Corporation.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader
Disclaimer
are either trademarks or registered trademarks of Adobe
Some components of this product are based on Java™. Any
Systems Incorporated in the United States and/or other
code change in these components may cause unpredictable
countries.
and severe malfunctions and is therefore expressly
Oracle is a registered trademark of Oracle Corporation.
prohibited, as is any decompilation of these components.
UNIX, X/Open, OSF/1, and Motif are registered trademarks
Any Java™ Source Code delivered with this product is
of the Open Group.
only to be used by SAP’s Support Services and may not be
Citrix, ICA, Program Neighborhood, MetaFrame,
modified or altered in any way.
WinFrame, VideoFrame, and MultiWin are trademarks or
registered trademarks of Citrix Systems, Inc.
Documentation in the SAP Service
HTML, XML, XHTML and W3C are trademarks or registered
Marketplace
trademarks of W3C®, World Wide Web Consortium,
You can find this document at the following address:
Massachusetts Institute of Technology.
https://service.sap.com/instguides
Java is a registered trademark of Sun Microsystems, Inc.
2/34 PUBLIC 04/07/2008

Typographic Conventions
Example Description
< > Angle brackets indicate that you replace these words or characters with appropriate
entries to make entries in the system, for example, “Enter your <User Name>”.
Arrows separating the parts of a navigation path, for example, menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the
documentation
Example Textual cross-references to an internet address, for example, http://www.sap.com
/example Quicklinks added to the internet address of a homepage to enable quick access to
specific content on the Web
123456 Hyperlink to an SAP Note, for example, SAP Note 123456
Example n Words or characters quoted from the screen. These include field labels, screen titles,
pushbutton labels, menu names, and menu options.
n Cross-references to other documentation or published works
Example n Output on the screen following a user action, for example, messages
n Source code or syntax quoted directly from a program
n File and directory names and their paths, names of variables and parameters, and
names of installation, upgrade, and database tools
EXAMPLE Technical names of system objects. These include report names, program names,
transaction codes, database table names, and key concepts of a programming language
when they are surrounded by body text, for example, SELECT and INCLUDE
EXAMPLE Keys on the keyboard
04/07/2008 PUBLIC 3/34

Document History
Caution
Before you start the upgrade, make sure that you have the latest version of this documents. You can
find the latest version at the following location: https://service.sap.com/instguides.
The following table provides an overview of the most important document changes.
Version Date Description
1.00 1/10/2007 First version

1.01 8/3/2007 Minor changes
2.00 4/7/2008 Version for Support Releases 1 to 3
4/34 PUBLIC 04/07/2008

Table of Contents
Chapter 1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . 7
Chapter 2 Naming Conventions . . . . . . . . . . . . . . . . . . . . 9
Chapter 3 Upgrade Process . . . . . . . . . . . . . . . . . . . . . . 11

3.1 Step 1: Creating a Copy of your Production System . . . . . . . . . . 11
3.2 Step 2: Performing a Standard Upgrade . . . . . . . . . . . . . . 11
3.3 Step 3: Completing the Copy . . . . . . . . . . . . . . . . . . 11
3.4 Step 4: Customer-Based Export . . . . . . . . . . . . . . . . . 11
3.4.1 Preparing the CBU Export . . . . . . . . . . . . . . . . . . . 11
3.4.2 Starting the CBU Export . . . . . . . . . . . . . . . . . . . . 12
3.4.3 Entering Initial Information . . . . . . . . . . . . . . . . . . 13
3.4.4 Export Phases . . . . . . . . . . . . . . . . . . . . . . . . 13
3.5 Step 5: Creating an Additional Copy of the Production System . . . . . . 19
3.6 Step 6: Performing the Customer-Based Upgrade . . . . . . . . . . . 19
3.6.1 PREPARE . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.6.1.1 Starting PREPARE . . . . . . . . . . . . . . . . . . . . . . 19
3.6.1.2 Performing CBU-Specific Phases and Actions During PREPARE . . . . . 20
3.6.2 CBU-Specific Phases and Actions During the Upgrade . . . . . . . . . 23
3.6.3 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . 24
Chapter 4 Post-Upgrade Activities . . . . . . . . . . . . . . . . . . . 25
Chapter A Appendix . . . . . . . . . . . . . . . . . . . . . . . . . 27
A.1 Complete Phase List for the Export . . . . . . . . . . . . . . . . 27
A.2 Example of a PIF (SORTCOMCD.LST) . . . . . . . . . . . . . . . 28
04/07/2008 PUBLIC 5/34

6/34 PUBLIC 04/07/2008
1 Overview
1 Overview
A Customer-Based Upgrade (CBU) is a special upgrade procedure that aims to significantly reduce
overall downtime when you upgrade an SAP production system.
This is achieved by including all customer-specific adjustments, which are normally made during
or after the upgrade:
n Importing Support Packages for the target release
n Importing add-on updates and installations (with SAINT) as well as add-on patches and Conflict
Resolution Transports (CRTs)
n Modification adjustment (transactions SPDD/SPAU)
n Adjustments to customer development objects
This customer-specific export removes the need for the following actions when you use a
Customer-Based Upgrade for the production system:
n Modification adjustment (transactions SPDD/SPAU)
n Import of Repository objects during downtime
n Import of customer transports after the upgrade (with the exception of Customizing)
A CBU also offers the following advantage:
Critical or long-running database modifications (such as DROP FIELD actions or creating indexes)
can be analyzed and avoided, if necessary.
In general, the process flow of a Customer-Based Upgrade allows you to plan the upgrade of the
production system more precisely.
This documentation tells you how to proceed with a CBU, and is particularly intended for consultants
who want to use a CBU to upgrade systems at SAP customer sites.
Prerequisites
You must meet the following prerequisites before you perform a Customer-Based Upgrade:
n You must be able to make a quick copy of the production system.
n After you have made the first copy of the production system, you must ‘freeze’ the Repository of
the production system. Any transports and corrections that you make in the production system
after you make this copy may be lost in the CBU upgrade and need to be repeated manually
at a later time.
n The hardware you use to upgrade the second copy should be the same as the hardware of the
production system. This is the only way you can reliably estimate the downtime needed for the
(platform-specific) upgrade procedure.
04/07/2008 PUBLIC 7/34

1 Overview
Process
1. Create a copy (C3x) of the production system (P3x).
2. Perform a standard upgrade of the copy (C3x C60).
3. Complete the copy with post-upgrade and other actions (C60):
n Perform a modification adjustment in the copied system, or copy the modifications from
the development system
n Import further Add-On Installation or Upgrade Packages and Support Packages, if needed
n Complete the export system by importing customer developments
4. Run the CBU export on the copy (C60).
5. Create an additional copy (C3x’) of the production system.
6. Test the CBU Export result by performing a Customer-Based Upgrade of the second copy of
the production system C3x’ C60’)
7. Verify the system (C60’) after the upgrade. 8. Perform a Customer-Based Upgrade of the
production system P3x P60).
8/34 PUBLIC 04/07/2008

2 Naming Conventions
2 Naming Conventions
Export Directory
This is the directory that is used for the export phase.
This directory is referred to as <cbuexpdir> in this document.
Required freespace: 100 MB
Reference Directory
This is the directory that is created during the CBU export and that contains all the files that are
replaced by or added to the Customer-Based Upgrade.
This directory is referred to as <refdir> in this document.
CBU Tools Directory

This is the directory containing the CBU specific tools. In this document the directory is referred to
as <cbucd>.
Cross-Client Transport (Single Change Request)

The cross-client transport contains all cross-client objects that are included as a single transport
request in the Customer-Based Upgrade of the production system.
The default name is SAPKUUI700.
This transport has to be selected as Single Change Request in the BIND_PATCH phase of the Customer-Based
Upgrade. It will also be automatically used as modification adjustment transport.
Client-Specific Transport
The client-specific transport contains all client-specific objects for the Customer-Based Upgrade.
The default name is SAPKUUD700.
This transport has to be imported manually into the production system in the production client
after the Customer-Based Upgrade.
04/07/2008 PUBLIC 9/34

This page is intentionally left blank.
3 Upgrade Process
3 Upgrade Process
3.1 Step 1: Creating a Copy of your Production System
Create a copy of your production system.
3.2 Step 2: Performing a Standard Upgrade
Refer to the relevant Upgrade Guide:

n Upgrade Guide ‒ SAP ECC 6.00 SR1
3.3 Step 3: Completing the Copy
Complete the copy with post-upgrade and other actions:

n Perform a modification adjustment in the copied system, or copy the modifications from the
development system.
Make sure that transaction SPAU has been completed.
n Complete the export system by importing
l further Support Packages and Add-On Installation or Upgrade Packages (SAINT), if needed
l the customer developments
n Make sure that all corrections and transport requests are released.
3.4 Step 4: Customer-Based Export
3.4.1 Preparing the CBU Export
Caution
Before you start the export, read SAP Note 997221.
This SAP Note contains current information about the CBU Export and the Customer-Based
04/07/2008 PUBLIC 11/34

3 Upgrade Process
Upgrade.
Prerequisites
Caution
In the export phase INIT_CBU you must enter a CBU keyword that is specific for your
Customer-Based Upgrade.
n To get this keyword, create an error message in SAP Support Portal and assign it to the component
XX-PROJ-CBU. You must include the following in this error message:
l the name of the system used for the upgrade of the copy and the export
l the name of the host used for the upgrade of the copy and the export
l the name of your certified CBU consultant
Your CBU consultant then receives your CBU keyword by mail from SAP.
n Perl version 5.x or higher has been installed and can be accessed as perl using the search path.
Procedure
1. Create the CBU tools directory <cbucd> .
2. Unpack the CBU700_<product>.SAR.archive:
n cd <cbucd>.
n SAPCAR –xvf CBU700_<product>.SAR.
3. Create the export directory <cbuexpdir>.
This directory must be empty.
4. Create the reference directory <refdir>.
This directory stores all files that are copied to the upgrade directory of the target system. The
directory must be empty with approximately 100 MB freespace.
5. Set the following in the instance profile:
n DIR_PUT = <cbuexpdir>
n If necessary, restart the SAP System.
3.4.2 Starting the CBU Export
1. Start the export with the following commands:

a) cd <cbuexpdir>
b) perl <cbucd>\CBUEXPORT
The script unpacks the archives CBUEXE700.SAR and CBUMISC700.SAR and starts SAPup.
2. If necessary, restart SAPup:
a) cd <cbuexpdir>\exe
12/34 PUBLIC 04/07/2008

3 Upgrade Process
b) SAPup CBU_EXP upgdir=<cbuexpdir>
Caution
If you use the Upgrade Assistant to start SAPup, choose Administrator Start SAPup with options and
enter CBU_EXP.
For more information about the Upgrade Assistant, refer to the relevant upgrade guide.
3.4.3 Entering Initial Information
Enter the following initial information:

n Operation Mode (SERVER/SCROLL)
n Name of the SAP system (SAPSID)
n Database type
3.4.4 Export Phases
INITPUT
Enter the following information:
n SAP system ID
n SAP system host
n Instance number
n Kernel path
n Database ID
n Database host
n DB password (ORACLE)
n DDIC password
n Background host
DBCHK
This phase determines DB and SAP version.
INIT_CBU
n The path to the standard upgrade directory
04/07/2008 PUBLIC 13/34

3 Upgrade Process
Caution
The directory that you have to specify here must at least contain the entire contents of the ’bin’
and ’buffer’ upgrade subdirectories.
n Path to the CBU reference directory (<refdir>)

n Your CBU keyword
REQ_READNOTE
Before you start the export, read SAP Note 997221 thoroughly. It contains important additional
information about the CBU Export.
RFCCHK
This phase tests the RFC connection.
SCRIPT_TST_UVERS
This phase checks the upgrade status.
The upgrade must have been completed successfully.
SCRIPT_TST_PATCH
This phase checks the Support Package status.
No terminated Support Packages must exist for the current release.
LOCKEU_CBU
This phase locks the Workbench.
LOCKSYS_CBU
This phase locks the system.
COMPINFO_CBU
This phase gets information about current component versions and package levels.
UNPACK_REF
This phase unpacks the .SAR archive CBUREF700.CAR into the reference directory <refdir>.
TOOLIMP_CBU
This phase imports the CBU tools for the export.
REQ_EXP_TR
Caution
The merge process in phase REQ_EXP_TR is the most sensitive part of the whole CBU process.
Therefore, read the following information thoroughly.
14/34 PUBLIC 04/07/2008

3 Upgrade Process
REQ_EXP_TR prompts you to merge the transports and create the single change request (cross-client
transport) and the client-specific transport with program RDDPUT49.
RDDPUT49
The program RDDPUT49 is used in the CBU export process to collect all objects that have been
modified in the copy system after the upgrade.
To find these objects, the program scans all transports and correction requests within a given date
and time range, and collects the objects contained in these transport requests. Excluded from this
scan are only transport requests starting with SAPK, which are the regular SAP delivery transports
and are of no interest here.
Caution
The program will only scan transports and correction requests that have been released.
The gathered objects are divided into three transport requests:

n The cross-client transport has the default name SAPKUUI700 and is included as a single change
request in the upgrade of the production system.
n The client- specific transport has the default name SAPKUUD700 and has to be imported in the
production system into the production client after the production upgrade.
n The third transport has the default name SAPKUUX700 and gathers objects that have been
excluded from the cross-client transport and the client-specific transport (see below). This
transport is usually empty.
Figure 1: Transport Request Merge Screen
04/07/2008 PUBLIC 15/34

3 Upgrade Process
The selection screen has been completely preset. It contains the names for the transport requests,
short texts for the transport requests, and the time range for the scan.
Choose Execute for each transport request to switch the corresponding merge run on and off. By
default, all merges are run.
The lower date of the time range is preset with the time at which the Repository switch took place
during the last upgrade. This time is necessary to gather all possible modification adjustment
transports that were integrated into that upgrade.
The upper time limit is set to now
Caution
Before changing these fields contact the SAP Development Support. Do not change them on
your own.
As a result of the program, two transport requests named SAPKUUI700 and SAPKUUD700 are
created.
The third transport request named SAPKUUX700 contains the rejected objects from the scan if
any are found.
Rejected objects are:
PGMID OBJECT OBJ_NAME
R3TR XPRA
R3TR TDAT PDST_BASE
R3TR TDAT PDST
R3TR TDAT PDWS_BASE
R3TR TDAT PWDS
These objects will all be placed in the third transport if they are found within transports in the
scan range.
Our recommendation is to decide together with the customer whether to transport these objects
into the production system. If so, export this transport from the production client and also import
it after the production upgrade into the production client.
Note that the TDAT entries require special export preparation (that is why they were excluded
from the standard transports). For more information, see SAP Note 138411.
After the program has been executed, a detailed analysis and statistics log is displayed. Check
this log for any error messages. You can find the log files in the <cbuexpdir>/log directory of
the system under SAPKUU<I/D/X>700<SID>.
16/34 PUBLIC 04/07/2008

3 Upgrade Process
Note
The merge process is the most sensitive part of the whole CBU process. SAP has made the process
as secure as possible, but always checks the merge logs for possible errors.
If there is more than one client from which you need to export, you should duplicate the client-
specific transport by re-running program RDDPUT49 for each further client with the following
(adapted) parameter settings:
l Deselect the Execute Step checkbox for the SAPKUUI700 and SAPKUUX700 requests.
l Change the request name SAPKUUD700 to, for example, SAPKUUD70<n> (with <n> being a
consecutive number different for each client).
Actions after RDDPUT49
After you have merged the transports with program RDDPUT49, proceed as follows:
1. Log on as user <sapsid>adm.
2. cd <cbuexpdir>\bin
tp pf=DEFAULT.TPP export SAPKUUI700 -s <SAPSID> u1
3. Export the client-specific transport(s):
cd <cbuexpdir>\bin
tp pf=DEFAULT.TPP export SAPKUUD700 client=<client> -s <SAPSID> u1
Repeat this step for each further client-specific transport, if there are any.
4. Export the XPRAs and workflow objects:
If a transport request with XPRAs and workflow objects (SAPKUUX700) has been created,
export it and copy the data and cofiles to the corresponding subdirectories of the reference
directory (<refdir>).
Note
If the export was successful, you can ignore the tp return code 40 (no import will follow).
CBU_GETTA
n Cross-client transport request (default: SAPKUUI700)
n Client-specific transport request (default: SAPKUUD700)
EXEC_PLMODT
Replaces the following in the files <cbuexpdir>\bin\CBUCPREF.LST and <refdir>\bin\CBUFIL1.LST:
n <CLICOF> with the name of the cofile
n <CLIDATR> with the name of the data file
n <CLIDATD> with the name of the ADO data file (if it exists) of the cross-client transport
04/07/2008 PUBLIC 17/34

3 Upgrade Process
JOB_PIFGEN
The report RSCBUGENPI generates the Patch Integration Files (PIF) SORTCOMCD.LST and
INDEPPROD.LST.
The imported components, that is, Support Packages, add-ons, plug-ins, Add-On Support Packages,
or CRTs, and the import sequence of the corresponding requests are described in these files. The
components and requests described are those included in the upgrade and those installed after the
upgrade (using transaction SAINT, for example).
The PIF files are included in the Customer-Based Upgrade. They ensure that the components you
want to import or update are complete and consistent.
EXEC_CPPIF
The Patch Integration Files are copied to the reference directory for inclusion in the Customer-Based
Upgrade.
INTEG_CHK
This phase checks the validity of the generated Patch Integration Files.
EXEC_R3TRANS_EXP
R3trans exports modification status information.
INFO_STORE
This phase creates the control file CBUINFO.CTL with the following information:
n Included Support Packages (PAT03)
n Name of the cross-client transport (single change request)
n Name of the client-specific transport (single change request)
EXEC_CPYREF
This phase copies the relevant data created during the export to the reference directory.
EXEC_CBUPRD
This phase creates the CAR archive CBUPRD.SAR.
UNLOCKSYS_CBU
This phase unlocks the SAP system.
UNLOCKEU_CBU
This phase unlocks the ABAP Workbench.
REQ_FINAL_MSG
This phase displays final CBU information. Do not forget to execute the following actions (for a
detailed description, see below):
18/34 PUBLIC 04/07/2008

3 Upgrade Process
3.5 Step 5: Creating an Additional Copy of the Production System
n When upgrading the target system (phase INIT_CBU), enter <refdir> as the reference directory.
n When upgrading the target system, select the cross-client transport request SAPKUUI700 as Single
Change Request.
END
EXIT
3.5 Step 5: Creating an Additional Copy of the Production

System
Create an additional copy of the production system.
3.6 Step 6: Performing the Customer-Based Upgrade

In this step you perform the Customer-Based Upgrade using the export created in step 4. This
requires the following actions:
n CBU PREPARE
n Customer-based upgrade
3.6.1 PREPARE
3.6.1.1 Starting PREPARE
You can use PREPARE in scroll mode or with the Upgrade Assistant. We recommend using the
Upgrade Assistant to execute PREPARE. To copy and unpack it from the CD, you must start PREPARE
once directly from the CD.
Prerequisites
You have met the requirements for PREPARE.
Windows NT
1. Make sure that the database and the SAP system have been started.
2. Insert the Upgrade Master CD.
3. Log on as user <SAPSID>ADM to the host on which the central instance is running.
4. In the Windows NT Explorer, change to subdirectory NT\I386 (or NT\ALPHA) on the CD drive.
5. Start PREPARE.EXE.
04/07/2008 PUBLIC 19/34

3 Upgrade Process
The tool creates directory \USR\SAP\PUT\UA, into which the Upgrade Assistant is unpacked.
6. Exit SAPup before choosing the PREPARE modules, as shown in the following dialogue:
#################################################################
SAPup> The following options are available:
select: Display screen for selecting PREPARE modules
status: Display the statuses of the PREPARE modules
exit: Exit PREPARE
help: Getting help about PREPARE
- “select”
- “status”
- “exit”
Enter one of these options or “help” [select] := exit
###############################################################
7. Rename fileSAPup.exe in directory<upgrade directory>\exe\SAPup.exe (for example, in
SAPup.exe.std).
8. Unpack the SAPCAR archive CBUPRD.SAR from the CBU reference directory to the upgrade
directory:
cd <upgrade directory>
SAPCAR -xvf <refdir>\CBUPRD.SAR
9. Check whether the correct SAPup is used with SAPup -v or SAPup -V .
The output must be: ... for Customer-Based Upgrade.
10. Restart SAPup as follows (or use the Upgrade Assistant):
cd <upgrade directory>\exe
SAPup check
As a result, the following will be displayed:
SAP UPGRADE CONTROL PROGRAM
>>> Customer-Based Upgrade <<<
3.6.1.2 Performing CBU-Specific Phases and Actions During

PREPARE
Note
Note that new phases during PREPARE are marked as such. The other phases listed below are standard
phases that were modified for the CBU PREPARE.
20/34 PUBLIC 04/07/2008

3 Upgrade Process
Parameter Input Module
REQ_READNOTE (new phase)
Caution
Before you start the export, you must read SAP Note 997221.
SAP Note 997221 contains current information about the Customer-Based Upgrade and complements
the other standard Upgrade Notes.
INIT_CBU (new phase)

Enter the CBU reference directory <refdir>.
Import Module
CPYFIL0_CBU (new phase)

This phase prepares the data copy from the reference directory.
EXEC_CPYFIL1_CBU (new phase)

This phase copies the data from the reference directory <refdir> to the upgrade directory <upgrade
directory>.
INFO_STORE_READ (new phase)

This phase reads the CBU control file CBUINFO.CTL that was created during the export.
It reads the following information:
n Name of the cross-client transport (single change request)
n Name of the client-specific transport
n Support Packages imported into the export system
Extension Module (Read CD Module)
JOB_CBUPIFCHK (new phase)

The report RSCBUPRP checks the PIF file and uploads the Support Package requests that you want
to import.
IS_SELECT
In this phase you must make the same selection as when you upgraded the export system.
EXEC_CPYFIL3_CBU (new phase)

This phase copies additional files from the reference directory <refdir> to the upgrade directory
<upgrade directory>.
04/07/2008 PUBLIC 21/34

3 Upgrade Process
BIND_PATCH
You must select all Support Packages that were imported into the export system (at the time of
the export).
For the Customer-Based Upgrade, the Patch Integration Files are used that were created during the
export. At the beginning of this phase, the following dialog box appears which contains the valid
product description for this upgrade. Note that you must use the procedure described in the Standard
Upgrade Guide, even though a PIF is being used. There is an example of a PIF in the appendix.
Figure 2: Support Package Level Selection Screen
You must also select the single change request (cross-client transport: SAPKUUI700 that was created
during the export.
22/34 PUBLIC 04/07/2008

3 Upgrade Process
Figure 3: Single Change Request Screen
ADJUSTPRP
As the cross-client transport will be used automatically as modification adjustment transport request,
this phase is not running during the CBU upgrade.
INTEG_PATCH
This phase checks whether the product description of the PIF file concerning the current system
status and the selection in the phases IS_SELECT and BIND_PATCH is consistent. If an error occurs that
indicates an inconsistency, contact SAP Support.
3.6.2 CBU-Specific Phases and Actions During the Upgrade
Note
Note that new phases during the Customer-Based Upgrade are marked as such. The other phases
listed below are standard phases that were modified for the CBU
INITSUBST
This phase selects the strategy downtime minimized.
EXEC_CPDEFTPP (new phase)

This phase copies the adapted default transport parameter file.
04/07/2008 PUBLIC 23/34

3 Upgrade Process
JOB_CBUEPI (new phase)

This phase updates the status of the components or requests that have been imported and that were
not processed in the phase TR_PATCH_STATUS_UPGRADE.
REQFINCBU (new phase)

Remember to import any other transports that have been created as part of the CBU export:
n client-specific objects (SAPKUUD700)
n XPRAs, if they exist
n workflow objects, if they exist
3.6.3 Troubleshooting
Read SAP Note 997221 before creating your error message. This Note contains important information
about the CBU Export and the Customer-Based Upgrade.
If any problems occur during a Customer-Based Upgrade that you cannot solve, create an error
message in SAP Support Portal and assign it to the component:
n XX-PROJ-CBU for CBU Export problems
n BC-UPG for general upgrade problems (indicate that you are performing a CBU)
24/34 PUBLIC 04/07/2008

4 Post-Upgrade Activities
4 Post-Upgrade Activities
Importing Additional Transports

In addition to the standard post-upgrade activities, you must import any other transports that were
merged and exported during the export:
n Client-specific objects (SAPKUUD70<n>) The client-specific transport has to be imported
manually after the Customer-Based Upgrade.
n XPRAs and workflow objects (SAPKUUX700) You may also have transports with XPRAs or
workflow objects. These transports have to be imported manually as a client-specific transport
after the Customer-Based Upgrade.
04/07/2008 PUBLIC 25/34

A Appendix
A Appendix
A.1 Complete Phase List for the Export
Phase Duration (%) Actions by the Export Log User Actions

BEGIN <1% Checks upgrade
directory
INITPUT --- Enter parameters
DBCHK <1% Determines DB and
SAP version
INIT_CBU --- Enter your CBU
keyword and
parameters
EXEC_CPYUPG <1% Copies files from
the standard
upgrade directory
CBUCPUPG.LOG
REQ_READNOTE --- Read SAP Note 997221

RFCCHK <1% Tests the RFC
connection
RFCCHK.LOG
SCRIPT_TST_UVERS <1% Checks the upgrade

status SCRIPTCHKU.LOG
UVERS_U.LOG
SCRIPT_TST_PATCH <1% Checks the Support SCRIPTCHKP.LOG

Package status PATCHTST.LOG
LOCKEU_CBU <1% Locks the Workbench LOCKEUPR.LOG
LOCKSYS_CBU <1% Locks the system LOCKSYPR.LOG
COMPINFO_CBU <1% Gets component COMPINFOCBU.LOG

information
UNPACK_REF <1% Unpacks the UNPACKR.LOG
CAR archive
CBUREF<REL>.CAR
into <refdir>
TOOLIMP_CBU <1% Imports the CBU tools TOOLIMPU.ELG
for the export
REQ_EXP_TR --- Merge process Run RDDPUT49
04/07/2008 PUBLIC 27/34

A Appendix
A.2 Example of a PIF (SORTCOMCD.LST)
Phase Duration (%) Actions by the Export Log User Actions

CBU_GETTA --- Enter the name of the
cross-client transport
(SAPKUUI700)
and the client-
specific transport
(SAPKUUD700)
EXEC_PLMODT <1% Replaces contents CBUFIL1.LSRPLMODT.LOG
in the files
<cbuexpdir>\bin\CBUCPREF.LST
and <refdir>\bin\
JOB_PIFGEN <1% Generates the PIF files PIFGEN.ELG
PIFGEN.LOG
RSCBUGENPI.<SID>
EXEC_CPPIF <1% Copies the PIF files to CBUCPPIF.LOG

the reference directory
INTEG_CHK <1% Checks the validity of INTGPTCH.LOG
the generated PIF files
EXEC_R3TRANS_EXP 10 % R3trans export of R3TEXP.LOG
modification status
information
INFO_STORE <1% Creates the control CBUINFO.CTL
file INFOW.LOG
EXEC_CPYREF <1% Copies the relevant CPYREF.LOG

data created during
the export to the
reference directory
EXEC_CBUPRD <1% Creates the CAR CBUPRD.CAR
archive CBUPRD.LOG
UNLOCKSYS_CBU <1% Unlocks the SAP

System
UNLOCKEU_CBU <1% Unlocks the
Workbench
REQ_FINAL_MSG --- Displays final CBU
information
END ---
EXIT ---
28/34 PUBLIC 04/07/2008

A Appendix
# generated PIF-file for CBU; Basis Upgrade 40B /470

#STARTRELEASE 40B
#ENDRELEASE 470
# SID: QO2
# DATE: 20030721 124536
# <Id> "CBUGEN QO2 470 " <Version> 1
#
<Description>
# Upgrade PI_BASIS 2002_2_620.
SAPKINB87D
SAPKINB87F
SAPKINB87K
SAPKINB87M
SAPKINB87O
SAPKINB87R
SAPKINB87T
SAPKINB87W
SAPKINB87X
SAPKINB87Z
# Basis Support Package 18 for 6.20
SAPKB62018
SAPKB62019
# Upgrade PI 2002_2_470.
SAPKIND87D
SAPKIND87F
SAPKIND87K
SAPKIND87M
SAPKIND87O
SAPKIND87R
SAPKIND87T
SAPKIND87W
SAPKIND87X
SAPKIND87Z
# ABA Support Package 18 for 6.20
SAPKA62018
# PI_BASIS 2002_2_620: patch 0001
SAPKIPYG51
# PI_BASIS 2002_2_620: patch 0002
SAPKIPYG52
04/07/2008 PUBLIC 29/34

A Appendix
# PI 2002_2_470: patch 0001

SAPKIPZG51
# PI 2002_2_470: patch 0002
SAPKIPZG52
# Upgrade IS-M 471
SAPKISP86D
SAPKISP86F
SAPKISP86O
SAPKISP86R
SAPKISP86K
SAPKISP86M
SAPKISP86T
SAPKISP86W
SAPKISP86X
SAPKISP86Z
SAPKISP861
SAPKISP862
SAPKISP863
SAPKISP864
SAPKISP865
SAPKISP866
SAPKISP867
SAPKISP868
SAPKISP869
SAPKA62019
SAPKA62020
SAPKA62021
SAPKB62020
# SP 07 for SAP_APPL 4.70
SAPKH47007
SAPKH47008
# IS-M 471: patch 0001, CRT for SAPKH47007 - 08
SAPKIPPM01
# SPAM/SAINT Update - Version 620/0012
SAPKD62012
30/34 PUBLIC 04/07/2008

A Appendix

SAPKH47009
SAPKH47010
# IS-M 471: patch 0002, CRT for SAPKH47009 - 10
SAPKIPPM02
SAPKH47011
# IS-M 471: patch 0003, CRT for SAPKH47011
SAPKIPPM03
# PI_BASIS 2002_2_620: patch 0003
SAPKIPYG53
# PI_BASIS 2002_2_620: patch 0004
SAPKIPYG54
# PI 2002_2_470: patch 0003
SAPKIPZG53
# PI 2002_2_470: patch 0004
SAPKIPZG54
# PI 2002_2_470: patch 0005
SAPKIPZG55
SAPKA62022
SAPKA62023
SAPKA62024
SAPKA62025
SAPKA62026
SAPKB62021
SAPKB62022
SAPKB62023
SAPKB62024
SAPKB62025
04/07/2008 PUBLIC 31/34

A Appendix
# PI_BASIS 2003_1_620: Add-On Delta Upgrade

SAPKINB97B
# PI_BASIS 2003_1_620: patch 0001
SAPKIPYH51
# PI_BASIS 2003_1_620: patch 0002
SAPKIPYH52
# Product description AFTER UPGRADE
<Product> COP_SAP_BASIS:25 COP_SAP_ABA:26 COP_SAP_APPL:11 COP_SAP_HR:10
AOP_EA-APPL:6 AOP_EA-FINSERV:6 AOP_EA-GLTRADE:6 AOP_EA-HR:10 AOP_EA-IPPE:6
AOP_EA-PS:6 AOP_EA-RETAIL:6 AOP_IS-M:1 AOP_PDB-ADD-ON:0 AOP_PI:2 AOP_PI_BASIS:2
AOP_WP-PI:0 EA-APPL110 EA-FINSERV110 EA-GLTRADE110 EA-HR110 EA-IPPE110 EA-PS110
EA-RETAIL110 IS-M471 PDB-ADD-ON210_471 PI2002_2_470 PI_BASIS2002_2_620 WP-PI211_40B
# Product description BEFORE EXPORT (Add-on patch levels based on release AFTER UPGRADE)
<Product> COP_SAP_BASIS:25 COP_SAP_ABA:26 COP_SAP_APPL:11 COP_SAP_HR:10
AOP_EA-APPL:11 AOP_EA-FINSERV:11 AOP_EA-GLTRADE:11 AOP_EA-HR:10 AOP_EA-IPPE:10
AOP_EA-PS:11 AOP_EA-RETAIL:11 AOP_IS-M:3 AOP_PDB-ADD-ON:0 AOP_PI:5 AOP_PI_BASIS:4
AOP_WP-PI:0 EA-APPL110 EA-FINSERV110 EA-GLTRADE110 EA-HR110 EA-IPPE110 EA-PS110
EA-RETAIL110 IS-M471 PDB-ADD-ON210_471 PI2002_2_470 PI_BASIS2002_2_620 WP-PI211_40B
#
#UPLOAD:SAPKD62012 :PAT
#UPLOAD:SAPKIPPM02 :CRT
#UPLOAD:SAPKIPPM03 :CRT
#UPLOAD:SAPKIPYG53 :AOP
#UPLOAD:SAPKIPYG54 :AOP
#UPLOAD:SAPKIPZG53 :AOP
#UPLOAD:SAPKINB97B :AOU
#UPLOAD:SAPKIPYH51 :AOP
#UPLOAD:SAPKIPYH52 :AOP
#
#EPILOGTX:PI_BASIS 2003_1_620 : Add-On Delta Upgrade
#EPILOGUE:PI_BASIS :2003_1_620 :SAPKINB97B
#
32/34 PUBLIC 04/07/2008

SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
T +49/18 05/34 34 34
F +49/18 05/34 34 20
www.sap.com
© Copyright 2008 SAP AG. All rights reserved.

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 contained herein may be
changed without prior notice.

Cbu Struc Win 080407

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Cbu Struc Win 080407

Hochgeladen von

Copyright:

Verfügbare Formate

PUBLIC

n Customer-Based Upgrade Consultants

Document version: 2.00 ‒ 04/07/2008

2/34 PUBLIC 04/07/2008

04/07/2008 PUBLIC 3/34

1.00 1/10/2007 First version

4/34 PUBLIC 04/07/2008

Chapter 2 Naming Conventions . . . . . . . . . . . . . . . . . . . . 9

Chapter 3 Upgrade Process . . . . . . . . . . . . . . . . . . . . . . 11

Chapter 4 Post-Upgrade Activities . . . . . . . . . . . . . . . . . . . 25

04/07/2008 PUBLIC 5/34

04/07/2008 PUBLIC 7/34

8/34 PUBLIC 04/07/2008

CBU Tools Directory

Cross-Client Transport (Single Change Request)

04/07/2008 PUBLIC 9/34

3.1 Step 1: Creating a Copy of your Production System

Create a copy of your production system.

3.2 Step 2: Performing a Standard Upgrade

Refer to the relevant Upgrade Guide:

3.3 Step 3: Completing the Copy

Complete the copy with post-upgrade and other actions:

3.4 Step 4: Customer-Based Export

3.4.1 Preparing the CBU Export

04/07/2008 PUBLIC 11/34

3.4.2 Starting the CBU Export

1. Start the export with the following commands:

12/34 PUBLIC 04/07/2008

b) SAPup CBU_EXP upgdir=<cbuexpdir>

3.4.3 Entering Initial Information

Enter the following initial information:

3.4.4 Export Phases

04/07/2008 PUBLIC 13/34

n Path to the CBU reference directory (<refdir>)

14/34 PUBLIC 04/07/2008

The gathered objects are divided into three transport requests:

Figure 1: Transport Request Merge Screen

04/07/2008 PUBLIC 15/34

16/34 PUBLIC 04/07/2008

04/07/2008 PUBLIC 17/34

18/34 PUBLIC 04/07/2008

3.5 Step 5: Creating an Additional Copy of the Production

Create an additional copy of the production system.

3.6 Step 6: Performing the Customer-Based Upgrade

3.6.1.1 Starting PREPARE

04/07/2008 PUBLIC 19/34

3.6.1.2 Performing CBU-Specific Phases and Actions During

20/34 PUBLIC 04/07/2008

Parameter Input Module

REQ_READNOTE (new phase)

INIT_CBU (new phase)

CPYFIL0_CBU (new phase)

EXEC_CPYFIL1_CBU (new phase)

INFO_STORE_READ (new phase)

Extension Module (Read CD Module)

JOB_CBUPIFCHK (new phase)

EXEC_CPYFIL3_CBU (new phase)

04/07/2008 PUBLIC 21/34

Figure 2: Support Package Level Selection Screen

22/34 PUBLIC 04/07/2008

Figure 3: Single Change Request Screen

3.6.2 CBU-Specific Phases and Actions During the Upgrade

EXEC_CPDEFTPP (new phase)

04/07/2008 PUBLIC 23/34