Hi All,
During the Create of Decision Table, in the Choose the parameter category from the query results.
In the insert row enter the category id ( like CA_01,...) and match the support team .
So it automatically detect the support team after selecting the Multilevel Categorization depend up on ID you have chosen.
Rg,
Karthik
Hi Adriana,
Check the below sap demo
https://websmp103.sap-ag.de/~sapidb/011000358700000478072011E/index.htm
Select the customize or workbench task and release it.( not the transport,only the task).
check the demo for more details.
Rg,
Karthik
Dear All ,
I have done the technical monitoring configuration and in the system monitoring , i could see some metrices are not delivered any data " No Metrics Delivered " .
When I click the metric troubleshooting for the metrics . I fould that DPC Pull core extractor is ended in warning with below message .
Could anyone have any idae how to fix the below issue.
Regards
Bala
Hi Nick
Please check the following Blog:
Incident Management and Change Request Management: E-Mail functionality in SAP Solution Manager 7.1
http://scn.sap.com/docs/DOC-35291
I hope this will help.
Thanks
Vikram
Hi All,
I have gone through various ST13 documentations and did some R&D,i came to know that SAP provides a configuration to sort the process chains based on statuses also.In addition it provides to sort the process chains based on Process types and variants (which will be very helpful for determining which step in process chain had a longer run by comparing with other dates).
Click on Process Types(F6)
Sample Output:
Comparing one particular variant
For reporting purpose this option seems to be provide a better information than the normal process chain information from st13.
Regards,
Kannan
Hi PK
There is no tool for moving the SLFN documents from one solman to the other. The only option to keep the already created tickets is to upgrade the the existing solman system to release 7.1.
In SOlman 7.1 SM* transaction types are comming so during the upgrade we don´t make any changes to the old transaction types like SLFN, so the upgrade should not change your current configuration in solman 7.0 for incident management.
You will not have any impact on Service Desk when using the old transaction type SLFN.
So there can be only one recommendation for your situation:
Perform an UPGRADE and please don't go for a fresh installation with data migration afterwards.
There is no easy transfer of CRM document (as incidents, change requests, issues, top issues, ...) available.
Advantages of the upgrade:
- standard procedure
- configuration and data is available after the upgrade
The solman 7.1 is coming with new transaction types that you need to customizing and it is not touching the old transaction types existing in solman 7.0.
Please, take a look at this:
http://scn.sap.com/docs/DOC-30133
Also check below note which answers few FAQ's:
1567003: FAQ: ST710 Incident Management Frequently Asked
Check below Wiki as well:
http://wiki.sdn.sap.com/wiki/display/SAPITSM/Configuration+and+Administration+of+ITSM
(all in one line)
And select Configuration Guide - Application Incident Management
Also check the External Service Desk Functionality.
Please follow the path to the nodes listed below.
SAP Solution Manager Implementation Guide
SAP Solution Manager
Capabilities (Optional)
IT Service Management
External Integration
Service Desk
External Service Desk
Thanks
Vikram
Hi
Please check and implement the following note:
Thanks
Vikram
Hi Dev,
Please check the following note first:
1853096 - Availability Metric: ABAP Message Server Status
The reason seems to be the following: you have assigned in "setup Monitoring" the template delivered from "SAP ABAP CENTRAL SERVICES" to the real Central Service Instance: DGW~ABAP~Central Service Instance
and additionally to the Managed Object: DGW~ABAP~vwmdasapgw_DGW_10
but this is not your central instance! (see attached screen)
Well, you have now to remove the template "SAP ABAP CENTRAL SERVICES" from DGW~ABAP~vwmdasapgw_DGW_10 and re-do the Setup for managed object.
To remove the template:
- Select Managed Object "XXX~ABAP~XXXXXXXXXXXXXXXXXXXXXX" and click on
"Restore Defaults" save it
Assign the correct Template to the managed object as per you choice.
Thanks
Vikram
Hi,
I need to do a presentation about Job Scheduling Management, but I am not finding
good materials.
Please, can you help me with some links about JSM, something that describe detailedly and completly about this subject.
Thank you.
Yes, To reactivate the service (webdynpro) although you see it active by SICF transaction.
Now it works properly again!!
Regards
Hi PK,
Like everybody mentioned here already it is not possible to migrate old tickets
the best option would be to do system copy if you are migrating to new hardware and then perform the complete Upgrade using SUM etc
further, create new transaction type as per process in this system
you can check my blog as well for some common errors and issues during upgrade
Upgrade Roadmap - Solution Manager 7.0 to 7.1 with Service Desk/ChaRM
Thanks
Prakhar
Hi Monique,
Did you get the problem fixed? I have solman7.1 SPS08, for ALL managed systems, i have the same problem as follows.
All other Metrics of Oracle Tablespace are Green, except these two in Gray, implemented the note 1807168 to both Solman and managed system, but did not fix the problem.
Could someone share with me how to fix the gray issue?
oracle release: 11.2.0.3.0
Thanks.
Asif,
to your first answer: no, because I can't remember all the 1,000 steps 
, sorry.
The second answer is also no, because it is a Z-Transaction (or in my case it is an Y) type and whereever it is possible, the methods of the super classes are called
After upgrading new Solution Manager 7.1 to SP11 (via SUM) I have problems with
all web-based transactions such as solman_setup, soamanager.
HTTP ports Ok in general (nwa on 50000, 8000 ports can be reached).
- I get HTTP 500 error in brouser after calling web-based tr.
In SICF all services are ON. If make test appropriate services I get
500 SAP Internal Server Error
ERROR: Syntax error in program CL_WDR_CLIENT_SSR_LS==========CP . (termination: RABAX_u'oATE)
- I get dumps in st22 after web-based tr. starts (SYNTAX_ERROR in "CL_WDR_CLIENT_SSR_LS==========CP ". Text below)
- There are a lotof dumps SYNTAX_ERROR in CL_SISE_MNG_RFC_STATUS_HANDLERCP - text below
Could you give me advise??? (Info from WP log added)
- Besides i see several SNotes in "Incompletely implemented" status:
1815196
1821727
1850983
1861585
1879253
1882914
1888783
1890903
1894598
1899812
1902251
1903942
1906936
1906937
1909714
1912693
1914046
1935934
1970628
1972789
1981760
--------------------dump 1----------------------------------------
Category ABAP Programming Error
Runtime Errors SYNTAX_ERROR
ABAP Program CL_WDR_CLIENT_SSR_LS==========
Application Component BC-WD-ABA-REN
Short text
Syntax error in program "CL_WDR_CLIENT_SSR_LS==========CP ".
What happened?
Error in the ABAP Application Program
The current ABAP program "CL_WDR_CLIENT_ABSTRACT_HTTP===CP" had to be
terminated because it has come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program
"CL_WDR_CLIENT_SSR_LS==========CP " in include
"CLUR_NW7_FACTORY==============CU " in
line 892:
...unknown field "INPUTFIELDTEXTSTYLE_ENUM".
The include has been created and last changed by:
Created by: "SAP "
Last changed by: "SAP "
Error in the ABAP Application Program
The current ABAP program "CL_WDR_CLIENT_ABSTRACT_HTTP===CP" had to be
terminated because it has
come across a statement that unfortunately cannot be executed.
Server-Side Connection Information
Information on Caller of "HTTP" Connection:
Plug-in Type.......... "HTTP"
Caller IP............. "#########"
Caller Port........... 8000
Universal Resource ID. "/sap/bc/webdynpro/sap/wd_sise_main_app"
Program............. "CL_WDR_CLIENT_ABSTRACT_HTTP===CP"
Screen.............. "SAPMHTTP 0010"
Screen Line......... 2
Information on Caller ofr "HTTP" Connection:
Plug-in Type.......... "HTTP"
Caller IP............. "############"
Caller Port........... 8000
Universal Resource Id. "/sap/bc/webdynpro/sap/wd_sise_main_app"
Information on where terminated
Termination occurred in the ABAP program "CL_WDR_CLIENT_ABSTRACT_HTTP===CP" -
in "CLIENT_INSPECTOR_CREATE_CLIENT".
The main program was "SAPMHTTP ".
In the source code you have the termination point in line 19
of the (Include) program "CL_WDR_CLIENT_ABSTRACT_HTTP===CM01C".
Source Code Extract
Line SourceCde
1 method client_inspector_create_client.
2
3 data:
4 name type string,
5 user_agent type string.
6
7 cl_wdr_client_abstract_http=>m_appl_props_tmp = get_appl_props( rr_application = applicati
8
9 name = wdr_task=>client_window->framework_parameters->client_name_key.
10 translate name to lower case.
11
12 user_agent = wdr_task=>request->get_header_field( if_http_header_fields=>user_agent ).
13 if user_agent cs 'SAP-NW' and name is initial.
14 name = 'smartclient'.
15 endif.
16
17 case name.
18 when '' or 'ssrclient' or 'htmlclient'.
>>>>> CREATE OBJECT client type ('CL_WDR_CLIENT_SSR_LS')
20 EXPORTING
21 client_info_object = client_info_object.
22 when 'smartclient' or 'smartclient-new' or 'smartclient-old'. " new smart client imp
23 if cl_wdr_client_abstract_http=>m_appl_props_tmp-enable_xbcml_client = abap_true.
24 CREATE OBJECT client type ('CL_WDR_CLIENT_SMART_NEW')
25 EXPORTING
26 client_info_object = client_info_object
27 application_info = application.
28 else.
29 message e026(webdynpro_rt) with name.
30 endif.
31 when others.
32 message e018(webdynpro_rt) with name.
33 endcase.
34
35 data: client_fulfills type abap_bool.
36 client_fulfills = client->if_wdr_client~fulfills( ).
37
38 if client_fulfills = abap_false or client_fulfills = '-' and application->get_property( if
------------------ from WP log ------------------------
Sun Apr 13 19:30:09 2014
*GENER* request remote generation: CL_WDR_CLIENT_SSR_LS==========CP.
Sun Apr 13 19:30:11 2014
*** ERROR => Syntax error in program CL_WDR_CLIENT_SSR_LS==========CP [abgen.c 1828]
{root-id=0050568147F11ED3B0E40FE685FAC4C2}_{conn-id=0050568147F11ED3B0E40FE6846364C2}_1
*** ERROR => > Include CLUR_NW7_FACTORY==============CU line 892 [abgen.c 1830]
{root-id=0050568147F11ED3B0E40FE685FAC4C2}_{conn-id=0050568147F11ED3B0E40FE6846364C2}_1
*** ERROR => > Неизвестное поле "INPUTFIELDTEXTSTYLE_ENUM". Но существуют следующие поля с подо [abgen.c 1832]
{root-id=0050568147F11ED3B0E40FE685FAC4C2}_{conn-id=0050568147F11ED3B0E40FE6846364C2}_1
*** ERROR => > бными именами: "INPUTFIELDTYPE_ENUM", "INPUTFIELDFIELDHELP_ENUM" и "INPUTFIELDSI [abgen.c 1834]
{root-id=0050568147F11ED3B0E40FE685FAC4C2}_{conn-id=0050568147F11ED3B0E40FE6846364C2}_1
*** ERROR => > ZE_ENUM". [abgen.c 1836]
{root-id=0050568147F11ED3B0E40FE685FAC4C2}_{conn-id=0050568147F11ED3B0E40FE6846364C2}_1
TH VERBOSE LEVEL FULL
** RABAX: level LEV_RX_PXA_RELEASE_MTX entered.
** RABAX: level LEV_RX_PXA_RELEASE_MTX completed.
** RABAX: level LEV_RX_COVERAGE_ANALYSER entered.
** RABAX: level LEV_RX_COVERAGE_ANALYSER completed.
** RABAX: level LEV_RX_HOTSPOT_TRACE entered.
** RABAX: level LEV_RX_HOTSPOT_TRACE completed.
** RABAX: level LEV_RX_SAVE_SHMLOCKS entered.
** RABAX: level LEV_RX_SAVE_SHMLOCKS completed.
** RABAX: level LEV_RX_RESET_SHMLOCKS entered.
** RABAX: level LEV_RX_RESET_SHMLOCKS completed.
** RABAX: level LEV_RX_ROLLBACK entered.
** RABAX: level LEV_RX_ROLLBACK completed.
** RABAX: level LEV_RX_DB_ALIVE entered.
** RABAX: level LEV_RX_DB_ALIVE completed.
** RABAX: level LEV_RX_HOOKS entered.
*** ERROR => SemRel: Inv. Operation. Units 1. Key=51 [semux.c 1393]
I {root-id=#######}_{conn-id=0050568147F11ED3B0E40FE6846364C2}_1
A ** RABAX: level LEV_RX_HOOKS completed.
A ** RABAX: level LEV_RX_STANDARD entered.
A ** RABAX: level LEV_RX_STANDARD completed.
A ** RABAX: level LEV_RX_STOR_VALUES entered.
A ** RABAX: level LEV_RX_STOR_VALUES completed.
A ** RABAX: level LEV_RX_C_STACK entered.
-------------------dump 2------------------------------
Category ABAP Programming Error
Runtime Errors SYNTAX_ERROR
ABAP Program CL_SISE_MNG_RFC_STATUS_HANDLERCP
Application Component SV-SMG-INS-CFG
Short text
Syntax error in program "CL_SISE_MNG_RFC_STATUS_HANDLERCP ".
hat happened?
Error in the ABAP Application Program
The current ABAP program "CL_DIAGLS_STATUS_MANAGER======CP" had to be
terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program
"CL_SISE_MNG_RFC_STATUS_HANDLERCP " in include
"CL_SISE_MNG_RFC_STATUS_HANDLERCM003 " in
line 56:
Formal paramet "HAS_BACK_OK" does not exist
" "
" "
" "
The include has been created and last changed by:
Created by: "SAP "
Last changed by: !!! ME !!!!!
Error in the ABAP Application Program
The current ABAP program "CL_DIAGLS_STATUS_MANAGER======CP" had to be
terminated because it has
come across a statement that unfortunately cannot be executed.
Information on where terminated
Termination occurred in the ABAP program "CL_DIAGLS_STATUS_MANAGER======CP" -
in "CLASS_CONSTRUCTOR".
The main program was "SAPMSSY1 ".
In the source code you have the termination point in line 28
of the (Include) program "CL_DIAGLS_STATUS_MANAGER======CM001".
Source Code Extract
Line SourceCde
1 method class_constructor.
2 data:
3 lr_de_physical_host type ref to cl_diagls_de_host_status_hndlr,
4 lr_de_database type ref to cl_diagls_de_db_status_hndlr,
5 lr_tech_syst_def type ref to cl_diagls_tech_syst_definition,
6 lr_robomate_rfc_gen_status type ref to cl_sise_mng_rfc_status_handler,
7 lr_robomate_diag_conf_status type ref to cl_sise_mng_diag_statushandler,
8 lr_robomate_plugin_status type ref to cl_sise_mng_plugin_statushandl,
9 lr_robomate_def_changed_status type ref to cl_sise_mng_def_changed_status,
10 lr_ccdb_status type ref to cl_diagst_ts_store_status,
11 lr_selfcheck_status type ref to cl_diagls_selfcheck_status,
12 lr_logviewer_status type ref to cl_diagst_ts_logviewer_status,
13 lr_bi_reporting_status type ref to cl_e2erep_ts_status_handler,
14 lr_monitoring_status type ref to cl_mai_rep_mo_status_handler,
15 lr_template_status type ref to cl_mai_rep_template_status,
16 lr_tech_managed_status type ref to CL_SISE_MNG_DEF_CHANGED_STATUS.
17
18 " REGISTER THE CHECKS HERE
19 " LANDSCAPE =================================================
20 create object lr_de_physical_host.
21 append lr_de_physical_host to mt_status_handlers.
22
23 " LANDSCAPE =================================================
24 create object lr_tech_syst_def.
25 append lr_tech_syst_def to mt_status_handlers.
26
27 " ROBOMATE: RFC GENERATED =================================================
>>>>> create object lr_robomate_rfc_gen_status.
29 append lr_robomate_rfc_gen_status to mt_status_handlers.
30
31 " ROBOMATE: DIAGNOSTICS CONFIGURED =================================================
32 create object lr_robomate_diag_conf_status.
33 append lr_robomate_diag_conf_status to mt_status_handlers.
34
35 " ROBOMATE: PLUGIN STATUS (ST PI & ST A/PI) ============================================
36 create object lr_robomate_plugin_status.
37 append lr_robomate_plugin_status to mt_status_handlers.
38
39 " Database =================================================
40 create object lr_de_database.
41 append lr_de_database to mt_status_handlers.
42
43 " SelfCheck status =================================================
44 create object lr_selfcheck_status.
45 " This status has
46 " append lr_selfcheck_status to mt_status_handlers.
------------------------form WP log --------------------------------------------
A Sun Apr 13 19:44:10 2014
A *GENER* request remote generation: CL_SISE_MNG_RFC_STATUS_HANDLERCP.
A *** ERROR => Syntax error in program CL_SISE_MNG_RFC_STATUS_HANDLERCP [abgen.c 1828]
A {root-id=744CD8DDC32211E390060000001904E2}_{conn-id=28365B90C29A11E388B2C4420A147023}_1
A *** ERROR => > Include CL_SISE_MNG_RFC_STATUS_HANDLERCM003 line 56 [abgen.c 1830]
A {root-id=744CD8DDC32211E390060000001904E2}_{conn-id=28365B90C29A11E388B2C4420A147023}_1
A *** ERROR => > Формальный параметр "HAS_BACK_OK" не существует [abgen.c 1832]
A {root-id=744CD8DDC32211E390060000001904E2}_{conn-id=28365B90C29A11E388B2C4420A147023}_1
A TH VERBOSE LEVEL FULL
A ** RABAX: level LEV_RX_PXA_RELEASE_MTX entered.
A ** RABAX: level LEV_RX_PXA_RELEASE_MTX completed.
A ** RABAX: level LEV_RX_COVERAGE_ANALYSER entered.
A ** RABAX: level LEV_RX_COVERAGE_ANALYSER completed.
A ** RABAX: level LEV_RX_HOTSPOT_TRACE entered.
A ** RABAX: level LEV_RX_HOTSPOT_TRACE completed.
A ** RABAX: level LEV_RX_SAVE_SHMLOCKS entered.
A ** RABAX: level LEV_RX_SAVE_SHMLOCKS completed.
A ** RABAX: level LEV_RX_RESET_SHMLOCKS entered.
A ** RABAX: level LEV_RX_RESET_SHMLOCKS completed.
A ** RABAX: level LEV_RX_ROLLBACK entered.
A ** RABAX: level LEV_RX_ROLLBACK completed.
A ** RABAX: level LEV_RX_DB_ALIVE entered.
A ** RABAX: level LEV_RX_DB_ALIVE completed.
A ** RABAX: level LEV_RX_HOOKS entered.
I *** ERROR => SemRel: Inv. Operation. Units 1. Key=51 [semux.c 1393]
I {root-id=744CD8DDC32211E390060000001904E2}_{conn-id=28365B90C29A11E388B2C4420A147023}_1
A ** RABAX: level LEV_RX_HOOKS completed.
A ** RABAX: level LEV_RX_STANDARD entered.
A ** RABAX: level LEV_RX_STANDARD completed.
A ** RABAX: level LEV_RX_STOR_VALUES entered.
A ** RABAX: level LEV_RX_STOR_VALUES completed.
A ** RABAX: level LEV_RX_C_STACK entered.
Hi,
Please check the below notes
1846481 - Syntax error in program CL_WDR_CLIENT_SSR_LS==========CP
Rg,
Karthik
Hi All,
Could any one please help in knowing and resolving below issue?
There is a CR, for which only "rejected", "cancelled", and "recheck request for change" is getting displayed under Actions tab, and so we are not able to confirm the CR. While the related CD has already been confirmed. Strange thing seen is in approval assignment block the steps are not showing as approved.
But, as a normal behaviour, a CD is only created under a CR, when all the approval steps have been approved by responsible persons.
Please let me know what all are the possibilities, and where we can check for this kind.
Thanks.
Regards,
Nidhi
Hi Nidhi,
typically the Recheck request for change will only appear in the ticket or RfC if there are errors
Kindly do or perform the recheck action and let us know further.
Past the screenshot so we can help easily
Thanks
Prakhar
Thanks Prakhar for your reply.
I have already tried with performing recheck request for change, still only same 3 options are coming under Actions tab i.e. cancelled, rejected, recheck request for change.
Thanks.
Regards,
Nidhi
Hi Nidhi,
Can you past the screenshot or transaction log etc for the incident.
Regards
Prakhar