RAISE tl_task_group_not_lock. ENDIF. """""""""""""""""$"$\SE:(1) Class CL_AI_CRM_ACTION_UTILITY, Method REASSIGN_CHANGE, End A *$*$-Start: (1)---------------------------------------------------------------------------------$*$*
ENHANCEMENT 1 Zabc_CHARM_MESSAGE_LOG. "active version ******************************************************************************* * Created: 11/13/2015 Robyn Osby * Usage : When Changing project assignment, the original Change Request that * contained the approval is not logged on the reassigned Change Document. * Write the source CR to the textbox log in the CD. * Note : If needed in testing, this logic will read new and existing ChaRM texts: * data lt_texts type COMT_TEXT_TEXTDATA_T. * clear lt_texts. refresh lt_texts. * CALL FUNCTION 'CRM_DNO_READ_ORDER_TEXT' * EXPORTING * iv_header_guid = mv_crm_doc_guid * IMPORTING * et_alltexts = lt_texts. * ******************************************************************************** data: ls_PROCESS_type TYPE CRMT_PROCESS_TYPE_DB. data: lt_docflow TYPE Zabc_CHARM_DOC_FLOW_TAB, ls_docflow type Zabc_CHARM_DOC_FLOW. data: ls_APP_MESSAGE type BALMI. data: lt_text3 type CRMT_TEXT_COMT, ls_text3 type CRMT_TEXT_COM, ls_lines3 type line of COMT_TEXT_LINES_T, ls_field_names type CRMT_INPUT_FIELD_NAMES, lt_input_field TYPE CRMT_INPUT_FIELD_TAB, ls_input_field type CRMT_INPUT_FIELD.
data: lt_objects_to_save TYPE CRMT_OBJECT_GUID_TAB, ls_objects_to_save TYPE CRMT_OBJECT_GUID, lt_saved_objects TYPE CRMT_RETURN_OBJECTS, lt_objects_not_saved TYPE CRMT_OBJECT_GUID_TAB, gt_nocheck_before_save TYPE CRMT_OBJECT_GUID_TAB.
constants: lc_object TYPE COMT_TEXT_TEXTOBJECT value 'CRM_ORDERH', lc_tdid type TDID value 'CD03', "general note textbox lc_RFC type CRMT_PROCESS_TYPE_DB value 'ZMCR'. *------------------------------------------------------------------------------* 1) Process only for CDs SELECT SINGLE PROCESS_TYPE INTO ls_PROCESS_TYPE FROM crmd_orderadm_h WHERE guid = mv_crm_doc_guid. if sy-subrc = 0. case ls_PROCESS_TYPE. when 'ZMAD' or 'ZMMJ' or 'ZMMI' or 'ZMTM'. "CDs that can reassign project?
* 2) Read Change Request number that created this Change document. * If first project reassignment, the Change Request will be in the document * flow. Read that CR #. CR # will not be found if it after 1st reassignment. CALL METHOD Zabc_CHARM=>READ_DOC_FLOW EXPORTING PI_GUID = mv_crm_doc_guid PI_PROCESS_TYPE = ls_PROCESS_TYPE IMPORTING PO_DOCFLOW = lt_docflow.
sort LT_DOCFLOW by process_type. read table LT_DOCFLOW into ls_docflow with key process_type = lc_RFC binary search. if sy-subrc = 0. "RfC found?
* 3) Populate message ls_APP_MESSAGE-MSGTY = 'I'. ls_APP_MESSAGE-MSGID = 'ZCHARM'. ls_APP_MESSAGE-MSGNO = '027'. "Original Change Request &1 contains approvals. ls_APP_MESSAGE-MSGV1 = ls_docflow-Object_ID. clear: ls_APP_MESSAGE-MSGV2, ls_APP_MESSAGE-MSGV3, ls_APP_MESSAGE-MSGV4.
* 4) Store message for screen dialog (top of ChaRM) append ls_APP_MESSAGE to et_APP_MESSAGE.
* 5) Update textbox with message so it is retained on save clear: ls_text3, lt_text3, ls_field_names. refresh: lt_text3. ls_text3-REF_GUID = mv_crm_doc_guid. "charm guid ls_text3-REF_KIND = 'A'. ls_text3-TEXT_OBJECT = lc_object. ls_text3-TDID = lc_tdid. ls_text3-TDSPRAS = 'E'. ls_text3-MODE = 'A'. "text creation ls_lines3-TDFORMAT = '*'. message id ls_APP_MESSAGE-MSGID type ls_APP_MESSAGE-MSGTY number ls_APP_MESSAGE-MSGNO inTO ls_lines3-TDLINE with ls_APP_MESSAGE-MSGV1 ls_APP_MESSAGE-MSGV2 ls_APP_MESSAGE-MSGV3 ls_APP_MESSAGE-MSGV4. append ls_lines3 to ls_text3-lines. append ls_text3 to lt_text3.
clear ls_input_field. ls_input_field-REF_GUID = mv_crm_doc_guid. "charm guid ls_input_field-REF_KIND = 'A'. ls_input_field-OBJECTNAME = 'TEXTS'. concatenate lc_tdid 'E' into ls_input_field-LOGICAL_KEY. ls_field_names-FIELDNAME = 'LINES'. append ls_field_names to ls_input_field-FIELD_NAMES. append ls_input_field to lt_input_field.
* 5a) Update textbox CALL FUNCTION 'CRM_ORDER_MAINTAIN' EXPORTING it_text = lt_text3 CHANGING ct_input_fields = lt_input_field EXCEPTIONS OTHERS = 99.
IF sy-subrc IS INITIAL.
* 5b) Save ChaRM with new textbox ls_objects_to_save = mv_crm_doc_guid. "charm guid append ls_objects_to_save to lt_objects_to_save. append ls_objects_to_save to gt_nocheck_before_save.
CALL FUNCTION 'CRM_ORDER_SAVE' EXPORTING it_objects_to_save = lt_objects_to_save * iv_update_task_local = true IMPORTING et_saved_objects = lt_saved_objects et_objects_not_saved = lt_objects_not_saved CHANGING ct_nocheck_before_save = gt_nocheck_before_save EXCEPTIONS OTHERS = 0.
COMMIT WORK. endif.
endif. "RfC found?
when others.
endcase. endif.
ENDENHANCEMENT. *$*$-End: (1)---------------------------------------------------------------------------------$*$*
ENDMETHOD. "create_request
Class Zabc_CHARM method READ_DOC FLOW Class Zabc_CHARM method READ_DOC_FLOW is used for other doc flow logic in other areas so it has extra logic. It contains: method READ_DOC_FLOW. ********************************************************************************* * Created: 9/30/2015 Robyn Osby * Usage : Read the preceding and following ChaRM documents within the document flow. ********************************************************************************* data: ls_DOCFLOW type zabc_charm_doc_flow. data: zz_ls_prior_doc_guid type CRMT_OBJECT_GUID, zz_ls_next_doc_guid type CRMT_OBJECT_GUID. data: zz_lz_guid type CRMT_OBJECT_GUID, "next doc's guid zz_l_guid TYPE CRMT_OBJECT_GUID_TAB. data: zz_lz_doc_flow TYPE line of cRMT_DOC_FLOW_WRKT, zz_lz_doc_flow_db type line of CRMT_DOC_FLOW_DB_WRKT. data: zz_iz_doc_flow TYPE cRMT_DOC_FLOW_WRKT, zz_li_DOC_FLOW_DB_WRKT type CRMT_DOC_FLOW_DB_WRKT. DATA: zz_LI_REQTD_OBJS TYPE CRMT_OBJECT_NAME_TAB. data: zz_lz_orderadm_h_wrk TYPE CRMT_ORDERADM_H_WRK, zz_lz_process_type TYPE CRMT_PROCESS_TYPE, zz_l_doc_linked TYPE CRMT_OBJECT_ID, zz_lz_object_type TYPE SWO_OBJTYP. DATA: zz_L_CV_LOG_HANDLE TYPE BALLOGHNDL. *-------------------------------------------------------------------------------------* 1) Read the document flow CLEAR: zz_LI_REQTD_OBJS, zz_L_GUID, zz_iz_doc_flow, zz_lS_prior_doc_guid, zz_lS_next_doc_guid. REFRESH: zz_LI_REQTD_OBJS, ZZ_L_GUID, zz_iz_doc_flow. APPEND 'DOC_FLOW' TO zz_LI_REQTD_OBJS. APPEND pi_guid TO zz_L_GUID. CALL FUNCTION 'CRM_ORDER_READ_OW' EXPORTING IT_HEADER_GUID = zz_L_GUID IT_REQUESTED_OBJECTS = zz_LI_REQTD_OBJS IMPORTING ET_DOC_FLOW = zz_iz_doc_flow CHANGING CV_LOG_HANDLE = zz_L_CV_LOG_HANDLE EXCEPTIONS DOCUMENT_NOT_FOUND = 1 ERROR_OCCURRED = 2 DOCUMENT_LOCKED = 3 NO_CHANGE_AUTHORITY = 4 NO_DISPLAY_AUTHORITY = 5 NO_CHANGE_ALLOWED = 6 OTHERS = 7. IF SY-SUBRC <> 0. ENDIF. * 2) Read preceding document (e.g. CR for CDs documents reported). loop at zz_iz_doc_flow into zz_lz_doc_flow. zz_Lz_GUID = zz_lz_doc_flow-OBJKEY_a. "for PRECEDING docs CALL FUNCTION 'CRM_ORDERADM_H_READ_OW' EXPORTING iv_orderadm_h_guid = zz_Lz_GUID IMPORTING es_orderadm_h_wrk = zz_lz_orderadm_h_wrk ev_process_type = zz_lz_process_type ev_object_id = zz_l_doc_linked ev_object_type = zz_lz_object_type EXCEPTIONS admin_header_not_found = 1 OTHERS = 2. if sy-subrc = 0. ls_DOCFLOW-process_type = zz_lz_orderadm_h_wrk-process_type. ls_DOCFLOW-OBJECT_ID = zz_l_doc_linked. ls_DOCFLOW-guid = zz_ls_next_doc_guid = zz_Lz_GUID. append ls_DOCFLOW to PO_DOCFLOW. endif. * 3) Read FOLLOWING documents zz_Lz_GUID = zz_lz_doc_flow-OBJKEY_B. "for FOLLOWING doc CALL FUNCTION 'CRM_ORDERADM_H_READ_OW' EXPORTING iv_orderadm_h_guid = zz_Lz_GUID IMPORTING es_orderadm_h_wrk = zz_lz_orderadm_h_wrk ev_process_type = zz_lz_process_type ev_object_id = zz_l_doc_linked ev_object_type = zz_lz_object_type EXCEPTIONS admin_header_not_found = 1 OTHERS = 2. if sy-subrc = 0. case pi_PROCESS_TYPE. "doc currently being processed when 'SDCR' or 'ZMCR'. "7.0 and 7.1 CRs? Then find CDs linked ls_DOCFLOW-process_type = zz_lz_orderadm_h_wrk-process_type. ls_DOCFLOW-OBJECT_ID = zz_l_doc_linked. ls_DOCFLOW-guid = zz_ls_next_doc_guid = zz_Lz_GUID. append ls_DOCFLOW to PO_DOCFLOW. when others. "currently on a CD? ls_DOCFLOW-process_type = zz_lz_orderadm_h_wrk-process_type. ls_DOCFLOW-OBJECT_ID = zz_l_doc_linked. ls_DOCFLOW-guid = zz_ls_next_doc_guid = zz_Lz_GUID. append ls_DOCFLOW to PO_DOCFLOW. endcase. endif. endloop. * 4) Compress and filter out current ChaRM delete PO_DOCFLOW where process_type = pi_process_type. sort PO_DOCFLOW by guid. delete adjacent duplicates from PO_DOCFLOW. endmethod.
Results The standard messages are still displayed at the top of the UI. The Related Request for Change field is still cleared (when more than CD is linked to the source RfC).
But now, the messages at the top of the UI and the Text log (under General Note) now contain the RfC that contains the approvals... 20160303M7.jpg
Hopefully, SolMan will contain this enhancement as a standard in a upcoming release. Until then, I hope my solution will be of help to your project!
Cheers!
03/12/16--10:03: Solution Manager 7.2 - Fasten your seatbelts.
0
0
Having now experienced a bit of Solution Manager 7.2 for real, I'd like to share a few initial thoughts. It goes without saying this is a big improvement on the earlier 7.1 in terms of three key areas that really need to be integrated: documentation of existing processes, process modelling new features, and change control from one to the other. I'm hopeful this is an inflexion point on Solution Manager demand, as the integrated approach is a much more compelling story than piece-meal adoption of tools. There are many things that seem deserving of mention, I'd just like to explore two of them for now. The Branch Concept Solution Manager 7.2 introduces a branch concept for storing documentation (and through integration, process monitoring and change control between them). Starting with a single and solitary Solution, there is always a Production branch (locked), and child "Maintenance" branch (unlocked). New, changed and deleted changes can be released into the production branch. If other branches exist off the Production branch, such as parallel developments, or other innovation and upgrade projects, these too will recieved the released changes. If there is a difference between branches, then the conflict has to be resolved resolved before the changes can be released. If ChaRM is integrated, then changes can't be made until a change request is approved and change request assigned. Branches.png
When trying to understand the behviour of elements in the branches, I think it is a mistake to think of them as directories in the conventional sense, with copies moving up and along the branches. In reality, each branch is a different view of the one Knowledge Warehouse document repository in which the mulitiple physical versions of a named logical artefact are stored. Changing an artefact in one branch changes the physical (hidden) version but the logical (displayed) identifier remans the same, and connects them together. While the Production branch is paired with the production environments, the maintenance branch is for all sub-production environments: development, QAS and Pre-production (if it exists). Therfore the branch concept does not reflect the managed system landscape, but is a virtual representation for the PRD / DEV Solution Manager landscape. Let me illustrate this point with a warning. If you are are to upgrade an existing 7.1 system you have to think carefully about planning it. Many customers would perhaps start with Development. That is not a problem per se, but the process documentation put into the system is not meant to transported to Production when it arrives, nor is it a viable option to perform a system copy of the development system. The process documentation and configuration is meant to be entered into the Production Solution Manager 7.2 system directly, at the level of the Maintainance or equivalent child branch to be relased when ready into the Production branch. The branch concept thus represents a virtual representation of SolMan Dev and Prd, all in the physical Production instance. The Process Level Seven - freedom at last? The much anticipated extension of the three process hierachy levels (Scenaro/Process/Step) to seven levels was interesting to explore. So how best can these seven levels be used? Let's start with the restrictions. In Solution Manager 7.1, a Solution could act as fourth level. It's use was never well defined, and originally was the only place were interfaces could be documented. In 7.2, Solutions are meant to exist uniquely, except perhaps for service providers with multiple customers where one customer is managed per Solution. Nevertheless a second Solution has proved useful as it appears that Best Practices can only be downloaded once per Solution. If there was a problem there appears to be no facility to delete and start again except with a new Solution (but this is only a provisional finding to report, there may be more to this). Another restriction is the sequence Scenario > Process > Step. No other levels are allowed between Scenario and Process or Process and Step. I would imagine this is kept for compatibility reasons, though in actuality Senario is merely another folder level with a dfferent icon. Processes must belong to scenarios and steps must belong directly to a Process. Steps are always the lowest level, there can be no futher sub-divisons. Further sub-processing is only catered for by the abstraction of an interface business process step, in which further levels used to document preceding and post interface steps are contained in the Interface Library. Finally, the very first level is occuppied with division between Business Processes and Libraries. Therefore there exists three levels in addition to Scenario > Process > Step to fit alongside, for example, the SAP standard process modelling hierarchy Figure 2_Field Service Process hierarchy model.png
Source: https://wiki.scn.sap.com/wiki/display/ModHandbook/Process+Hierarchy Model Hierarchy.PNG
I think the following comparisons can be made: 1. Process Model Level 6 (Activity, single actions to perfom a process step) corresponds to Solution Manger Assignments for a Process Step. 2. Process Model Level 4 (Process Variants) has no corresponding Solution Manager level. The recommended way is to either have one process per variant (as for Test Automation purposes) or handle the variants within the step, either by modelling every variation within the one BPMN diagram, of each variant as one seperate BPMN diagram assigned to the same process level. 3. Process Model Level 2 (Process Groups) could (should?) be represented at the Solution Manager Scenarios levels. For example, if the Process Model Level 1 is take to be 1.0 Purchase-to-Pay (or other E2E business area), each scenario is a grouping of processes along the way. For P2P this could be 1.1 Ordering, 1.2 Receipting, 1.3 Paying. There's obviously a lot more to say about Solution Manager 7.2 features, and this blog has really only touched on a couple of areas I've looked at in detail so far. Solution Manager 7.2 will keep everyone very busy and very happy for some time to come.
03/13/16--14:24: Solution Manager 7.2 - Installation and Configuration - IV - Managed System Config - General Info
0
0
Part 1: Solution Manager 7.2 - Installation and Configuration - I - Installations Part 2: Solution Manager 7.2 - Installation and Configuration - II - Configurations Part 3: Solution Manager 7.2 - Installation and Configuration - III - Changes from 7.1 to 7.2 Part 4: Solution Manager 7.2 - Installation and Configuration - IV - Managed System Config - General Info I want to give some general information about the related components for managed system configuration.
Let me start with the general architecture of Solution Manager, then list the components of the architecture and give some details and related links.
Technical Architecture of Solution Manager
Indeed, I searched many pages, presentations through internet but I could not find a figure that reflects my mind's figure for Solution Manager and Managed Systems. I tried to figure it out like below. SM72_Part4_Main.jpg
More detailed technical overviews can be seen in Technical Infrastructure link according to scenarios of the Solution Manager. The data flow, ports, users are defined in detail. There is also a pdf document about the infrastructure information (Technical Infrastructure) that you can download.
We have below components related to managed system configuration on Solution Manager and Managed Systems landscape; Solution Manager (ABAP + Java Instances) Managed System (ABAP, Java, Dual Stack, BOBJ, etc) Software Provisioning Manager (SWPM) SM Diagnostic Agent (SMD) SAP Host Agent (SAPHOSTAGENT) Introscope Enterprise Manager (IEM) Introscope Java Agent Support Tools (ST* Plugins) System Landscape Directory (SLD) Landscape Management Database (LMDB) Extractor Framework Solution Manager Busines Warehouse SAP Support Backbone
First three blogs were about the Solution Manager so I will not give details again here. The next blogs will be about the configurations of ABAP, Java, BOBJ, HANA etc managed systems so I will not mention about them here either.
Here are the short descriptions of the other components and some useful links about them.
Software Provisioning Manager (SWPM) Software Provisioning Manager offers relevant system provisioning procedures to install, copy, and transform SAP systems in your landscape. We use SWPM for installation of systems and especially SM Diagnostic Agents. SM72_Part4_SWPM.jpg
You can chek link Overview - Software Provisioning Manager 1.0 for detailed overview. You can download the tool itself, the Kernel for the tool the documentation from this link. Central Release Note for SL Toolset 1.0 is SAP Note 1563579. Help page for the tool is Software Logistics Toolset (SL Toolset) Demo for Software Provisioning Manager 1.0.
SM Diagnostic Agent (SMD) Normally SMD Agent is optionally installed when you are installing the SAP System. I recommend to install the latest version of the tool before carrying out the managed system config. So if it is installed with the SAP system together check whether it is the latest version. If it is not uninstall the existing one using SWPM firstly and then reinstall the latest version. SM72_Part4_SMD.jpg
Check the notes and wiki pages for the currnet information 1833501 - Diagnostics Agent - Installer Versions 1365123 - Installation of Diagnostics Agents Concerning Diagnostics Agents always pay attention to the 6 essential rules, as described in the attached "AgentInstallationStrategy.pdf" document. Note: Further details on recommended SAP Host Agent and SWPM versions, as well as existing Diagnostics Agent maintenance procedures are available in the SCN wiki: "Diagnostics Agent Maintenance Procedures.
SAP Host Agent (SAPHOSTAGENT) SAP Host Agent is installed automatically when you install an SAP system. You should keep this component also in the latest version. You can use auto upgrade feature of the component. Her is a figure of SAP Host Agent architecture. Saphostexec, saphostctrl services are the main programs for the component. SM72_Part4_SapHostAgent.jpg
Check the notes and wiki pages for detailed information Have Up-To-Date SAP Host Agents 1031096 - Installing Package SAPHOSTAGENT 1473974 - Using the SAP Host Agent Auto Upgrade Feature
Introscope Enterprise Manager (IEM) Introscope is an application management solution created to manage Java application performance. The Right to View (RTV) version of CA Introscope is a restricted, read-only form of the full product and is bundled with SAP Solution Manager.
The Enterprise Manager is typically installed on the Solution Manager host. Alternatively, you can install the Enterprise Manager on a separate host. You can find detailed information about the installation of Introscope Enterprise Manager in blog Part 2. SM72_Part4_IEM.jpg
Check the note and wiki page for detailed information 797147 - Introscope Installation for SAP Customers RCA_Introscope_Home
Introscope Java Agent (on managed systems) The setup of the Java agent is typically done centrally via the managed setup in Solution Manager. After activation by restarting the Java VM, the agent runs within the Java process of the monitored system.
Host-Level Introscope Agent (on the managed systems) The so-called Introscope Host Adapter runs as part of the Diagnostics Agent in the Diagnostics Agent process to collect data on operating system level, e.g., from saposcol, GC logs, ABAP instances, and TREX. The host adapter generates less load on the Enterprise Manager than a normal agent. Wiki for Introscope Host Adapter. SM72_Part4_Bytecode.jpg
Support Tools (ST-PI and ST-A/PI) We see these plug-ins on EWA reports as seen below. In order to have better service you should keep these plug-ins up to date on managed systems. SM72_Part4_Plugins.jpg
Solution Tools Plug-In ST-PI : This add-on or plug-in contains Service Data Control Center (SDCCN) that controls the data collection and transfer of analysed data for a service session. Service Tools for Applications Plug-In ST-A/PI: This plug-in contains application-specific data collectors providing data to SDCCN. It has also service preperation check RTCCTOOL feature.
Check the notes and help page for detailed information https://support.sap.com/supporttools 539977 - Release strategy for add-on ST-PI 69455 - Servicetools for Applications ST-A/PI (ST14, RTCCTOOL, ST12)
System Landscape Directory (SLD) The System Landscape Directory of SAP NetWeaver (SLD) serves as a central information repository for your system landscape. A system landscape consists of a number of hardware and software components that depend on each other with regard to installation, software updates, and demands on interfaces. SAP Systems inside a landscape report data automatically to the SLD. The figure below shows the flow of data between the SLD and other components.
SM72_Part4_SLD.jpg
As it can be seen above figure component information is provided by SAP. It is recommended that you always use the latest version of SAP CR Content. The note 669669 - Update of SAP System Component Repository in SLD can be used for details.
Check below help document, blogs, presentation and pdf document for detailed information System Landscape Directory (help.sap.com) System Landscape Directory (SLD) (blog) SCN blogs and docs on SLD and LMDB (blog) System Landscape Directory of SAP Netweaver by Boris Zarske (presentation) Planning Guide – System Landscape Directory (pdf document about the details, topologies etc. )
Landscape Management Database (LMDB) The Landscape Management Database (LMDB) is an index of the elements in a system landscape. LMDB uses the SAP enhancement of the Distributed Management Task Force (DMTF) Common Information Model (CIM) to describe the landscape elements, analogously to the System Landscape Directory (SLD). Typical model elements are „computers“, „systems“, „products“ and „software components“. LMDB was introduced in SAP Solution Manager 7.1, and is required since then. SM72_Part4_LMDB.jpg
Useful links about LMDB; Documentation for Landscape Management Database - LMDB (For a list of system landscape management documentation) Guidance to Best Practices in SLD and LMDB SLD-LMDB Topology – Connections, Valid, and Invalid Data Exchange Between SLD and LMDB of SAP Solution Manager Landscape Management Database (LMDB) Landscape Management Database (LMDB) – FAQ
Extractor Framework (EFWK) Below short overview of EFWK is taken from EFWK_Home --> EFWK_OVERVIEW. The picture below shows the high level architecture of the EFWK. SM72_Part4_EFWK.jpg
On the left side you find the different data sources for the extractors. Extractors don’t only run in Solution Manager, but also in the managed systems. Usually extractors are functions in function modules (mainly shipped with ST-PI and ST-A/PI for ABAP) or part of the aglets of the diagnostics agents.
There are links on mentioned wiki pages about Setup & Administration, How Tos, Troubleshooting, Frequently Asked Questions (FAQ) of EFWK.
Solution Manager Busines Warehouse E2E Monitoring and Alerting Infrastructure (MAI) data is put in the SAP Solution Manager BW by the Extractor Framework (EFWK), and in particular, the Alerting Framework. No process chains and DataSources are used, the data is written directly to DSOs by extractors. BI Content for SAP Solution Manager
Mostly BW data is kept in Solution Manager System but you can use external BW system for this purpose. When the mandatory configuration is done most of the BI structures are activated and infocubes, dsos, web templates are generated. There could be errors in extractors that are pointing to not generated BI objects. EWA reports for BOBJ, Java systems can also refer these kind of errors. SM72_Part4_BW.jpg
SAP Support Backbone Support Backbone integrates the SAP Solution Manager, the SAP Service Marketplace, and the SAP service infrastructure. Integration includes access to support processes and tools, which both SAP Support staff and SAP partners can access. You use wizards to set up service connections to SAP for the managed systems in your solution. You open a service connection for a specified period so that a member of SAP Support staff can log on to your system and provide support directly. Managed System Configuration of an ABAP, Java, BOBJ and HANA Systems are coming next.
Thanks for your interests.
03/18/16--03:12: SAP Solution Manager 7.2 ALM Best Practices
0
0
As of now SAP Solution Manager 7.2 Best Practices and IT Processes are ready for download to your SAP Solution Manager 7.2 system. The Best Practices will provide an excellent visualization of the IT processes running on SAP Solution Manager. The package comes with process definitions, process diagrams, process step, executable, and configurations for all relevant build processes. The content allows SAP Solution Manager 7.2 customers to visualize their ALM processes and model their process variants. This leads to time-efficient discussions with IT experts, shorter ALM implementations and by that to an increased efficiency of ALM engagement delivery. Process.png
The process diagrams have been modeled by ALM RIG EMEA in collaboration with SAP Solution Manager product management, development and regional CoE EMEA. Currently the package covers all Application Lifecycle Processes from Requirement to Deploy (R2D):
Modular Processes: Project & Requirements Management: 3 processes Process Management: 22 processes Test Management: 31 processes Change Control Management:: 7 processes IT Service Management: 22 processes
E2E Process: Urgent Correction
The content is stored on the One Content Platform and available for download like any other SAP Best Practices package, e.g. the S/4 HANA Best Practices. It will be continuously extended and the new Best Practice versions regularly rolled out. Upload.jpg
Stay tuned. Henrik
03/19/16--07:56: Job SM:EXEC SERVICES does not process the EWA session on a future date
0
0
Symptom I manually create an additional SAP EarlyWatch Alert session on a future day. QQ20160319-0.png
But I want to process the collected data (manually collect data in source system with now option) now, so click start service processing botton now. QQ20160319-0.png
The job SM:EXEC_SERVICES_.... for service processing finishes successfully and very quickly. However, after the completion of job, I still need to process service data (the same picture is shown above) and no EarlyWatch Alert report is generated. The job log for SM:EXEC_SERVICE_... 1.png
Compared with the normal processing log of EWA, the following part is missing:
Analysis The EWA session is scheduled on a future date, while the job SM:EXEC SERVICES does not process this session. 1997456 - Job SM:EXEC SERVICES does not process the EWA session on a future date
Solution Schedule a new EWA session for today, and re-generate a new report If a session is scheduled on a future date, this session will be processed by JOB SM:EXEC SERVICES scheduled on that day. (so you should be patient and wait...) Process the session manually in transaction RSA, for more detailed information, please refer to 1997456 - Job SM:EXEC SERVICES does not process the EWA session on a future date
03/23/16--15:00: Solution Manager 7.2 - Installation and Configuration - V - Managed System Config - ABAP System
0
0
Part 1: Solution Manager 7.2 - Installation and Configuration - I - Installations Part 2: Solution Manager 7.2 - Installation and Configuration - II - Configurations Part 3: Solution Manager 7.2 - Installation and Configuration - III - Changes from 7.1 to 7.2 Part 4: Solution Manager 7.2 - Installation and Configuration - IV - Managed System Config - General Info Part 5: Solution Manager 7.2 - Installation and Configuration - V - Managed System Config - ABAP System This blog is about the configuration of an ABAP managed system.
Before configuration if you perform below preperation steps it will be easy for you to perform the configuration.
Register your ABAP system to the SLD of your system landscape Solution Manager's SLD is usually used for keeping the systems landscape data. (Sometimes there could be PI system's SLD before Solution Manager System's one in the landscape. That time you can configure PI's SLD first and then you can synchronize systems' data to Solution Manager's SLD automatically usind SLD bridge.) Use RZ70 transaction to register your system to SLD. You need SLD system Hostname or IP and http Port number of SLD. SM72_Part5_RZ70.jpg
Synchronize LMDB from SLD After registering your system to SLD, LMDB synchronization jobs (SAP_LMDB_LDB_*) runs with 10 mins period value and your systems data is synchronized to LMDB
SM72_Part5_LMDB.jpg
Check SMD Agenton your ABAP System Host If there is no SMD agent on your system install the latest version with SWPM like described below.. If there is an SMD Agent installed on your system, check the version first and then update to the latest version if required.
Use below URL for Agent Administration application. http://:/smd/AgentAdmin
Check SAP Host Agent version on your system It must have been installed during system installation. Use 1031096 - Installing Package SAPHOSTAGENT for the installation or upgrade of the Host Agent. You can use below commands to find the version of SAP Host Agent. saphostexec -version saphostctrl -function ExecuteOperation -name versioninfo SM72_Part5_SHA.jpg
Download the latest Host Agent, Extract it and upgrade it using saphostexec -upgrade. SM72_Part5_SHA_2.jpg
Check ST-PI and ST-A/PI versions and Update if Required Check ST-PI and ST-A/PI versions of your plugins on your ABAP system and upgrade the versions. New installed ABAP system does not have ST-A/PI pulugin so you must download it and import to your system. The notes recommended in the picture gives detailed information and version compatibality of SAP_BASIS and ST* plugins. This picture is taken from an EWA report before managed system configuration you cannot get this Plug-In Statuses. But you should check the versions and upgrade them to the relevant latest SP version. SM72_Part5_STPlugins.jpg
* Installation of SMD Agent with SWPM Check the version of the diagnostics agent and kernel. Versions can be checked like the ones in below pictures. SAPDIAGNOSTICAGENT version: SM72_Part5_SMD_Version3.jpg
SMD Kernel Version: SM72_Part5_SMD_Version2.jpg
If there is an older version of SMD, uninstall it using SWPM. Install the SMD Agent using the latest SWPM and Kernel.
Download the latest DIAGNOSTICS AGENT from swdc as seen below screen. SM72_Part5_SMD_download.jpg
Download latest swpm and latest Kernel files for your platform from Software Logistics Toolset 1.0 page. And install SMD Agent using SWPM. The following screenshots are the detailed parameter summary of SWPM. SM72_Part5_SMD_SWPM1.jpg
SM72_Part5_SMD_SWPM2.jpg
As you can see in below picture the latest kernel package (SAPEXE* file), latest jvm patch and latest SAPDIAGNOSTICS AGENT is downloaded and declared in SWPM. SM72_Part5_SMD_SWPM3.jpg
And the final successful installation of SMD screen. SM72_Part5_SMD_SWPM4.jpg
* Managed System Configuration Steps After you registered your ABAP system to SLD, the data is replicated to LMDB you can start managed system configuration of the system using SOLMAN_SETUP on solution manager. Use Solman_admin user for the process. The start of configuration is done like below screen. There are detailed explanations for each step. SM72_Part5_MSConfig1.jpg
There are 10 tabs for completing the comfiguration. There will be a picture for each steps below.
1. Assing Product You can read the help text. By setting Diagnostic Relevance automatically we can set the status of the step green. The assigned prroduct can be seen on the left bottom corner. SM72_Part5_MSConfig3.jpg
2. Check Prerequisites You execute all automatic activities. If there is no problem you can press Next. As you see below there is a problem in this step. You check the activity logs and press Show button. There is details and SAP Note recommendations. SM72_Part5_MSConfig4.jpg
For the solution of the problem the Note "1419603 - Missing ABAP SAP Central Services (ASCS) instance in SLD/LMDB" adressed. You apply the note and check LMDB whether ASCS instance has come or not. It must be there. Then execute the activity again. The status will be green too.
3. Maintain RFCs In this step select the production client line then select create RFCs or appropriate choice from drop down list, check all checkboxes for the creation of RFCs and Execute. When RFCs are created status will be green. SM72_Part5_MSConfig6.jpg
SM72_Part5_MSConfig7.jpg
SM72_Part5_MSConfig8.jpg
4. Assign Diagnostics Agent When SMD Agent is installed on satellite host it is also registered to SLD. You can check SMD Agents using URL: http://:/smd/AgentAdmin SMD Agent is listed under Non-authenticated Agents tab. If the version is "INCOMPATIBLE VERSION" Update the Agent first. Then cliekc Trust Agents to put the agent to Connected Agents tab. If the host name of the agent is not coming and named as you can run below script on satellite host to bring the host name. X:\usr\sap\DAA\SMDA98\script>smdsetup.bat changeservername servername:"myhostname" SM72_Part5_MSConfig9.jpg
After above processes you can check the status of Assign Diagnostics Agent step. Check the version of the SMD.
5. Enter System Parameters You fill in the required fields for System Parameters as seen below. For setting up DBA Connection I chose SQL Authentication and created solmansetup user on SQL Server. (SQL Server must be configured for SQL Authentication type). Then by pressing the "Setup DBA Cockpit Connection " button it is made available.
You save the data to make the status of the step to green. SM72_Part5_MSConfig11.jpg
6. Enter Landscape Parameters Just check the values of the parameters and update if required and then save them to make the status green. You can select the checkboxes to make some checkes during save operation. SM72_Part5_MSConfig12.jpg
7. Maintain Users In this step you create or update dialog or technical users and assign roles to those users. SM72_Part5_MSConfig13.jpg
SM72_Part5_MSConfig14.jpg
8. Finalize Configuration There are automatic and manual activities that needs to be fulfilled in Final Configuration step. You can leave postponed activities as is. Fot manual activities got to each transactioon or URL to perform the activity. SM72_Part5_MSConfig15.jpg
9. Check Configuration In this step, you automatically check whether the system is configured correctly, and you update the statuses in the overview of the Managed Systems Configuration.
10. Complete This step provides an overview of the steps that have been performed in this scenario, including information about the users who made the changes, and the status of each step.
Managed System Configuration of a Java System is coming next.
Thanks for your interests.
03/24/16--01:04: External service desk coupling SAP Solution Manager 7.1 - OTRS
0
0
Many customers have a service desk in place which is used for all departments, throughout the company. That service desk often is not SAP Solution Manager. This means that in many cases, it can become interesting to connect the SAP world to that service desk. This translates into scenario's that leverage information from SAP systems or from SAP Solution Manager and then use the IT Service Management scenario in SAP Solution Manager to connect to the external (non-SAP) service desks in one way (shipping data out) or bi-directional (shipping data out and synchronizing in again or exchanging information in both ways).
A few examples:
Creating an incident (support message) from within a SAP application and sending it to an external service desk: From within a SAP transaction, an end-user can create a support message. This data would then be sent to SAP Solution Manager and SAP Solution Manager can sent it further to the service desk that is used beyond SAP. This could be with or without a middleware in between as displayed in below line examples:
Managed SAP system (ERP for example) -> SAP Solution Manager -> External Service Desk Managed SAP system (ERP for example) -> SAP Solution Manager -> Middleware (SAP PO for example) -> External Service Desk
This functionality is foreseen also in newer applications (Fiori applications) in the latest SAP ERP versions (S/4 HANA Digital Core) for example so it stays relevant towards the future as a scenario.
Creating an incident from within SAP Solution Manager (Technical Monitoring scenario for example) and sending it to an external service desk:
SAP Solution Manager -> External Service Desk SAP Solution Manager -> Middleware (SAP PO for example) -> External Service Desk These scenario's could also send data back so it could become bi-directional. Depending on which side is considered the "master" different options can be explored to make this possible. You could create an incident from within Technical Monitoring, then have someone handle the ticket in the external service desk and synchronize the status back to SAP Solution Manager so an operator who works inside SAP Solution Manager (who only works there for example, first line operation support) sees the status of the incident which is being handled in the external service desk.
Relevant SCN sources (external service desk coupling content):
SCN content Service Desk Implementation Guide Part II Activating ICT_SERVICE_DESK_API in 7.1
SAP notes 2234342 - Status change is not done over External Service Desk 1483276 - Use of Customizing Parameters in DNO_CUST04, AGS_WORK_CUSTOM, and ICT_CUSTOM 2281823 - HTTP 500 Internal Server Error occurrs when opening a Webservice via an external alias Whitepaper SAP Solution Manager 7.0 Service Desk WebService API http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e3eeb4a8-0b01-0010-bd99-f4a700a49d32?overridelayout=t… There isn't an awful lot of information available on SCN nor on SAP side on the standard WebService API that is delivered by SAP to make these kind of scenario's work. The whitepaper describes how the web services work and what is possible with which operation. A few good / interesting blog posts exist on SCN (although outdated) that provide additional information make it possible to get a better view on how the external service desk coupling is build up and functioning. I'm not going to discuss the basic setup or configuration of the external service desk coupling, this is already discussed in other blogs / threads. Instead I want to give some pointers which might help you when you have to set up a similar scenario. Debugging and tracing: As a consultant, don't underestimate the power of the ability to debug through code. It can be the difference between getting the implementation done or being stuck and having to wait on SAP support. You don't need to be a coder to "read" through code, check values of variables and get an understanding of what is happening in the system, figuring out why it's acting the way it is. To debug this scenario, I placed external breakpoints in the relevant class - methods on SAP Solution Manager side (for example CL_SOL_ICT_DNO_ORDER_API and CL_SOL_ICT_INTERNAL) when the external service desk (OTRS) would do a call to SAP Solution Manager. Little things, like filling in a value in an item on the webservice "addInfo" can have a big impact on what the system does with the information that is available in the request. In transaction SRT_UTIL I would filter and trace on the web service path to capture incoming requests so I can check what the external service desk system is sending to SAP Solution Manager. SOAPui can be used to perform requests to the different webservices and check what subtle differences might have as an effect. In the end, you will want to combine all these to get a good understanding of what happens in the system due to which reason. The same is often also needed on the other side (on the external service desk side) to get issues out and end up with a consistent scenario. It might not be easy but it can definitely be worthwhile to debug and trace on both sides.
Requester and provider role as described in the whitepaper:
ProcessFlow.png
One of the problems I bumped into, connecting SAP Solution Manager and OTRS (open source service desk) was that the requester and provider role got switched up in the calls. If you look at the whitepaper and the blog post part II it describes how only certain operations of the webservice are available depending on the state an incident is in (beginningstate, processingstate, etc) and the role a system has got you'll notice that when a ticket is new (in SAP Solution Manager) it's in "BeginningState" = BS and when you send it to the external service desk, using operation ProcessIncident() it goes into state "ProviderProcessing" = PP. Then you would think you can use other operations but since the calls inverted the requester and provider, we couldn't use it in that way and we only had "AddInfo()" and "CloseIncident()" to our disposal (see graphical representation above which differs from the flow depicted in the whitepaper because the roles didn't match the statements in the code). If you look at the whitepaper you'll see that normally you've got more options to your disposal (Accept, Reject, ...) and other intermediate states exist. When we performed calls in the system, we got the above result instead. We also wanted to get the scenario up and running avoiding code adjustments as much as possible, we ended up doing two minor adjustments in the end which makes it easier to maintain the solution afterwards. AddInfo operation doesn't update the status according to the whitepaper? The AddInfo() operation, in principal, doesn't update the user status according to the whitepaper. You can use customizing to set the "synchronization status" to a fixed user status value. However, it's possible to configure the system to copy the user status out of the AddInfo() request coming from OTRS to SolMan which then changes the code that is executed because in the coding if the UserStatus is initial, the operation specific coding is called. If the UserStatus isn't initial, a more generic piece of code is called to update the status thus making it possible to set any status, even when AddInfo() operation is called by OTRS (external service desk). External Service Desk - Alternative Value Mapping(1) makes it possible to copy the UserStatus from an inbound request. Customizing allows specific status to be set: SAP Solution Manager customizing (ICT_CUSTOM) allows to set a specific status through customizing (see SAP note 1483276) so, for example, when the incident gets sent to the external service desk, you can place a specific user status in the customizing so the incident automatically shifts to that user status. By customizing alone, we could set the following status flow up in SAP Solution Manager: New -> Sent to OTRS -> In Process -> Closed
Combining different options: When we then combine multiple options, it's possible to synchronize any status using AddInfo() and a decent mapping from the status value of the incident in the external service desk to SAP Solution Manager.
New -> Sent to OTRS -> In Process -> -> Closed
For example: New -> Sent to OTRS -> In Process -> Resolved -> Closed New -> Sent to OTRS -> In Process -> Forwarded -> Resolved -> Closed
Meanwhile on the OTRS side:
On the OTRS side, a package was implemented to have a OTRS connector to SolMan ITSM available and also a specific filtering was put in place to more easily filter on tickets that are coming from SolMan.
Similar tracing and debugging was done on OTRS side, a small piece of code was adjusted also because OTRS kept sending "open" state instead of the correct state back to SolMan (might be version dependant) so in the end, we had someone from OTRS operations team write an SQL statement to read the correct state from the relevant database table and pass the correct state to the mapping.
Result:
The scenario which was put in place, makes it possible for an operator to create an incident based on a technical monitoring incident in the Solution Manager "Technical Monitoring - Alert Inbox" workcenter. This incident is automatically sent to the external service desk (automated through CRM action profile) where it is processed further. The status of the external service desk is synchronized back to SAP Solution Manager so the operators can see the status of the incident. When the incident is closed in the external service desk, the incident is SAP Solution Manager is closed and the alert gets confirmed.
03/24/16--06:13: How to install a Diagnostics Agent with SWPM 1.0 SP10 (archive based installation)
0
0
This blog describes the new feature of installing Diagnostics Agents using Software Provisioning Manager 1.0 SP10 as part of SL Toolset 1.0 SPS 16. Instead of providing a complete kernel media dvd to the installer, you can now download just the relevant archives, and perform the installation with them. Installing a diagnotics agent in the past required a complete kernel media DVD. It was also recommended to exchange SAPJVM and SAPDIAGNOSTICSAGENT with the latest available versions. Starting with the new SWPM 1.0 SP10 (available since February 15th 2016) you can also download the specificly required installation archives for your SAP system installation instead of providing a complete SAP kernel media. You only need to download - apart from the Software Provisioning Manager 1.0 SP10 archive which is always required for an installation - the following archive files:
Required Archive Versions and Patch Levels if you want to install with an SWPM Kernel 721_EXT or 721 SWPM Kernel 721_EXT (SAPEXE.SAR) or alternatively SWPM Kernel 721 (SAPEXE.SAR) SAP Host Agent 721 (SAPHOSTAGENT.SAR) SAP JVM 6.1 (SAPJVM.SAR) Diagnostics Agent version 7.45.1 (SAPDIAGNOSTICSAGENT.SAR)
Required Archive Versions and Patch Levels if you want to install with an SAP Kernel 745 SAP Kernel 745 (SAPEXE.SAR) SAP Host Agent 721 (SAPHOSTAGENT.SAR) SAP JVM 6.1 (SAPJVM.SAR) Diagnostics Agent version 7.45.1 (SAPDIAGNOSTICSAGENT.SAR)
SWPM Archive Based Installation
SWPM: Selection screen
SWPM_1.png
SWPM: Define Parameters The checkbox "Provide the path to each archive seperately" has to be enabled SWPM_2.png
SWPM: Summary screen SWPM_3.png
Sources SAP Note 2253383 - Diagnostics Agent - SWPM Archive Based Installation SAP Note 1833501 - Diagnostics Agent - Installer Versions SAP Note 1858920 - Diagnostics Agent installation with SWPM SL Toolset 1.0 SPS 16: improved Software Logistics Tools
Information about our SAP ALM Consulting Services:https://support.sap.com/alm-consulting
03/30/16--07:12: SAP Activate integration with Solution Manager 7.2
0
0
The SAP Solution Manager 7.2 is designed to support the S/4HANA on premise implementation and the complete solution lifecycle. The SAP Solution Manager 7.2 is an environment with tools for project management, process modeling, change management, test management and much more to implement, to run and optimize your SAP software. You can import the SAP Activate Best Practices into the SAP Solution Manager 7.2: First SAP provides project best practices: You can load a project plan as a template for the SAP S/4HANA implementation. Project plan templates that describe the tasks according to SAP Activate. The templates are provided for different implementation scenarios. You can adjust the template to your need during the planning workshops. In those project management templates you can identify who needs to be involved in the project, when and what kind of skills are required (Resource Management). Following that, you can use it for working with changes which result from Fit/Gap analysis. Second SAP provides process best practices: This includes process models and configuration for SAP S/4HANA editions. You can use this for build design. The delta scoping and new requirements can be documented in the standard BPMN 2.0 in the modeling environment on the process or process step level. SAP Solution Manager 7.2 fulfils the requirements for process modeling, solution implementation and documentation – continues validation of your processes based on system usage. IT Project and Solution Branch from import.png
Finally, SAP provides capabilities to document and apply changes in a consistent and combine way across the multi-system landscape. Based on the process models you can setup, later on, the business process monitoring for elements of the process, process step or interfaces. Using SAP Solution Manager 7.2 in combination with SAP Best Practices for S/4HANA and configuration work in SAP S/4HANA system, you will be required to document only the changes to the standard solution (Model Company) and not to start from scratch. With the SAP Activate content import into SAP Solution Manager 7.2, you will get:
The project template plan into the IT project: The IT project describes the tasks and work which need to be done. This template can be edited and adjusted. The business process structure in the new business process model design: The SAP Activate business process model content should be imported in a non-production solution brunch to filter the processes in scope of the implementation. Libraries of objects: The SAP Best Practice content creates also Libraries of objects (e.g. executables / configuration objects) which you can use to create own processes on top of SAP delivered process. Accelerators and Building Blocks: With the process structure and object libraries, the best practice documentation e.g. configuration documentation or business process documentation will be imported as well. Process diagrams: Editable process models are part of the imported content. You can adjust the process diagrams or create new ones in a system-based or role-based representation to facilitate the interaction with your LoBs. Additionally, depending on the implementation scenario, further documentation e.g. test scripts or the integration best practices are provided with the imported content for SAP S/4HANA. Below you find a few screenshots, for your "look and feel", of the SAP Activate content which will be available in SAP Solution Manager 7.2. SAP Activate in SAP Solution Manager 7.2 – SAP Best Practice Content Upload: Import SAP Best Practice.png
SAP Activate in SAP Solution Manager 7.2 – Business Process Content Best Practice content.png
SAP Activate in SAP Solution Manager 7.2 – Accelerators and Building Blocks Acceleratos and Building Blocks.png
SAP Activate in SAP Solution Manager 7.2 – Process Diagrams Process Model.png
SAP Activate SAP Solution Manager 7.2 – IT Project Workbreak Structure PPM Project.png
SAP Activate in SAP Solution Manager 7.2 – IT Project Structure Tasks Project struture - tasks.png
SAP Activate in SAP Solution Manager 7.2 – IT Project Resource Planning Resource Planning.png
04/05/16--03:03: Quick Tip - Note Search help in SOLMAN_SETUP in Solution Manager 7.1 SP14
0
0
I hope all the administrator are now pretty much acquainted with Solman_setup transaction which is the main transaction for configuration or setup in Solution Manager 7.1 or 7.2 Many times during the configuration, we face error during a step or a sub-step. There is one good feature HIDDEN within this setup which is the SAP Note search. for e.g During the Managed System Configuration setup, we get some error in the step for Check Pre-requisites as below. Capture.jpg
Now let us say we know we are fine with pre-requisites but still the error persists so we need to search for SAP notes. In this case, click on the link Settings on the extreme right side. Capture.jpg
Bingo. We have found a field Note Search under Hidden Column. Move it to displayed columns by selecting it and using add button. Click OK button further. Capture.jpg
We will now notice or get a new column called as Note Search as shown below. Now we will also see the real advantage of adding it as there is an entry 'Search' next to an ERROR or WARNING message. Click on the 'Search' and below pop will be displayed. Capture.jpg
In the above pop up, we will see the SAP note relevant for the error and also whether they exist in our system or not. Moreover, we have the flexibility of searching further from the same pop up if want to do manual search. Enabling this feature will take just couple of minutes but really saves time when we have huge no. of systems connected with Solution Manager and having different issues which may or may not be an issue. Please note - This feature is only available as of Solution Manager 7.1 SP14 version in the solman_setup.
04/21/16--14:31: System Decommissioning : Guided Procedure (Ad-hoc and Planned)
0
0
Hello Friends, You have successfully upgraded your SAP Solution Manager. Now somehow you want to decommission your one of the SAP system and you are wondering where to start. This document helps you to decommission you system from SAP Solution Manager 7.2
Ad-hoc removing system from you SAP Solution Manager Login to your SAP Solution manager and run SM_WORKCENTER transaction code
Go to Managed system configuration and select technical system. From Advanced option select Decommissioning and continue with process
Planned task for removing system from you SAP Solution Manager Login to your SAP Solution manager and run SM_WORKCENTER transaction code
Missing step in new solution manager Opent Technical Administration Tile
Guided Procedure Management
Select Technical system and start in new window
You are missing Decommissioning option in there
Procedure Login to your SAP Solution manager and run SM_WORKCENTER transaction code
Unter Technical Administration select Planning
Select Plans for Technical Systems
Select Guided Procedure (Standard)
Select Decommissionig from the list and press Guided Procedure button
Once you have addedd procedure in list by selectiong procedure Assign or Change Managed object as below Note: Make sure you select Start On time and Date
Select Technical system you want to decommission and Add
Make sure you select RFC connected clients
Once you have addedd systeme in list by selectiong procedure Assign or Change Processor as below
Save your changes and your decommission process will start on time you have assigned to task
Thank you for reading Yogesh
04/25/16--04:14: Big News About SAP Solution Manager: Announcing Focused Solutions
0
0
If you are using SAP Solution Manager to maintain your SAP software environment, here’s some excellent news for you and your team. We have just launched focused solutions for SAP Solution Manager, a new extension concept for SAP Solution Manager, with the idea of helping our customers meet their particular innovation needs on an individual basis, without the need for homegrown software or partner solutions.
Let me share a little background. What’s happened over time is that, as SAP Solution Manager has evolved, it’s become a stable and widely used platform for managing SAP software landscapes. But customers often have specific and individual needs. If SAP were to make changes to the core product to support these customers, or otherwise introduce innovations, we run the risk of the “long tail”: overly complex software with functionality that’s mostly irrelevant for everyone else. The alternative is for customers to develop custom code on top of SAP Solution Manager, which is expensive and timeconsuming, and doesn’t give them the kind of agility they need.
Now, with focused solutions, you can take advantage of a product with a reference process, and with tools and training delivered. SAP delivers standard upgrades, so you license the focused solution once, and we promise to keep it running on future releases. And of course, there are no integration issues because SAP delivers focused solutions based on the proven SAP Solution Manager standard.
This is something I have hoped to offer our customers for a long time. We can do it now thanks to SAPStore.com. If you’re not familiar with SAP Store, it’s an online store that SAP launched last year to provide various offerings with a simple click-through process that doesn’t require technical assistance or any human intervention at all. It’s a great way for individuals at enterprise customers to be able to safely and securely try out apps from SAP, for example, or for entrepreneurs and small businesses to take advantage of enterprise-class software.
Currently, there are two focused solutions available on SAPStore.com. Focused Build for SAP Solution Manager provides an integrated methodology to manage software development for large projects that have specific requirements. Focused Insights enables top-level, strategic, KPI-driven management with user access to metrics in dashboard form, like service level, application performance, or IT scorecard. See for yourself: click here for Focused Build and here for Focused Insights.
The Focused Build approach uses agile software-engineering methods, with progress measured in terms of working functions or products. Tasks are broken down into small increments with short time frames, known as “sprints.” Documentation is streamlined and pragmatic, which means that the project team does not need to understand the details of every business requirement. Since the methodology is ready to run and preconfigured, reporting is completely automated. Project teams have full visibility into solution readiness at all times.
Focused Insights delivers the most relevant and valuable information to the right people in real time. While it provides full transparency of information stored inside SAP Solution Manager, it also takes into account the best practices and experience gained during many customer projects, offering you a set of prepackaged dashboards personalized to your needs.
These focused solutions are available for purchase for all customers. Please note that customers using SAP MaxAttention get their licenses with a dedicated service, and do not have to buy in SAPStore.com. And there is no need for all your SAP Solution Manager users to have access to it; only active project members who actually work with the solution should be licensed. The idea is to be simple, lightweight, user-based, and affordable – only €250 per user for a whole year. We think that with these focused solutions, we are now offering the perfect SAP Solution Manager to run your transformational engagements. The response from the first adopters has been very positive. We hope you will try it out and let us know what you think.
Focused solutions – standard software tailored to you.
We will also highlight SAP Solution Manager focused solutions at the upcoming SAPPHIRE NOW event, taking place in Orlando on May 17-19, 2016. Please feel free to add the following sessions to your personal agenda:
Increase IT Transparency with Focused Insights for SAP Solution Manager, Session ID 34867, Speaker Marc Thier Build Your Digital Core with Focused Build for SAP Solution Manager, Session ID 34865, Speaker Marc Oliver Schaefer
Also see http://support.sap.com/focused for more information. Follow us on Twitter https://www.twitter.com/focusedSAP
04/27/16--00:36: We Launch New Book "SAP Solution Manager for SAP S/4HANA" at SAPPHIRE NOW
0
0
Ten years after Matthias Melich an I introduced SAP Solution Manager to the book market we will launch the new book on SAP Solution Manager at SAPPHIRE NOW 2016 in Orlando. The book explains how we can help manage our customers' digital transformation journey to SAP S/4HANA. Stay tuned for more detailed information in this blog! 1413.jpg
04/29/16--13:04: How to read the contents of a ChaRM textbox for SolMan reporting
0
0
Hello everyone! Sometimes, in Solution Manager, there is a requirement to report Change Request Management (ChaRM) textbox contents. In this post, I will provide the code to do just that. Enjoy!
Create a function module with the following code: FUNCTION Z_SM_READ_CHARM_TEXTBOX . *"---------------------------------------------------------------------*"*"Local Interface: *" IMPORTING *" VALUE(P_GUID) TYPE CRMT_OBJECT_GUID *" VALUE(P_TEXTTYPE) TYPE TDID *" EXPORTING *" REFERENCE(PT_TEXTS) TYPE STRING *"--------------------------------------------------------------------- data: ls_orderadm_h_wrk TYPE LINE OF crmt_orderadm_h_wrkt, ls_PROCEDURE TYPE COMT_TEXT_DET_PROCEDURE, ls_PROC_TYPE TYPE CRMC_PROC_TYPE, lt_struc_p TYPE comt_text_cust_struc2_tab, lt_struc_r TYPE comt_text_cust_struc2_tab, ls_struc_p LIKE LINE OF lt_struc_p, lt_struc2_r TYPE comt_text_cust_struc2_tab, lt_textcom_p TYPE comt_text_textcom_t, ls_textcom_p LIKE LINE OF lt_textcom_ p, lt_textdata TYPE comt_text_textdata_t, lt_textdata_h LIKE lt_textdata, Ls_TEXTDATA_H type COMT_TEXT_TEXTDATA, ls_textdata_h_lines type TLINE, lt_texts_all type table of TDLINE, ls_tabix like sy-tabix. constants: lc_object TYPE COMT_TEXT_TEXTOBJECT value 'CRM_ORDERH', lc_OBJECT_KIND(1) value 'A', lc_no_auth_check(1) value 'X'. * 1) Read CR's info CALL FUNCTION 'CRM_ORDERADM_H_READ_OW' EXPORTING IV_ORDERADM_H_GUID = p_guid IMPORTING ES_ORDERADM_H_WRK = ls_orderadm_h_wrk EXCEPTIONS item_not_found = 98 OTHERS = 99. * 2) Read text procedure CALL FUNCTION 'CRM_ORDER_PROC_TYPE_SELECT_CB' EXPORTING iv_process_type = ls_orderadm_h_wrk-process_type IMPORTING es_proc_type = ls_proc_type EXCEPTIONS entry_not_found = 1 text_entry_not_found = 2 OTHERS = 3. IF sy-subrc <> 0. * MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO * WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4. ENDIF. ls_procedure = ls_proc_type-text_procedure. CALL FUNCTION 'COM_TEXT_CUST_I_PROTEXTID_READ' EXPORTING iv_object = lc_object "CRM_ORDERH iv_procedure = ls_procedure "ZMCR0001 IMPORTING et_struc2_r = lt_struc2_r CHANGING et_struc2 = lt_struc_p EXCEPTIONS textobject_missing = 1 textobject_not_found = 2 textprocedure_missing = 3 textprocedure_not_found = 4 other_error = 5 OTHERS = 6. IF NOT lt_struc_p IS INITIAL. MOVE lc_object TO ls_textcom_p-stxh_key-tdobject. MOVE p_guid TO ls_textcom_p-stxh_key-tdname. LOOP AT lt_struc_p INTO ls_struc_p. MOVE ls_struc_p-textid TO ls_textcom_p-stxh_key-tdid. APPEND ls_textcom_p TO lt_textcom_p. ENDLOOP. * 3) Read text lines CALL FUNCTION 'Z_COM_TEXT_READ_HIST_API' EXPORTING iv_object = lc_object "CRM_ORDERH iv_procedure = ls_procedure "ZMCR0001 iv_no_auth_check = lc_no_auth_check p_texttype = p_texttype IMPORTING PI_TEXTDATA = lt_textdata_h CHANGING it_textcom = lt_textcom_p. ENDIF. * 4) Format text line into one line sort LT_TEXTDATA_H by stxh."by guid and date/time stamp loop at LT_TEXTDATA_H into Ls_TEXTDATA_H. loop at ls_textdata_h-lines into ls_textdata_h_lines. concatenate pt_texts ls_textdata_h_lines-TDLINE into pt_texts separated by space. endloop. endloop. shift pt_texts left deleting leading space. ENDFUNCTION. If function module 'Z_COM_TEXT_READ_HIST_API', it is a modified version of COM_TEXT_READ_HIST_API. I updated it to read specific text id via parameter P_TEXTTYPE, removed data that was not relevant, and returned only text lines as documented
in Cheers!
05/10/16--00:39: Focused Insights: How to build an Operation Dashboard (Part I)
0
0
Operation Dashboard
Based on your catalog of critical alerts and incidents, Operation dashboard builds a real time snapshot of your IT solution status. You can organize and decompose freely your alerts and incidents catalogs in hierarchical structures based on your organization, landscape, locations, customers…Single alerts and incidents are then propagated to the upper levels of your hierarchical structure to offer at the end a single summary view which reports real time on the status of your solution, whatever its complexity.
You can pick alerts and incidents from any producer available in Solution Manager (Application Operation, Business Operation, Business Process Improvement, End-user Experience Monitoring, ITSM…)
It is possible to navigate into your reporting tree to go from the top aggregated level up to the detail of a single event. From the detail of an event, you can jump-in to native expert tools offered by Solution Manager or build your own view to monitor additional contextual information. The dashboard is designed to be displayed in a control center, a computer or in a mobile device. You can create as many dashboard instances as you want, to cover several catalogs or build different role oriented views over the same catalog. Template mechanism helps to tackle mass configuration for large landscapes. In this blog, we will show how to create an Operation Dashboard for your OCC based on Business Process Monitoring. OPE1.png
HOW TO (step by step)
Enter dashboard title: “Demo Focused Insights” Enter level 1 title: “Business Process” Enter level 2 title: “Business Process Step” OPEConfig1.png
Select tab Business Process Select checkbox: “Use Real Business Process” Click on selector to select a business process from solution documentation OPEConfig2.png
Select Your Solution/ Scenario / Process OPEConfig3.png
Select Business Process Step OPEConfig4.png
Select Key Figures with the Helper OPEConfig5.png
Key Figures are select with the arrow
OPEConfig6.png
Save the selection OPEConfig7.png
Click on the following link to get the result OPEConfig9.png
The dashboard is now ready to be distributed
OPEConfig8.png
Focused Insights (http://support.sap.com/focused-insights) Focused solutions for SAP Solution Manager, is the extension concept for SAP Solution Manager, with the idea of helping our customers meet their particular innovation needs on an individual basis, without the need for homegrown software or partner solutions.
The goal of Focused Insights is to build and distribute powerful customer-specific dashboards in minutes using state-of-the-art user experience. The content delivered with Focused Insights has been designed to deliver, in real time, the most relevant and valuable information to the right people. While it provides full transparency of information stored inside SAP Solution Manager, it also takes into account the best practices and experience gained during numerous custom projects, offering a set of prepackaged dashboards tailored to your needs. SAP Focused Insights offers specialized dashboards for experts as well as management or non-technical users. Whether they address the CIO or an expert, dashboards remain consistent among each other since they rely on the same data sources mixed up and presented in different granularities or aggregation levels Focused Insights comes with a rich content. It fully exploits the huge amount of data stored inside SAP Solution Manager. Metrics produced by the activation of a scenario, whether it is IT or business related, become immediately available to the prepackaged dashboards. Raw metrics can be grouped or combined to produce advanced metrics and high level KPIs.
05/10/16--11:43: Focused Insights: Tactical Dashboard Indicators (Part I)
0
0
Tactical Dashboard
Tactical Dashboard comes with a predefined KPIs catalog. You just need to select the managed landscape in scope together with the KPIs you want to monitor. You’ll then have to configure the relevant time periods that you want to monitor (last hour, last 24 hours, yesterday, last week…), your thresholds to calculate the color ratings as well as other parameters depending on the type of KPI.
As a main view, the Tactical shows the current status of the managed landscape for the selected periods. It is fast and simple to check if something is going wrong for one of the KPIs selected and to identify problematic systems.
From the main view, the dashboard offers, for each type of KPI, drill down capability to detailed views. Detail views provide best practice measures and advanced charts with various filters and selectors, to monitor closely the trend of the KPI and pin point the root causes when an issue occurs in the managed landscape.
The objective of this blog is to describe the meaning of the Indicators available int he Tactical Dashboard:
Category Performance TACPERF.jpg
Indicator
System
Value
Trend
Average for selected period and selected source:
Source:
“Average Response time per Dialog Step”
Comparison between
Technical Monitoring (dividing the Total Response time by the Total Number of Steps as it is done in transaction ST03N)
ABAP
yesterday's average and last week's average
Statistical Records Period: yesterday last hour
“WebDynpro/Servlet Response
Average for selected period: yesterday or last hour
JAVA
Time”
Comparison between yesterday's average and last week's average
Category Availability TACAvail.jpg
Indicator
System
Value
Trend
Percentage of system availability for the selected period
System Availability
ABAP / Java
Period:
N/A
Last hour Today Yesterday
Category Hardware Resources TACHARDWARE.png
Indicator
System
Trend
Value Percentage of utilisation for the selected period
CPU Utilization for ALL Virtual Hosts of the SAP System as described in the LMDB.
ABAP / JAVA
N/A
Period: Last hour Yesterday Percentage of utilisation for the selected period
Memory Utilization ALL Virtual Hosts of the SAP System as
ABAP /
described in the LMDB.
JAVA
N/A
Period: Last hour Yesterday
Category Transaction Performance TACPerfTrans.jpg
System
Indicator
Value
Trend Trend of worst Transaction
Average Response Time for the selected period.
Transaction Performance for Core Transactions
Number of configurable
Transactions
is
Each select transaction has different thresholds.
ABAP
Comparison of the AVG Response time
with the selected period.
Period: Last hour Yesterday Last 7 days
Period:
Last 8 weeks Last 12 Months
Focused Insights (http://support.sap.com/focused-insights)
Focused solutions for SAP Solution Manager, is the extension concept for SAP Solution Manager, with the idea of helping our customers meet their particular innovation needs on an individual basis, without the need for homegrown software or partner solutions.
The goal of Focused Insights is to build and distribute powerful customer-specific dashboards in minutes using state-ofthe-art user experience.
The content delivered with Focused Insights has been designed to deliver, in real time, the most relevant and valuable information to the right people. While it provides full transparency of information stored inside SAP Solution Manager, it also takes into account the best practices and experience gained during numerous custom projects, offering a set of prepackaged dashboards tailored to your needs.
SAP Focused Insights offers specialized dashboards for experts as well as management or non-technical users. Whether they address the CIO or an expert, dashboards remain consistent among each other since they rely on the same data sources mixed up and presented in different granularities or aggregation levels
Focused Insights comes with a rich content. It fully exploits the huge amount of data stored inside SAP Solution Manager. Metrics produced by the activation of a scenario, whether it is IT or business related, become immediately available to the prepackaged dashboards. Raw metrics can be grouped or combined to produce advanced metrics and high level KPIs.
older | 1 | .... | 14 | 15 | (Page 16) | 17 | newer
HOME | ABOUT US | CATALOG | CONTACT US | © 2018 http://www.rssing.com
When life gives you a hundred reasons to cry, show life that you have a thousand reasons to smile
© Copyright 2015 - 2024 PDFFOX.COM - All rights reserved.