Client Copy Delta initialisation lost

Hi Guys,
We are planned to do client copy in testing every month, my question is what will happen to delta initiliazation.
Will delta init break between BI testing to ECC testing? We do client copy ECC prod to ECC testing.
Regards,
Anand

Hi There,
Yes, you may lose your deltas.
In fact, you may lose your deltas in production!
SAP recommends that that a BW - ECC combimation be copies as a unit.
The reason is that at a basis level, the systems know one another.
When the BW is copied, without the ECC system, two BW systems will try to use the same delta, causing 'inconsistancies"
I lost all my deltas in Production.
Get with your basis support, and make sure the understand
Note 886102 - System Landscape Copy for SAP NetWeaver BW
https://service.sap.com/sap/support/notes/886102
Good luck,
John Hawk

Similar Messages

Local client copy for delta changes

Hello Support,
We have requirement of copying data(local client copy) of last one month. This is a rrepetitiveactivity and has to be done once in every month.
For example, in DEV we have 3 clients 200, 210 clients. They make changes in 200 client and these changes has to be reflected in 210 clients. For changing 1 month data we can't perform client copy with SAP_ALL.
I have an idea that we can perform local client copy using TDMS 4.0 but can we do delta client copy?
So, my question here is
1. Can we perform client copy for specific selected data(by date, for eg last 30days) without deleting existing data?
2. We have step 'Start Deletion of Data in Receiving System' in Time Based Reduction scenario, can we skip this and continue proceed with client copy?
Thanks,
Uday.

Hello Uday,
SAP TDMS Time based reduction package copies the whole of master data and customization data along with the transactional data being filtered based on the Data Slice Date Provided.
SAP TDMS cannot be used for a Delta Copy to copy only a months data keeping the existing data in the system. If the requiremnt is to run every month, you could give an approritate slice date and transfer the whole data again using SAP TDMS which would include the latest one month data as well.
It is not recommended to skip the step "Data deletion in Receiver system" and then execute the SAP TDMS package. This can lead to issue during the transfer.
Regards,
Sreejith Rajashekaran

Client copy and delta initialization

Hello all,
We want to copy the source system, i.e. make a client copy.
Could you all please advise me what will happen with delta? Should I initialize again after the copy?
Please guide me.

Hi,
Before you do a copy, make sure that your deltas have been fetched from the DeltaQueue into BW and that no delta is pending. After the client copy, an inconsistency might occur between BW delta tables and the OLTP delta tables as described in Note 405943.
After the client copy, Table ROOSPRMSC may be empty in the OLTP since this table is client-independent.
After the system copy, the table will contain the entries with the old logical system name that are no longer useful for further delta loading from the new logical system. The delta must be initialized in any case since delta depends on both the BW system and the source system. Even if no dump 'MESSAGE_TYPE_X' occurs in BW when editing or creating an InfoPackage, you should expect that the delta have to be initialized after the copy.

Remote Client Copy - Ended in Erros

Hi Friends,
We recently performed a Remote client copy. What we normally do is we restore an latest offline backup of the Prod into an instance built exclusively for performing client copies into our QA system.
So if our actual PROD is ABC ( production ), the replica system is ADC. We restore latest backup onto ADC. Then from ADC we do a client copy onto AQC ( Quality ). We have n number of clients in AQC. When copying into a particular client we are facing this problem of 3 tables not being able to get copied. They are BKPF,LTAK and SOST. It happened twice that the Remote client ended with errors.
It says "Read or conversion error". The detailed error looks like below ;
TAB_COPY_R_CONTINUE LTAK WITH KEY:
I01 0000066362
Read or conversion error system: ADCT500 table: LTAK
ERROR: Internal error when inserting in table: LTAK
Internal error:      1,262,713         65,536 VERIFY_CNT
Process 00001 has copied data 25.02.2010 18:04:16
Read or conversion error system: ADC500 table: BKPF
Process 00002 has copied data 25.02.2010 19:09:00
Start: Recopy errors 25.02.2010 19:09:02
TAB_COPY_R_CONTINUE BKPF WITH KEY:
2100 5100019665 2008
Read or conversion error system: ADC500 table: BKPF
ERROR: Internal error when inserting in table: BKPF
Internal error:      6,948,636      1,777,664 VERIFY_CNT
Read or conversion error system: ADC500 table: LTAK
TAB_COPY_R_CONTINUE SOST WITH KEY:
OTF 34 000000019247
Read or conversion error system: ADC500 table: SOST
ERROR: Internal error when inserting in table: SOST
Internal error:      2,594,254        180,224 VERIFY_CNT
We approached SAP and they asked to do a DB reorg, run update statistics on both source and target and then re run the client copy.
Well DB reorg is a big activity so we just updated the statistics and ran again the "recopying errors" but still it is the same problem.
Can anybody please suggest something. Thank you.
regards
Vinod K

