Plan and prepare  the system copy procedure. Check that all required information is available  and that the copy strategy is complete. Prepare or check the target hardware  and software environment.

⚠  This procedure requires exclusive access to all systems for a brief period.

Generic

1.1 – Get required  documentation

Plan and prepare the system copy procedure. Check that all required information is available and that the copy strategy is complete. Prepare or check the target hardware and software environment.

1.2 – Determine a  clear copy strategy

Several copy  scenarios are possible. To find the scenario closest to your current  requirement refer to SAP Note 886102 which specifies the necessary steps.

1.3 – Build up  desired initial state of source system

If desired, apply any lacking changes to the source systems which should be present in the  target systems as well. This step can spare you from applying required modifications twice.

1.4 – Prepare the hardware and environment for the target systems

Before you can begin with the practical tasks of installing or copying the components of the target landscape, you need to plan the setup of the landscape and prepare the environment accordingly.

1.5 – Check the hardware and environment for the target systems

1.6 – Inform the user community

BW Specific

From SAP Note 886102

Scenario A2 – Chosen on the basis of the current customer brief

You want to copy the entire environment including all systems connected to the BW source  system (the entire system group). You want to create a new non-productive  system group or refresh an existing non-productive system group [PRD to NPS, installation or refresh]. If the whole system group is refreshed, the  installation and refresh scenario do not differ since all systems are overwritten.

CRM  Specific

If you are doing a refresh of an already existing CRM landscape, your existing CRM components  can be reconnected to the new copied CRM server. Please check note 543841 to determine the correct version of the CRM components that match your CRM support package.

1.1 – Get required documentation

  • 564435 Additional information on CRM System copy
  • 543841 to determine the correct version of the CRM components that match your CRM support package.

1.2 – Determine a  clear copy strategy

  • To get a consistent target landscape, consider copying the CRM server together with the other SAP systems such as ERP, BW, APO.

Notes:

You must clearly define your copy scenario. The definition is found in SAP Note 886102.

The scenario should be clearly communicated to the project and business  stakeholders and agreement that it (the  scenario) is the most suitable in this case.  This should be fomally documented.

APO  Specific

1.1 – Get required documentation

  • 457425  Homogeneous liveCache copy using backup/restore
  • 129352  Homogeneous system copy with MaxDB (SAP DB)

1.2 – Determine a clear copy strategy

  • liveCache Server
    • liveCache is usually copied using a database restore method SAP Note 457425.
  • All BW Specific system copy activities need to be considered, checked and applied discounted for SCM

APO  Specific:

Attention when using data extraction via BW functionality from other systems:

If you extract  data via BW functionality to load data into the SCM system, consider that it  may be required to additionally apply the system copy activities for a BW  system according to note 886102 to the SCM system.

Specifically when  using DP or SNP, data extraction is commonly used in SCM to load data from a  source system, for example from a BW system.

Please  note that when applying note 886102 to the SCM system, you need to consider  your SCM system being the ‘BW system’ while the source system for the  extracts can be a BW system.

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply