System Copy : Transactions sm59, we20, we21, bd64

Hi forum,
if you are to make a system copy, one system - as a rule QA - is overwritten by a production system. You can save
the RFC connections by consistently exporting (by use of brspace f.ex.) all table starting with rfc* and after the copy
you can reimport it. Same as for transactions we20 and we21. The tables in question are mentioned in note 181172.
But what can you do to export and later reimport the contents of transaction bd64 ???
Kind regards
OEggert2706

Hello,
Did you try the following option?
BD64--> Edit --> Model View --> Transport
Partner profiles are stored in the following tables. I think you can add these tables in a transport request, release it before refresh and import the same after refresh.
EDPP1: General partner profile
EDP12: Partner profile outbound, additional data NAST
EDP13: Partner profile outbound
EDP21: Partner profile inbound
EDIPHONE: Connection to SAP telephony (optional)
Thanks,
Siva Kumar
Edited by: Siva Kumar Arivinti on Dec 13, 2011 8:28 PM

Similar Messages

Homogeneous System Copy - Remaining ALE Configuration

We made a system copy of an R/3 HR productive system to a new server for testing purpose. The system copy was made with a backup / restore procedure. Now, the new server in online and is working fine. The problem starts when we want to make the accounting payroll. This process needs financial data from R/3 Finance system via ALE to make the accounting. So we decided to connect this new test system with our R/3 Finance QAS system, via ALE, to make possible the extraction of the data needed.
When running the accounting payroll process, we get the following error: "RFC Destination is not maintained for object BUS6004 and method check" and the accounting is canceled. We noticed that the system is trying to use a RFC which its destination is R/3 HR Productive system. Obviously, we deleted the RFC connection pointing to the real productive system to prevent any damages. Also, we checked the ALE configuration and everything is OK (Transactions: BD97, WE20, WE21). But, when we checked the consistency of the ALE configuration, in transaction BDM5, we noticed that there is another ALE configuration defined, which is pointing to the R/3 HR Productive system. It seems that the system copy brings all the definitions of the ALE configurations that were defined in the original R/3 HR productive system. However, this new system is using these settings for connecting via ALE. There is a way to delete or disable these old settings defined in this new system? When making a system copy, there is a way to avoid copying the ALE configurations defined in the source system?

You have some options here ie after system copy
- Before starting the background process (ie #rdisp/wp_no_btc)
- Start SAP system, execute sm59 and append to all the <destination/target> with <destinaion/target>_no connect for each RFC. This way the connections won't happen
- Save
- Stop SAP
- remove # frm rdisp/wp_no_btc
- Restart SAP
whenever you want to try a connection then will remove the _NOCONNECT and it connect
or
you have a table RFCDES, which can be disabled (i haven't tried this).
Cheers

WE20, WE21 settings after SAP BW system copy

Hi!
I copied SAP BW system and have executed the following post installation settings:
- BDLS (conversion of logical system names)
- Program RS_BW_POST_MIGRATION
When I go to tcode RSA1 on my new copied SAP BW system and try to reach source system I get the following error:
BI unknown in source system
BI IDoc type ZSBA004 is not the same as source system IDoc type
The following errors occurred in the source system
EDI: Partner profile not available
+Entry in inbound table not found +
Entry in outbound table not found
Question:
Should I create new entries in tcode WE20, WE21?
If yes, how (copy of existing one from SAP source BW system)
Thank you!

Hi!
I face currently with the problem on my new SAP BW within RSA1 --> Source system --> Check:
BI unknown in source system
BI IDoc type ZSBA004 is not the same as source system IDoc type
How can I solve this problem?
The partner definition t-RFC as well are created...
Thank you!

Exporting WE20, WE21 and SM59 Entries

Hi,
Can anyone knows how can we export or keep a copy of WE20, WE21 and SM59 Entries for later use. As We are going to refresh the development server with quality and wish to restore the orignal DEV servers parameter (Enteries) settings.
How can we do Export and Import. Pl. suggest me some solution.
Thanks,
Raj

Try this Script . Go to /usr/sap/trans/bin create a file ( <filename>.ctl > with the following entries
export
file '/usr/sap/trans/data/filename1.dat'
delete from rfcattrib
select * from rfcattrib
delete from rfcdes
select * from rfcdes
delete from rfcdoc
select * from rfcdoc
delete from rfcsysacl
select * from rfcsysacl
delete from rzllitab
select * from rzllitab
delete from rzlliclass
select * from rzlliclass
delete from sxroute
select * from sxroute
delete from rfccheck
select * from rfccheck
2 ) execute the command R3trans -w <filename>.log <filename.>.ctl , a log file will be created in /usr/sap/trans/bin with the file name <filename>.log , R3trans return code should be 000 0r 004.
3) If you want to reimport it to the same system at a later point of time create a script <filename2>.ctl in /usr/sap/trans/bin
import
file '/usr/sap/trans/data/filename1.dat'
4) R3trans -w filename2.log -u 1268 <filename2>.ctl
The return code should be 000 or 004 , compare the no of table enties in the exported and imported log files , they should be in sync .
Edited by: Mann Mohandas on Feb 20, 2010 8:33 AM