Hi Friends,
My apologies for coming back to you guys so late. I kind of was lost to find a solution for this.
Hi Sanujit,
The database logs dont indicate anything at all about this error or i am not able to locate them.
Rajesh,
There was a table comparison done for these tables properties in both source and target and everything looked ok and confirmed by the application.
At this moment we have anyway decided to go a fresh client copy again as lot of time has already passed and there would be differences in source and target tables.
But anyway could you please tell me the procedure to transport tables between source and target systems?
Hi Anil,
SAP iS ECC 6.0 and Oracle is 10.2.0.4.0
Thanks again for your time and pateince.
Regards
Vinod K

SWN_SELSEN not working in test client after client-copy

Hi all,
We are using extended notification without problem until test client was refreshed by client-copy from production client. In test client, report SWN_SELSEN did not generated notification even there are newly generated workflow items. Because of client-copy, I found that tables SWN_NOTIF, SWN_NOTIFTSTMP, SWN_SENDLOG, SWN_TIMESTAMPS are all empty in test client.
Please advise how to make report SWN_SELSEN back to work in test client. Thanks.
<< Additional information >>
(1) Run report SWN_SELSEN_TEST with test Case 5 - Simulate Send Only. After this, some entries were written to above tables. But test on new workflow item, the schedule report SWN_SELSEN still fail to trigger notification.
(2) Run report SWN_SELSEN_TEST with test Case 4 - Send One Message Only. It triggered notifications for all active workflow items and sent out several hundred emails including workflow item created in step 1. However, further test on new workflowitem, the schedule report SWN_SELSEN is still unable to trigger notification.
I think there may be something else missing, like the timestamp of delta. Please help.
Regards,
Donald

Hello,
I've experienced a few cases where stopping SWN_SELSEN and then restarting it helped to fill up SWN_TIMESTAMPS with proper values. How does that table look after you run it?
What is SWN_SELSEN_TEST?
Chck in SLG1 to get an idea of why it's not working. You can also run SWN_SELSEN in the foreground and debug it to see exactly where and why it goes wrong. Also check ST22.
regards
Rick Bakker
hanabi technology

Extraction failing after source system and client copy

Hi all,
We refreshed our source QA system with a copy of production. And basically tried to "restore" the connection from our BW QA system. Some of the datasources can be extracted from BW, others fail with an error of "No transfer structure is available for InfoSource 0COSTCENTER_ATTR in the source system".
Trying to do the same thing with RSA3 in the source system, works fine.
The strange thing is it works for some objects but not others.
here's what we did:
1. System copy from R3 Prod to R3 QA
2. Client copy with R3 QA client 300 -> 200
3. Restore connectivity in BW QA to the R3 QA system (Using RSA1 -> Source System -> Restore)
4. Now some objects can be extracted in BW, others fail as I mentioned above.
I have regenerated the transfer structures in BW and R3.
All of these objects that don't work seem to work in RSA3 on the R3 system but not in RSA1 on BW.
All the SAP documentation is geared to copying the R3 source system and then restoring connectivity between BW and R3. I don't think any of it involves copying the client in the R3 source system - which might be causing our problems.
We are using an SAP delivered PDF and note 886102 mainly for direction.
SAP PDF is "How to... System Copy in SAP Business Intelligence System Landscapes".
Does anyone have any ideas?
Thanks,
Kevin

