Solution Manager connection to Satellite system
Hi Gurus
I would like to find out on what kind of tests can I perform on business process management to ensure that the Solution Manager is communicating with the sattelite system.
Regards
Khuselwa
Hi Khuselwa -
Do you just want to ensure that a connection is established between Solution Manager and the satellite systems? You can do both a connection test and authorization test in the Configuration of RFC Connections transaction.
Transaction SM59
Expand ABAP Connections
Double click an entry
Choose Connection Test button.
You can also test the authorization by Utilities --> Test --> Authorization Test
Hope this helps,
Nathan
Similar Messages
-
Configuration check error: The SMD Agent is not able to connect the Satellite System (J2EE stack)
Hi friends,
Getting the below error in step 10 (configuration check) in managed system configuration.
The SMD Agent is not able to connect the Satellite System (J2EE stack).
Please check the JAVA Connect Parameters provided in the Managed System Setup Wizard for this
System.
java.rmi.RemoteException.P4 Connection failed -
P4AuthorizationException -
com.sap.smdagent.plugins.connectors.p4.exceptions.P4AuthorizationException:
Access is denied to SAP System sid [XYZ/null]: check the connection
credentials.More details about the error in agent 'xyz' log file
(SMDAgentApplication.X.log).; nested exception is:
com.sap.engine.services.security.exceptions.BaseLoginException: Cannot
authenticate the user.
The SMD log file referred to in the log above gives the same information and not anything much useful.
Any idea what could be the reason for the above error?
Thanks,
ArindamHi All,
Thaks for your suggestions. I chcked the note 182020, but the issue described in the note is for error byte code adapter installation whcih is not my case. The byte cde adapter intallation has been successful in our solman system All the steps from 1 to 9 are green. Only in step 10, check cniguration I am getting the above error.
The logon test wth the user id in step 3 "Enter system parameters" is successful. The message server port is also correct.
Hi Khaja,
I went to the links as suggestedby you but there its about a ifferent error message "Invalid Response Code: (401) Unauthorized.". I am not getting any such kind of error.
All I am getting is this -
The SMD Agent is not able to connect the Satellite System (J2EE stack).
Please check the JAVA Connect Parameters provided in the Managed System Setup Wizard for this System.
java.rmi.RemoteException.P4 Connection failed -
P4AuthorizationException -
com.sap.smdagent.plugins.connectors.p4.exceptions.P4AuthorizationException:
Access is denied to SAP System sid [XYZ/null]: check the connection
credentials.More details about the error in agent 'xyz' log file
(SMDAgentApplication.X.log).; nested exception is:
com.sap.engine.services.security.exceptions.BaseLoginException: Cannot
authenticate the user.
Thanks,
Arindam -
Adding existing systems to a new Solution Manager 7.0 Ehp1 system
Dear Experts,
We've just installed a new Solution Manager 7.0 Ehp1 system, we have a 3 system landscape in action, please need your help to connect these systems with this new Solution Manager system. The post installation Initial Configuration and Basic Configuration has been performed successfully. Also need your help with Maintenance Optimizer configuration and setting up EWA.
Please do share experiences, links and documents for the above.
Thanks in advance,
Best Regards,
basis-novicePage 65-67 of Netweaver EHP2 Upgrade Guide found in service.sap.com/instguides.
You can use the explanation below to configure MOPZ and maintain systems in SMSY.
4.5.2Configuration of the Maintenance Optimizer
You have to configure the Maintenance Optimizer. For a list of configuration tasks, see the Maintenance Optimizer Configuration Guide.
Make sure that you run the guided procedure SOLMAN_SETUP after every installation or update of SAP Solution Manager and that it completes successfully.
Related Documents
Available at...Maintenance Optimizer Configuration Guide http://service.sap.com /mopz (link at the bottom of the page)
4.5.3Maintaining System Landscape Information
The Maintenance Optimizer relies upon up-to-date information about your system landscape. Therefore you have to maintain this data in SAP Solution Manageru2019s system landscape (transaction SMSY). In the following, you will find the description how to maintain this data. If you already have maintained the system landscape data, then check if the data is correct.
If you use the System Landscape Directory (SLD), then use it to capture the system data.
If you do not use the System Landscape Directory (for example, if you have a pure ABAP system), you use RFC connections to maintain the data.
Procedure
Maintaining the System Landscape Data Using SLD
1.
Register both Java systems and ABAP systems that you want to update in your central SLD.
The central SLD can either be on your SAP Solution Manager system, or you can have a separate system where you run the SLD (central runtime SLD). If you use a central runtime SLD, make sure that it is synchronized with the local SLD of your SAP Solution Manager system.
4.5.3Maintaining System Landscape Information
The Maintenance Optimizer relies upon up-to-date information about your system landscape. Therefore you have to maintain this data in SAP Solution Manageru2019s system landscape (transaction SMSY). In the following, you will find the description how to maintain this data. If you already have maintained the system landscape data, then check if the data is correct.
If you use the System Landscape Directory (SLD), then use it to capture the system data.
If you do not use the System Landscape Directory (for example, if you have a pure ABAP system), you use RFC connections to maintain the data.
Procedure
Maintaining the System Landscape Data Using SLD
1.
Register both Java systems and ABAP systems that you want to update in your central SLD.
The central SLD can either be on your SAP Solution Manager system, or you can have a separate system where you run the SLD (central runtime SLD). If you use a central runtime SLD, make sure that it is synchronized with the local SLD of your SAP Solution Manager system.
4.
Create an RFC connection
1.
Choose the Client tab for your system.
2.
Maintain at least client 000.
3.
Create an RFC connection between the Solution Manager and the system you want to update using the RFC Assistant.
5.
Start the data transfer
To initiate the remote transfer of system data from the target system, choose the Read System Data Remote.
RECOMMENDATION
We recommend you to schedule automatic data transfers using transaction SMSY_SETUP. -
Solution Manager: Connection via Service Connection???
Hello,
I would like to connect the solution manager with a customer system via an exististing service connection, there is no solution manager installed on the customer's system. Is this possible? Is it possible to find any documentation about this?
Regards,
BrittaHello,
You can run TCD DSWP
Then clcik the Solution Landscape button
Then Clcik the Service Connection link
Then click the Solution Manager drop down menu and select setup connection
Then fill in the details:
Product System
Description
Installation Number
Systen ID
System Number
Service Connection type
The support Service Connection types are reference at http://service.sap.com/connectiontypes and for each connection type the corresponding Note is provided.
This setup will allow you to create service connections to OSS on Solution Manager
Once you have setup the connection you will still navigate to Service Connections, only you will use the Connection Drop down menu button to select Open Connection.
Regards,
Paul -
Connection From Satellite System to Solution Manager for key users
Hi All,
Can anybody suggest which RFC connection/destination should be maintained in BCOS_CUST table under satellite system to connect to Solution Manager.
1. SM_SSMCLNT010_TRUSTED
2. SM_SSMCLNT010_BACK
I don't want user to Login to solution manager while creating a support message. They should create a support messsage seamlessly from satellite system.
Any help is greatly appreciated.
Thanks...Thakur,
Sorry for the cryptic answer back there - read it myself and it didn't make much sense to me either so here we go with the seamless way to allow users to create service messages.
There are 2 ways to do this - 1 way is to use a connection like the 'BACK' connection but if you do this - all user tickets entered will have the username of the 'BACK' connection logon id as the message creator. The other way is to use the trusted connection so the userid of the person logging the message is transfered with the created ticket.
I will assume that you want to preserve the unique userid and use trusted connections. So here we go:
Step 1 - Go into BCOS_CUST on the Satelite and put in your TRUSTED RFC Connection as the detination for the Service Messages - either use the one that Solman created when generating or make your own ABAP Trusted Connection.
Step 2 - All users in Satelite and in Solution Manager need to have Authority Object S_RFCACL assigned to their userid's so they can use the Trusted RFC Connection (this is not in SAP_ALL or SAP_NEW).
Step 3 - All users that will use this method of creating service tickets need both a userID and a BP with the respective system keys to allow them to enter tickets for those Satelites.
That is all there is to it assuming that all issues with Trusted Connections have been worked through already (test this in SM59 by going to your 'TRUSTED' connection on the Satelite and execute the RemoteLogon button - you should be sent to the Solution Manager with out having to logon).
If this answers your question, please set this message to answered.
Edited by: David Milliken on Jan 25, 2008 1:55 AM -
Multiple Solution Manager Connectivity to 1 Satellite system
HI..
I have a requirement. There is already an existing landscape with solution manager ECC, BI etc. The solution manager is configured for EWA, Maintenance optimizer etc. I now have to install a new solution manager and connect it to the same set of satellite systems so that I receive the EWA, configure MOPZ again. Will this create any kind of a problem and technically how can we do it? I have two ideas for this scenario
1. Connect the new solution manager to the same satellite systems and do configuration as normal. Got this idea from the below link but not sure how it will work.
Re: send EWA report to more than one solution manager
2. Is it possible to push data from the existing solution manager to the new solution manager?
Would highly appreciate technical suggestions. Thx in advance for your help.Hello,
You need the SMD Agent in order to have ABAP data going to the Solution Manager. Some RFCs are established directly from Managed System to the Solution Manager to extract E2E Change Analysis, Exception Analysis. The Workload Analysis and Host Information (SAPOSCOL) is extracted from WIly EM
Having that said, you can imagine that you cannot have only RFCs and you cannot have only data extracted from WIly EM.
I suggest you to take a look at the FWK Administration in the solman_workcenter, choose the Managed System tab, and start looking into the details of each extractor. Some have an RFC destionation, others have SOLMANDIAG. The SOLMANDIAG are coming from the Solution Manager Java stack, which is responsible to poll the Wily EM.
The reason you need two SMD Agents is because the SMD Agent connects to the ABAP stack, retrieves data, and then connects to the Wily Enterprise Manager. The Solution Manager polls data from the Wily EM and persists it in the BW.
The SMD Agent doesn't support connecting to two Wily EMs at the same time.
So it is required to have TWO SMD agents polling data from the ABAP stack, at the same time, one of them reporting to one Wily EM, and the other reporting to the other Wily EM.
Each solution manager has it's own Wily EM, and it will pull the ABAP data from the Wily EM.
It is not possible to make the two Solution Manager's connect to one Wily EM, since the setup framework needs to see a SMD Agent available to run the setup wizard and to create the destinations. So each Solution Manager needs a SMD Agent running in the physical host.
I hope it is clear for you.
Best regards,
Guilherme
Edited by: Guilherme Balbinot on Feb 6, 2012 9:44 PM
Edited by: Guilherme Balbinot on Feb 6, 2012 9:49 PM -
SMSY - Generated RFC between solution mananger and a satellite system
Hi gurus,
I would like to ask you some things about configuration of SMSY - create systems and their RFC´s between solution manager (SSM) and a satellite system (for instance the DEV system SD3 (in solution manager system)
But my problem is which of these users I must use in each RFC???
Because until this moment I have been doing without knowing very well where I must put that users in those RFC´s!!!!! And I don´t know if I have been doing well!! You understand ?!? :- /
Can somebody give me a simple explanation about this... Which user I have to put (due to the authorizations) in those RFC connections?!
And other thing, if you don´t mind take a look to other question I ask yesterday which is related with this doubt:
Help me please... :- /
Thanks in advance
Best regards,
João DimasHi Joao,
As I understand, the respective RFCs and users are created autmatically when the RFCs are
generated for a satellite system in SMSY.
Furthermore, the Z roles and profiles for each of these users are also created/generated during the
generation procedure. The roles/authorization assigned to each of the generated user are as mentioned
in the below link:
http://help.sap.com/saphelp_smehp1/helpdata/en/48/647e3ddf01910fe10000000a114084/frameset.htm
The administration/customizor specific authorization objects are also provided. As you mentioned the
above helps understand the roles/authorizations required for specific user with regards to an RFC.
Apart from this, all the actual creation, generation and assignment is done - thanks to the automated
setup in SMSY
Also I suppose the above link should help you decide the auhtorization objects requested by you
in the other thread.
Hope this helps.
Regards,
Srikishan -
Solution Manager connection in Data Services
Hi,
When trying to make a data store connection in Data Services to a Solution Manager system I get an error that there is no connection or my credential are wrong.
I can ping the system so there is a connection.
I can log in to the Solution Manager system via the GUI so the credentials are ok.
So far i have found out that the Data Store connection cannot connect to Solution Manager because it per default tries to connect to port number 3200 while the Solution Manager system default has port number 3300.
But i can't change / select port number in the Data Services data store connection. So what do i do?There is a problem in the transport file supplied with BODS installation folder. Pls refer to the SAP Note :
1616269 - Problems when installing Data Services 4.0 SAP transport files (900155.R63)
We have used the new transport files but we are still getting the below warnings in the log files and it returned with return code 4 :
Maximum length ("255") for "CHAR" in transparent tables exceeded
The SAP Note 1446648 - Warning Messages installing SAP R3 transports for Data Services sayou can ignore those warnings but we are still not able to see the ZAW0 Function group in SE37.
Let me know if you are able to do it successfully. -
SLD Solution Manager & connections to other SAP productes in landscape?
Hi All
I have installed Solution Manager 4.0 SR3 in order to implement global monitoring across our landscape and I have decided to install and use the SLD.
I have set up the SLD and followed the post installation guide, however I now want to connect all of our sytems to it so that Stack , version Information, components etc can be transfered to the SLD automatically. Once this is done in Solution Manager (SMSY) I can then view all of my systems.
Firstly is this possible and does anyone have any information on how to do this?
Many Thanks
PhilHi Phil,
It is possible.
Firstly in satelite systems you need to enter your SLD server info using transaction SLDAPICUST. Here you specify your Solution Manager system as host, user usually j2ee_admin and j2ee_admin's password. The alias can be anything and default port is 5<instance no>00.
Secondly, you test the connection with transaction SLDCHECK. If it's green it's OK, you can ignore most warning messages.
Then last you setup data collection and job scheduling and you do this in transaction RZ70.
Sorry don't have any reference to notes or documentation but each transaction above should make sense of what I mentioned.
Hope this helps.
Regards,
Nelis
Message was edited by:
Nelis Lamprecht -
Solution Manager to Solution Manager connection
Hello everyone,
I am searching for an answer for such a question: is it possible to connect one SolMan (the one from the service provider) to another SolMan (customer's one) in a way that tickets would go from customer's ERP to their SolMan (as it is now) and afterwards would be automatically forwarded to the other SolMan where the tickets should be processed?
If you have any idea, experience or relevant document, please share it - I will be really grateful.
Best regards,
Katarzyna KlysHi Katarzyna,
Please check the External service desk functionality for this. You can check SPRO entry for this:
SPRO --> SAP Reference IMG --> SAP Solution Manager Implementation Guide
--> SAP Solution Manager --> Scenario-Specific Settings --> Solution Manager - External Integration --> External Service Desk
Also check below link:
http://help.sap.com/saphelp_sm40/helpdata/en/8a/b0278648ac4f058a7111c3f9b60feb/frameset.htm
(All in One line)
In Solman 7.0 system:
1. T-code SM59 > Define an RFC connection to 7.1 system;
2. T-code ICTCONF > Add an entry for the 7.1 service desk, specify the RFC Destination as the one you defined > Activate -> Generate default value mapping (you may find the button on the top of ICTCONF).
In Solman 7.1 system:
1. T-code SM59 > Define an RFC connection to 7.0 system;
2. T-code ICTCONF > Add an entry for the 7.0 service desk, specify the RFC Destination as the one you defined > Activate -> Generate default value mapping;
3. Customize your own value mapping including the transaction type. You will find the details in:
IMG -> SAP Solution Manager -> Capabilities (Optional)
-> Application Incident Management (Service Desk)
-> External Integration -> External Service Desk
Most fields of SIVA and SMIV are the same (for example, priority) so you do not need to care about the value mapping if you do not havespecial requirement. However, some fields only exist in SIVA (category, subject) and others only exist in SMIV (multilevel categories). You may need to implement your own code according to your requirement.
Notes might help:
1159722
1136816
Thanks
Vikram -
Solution manager - WHY an own system ?
hi,
we are uprgrading from sap R/3 4.6c to mySAP ERP2005 the next weeks.
SAP told us that from April 2nd it is a MUST to have a solution manager for runnint mySAP ERP2005. is this true ?
why we have to use the sol. manager ? what is it good for ?? is it really a own system or can we install it together with mysap erp on the same system ?
We are a little bit 'pissed off' about this situation, because no one told us before.
regards, Martin> >Believe it or not - but now the sales department
> would send a consultant to "help" us >setting the
> system up - that's the story.
>
> That's its happening around SAP, not jus' products.
Yes, I know - but we won't pay him.
>
> >No comment on this, this is an open platform and
> sharing those kind of information is >crucial. If you
> (= SAP) don't want that, then please moderate the
> forums, delete all posts, >that are not just hyping
> your products. People want to know reality.
>
> Hyping??!@ you will not learn at all...
Yeah - If you tell people just to ask "technical" question and not to pinpoint the necessity and valuability of a product, that is "hyping" - just as M$ is doing with Vista and the "revolutionary Office 2007".
>
> >So constructive criticisim is not wanted? SDN is
> just for saying how "nice" and "good" >products are?
> I'm not shouting because of shouting but I'm arguing.
> As of now I did not >get ANY point of you to confute
> my arguments - you are just pointing to high-gloss
> >marketing powerpoint presentation - and we all know,
> from long experiences, what they >tell.
> Using words like S*t,h*l, this is what you call
> constructive criticism?? If you don't understand the
> products atleast try to understand people. Its not
> about saying "nice" and "good", its about saying
> "whether it is nice?" or "whether it is nice?". Pros
> and Cons are beautifully discussed in this forum
> previously, i would place an humble suggestion to go
> thru' them first.
Where did I wrote "sh***"?
> If you really have done it with latest patches and
> release levels you may hardly need to rever 5 - 10
> notes. For your kind information, this SOLMAN with
> all features can be implemented in 7 Mandays with all
> the features.
7 Mandays? will you pay me for this? Will YOU pay users disruptions when installing agents/plugins/patches on the connected systems? Will YOU pay the time you need to keep those patches/agents/plugins in the external systems up-to-date? We had BIG problems with ST-PI* and ST-A/PI* during our Unicode conversion so don't tell me, there is no disruption.
>
> You know the usage of SOLMAN, sorry you don't know,
> that's why you are arguing. It is to add
> professionalism to your work.
> If you had implemented SAP how did you maintain your
> documents? I bet you would have had as junk folders.
> That's no more with SOLMAN.
We started with release 2.2d in 1995 and upgraded since over the 3.0 releases to now 4.7 - and we did that without SolMan because it did simply not exists - and it worked - sucessfully, otherwise I wouldn't post here. Believe it or not, we used ASAP (the product before SolMan) - and we have those processes documented in there (still).
> Have you ever documented your Business Process? I bet
> you would not have, even if you had you will have in
> junk folders as files.
YES - we have - and we also teach other companies to do on that. And there are MORE systems involved than just SAP systems; environments are NEVER homogeneous (as you and evreyone @ SAP might assume).
> Have you ever monitored your business process, to see
> if your people are working Smart. I bet you would not
> have monitored, because you didn't have SOLMAN. Its
> not just Clearing Invoices, making FI Entries,
> procuring materials. It is doing all these
> efficiently.
Yes, that's what you got told, BPs in a manufacturing company are MUCH more than that - and they ARE documented - indeed - but not in SolMan, there are other products for that purpose too and I doubt that we will pay a lot of $$$ again to put them into SolMan. We have documented about 250 of them - do you know any customer who have that much in their Solution Manager? If yes, then I would love to talk to that customer. It's not because SolMan may not be good for that - it's because SolMan is too SAP centric (or can you tell me how to "monitor" an interface to a non-SAP host system)?
>
> Have you ever seen what is going wrong technically in
> your Existing ERP system, I bet you would not have
> because you don't have System Monitoring in place.
So:
- if we have a working monitoring infrastructure (NOT based on SolMan and NOT reduced to SAP systems (there's network, backup, filesystems, VPN, encryption etc. etc. etc.)
- if we have a working workflow for change management (not based on SolMan and not only reduced to SAP products, there is more than that)
- if we have a ticket system (for SAP and all the other areas around including PC helpdesk, printers, blackberry and other stuff)
- if we are maintaining and tuning our systems from day 1 (01/01/1995 starting with 2.2d) ourselves, EWAs often led to unstartable inperformant systems or make them not come up, "burned kid avoids fire", thus the reason, why we don't use them at all.
then WHAT is the additional value of investing 7 mandays in a separate product?
I'm not saying, that it's a bad product, I'm blaming the product management for FORCING it to customers, denying the competence of a customer without a SolMan to find the right patches, assuming that people are unable to drive their business without it. They did the last 10 years and we MAY need something additional if SOA/ESA/Web2.0/whatever-name comes into production one day, but that is far ahead (if you ask me) and a different topic.
Keep in mind that not everyone uses just ERP 200x, EPy and M$ operating systems.
Markus -
Accessing Component Information for systems connected to Solution Manager
We currently aggregate system component information for our ABAP systems through the following manual (and tedious) process:
Log into each ABAP system
Menu: System -> Status
Click Component Information button (magnifying glass icon)
Retrieve the information: Component, Release, Level, Support Package Name, Description.
Recently, we were drilling through Solution Manager Root Cause analysis -> Change reporting and noticed that this information is available for each system. In the ABAP-Software data store. This led us to consider if this information is contained within the Solution Manager BW cubes.
However when we looked at the SMD Change Analysis (thinking this would map to what we saw in the Change Analysis reporting), we didn't see this information.
So, the question is, does anyone have any thoughts were the Component information for systems is stored in Solution Manager? Ideally, we would like to tap into this source for our own custom report as opposed to retrieving it manually from each system as I described.
Thanks,
Jeff HenkeHi Jeff,
the information about software components (and this is I think what you are looking for) is stored in the LMDB of Solution Manager. Each satellite system sends its component info into SLD (either in an external system or in Solution Manger itself). From there it is redirected to LMDB.
Try transaction LMDB in Solution Manager. There you have (depending on your SP-Stack) access to several reports to evaluate your landscape.
Best regards, Alexander -
System Monitoring in Solution Manager 4.0
Hi all,
I want to set up system monitoring for landscape BW, ECC and SCM systems using Solution Manager 4.0 and am new to Sol Man.
So could anyone please help me with the steps.
Thanks in advance,
Sandeep.Sandeep,
Trust me, there is no one resource that you can refer to and complete this system monitoring project. I recently configured this a couple of days ago. I can tell you that I haven't completed it yet. I have only completed the configuring the 'System Monitoring' part of it. I am yet to define monitors so that, I can monitor what I want of the satellite systems. So far, it took me about 4 days. Let me point out the basic steps you need to follow. Beyond that, please refer to the links I paste below:
Steps to configure 'System Monitoring' in Solution Manager:
1. Follow the 'Solution Manager Preparation' found under SPRO --> Solution Manager --> Read Me.
2. Make sure you have the latest ST-ICO and ST-SER installed in your Solution Manager (Note: 892412).
3. Make sure the Solution Manager has the latest support packages applied.
4. Prepare the 'Satellite Systems' as per note 455356:
a. Create the role 'SAP_BC_CSMREG' (if it doesn't exist) with the following authorization objects
--> S_CCM_RECV (with the objects and values mentioned in the above note)
--> S_RFC (with the objects and values mentioned in the above note)
--> S_RZL_ADM (with the objects and values mentioned in the above note)
--> S_CUS_CMP (with the objects and values mentioned in the above note)
b. Create a 'communication' user CSMREG (if it doesn't exist) and assign the profile S_CSMREG
5. Create the user CSMREG in Solution Manager using RZ21 transaction
-->RZ21 --> Technical Infrastructure --> Configure Central System --> Create CSMREG user (Provide the required password and confirm).
6. An agent needs to be registered in all the satellite systems that collects the monitor statistics and pass on to the Solution Manager. Before registering the agent in the satellite system, a 'CSMCONF' file has to be generated in the Solution Manager and store it in a central location which, will be used by the CCMS agent while registration. This CSMCONF file holds the communication details for the agent to talk to the Solution Manager. To create CSMCONF file, proceed as follows:
--> RZ21 --> Technical Infrastructure --> Configure Central System --> Create Start CSMCONF for Agents
--> Store the file in a central location that can be accessed by the satellite system/s.
7. In the satellite system, copy the file 'CSMCONF' to the working directory of SAPCCM4X (F:\usr\sap\PD1\SYS\DVEBMGS01\log\sapccm4x - for example. If the 'sapccm4x' folder does not exist, create one).
8. Copy the downloaded 'SAPCCM4X.exe' file to the kernel directory on the satellite system.
9. Execute "sapccm4x -R pf=<path of the instance profile>". This should ask for the 'CSMREG' password and the admin user password on the solution manager system. Please input the same and confirm other questions. Upon confirmation, the CCMS agent should be registered in the satellite system.
10.Make sure you establish the trusted RFC connection on the Solution Manager to the satellite system you would want to monitor. This you can do from 'SMSY' transaction.
11.After successfully creating the RFC connections, and assigning the system to a logical component, please go to transaction, 'SOLUTION_MANAGER'. You can see the monitored system in the System Overview.
Below are the reference links:
Weblogs Related to Solution Manager
Hope this helps. Award with relevant points if my response is helpful.
Thank you. -
Setting up EarlyWatch in Solution manager
Hi Guys
I am trying to configure Early Watch in solution manager(System Id u2013SOL , Installation No - 0020306432) for an satellite system (System Id -DEV u2013Installation No : 0020181089).
I have followed all the configuration steps listed below :
1. Configuration RFCs to market place SAPOSS and to satellite Systems and RFC Back to solution manager. All RFC like SAPOSS and Back has been tested from SDCCN (Solution manager and satellite system)
2. Configured SDCCN in solution manager and in satellite system except u201CGenerate Includes for Service data control centeru201D in SPRO of solution manager as this process is getting time out and not letting us to generate all the includes
3. Activated Service data Control center locally and assign solution manager as u2018Master system for allu2019.
4. Activated SDCCN in satellite system(DEV) ,Created Earlywatch Service in Solution manager for DEV system and also created/Started u2018Refresh Sessionu2019 in SDCCN of DEV(Satellite system)
5. This successfully shows me Early watch link in u2018Waitingu2019 Status in solution manager.
6. I click on u2018Start Service Processingu2019 to Schedule/Run u201CSM:EXEC SERVICESu201D background job .
Problem : Background job u201CSM:EXEC SERVICESu201D get cancelled after some time and throws a Dump which is pasted below.
Dump shows that an include u2018/1CAGTF/IF_LOGFUNC_000393u2019 is missing which should have been generated while activating the includes for SDCCN in SPRO of solution manager.
I found includes from u2018/1CAGTF/IF_LOGFUNC_000001u2019 to u2018/1CAGTF/IF_LOGFUNC_000353u2019 in the system as it seems that not all include have been generated .
*Could you please help me to provide some SAP note so that I would be able to generate all the includes . *
DUMP
Runtime Errors SYNTAX_ERROR
Date and Time 24.05.2008 00:01:02
Short text
Syntax error in program "RDSVASAEW_ROOT_____________073 ".
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLDSVAS_PROC" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program "RDSVASAEW_ROOT_____________073
" in include "RDSVASAEW_ROOT_____________073 " in
line 96:
"INCLUDE report "/1CAGTF/IF_LOGFUNC_000393" not found."
The include has been created and last changed by:
Created by: "SAP "
Last changed by: "SAP "
What can you do?
Please eliminate the error by performing a syntax check
(or an extended program check) on the program "RDSVASAEW_ROOT_____________073
You can also perform the syntax check from the ABAP Editor.
If the problem persists, proceed as follows:
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
The following syntax error was found in the program
RDSVASAEW_ROOT_____________073 :
"INCLUDE report "/1CAGTF/IF_LOGFUNC_000393" not found."
How to correct the error
Probably the only way to eliminate the error is to correct the program.
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
System environment
SAP-Release 700
Application server... "mslsol"
Network address...... "192.168.193.154"
Operating system..... "Windows NT"
Release.............. "5.2"
Hardware type........ "2x Intel 801586"
Character length.... 16 Bits
Pointer length....... 32 Bits
Work process number.. 10
Shortdump setting.... "full"
Database server... "MSLSOL"
Database type..... "ORACLE"
Database name..... "SOL"
Database user ID.. "SAPSR3"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Aug 29 2006 00:18:21"
create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version. "OCI_10201_SHARE (10.2.0.2.0) "
Patch level. 75
Patch text.. " "
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
SAP database version. 700
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
Memory consumption
Roll.... 8176
EM...... 29266272
Heap.... 0
Page.... 24576
MM Used. 24845128
MM Free. 236264
User and Transaction
Client.............. 600
User................ "BASISA"
Language key........ "E"
Transaction......... " "
Program............. "SAPLDSVAS_PROC"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
Termination occurred in the ABAP program "SAPLDSVAS_PROC" - in "EXECUTE".
The main program was "RDSMOPBACK_AUTOSESSIONS ".
In the source code you have the termination point in line 2146
of the (Include) program "LDSVAS_PROCCD0".
The program "SAPLDSVAS_PROC" was started as a background job.
Job Name....... "SM:EXEC SERVICES"
Job Initiator.. "BASISA"
Job Number..... 00384300
Source Code Extract
Line
SourceCde
2116
ls_stdparameter-versnr = po_ctnode->versnr.
2117
ls_stdparameter-grp = po_ctnode->grp.
2118
ls_stdparameter-id = po_ctnode->id.
2119
ls_stdparameter-reference_versnr = po_ctnode->reference_versnr.
2120
ls_stdparameter-reference_grp = po_ctnode->reference_grp.
2121
ls_stdparameter-reference_id = po_ctnode->reference_id.
2122
else.
2123
ls_stdparameter-grp = pf_grp.
2124
ls_stdparameter-versnr = pf_versnr.
2125
ls_stdparameter-reference_grp = pf_grp.
2126
ls_stdparameter-reference_versnr = pf_versnr.
2127
endif.
2128
2129
Formroutinen aufrufen
2130
loop at actseq
2131
into ls_actrel
2132
where exec_time = pf_exec_time.
2133
check ls_actrel-exec_time ne gf_exec_time_event
2134
or ( ls_actrel-exec_time = gf_exec_time_event and
2135
ls_actrel-event = pf_event ).
2136
call function 'DSVAS_CDMNT_FORM_NAME'
2137
exporting
2138
pf_container_type = 'A'
2139
pf_form_number = ls_actrel-action
2140
importing
2141
pf_form_name = lf_form_name.
2142
perform (lf_form_name)
2143
in program (program)
2144
using ls_stdparameter
2145
if found.
>>>>>
endloop.
2147
endmethod. "execute
2148
2149
Collect_Known_Events
2150
method collect_known_events.
2151
data: ls_actseq type line of ltype_action_sequence_table,
2152
lf_event type dsvasactseq-event.
2153
2154
loop at actseq into ls_actseq
2155
where ( exec_time = gf_exec_time_event and
2156
event ne space )
2157
or exec_time = gf_exec_time_1
2158
or exec_time = gf_exec_time_2
2159
or exec_time = gf_exec_time_3
2160
or exec_time = gf_exec_time_modus_close.
2161
if ls_actseq-exec_time = gf_exec_time_event.
2162
read table pt_events with table key table_line = ls_actseq-event
2163
transporting no fields.
2164
if sy-subrc ne 0.
2165
insert ls_actseq-event into table pt_events.
Contents of system fields
Name
Val.
SY-SUBRC
0
SY-INDEX
1
SY-TABIX
1
SY-DBCNT
0
SY-FDPOS
30
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
SY-UCOMM
SY-TITLE
DSWP: Execute rule set
SY-MSGTY
E
SY-MSGID
FL
SY-MSGNO
046
SY-MSGV1
DSVAS_TOOLS_PACKAGE_GET
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO
0
SY-DATUM
20080524
SY-UZEIT
000049
SY-XPROG
SAPCNVE
SY-XFORM
CONVERSION_EXIT
Active Calls/Events
No. Ty. Program Include Line
Name
11 FORM SAPLDSVAS_PROC LDSVAS_PROCCD0 2146
EXECUTE
10 METHOD SAPLDSVAS_PROC LDSVAS_PROCCD0 2142
LCL_ACTION_SEQUENCE=>EXECUTE
9 METHOD SAPLDSVAS_PROC LDSVAS_PROCCTI 1741
LCL_CHECK_TREENODE=>EXECUTE
8 METHOD SAPLDSVAS_PROC LDSVAS_PROCCTI 1792
LCL_CHECK_TREENODE=>EXECUTE_AND_PROPAGATE
7 METHOD SAPLDSVAS_PROC LDSVAS_PROCCTI 1806
LCL_CHECK_TREENODE=>EXECUTE_AND_PROPAGATE
6 METHOD SAPLDSVAS_PROC LDSVAS_PROCSEI 2025
LCL_SESSION=>EXECUTE
5 METHOD SAPLDSVAS_PROC LDSVAS_PROCSEI 1582
LCL_SESSION=>CONTEXT_INSTANCES_CREATE
4 METHOD SAPLDSVAS_PROC LDSVAS_PROCSEI 1995
LCL_SESSION=>EXECUTE
3 FUNCTION SAPLDSVAS_PROC LDSVAS_PROCU02 303
DSVAS_PROC_SESSION_OPEN
2 METHOD CL_DSMOP_SOLUTION=============CP CL_DSMOP_SOLUTION=============CM01P 184
CL_DSMOP_SOLUTION=>START_PERIODIC_SERVICES
1 EVENT RDSMOPBACK_AUTOSESSIONS RDSMOPBACK_AUTOSESSIONS 72
START-OF-SELECTION
Chosen variables
Name
Val.
No. 11 Ty. FORM
Name EXECUTE
PF_EXEC_TIME
I
4
9
0
0
PF_EVENT
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
PO_CTNODE
|
| 2000D000 |
| E0001C00 |
| PF_GRP |
| |
| 22222222222222222222 |
| 00000000000000000000 |
| 00000000000000000000 |
| 00000000000000000000 |
| PF_VERSNR |
| 00000 |
| 33333 |
| 00000 |
| 00000 |
| 00000 |
| <%_L02E>-EXEC_TIME |
| ??? |
| ?????? |
| ?????? |
| <%_L02F> |
| I |
| 4 |
| 9 |
| 0 |
| 0 |
| LS_ACTREL-EXEC_TIME |
| I |
| 4 |
| 9 |
| 0 |
| 0 |
| GF_EXEC_TIME_EVENT |
| E |
| 4 |
| 5 |
| 0 |
| 0 |
| SYST-REPID |
| SAPLDSVAS_PROC |
| 5454455455554422222222222222222222222222 |
| 310C43613F02F300000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| LS_ACTREL-EVENT |
| |
| 2222222222222222222222222222222222222222 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| SY-SAPRL+0(4) |
| 70 |
| 33 |
| 70 |
| 00 |
| 00 |
| LS_ACTREL-ACTION |
| 108 |
| 333 |
| 108 |
| 000 |
| 000 |
| LF_FORM_NAME |
| ACTION_108 |
| 44544453332222222222222222222222 |
| 1349FEF1080000000000000000000000 |
| 00000000000000000000000000000000 |
| 00000000000000000000000000000000 |
| ME->PROGRAM |
| RDSVASAEW_ROOT_____________073 |
| 5455454455544555555555555553332222222222 |
| 243613157F2FF4FFFFFFFFFFFFF0730000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| %_DUMMY$$ |
| |
| 2222 |
| 0000 |
| 0000 |
| 0000 |
| LS_STDPARAMETER |
| EA6000000000255###ESESSION 00047EA_ROOT |
| 4433333333333330004545544422222222222222222222222222222222222222222223333344554452222222222222 |
| 516000000000255010535339FE00000000000000000000000000000000000000000000004751F2FF40000000000000 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| No. 10 Ty. METHOD |
| Name LCL_ACTION_SEQUENCE=>EXECUTE |
| PF_EXEC_TIME |
| I |
| 4 |
| 9 |
| 0 |
| 0 |
| PF_EVENT |
| |
| 2222222222222222222222222222222222222222 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| PO_CTNODE |
|
2000D000
E0001C00
PF_GRP
22222222222222222222
00000000000000000000
00000000000000000000
00000000000000000000
PF_VERSNR
00000
33333
00000
00000
00000
<%_L02E>-EXEC_TIME
<%_L02F>
I
4
9
0
0
LS_ACTREL-EXEC_TIME
I
4
9
0
0
LS_ACTREL-EVENT
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
LS_ACTREL-ACTION
108
333
108
000
000
LF_FORM_NAME
ACTION_108
44544453332222222222222222222222
1349FEF1080000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
ME->PROGRAM
RDSVASAEW_ROOT_____________073
5455454455544555555555555553332222222222
243613157F2FF4FFFFFFFFFFFFF0730000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
LS_STDPARAMETER
EA6000000000255###ESESSION 00047EA_ROOT
4433333333333330004545544422222222222222222222222222222222222222222223333344554452222222222222
516000000000255010535339FE00000000000000000000000000000000000000000000004751F2FF40000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
No. 9 Ty. METHOD
Name LCL_CHECK_TREENODE=>EXECUTE
PF_EXEC_TIME
I
4
9
0
0
PF_EVENT
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
GF_EXEC_TIME_ATTRIBUTES
a
6
1
0
0
RSJOBINFO
00000000000000 ##
2222222222222222222222222222222233333333333333222222222222222222222222222222222200
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
ME
|
| 2000D000 |
| E0001C00 |
| GT_OPEN_SESSIONS |
| Table IT_3668[1x44] |
| FUNCTION-POOL=DSVAS_PROCDATA=GT_OPEN_SESSIONS |
| Table reference: 1911 |
| TABH+ 0(20) = 807E0D3E000000000000000077070000540E0000 |
| TABH+ 20(20) = 010000002C000000FFFFFFFF0417010010040000 |
| TABH+ 40( 8) = 10000000A4318001 |
| store = 0x807E0D3E |
| ext1 = 0x00000000 |
| shmId = 0 (0x00000000) |
| id = 1911 (0x77070000) |
| label = 3668 (0x540E0000) |
| fill = 1 (0x01000000) |
| leng = 44 (0x2C000000) |
| loop = -1 (0xFFFFFFFF) |
| xtyp = TYPE#000007 |
| occu = 16 (0x10000000) |
| access = 4 (ItAccessHashed) |
| idxKind = 0 (ItIndexNone) |
| uniKind = 1 (ItUnique) |
| keyKind = 3 (user defined) |
| cmpMode = 8 (cmpManyEq) |
| occu0 = 1 |
| groupCntl = 0 |
| rfc = 0 |
| unShareable = 0 |
| mightBeShared = 0 |
| sharedWithShmTab = 0 |
| isShmLockId = 0 |
| gcKind = 0 |
| isUsed = 1 |
| isCtfyAble = 1 |
| >>>>> Shareable Table Header Data <<<<< |
| tabi = 0xC0AB0D3E |
| pgHook = 0x00000000 |
| idxPtr = 0x78F10D3E |
| shmTabhSet = 0x00000000 |
| id = 2504 (0xC8090000) |
| refCount = 0 (0x00000000) |
| tstRefCount = 0 (0x00000000) |
| lineAdmin = 16 (0x10000000) |
| lineAlloc = 16 (0x10000000) |
| shmVersId = 0 (0x00000000) |
| shmRefCount = 1 (0x01000000) |
| >>>>> 1st level extension part <<<<< |
| regHook = Not allocated |
| collHook = Not allocated |
| ext2 = Not allocated |
| >>>>> 2nd level extension part <<<<< |
| tabhBack = Not allocated |
| delta_head = Not allocated |
| pb_func = Not allocated |
| pb_handle = Not allocated |
| GF_EXEC_TIME_BEFORE_REPORT_GEN |
| R |
| 5 |
| 2 |
| 0 |
| 0 |
| GF_EXEC_TIME_INIT |
| I |
| 4 |
| 9 |
| 0 |
| 0 |
| ME->INITIALIZED |
| |
| 2 |
| 0 |
| 0 |
| 0 |
| GF_EXEC_TIME_AFTER |
| A |
| 4 |
| 1 |
| 0 |
| 0 |
| ME->ACTSEQ |
|
2000D000
C0003C00
SCREEN
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
ME->HAS_TABLES
X
5
8
0
0
SYST
##########################A###P##############################################T###ÿ##### u####
0000000000000000000000100040005000000050000000007000000000000000000000000000105000F00050270000
1000101000001000000000E010101000000000C0000000004000000000000000000000000000604000F00080050600
0000000000000000000000000000000000000000000000001000000000000000000000000000000000000040000000
00000000000000000000000000000000000000000000000070000000000000000000000000000000000000D000000C
SY-REPID
SAPLDSVAS_PROC
5454455455554422222222222222222222222222
310C43613F02F300000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
ME->CHECK_TABLES
|
| 2000D000 |
| 3000CC00 |
| No. 8 Ty. METHOD |
| Name LCL_CHECK_TREENODE=>EXECUTE_AND_PROPAGATE |
| PF_EXEC_TIME |
| I |
| 4 |
| 9 |
| 0 |
| 0 |
| PF_EVENT |
| |
| 2222222222222222222222222222222222222222 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| PF_CON |
| SESSION |
| 5455444222 |
| 35339FE000 |
| 0000000000 |
| 0000000000 |
| PF_INS |
| |
| 2222222222222222222222222222222222222222 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| ME->DYNAMIC |
| X |
| 5 |
| 8 |
| 0 |
| 0 |
| ME |
|
2000D000
E0001C00
GF_SESSION_DEF_TYPE_MORE_DEV
L
4
C
0
0
ME->ACTIVE
X
5
8
0
0
GF_SESSION_DEF_TYPE_VERSION
V
5
6
0
0
ME->CON
SESSION
5455444222
35339FE000
0000000000
0000000000
ME->INS
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
ME->CHILD_CONDSEQ
F0000000
F0000000
GF_CONTEXT_SESSION
SESSION
5455444222
35339FE000
0000000000
0000000000
ME->CHILDREN
Table[initial]
LO_TNODE
|
| F0000000 |
| F0000000 |
| %_ARCHIVE |
| |
| 2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| No. 7 Ty. METHOD |
| Name LCL_CHECK_TREENODE=>EXECUTE_AND_PROPAGATE |
| PF_EXEC_TIME |
| I |
| 4 |
| 9 |
| 0 |
| 0 |
| PF_EVENT |
| |
| 2222222222222222222222222222222222222222 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| PF_CON |
| SESSION |
| 5455444222 |
| 35339FE000 |
| 0000000000 |
| 0000000000 |
| PF_INS |
| |
| 2222222222222222222222222222222222222222 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| ME |
|
2000D000
F0000C00
ME->CHILD_CONDSEQ
|
| F0000000 |
| F0000000 |
| ME->CHILDREN |
| Table IT_3674[26x8] |
| DATA=CHILDREN
Table reference: 1919
TABH+ 0(20) = 68550D3E00000000000000007F0700005A0E0000
TABH+ 20(20) = 1A00000008000000800100000417010030080000
TABH+ 40( 8) = 10000000C1288001
store = 0x68550D3E
ext1 = 0x00000000
shmId = 0 (0x00000000)
id = 1919 (0x7F070000)
label = 3674 (0x5A0E0000)
fill = 26 (0x1A000000)
leng = 8 (0x08000000)
loop = 384 (0x80010000)
xtyp = TYPE#000029
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 4 (cmpSingleEq)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0xB0B10D3E
pgHook = 0xF0882E3E
idxPtr = 0x00000000
shmTabhSet = 0x00000000
id = 2508 (0xCC090000)
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 48 (0x30000000)
lineAlloc = 48 (0x30000000)
shmVersId = 0 (0x00000000)
shmRefCount = 1 (0x01000000)
>>>>> 1st level extension part <<<<<
regHook = Not allocated
collHook = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
LO_TNODE
|
| 2000D000 |
| E0001C00 |
| LO_CTNODE |
|
2000D000
E0001C00
%_SPACE
2
0
0
0
No. 6 Ty. METHOD
Name LCL_SESSION=>EXECUTE
PF_EXEC_TIME
I
4
9
0
0
PF_EVENT
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
PF_CON
SESSION
5455444222
35339FE000
0000000000
0000000000
PF_INS
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
ME->ACTSEQ
|
| F0000000 |
| F0000000 |
| ME->GLOBAL_CHECK_GRP |
| EA_ROOT |
| 44554452222222222222 |
| 51F2FF40000000000000 |
| 00000000000000000000 |
| 00000000000000000000 |
| ME->GLOBAL_VERSNR |
| 00047 |
| 33333 |
| 00047 |
| 00000 |
| 00000 |
| ME->CHECK_TREE |
|
2000D000
F0000C00
GF_EXEC_TIME_MODUS_CLOSE
W
5
7
0
0
ME->RAISED_EVENTS
Table[initial]
GF_EXEC_TIME_LOGICAL_COMPLETE
L
4
C
0
0
No. 5 Ty. METHOD
Name LCL_SESSION=>CONTEXT_INSTANCES_CREATE
LT_ZOMBIES
Table[initial]
LS_CTREL-TREENODE
F0000000
F0000000
LO_ZOMBIE
|
| F0000000 |
| F0000000 |
| LT_NEW_CONINS |
| Table IT_3670[1x100] |
| FUNCTION-POOL=DSVAS_PROCCLASS=LCL_SESSIONMETHOD=CONTEXT_INSTANCES_CREATEDATA=LT_NEW_CONINS |
| Table reference: 1920 |
| TABH+ 0(20) = 90C50D3E30F3DE3D0000000080070000560E0000 |
| TABH+ 20(20) = 0100000064000000080100000417010060140000 |
| TABH+ 40( 8) = 01000000C1248401 |
| store = 0x90C50D3E |
| ext1 = 0x30F3DE3D |
| shmId = 0 (0x00000000) |
| id = 1920 (0x80070000) |
| label = 3670 (0x560E0000) |
| fill = 1 (0x01000000) |
| leng = 100 (0x64000000) |
| loop = 264 (0x08010000) |
| xtyp = TYPE#000094 |
| occu = 1 (0x01000000) |
| access = 1 (ItAccessStandard) |
| idxKind = 0 (ItIndexNone) |
| uniKind = 2 (ItUniqueNon) |
| keyKind = 1 (default) |
| cmpMode = 2 (cmpSingleMcmpR) |
| occu0 = 1 |
| groupCntl = 0 |
| rfc = 0 |
| unShareable = 0 |
| mightBeShared = 1 |
| sharedWithShmTab = 0 |
| isShmLockId = 0 |
| gcKind = 0 |
| isUsed = 1 |
| isCtfyAble = 1 |
| >>>>> Shareable Table Header Data <<<<< |
| tabi = 0x08AB0D3E |
| pgHook = 0x00000000 |
| idxPtr = 0x00000000 |
| shmTabhSet = 0x00000000 |
| id = 2505 (0xC9090000) |
| refCount = 0 (0x00000000) |
| tstRefCount = 0 (0x00000000) |
| lineAdmin = 1 (0x01000000) |
| lineAlloc = 1 (0x01000000) |
| shmVersId = 0 (0x00000000) |
| shmRefCount = 1 (0x01000000) |
| >>>>> 1st level extension part <<<<< |
| regHook = 0xB0F0BE3D |
| collHook = 0x00000000 |
| ext2 = 0x00000000 |
| >>>>> 2nd level extension part <<<<< |
| tabhBack = Not allocated |
| delta_head = Not allocated |
| pb_func = Not allocated |
| pb_handle = Not allocated |
| <LFS_CONINS> |
| SESSION |
| 54554442222222222222222222222222222222222222222222 |
| 35339FE0000000000000000000000000000000000000000000 |
| 00000000000000000000000000000000000000000000000000 |
| 00000000000000000000000000000000000000000000000000 |
| ME |
|
90006000
4000B000
<LFS_CONINS>-CON
SESSION
5455444222
35339FE000
0000000000
0000000000
<LFS_CONINS>-INS
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
SY
##########################A###P##############################################T###ÿ##### u####
0000000000000000000000100040005000000050000000007000000000000000000000000000105000F00050270000
1000101000001000000000E010101000000000C0000000004000000000000000000000000000604000F00080050600
0000000000000000000000000000000000000000000000001000000000000000000000000000000000000040000000
00000000000000000000000000000000000000000000000070000000000000000000000000000000000000D000000C
GF_EXEC_TIME_BEFORE
B
4
2
0
0
No. 4 Ty. METHOD
Name LCL_SESSION=>EXECUTE
PF_EXEC_TIME
I
4
9
0
0
PF_EVENT
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
PF_CON
2222222222
0000000000
0000000000
0000000000
PF_INS
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
ME->ACTSEQ
|
| F0000000 |
| F0000000 |
| ME |
|
90006000
4000B000
ME->LOGICAL_COMPLETE
2
0
0
0
GF_EXEC_TIME_COMPLETE
C
4
3
0
0
ME->COMPLETE
2
0
0
0
SY-XFORM
CONVERSION_EXIT
444545544454545222222222222222
3FE65239FEF5894000000000000000
000000000000000000000000000000
000000000000000000000000000000
No. 3 Ty. FUNCTION
Name DSVAS_PROC_SESSION_OPEN
PF_HANDLE_TO_USE
0
0000
0000
PF_MAX_TREE
2
0
0
0
PF_MODE
C
4
3
0
0
PS_SESSION_NUMBER
EA6000000000255
443333333333333
516000000000255
000000000000000
000000000000000
PF_HANDLE
1
0000
1000
PF_HIDE_TREE
2
0
0
0
PF_MODE_USED
2
0
0
0
PF_NEXT_CHECK_GRP
22222222222222222222
00000000000000000000
00000000000000000000
00000000000000000000
PF_NEXT_CHECK_ID
00000
33333
00000
00000
00000
PF_NEXT_CON
2222222222
0000000000
0000000000
0000000000
PF_NEXT_INS
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
PT_ERRORS
Table[initial]
PT_FRONTEND_TREE[]
Table[initial]
PF_LANGUAGE
E
4
5
0
0
<%_TABLE_DSVASSESSADMIN>
LF_BUNDLE_VERSNR
00038
33333
00038
00000
00000
DSVASRESULTSGEN-CLUSTR
0
00
00
PS_SESSION_NUMBER-SESSNO
6000000000255
3333333333333
6000000000255
0000000000000
0000000000000
LS_OPEN_SESSIONS-SESSION
|
| 90006000 |
| 4000B000 |
| LO_SESSION |
|
90006000
4000B000
LS_OPEN_SESSIONS
EA6000000000255C####k#
4433333333333334009060
51600000000025531040B0
0000000000000000000000
0000000000000000000000
SY-XPROG
SAPCNVE
5454454222222222222222222222222222222222
3103E65000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
LS_SESSDEFGEN-MULTI_USERPlease replace the Service Definitions in your SAP Solution Manager
system as described in SAP Note 727998.
As of SAP Solution Manager 7.0 (= 4.0) Support Package Stack 15 (which
includes ST-PI 700_2005_1 SP06) you can trigger the required steps
within transaction SDCCN:
Menu Utilities -> Maintain Service Definitions ->
Select 'Delete and Replace Service Definitions -> Confirm this
selection-> Confirm that you want to delete the definitions -> Confirm
that a new task 'Service Definition Refresh' was created
Take a note of the task id -> Review the log for this task id when it
is completed. You should not see any errors for either the update
of a Service Definitions table or the generation of any re-import
include.
Reschedule SM:EXEC SERVICES and the reported dump will no longer
occur. -
Service desk configuration for solution manager
hi this ,
sudheer i have configured the service desk configuration on my solution manager system with all satellite system, i have mapped all business partners in my satellite systems to solution manager , and also iam able to see all messages are send by business partners using DSWP transaction, but how to see reply from solution manager sytem to satellite system ( message inbox of satellite system)
can any body tell the configuration of satellite system to see reply message from solution manager ?
thanks and regards
sudheerkoppala@ g ma il .com>
sudheer koppala wrote:
> sudheer i have configured the service desk configuration on my solution manager system with all satellite system, i have mapped all business partners in my satellite systems to solution manager , and also iam able to see all messages are send by business partners using DSWP transaction, but how to see reply from solution manager sytem to satellite system ( message inbox of satellite system)
> can any body tell the configuration of satellite system to see reply message from solution manager ?
There is no "message inbox" in satellite systems, but you can use the SAP Solution Manager to have a central access to all reported messages.
Configure Work Center "Incident Management" in SAP Solution Manager and grant access for message reporters.
See answers to similar question in accessing the service desk message from satellite system
Best regards,
Ruediger
Maybe you are looking for
-
When I go into option menu, then click on the content tab, nothing happens; regardless of the duration of the waiting period, as when you click it and wait, you might as well walk away, because it will not load even if you wait an hour; THE OTHER TAB
-
I used FF for some time, then I looked up a page in Turkish (not my language), and the page appeared in a small format, and I couldn't open it. Even when I right-clicked the FF icon, I couldn't close it, so I turned the computer off, and restarted, b
-
Need suggestion for hooking up 3 monitors to my desktop PC
Hello everyone, I am wanting to know the best and cheapest way to hook up 3 monitors to my PC. I have an HP Pavilion HPE h8-1234 with a 6 core AMD FX-6120 processor at 3.5ghz(up to 4.1ghz in turbo) with 10gb of DDR3-1600 RAM. My graphics card is a Ra
-
Hi guys. I have a problem and can´t solve it. I am a few rookie in oracle. I have to load a txt file. I develope the next ctr: LOAD DATA INFILE './file.txt' INTO table REPLACE FIELDS TERMINATED BY '|' OPTIONALLY ENCLOSED BY '"' field_1, field_2, ID S
-
SQLEXEC on each new trail file or just on replicat start to capture current FILESEQNO?
Dear community, I need to capture fileseqno of the trail file that replicat is processing. But I only need to capture it once without overhead of adding fileseqno column to target tables. I clearly understand that using colmap ( usedefaults, FILESEQN