Client Copy steps..in SRM5.0

Hi
any one tell me the newly created client default password (like sap*/pass..).. and also Some Important Transaction codes..
Thanks

Hi guys ..
Procedure
1. Maintain the new client with transaction SCC4.
2. Activate kernel user SAP*:
a) Set the profile parameter
Login/no_automatic_user_sapstar to 0.
b) Restart the application server.
3. Log on to the new client with kernel user SAP* and password PASS.
4. Copy the client with transaction SCCL and profile SAP_CUST.
5. Check the log files with transaction SCC3.
6. Deactivate kernel user SAP*:
a) Reset login/no_automatic_user_sapstar to 1.
Caution
You create SAP system user SAP* on the new client
before resetting
login/no_automatic_user_sapstar.
b) Restart the application server.
rgds
echo

Similar Messages

Pre-Client Copy Steps

Hello All,
I am really confused with the application data & customizing data..What are the differences between these 2??I have to perform a Local client copy so what pre client copy steps I need to perform??

Ashley,
Following link will help you.
[http://help.sap.com/saphelp_sm32/helpdata/en/ff/9be1817d811c41985662da25061f98/content.htm]
Manoj

Steps should be taken to make a client copy say from dev to test using BDLS

Some one help to write up on real situation at any client site...by BASIS group
for SRM box..
Say client num in Dev is 100
and we want to copy all that to a test box where the client number is 101...
initially client 100 SRM box is pointing to R/3 say dev box 201
the new R/3 box is 202. And we have to point the 101 to 202. So I am just wondering the steps
taken by BASIS group to build the test env. 101 ---> 202

Hello,
we had experienced some problems during client copy with SRM in our earlier project.
I am not a basis guy but i can give you some hint for yr situation:
- Copy R/3 client 101 to 202 with the profile SAP_ALL
- change the SID with BDLS
- Copy SRM client 100 to 101 with the profile SAP_CUST
- change the SID with BDLS
- Now download the masterdata from R/3 to SRM
SRM client should never be copied with SAP_ALL profile because ,if done so the logical system for product masters is copied that of old client.
This creates total chaos and nothing works.
BR
Dinesh
reward if helps

Is there any step necessary to be takan after remote client copy

Helllo
I wander generally is there any step necessary to be takan after remote client copy
Thank you in advance

Hi Sunny,
What about changing "Logical System Names", is it not necessary after a remote client copy.
Thanks
Ahamed

Pre and post steps of client copy

Hi,
There are some client copy official guide?
I was reading the help.sap.com, but in this guide not appears the pre- and post- steps of the client copy.
More thanks

>>If i use the copy profile SAP_APPL, this steps will not be necessay,no? The user master data from target system will be maintained.
Yes. You are right. This Profile will not over right the User Master Record. It is given on the document.
http://help.sap.com/saphelp_nw04/helpdata/en/99/0a2a887e2511d2a6250000e82deaaa/content.htm
Regards,
Subhash
Edited by: Subhash.Chandra on Jun 3, 2011 3:18 PM

Which action is the first step ,client copy or package?

i do ehp3 add-on. one system is copy client first,add-on later . Another system is add-on first then copy client .
To my surprise, to client compare is inconsistent.
why ? please give me answer.

As i understand the question is You have two system, and on System A you have upgraded the EHP3 then you copy the client and on System B You have first copy the client and then upgrade the EHP3 and the client size is different. So you want to know what should be done first? Either upgrade or Client Copy.
If this is the question then on my opinion Upgrade should be done first and later on client copy can be performed.
Regards,
Subhash

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

Client Copy back-end system

Hi Guys,
We have made a client copy of the back-end system of SRM (SRM 5.0). Only the back-end and not SRM has been copied.
After replication all the master- and customizing data again to SRM from the 'new' back-end I have found an issue with updating the suppliers.
It seems that I can not remove old business partners from SRM with BUPA_TEST_DELETE if these are used already in SC's. However the new copy of the back-end system has completely different suppliers we need to use in SRM. This causes for an inconsistency with the supplier numbers, as we want to keep the R/3 numbers in SRM.
Does anyone has a good idea how to proceed? That is, how can I remove the business partners (suppliers) in SRM which were used before the client copy of R/3, so that I will be able to completely get all the relevant 'new' vendors from the R/3 system after the client copy.
When I execute BUPA_TEST_DELETE it will end up in error saying the suppliers can not be removed. Do I need to archive all the old documents (SC & PO) before I can remove all vendors in SRM, or is there a way to force the removal of all the business partners from before the back-end client copy?
Thx.
Skander

Hi,
I already figured out how to solve the issue.
For anyone who wants to know how to:
-First clear the vendor groups in the vendor hierarchy; do not renove the root node
-Then run BBPGETVD which will get you the new vendors from the back-end; for me only role LF for suppliers.
-Then run BBPUPDVD which will update all the fields for the old business partner numbers in SRM which were used in documents, and replicated from the old back-end system.
In my case I had to play a litlebit with the setting 'only creditors', to update BP numbers which were not suppliers in the new back-end.
After performing these steps everything should be fine.
So it's perfectly possible to make a client copy of only the back-end system without copying SRM (in the classic scenario that is).
Rgds,
Skander

Error while doing client copy

Hi Gurus,
i have to copy my all data(all modules master data) from client 300 to 900 within the system. i have created a client 900 thru scc4, then logged in 900 with user sap* and passwd "pass".then sccl while scheduling this in background...i am getting a error window which as follows..it says for creation of RFC..
RFC Destination for client copy in systems with financials basis (FINBASIS) component.
The system could not find any suitable RFC destination for processing the client 300.
This note also appears if an RFC destination was found but this does not work.
0 RFC destinations: FINBTR@RPDCLNT300
0 Error text: 900
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 300).
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: 300
4.     Start the client copy again.
what i have to do..?? in which cleint i have to create RFC ..??pls help me out in this situation.
Thanks & Regards,
ACS