HTTP destination PI_INTEGRATIONSERVER missing (system , transaction SM59)

Hi Experts,
I am working on ABAP Proxy -> File scenario. When I trigger message in ECC, it is giving error.
When I go to SXI_Monitor in ECC, the message is shown as red with error message "HTTP destination PI_INTEGRATIONSERVER missing (system , transaction SM59)". But the RFC destination PI_INTEGRATIONSERVER exists and when i tested this connection I got 500 empty request received message.
I have configured in SXMB_ADM the ECC system as application system and mentioned 'dest://PI_INTEGRATIONSERVER' as corresponding integration server.
Could you please help me in resolving this issue?
Thanks and regards,
Prasad

Hi Prasad,
Ensure below items in your ECC system.
1. goto SM59
2. ensure your RFC - PI_INTEGRATIONSERVER has this entry '/sap/xi/engine?type=entry' (without quots)
3. Target Host has value your PI/XI hostname and correct port number (HTTP)
4, for Logon& Security Tab, ensure to use userID PIAPPLUSER and correct password (saved)
or Service user of Integration engine (maintained in Exchange profile)
You can write back to me if any further help required.
Regards
Sekhar
Edited by: sekhar on Dec 24, 2009 6:57 PM

HTTP destination IED_100 does not exist (system , transaction SM59)

Hi guys,
When I try to send a xml file to WAS using ABAP Proxy I receive this error message: "HTTP destination IED_100 does not exist (system , transaction SM59)".
I did a test connection in sm59 for http connections/R/3 systems and the messagem bellow is ICM_HTTP_CONNECTION_FAILDED.
What could be wrong?
Thanks in advance,
Ricardo

Hi Sridhar,
Im trying connecting XI to WAS 6.40 using ABAP Proxy.
Now I receive this error message: <SAP:Code area="INTERNAL">SYSTEM_NOT_CONFIGURED_AS_XMB</SAP:Code>
<SAP:Stack>System not configured as Integration Engine</SAP:Stack>
I have defined my business system IED_100 (WAS 6.40) like application system and the related integration server is XI. Its correct?
When I check the component monitoring > Integration Engines > Proxy runtime IED_100, this message is displayed:
Unable to log on to system IED_100 in language en with user XIRWBUSER. But in WAS system (IED_100) I dont have a user XIRWBUSER!!! I need to create it?
Tell me if Im correct: I dont need any RFC adapter; Im only need an XI adapter (http) to send the xml file to ABAP proxy (IED_100) and on IED_100 I need to activate XI message format service in SICF and create a RFC connection in SM59 to call XI integration server. This is already done!
In sm59 I continue with ICM_HTTP_CONNECTION_FAILED
Thanks in advance,
Ricardo.

Homogeneous System Copy - Export Import of RFC's, ALE, Content Repositories

Good Morning,
I have a landscape with a Development and Production Systems with SAP R3 Enterprise 4.70 Ext 110, MaxDB 7.5, HP-UX 11.23. A Homogeneous System Copy is going to be done from Production to Development.
I have a idea to be able to recover the RFC's, ALE and Content Repositories Information after the Copy, which is to create a transport order with the structures which contain data for the RFC's definition, the ALE configurations and definitions and the Content Repositories configurations and definitions in Development and after the copy, transport the orders back to Development. The problem is that i don't know which structures should i use, and if my idea is viable?
For example, if i go to transaction oac0 and look at the content repositories and if i look at the Technical Information, i can see that the fileds with data are from Structure SCMS_SCREP, but my question is, inserting thsi structure in a transport order to import after the copy willbe enough? Aren't there more structures i need to insert in a transport order? And for RFCs and ALE?
Can anyone help me on this matter please?
Kind Regards,
Pedro Gaspar

