I am not a Soluion Manager expert and I need some help from experts like you. We have upgraded Solution Manager from 7.01 to 7.1 SP5 recently along with the migration of Service Desk tickets already in the system. Now, we have to do the following:

1. Create a new Service Desk ticketing system where a particular kind of tickets will be created and maintained. This will co-reside with the earlier one.

   Question: How do we go ahead and create a new Service Desk ticketing system?  Would it be in the form of a new Solution or a new transaction?  Please help.

2. The new Service Desk Solution needs to have four customized fields based on which tickets can be searched and displayed.

Question: How do we create customized fields in the UI and underlying repository for this new solution/transaction which should NOT affect the earlier migrated tickets?

3. This new Service Desk Solution/transaction needs to be accessed from ECC 6.0/PI 7.0 to create tickets, close tickets and get a list of open tickets based on certain criteria.

Question: Are there any out of the box Web Services or remote Function Modules available in Solution Manager 7.1 which can be either called directly from ECC through RFCs or from PI? Please help.

Helpful answers will rewarded with points.

Hi,

I am new to Solman and got new project to work on service desk, couple of tasks are assigned to me as of now...

First of that to create a template for user access request as below.

I got a suggestion from BHASKAR KATHULA, i was not able to replay him somehow.

1. Create a copy of SMRQ transaction.
2. Create a copy of CRM UI form.
3. Tailor the form to meet your requirements.

This is a template, has more details below.. Please help.

Thanks,

Manish

Hello,

I'm having a challenge that I shouldn't be this difficult and was easy to set up in 7.0.      We are now on 7.1 SP11.

I need to default the Sold-To Party on ZMCR, but it is not defaulting. It should default based on the ibase.

Here are my details:

1) There is no preceding document. ZMCR is the start of the ChaRM flow.

2) IB52 is setup....

3) The partner 151 in IB52 points to top of PPOMA_CRM...

and BP 151 is setup as a Sold-To Party in tcode BP...

4) Partner determination is currently using access sequence 0018.

But I have also tried access sequences AIC2 and AIC3.  None of them work.

5) I found OSS note 1165357 . It says ...  "

• Execute the IMG Activity "Activate Partner and Address Inheritance, Change
  in the Past".
• For IBase Category 01: set the flag in the column PInherit. and ensure that
  the flag is also set in the column IB Past. "

But in 7.1 SP11, the IMG task title does not include "Change in the Past".

But, looking at the task, it is missing one of the fields in the note. It is missing column "IB Past".

I set column PInherit per the note, but have not made any change for IB Past.  I'm not sure if this part of the issue or not.

I have a feeling it is just the access sequence, but none are working so far.

Any ideas?

Thank you in advance for your help!

Hi All,

I have setup a BW Process Chain Monitor in BPM with the following Criteria:

Start Procedure: Use Chain Start Condition

Alert Configuration: Not Started on Time

Check Time Set to 02:00 hours (UTC Time)

Purpose: We want to track the specific BW Process chain if it has not started before 02:00 hours.

We are getting Red Alerts even when the Process chain started at 00:57 hours UTC time.

I checked RZ20 in BW system and notice the status is Green:

DESCRIPTION                                 PanHP GATP Reporting PSG APJ Demand Shaping

50LIZM7415091EM2KW5CHONXW 01/19 02:58:37    Entire chain now has status 'G'            , Green 19.01.2015 , 03:56:52

50LWMQ1R6NG3MBQTEKAT44YLW 01/20 00:57:42    Entire chain now has status 'G'            , Green 20.01.2015 , 01:56:44

50M5S4JOPVWYKJC5OX2C0SCVO 01/21 00:57:34    Entire chain now has status 'G'            , Green 21.01.2015 , 01:59:07

However the Alert Inbox shows a Red Alert:

Alert Rating/Date/Time/Message:

Red 22.01.2015 02:48:28 No BW Chain was started by 02:00:00

Appreciate if you can let me know what could be the root cause or is there any step i am missing in the configuration.

Regards,

Prasanna

