DTP error after QA system refresh

Hello Experts,
Whenever we refresh our QA system[with Production data], the DTP's and the 7.0 datasources always point to the Production R3 system and not the QA R3 system. Is there a program available to correct this like we have in BW 3.x?
Thanks
Arvind

Hi,
Your basis should change the source system settings, connect to your Q r/3 but not P r/3. How about change source system connection, change IP to Q r/3 and then replicate & reactivate all datasources?
Also you can have a look at BDLS:
BDLS
Re: Question on BDLS
Regards,
Frank

Similar Messages

Activites after source system refresh

Hi all,
we made source system refresh recently.
When iam running INIT I am not able to get the data ,but in rsa3 data it is available
Now I am not able to retrive the data from source system for SD data sources like 2LIS_02_ITM.
Can any one tell me what type of activities i need to do after source system refresh for LO data sources.
Thank
Pruthvi

Hi Pruthvi,
As you mentioned about refresh, it would be a system other than Production system.
Delta Loads:
1. Whenever a refresh happens from the production, the delta pointers are disturbed.
2. You need to re initialize the delta pointer for the DS you mentioned.
3. If it is for the testing purpose of the Delta functionality, you may intialize the delta pointer 1st and then ask for postings of data in the ECC side.
4. Once the postings are done, you would see data in Delta Queue in RSA7 in source system.
5. Now run the Delta InfoPackage so as to fetch this data from the Delta Q of SS to the BW system.
Full Loads
1. If you are expecting a full load (Historical data), you need to first fill the Setup tables (in Background only) in the SS.
2. Once the Setup table fill job is completed in SS, you may execute a Full InfoPackage in order to get this full load.
Let me know if this helps..
-Bhushan.

No Idocs were getting generated after the system Refresh

Hello Experts,
Recently my Sand box system has been refreshed with the Development system. (Its a system refresh and hence all the objects were also copied like Development).
After the refresh, we have performed the below activities --
BDLS to change the logical system
Maintained the LS in WE20
Partner Profiles from WE21 with proper settings with respect to the new logical system name. (Sand box).
RFC to myself source system and to the Flat File.
While executing a test load from Flat File the system is not able to generate any IDOCS in the system and failing with
"No Idocs generated; file system
Diagnosis
No IDocs have been created. With file systems as source systems, the IDocs are created in BI. As this did not happen, it is probable that there was a short dump in BI.
I dont see any short dumps in ST22 for this load and also any logs in SM21.
Any idea why the system is not able to generate IDOCS in the system?
We are planning to connect R/3 sandbox to BI sandbox once the Flat file load is running fine.
Thanks for your answers.
Raman

Hi ,
Hi
BD87 Update Idocs manually.
1. When you look in the Monitor screen for the first time on a day you mostly will see some Loads that have yellow traffic lights. When you click on the lowest line of the Load (with the time of Load start) you will get the next popup screen:
2. Here you can click on the "Yes" button. The Load specification window (right side of the screen) will now be filled with data.
3. You can now start the manual processing of the IDocs. You go to the "Details" tabpage of the right window. You right click on the line with the red traffic light stating "Request IDoc : IDoc ready to be transferred to application" on the "Details" tab page of the Load. In the option menu that appears choose the option "Update manually in OLTP" (click it).
4. You will get to the next screen (which is in fact a transaction in the source system (SAP R/3) where you can update the IDoc that is send by the source system)
5. Now click the "Excecute" button on the left of the screen (or press the F8 button on your keyboard). You will get to the next screen:
6. This states that the IDoc has been passed through to BW. You return to BW by clicking the "Back" button (or pressing the F3 button on your keyboard) twice. After the first time you will see the previous screen and after that the Monitor screen again.
7. You will now see that the Status of the Load has turned to yellow or green. When it is yellow you will have to wait a little time (the execution of the Load in BW is still running) and by clicking "Refresh Details" button on the left upper side of the screen (or pressing the F8 button on your keyboard) you will see the Load turn green.
Regards,
Rahul.

Lost Transport Import History after the system refresh

Hi,
We forgot to take the backup of the TPALOG table before the system refresh. We refreshed our testing system from production system. Right now we donu2019t have the old import history for the testing system. We played with TPALOG table and TPALOGHDR to synchronize TPALOG table with ALOG* files. But we are not able to do that. I remember we had synchronized the TPALOG table with ALOG* files in the past. Please advise for any function/program to achieve this. Thanks.
Thanks.
Raj.

