SAPTechno

Note 1389574 - SAP PRC 2.0: Switch upgrade to SAP ERP 6.0

Header
Version / Date 17 / 2011-10-24
Priority Recommendations/additional info
Category Upgrade information
Primary Component XX-PART-SRC SAP Product and REACH Compliance
Secondary Components

Summary
Symptom

You want to use the add-on

  • SAP REACH Compliance 1.1 Support Package 3 or higher (SRC 1.1)
  • SAP Product and REACH Compliance 2.0 (SPRC 2.0)


to perform an upgrade from Release mySAP ERP 2004 with ECC 5.0 (referred to as SAP ECC 500 below) to Release SAP ERP 6.0 with ECC 6.0 (referred to as SAP ECC 600 below).

Other terms

Upgrade, add-on, SAP Product and REACH Compliance, SAP Product and REACH Compliance 2.0, SPRC 2.0, TDAGBCA 110_500, TDAGBCA 200_500, TDAGBCA 200_600, TechniData basic components, SAPK-360EXINTDAGBCA
/TDAG/RCSC_LEGST

Reason and Prerequisites

SAP Product and REACH Compliance requires functions that are available with ERP 6.0 Enhancement Package 5. Since these functions are legal requirements, they will be available in lower releases only as of a specific Support Package. For this reason, the following Support Packages are a prerequisite for SAP Product and REACH Compliance:

  • SAP ERP 6.0 without an Enhancement Package EA-APPL Support Package 17
  • SAP ERP 6.0 Enhancement Package 2 EA-APPL Support Package 07
  • SAP ERP 6.0 Enhancement Package 3 EA-APPL Support Package 06
  • SAP ERP 6.0 Enhancement Package 4 EA-APPL Support Package 05
  • SAP ERP 6.0 Enhancement Package 5 EA-APPL without Support Package
  • SAP ERP 2004 EA-APPL Support Package 22



The following initial configurations are supported for the upgrade to ECC 600 without an Enhancement Package or with Enhancement Packages 2, 3, or 4:

  • SAP ECC 500 SAP REACH Compliance 2.0
  • SAP ECC 500 SAP REACH Compliance 1.1 Support Package 03


The following initial configurations are supported for the upgrade to ECC 600 Enhancement Package 5:

  • SAP ECC 500 SAP REACH Compliance 2.0 Support Package 02
  • SAP ECC 500 SAP REACH Compliance 1.1 Support Package 03


Solution

This note is updated regularly. Make sure that you are using the current version before you start the installation.

Contents
  1.  Change History
  2.  Requirements for the switch upgrade
  3.  Preparation for the upgrade
  4.  Additional information about the upgrade
  5.  Problems after the import
  6.  Postprocessing after the upgrade
  7.  Language support
  8.  Password
  9.  Additional information

1. Change History

Date Contents Short description
01.02.2010 All Initial creation
17.09.2010 3. Preparation         Manual steps for
                  for the upgrade       Web services
14.03.2011 2. Prerequisites Adding ERP 6.0 EHP5
28.03.2011 3. Preparation ACP package
for the upgrade
17.06.2011 3. Preparation ACP packages on Service
for the upgrade Marketplace
04.08.2011 3. Preparation Importing Support Packages
for the upgrade before the upgrade

2. Requirements for the switch upgrade
  • Delivery of SAP Product and REACH Compliance 2.0.

           The upgrade CD of SAP Product and REACH Compliance 2.0 is not automatically sent to all customers. Request the CD with material number 51038473 or download it from SAP Service Marketplace.

  • Required SAP and Add-On Release:
    • SAP ECC 500 and SAP Product and REACH Compliance 2.0
    • SAP ECC 500 and SAP Product and REACH Compliance 1.1 Support Package 03 or higher

           For ERP 6. 0 Enhancement Package 5 or higher, you must import Support Package SP02 for SAP Product and REACH Compliance 2.0 before the upgrade.

  • Add-on note

           If you want to upgrade your SAP release to ECC 600, the system automatically recognizes that an ABAP add-on SAP Product and REACH Compliance is installed and requests an additional CD with the upgrade package of the add-on. If this is available, the add-on SAP Product and REACH Compliance is also updated during the upgrade of the SAP release.

           Caution

           If you upgrade your SAP system to ECC 600 without importing the data of the upgrade CD with material number 51038473, the add-on SAP Product and REACH Compliance can no longer be executed after the upgrade. Since the status of the system is inconsistent in this case, we cannot assume any further responsibility.

  • Import the latest SPAM/SAINT update.

           Make sure that you have imported the latest SPAM/SAINT update into your system. If there is a more current version available on SAP Service Marketplace, import this SPAM/SAINT update.

  • Import the current versions of R3trans and tp.

           Make sure that you have imported the latest kernel version into your system. If there is a more current version available on SAP Service Marketplace, import the latest kernel.

  • Required PI_BASIS release

           In the upgrade to SAP ECC 600 with SAP Product and REACH Compliance 2.0, you must include a suitable PI_BASIS release in the upgrade. Note 555060 about component PI_BASIS provides an overview of all relevant notes.

  • Refer to the following notes before you start the upgrade:

           Information about the installation: 1389856
Release Strategy: 1398852
Add-on general conditions: 70228
Problems with transaction SAINT: 822380

           Required Support Packages
In addition to the Support Packages contained in SAP SAP ECC 600, you require the Support Packages of the following components for the upgrade, depending on to which Enhancement Package you are upgrading:

Component Release Support Package
EA-APPL 600 Support Package 17
or
EA-APPL 602 Support Package 07
or
EA-APPL 603 Support Package 06
or
EA-APPL 604 Support Package 05
or
EA-APPL 605 no Support Package

           If you have not yet installed the Support Packages of these components, you can download the relevant files from SAP Service Marketplace and include these in the upgrade. The files must exist in the directory <DIR_EPS_ROOT>/ before you start the UPLOAD_REQUEST preparation phase. For more information, see Note 83458.

  • Importing additional Component Support Packages

           The add-on SAP Product and REACH Compliance 2. 0 does not modify any objects of other components.

3. Preparation for the upgrade
  • If you want to install SAP Product and REACH Compliance 2.0 in combination with the upgrade to an ERP 6.0 Enhancement Package, install SAP Product and REACH Compliance before the upgrade. Note that the initial version (SP00) and the Support Packages cannot be processed in the same import queue in this case.
  • If you upgrade to ERP 6.0 Enhancement Package 5 or higher, import Support Package SP02 for SAP Product and REACH Compliance 2.0 first.
  • Request the CD of SAP Product and REACH Compliance 2.0 (material number 51038473) or download its contents from SAP Service Marketplace.
  • The add-on upgrade package can be unpacked automatically. In the phase CD UPLOAD_REQUEST, therefore, specify the directory in which you want to mount the add-on upgrade CD.
  • If you have downloaded the add-on upgrade package from SAP Service Marketplace, you must unpack it in the directory <DIR_EPS_ROOT>/in.
  • After unpacking, the file CSN0120061532_0040989.PAT must be in the directory <DIR_EPS_ROOT>/in at the latest after the phase UPLOAD_REQUEST.
  • If you upgrade to ERP 6.0 with an Enhancement Package, you also require the ACP package. For more information, refer to Note 1600792. You will also require this ACP package for future Support Packages.
  • For ERP 2004 and ERP 6.0, SAP Product and REACH Compliance 2.0 delivers technically different versions of the Web services for campaign statistics and project statistics. To prevent conflicts, remove the ERP 2004 versions of these services from the Internet Communication Framework (ICF) before the upgrade. To do this, proceed as follows:
    • Call transaction SICF.
    • Navigate to default_host/sap/bc/srt/rfc/TDAG.
    • Delete the entries for the Web services RCSWS_REG_PROJECTSTATUS and RCSWS_UEC_CAMP_OVERVIEW.

