Post processing steps for SAP BW system copy.
After system copy, you nees to perform some post action to reactivatethe extractors
Usually, to have the datasorted, you refresh both thesource andtargetsystem.
If you runthe refreshonlytheBWsystem, you can ignore thefirstparagraph
Action in souce system
Converts occurrences of the value for logical system name in various tables.
Convert BAPCLNT100 in BATCLNT100
Convert <LOGICALNAMESOURCE_PROD>in <LOGICALNAMESOURCE_TEST>
Do not continue untilboththe logical nameshave not beenconverted
check if in Logical system name is correct ( BDLS should fix it )
checkthat it exists andfunctions, theRFCconnectionBATCLNT100
checkthat there isa door thatpointstoBATCLNT100(exchange the portA0000000XX that points to thesystemofproductionBW)
createnewlogical systemBATCLNT100(notethe system must beopen tochangein order to changethe table)
createnewlogical systemBATCLNT100 like LStype, you must reset allflagsofBAPCLNT100. Sothe most ‘safe is to create itas a copy ofBAPCLNT100(the “No Partner” is the logical system, not the RFCconnection!). After thatin Outbound parmtrs, clicktwice on themessage t ype, thescreenwill openwiththe parameters configured, check that the dooris the same aspreviously configuredinWE21.
Checkthat in Classification, patner status is active ( A – active , I – inactive).
Action in bw system
To download Trainer, use the link at the bottom of the page.Functions:. If you experience any difficulty in the game «Sniper Elite 4» (2017) or just want to have fun, this cheat is created specially for you!
converts occurrences of the value for logical system name in various tables.
Convert BAPCLNT100 in BATCLNT100
Convert <LOGICALNAMESOURCE_PROD>in <LOGICALNAMESOURCE_TEST>
Do not continue untilboththe logical nameshave not beenconverted
Check the entry in follow table; should relate to thetest
RSLOGSYSDEST
RSBASIDOC
Function: RSAP_BIW_DISCONNECT
Parameter I_BIW_LOGSYS <<SLOGSYS>>
I_OLTP_LOGSYS <<RLOGSYS>>
I_FORCE_DELETE X
check that there isa door thatpointstoBATCLNT100(exchange the portA0000000XX that points to thesystemofproductionBW) Tafsir ibn kathir pdf.
create newlogical systemBATCLNT100(notethe system must beopen tochangein order to changethe table)
createnewlogical systemBATCLNT100 like LStype, you must reset allflagsofBAPCLNT100. Sothe most ‘safe is to create itas a copy ofBAPCLNT100(the “No Partner” is the logical system, not the RFCconnection!). After thatin Outbound parmtrs, clicktwice on themessage t ype, thescreenwill openwiththe parameters configured, check that the dooris the same aspreviously configuredinWE21.
Checkthat in Classification, patner status is active ( A – active , I – inactive).
right –> restore
User administrator
continue
Use
alsoreplicate
Dialog
execute evaluation
references
Skip to end of metadataGo to start of metadata
PREPARATION
So, Lock Users: Only administrator user IDs should be active and all other SAP user IDs should be locked so that no user intervention can occur at the time of client copy in the source system (SU01).
PRE-REQUISITES
PROCEDURE
Log on to source system - source client and make sure that all above steps have been performed .Then go to tcode SCC8 for Export. Select a client profile according to data to be copied as a Transport request. Mention target system into which the client should be copied. Configure this as a background or dialogue process.
According to the client profile selected and the data available, maximum 3 transport requests will be created and automatically exported to target system mentioned. The requests are like
<sid>KO<No> - For cross client data
<sid>KT<No> - For client specific data
<sid>KX<No> - For client specific texts
Once above TRs got created, all of them automatically released and exported to a target system. This can be checked in SE01 or SCC3.
IMPORT
Log on to target system(client) and execute STMS tcode.
STMS > import overview > refresh the buffer to find exported requests →import Queue of target
Client → start import.
In case 3 transport requests are created in export any one of the TR is started then the rest TRs also get imported in to target client automatically. Skip to end of metadataGo to start of metadata
If you copy a system which is connected to a BW system or in case you copy the BW itself or both, several steps has to be considered in order to make sure that the connection between BW and another SAP source system works again after one or both systems have been copied.
System copy with PCA (Post-Copy Automation)
SAP provides an automated solution in order to manage the very complex challenge.
A very good overview is available under the following link:
and SAP note 1707321
delta queue cloning and renaming of the prefix is only possible with PCA
ODP source system connection and ODQMON: deletion of subcriptions which are pointing to the wrong system and creation of the 'new'subcription to the correct system is possible
PCA is not yet released on BW/4HANA, have a look at SAP note 2570363
System copy without PCA tool
Not all landscapes can be described but the the main steps are also described in SAP note 886102. This consulting note has been created when SAPI source systems are involved. In case of ODP source systems, PCA should be used. Not all steps are not necessary anymore for ODP source systems but additional tasks are necessary e.g. cleanup of ODQMON which is possible by using PCA.
Important is that all steps should be executed in the correct order. Additionally have a look at the recommended note list, which should be implemented in case you need to execute BDLS: KBA 2176213
System copy on HANA:
Run the Report RS_BW_POST_MIGRATION with the Option 12 (create calculation view cubes/infoobjects) and 15 (Adjust Snapshots and AnalyticalIndexe) to create missing calc views and workspaces.
SAP note 886102 is not applicable for BW/4HANA systems! Have a look at SAP note 2570363
According to SAP note 886102:
What do you intend to copy?
Below scenarios only decribe the steps which are necessary for SAPI source system connection. For ODP source system connection, have a look at SAP note 886102
Special business requirements
Pre Check For System Refresh In Sap AccountRestriction concerning system copy without PCA:
Connections errors after a system copySap Refresh Steps
Page:BDLS Notes (System Copy)Page:BDLS - Logical system name conversionPage:Scenario A1Page:Scenario A2Page:Scenario B1Page:Scenario B2Page:Scenario B3Page:Scenario B4Page:Scenario C1Page:Scenario C2Page:Scenario C3Page:Scenario C4Page:Transport for sourcesystem dependent objects
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |