Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Refreshing an SAP system for ERP 6.0

System refresh is the process of copying one SAP system to an existing system. During system refresh, interaction takes place between the source ERP system and the target ERP system. System refresh is executed on the target ERP system.

This section contains the following topics:

Before you begin

Ensure that you have completed the following activities before you request the service offering:

  • Create or update the SAP user DDIC in every client of the source and target system with the same password.
  • Create or update SAP user CLMADM in every client of the source and target system with the same password.
  • Increase the SAP profile parameter rdisp/max_wprun_time on the target SAP system to a suitably high value to ensure successful completion of the BDLS and user master import.
  • Maintain the SAP logical system pairs using the custom SAP transaction ZBDLSMAINTAIN.
  • Verify that there is an authorization role with access to the SAP transaction ZBMCVARIANT and activity VARIANT in authorization object ZBMC_SCAPA
  • Verify that there is an authorization role with access to the SAP transaction ZBDLSMAINTAIN and activity BDLS in authorization object ZBMC_SCAPA
  • Verify that there is an authorization role with access to the SAP transaction ZBMCPOSTPROCESSING and activity REPROC in authorization object ZBMC_SCAPA

Overview of the process for refreshing an SAP system

A system refresh is a combination of a number of activities that are performed in two phases. The first phase prepares the system for ERP refresh and the second phase is the actual refresh.  

Phase 1 - Prepare for ERP refresh

BMC Cloud Lifecycle Management:

  1. Installs Java connectors on the target system.
  2. Moves Advance Business Application Programming (ABAP) transports on the target system.
  3. Creates ABAP exports on the location provided by the end user.
  4. Moves the ABAP transports to the source system.

Phase 2 - Refresh ERP

BMC Cloud Lifecycle Management:

  1. Takes a backup of the source database.
  2. Archives log files and stops SAP on the target system.
  3. Restores the database taken from the source system to the target system.
  4. Imports the ABAP exports taken from the source system to the target system.
  5. Starts SAP.

To prepare the source and target systems for ERP refresh - Phase 1

  1. Log on to the Cloud Portal.
  2. Navigate to Service Instances.

  3. Click an existing ERP system in BMC Cloud Lifecycle Management.

    Tip

    Because system refresh is a post-deployment action, execute it from operator actions.

  4. In the toolbar, click Modify Actions Modify Actions icon_.jpg and select Refresh ERP System from the drop-down menu.

    1.jpg

    The SAP ERP 6.0 EHP5 ABAP based on NW 7.02 - RHEL/Oracle screen appears.

    2.jpg
  5. Select Prepare for ERP refresh and then click Next.

    The second section of the SAP ERP 6.0 EHP5 ABAP based on NW 7.02 - RHEL/Oracle screen appears.

    3.jpg

  6.  In the Parameters section, enter the appropriate values in the respective fields as described in the table below:

    Label 

    Parameter used

    Description

    Source SAP System Database Hostname 

    SAP_SOURCE_HOSTNAME

     • Enter the host name of the database host.

     • To find out the host name, enter the command hostname on the database host. 

    Source SAP System ID (SAPSID) 

    SAP_SOURCE_INST

     • This ID is the identifier for the Source SAP system.

    Target SAP System Client Number 

    TARGET_CLIENT_NUMBER

     • This number is the identifier for the client on the target system.

    Target SAP System ID (SAPSID) 

    SAP_INST 

    • This identifier applies to the SAP system.

    • The ID is unique throughout your organization.

    • The ID consists of exactly three alphanumeric characters.

    • The ID contains only uppercase letters and the first character must be a letter, not a number.

    • Reserved IDs cannot be used.

    ABAP Export Location 

    EXPORT_LOCATION 

    • This location stores the ABAP Exports.

    RFC user password 

    RFC_PASSWORD 

    • This is the RFC user password.

    DDIC user assword 

    DDIC_PASSWORD  

    • This is the DDIC user password.

  7. Click Next.

    The last section of the SAP ERP 6.0 EHP5 ABAP based on NW 7.02 - RHEL/Oracle screen appears.

    4.jpg

  8. After you verify the entered details on this screen, click Submit. 

    Note

    After you perform the steps for Phase 1, the SAP BASIS administrator needs to ensure that the ZBDLSMAINTAIN table is present on the target system. This check is very important before you proceed with Phase 2 of the system refresh.

To refresh an ERP system - Phase 2

  1. Log on to the Cloud Portal.
  2. Navigate to Service Instances.

  3. Click an existing ERP system in BMC Cloud Lifecycle Management.

    Tip

    Because system refresh is a post-deployment action, execute it from operator actions.

  4. In the toolbar, click Modify Actions Modify Actions icon_.jpgand select Refresh ERP System from the drop-down menu.

    1.jpg

    The SAP ERP 6.0 EHP5 ABAP based on NW 7.02 - RHEL/Oracle screen appears.

    2_1.jpg

  5. Select the Refresh ERP radio button and click Next.

    The second section of the SAP ERP 6.0 EHP5 ABAP based on NW 7.02 - RHEL/Oracle screen appears.

    3_1.jpg

  6. In the Parameters section, enter the appropriate values in the following mandatory fields:
    • Database Backup Host
    • Source SAP System Database Hostname
    • Source SAP System ID (SAPSID)
    • Target SAP System Client Number
    • Target SAP System ID (SAPSID)
    • ABAP Export Location
    • RFC user password
    • DDIC user password
  7. Click Next.

    The last section of the SAP ERP 6.0 EHP5 ABAP based on NW 7.02 - RHEL/Oracle screen appears.

    4_1.jpg
  8. Verify the information that you entered and click Submit. 
  9. Verify the status of the SAP transactions and programs executed as part of post SAP system refresh by executing SAP transaction ZBMCPOSTPROCESSING.

Limitations when refreshing an SAP system for ERP 6.0

The following limitations pertain to refreshing an SAP system for ERP 6.0:

  • The disk space required for taking the backup for the system refresh is not checked. BRBACKUP issues an error message, if the storage space for backup is insufficient.
  • The file system space requirement is not calculated or provisioned during the system refresh process.
  • The <SAPSID> is not validated for restricted <SID> .
  • There is no option to enter the Master password.
  • Postinstallation activities within SAP system need to be performed manually.
  • <SAPSID> cannot be validated on the input screen.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*