Hi,
can you isolate somehow the kind of DataSource which works and those who don't?
Master data / transactional or client dependent and not, delta or full....
To which R/3 client is your BW connected? when you succeed loading the data, is it coming from the right client?
RSA3: do you run it specifying your BW client in the target sys field? does it make a difference if yes or if not?
Are your RFC connections and partner profiles all right?
Check some IDOCs sent by BW received in R/3 and vice-versa (RSSEND, RSINFO, RSRQST..). Load a hierarchy (via IDOC)... verify that your IDOC have the correct partner settings....
let us know
Olivier.
Message was edited by:
Olivier Cora

Error message: no valid initialization after client copy

Hi,
We recently did a client copy of our quality BW and R/3 systems from preproduction. In the 'new' clients we have problems with the delta process for 2LIS_13_VDITM. We get an error message that there was no valid initialization in the system, where in fact a valid initialization has taken place (everything from preprodcution was copied).
The source systems setting where corrected using BDLS, but the entries in R/3 tables roosprmsf / roosprmsc were still pointing to the old system. This has now been corrected.
One problem remains. There is no entry for 2LIS_13_VDITM in table RSSDLINIT. I suspect that this causes the error message. Can anybody confirm this ? Is there a standard way to add the correct entry (with the package number of the init package) in table RSSDLINIT or realign table RSSDLINIT with table roosprmsf in R/3 ?
Thanks in advance !

Hi,
After system copy. You will ahve delet your whole data and reload every thing.
In case you are getting dump when you double click infopacakge then delete your data source entry in RSA7 in source system and then go for fresh init load and then continue with delta load. Before goign for fresh init load you will have to first delet the init load entry.
This must help
Regards,
Rohini
Message was edited by: Rohini Garg

After client copy and import export, WebUI not functioning

Hi Experts,
We have copied the client MKH300 into the client MKH305. The client
copy was performed using SAP_ALL authorization.
After the client copy a client compare was performed and several
differences were discovered. BDLS was run and a custom program was run
to copy custom tables from MKH300 to MKH305. This program has been run
in several other client copy cases and there is no issue with it.
When logging into the WebUI in client MKH305 an error message is
displayed in the application log:
"An exception has occurred during program processing"
(Please see attached screen shot)
When looking into the details the following text is shown:
Diagnosis
An exception occurred during request processing. This was handled
centrally. It changed the program flow and the result of the request
probably contains errors.
Procedure
Contact your system administrator.
Procedure for System Administration
Activate checkpoint group BSP_WD_EXCEPTION_DISPLAY. To do this, use
transaction SAAB. If the error recurs, further details are displayed.
When the check point group was activated there was no more information.
The links in the Homepage are not correct even though the business
roles, config keys etc look the same between the clients.
Much customization seems lost for the WebUI although when comparing the
two clients' customization for the WebUI they seem identical.
The client MKH300 works fine so the intention was that MKH305 should be
an exact copy of that client, but that did not happen.
Could you please help me out.
Thanks!
Nagaraju

they are included in the xe server install ...you could try copying the executables but maybe that wont work if all the libraries arent present
failing that install the regular oracle client

Client Copy and Partner Profiles

Hi,
I have a doubt related to client copy and how it will affect the partner profiles.
We have a client which has quite a lot of partner profiles defined in it. Now the problem is that the Basis team is planning to perform periodic client copies on this System which will copy the data from another client say 010 to the client in discussion. My doubt is, when this happens what will happen to the partner profiles that are already there in the target? Will it be lost resulting in we creating it all over again? if so is there anyway to get around this issue?
I would appreciate any kind of input on this issue.
Thanks
Praveen

as far as i know a client copy is based on some parameter say it can be client copy based on master data, client copy based on application data etc. I guess partner profile is an application data so in tht case if client copy is done in its context no data will be lost.
just my thought, but please confirm on this with a BASIS team or try a post in the forum for Adminstration and BASIS.

Post installation Client copy

I installed SAP NetWeaver2004s SR2.000,001,066 client are automatically established.
Now I'm at client copy section in Installation document.
Is it necerrasy to copy 000 to new client use as production client. Why client copy?
Can not Client-000 be used as production client?
And what are the missions of Client-000,0001,066? What are the differences against each other?
Thanks.
Message was edited by:
Cemil Bozlagan