Business Process Analytics in SAP Solution Manager is a problem-oriented tool that allows customers to identify weaknesses in their existing SAP Business Suite processes and provides fast root cause analysis capabilities in order to make processes more efficient end effective (see also the blog Systematic errors vs real exceptions or improving efficiency vs effectiveness) without changing the process design itself (no re-engineering). A more detailed description, about the functions that come with Business Process Analytics, is given in the blog Business Process Analytics: Types of functions and their respective features & purposes. Using Business Process Analytics for cleaning-up your system before implementing SAP HANA might be also an important considertation. More information can be found in Before you get started with SAP HANA...you should also consider cleaning-up your backend system first. No matter if your backend is running on SAP HANA as a database or on any other database, you can also use Business Process Analytics powered by SAP HANA for an ad-hoc, real time analysis.

Upcoming Events on Business Process Analytics: 

• January 27th: DSAG Thementage SAP Solution Manager in Wuerzburg "Business Process Analytics: Der persönliche Gesundheitscheck für ihre Geschäftsprozesse" and a customer experience "Business Process Improvement with Business Process Analytics bei der adidas group"
• February 24th: DSAG Technologietage in Mannheim "Geschäftsprozesse optimieren mit Mobile Business Process Anlaytics des SAP Solution Manager"

News:

Since November 28th 2013 the "SAP Business Process Analytics" app is available for download in Apple's App Store. This app requires iOS 6.0 or higher.

Customer Stories:

• Customer testimonials on Business Process Analytics

New key figure content

A general description about the five existing key figure types (throughput, backlog, exception, lead time, automation rate) is given in the blog

Business Process Analytics: Types of key figures and their respective use cases. The following list of blogs provides a chronoligical overview about what came new when:

• New key figures with ST-A/PI 01M support package 1, e.g. new CRM Marketing content
• New key figures with ST-A/PI 01N,  e.g. new lead time key figures
• New key figures with ST-A/PI 01P, e.g. further lead time key figures
• New key figures with ST-A/PI 01Q,, e.g. new FSCM content & new key figure types
• New key figures with ST-A/PI 01Q support package 1, e.g. new exception key figures for CO-PC
• New key figures with ST-A/PI 01Q support package 2, e.g. new Travel & Expense Management and SAP for Banking content
• New key figures with ST-A/PI 01R, e.g. new delta throughput for OTC and new business workflow key figures
• New key figures with ST-A/PI 01R support package 1, e.g. new 3rd party (drop ship) and MRP list related content

If you require some customer or industry specific key figure content that is not (yet) available, you can also create your own key figures via an Customer Exit.

Application specific blogs

• Best Practice: Business Process Monitoring for Manufacturing
• Best Practice: Business Process Monitoring for Procure to Pay
• Best Practice: Business Process Monitoring for Order to Cash
• Best Practice: Business Process Monitoring for CRM Sales
• New key figures: Analyzing/Monitoring exceptions during delivery due processing
• New key figure: Analyzing/Monitoring exceptions during billing due processing
• Enhanced key figures: Analyzing/monitoring SD invoices not transferred to FI
• New key figures: Analyzing/monitoring exceptions in CRM Sales or Service documents, Business Activities or Tasks
• New keyfigures: Analyzing/monitoring exceptions from APO planning runs
• New key figures: Analyzing/monitoring exceptions during Period End Closing
• New key figures: Analyzing/monitoring exceptions in Controlling (CO-PC)
• Enhanced key figures: Bridging the organizational gap between SD and FI-AR
• Discrete manufacturing: Mapping BP Analytics key figures to system status

Frequently Asked Questions:

• http://wiki.sdn.sap.com/wiki/display/SM/FAQ+Business+Process+Analytics or closely related you might also want to visit the following
• http://wiki.sdn.sap.com/wiki/display/SM/FAQ+Business+Process+Monitoring
• How play Process Observer and Business Process Analytics together?

Hi experts,

yesterday we had the following issue.

A host was extremly slow. It was an VM-Issue.

But, the host was ping-able, so the host-ping metric didn't fire an alert.

However, it was not possible to make a logon on the system.

But, no one of the "instance logon metrics" did fire an alert.

I did check it. The thing is/was, that all the checks are done by LOCAL DAA.

And as the sytem was so slow, no availability-values had been reported from DAA.

So, we had a system which was not working, but didn't got any alert.

My question is now, I did see that in the template for "Technical Systems", there is a "ABAP-System Remote RFC-Availability" metric.

Which is executed by Solman.

(data collector is "RFC (PULL)" and supplier is "RFC Check from Solman").

I would like to have the same check, on instance level.

But I am not really sure, what I have to enter into the field "DESTINAION".