Hi,
If the target system is being refreshed then first secure any information that you may require.
1) Backup user master and authorization data from each client where this data needs to be retained.
Use transaction SCC8 to export this data. Select profile SAP_USER and specify target system = TARGET_SID.
2) Backup RFC tables to restore destinations afterwards.
the only below tables required to take backup.
Call SE01 and create a new request of type = ""Transport of Copies"" with description = ""Export RFC destination tables prior to system refresh"".Make sure to specify a Target for the request or no data file will be created.
RFCATTRIB
RFCCHECK
RFCDES
RFCDESSECU
RFCDOC
3) ALE / Partner profiles.
Call WE20 and select each partner profile.
Follow menu path ""Partners --> Check"" and obtain a list of tables used.
The only tables listed were the ones listed below.
These tables are client-dependant therefore you will have to logon to each client and call SE01 and create a new request of type = ""Transport of Copies"
EDPP1
EDP13
EDP21
Also document the WE21 --> Ports --> Transactional RFC" section.
Run transaction BD64 and document each configured distribution model. This information is client-dependent so make sure to record values for each required client. and also record RFC destinations for synchronous method calls in BD97.
I hope it will help you.
Regards,
Kiran .V

System copy for PI 7.0 system

Hi,
We are doing system copy for complete landscape and every time we used to perform PI system copy using SAP standard procedure of backup/restore, Java exp/imp.
But can we use another approach of exporting IR/ID from source to Target. Because we do not have any transactional data in PI and what are different things that we need to take care if we export individual components.
Like new ports, we20,we21, IDX1,IDX2
Thanks,
Venkat.

to elaborate more,
we are doing system copy from Dev to Sandbox (we already have working sand box)
I am planning below steps
1) export all the software components from development system - Integration repository and Directory
2) Adjust the transport path in SLD (source Dev and target Sandbox)
3) Import the software components to Sandbox for Integration repository and Directory.
4) change user-passwords to match sandbox authentication.
Please let me know if i am missing any steps and has any one did a copy by above procedure.
Thanks,
Venkat.

System copy : how to backup your rfc connections, partner profiles ...

system copy : how to backup your rfc connections, partner profiles (we20) amd ports in IDOC processing (we21) ???
Hi forum,
if you want to copy your production system to your quality assurance system you can export users and later on reimport
it to save work. That's good.
But how about RFC connections, partner profiles and ports in IDOC processing ? Anyway to export and reimport it later on ?
Thank you for your help.
Kind regards
O.Eggert

Hi forum,
in the meantime I found out how to handle this matter. May be this solution is not very elegant, but it works.
As for RFC-Connections there are several tables beginning with rfc. e.g., rfccheck. But 4 of it only differ from one system
to the next. These are rfcdes, rfcdoc, rfcattrib and rfccheck. What I did is the following : I used
brspace -u sapsr3/<password> -f tbexport -t "RFC3"
and quite simply exported these tables. Then I deleted some of the RFC-Connections, both ABAP and TCP/IP. After reimporting
what I exported before all these destinations were availlable again. As for ABAP the password had to be reentered but this
can be avoided, too. Have a look at transaction /nsecstore. The tables behind it are RSECTAB and RSECACTB, rspectively.
Export it after having exported the rfc* tables and reimport it after having reimported the rfc* tables. Very important : enable
the option "consistent export" !!!
It worked this way although there might be better and more elegant solutions.
As for transaction we20 check sap not 182172.
Hope that I could be of profit to this forum.
Kind regards
Olaf Eggert
p.s.
import command : brspace -u sapsr3/<password> -f tbimport.
Them select what you exported before.

Logical System Name after System Copy

Hello,
I have three questions about the logical system name after system copy.
Q1) When I change SID D22 to S11 during system copy,
do I have to change the logical system name of all clients in the target system? The target system is used for test, and the landscape has S11 and Virtial system. The target system S11 does not communicate with the source system D22.
Q2) If the answer for Q1 is YES, is it correct that the following procedure for changing logical system name?
1.Tr-CD:BD54
Add new logical system name for all clients in the target system.
2.Tr-CD:SCC4
As for all clients, select new logical system name with F4 help.
Q3) If the answer for Q1 is YES, do I have to add new RFC connection entries with SM59 for all clients in the target system?
I refer to the guide "Homogeneous and Heterogeneous
System Copy for SAP Systems Based
on SAP Web Application Server
ABAP 6.40 SR1".
thanks,
Keishi

