on 04-06-2007 5:22 PM
I have setup solution manager 4.0, Configured Earlywatch. Now the Solution screen shows :
SAP EarlyWatch Alert 31.03.2007 QST (0020)
SAP EarlyWatch Alert 01.04.2007 PPD (0020)
SAP EarlyWatch Alert 01.04.2007 PPD (0020)
SAP EarlyWatch Alert 01.04.2007 QST (0020)
SAP EarlyWatch Alert 07.04.2007 PPD (0020)
SAP EarlyWatch Alert 07.04.2007 QST (0020)
SAP EarlyWatch Alert 07.04.2007 QST (0020)
Some of these show data is available. when i process the reports a background job is started:
SM:EXEC SERVICES 000000006300100
this job immeidately stops saying it is cancelled.
The joblog says this:
06.04.2007 20:12:47 Job started
06.04.2007 20:12:47 Step 001 started (program DSMOPBACK_AUTOSESSIONS, variant &0000000000054, user ID SOLMAN)
06.04.2007 20:12:48 Solution COMPANY is being edited (Operations)
06.04.2007 20:12:48 Trying to perform session 0010000000058
06.04.2007 20:12:51 ABAP/4 processor: SYNTAX_ERROR
06.04.2007 20:12:51 Job cancelled
How do i make sure that this job is executed successfully?
I am facing the same problem when i am trying to view the Service Level Reports.
how do i go about?
Does anyone have the exact steps required in setting up the solutions of Solution Manager?
Is there a coresponding Short dump in ST22 for the syntax error message? How bout an entry in the system log (SM21)?
Is the user ID SOLMAN ok? Locked, improper authorizations?
Thanks,
Tim
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, please verify the short dump.
If the syntax error is similar to this (probably with a different program), then see the solution below:
The following syntax error occurred in the program
RDSVASAEW_ROOT_____________070 : "INCLUDE report "/1CAGTF/IF_LOGFUNC_000393" not found."
I happens in general, after implementing a new add-on ST-SER.
Follow instructions of SAP Note 727998 "Complete Replacement of Service Definitions for SDCC/SDCCN"
The steps are also explained in the SAP Solution Manager IMG
- transaction SPRO -> SAP Reference IMG
-> SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Basic Settings -> SAP Solution Manager System -> Operations -> Setup Service Data Control Center -> Generate Includes for Service Data Control Center
The steps are mainly
- update Service Definitions (that are table, which control which data is collected for a specific service session)
- regenerate logfuncs
Best regards,
Ruediger Stoecker
Well, for starters, read that note carefully. The Service Definitions file is only for systems which DO NOT have access to SAP Support - is yours such a system? THis is an odd solution from SAP since if you don't have access to SAP support, you probably won't have access to a sapserv. The format is just ftp://sapservX, where X is the sapserver your firm conencts - ususally broken out by geographical locations. Were you not able to run the service definition refresh from your system?
If not, I'd personally open a message with SAP and request that they send it to you - this should not be a big deal and you can open an OSS message over the phone still.
Typically, SAP attaches these files to the OSS note, but not in this case
I hope these solutions help.
-Tim
Hi,
I just traced the steps i did for enabling the EWA Service.
Firstly, SDCC_OSS RFC is not createed automatically, and so my OSS1 does not function. i think the service definition refresh is not happning because my connectivity to sap is not there.
-
can you please tell me how do i create SDCC_OSS RFC.
-
And what is the concept of the master data. I have DEV, QST ,PPD conectied to my solution manager.
I feel that i have missed out some steps in configuring my EWA, any guide?
I am sorry, I am getting a bit basic, but i am helpless,cannot get a straight way to setup my solution manager.
Lalchand.R
Hi,
Check this note <b>763561</b>
Here's a part of note I copied.
SDCC_OSS uses its own logon details:
User: SDCC_NEW
Password: DOWNLOAD
Client: 001
To ensure SDCC_OSS can be created correctly, SAPOSS itself has to be maintained correctly. The best way to maintain SAPOSS is via settings in transaction OSS1, as described in note 33135.
It is recommended that SAPOSS also use 'Load distribution'; to achieve this use note 766505.
Is there a template against which I check these destinations:
Target host: /H/X1/S/sapdp99/H/X2/S/sapdp99/H/oss001
with
X1 = customer saprouter IP address
X2 = IP address of sapservX ( sapserv1 = 194.117.106.129,
sapserv2 = 194.39.131.34, sapserv3 = 147.204.2.5,
sapserv4 = 204.79.199.2, sapserv5 = 194.39.138.2,
sapserv6 = 194.39.139.16, sapserv7 = 194.39.134.35 )
System number = 01
When SAPOSS is updated, the copy SDCC_OSS must be updated manually. The best way to do this is to delete SDCC_OSS in SM59 and then recreate it, via
SDCCN -> Goto->Settings-> Task Specific -> RFC destinations
-> Change Mode -> Create destination to SAPNet R/3 Frontend
a) Destination to connect to SAP Solution Manager
The connections between satellite system and SAP Solution Manager are described in the configuration guide for SAP Solution Manager.
This will solve you problem.
Feel free to revert back.
--Ragu
HI Raghu,
Thanks for all the help.
I solved the issue using these steps.
Step 1:
In Transaction SE38, you must execute report
BDL_DELETE_ALL_TABLES . The service
definition tables are now empty.
Step 2: Please update the service Definitions.
(SDCC -> Maintenance -> Refresh -> Service Definitions)
Step 3:
Now call function module
'BDL_GENERATE_LOGFUNC_INCLUDES'
if you have installed ST-PI on
Basis Rel 4*. See note 91488. )
using Transaction SE37 and 'Single test (F8)' . Assign the value
'ALL' to the import parameter 'OPTION' (keep the default values
for all other parameters) and execute the module. Note that
during this activity there is an increased system load. During
this time you can not use SDCC, or you will generate a shortdump
Please retest your current issue when this has completed.
Ths mistake i did was i used this /BDL/_GENERATE_LOGFUNCINCLUDES' and nuthing was happening.
@ Ruediger Stoecker:
Thanks for your tip. Implementing note 727998 solved another (similar) problem of mine.
I had an SAP EarlyWatch Alert, described as "Data is available", but I just couldn't get any document out of it.
I overlooked that few errors was reported when "Generating reimport includes" few days ago, when I was configuring EWA...
Thanks (once again), regards,
Nenad
User | Count |
---|---|
84 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.