Client 000

Hi,
Why do we need to apply support package thru client 000? Why can't we do it thru some other client?
It was an interview question.
Is there any specific documentation or note about client 000 and why do we need to use client 000?
Regards....Iyy

Hi
Client 000 is a SAP define client and client independent if change in client 000 it will effected all clients
http://help.sap.com/saphelp_erp2004/helpdata/en/a7/a7a932845c11d2b421006094b9ea64/content.htm
Rewards point if helpful
Thanks
Pankaj Kumar

Similar Messages

Assign Logical System to client 000

I need to install Bw at SAP ECC 6.0, in doing so on the client 000 with the transaction RSA1, present the message that should be assigned System logical customer 000, it does not bring inconvenience to any future activity,
Thanks

Hi Victor,
If you're installing BW you shouldn't use cleint 000, create a new client...
Once you create the client go to transaction SALE and You'll see Create logical system ans assign logical system in the list.
First create a new logical system for the client to use... then assign the logical system to the client.
Regards
Juan
Please reward with points if helpful

Logical Systems for client 000 and 001

I've just install solman 7.0 ehp1 sr1 and am going to create a new client from 001.
Do I need to create logical systems for clients 000 and 001?
Do I need to creat rfc's for these?
Thanks,
Daniel

no, no need.
you will create a logical system name for the copied client (such as 100)

RFC_NO_AUTHORITY error for user SAPSYS in client 000

Hi
I have a lot of abap dumps in ST22 RFC_NO_AUTHORITY error for user SAPSYS in client 000 for today which I'm not sure what they mean. I don't have a SAPSYS user in client 000.
The reason that I'm concerend is we had an incident with the SAP server last night where it became unresponsive about 2.30 am and had to be manually rebooted this morning. The R3 jobs all ran OK but the BW loads failed and had to be re-run this morning. There were no unusual jobs or programs running last night and the Server Event Log does not contain any further information as to the probable cause of the problem.
I'm not sure if this error is related to the BW jobs running and was wondering did anyone come accross it and what it means.
Thanks
Siobhan

Check notes 944615 and 93254.
Rich

Autoreaction doesn't work from client 000 but works from other clients

Autoreaction doesn't work from client 000.
More details coming.   Having trouble getting the thread to post.

We set up a new local auto-reaction.   This is not a central auto-reaction. The auto-reaction writes a
message to the UNIX system log /var/adm/messages when a "Security"
alert i.e. - Logon, RFCLogon, TransactionStart, etc. occurs.
The RZ20 alerts are being properly generated and can be seen in both
the CEN system and the local system. On the local system if I view
all alerts for the MTE using transaction RZ20 and select one of the
alerts and choose Edit -> Nodes ( MTE ) -> Start methods -> Start auto-
reaction method. The auto-reaction writes the message to the UNIX
system log. If I execute the same procedure in client 000 nothing is
written to the UNIX system log.
I've also tried triggering a new alert and running SAPMSSY8 from SE38
while the alert is still in status ACTION_REQUIRED. If I do this from
client 010, an entry is written to the unix system log. If I do this
from client 000, nothing is written to the unix system log. In both
cases, the status of the alert changes from ACTION_REQUIRED to ACTIVE.
Since the System Cyclic program ( SAPMSSY6 ) that triggers SAPMSSY8
always runs in client 000, the auto-reaction never writes the messages
to the UNIX system log.
I have been working on this issue for days. There are several posts and notes relevant to a similar situation with e-mail alerts that are not working from client 000 because SAPCONNECT is not set up in client 000.   However, this auto-reaction does not send an e-mail, so SAPCONNECT set-up should not be necessary.   I've searched Service Marketplace and could not find any notes that resolved the problem either.
I've also checked CCMS Self-Monitoring and cannot find any alerts or errors relevant to this problem.
Does anyone know why the auto-reaction only works from a client other than client 000?
Best regards,
Dave

Error: The sap bw system must not be operated in client 000

Hi
I login as a client "200" and create new user "imran" and then login as a client 200 and user imran successfully but when I goto T.code RSOR it shows "the sap bw system must not be operated in client 000" when I check the status it shows client 200 and user imran.
so what is the solution??
Regards
Imran

hi
Yes I create new client "200" in a sap* then I login as a client "200" user "sap*" and password "pass" then create new user "imran" using copy DDIC then login as client 200 and user imran but result is same.
Edited by: iskhan on Nov 5, 2009 7:24 AM
Edited by: iskhan on Nov 5, 2009 11:36 AM

How to copy tax procedure TAXINJ from Client 000 to Dev client in ECC 6.0

Hi,
We are facing a problem for TAXINJ and TAXINN procedure, which are not available in our development client, but available in client 000.
Please advice how to copy those procedures from client 000 to development client.
(In client 000, we can not create a trabnsport request).

Hello ravi,
first check whether there request being generated at the time og customization in the server where the standard procedures exist.
if yes,then you just need to change a little bit of description of these procedures and save system will ask for the development request or customization request.,you can then ask the basis guy to transport it.
remember it is only a work around solution.
nevertheless you can also create it manually
revert if helpful
Mohit Singh