Hi Keishi,
As a good and ideal practice the answer to your first question Q1 is yes. Infact I would say that in case you are using ALE then it is must
For Q2 there has to be an additional step which is most important one. Running BDLS transaction which would allow you to change logical systems in relevant tables from the one of source system to target system.
For Q3 the answer is agaain yes and you can have two approaches>
1. manually recreate all the RFC destinations after sys. copy.
2. Export all the RFC destination data relevant tables before system copy and then reimport them after sys. copy.
Regards.
Ruchit.

Error in documentflow after System copy

Hi experts
After a system copy we are not able not use the documentflow functionality in CRM for sales orders that has been replicated to R/3. We get following errormessage:
"BUS2032 with key 'order number' is not available in logical system xxx'
The logical system "pointer" is pointing at the wrong system. How do we change the pointer to the correct logical system?
Best regards
Jørgen Jensen

Please check if BDLS has run properly after you have done a system copy.
Else please use transaction SALE in order to check the setup of your logical systems and what systems are being pointed to currently. Also you may need to check your SM59 settings

ODS/PSA Problems after System Copy

Hello All....i am a basis admin and am having problems with PSA after performing system copy. I have copied R/3 (source system) ans SCM (source system) and BW (3.5)systems from production into test environment in parrallel. I have performed all required BDLS steps on R/3, SCM, and BW as well as maintenance of RSLOGSYSDEST table. All profiles and ports (we20/we21) have been maintained as well. I have modified and tested all RFC connections and have used RSA1 to restore the source system connections and to activate and replicate. When activating ODS objects, the following error is generated...
There is no PSA for InfoSource 8ZFAP_O01 and souce system PB1CLNT510.
PB1CLNT510 references former production BW logical sys and correct logical sys should be QB1CLNT510. Apparently BDLS has missed a table or I have skipped a step in my post-clone process of BDLS and WE20/21. I am wondering if there is a re-initialization or logical system conversion step i have missed or is anything else i can do to resolve this issue.
Maximum points awarded for quick resolution.
Thanks in Advance
Chris
Basis

Hello Chris,
This InfoSource is related to a DataSource in which the source system is BW system itself (in your case: QB1CLNT510).
Try to first activate the DataSource 8ZFAP_O01 using the standard program (SE38): RS_TRANSTRU_ACTIVATE_ALL in which you should input the source system (QB1CLNT510) and the InfoSource 8ZFAP_O01. If you get a green light in the log that appears after the activation completes in which it says that all the structures have been activated, then all you need is to locate the DataSource in RSA15 and right click -> replicate.
If the log showed you that this DataSource doesn't exist, then you'll need to Activate the source system QB1CLNT510 again.
I hope this helps. Cheerz,
Ali

System Copy in AIX

Hi experts,
o m new to basis. can anybody answer to following questions?
1)complete system copy procedure(pre-requisites and post).
2)what are all the file systems i shud take back up for system copy.
3)Pls tell me be how to check the file systems(sapdata1,2,3 etc).
can u give the commands in steps wise.
Regards,
Abdul Majid

Hello Abdul
Refresh from Offline backup (AQC from APC) let's say AQC is quality and APC is production
Pre-processing Activity:
Verifications:
1. Verify the last offline backup in the source system
/oracle/<sourceSID>/sapbackup/back<sourceSID>.log
2. Verify that both the source and target systems are at the same Oracle level (which is already the case
between APC and AQC)
3. It is recommended that an off-line backup be taken of the target system before starting this process, in
case of fall back.
4. Confirm there is enough space in the target (AQC) file systems to contain the data from the source
system this is required as we may have to copy the files from Production to quality.
/oracle/SID/sapdata* folders should be having little more space as compared to the source filesystem.
5. Check access to SAP* for APC (000 and 400) and also for AQC (000 and 400)
6. Check other passwords such as <sid>adm and ora<sid>
7. Server : <source server name>
User : ora<sid>
> sqlplus u201C/ as sysdbau201D
> alter database backup controlfile to trace
> exit
In /oracle/SID/saptrace/usertrace, the last trace (check the time) is the script for recreating the control
file. You will need to edit it. Please rename the trace file to ld<TARGET_SID>.sql and send the file to the
target system /oracle/SID
Edit the Script:
vi ld<SAPsid>.sql
Delete or comment out all lines at the beginning of the file before STARTUP NOMOUNT which is kept.
Change old controlfile creation statement at the beginnig of the controlfile:
Old line:     create controlfile reuse database <SAPsid>   NOresetlogs archivelog;
          change to