On system level it is "$T_SYSTEM_DESTINATION$".

Is there a similar value on instance-level?

Thank you

Hi ,

How to add the new SRtye in specify status Attribute  like Pre-Production system, UAT system... in ChaRM configuartion

I am using SAP Solution manager 7.1 SP04.

i am trying to add ustomize systenm type in landscape block in normal change .

Rg,

Karthik

Greetings,

Somehow, after upgrading my PI system from NW 7.11 to NW 7.4, the SAP-XICONS component was left at the lower version. Everything else was upgraded and SUM didn't complain about this component. The component was present in the stack.xml file and the SCA was available. Yet somehow it was missed.

Now I am unable to use SUM to update the component. There seems to be no way to get the LMDB to reflect the actual versions of this system and have Maintenance Optimizer function.

After I assigned everything in the LMDB, the Verification Check says "Only assign one SAP NetWeaver product version to product system". And then MOPZ gives errors such as: "Wrong Netweaver product version found SAP NETWEAVER 7.4" and "Multiple Netweaver Product Version were found".

However, if I remove the assignment of 7.11, MOPZ is still unable to calculate the queue. It even gives the same errors.

How can I fix this? Is there some other way to generate the stack or get SUM to upgrade the component?

I have a landscape with several Development Systems, when I assign logical component for these in managed system configuration a mandatory field is System role. When I select Development System on on my second dev system it says "Two technical systems with the same system role are not supported"

Is there a way around this?

The present blog is the result of the effort of our Solution Manager Technical Team, that working in different areas made this simple solution available to our user community.  There is no big secret behind this, but there are so many presentations SAP has in which they say it is possible to forward ITSM incidents to SAP, but after some weeks we could not find the easy way to do it and all the elements that are required to have all the pieces working like a Swiss watch.

Following our sense of sharing our experience as it flourishes, below you will find it all grained ready and ready for baking.

Steps.

1.  There is an Assignment Block hidden in the ITSMWebUi, called SAP Collaboration.  You have to make it visible selecting Lazy or Direct.

3. You need to enable the transaction type actions that are relevant for this service.  Some are already activated, some others not.  Via transaction CRMC_ACTION_DEF select the transaction type (ZMIN  or ZMRQ) and activate the services below:

The actions above cover a wide range of activities related to the incidents opened with SAP.    For this particular blog, we are not going to deal with actions like Opening system for SAP or Maintain SAP Logon Data.  Although they are related to the topic per se, the goal here is to show how we can enable functionality.  Those mentioned actions are more Basis related and authorization and security may be involved to actually control who can perform them, as well.

4.  Behind the scenes, the processing of all requests uses the RFC (Remote Function Call - for the non-Basis folks), SAP-OSS.  That connection should be always enabled with a SAP marketplace user and its correct password there.

The connection test must be successful.  If it fails, coordinate with your Basis support.   On the paper, the SAP support user being used in the RFC should be an anonymous account with its correspondent associated user in the ABAP stack of your SolMan system.   That latter is recommended to be an account type System or Service, which password does not expire.   The reason for the match between those 2 accounts will be explained further down.

5.  All the users who regularly create incidents directly in the SAP marketplace, including the anonymous account should have an entry in the SAP Reference IMG > SAP Solution Manager > Technical Settings > Assign S-User for SAP Support Portal Functionality.

6.  With that in place you are all set.  The following screens will tell you how to create the incident and get the replies from SAP.

6.1 Create an incident as usual.   Important is that you add a description, which may not be mandatory for internal incidents, though no logic.

Remark:  You can also add attachments in the respective assignment block?

6.2.  If the incident is to be sent to SAP support portal, you will find in ITSM a new assignment block in the incident called SAP Collaboration.   Click there and the button Sent to SAP.

6.2  From then on, a process similar to the one you also followed when you had to open incidents in the SAP support portal.  You will need to proceed one by one through the screens, being aware that in many cases you do not have to worry about some empty fields.  The solution internally complete most of them as you move along.

6.3 For the screen below, what is most important is the system data and that is automatically entered due to the fact that in the moment the incident was created, a component was to be selected.       Provide any additional information that may help SAP to properly identify your system.  We only provided the basic part and that is sufficient.