Hi
Client 000: SAP Reference Client (SAPR)
This client is shipped as an industry-neutral model company.
To create a new client, as recommended in this documentation, the SAP reference client (SAPR) should be used as the source client in the client copy procedure. The new client will then contain an executable system that can serve as the basis for further customizing, development, training, and testing.
During an upgrade to the mySAP software, client-dependent changes will be automatically updated in the SAPR. To reflect these changes in the other clients, the settings will need to be copied from the SAPR to the other clients.
The Implementation Guide (IMG) contains delta projects that highlight the changes between different mySAP releases. These projects can be used for distributing the new functionality to other clients and other systems in the landscape.
Client 001: SAP Sample Client (SAPS)
As stated previously, when the mySAP system is installed, the SAP reference client (SAPR) and the SAP sample client (SAPS) are identical. After the system has been upgraded, or additional languages have been imported, it is likely that the SAPR will contain customizing table entries and language-dependent text entries relevant to the new release.
The SAPS, like all other clients in the mySAP System, will not contain the new entries after the update. If this information is required in the SAPS, it will need to be transported with customizing transactions and the change management system.
Client 066: SAP Early watch Service Client (SAPE)
SAP provides a proactive support service for checking the performance of a customers system. This Early Watch Service (EWS) involves a survey of the customer system to check various performance criteria. A report is then compiled and forwarded to the customer with recommendations. These recommendations are aimed at improving system performance. The report should also alert the customer to potential problems, so that immediate, corrective action can be taken.
The SAP Early Watch service client (SAPE) enables SAP to remotely access the customer system. The client contains a user record that the SAP EWS personnel use to log onto the customer system and gather the necessary information. The user record only has the minimal R/3 authorizations necessary to allow the EWS to be performed. As the EWS personnel, survey an isolated client, it also protects the companys confidential data in the production (PRD) system.
Normally you copy a new client for the client 000. The new client will then contain an executable system that can serve as the basis for further customizing, development, training, and testing.
Yeh you gotta perform a client copy for making other clients. Its alwaez recommended and better to use client copy to make production client.
You can use various SAP Defined Profiles to perform client copy like SAP_ALL and SAP_CUST as per the requirement.
Hope the above explanation clears your doubt.
Regards
Sumit Jain
**Reward with points if useful.

Logical System and Client copy

Hi Gurus ,
             I just now finished ECC 6.0 successfully , I want to take the client copy . But i hacve one doubt , In client creation one TAB logical system is there , Kindly advice me how to create Logical system and steps .
Regards
Selvan

Hi Manjula ,
              Below i mentioned the full detail about the error .
    RFC destination for client copy in systems with Financials Basis     (FINBASIS) component.
The system could not find any suitable RFC destination for processing     for client 000.     This note also appears if an RFC destination was found but this does not     work.     o   RFC destination: FINBTR@ID3CLNT000     o   Error text: Error during the retrieval of the logon data     Proceed as follows to eliminate this error:
1. Start the wizard to create a new RFC connection     or perform the following steps manually:     1. Create an RFC destination with the target ZK>source client of client         copy (in this case 000).
2. Check whether the RFC destination works in transaction SM59.         To avoid errors when assigning the password or the authorizations of         the RFC user, use the authorization test Test -> Authorization.
3. Enter the RFC destination:         -   Transaction: FINB_TR_DEST (Destinations for Transport Methods of             the Financials Basis)         -   Client: 000
4. Start the client copy again.
Kindly advice me
selvan

Client Copy from BWP to BWT

I had a problem with my List Cube Transaction and for that reason, I had a look at the Infoprovider and also the Data Sources.
When tried to execute the infoproviders in LISTCUBE, the following messages are being displayed in BWT system:
1. Error reading the data of InfoProvider ZIP_RC_01
2. There is still no data source assigned to VirtualProvider ZIP_RC_01
But, when executed the same in BWD, then it is working fine.
I have checked the Data Sources in the R/3 Dev system and the DS has no problem. But, when I check the DS in the R/3 Prod (SS in BWT system), the following error message is displayed in the status bar:
"DataSource Z_IP_RC_DS_1 is not defined in the source system"
I thought, as the system says the Source system is not available, hence the problem in LISTCUBE and thought if we transport the DS again and then replicate in BW, then our problem would be resolved.
But, seems that even though the source system says "PRD300", if I look at SM59 it actually points to our QAS system. It says PRD300 because BWT is a copy down from BWP, and that's the source system we use - in other words the logical name is the same, but the actual servers are different.
In any case, the datasource is transported to our QAS enviroment.
So, once we do a client copy from Prod to Test, even the source systems get copied. If yes, then does it really affect in case of replications and transports???
I am really confused in this part...please explain.
Thanks & Regards