Transport of modifications with ChaRM in client "000"?

Hi,
I do have a typical logical component DEV:100 -> QAS:100 -> PRD:100.
For standard customizing and workbech tansports all is working fine.
Now I have done a modification on a standard SAP object. Therfore the system wants to have a transport for client "000".
But with standard ChaRM I only user the typical logical component with the standard transport routes for client 100.
Does anyone have had a similar problem or a solution for that?
To change the system in the transport does not work, because SolMan does check the ChaRM related transports within a special table.
The only solution, which is in my mind, is the use of a second logical component for client "000" to do the modifications.
Thanks for any help.
Regards,
Alex

Agree with you Alex. For defining multiple routes in ChaRM, you need to define different logical components and assign them to the maintenance cycle.
Rajeev

Client 000 has status not modifiable

Dear all,
after installing ABAP and JAVA stacks I can normally
work in both system (NSP, J2E). I created a RFC function module via se37 to use it as a basis for a web service.
But when I try to release my web service for SOAP runtime using TA WSCONFIG I always get an error message: <b>Client 000 has status not modifiable</b>...
Are there any restrictions or did I make a mistake?
Thank you

hi Harald,
Did you make a client copy after your ABAP installation? SAP doesn't allow you to work on 000 client. so you need to make a copy of 000 (say 111 or any other number)and continue to install your JAVA Stack on this CLIENT. i guess you had put your JAVA stack on 000 itself. that's the problem.
Just make a new client or "Client Copy". and Put a java stack on that client. Remove the old java stack. This should solve your problem.
Regards
Arun

Client -000 - locked

Hi,
We have not used Client-000 - SAP*/DDIC accounts recently and it got locked while trying to logon. Is there anyway for the Basis admin to unlock and reset the password.?
Thanks,
Sam

Thanks..!!
For benefit of others...
http://www.sap-basis-abap.com/bc/forgot-password-for-user-id-sap-in-client-000.htm

Client 000 for BW

Hi
I have installed SAP Netweaver2004s but I am restricted to 000 for BW . I have create 2 more clients but system does not allow me to run RSA1 other than Client000.
Please Tell me the detail of SAP NTWeaver2004s regardingf BW .
Does it me to say that we dont need a separate BW server and all the functionalitties is available uin Client000. What are the prerequisites to start work in client000
If anyone have some good docs plz email me
[email protected]

Some details on Client 000....
each client has a some specific purpose
000 - Administration Purpose,
001 - Test Purpose
066 - Early Watch or SAP Remote Services
Check:
http://help.sap.com/saphelp_nw04/helpdata/en/7e/c8189452c511d182c50000e829fbfe/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/6c/a74a3735a37273e10000009b38f839/frameset.htm
Also see :
Re: LIS DATASOURCE
hope this helps..***
assign points if useful ***
Thanks,
Raj

Client 000 & 001 ?

Hello all,
I would like to know
1) What is the diff between clients 000 and 001?
and what is use of 001?
2) What is Transport domain and Domain controller?
pls explain me
points must be rewarde
regards
Gajendra

Hello Gajendra
Just to finish off your questions...
What is Transport domain and Domain controller?
A transport domain is a group SAP Systems that are managed jointly by the same Transport Management System. So you have your test environment, QAS and productive as part of a Transport Domain.
Certain system settings are the same for all systems within a Transport Domain, such as the transport routes. To achieve this, one SAP System in the transport domain has the reference configuration, with all other SAP Systems in the transport domain taking copies of this reference configuration. The system with the reference configuration is known as the Domain Controller; only in this system can you make changes to the reference configuration. Each time you change the reference configuration, you must distribute the new configuration to all systems. The TMS automatically generates RFC connections between the systems in a domain so that they can communicate.
Hope this helps
Regards
Ken

Client 000, 001 and 066

Hi everyone,
Pretty new to SAP.
I am struggling to find answers to the following questions:
How do you use client 000, 001 and 066?
Apart from initial installation and support (066) can theses clients be used in development, testing and production environements?
Can 000 and 001 be used as working clients or should they only be used as template?
What should their configurations be when using SCC4 for each system inthe landscape: DEV, QA and PROD (and Solution Manager)
From a security point of view, once SAP*, DDIC have been secured should they be any other users (Dialog, System) in these clients?
Sorry quite a few questions but if anyone could give me direction as I am trying to understand if some of our current settings are correct and if not why.
Thank you