New line:     create controlfile   set   database   <SAPsid> resetlogs archivelog;
replace all occurences of string <source_SAPsid> by <SAPsid> in each line where <source_SAPsid>
appears
:g / <source_SAPsid> / s / <source_SAPsid> / <SAPsid> /g
example:
:g/P10/s/P10/T21/g
Delete the following lines a the end of the script:
               RECOVER DATABASE;
               ALTER SYSTEM ARCHIVE LOG ALL;
               ALTER DATABASE OPEN;
8. Get from the Prod system (APC) the .aff and backDPR.log and copy them on AQC.
(/oracle/<SID>/sapbackup)
Copy      the files to /instkits/SID/. And after we can go on target source server and copy them from
/instkits/SID to the /oracle/SID/sapbackup/. With the good owner and permission
9. Lock all the users in client 400 except Basis and post system message.
Target system data collection (On AQC -400):
1.     SM59 Expand all the trees, print by choosing: ->System ->List ->Print
i)     Compare list to R/3 connections on source system. Record details for any that will need to be
recreated on target system.
2.     SCC4 Record all client settings. -> Tableview ->Print ->Standard List -> List -> Print
Make sure you understand the columnsu2026
3.     SE06 Record system change options
4.     RZ10 Record the instance profile settings for: rdisp/wp-no-btc and rdisp/max_wprun_time
5.     STMS Record current transport routes. ->Overview -> Transport Routes ->           manually
expand all trees -> system ->list ->print
6.     Request customer to provide u201Ccatch-upu201D list of transports to be applied to system after refresh
(QA and Sandbox systems).
7.          RZ04 Record current work process set-up. Highlight each operation mode and click
instances/op modes button.
i)     Print with ->System ->List ->Print
8.     SAP License Ensure the SAP license information is available. If not on-hand, logon target
system as <sid>adm and enter command: saplicense u2013show. This information is also available on OSS.
9.     TSM Nodename View /usr/tivoli/tsm/client/api/bin64/dsm.sys on source and target system.
Record the nodename entries. These will be <SID>SAP or server names.
11.       Take printer Export through SPAD and save it locally to desktop->SPAD
12.        Take Export of User Master from the client 400 through SCC8 target system is AQC , so that it
may be re-imported through STMS.
Note the Transport number here also verify the transport exist in the queue.
DB Restore from offline backup from APC:
1. Stop SAP on AQC -> Login as aqcadm -> stopsap
2. Change the TSM node on AQC-> cd /usr/tivoli/tsm/client/api/bin64
        ls -lrt
       vi /usr/tivoli/tsm/client/api/bin64/dsm.sys
Change it to point to APC, comment the AQC Node.
Post Restore Acitivity:
1. Stop Database
Delete Old controlfile
rm /oracle/AQC/sapdata1/system_1/cntrl/*
rm /oracle/AQC/saparch/cntrl/*
rm /oracle/AQC/origlogA/cntrl/*
2. Re-create the controlfile and then after that start the database
User : ora<sid>
> cd
> sqlplus u201C/ as sysdbau201D
> @ld<target_sid>.sql
> alter database open resetlogs;
3. Change the sapr3 password
Server : <target server name>
User : ora<sid>
Temporarily, we have to change the sapr3 password to the default password. With SAPBA, change this
user password to pass.
4. Test the connection:
Server : <target server name>
User : <sid>adm
> R3trans u2013d
It should have a return code of 0000
5. Reasign tempfile
alter tablespace psaptemp add tempfile '/oracle/AQC/sapdata1/temp_1/temp.data1'
size 6020M reuse autoextend on next 20971520 maxsize 10000M;
alter database rename global_name to AQC.WORLD;
drop user OPS$APCADM cascade;
drop user OPS$ORAAPC;
create user OPS$ORAAQC identified externally default tablespace psapdnausr
temporary tablespace psaptemp;
grant connect, unlimited tablespace, SAPDBA to OPS$ORAAQC;
grant connect, unlimited tablespace, SAPDBA to OPS$AQCADM;
7. Change the instance profile to stop all the background processing
To be sure that no production batch are executing, set rdisp/wp_no_btc to 0
posprocessing:
8. Startsap
9. Run Transaction SICK (as sap*)
10. Installing license through the tcode: slicense
While logged in as 000/sap*/using password of APC system
Get the License from service.sap.com and download it to local machine
Log in 000 client using SAP* and run the Tcode slicense
import printers, run BDLS for logical system name conversions
se06 posprocessing
stms
usermaster import
import profiles for QAS
thanks
Bhudev