Hi,
It looks like the basis team, or whoever performed the Copy from production to QA box hasn't finished all the necessary Steps :
Main transaction to know:
SSC4 -> To create new client
SCCL -> Client copy within local system
SCC9 -> remote client copy
SCC3 -> display client copy log
http://help.sap.com/saphelp_nw04/helpdata/en/69/c24c4e4ba111d189750000e8322d00/content.htm
http://www.sap-basis-abap.com/bc/client-copy-from-production-to-quality-server-to.htm
http://searchsap.techtarget.com/tip/1,289483,sid21_gci552257,00.html
Probably sounds like transaction BDLS hasn't been done.

Client copy with configuration data in R/3. Is there any effect on EBP sys

Hi all,
We are using classic scenario. Our client is reorganizing their Org structure for that we need to do client copy with only configuration data.
In this scenario we are uploading the master and transactional data through ALE in order to retain the same number ranges and the same data in EBP system.
My doubt is when we do config steps Define logical system and assign the logical system to the client and define Idoc message types etc... Is it necessary to run BBP_LOCATIONS_GET_ALL job. If yes the same data like Plant and storage location and all master data will override the existing data or not. And what about the open Purchase orders and open goods receipts.
Can you please reply immediately. It is very urgent.
Thanks in advance

waiting online

Unable to log in to newly create client copy

I 'm attempting to create a new client from a newly installed ECC 6.0 IDES system. I go into SCC4 and create a new lient '200' and log off.
I try to log in to client 200 using sap* and pass and get wrong username or password error.
I can see the client listed in scc4, but can't log into it.
Any ideas?
Bob

Hello,
Having the previous question answered helped alot, but I do have another question:
Can I put the client copy on a different drive than the original?
I have SAP installed on the E: drive and would like to place the new copy client on the F: drive, can I do that?
Bob

Remote Client Copy Errors

Dears,
Today I am going to do remote client copy from PRD to QAS.
For it yesterday i scheduled Test run in simulation mode.As i am having two CPU for both Dev and PRD so I scheduled it with 6 Parallel Processes.
But my Test run failed with errors:
Copy Type                   Remote copy
                                  Test Run
Profile                          SAP_ALL
Status                          Ended with Errors
User                             SAP*
Start on                        14.08.2008 / 01:30:54
Last Entry on                14.08.2008 / 05:57:54
Statistics for this Run
- No. of Tables                 30,806 of       30,808
- Deleted Lines                     15
- Copied Lines               72748,776
Warnings and Errors
Table/Object       Component                Error
BKPF                 FI                       Read or Conversion Error
BSIS                   FI                       Read or Conversion Error
Thus showing read or Conversion Error in these two tables.
In System log of source system I also see these error:
ORA-01652 unable to extend temp segment by 2560 in PSAPTEMP
Database Error 1652 at SEL access to table BKPF.
Database Error 1652 at SEL access to table BSIS.
Please suggest how to resolve the issue.
Shivam
Edited by: Shivam Mittal on Aug 14, 2008 6:08 AM

Hello Shivam
How is your remote copy going on?
Did you increase the size of psap temp in order to carryon with the copy?
Your Source system is PRD system.Are you doing this copy while users are using the PRD system.
If not then this may not be result of client copy? or
if no user is logged in in your PRD system,You have to decide if this is due to client copy.
Let me know what corrective measure taken by you to completed the remote client copy?
normally we dont get this dump in the source system but I have psaptemp around 30 GB or more in al my systems so may be this might have not surfaced in my environment.
Thanks
Amit

Client Copy Delta initialisation lost

Similar Messages

Maybe you are looking for