6.4 For the next step, the system internally checks that the user creating the incident, has a S0* account in SAP service marketplace or in  SolMan's view V_AISUSER (or SPRO > SAP reference IMG > SAP Solution Manager Implementation Guide > SAP Solution Manager > Technical Settings > Assign S-user for SAP support functionality).   If you regularly create incidents in SAP support portal, we have taken care of your account, long time ago.    This was explained already in step 5.

Green means okay, whereas Red, means either the sapgui account used in ITSM has not been associated in the table referred above with a S-user account, or the sapgui account being used in ITSM does not have a S-user account at all requested in SAP support portal.   If there is an error on the screen bellow, consult your SAP Basis provider.

6.5  For the following screen, you are prompted to provide the specific SAP component at SAP that this incident should be associated with.  In other words, the team at SAP that you think should take care of this incident. Also, proceed to provide a priority to the incident, which may be different than the priority given to the incident in the header when it was originally created.

6.6  Provide any additional information that you think is important for SAP support to now.  This is not mandatory and you can skip it by pressing Next.

6.7  If you are satisfied, submit the incident to SAP, otherwise press the Previous button and review again.

Any errors when you submit, contact your Basis Team.  Most likely an issue related to RFC SAP-OSS.

6.8  In case the RFC connection is correct or was corrected, the result after submitting the incident should look like below.

As you can see, incident at SAP is 48869.

6.9  Additionally change the status of the ITSM incident to Sent to SAP, so that the requester is aware of the status of their incident.

6.10  The behavior in the background is exactly as if you had created the incident directly in the SAP support portal.  You do not need to do the step below, but it is just FYI.   You can open the incident at the SAP support portal and see that even the attachments of the original ITSM incident are also found there, as expected.

6.11  From then on, you are already familiar with the processing.

SAP eventually will place the message in Customer Action.  Further down we explain an automatic process to feed ITSM from SAP support portal, but you can individually check if there is an update from SAP for your own incident.  In the same Assignment Block SAP Collaboration, press the button Update from SAP.

6.12  If you see that the incident is in Customer Action, the reply from SAP has been included in the Assignment Block Text, and if they submitted attachments they will also be found in the respective Assignment Block, as well.

Reply from SAP with attachments:

6.13  If you are satisfied, you can proceed to Confirm the incident for which you press the button Confirm at SAP, or you can go back and Send to SAP for further actions.   After you confirm, you can even complete the survey from ITSM.  What else do you need!!!

7. Q&A?

7.1 Is there a way to automatically feed ITSM with the replies from SAP, instead of having to individually press the button Update from SAP at each open incident?

Answer:  Yes.   There is a program you can schedule for that to run every 5 minutes.  The program is AI_CRM_IM_UPDATE_FROM_SAP.   If there is a change found a the support portal for any incident in progress, the ITSM SAP Collaboration statusof each ITSM incident affected changes from Sent to SAP to Customer Action, and the ITSM incident's header status changes from Sent to SAP to In Process.  That action should trigger an internal email notification so that the incident processor at your company gets notified that an update from SAP has arrived.

That process or activation of that notification is well documented in: http://scn.sap.com/docs/DOC-35291

Important to say that the email configuration is optional, and it is based on events. The PPF actions that trigger the email are based on a scheduling condition

and a start condition.   The notifications are not triggered directly by AI_CRM_IM_UPDATE_FROM_SAP, but by the subsequent status change affected by the that program.

Recommendation.  Search in the marketplace for the program and apply all missing notes you have with regards to it.  There is a huge improvement SAP has done to that report over time, so you better dance with the latest and avoid unnecessary troubleshooting.

7.2  What about incidents we already created in the SAP support portal?  Can they be imported into ITSM?

Answer:  Yes, they can.  There is an option in the program AI_CRM_IM_UPDATE_FROM_SAP to create new incidents in ITSM for those cases.  There is even an option to create ITSM incidents for already confirmed messages, but that can overload your system and may take time to run.

7.3 What if I go and update the try to close the incident directly in the SAP support portal?

Answer:  Next time you run AI_CRM_IM_UPDATE_FROM_SAP it will bring over on to ITSM those updates.

7.4 What if I confirm the incident right in the SAP market place?

Answer:  Nice try!!!  SAP will send you back the incident and you will only be able to request confirmation in ITSM.

7.5  Will SAP still notify me via email that my incident at SAP is in Customer Action?

Answer:  Not anymore.  Note 1278052 explains SAP stopped doing that due to the confusion that created and also to enforce us to use ITSM, instead.  Read 9.1, which has the link to enable internal notifications.