4. Additional information about the upgrade
  • Phase IS_SELECT
    Choose the upgrade type for the installed add-ons:
    TDAGBCA: "Upgrade with SAINT Package"
    PI_BASIS: "INST/UPG WITH STD CD" (or "Upgrade with Add-On CD" for a new PI_BASIS release )
  • Phase ADDONKEY_CHK
    The system requests you to enter a password. The required password is in the "Password" section.
  • Phase BIND_PATCH
    In this phase, the system displays which Support Packages are in the directory <DIR_EPS_ROOT>/in and can be included in the upgrade. Make sure that at least the Support Packages specified in section 2 "Requirements for the switch upgrade" are included.
7. Problems after the import
  • Generation error
    • Screen /TDAG/SAPLRCS_900 9040:  Generation error

                    This error occurs because there are generated dialogs for Customizing views in the customer number area. This error does not have any effects and you can ignore it.

    • Program /TDAG/SAPLCP_LB23, include /TDAG/LCP_LB23F03: Syntax error in line 001912.
      The data object 'IC_WWI_OHSTATUS' does not have a component called 'PROCESS'.

                    If the following generation error message occurs during the installation, apply SAP Note 937968 or use EA-APPL SP13.
8. Postprocessing after the upgrade

  • Activating SAP Enterprise Extensions in the Switch Framework

           The add-on SAP Product and REACH Compliance 2. 0 requires the Enterprise Extension EA-PLM. You must activate this if you have not already done so.  For more information, see Note 1049251.

  • Importing Support Packages after the upgrade

           The add-on SAP Product and REACH Compliance 2. 0 does not contain any modifications. Therefore, you can install further Support Packages of other components after the upgrade.

  • Delivery Customizing
    • Delivery Customizing is imported in client 000 and may need to be copied to other clients also.
    • Classes and characteristics are imported in client 000 and may need to be copied to the other clients.
9. Language support
  • SAP Product and REACH Compliance 2.0 supports the languages English and German.
  • All language-dependent parts for the languages English and German are contained in the installation package of the add-on. If the supported languages exist in your system, then all language-dependent parts of the add-on are automatically imported during the installation. You are not required to import a separate language transport.
  • If you install a new language in your system after you have installed SAP Product and REACH Compliance 2.0, you must manually ensure that the corresponding language-dependent part of the add-on contains this language.
10. Password
  • During the upgrade, the system requests you to enter a password. The password is: C6C648C394.

9. Additional information
  • After you install or upgrade the ABAP stack, you must install the Java stack.

           If you have already installed and set up ECC500 with SPRC 2. 0 before the upgrade, you can then skip the installation of the JAVA stack and working through the guide.

           If you already used SRC 1.1, you must perform the installation of the JAVA stack depending on the scenarios you used.

  • You require the following installation archives with the highest available patch level:
    • TDAGRCSINV00
    • TDAGRCSINVUI00
    • TDAGRCSMATASS00
    • TDAGRCSEPMGMT00
    • TDAGRCSREPORTING00
    • TDAGRCSCONVSVC00
    • TDAGRCSPC00
    • TDAGRCSBPCOLL00
  • Required components and Support Packages for the Java stack
    • SAP Netweaver CE 7.1 Application Server Java SP Stack 07 or
    • SAP Netweaver CE 7.1 Enhancement Package 1 Support Package 03

           If you use a central portal, you can integrate the processes of Product and REACH Compliance 2.0 there. For more information about this option, see Note 1541940.

  • For more information about the installation of the JAVA stack, see the guides. See Note 1386600.


Affected Releases
Software Component Release From Release To Release And subsequent
TDAGBCA200_600200_600200_600

Related Notes
1600792Installation/Switch-Upgrade with ERP 6.0 Enhancement Package
1541940Integration in existing portal landscape
1398852SAP PRC 2.0: Release strategy
1389856SAP PRC 2.0: Release information
1386600SAP PRC 2.0: Documents for installation and configuration
632429ADD-ON: Composite SAP note for upgrading or updating