Hi Corinne,
Even though it is a very basic question, it is very essential to understand and find an answer to your questions.
Client 000, 001 and 066 are (as you know) standard clients thats pre-built when you install SAP.
"Apart from initial installation and support (066) can theses clients be used in development, testing and production environements?"
Answer: No, they cannot be used for development, testing or production environments. When I say, "they cannot", I mean they are not supposed to be used.
"Can 000 and 001 be used as working clients or should they only be used as template?"
Answer: Client 000 is basically used as working client only when you do support pack upgrade or ABAP load generations (SGEN) and implementing additional languages, etc. Otherwise, client 000 should not be used as a working client. The same applies to client 001. But the only exception with 001 is, with Solution Manager, 001 will be your working client. You will do all configurations and obtain support from SAP through this client. With other Systems like BW and CRM, this client (001) will not be a working client.
"What should their configurations be when using SCC4 for each system inthe landscape: DEV, QA and PROD (and Solution Manager)"
Answer: In the production system - "Changes and Transports for Client-Specific Objects" should be set to "No Changes allowed". "Cross Client Object Changes" should be set to "Changes to Repository and Cross-Client Customizing Allowed". "Protection: Client copier and comparison Tool" must be set to "Protection Level 1: No Overwriting". Same applies to Quality System and Development System. These are by-the-by default settings also when you install the system.
"From a security point of view, once SAP*, DDIC have been secured should they be any other users (Dialog, System) in these clients?"
Answer: Once you install the system, you must first make a copy of DDIC to any user you create in your name or any standard name. Never use DDIC when you do initial settings after the installation.
The following link might be of some help to you.
http://help.sap.com/saphelp_nw2004s/helpdata/en/7e/c8189452c511d182c50000e829fbfe/frameset.htm
Hope this helps.
Thank you.

SolMan 7.1 SP10: Managed Systems Configuration: client 000 OK, client 100 error

Hello,
after installing SolMan 7.1 SP10 successfully I also completed the steps "System Preparation" and "Basic Configuration".
Now I'm connecting the managed ABAP systems to the Solution Manager by performing step "Managed Systems Configuration".
After several other ABAP systems I'm now connecting our productive CRM 7.0 EHP1 system "CM3" (SAP_BASIS 702).
I also connected the CRM development and CRM quality assurance system without a problem.
For client 000 everything worked fine, the RFC destinations were created and a green light is shown.
Now the problem is to connect the productive client 100:
The log for Activity RFC Connection says:
The corresponding dev_rfc tracefile says:
**** Trace file opened at 20140326 164911 W. Europe Standard Time, by disp+work
**** Versions SAP-REL 720,0,523 RFC-VER U 3 1468763 MT-SL
======> Name oder Kennwort ist nicht korrekt (Wiederholen Sie die Anmeldung)
ABAP Programm: SAPLSM_SETUP_API (Transaction: )
Called function module: FUNCTION_EXISTS
User: SOLMAN_ADMIN (Client: 001)
Destination: 0050568713C71ED3AD9FC4F78AC9D9EB (Handle: 16, DtConId: 27FEB4E356BCF14F99EB0050568713C7, DtConCnt: 1, ConvId: 64734943,{27FEB4E3-56BC-F14F-99EB-0050568713C7})
EPP RootContextId: 0050568713C71ED3AD9FB7AD4C4859EB, ConnectionId: 0050568713C71ED3AD9FB784232C59EB, ConnectionCnt: 1
EPP TransactionId: BDFDB4E3626AF14899EB0050568713C7
But both users taken to execute this step (SAP Solution Manager Administrator "SOLMAN_ADMIN" and Managed System Configuration User "SM_ADMIN_SM3") exist and have the correct provided password.
Does anyone have a clue?
Kind regards
Rüdiger Höckel

Hello Ranjith,
thanks for your quick response.
The ST-A/PI software component is the same on all systems: 01Q_700 #2.
SolMan system: SM3
CRM systems: CM0 (ok), CM1 (ok), CM3 (problem with client 100, client 000 OK).
I also tried the recommendation found in the SAP Community Network
(http://scn.sap.com/thread/3483642) but this didn't help either:
1.Delete system from LMDB.
2.Delete system from SLD of solman.
3.Re- register the system to SLD of solman(rz70 for AS ABAP)
[the LMDB synchronizes with the SLD every 10 minutes, system CM3 is visible again in the LMDB]
4.Now follow the steps in managed system configuration.
The wizard worked fine for client 000 but throws this error for client 100.
I use all the latest installation and configuration guides.
For this step I'm using the guide "Managed System Configuration" that is available in the SOLMAN_SETUP wiki.
https://websmp206.sap-ag.de/~sapidb/011000358700001120342013E.pdf
Kind regards
Rüdiger
P.S. In total I have already connected eight systems (SAP_BASIS 700 to 731) but this is the first system that gives an error.

How to reset ddic password for client 000 in MSSQL 2005 database

SAP = ECC6
DB = MSSQL 2005
client = 000
1. SAP* account was removed from the DB, can't be found in USR02 table.
2. Only left ddic account and was locked. How can i reset ddic password?
3. How can i unlock and reset my own password from the MSSQL database?

You can unlock and reset passwords for DDIC and for your own user id in the following way:
Please execute the below queries at your database level:
To unlock user ids:
SQL>update SAP<SID>.usr02 set flag=0 where bname="*user id*" and mandt=client number;
SQL>commit;
To reset the passwords:
SQL>update SAP<SID>.usr02 set bcode="encrypted password" where bname="*user id*" and mandt=client number;
SQL>commit;
Then log into the system and execute /$sync
hope this will help you.
Regards,
FAisal

Client 000

Similar Messages

Maybe you are looking for