Hi,

In schedule manager transaction SCMA. When choosing Other Tasklist in the menu, a pop-up with all the tasklist cycles including completed ones are visible to select. Is it possible to have only the active tasklists visible in this pop-up?

Best regards,

Kim Lai

Hi All,

When I replicate a new transaction type from SMIN into (let's say) ZMN1, by default SNRO CRM_INCDNT still being used in that new copied transaction type. I know that I can change the internal number range from (default) '01' to something else 'Zx'.

It is also clearly explained in this article.

However, I would like to know if I can change the number range object from CRM_INCDNT to another new custom number range that I defined. How can I achieve that?

Also, what is the impact (probably the the shortage?) if I use a custom SNRO compare to default SNRO assigned by SAP?

Appreciate your feedback.

Thanks,

Dinivian.

Dear Expert,

I have created a support message successfully through the sap portal version 7.31

But the created message does not have correct name of Reported by user in sap solman system version- 7.1 field assigned.

Continuously one user name is comeing in field "Reported by" while successfully support message created.

For example:

Suppose have portal user have xyz,PQR and mnm.

I loged into the portal with user PQR or mnm and create the support message successfully through the sap portal.

When am going to sap backend solman system,while checking each and every things are fine but "Reported by" field showing xyz name in Reported by field but I have created support message from user PQR ,If I create support message from any users always reflecting xyz name in Reported by field.

For you info xyz is portal admin ID,hvae done config from this ID only.

Please suggest to me that where am missing config level sap portal end or sap solman system end.

Thanks and Regards,

Sam

Hi Everyone, We have implemented ChaRM in SolMan 7.1. Our Project Managers are asking for a report that shows un-released tasks.  I can see the transport/task relationship on CD's in Transport management section in ChaRM but cannot find a way to build a report for them.  We've looked at /TMWFLOW/REPE70O and /TMWFLOW/TRTASK tables for instance but there are missing entries we see on CDs and not in the tables, and entries in the tables we don't see on the CD.  Is there a way we can put this report together so it matches ChaRM?

How can I Unlock a document by a user that is no longer an active user.

Thanks

Sophia

Hi Experts,

I have recently activated Technical Monitoring for one of our ECC System, But it returns Grey status for all Host related metrics.

PFB steps and details of Systems

SAP Solution Manager 7.1 SP11 System, To resolve this issue i have performed below steps as well.But still no luck.

1. Upgraded the Diagnostics Agent of Solution Manager.
2. Solution Manager Host Agent was upgraded.
3. Host Agent of Managed System upgraded.
4. LM-Service of Solution Manager Upgraded.
5. Host Agent services, OSCOL, etc are running absolutely fine for Managed as well as Managing System.

Also the host_profile contains trust connection user and required porttypes details.

6. DAA of Managed system is connected to Solution Manager as well as SLD.

7. DAA is running fine except for the errors and Exceptions that we can see in Agent Administration screen.

Also perfomed below activities:

1. LM- Service  upgraded to latest patch,

2. All steps mentioned in KBA 1854525 are performed several times.

3, As per solution mentioned in Note 2142276 , LM Service is already upgraded.

4. As per KBA 2057141, SAP Note 2058556 is applied, After applying this note Basic config, Managed System Config and Assigning Templates steps of Technical Monitoring are also performed, But still have the same error.

Please help me with any suggestion that will help me to get Host details parameters,

Thanks,

Rakesh Bhor

Hi,

I am setting up wily monitoring for Java stack system. Can you please share with me the respective documents and helpful blogs.

I will appreciate your help.

Thanks in advance

Hi Experts ,

I am using the option to generate notifications to "Third-Party

Components" sending SNMP TRAP.

We found that the SNMP TRAP sent with "QUOTES" limiting the fields.

Example :

snmp_vals=[''SID~ABAP'',''T_SYSTEM'',''C81F66FA89421EE5A985611A46185566'',''20151216'',''192724'',''ABAP".

It's possible to eliminate  this "quotes"  ?

Best Regards,

Carlos Alberto

Hello,

We are running sap solution manager 7.1 :

We have installed the manageed system SAP S/4 HAna on premise 1511 SP0 and would like to patch it to SP01

The problem is that the product version SAP S/4 HANA on PREMISE is not displayed in MOPZ

It tunrs out that the PRoduct version SAP S/4 HANA on PREMISE  is not displayed at all in smsy side either.

I suppose that I need to patch/update out solution manager, but could not find any note mentionning the required support package.

Thank you for your help

Regards

Hi experts, we have a running solman SP12 configured for VAR scenario, we have been using it for incident management, however, we have not working the mail sending feature. We did the configuration using: "Application Incident Management –Configuration and Upgrade Guide for Service Provider / SAP Channel Partner (VAR) " but theres no anything about mail sending.

When we go to an incident and then More->Send E-Mail->Send , we get the message:"No e-mail adress in your user master record; E-mail will not be sent", however if i check in SU01 and BP transactions,my system users and business partners(related to this users) all have e-mail adress.

Another strange thing is that , in the mail screen, if i select more->from  , i get an empty list

And also, when listing the contact persons for a ticket, the email is empty,however all su01 and business partners, have e-mail assigned:

Does anybody has some tips for configuring e-mail(and make e-mail adresses appear in the incident management screens)?

Thank you so much!

Hi Experts,

We have landscape of SAP ERP ECC6 EHP 7 and Solution Manager 7.1 SP04. We complete the steps system preparation and Basis configuration and now stuck in Managed system configuration.

My question is Can we configure EHP7 Systems in Solamn 7.1 SP04...? If so how it configure...

Awaiting for your replays....

Regards,

SajmaL

Hi,

We have created two sold to party for our two business entities and also configured two separate org structure. We are using support team auto determination by rule.

We have below requirement in incident management

1. Auto determination of sold to party based on either reported by field or support team field.

2. Atleast one support team member should be assigned by default in a message processor field once the Support Team field is determined.

Need your help to understand the possibilities of above requirements either  through standard configuration or development.

Thanks

Dear experts,

I have enabled the technical Monitoring for HANA DB . In the last step in technical Monitoring -->Reporting Step 7 ->there is nothing displayed.

Is this OK ? There is nothing to activate for HANA DB??

For ABAP and JAVA Systems I activated the SID ID ....

Please advice...

Thank you very much!

Hi Experts,

Currently we are working on a Project to Migrate Two Landscapes under one Solman. The requirement is to integrate ITSM with GRC (by replacing REMEDY ticketing Tool). Is there any possibilities or Hints from your side would be great & helpful.

Dear All,

I am going to install the Solution manager 7.1 with SPS 13 with oracle DB in windows environment. Please help me what are the activities we need to carried out before starting my activity.

Thank you for your help..

Hi, experts.
I am not very experienced with solman, that is why I need your help. My requirement is to display the latest 100 tickets in worklist, if the query is empty. Right now (as per default), the oldest 100 are displayed. Is there a way to do this? I am using Solman 7.1. If the solution requires programming, which it probably does, it won't be a problem for me. Any kind of hint would be appreciated.
Thanks in advance,
Borys

Hi Experts,

We want to have different time recording activities for different transactions.

Below are the steps will be followed to define time recording activities.

1. Go to SAP Solution Manager -> Capabilities (Optional) -> Application Incident Management (Service Desk) -> Time Recording -> Specify Activity Description

Navigate to Time Recording > Specify Activity Description

Select profile SOLMANPRO

Double click on Activity Description

Enter as many activity descriptions as desired and click SAVE

We will maintain different activities in common for Role SOLMANPRO.

Suppose we maintain below activities

AAAAAA for SMIN

BBBBBB for SMIN

CCCCC for SMCR

DDDDD for SMMJ

EEEEE for SMAD

FFFFFF for SMTM

GGGGG for SMHF

But all this activities will be displayed in common for all the Time Recording assignment blocks of different transaction type say (SMCR,SMIN, SMHF, etc).

If more than 100 activities are defined in common it will be too large to search for activity.

Can anything be done to specify these activities based on transaction types.

for example

AAAA and BBBB will be displayed only in SMIN, Likewise CCCCC will be displayed only in SMCR, etc.

Thanks,

Rakesh Bhor

Hi CHARM Experts,

we have completed CHARM Configuration in solman 7.1 sp 14, we are not able to find the roles to the user like requester, developer, manager, tester and IT administrator, and in normal change change manager not able to assign the developer in SM_CRM portal, please assist me on this.

Regards,

Hanuman.

Hi Sap Gurus,

My client wants that the system send a email notification to the processor when the field processor was change.

How can i do?

Sorry for my english.

Thank

Hi, I have seen several cases like mine here, but somehow the provided answers don't fit.

We have several SMD agents installed, some of them as local agents on windows machines for EEM.

But one agent on my local PC is always disconnecting since some time. I can't exactly tell, when this started. I know that it worked last December, but fails at least since end of August, 2015.

Symptom:

in dev_smdagent:

J Thu Sep 10 13:01:38 2015

J     :    [12624] 13:01:38    ***Warning: Thread.stop(): Thread.stop() called using java.lang.ThreadDeath in com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.close()V:264

F 

F [Thr 764] Thu Sep 10 13:01:46 2015

F  [Thr 764] *** LOG => State changed from 3 (Running) to 10 (Starting apps).

F  [Thr 764] *** LOG    state real time: 240.286 CPU time: 0.405 sys, 3.088 usr

F  [Thr 764] *** LOG    total real time: 10655.463 CPU time: 67.096 sys, 270.037 usr

F  [Thr 764]

F 

F [Thr 764] Thu Sep 10 13:01:54 2015

F  [Thr 764] *** LOG => State changed from 10 (Starting apps) to 3 (Running).

F  [Thr 764] *** LOG    state real time: 8.281 CPU time: 0.826 sys, 2.948 usr

F  [Thr 764] *** LOG    total real time: 10663.744 CPU time: 67.922 sys, 272.986 usr

F  [Thr 764]

this is repeating every five minutes or so.

Corresponding error message in the Agent-Errorlog on the Solman:

This is the SMDSystem.log:

And this is from the smdagent_trace file:

#1.5 #020085E2EC040001000006EE00001D5400051F6293326155#1441883120815#SMDloggerSystem##SMDloggerSystem#######Thread[Connector,5,main]##0#0#Info##Plain###Old Agent Handle com.sap.smd.agent.AgentHandle@5b1e96 cleanup.#

#1.5 #020085E2EC040001000006EF00001D5400051F629332B139#1441883120836#SMDloggerSystem##SMDloggerSystem#######Thread[Connector,5,main]##0#0#Info##Plain###Reading JStartup environment...#

#1.5 #020085E2EC040001000006F000001D5400051F629332B1A0#1441883120836#SMDloggerSystem##SMDloggerSystem#######Thread[Connector,5,main]##0#0#Info##Plain###'SAPLOCALHOST' found, The value 'C011A0170' will be used to determine the Agent name.#

#1.5 #020085E2EC040001000006F100001D5400051F629332B208#1441883120836#SMDloggerSystem##SMDloggerSystem#######Thread[Connector,5,main]##0#0#Info##Plain###InetAddress Resolving for 'C011A0170' - FQN: C011A0170.group.rwe.com SQN: C011A0170 IP: 10.183.81.13#

#1.5 #020085E2EC040001000006F200001D5400051F629332B330#1441883120836#SMDloggerSystem##SMDloggerSystem#######Thread[Connector,5,main]##0#0#Info##Plain###InetAddress Resolving for localhost - FQN: C011A0170.group.rwe.com SQN: C011A0170 IP: 10.183.81.13#

#1.5 #020085E2EC040001000006F300001D5400051F629332B3C4#1441883120836#SMDloggerSystem##SMDloggerSystem#######Thread[Connector,5,main]##0#0#Info##Plain###Agent Handle have been created#

#1.5 #020085E2EC040001000006F400001D5400051F629332B4A0#1441883120837#SMDloggerSystem##SMDloggerSystem#######Thread[Connector,5,main]##0#0#Info##Plain###  Agent Version .............. : 7.10.12.2.20141128090136#

#1.5 #020085E2EC040001000006F500001D5400051F629332B4F5#1441883120837#SMDloggerSystem##SMDloggerSystem#######Thread[Connector,5,main]##0#0#Info##Plain###  Agent ID ................... : C011A0170.group.rwe.com_DAA_SMDA98#

#1.5 #020085E2EC040001000006F600001D5400051F629332B53E#1441883120837#SMDloggerSystem##SMDloggerSystem#######Thread[Connector,5,main]##0#0#Info##Plain###  Assigned Server Name ....... : rob_r002358#

#1.5 #020085E2EC040001000006F700001D5400051F629332B58B#1441883120837#SMDloggerSystem##SMDloggerSystem#######Thread[Connector,5,main]##0#0#Info##Plain###  Canonical Host Name ........ : C011A0170.group.rwe.com#

#1.5 #020085E2EC040001000006F800001D5400051F629332B5CD#1441883120837#SMDloggerSystem##SMDloggerSystem#######Thread[Connector,5,main]##0#0#Info##Plain###[ms://r0184i1:8101/P4] Registering agent on server ... #

#1.5 #020085E2EC0400E40000000000001D5400051F6293474752#1441883122185#SMDloggerSystem##SMDloggerSystem#######Thread[Thread-628,5,main]##0#0#Info##Plain###[AgentContext.stopApplications] Stopping Agent applications ...#

#1.5 #020085E2EC0400E40000000100001D5400051F6293474F02#1441883122187#SMDloggerSystem##SMDloggerSystem#######Thread[Thread-628,5,main]##0#0#Info##Plain###[ExecutionManager.Shutdown] Shutting down ExecutionManager{selfd:filter}.#

#1.5 #020085E2EC0400E40000000200001D5400051F62934751CF#1441883122188#SMDloggerSystem##SMDloggerSystem#######Thread[Thread-628,5,main]##0#0#Warning##Plain###Cannot close the thread group selfd:filter#

#1.5 #020085E2EC0400E40000000300001D5400051F629356FDEA#1441883123214#SMDloggerSystem##SMDloggerSystem#######Thread[Thread-628,5,main]##0#0#Info##Plain###[ExecutionManager.Shutdown] Shutting down ExecutionManager{e2emai:jobmgr}.#

#1.5 #020085E2EC0400E40000000400001D5400051F6293570E9F#1441883123219#SMDloggerSystem##SMDloggerSystem#######Thread[Thread-628,5,main]##0#0#Warning##Plain###[com.sap.smd.om.impl.broker.ObjectReference@2c8d79 (entities:com.sap.smd.agent.application.e2emai.MAIService [ref])]: unload did not unregister all dependencies of entities:com.sap.smd.agent.application.e2emai.MAIService#

#1.5 #020085E2EC0400E40000000500001D5400051F6293570F7F#1441883123219#SMDloggerSystem##SMDloggerSystem#######Thread[Thread-628,5,main]##0#0#Warning##Plain###[com.sap.smd.om.impl.broker.ObjectReference@1cb215e (states:dpc.startup [ref])]: unload did not unregister dependant "entities:com.sap.smd.agent.application.e2emai.MAIService" of "states:dpc.startup" - could be cycle. Will clean dependants set now!#

#1.5 #020085E2EC0400E40000000600001D5400051F6293582B0F#1441883123292#SMDloggerSystem##SMDloggerSystem#######Thread[Thread-628,5,main]##0#0#Info##Plain###[ExecutionManager.Shutdown] Shutting down ExecutionManager{dpc:job}.#

#1.5 #020085E2EC0400E40000000700001D5400051F6293583E69#1441883123297#SMDloggerSystem##SMDloggerSystem#######Thread[Thread-628,5,main]##0#0#Info##Plain###the deamon thread group dpc:job is already closed.#

#1.5 #020085E2EC0400E40000000800001D5400051F6293583F03#1441883123297#SMDloggerSystem##SMDloggerSystem#######Thread[Thread-628,5,main]##0#0#Info##Plain###the thread group dpc:job is already closed.#

#1.5 #020085E2EC0400E40000000900001D5400051F62935842C5#1441883123298#SMDloggerSystem##SMDloggerSystem#######Thread[Thread-628,5,main]##0#0#Info##Plain###[ExecutionManager.Shutdown] Shutting down ExecutionManager{check}.#

#1.5 #020085E2EC0400E40000000A00001D5400051F6293585A3B#1441883123304#SMDloggerSystem##SMDloggerSystem#######Thread[Thread-628,5,main]##0#0#Info##Plain###the deamon thread group check is already closed.#

#1.5 #020085E2EC0400E40000000B00001D5400051F6293585AD1#1441883123304#SMDloggerSystem##SMDloggerSystem#######Thread[Thread-628,5,main]##0#0#Info##Plain###the thread group check is already closed.#

#1.5 #020085E2EC0400E40000000C00001D5400051F6293586C0B#1441883123308#SMDloggerSystem##SMDloggerSystem#######Thread[Thread-628,5,main]##0#0#Info##Plain###[ExecutionManager.Shutdown] Shutting down ExecutionManager{agelet_WilyEM}.#

#1.5 #020085E2EC0400E40000000D00001D5400051F629358713E#1441883123310#com.sap.smd.e2edcc##com.sap.smd.e2edcc#######Thread[Thread-628,5,main]##0#0#Info##Plain###[DCCService.clean] DCCService cleaned.#

#1.5 #020085E2EC0400E40000000E00001D5400051F62935871CE#1441883123310#SMDloggerSystem##SMDloggerSystem#######Thread[Thread-628,5,main]##0#0#Info##Plain###[ExecutionManager.Shutdown] Shutting down ExecutionManager{OutsideDiscovery}.#

#1.5 #020085E2EC0400E40000000F00001D5400051F62935874E5#1441883123311#SMDloggerSystem##SMDloggerSystem#######Thread[Thread-628,5,main]##0#0#Info##Plain###the deamon thread group OutsideDiscovery is already closed.#

#1.5 #020085E2EC0400E40000001000001D5400051F629358751F#1441883123311#SMDloggerSystem##SMDloggerSystem#######Thread[Thread-628,5,main]##0#0#Info##Plain###the thread group OutsideDiscovery is already closed.#

#1.5 #020085E2EC0400E40000001100001D5400051F629358758B#1441883123311#com.sap.smd.e2edcc##com.sap.smd.e2edcc#######Thread[Thread-628,5,main]##0#0#Info##Plain###[DCCService.dispose] DCCService released.#

#1.5 #020085E2EC0400E40000001200001D5400051F6293587661#1441883123311#SMDloggerSystem##SMDloggerSystem#######Thread[Thread-628,5,main]##0#0#Info##Plain###[WHS] Shutting down Wily Handler Service#

#1.5 #020085E2EC0400E40000001300001D5400051F62935883ED#1441883123314#SMDloggerSystem##SMDloggerSystem#######Thread[Thread-628,5,main]##0#0#Warning##Plain###[com.sap.smd.om.impl.broker.ObjectReference@14d1e30 (applications:com.sap.smd.agent.application.e2emai [ref])]: trying to unload dependent "entities:com.sap.smd.agent.application.e2emai.MAIService" revealed dependency to non-existent broker#

#1.5 #020085E2EC0400E40000001400001D5400051F6293588587#1441883123315#SMDloggerSystem##SMDloggerSystem#######Thread[Thread-628,5,main]##0#0#Warning##Plain###[com.sap.smd.om.impl.broker.ObjectReference@c11070 (applications:com.sap.smd.agent.application.nodescontroller [ref])]: trying to unload dependent "entities:com.sap.smd.agent.application.nodescontroller.nodesController" revealed dependency to non-existent broker#

#1.5 #020085E2EC0400E40000001500001D5400051F6293588821#1441883123316#SMDloggerSystem##SMDloggerSystem#######Thread[Thread-628,5,main]##0#0#Warning##Plain###[com.sap.smd.om.impl.broker.ObjectReference@13853f7 (applications:com.sap.smd.agent.application.runtime [ref])]: trying to unload dependent "entities:com.sap.smd.agent.application.runtime.servicesEntityFactory" revealed dependency to non-existent broker#

#1.5 #020085E2EC0400E40000001600001D5400051F629358893A#1441883123316#SMDloggerSystem##SMDloggerSystem#######Thread[Thread-628,5,main]##0#0#Info##Plain###[ExecutionManager.Shutdown] Shutting down ExecutionManager{WILYHOST_SCHEDULER}.#

#1.5 #020085E2EC0400E40000001700001D5400051F6293588CF6#1441883123317#SMDloggerSystem##SMDloggerSystem#######Thread[Thread-628,5,main]##0#0#Info##Plain###the deamon thread group WILYHOST_SCHEDULER is already closed.#

#1.5 #020085E2EC0400E40000001800001D5400051F6293588D5E#1441883123317#SMDloggerSystem##SMDloggerSystem#######Thread[Thread-628,5,main]##0#0#Info##Plain###the thread group WILYHOST_SCHEDULER is already closed.#

#1.5 #020085E2EC0400E40000001900001D5400051F6293588DA3#1441883123317#SMDloggerSystem##SMDloggerSystem#######Thread[Thread-628,5,main]##0#0#Info##Plain###[ExecutionManager.Shutdown] Shutting down ExecutionManager{EEM_SCHEDULER}.#

#1.5 #020085E2EC0400E40000001A00001D5400051F6293588F4B#1441883123317#SMDloggerSystem##SMDloggerSystem#######Thread[Thread-628,5,main]##0#0#Info##Plain###the deamon thread group EEM_SCHEDULER is already closed.#

#1.5 #020085E2EC0400E40000001B00001D5400051F6293588FA1#1441883123317#SMDloggerSystem##SMDloggerSystem#######Thread[Thread-628,5,main]##0#0#Info##Plain###the thread group EEM_SCHEDULER is already closed.#

#1.5 #020085E2EC0400E40000001C00001D5400051F6293588FDF#1441883123317#SMDloggerSystem##SMDloggerSystem#######Thread[Thread-628,5,main]##0#0#Info##Plain###[ExecutionManager.Shutdown] Shutting down ExecutionManager{com.sap.maimgr}.#

#1.5 #020085E2EC0400E40000001D00001D5400051F6293589086#1441883123318#SMDloggerSystem##SMDloggerSystem#######Thread[Thread-628,5,main]##0#0#Info##Plain###[ExecutionManager.Shutdown] Shutting down ExecutionManager{com.sap.exmmgr}.#

#1.5 #020085E2EC0400E40000001E00001D5400051F62935890D5#1441883123318#SMDloggerSystem##SMDloggerSystem#######Thread[Thread-628,5,main]##0#0#Info##Plain###[AgentContext.stopApplications] Agent Applications stopped.#

#1.5 #020085E2EC0400E40000001F00001D5400051F62938A1C1E#1441883126564#SMDloggerSystem##SMDloggerSystem#######Thread[Thread-628,5,main]##0#0#Info##Plain###[AgentContext.startApplications] Starting Agent Applications...#

And what I did: I re-registerd the SMD agent with

smdsetup managingconf  hostname:"sapms://r0184i1.rwe.com" port:"8101" user:"*******" pwd:"*****"

several times (without error), restarted the SAP hostagent and the SMD agent, but every five minutes or so the agent restarts and disappears from the list of available agents.

Connection method for all robot pc agents is MS/P4, since our solution manager is clustered. All agents are 32bit, Version 7.10.12.2

Any suggestions?

thanks for your advice in advance ...