SOLUTION:
Login to client 300
Go to sm59, create rfc connection type 3, give the rfc destination : FINBASIS_300
Logon and security--> give user id and password (of any user in client 300)
create any service type of user:(user should be a service user or communication user so as to avoid password lock situation) in 300
Check Test connection: test ---à authorization test.
Login in to new client: 900
Run the tcode: FINB_TR_DEST
Click on new entries:
Give the client: 300 and destination as FINBASIS_300 and save .
Run Tcode: sccl make client copy

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

Data migration from one DEV(DE1) system to other DEV(DE2) BW system using client copy or client export import

HI SAP Gurus,
Please find the below details:
SAP NetWeaver 7.3
We have to copy all customized or developed BW objects like master data, DSO's , Infocubes , Reports etc.
We need only the design changes but not the data within the DSO or cubes that exist .
We have tried below procedure:
1) Taken export of DE1 source client 400 with profile SAP_CUST
2) Imported transports generated for above export into DE2 target client 350.
3) Executed transaction SCC3 and performed post processing, post processing was successful . Still we are not able to see DSO's, infocubes ,reports.
Please lets us know what we need to do to fulfill our requirement.
Thanks,
Avadhesh
+ 91 8095226536

Hi Basis,
Please refer to below documentation on how to perform system copy in BI systems
How to System Copy in SAP Business Intelligence System Landscapes (NW2004)
Post processing steps for SAP BW system copy or db copy
BI systems has mostly cross client objects. So client copy with SAP_CUST profile will not serve your purpose.
Hope this helps.
Regards,
Deepak Kori

Audit Issue in QA after system restore and client copy

Hi Experts,
We have an audit issue and need your advise on that.
Our QA system was audited and auditors were looking for the approval tickets on which a user was created. I found that several users that were not created in QA and do not even exist in QA have their change logs in QA showing that user was created.
I researched it and found the steps that Basis and DBA's do when creating a new QA client.
1. Basis export user master and authorizations using SAP_USER profile from the target QA environment.
2. Then DBA's restore the QA Environment from the Production Backup.
3. Basis import back the preserved User master and roles using SAP_USER profile.
But when reading about this profile, I came to understand that change documents ( USH* ) tables are not exported and imported back. So that is why we have change logs in our QA from Production system.
So my question is how to solve this issue, where Auditors look at the change documents in QA and ask for the documentation though in reality these change documents are coming from Production. Should we ask for DBA team to truncate USH tables or is there a client copy profile that saves the change logs that we can export and import back.

Hi,
as you know the USH* tables belong to delivery class L. The tables in this class are never copied during client copy but you don't do client copy. Idea of deleting records from L tables after backup restore does not sound good because you will loose all data. As a workaround you could backup content of tables with delivery class L, export users SAP_USER, restore production backup, import users and import backup for tables with delivery class L. There is around 5000 L tables in ECC. Another approach could be to restore production on different box and do proper client copy to QA system.
Cheers

Client Copy in BI 7.0 and ERP 6.0

Hi
I have done a system copy of both the BI system and it's source ERP system and am following the post copy steps to ensure that the connectivity between the two is maintained. However before I run BDLS to change the logical system names I would like to change the client numbers on both the BW and ERP client. Does anyone know what the implications of doing a client copy in both systems is and then running BDLS for these logical system names? Has anyone tried this and was it successful? Can you do a successful client copy of BI?
Points awarded.
Thanks
Leigh

Hello,
Have a look at these OSS
SAP Note 446294 CC INFO: Logical system name and client copy
SAP Note 793717 Client copy into the BW client in Netweaver/mySAP ERP
SAP Note 103228 Naming the logical system
SAP Note 886102 System Landscape Copy for SAP BW and NW BI
SAP Note 307018 Convert partner name w.respct to logcl systm name
SAP Note 325525 Copying and renaming systems in a BW environment
SAP Note 325470 Activities after client copy in BW source systems
SAP Note 369758 BDLS: New functions and better performance
SAP Note 1148403 70SP18: BDLS after early replication
SAP Note 932032 BDLS: specific conversion for large tables
SAP Note 1059278 70SP15: Error in transaction BDLS
Also see,
Ex[Execute conversion of logical system names (BDLS) in short time and in parallel - Intermediate|Execute conversion of logical system names (BDLS) in short time and in parallel - Intermediate]
SAP Note 121163 BDLS: Converting logical system names
SAP Note 931029 Transformations are not taken into account (BDLS)
SAP Note 187297 Changing the logical system name in table T000
Thanks
Chandran

Client Copy steps..in SRM5.0

Similar Messages

Maybe you are looking for