CCMS_ONALERT_EMAIL with client 000

Hi,
I tryed to send an E-mail from the System by using the CCMS_ONALERT_EMAIL method in transaction [rz20].
I created a new method in [rz21] with the parameters:
sender: SAP*
recipient: .[email protected]
recipient-typeid: U
The problem is: the default client in our system is 001. I read I have to use a sender in client 000. Could I use the default user SAP* because I have no access to client 000 or the login failed.
I also need this client to set the SAPconnect (transaction [sicf])
The smtp settings in transaction [scot] should be right.
I have a process chain with a failure and tryed to send an Alert E-mail but notihng happens.
Are there other reasons?
Could anybody help me?
Thank you and best regards
Frank

hi al mamun ,
can you please explain how you configured the alert mail configuration in solution manager centrally .
i am assigned with this task .
but i dont know how to start and where to start .
can you provide me step by step configuration for this central ccms monitoring and triggering mails

Similar Messages

CCMS_ONALERT_EMAIL client 000

Good day all,
I tryed to send an E-mail from the System by using the CCMS_ONALERT_EMAIL method in transaction [rz20].
I created a new method in [rz21] with the parameters:
sender: SAP*
recipient: .[email protected]
recipient-typeid: U
The problem is: the default client in our system is 001. I read I have to use a sender in client 000. Could I use the default user SAP* because I have no access to client 000 or the login failed.
I also need this client to set the SAPconnect (transaction [sicf])
The smtp settings in transaction [scot] should be right.
I have a process chain with a failure and tryed to send an Alert E-mail but notihng happens.
Could anybody help me?
Thank you and best regards
Frank

Hi,
You have to create RFC to the work client from 000 only, and other clients will not work for this.
Because we will be giving the RFC in T-code SALRT1 in 000 client.
So please be sure that you use work client(001) and 000 clients only.
Regards,
Phani.

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

Configuring CCMS_OnAlert_Email with CCMS

Hi,
I have setup CCMS_OnAlert_Email with CCMS for transport alerts, I have also setup distribution list in client 000 but I got express message as "Cannot process message, no route from DDIC to DEV:<client>:<userid>", please let me know how to route DDIC to other client users.
Thanks in advance
KVR

I have configured in individual system, what CCMS background jobs run for transport alerts? I have configured CCMS alerts through DDIC in 000. I am assuming jobs will run with that user.
I don't have any other users so I have configured a distribution list for forwarding the alerts. But when I am trying to send a mail from SAP business workplace using distribution list I was getting above error.
Thank you

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

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

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.

Username passwords for client 000

Dear All,
I don't have credentials of SAP* DDIC in DEV QAS and PRD of client 000.
Can you please let me know steps to recover the passwords?
Please let me know the steps or ways . don't put external links
Regards
Nikhil

Hi Nikhil,
You follow below process to reset the password and login to your ABAP system
1) set profile parameter login/no_automatic_user_sapstar=0 in instance profile
2) Delete SAP* from database table from client 000
SQL> delete from <schema>.<USR02> where bname='SAP*' and MANDT='000'
3) Take restart of SAP application
4) Login to 000 client with user = SAP* and password= pass
5) Using this ID you can reset password for other users like DDIC.
6) Once You can login with DDIC , you may create SAP* again using SU01.
Hope this helps.
Regards,
Deepak Kori

Client Copy - Which source client 000 or 001?

I have a new SAP Netweaver 2004s SR1 ABAP+JAVA system with the following usage types:
SRM App
SRMLac
AS Java
AS ABAP
DI
MI
All the post-installation steps have been completed (including the CTC template configurations for DI and MI). The Java, DI, and MI have been configured against client 001. Now I want to create a new production client. The J2EE_ADMIN and users associated with DI and MI exist in client 001.
I want to create a new production client 010. Should I copy the users (SAP_USER) from client 001 and the customizing data (SAP_CUST) from client 000? Or, can I copy everything from client 001? There is a lot of conflicting information in the SAP Notes in regard to which source client to use.

You should not use a transport of copies for table USR02. Use client copy profile SAP_USER or SAP_UONL (without authorization profiles and roles).
And you should never copy customizing from client 001 to build up a new client. 001 happens to be a ordinary customer client which does not get supplied with changes SAP delivers after the release date. New SAP Netweaver 2004s installations use client 001 to file the user masters needed for the JAVA part. But this does not change the fact that client 001 is a customer client and should not be used as a template.
For local client copies you could use copy profile SAP_UCUS with source client 000 and source client user master 001 in one step. This has the same result as a client copy with SAP_CUST from 000 and SAP_UONL from 001 (i.e. thet authorization profiles and roles come from 000, when you need them from 001 you can either copy the missing individually or use SAP_ PROF in a separate step).

Can I get password for client 000 and user SAP*

Hi Experts,
Can get ur help for getting password for User SAP* for client 000 i.e SAP std. client.
please it's urgent.
Thanks & Regards,
Yogesh

Hi ,
If all the users are locked, they can be unlocked by
a)Try this command at ur sql plus query level
Go to cmd prompt.
Sqlplus /nolog
conn /as sysdba
this will take you to the sqlprompt.
Just execute the earlier commands there.
sqlplus>UPDATE SAP<schema>.usr02 set uflag=0 where mandt=<CLNT NO> and uflag=64; this statement actually unlocks the users of that particular client. So, try for every client in that sap system.
b) You can delete sap* user
Go to cmd prompt.
Sqlplus /nolog
conn /as sysdba
sqlplus>DELETE SAP<SID>.usr02 where mandt='CLIENT.NO' and bname=SAP*;
Note:-
After doing this restart the system. So, that a new user with the name "sap" gets generated with password "pass". Provided the parameter is set login/no_automatic_user_sapstar= 0 (Automatic user SAP is permitted).
regards,
kanthi

Difference between client 000 and 001.

Hi,
what is the difference between vclient 000 and 001 ?
Best regards

000: SAP standard client
This client is used to set up new "neutral" clients by client copy. Do not change or delete this client.
This is an SAP referce client
Every time an SAP system is installed the 000 client is created by default woth 2 users SAP* and DDIC. Transport configurations are always done from 000 client. (they can t be done in any other client and they have to be done with the user DDIC).
Other client like Customizing client, testing client etc are created form the 000 client. Similarly in the production environment also the productive environment client is copied from 000.
001: SAP standard client
This client is used to set up new "neutral " clients by client copy.
This is also an SAP reference client. No changes should be done in this client either
Do not change or delete client 000 or client 001.
Regards,
Prashant

Copy output type from client 000?

How can I copy output types from client 000?
Sincerely,
Ketan

Hello Ketan
What do you mean with output types??, is it a data element?, a parameter? Im lost!!
Hope I can help you with any ideas....
Bye
Gabriel P-

CCMS_ONALERT_EMAIL with client 000

Similar Messages

Maybe you are looking for