Hello Raj,
The mechanism behind the import history is that STMS will look in table TPALOGHDR to check if the time frame for which the import history is called, is between STARTTIME and ENDTIME.
If it is, it will use the entries in table TPALOG.
If not, it will read the ALOGxxxx files on /usr/sap/trans/log and update table TPALOG.
Modifying the ENDTIME in TPALOGHDR will force reading the ALOG files again and will update the internal table TPALOG. In most cases,using the first date you find in the ALOG file that covers the missing transport.
To reduce the possibility of competing accesses to the action log you can select a system-specific name. For this purpose, set the tp parameter ALLLOG in the STMS transport tool as global and with value:
ALLLOG = ALOG$(syear)$(yweek).$(system)
This will create system dependant ALOG files like, ALOG0318.D01
It should be noted that : The import history in TMS is only available for periods after the last copy of a system. The reason for this is, that TMS needs some information about the ALOG files which are stored
in the database. During a database copy, this information is destroyed and there is no possibility to restore this data.
Best Regards
Niraj

HP2000 issues after doing system REFRESH and everytime it does UPDATES

Every time I have updates on my laptop HP 2000 bf69wm I have major issues. It happened again today I did the updates and then I cannot access anything on the internet. I get the spinning circle of death and no pages load. I did a system REFRESH which states it will not affect your personal stuff. Well great my pics are all intact however my Windows Office programs are GONE!!! I had to pay to put that on my computer and now they are gone!!! I got this laptop as a Christmas gift from my parents because my Toshiba is falling apart literally it is duct taped together. However the Toshiba still has less issues than this laptop does and it is brand new. So now do I honestly have to pay for Windows office again. It was a one time download so I cannot just download it again and I need it for my college classes. It is awesome to have a brand new laptop that only works when it feels like it and gives me more stress than it helps. Can someone please help me on what the deal is with this and also why I keep getting a message saying my usage is at 100%? I can be in my email and it tells me I am running at too much blah blah blah. So what is the purpose of the laptop if I cannot use it? If I had known it was this bad I would have returned it but too late now. PLEASE HELP!?!?!?!?!?

Hello xopixiegirlox,
Please call in and speak to a representative.
If you live in the US, contact HP Here.
If you are in another part of the world, start Here.
Please let me know if the rep was able to take care of your issues.
Good luck!
↙-----------How do I give Kudos?| How do I mark a post as Solved? ----------------↓

Error after lastest system update

I downloaded the new update this morning and now after I start up the console if I play a game or access any of the settings. For some odd reason whenever I finish whatever i was doing the Playstation doesn't eject disks and I can't access anything else except the start screen.

Thanks it worked. Now I only have to stress about what game I'm going to play

Windows 8.1 will not activate on HP19-2113w after system refresh.

Everything was working fine on my PC. Then the other day it crashed and said there was a disk error and that it had to scan the whole drive to find the error. It finished scanning, but windows 8.1 would not load sucessfully. Therefore I did a system refresh thru HP recovery. After doing that windows would start up normally, but I lost my activation. When I tried to activate the response was "Key doesn't work try again later" or something like that. Kept trying, no luck. I thought it may have been an error with the system refresh, so I did the total system reset (after saving personal data). Now I am having the same problem with activation, and If I try to navigate the normal way to the activation screen, the screen disapears. I can get to activation using command prompt. but key still does not work. The key I am using I retrived from my BIOS data. Also, I ran the refresh and reset from the origional hard drive partition. I hope someone has a solution to this. Thanks is advance Bill

Hello , Welcome to the HP Forums, I hope you enjoy your experience! To help you get the most out of the HP Forums I would like to direct your attention to the HP Forums Guide First Time Here? Learn How to Post and More. I have read your post on how your desktop computer will not activate after performing a system refresh, and I would be happy to assist you in this matter! In order to correct this issue, I suggest following the steps in this resource on Windows 8 product activation, which should help to activate Windows 8.1 on your system. Please re-post with the results of your troubleshooting, and I look forward to your reply!
Regards

Source System Problem after system refresh in RSA1 trx