7.6 What if there is an attachment in my incident larger than 4MB, current restriction SAP has in the support portal for the attachments?

Answer:  Oh boy!!! I cannot do the whole exercise.  I am already exhausted of typing   Could you give it a try and share with us?

7.7  What about reporting?  Can I see the incidents with the respective SAP message number assigned by SAP?

Answer:  Yes and from factory.  Stay tuned for the answer.   TIP.  It is an additional column you could add to the incident search.

Enjoy!!!

Juan-Carlos Garcia-Garavito

Other posts from this author @ http://scn.sap.com/people/juan-carlos.garcia-3/content

Good afternoon:

I have ran into different documents, presentations from SAP mentioning that you can connect SAP ITSM to a 3rd party support desk tool, or to SAP support to forward your own SAP incidents in ITSM to SAP  in order to not just pass them to SAP, but to perform the follow up, and eventually receive the reply from SAP in that central location, your ITSM WebUI.

Does anyone out there has the steps or some guidelines to do that?  The theory looks nice on paper, but we have not seen the actual steps to do it.

Many thanks,

Juan-Carlos Garcia G.

Hi guys!

   Right now i am having an issue calculation a Stack.xml file through MOPZ, and i wasn't sure what was happening until i noticed something funny, and its that there are product versions mismatch between SLD and LMDB, for example, i see that in the SLD my technical system has component C-CEE 200 while on the LMDB it detected version 1xx, even if i to a resync from SLD, old version stays on the LMDB.

    The technical system wasn't manually modified nor on the LMDB, my system its an IDES based on NW 7.40 ECC 6.0 EHP7 that i need to use for a SAP Fiori demo system (which requires SP07).

     I was able to notice this inconsistency because in phase PREP_EXTENSION/ADDON_QCALC! i got "a newer version of C-CEE (200 version 0000) is already installed" severe error.

     Yesterday i was able to update CR_Content (cim/CR_Delta) several levels, it wasn't that outdated (2 months old) but now it is updated with the very latest versions.

Any thoughts would be appreciated.

Best regards,

Martim.

I have in place a new System Solution Manager 7.1.

There where some Projects in the older system which I have done transports into the new system.

Do you know how I get the learning maps to new system SOLAR_LEARNING_MAP ?

Hi !

We're in the process of completing our MSC setup for a standalone Java system.

Step 7-->Finalize Configuration-->Register ADC Collector gives the below error:

Solman 7.1: SP 12

Java 7.40 Portal system: SP 7

We've used the "Administrator" user in "Enter System Parameters".

The Test Logon works Ok too.

This user has the Administrator role as per Note 1857914.

I've even restarted the Activity collector services from NWA...

Please help advise

Thanks a lot !

saba.

We have a Bad dialog response time (instance level) alert in which dialog response time metric has data collection and granularity both set for 5 minutes.

But when checked the alert in alert inbox of technical monitoring work center, i can see start time and end time being same but the number of alerts generated are more... How is this possible??? when the data collection itself is 5 minutes.

My way of looking at the issue - If we have 3 alerts then the start and end time should be in difference of atleast 10/15 minutes as the data collection of the metric itself is 5 minutes.. Can someone explain this strange things happening in alertinbox/metric functioning.

FYI - Issue is not specific to Bad dialog response time alert but also for other alerts as well.

Hi Experts,

I am getting following error while updating the CR content in solman sld