Transformation inactive after system copy in SCM system

Hi Team,
I am posting this in BW keeping in mind that i am receiving issues in RSA1 transaction in my SCM system after the recent system copy. We did the system copy of SCM system and DTP conversion was also done using program RSBKDTP_BDLS. No errors occurred while the program ran. Now we have handed the system back to users for checking and they have reported an error saying there were some transformations missing in the system while checking the DTP . I went to RSA1 transaction in my SCM system and searched for the DTP and status seems to be in inactive status. I then clicked on change button and an error message mentioning the below appears.
Transformation XXXXXXXXXXXXXXXXXXXXXXXX inactive; action cannot be executed
Message no. RSBK260
Diagnosis
A transformation (XXXXXXXXXXXXXXXXXXXXXXXX) used by the DTP is inactive.
System Response
The action (request processing or DTP maintenance) was terminated.
Procedure
Activate the transformation. It connects the source XXXXXXXX XXXCLNT100 to the target XXXXXXXX.
I checked for the transformation entry in the table RSTRAN and did not find the same. Also i ran the program RSDG_TRFN_ACTIVATE to activate the transformation but nothing happens.
Have anyone came across this type of issue. I need some advise on the same and guide me in case if i am missing something, since i have not worked on this type of issue before.
Thanks for your help in advance.
Rajesh

Hi,
Due to the system copy we always get this issues.
Just ask your basis team to check source system assignments. they can do it.its their activity.
at BW Server, RSA1 -->menu tools--> manage source system, check the source system. same need to have at below we20.
at Tx - WE20, Partner type Ls---> under this you may see your target(SCM) and source system anmes. select source name and rigth side panel partner status need be active A.
At quality syste, activations thru program may not be happen. better to re-transport the dtp from dev system.
Thanks

We would like to test old deltas from the source system( copied to new)

Hi Gurus,
The scenario is
They will make a DB copy of the Prod system onto a QA system, the Copied system will have
its system ID changed(SID) to a new one.
There will be deltas available in the RSA7, as this is a copy of the 3 weeks old prod
system. Now the delta's will be available on the Copied system pointing to the BW Prod system.
We would like to test these delta's to BW Dev. why we would like to do the delta's to the
BW dev system is to check whether we can do system copies without clearing the delta's on
the source system.
After the system copy we will do all the activities necessary to reflect the system changes
a. Like BDLS, We20, we21,ALE checks, RFCDES, RSLOGSYSDEST, RSBASIDOC, etc on the source system to
reflect the changes of the BW Prod system to BW Dev system.
b. Likewise, we will perform all the above activities on the BW dev system by changing the
existing source system to the new source system( performing BDLS,we0, we21, etc)to reflect
the new Source system with the new (SID).
c. We will check the source system connection
d. Replicate the datasources on the new source system
e. Activate the Transfer rules for the new source system.
Now for us to do delta's from the new source system to the Bw dev system we need to change
underlying tables in source system to point the delta's, arfc TID's etc to the BW dev system.
We can change the entries in the TRFCQOUT, ARFCCSTATE, ARFCDATA tables to point the LUW's and
destination to the BW dev system.
What I presume is if we run the BDLS on the Copied system to change the BW prod system to BW
and also the underlying Tables for the LUW's and etc will still be pointing to BW Dev. I would
like to know if this is the case .
Lastly, appreciate if anyone can say if this is possible to do without having to clear the
BW delta queue on the source system.

Hi Ramesh,
Appreciate a lot for your response, but i would like to know if we can reflect the entries in table RSSDLINIT(Last Valid Initializations to an OLTP Source) and RSSDLINITSEL(Last Valid Initializations to an OLTP Source) in the BW system on the copied source system
tables ROOSPRMSC(Control Parameter Per DataSource Channel), ROOSPRMSF(Control Parameter Per DataSource Channel) by executing the ABAP program RSSM_OLTP_INIT_DELTA_UPDATE after we do the BDLS conversion on the new copied source system.
After the BDLS conversion I reckon the entries in the RSA7 queue, ARFCCSTATE, TRFCQOUT tables willl reflect the BW Development system instead of the BW Production system isnt it.
response much appreciated.
Kalyan

System Copy : Transactions sm59, we20, we21, bd64

Similar Messages

Maybe you are looking for