Hi,
We have R/3 4.7 Test source system created in our SCM 2007 Test System. The source system check was OK.
The R3 Test system was refreshed with Production data few days back and now my source system is not working. When i perform Source System check it says:
BI unknown in source system
BI IDoc type ZSSB006 is not the same as source system IDoc type
I performed following steps in R3 Test system after its system refresh:
1. Created logcal system and created RFC.
2. Created port in trx we21.
3. Created partner profile in trx we20.
4. For the outbound parameter RSSEND, I had to create idoc type that should be same as in my SCM system i.e. ZSSB006.
5. Created idoc type using trx we30 as a copy of RSSEND and added entry in table EDIMSG. Now, i could also create outbound parameter RSSEND with idoc type ZSSB006.
After performing the above steps i also replicated the datasources for the R3 Test source system, but its still showing above error.
I also checked the RSBASIDOC table in SCM test system. It has correct entry for my source system. But there is no such entry in RSBASIDOC table in the R3 test system.
Someone pls help me.
Regards,
Chintan

Hi
Need to restore the All Dalaload connection settings after refresh the system which either R/3 or SCM.
RSA1 -> select the Source system -> Right click -> Restore , It'll ask the connecon paramters like RFC , method of activations. Then check the connection test of the Source system .
Check the the note for further info...
Note 886102 - System Landscape Copy for SAP BW and NW BI
Hope halp you...
Regards,
Sureshram

Source System Problem after System Refresh

Hi,
We have R/3 4.7 Test source system created in our SCM 2007 Test System. The source system check was OK.
The R3 Test system was refreshed with Production data few days back and now my source system is not working. When i perform Source System check it says:
BI unknown in source system
BI IDoc type ZSSB006 is not the same as source system IDoc type
I performed following steps in R3 Test system after its system refresh:
1. Created logcal system and created RFC.
2. Created port in trx we21.
3. Created partner profile in trx we20.
4. For the outbound parameter RSSEND, I had to create idoc type that should be same as in my SCM system i.e. ZSSB006.
5. Created idoc type using trx we30 as a copy of RSSEND and added entry in table EDIMSG. Now, i could also create outbound parameter RSSEND with idoc type ZSSB006.
After performing the above steps i also replicated the datasources for the R3 Test source system, but its still showing above error.
I also checked the RSBASIDOC table in SCM test system. It has correct entry for my source system. But there is no such entry in RSBASIDOC table in the R3 test system.
Someone pls help me.
Regards,
Chintan

Hi Chintan,
Can you please check IDOC in your Target system. It should be the same type. Better you do the Partner profile steps.
Also please check have correctly created the idoc in Inbound or Outbound.
Consider the case like if its exist in BW as Out bound then its connected to Inbound IDOC of R/3 and vice a versa.
Please elaborate your refresh activites. Normally IDOC setting never get changed in you refresh activites.
Just check your BW system patch level and search for Notes.
Regards,
Mahesh

Java Dispatcher Down but Server0 and SDM up after system refresh

Hello,
I have done system refresh from PRD to QAS of CRM system - dual stack.Once after the system refresh ABAP is up and running fine but Java is down (Only Dispatcher is down. Both SDM and Server0 are running fine).
I have followed Note 609603 - Problems with Multiple NICs and SAP J2EE Engine and have given the correct host name but the no luck..
std_dispatcher.out says the following error:
Cannot attach to the Message Server. Can't open port [3925] on host [<Source Host Name>/Source IP Address].
Could you please let me know if I need to do any changes in the Config tool?
Thanks,
Subbu

HI,
IN DB restore the hostname of java system stored in profiles would be your PRD.
Go to Configtool in Edit mode -- cluster --> change the hostnames in Instance profile -- and under other files like bootstrap etc whereever you find PRD hostname.
And otherwise for JAVA system you should use export/import option.
Regards,
Tajinder

Restore periodic batch job after system refresh

Hi all
I am going to do a system refresh and is there anyway to restore my periodic batch jobs after the system refresh or i need to reschedule all of them manually.Thanks in advance.

You'll need to do them manually.
Regards
Juan

Trusted system after system refresh

I was wondering if theres an easy quick way to recreate the trusted system in SMSY after a system refresh or should I create the recreate the trusted system manually?
Regards
Juan

Juan,
recreating manually is in my opinion the only solution.
you can:
- recreate the RFCs again starting from SolMan
- only recreate SolMan as a trusted system in your satellite system
good luck!
Roel
Edited by: Roel Beckers on May 27, 2008 11:14 AM

ITAB_DUPLICATE_KEY Error after system copy

Hi!
I am facing with the following error after the system copy of SAP ERP 2005 on Windows migrated from MS SQL to SAP DB.
By entering into the db-relevant tcodes (DB13, etc.) the following error appears:
Runtime Errors ITAB_DUPLICATE_KEY
Date and Time 24.05.2008 14:01:23
Short text
A row with the same key already exists.
What happened?
Error in the ABAP Application Program
The current ABAP program "CL_DB6_SYS====================CP" had to be
terminated because it has come across a statement that unfortunately cannot be executed.
Error analysis
An entry was to be entered into the table "\CLASS=CL_DB6_SYS\DATA=SYSTEMS"
(which should have had a unique table key (UNIQUE KEY)).
However, there already existed a line with an identical key.
The insert-operation could have ocurred as a result of an INSERT- or
MOVE command, or in conjunction with a SELECT ... INTO.
The statement "INSERT INITIAL LINE ..." cannot be used to insert several
initial lines into a table with a unique key.
Has some one any ideas how to solve the problem?
Thank you very much!
regards
Thom

Hi,
I am facing same problem for oppty component bt111h_oppt.
Error analysis:
An entry was to be entered into the table
"\DATA=VIEWS" (which should have
had a unique table key (UNIQUE KEY)).
However, there already existed a line with an identical key.
The insert-operation could have ocurred as a result of an INSERT- or
MOVE command, or in conjunction with a SELECT ... INTO.
The statement "INSERT INITIAL LINE ..." cannot be used to insert several
initial lines into a table with a unique key.
How to resolve this ?
Please help me.
Regards
Krishna
Edited by: krishna nadupuri on Jun 16, 2011 4:12 PM

PROD Application servers are reflecting after system refresh in ST03 of QUA

Hi,
We recently performed DB refresh activity from Source: Production to Target: Quality.
We have 6 application servers excluding our central instance in production system.But after the system refresh,we observed in ST03 that these production application servers are reflecting as nodes on the left hand side in Quality system after refresh.
Please help us how to delete those application servers in ST03.
Regards,
Sudheer.

I too face the same problem with our quality system after refresh.

Activating data in DSO got dump SAPSQL_EMPTY_TABNAME after BW system copy

Hi all,
We had an issue after system copy.
After a system copy the data in the standard DSOs(all of them) cannot be activated. The DOSs themselves are active, the transformations are active but if one attempts to load data and activate u2013 it does not work. The job terminates with shortdump SAPSQL_EMPTY_TABNAME.
Found the issue is caused by u201Cmore than one versionu201D of the change log.
We tried the Program RSAR_RSTSODS_CHANGELOG_VRS but it didn't work.
We had the solution like this:
After activating the DSO itself(the object) using RSDG_ODSO_ACTIVATE the issue disappears and the data can be activated. Issue also disappears. BUT Drawback: Activating the DSO causes the transformations to deactivate.Then we used the program RSDG_TRFN_ACTIVATE to activate all transformations. And then the issue disappeared.
Want to know what the root cause for this. From some SDN threads, mentioned BDLS job in the post refresh steps are not correctly done during system copy may cause this issue. How did the BDLS run wrongly cause this issue? And what is the exact correct way? We ran BDLS for each source systems inlcuding the target refreshed BW system itself by the default selection - conversion of Client-Dependent and Client-Independent Tables; because we used database copy
for the system refresh.
We also restored all source systems in RSA1 inlcuding the refreshed BW system own in the post-refresh steps.
Thank you very much for your information and suggestion.
Heming

Hi Arun, as you say two change log tables it´s strange. In fact in my opinion it´s not right but the problem is that the second change log table appears after executing std SAP report RSDG_ODSO_ACTIVATE in order to be able to activate the DSO. So the solution provided by SAP it works but i´m not sure if the right one. Besides this the original change log table is full of data while the second one is empty... for new loads which are gonna a be filled by the activation process ? I suppose the second one... will this have some impact with the data stored in the first one... not in theory but.... i do not feel confortable with the consequences of this report.
And the most important, it seems that the reason why the DSO and the change log table had problems is due to a some problems or missing steps after executing the BDLS after BW system refresh but nobody can confirm this point...
So, i´ve been able to solve the issue but now i have two change log tables for the same DSO.
Anybody has the same situation after executing the above mentioned SAP std report ?
Regards,
Joaquin Casas Baca-Castex

DTP error after QA system refresh

Similar Messages

Maybe you are looking for