Exception: com.sap.sld.api.wbem.exception.CIMException: CIM_ERR_FAILED: http://xml.org/sax/features/external-parameter-entities at com.sap.sld.api.wbem.transform.CIMXmlParser.saxToCIMException(CIMXmlParser.java:289) at com.sap.sld.api.wbem.transform.CIMXmlParser.<init>(CIMXmlParser.java:65) at com.sap.lcr.pers.delta.importing.ImportHandler.getCimXmlParser(ImportHandler.java:2473) at com.sap.lcr.pers.delta.importing.ImportHandler.loadCatalog(ImportHandler.java:1679) at com.sap.lcr.pers.delta.importing.ImportHandler.loadCatalogIntoTempNamespace(ImportHandler.java:1404) at com.sap.lcr.pers.delta.importing.ImportHandler.prepareAggregateImport(ImportHandler.java:824) at com.sap.lcr.pers.delta.importing.ImportHandler.prepareZipFile(ImportHandler.java:297) at com.sap.lcr.pers.delta.importing.ImportHandler.prepareImpl(ImportHandler.java:185) at com.sap.lcr.pers.delta.importing.ImportHandler.prepare(ImportHandler.java:163) at jsp_importWarning1421838833691._jspService(jsp_importWarning1421838833691.java:59) at com.sap.engine.services.servlets_jsp.server.jsp.JspBase.service(JspBase.java:112) at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:568) at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:192) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1064) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176) Caused by: org.xml.sax.SAXNotSupportedException: http://xml.org/sax/features/external-parameter-entities at com.sap.engine.lib.jaxp.SAXParserFactoryImpl.setFeature(SAXParserFactoryImpl.java:43) at com.sap.sld.api.util.XmlParserFactory.getProtectedSAXParserFactory(XmlParserFactory.java:25) at com.sap.sld.api.wbem.transform.CIMXmlParser.<init>(CIMXmlParser.java:53) ... 26 more caused by: org.xml.sax.SAXNotSupportedException: http://xml.org/sax/features/external-parameter-entities at com.sap.engine.lib.jaxp.SAXParserFactoryImpl.setFeature(SAXParserFactoryImpl.java:43) at com.sap.sld.api.util.XmlParserFactory.getProtectedSAXParserFactory(XmlParserFactory.java:25) at com.sap.sld.api.wbem.transform.CIMXmlParser.<init>(CIMXmlParser.java:53) at com.sap.lcr.pers.delta.importing.ImportHandler.getCimXmlParser(ImportHandler.java:2473) at com.sap.lcr.pers.delta.importing.ImportHandler.loadCatalog(ImportHandler.java:1679) at com.sap.lcr.pers.delta.importing.ImportHandler.loadCatalogIntoTempNamespace(ImportHandler.java:1404) at com.sap.lcr.pers.delta.importing.ImportHandler.prepareAggregateImport(ImportHandler.java:824) at com.sap.lcr.pers.delta.importing.ImportHandler.prepareZipFile(ImportHandler.java:297) at com.sap.lcr.pers.delta.importing.ImportHandler.prepareImpl(ImportHandler.java:185) at com.sap.lcr.pers.delta.importing.ImportHandler.prepare(ImportHandler.java:163) at jsp_importWarning1421838833691._jspService(jsp_importWarning1421838833691.java:59) at com.sap.engine.services.servlets_jsp.server.jsp.JspBase.service(JspBase.java:112) at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:568) at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:192) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1064) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execte(SingleThread.java:104) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176.

Please help

Thanks

Pramod

Hello,

after Accepting the Domain Link in our ChaRM System i get an Error in the Sattelite System:

XT678 RFC-Destinations for the <Charm-SID>-System could not be generated.

When I try to generate the RFC Destinations in STMS i get Error XT115:

INTERNAL_ERROR 5 in Function RFC_MODIFY_R3_DESTINATION

I have in my Sattelite-System: SAP-BASIS 7.31 SP13 with Kernel 721_EXT_REL 400

Any help appreciated.

Jonas

Hi All,

I am trying to perform managed system configurations in solman_setup on our solution manager for a managed system Other then Solman  and in the step 'Enter system parameters' when I try to save the parameters, I get the following error "DBA cockpit connection XXX cannot be established".

When I click on Details->show in the logs I get the following message:

The tricky part is The user stated in the above error message is not a managed system XXX OS user. The user is solman OS and DB user. I have tried checking in various places like LMDB and DBA cockpit etc. But I wasn't able to figure out from where it is picking up this parameter (User). Also I have completed Managed system configuration for solman system without any issues in this step

Kindly help me with this.

Regards,
Kalpeet

Hello everybody,

we are currently planning to upgrade one of our systems from ERP 6.0 EHP4 to ERP 6.0 EHP6 SPS 14. This system is currently connected to a Solution Manager 7.0 EHP1 SPS 1, in order to use ChaRm.

We were wondering if there would be any kind of problems with ChaRm after the upgrade EHP4 - EHP6 and what you suggest in order to minimize efforts and problems.

Thank you in advance for your support and advices,

Federico

Hi All,

   I am searching for the Standard report which could help us in closure of incidents which do lie in service desk status Customer action & are 2 days older.

So if somebody could help me with the identification of such reports then i would be glad.

Regards

Vishal