Hi SDN, my company is going to migrate all SAP applications (ECC,SCM,BI,SLM) to a new provider and to new boxes. As a Solution Manager migration strategy they decided to install a new latest version SM and to migrate all needed object from old SM to the new one. My problem is that I maintained more then 1500 JobDocumentatios and now I don't know how to migrate them; manually is not feasible, so? JSM is defined in a solution, I tried to run /nsolution_transfer I obtain some xlm files with some generic definitions but it seems it is not the right way to proceed. All stuff I discovered in SDN point attention to SAP Note 1327024. I undertake some tests aimed to tranfer some JobDocu from my PRD SM to my DEV SM but is not so clear how to work. I've run RAGS_EJR_EXPORT_JODOC_XML and I'm able to produce an XML file, here it seems there are all information jobDocu related. But then I cannot understand how to import xml file content in DEV solution manager! It seems I have to run in DEP fm AGS_EJR_JSM_AUTOMATION, but how? whay I have to insert in IX_SCRIPT                      IV_SCRIPT_SCHEMA JOBDOC IT_INPUT        Is there someone that already had to export import JobDocus) Thanks Giovanni Lippolis

As described in my previous blog about new key figure content, since December 7 2015 the new ST-A/PI 01S was released and hence close to 100 new key figures have been shipped for Business Process Analytics and Business Process Monitoring in SAP Solution Manager, and over 100 existing key figures were updated. This blog will deal with new features of the KPI catalog and will summarize which key figure areas were updated. You can access the KPI catalog via

 

https://go.support.sap.com/kpicatalog



KPI ratings


If you go into the details of an KPI, then you have the chance to rate this specific KPI once with 1 to 5 stars. After you rated, it might take a short moment before your rating is also displayed on the KPI overview page due to some replication mechanism. As it is not yet possible to provide further comments with your rating, it would be good (in case of a low 1-3 star rating) if you send an email to bpimp@sap.com and provide your suggested enhancements. We are always interested in continuously improving our KPI content and with 01S we enhanced 110 of our existing KPIs.

Update status.png

 

Technical prerequisites for an KPI

Another new feature is the Prerequisites tab. There you can see which software components are required on your managed SAP system (ERP, CRM, SRM, SCM, S/4HANA) in order to be able to execute the respective KPI (version).

Update prerequisites.png

 

KPI versions

All 110 KPIs that got updated with ST-A/PI 01S, now got a new 2nd version. The technical prerequisites that you see per default are always related to the latest available KPI version. If you click on the Versions tab, then you see all different versions available. You also see some short release notes on what has changed in the new version.

Version.png

Typical changes are

  • new selection parameters
  • new output fields in the result list
  • new group by fields for historic trending
  • different program logic to make a key figure more specific/relevant for certain use cases

 

The version in bold font type, is the one that you are currently looking at. If you click on a different version, then you can also see the technical prerequisites for this older version.

Update prerequisites old.png

 

Updated Business Process Analytics & Monitoring content

Main areas of key figure enhancements were the following

  • Open & overdue vendor items got more header related BKPF fields and relevant vendor master data
  • Open & overdue customer items got more header related BKPF fields
  • Additional logic, input and output parameters for Payment runs per day
  • Further output fields for bank statement key figures
  • Open items FI-GLgot more header related BKPF fields
  • Automation rates for vendor/customer payments got additional check for batch input processing
  • Open dispute case key figures got value benchmarking activated based on disputed amount
  • Open promise to pay case key figures got value benchmarking activated based on calculated open amount
  • More input and output fields for Confirmation key figures
  • New logic and additional output fields for Stock-level key figures for Inventory Optimization
  • Planned order key figures with additional MRP list fields in result list
  • Production / process orders key figures with many additional output fields
  • New logic and renaming of Exceptions in incomplete purchase orders and Exceptions in MM invoices (status 'with errors')
  • Additional calculation of invoice receipt quantity for Purchase order items w/o 'final invoice' indicator
  • New output fields in many purchase requisition and Stock Transport Order key figures
  • Additional logic and output fields for MM contract and MM scheduling agreement key figures on item level
  • New output fields for SD invoices not posted to FI and Sales invoices with open FI-AR items
  • Location type as new selection parameter for planned order and purchase requisition key figures in APO
  • New general vendor/customer master data in Generic vendor/customer master check (CompCode level)
  • "Category" as new selection and group by parameter in PM/CS order key figures

 

 

 

Further reading

You can find all necessary information about Business Process Analytics in this document. More information on Business Process Improvement for SAP solutions can be found here.

 

Frequently Asked Questions about Business Process Monitoring and Business Process Analytics are answered under http://wiki.sdn.sap.com/wiki/display/SM/FAQ+Business+Process+Monitoring and

http://wiki.sdn.sap.com/wiki/display/SM/FAQ+Business+Process+Analytics respectively.

 

The following blogs (in chronological order) provide further details about Business Process Analytics and Business Process Monitoring functionalities within the SAP Solution Manager.

Since December 7 2015 the latest ST-A/PI 01S plug-in is available for download. With this plug-in close to 100 new key figures have been shipped for Business Process Analytics and Business Process Monitoring in SAP Solution Manager and over 100 existing key figures were updated. This blog deals only with the new content. The updated content is summarized in a separate blog.The plug-in contains (besides others)

 

  • New workflow related key figures for CRM sales and services
  • New key figures checking configuration settings in FI-GL (line item update open item management)
  • New key figures related to FI-AP clearing and the comparison with related MM invoice or vendor master data
  • New key figures for contract accounting FI-CA (locked accounts and open items)
  • New key figures regarding commitment items generated from purchasing documents
  • New key figures for Dealer Business Management in the automotive area
  • New billing, invoicing and bill print-out key figures for IS Utilities
  • New key figures for inventory optimization regarding project, sales order and consignment stock
  • New key figures for Physical Inventory Documents
  • New purchase order key figures for goods as well as services purchases (service entry sheets)
  • New MM contract key figures regarding different release information
  • New key figures regarding purchasing information records
  • New sales order item key figures (regarding billing, rescheduling, condition changes)
  • New APO key figures regarding planning run exceptions and backorder processing (BOP)
  • New leave request key figure
  • New key figures for QM notifications

 

The complete list of new key figures can be accessed via the KPI catalog that you find at (S-user login required)


https://go.support.sap.com/kpicatalog

When you access the catalog, then you can filter in the New / Updated area on New. Additionally you might want to filter on Business Process Analytics to only see application specific key figure content.

New and update overview.png

 

You then get to see all the 95 new key figures in our area.

New status.png

Of course you can set additional filters as described in the general blog about the KPI catalog,so that you can find key figures only for your area of interest.

 

Important remark: In order to better align the KPI catalog and the Business Process Analytics & Monitoring setup in SAP Solution Manager, the application areas used for filtering in the SAP Solution Manager got readjusted with ST-A/PI 01S. Hence the new application areas BPO* should be used for role authorizations in SAP Solution Manager and transaction ST13. If you apply the new ST-A/PI 01S on your managed system, then you might see twice as many application areas as filters in the Business Process Monitoring setup. This UI problem is solved with support package 14. For support package 12 or 13 you can implement SAP note 2109939 - Advance Corrections BPMon SM 7.1 ST710 delivered with SP14 to get this solved.

 

Further reading

You can find all necessary information about Business Process Analytics in this document. More information on Business Process Improvement for SAP solutions can be found here.

 

Frequently Asked Questions about Business Process Monitoring and Business Process Analytics are answered under http://wiki.sdn.sap.com/wiki/display/SM/FAQ+Business+Process+Monitoring and

http://wiki.sdn.sap.com/wiki/display/SM/FAQ+Business+Process+Analytics respectively.

 

The following blogs (in chronological order) provide further details about Business Process Analytics and Business Process Monitoring functionalities within the SAP Solution Manager.

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

Part 6: Solution Manager 7.2 - Installation and Configuration - VI - Managed System Config - HANA DB

Part 7: Solution Manager 7.2 - Installation and Configuration - VII - Managed System Config - Busines Objects

Part 8: Solution Manager 7.2 - Installation and Configuration - VIII - Managed System Config - Java System



You will find the configuration details of Solution Manager 7.2 on this blog.

 

Solution Manager 7.2 Configurations


I- CA Introscope Enterprise Manager Strategy


From Master Guide;

CA Introscope Enterprise Manager must be installed on the SAP Solution Manager host or on a separate host.

For more information, see service.sap.com/instguides --> Installation & Upgrade Guides --> SAP ComponentsSAP Solution ManagerRelease 7.2 --> 6 Additional Guides - Introscope --> Introscope Setup Guide 9.7.


Useful SAP Notes about Introscope Enterprise Manager

1565954 - Introscope 9 Release Notes

797147 - Introscope Installation for SAP Customers

2138309 - Introscope 9.7 Release Notes for changes and open issues

1579474 - Management Modules for Introscope delivered by SAP

 

Follow the Setup Guide for downloading and installing the Interescope Enterprise Manager current version 9.7.

Install java package, Modify installer.properties first and run the OS independent installer.

SM72_Wily_0.jpg

You can verify the successful installation checking the installation logs from wily log directories.

 

You should carry on the post installation steps like adapting java parameters, isntallaing sap modules etc.

 

After successfull installation you can reach the IEM webview or workstation using the urls like http://emhost:8081/webview or http://emhost:8081/workstation.

Or you can use Solution Manager Root Cause Analysis work_center.

 

Sample workstation screen;

SM72_Wily_1.jpg

Sample webview screen;

SM72_Wily_2.jpg

 

II- SOLMAN_SETUP - Mandatory Configurations

 

These notes should be read carefully and applied before configuring the system.

2236044 - SAP Solution Manager 7.2 Support Package 01: Dump in transaction SOLMAN_SETUP

2229953 - Solution Manager 7.2 SP Stack 01: recommended corrections

2154957 - Unified Rendering for SAP_UI 740

2212887 - Corrections for unified rendering up to SAP_UI 740/14 Ia

1411980 - Comments about the implementation of unified rendering corrections

 

There are 3 mandatory configuration scenarios; System Preperation, Infrastructure Preperation and Basic Configuration.

SM72_mandatoryConfig.jpg

Here are the detail steps for all these configuration scenarios.


1- System Preperation

SM72_systemprep.jpg

Define the System's Role in the firts step.


There are manual and automatic activities to perform in Check Prerequisites Step. Each step  has its documentation. You can Display the documentation and follow the instructions carefully.

There is a navigation link also for the related transaction or web dynpro or related urls.

SM72_systemprep_2.jpg

SM72_systemprep_3.jpg

On Setup Connections to SAP step you have RFC Connectivity part for creating SAPOSS and SAP-OSS-LIST-O01.

And there is Support Hub Connectivity part for below functioanalities;

    • Configure SOAP Runtime  : User SRT_ADMIN to configure SOAP according to the documentation.
    • Register new S-User in SAP's PI System : You create a technical user on SMP according to the notes "2174416 - Technical User for Data Transfer with SAP Backbone System and 2174416 - Technical User for Data Transfer with SAP Backbone System"
    • Specify Configuration parameters

There are automatic activities Configure SSL Store, Configure Consumer Proxies and Log. Port and Check Channel Configuration.

SM72_systemprep_4.jpg

The help screen for this step explains us about the new  communication channel of SAP with below paragraph.

 

"SAP will introduce a new infrastructure and data communication channels, starting with SAP Solution Manager 7.2. This new framework builds the foundation for all future applications exchanging data between SAP Solution Manager and the SAP Support Portal in a secure, reliable, and controlled way. Existing applications will not be affected by this change and they will be migrated to the new platform gradually within the next few years without business disruption."

 

In Apply Recent Corrections step, you apply recent ABAP and Java corrections to your SAP Solution Manager system

SM72_systemprep_6.jpg

In Maintain Technical Users step you create or update dialog users, technical users, or BW users, and assign roles to users, depending on the scenario.

SM72_systemprep_7.jpg

In the last Complete step you can see overall configuration of system preperation steps. In need you can jump to the required step back.

SM72_systemprep_8.jpg

2- Infrastructure Preperation


In this scenario you configure the infrastructure to run SAP Solution Manager. There are 8 steps to succeed the configuration of the scenario.

SM72_Infra_1.jpg

In the "1- Set Up Landscape Management" step you set up the synchronization of the system landscape directories (SLDs) and SAP Solution Manager, to keep the information about the system landscape up-to-date. Each substep screens can be seen below.

SM72_Infra_2.jpg

In substep SLD Connnections you create a new connection like below.

SM72_Infra_3.jpg

 

"2- Set Up Java Connectivity" step consists of Define HTTP Connectivity, Enable Connectivity and Diagnostics Agent Authentication substeps. You provide required field values accordingly and execute automatic configurations as seen below.

SM72_Infra_4.jpg

Solution Manager is using SAP BW for reporting purposes. You can use either the currnet client of Solution Manager or you can define another SAP BW system. In "3- Set Up SAP BW" step you firstly confirm the BW system, then create BW users and in the last substep you execute automatic acitivities.

You must have defined the logical system name for your BW client.

SM72_Infra_5.jpg

In "4- Define CA Interescope" Step you discover and define your Interescope Enterprise Manager. You must have installed Diagnostic Agent (DAA) Instance on your Solution Manager System. You can manage Interescope EM users in this step also.

SM72_Infra_6.jpg

In "5. Set up E-Mail Communication"  step you set up the infrastructure that enables SAP Solution Manager to send notifications using e-mail and text messaging (short message service, SMS).

SM72_Infra_7.jpg

Some scenarios in SAP Solution Manager needs CRM infrastructure. In "6- Configure CRM Basics" step you configure these infrastructure in manual and automatic steps.

SM72_Infra_8.jpg

In "7- Enable Gateway Services" you activate OData services in SAP Gateway for SAP UI5 applications and mobile applications. With this activation you can use SAP Fiori applications for Solution Manager services. For SAP Solution Manager, the SAP Gateway and SAP Solution Manager share the same system.

As a prerequisite the user who performs this step has a task in the customizing transport request. Activation of the services uses this task.

After selecting the required services you prepare activation and then with the help of the help text you Start Transaction and activate OData services.

SM72_Infra_9.jpg

And in the final "8 - Complete" step you see the statuses of all steps. If you have any red status steps you could go back and correct the configuration.

SM72_Infra_10.jpg

Now you can pass the Basic Configuration Scenarios.



3- Basic Configuration

 

There are five steps to fulfill in this scenario as you can see below picture. In the first "1- Configure Basic Functions" step you execute automatic configurations for creating logical ports, activating services, enabling Solution Manager applications.

SM72_basic_1.jpg

In "2- Schedule Jobs" step many important Solution Manager Jobs are scheduled.

SM72_basic_2.jpg

 

In "3- Configure Manually" step, you configure the following:

• Content update (SAP Solution Manager Content, service content)

• Connection from SAP to the SAP Solution Manager system

• Session housekeeping

SM72_basic_3.jpg

In "4- Create Basic Dialog Users" step, you create or update dialog users for root cause analysis (SAPSUPPORT) and service delivery (SAPSERVICE).

SM72_basic_4.jpg

 

This final "5- Complete" 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.

SM72_basic_5.jpg

 

This is the end of Solution Manager 7.2 configurations.

 

Next topic will be about the changes from Solution Manager 7.1 to Solution Manager 7.2 in terms of System Administration.

 

Thanks for your interests.

Problem:

There is no performance data returned or the page always refreshed after clicking 'Click here to load data from business warehouse ' in SAP Solution Manager: Work Center -> Root Cause Analysis -> End-to-End Analysis -> select your system -> Workload Analysis -> Overview.

1.png

At the same time, there are lots of warning Communication error, CPIC return code 020, SAP return code 456 shown in SM21.

2.png

Detailed information for this warning:

3.png

4.png

 

Then I search in SAP SMP and get SAP notes 1983164 - "Error found retrieving data" refreshing a report with parent members / 1032461 - MDX parser does not start, according to these notes, I test the RFC connection MDX PARSER but failed with the error below:

5.jpg

 

 

Cause:

The file librfc32.dll which is used for communication between ABAP and MDX parser does not exist in kernel directory nor environment variable PATH directory. (Our Environment: Windows Server 2008 R2, Solution Manager 7.1 SPS13, Kernel 7.21 EXT)


Solution:

Download the current version of librfc32.dll for you kernel and extract it to your kernel directory.

Support Packages and Patches

  -> Additional Components

    -> SAP Kernel

      -> SAP KERNEL <32/64-BIT >  ##### Download non-unicode version! ######

        -> SAP KERNEL xxx

          -> <your platform>

            -> #Database independent

 

Perform connection test MDX parser RFC again.

6.png

Check performance overview data, now I get it.

7.png

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

Part 6: Solution Manager 7.2 - Installation and Configuration - VI - Managed System Config - HANA DB

Part 7: Solution Manager 7.2 - Installation and Configuration - VII - Managed System Config - Busines Objects

Part 8: Solution Manager 7.2 - Installation and Configuration - VIII - Managed System Config - Java System



Solution Manager 7.2 is already in Ramp-Up.

 

I watched the video of the chearful team of Solution Manager 7.2.

As System Administrators we willl also be installing and configuring Solution Manager 7.2 from now on.

So I decided to install it on premise.

 

Cloud version of Solution Manager 7.2 is also available on SAP Cloud Appliance Library https://cal.sap.com/

(SAP Solution Manager 7.2 SPS01 on SAP HANA for Content Activation Evaluation of a Customer's Own Documentation)

 

I am going to try to write some series of blogs on Solution Manager 7.2 in terms of System Administration.

They will be about installations, configurations, changes and managed system configurations.

Below you can find the installation specific part of this series of blogs.

 

Preperation Steps

  • Since Solution Manager 7.2 is in Ramp-Up yet you need to apply for this. You can find detailed info about Ramp-Up in links Demystifying SAP's Ramp-Up process and SAP Ramp-Up
  • Prepare a system for installation. If possible find a system that you could install SM 7.2 on HANA DB. Unfortunately I did not have chance to use HANA DB. I installed my system on SQL Server 2012. My system is a virtual system with 4 vCPU and 32 GB of RAM and enough disks.
  • Download DVDs

       SM72_Blog_I_DVD.jpg

  • Obtain Master Guide and Installation Guides
  • Read SAP Notes about Solution Manager 7.2
  • Preperatory Steps on the system
    • Turn Off UAC
    • Turn off Automatic Updates
    • Turn off Windows Firewall
    • Turn off IE ESC
    • Timezone Settings
    • Regional Settings
    • Configure Hostname
    • Configure Page File Size
    • Configure DEP
    • Configure Folder Options
    • Configure Start Menu
    • Configure Command Prompt
    • Activate Telnet Client
    • Install Notepad++

 

 

After preperation steps I followed the Implementation sequence from Master Guide in below order.

 

Master Guide

 

For information on the installation of SAP Solution Manager go to link SYSTEM PROVISIONING - SAP SOLUTION MANAGER 7.2 SPS 01 BASED ON SAP NETWEAVER 7.4 ABAP +JAVA (from master Guide: see service.sap.com/instguides --> SAP ComponentsSAP Solution ManagerRelease 7.2 --> InstallationSystem Provisioning for SAP Solution Manager 7.2)

 

From PAM page you can go below links about Solution Manager 7.2

SAP Road Map

Product Homepage

Master Guide

Installation / Upgrade Guide

SAP Help Portal

Release Notes

Release Restrictions Note

Additional Release Information

SAP Community Network

 

Installation and Configuration

 

The installation of SAP Solution Manager 7.2 SP01 needs to be run in the following way:

 

1. Instal DB Software (Microsoft SQL Server 2012)

 

Installed DB Software Microsoft SQL Server 2012 SP1 and then updated to SP2.  (Upgrade to and Installation of SQL Server 2012 in an SAP Environment)

SM72_Blog_I_DB.jpg

SM72_Blog_I_DB2.jpg

   

2. Install the SAP Solution Manager 7.2 SP01 ABAP system with SWPM and the resulting stack.xml.

 

Followed below Guide for installing ABAP part of the system.

Installation of SAP Systems Based on SAP NetWeaver 7.1 to 7.5 Using Software Provisioning Manager 1.0: MS SQL Server, Operating System: Windows, Technology: ABAP

 

 

SID

SMA

Instance Numbers

00,  01

 

SM72_Blog_I_ABAP_1.jpg

SM72_Blog_I_ABAP_2.jpg

 

Post Installation Steps for ABAP:

 

    • Logon to System
    • Perform the automated initial setup
    • Install the SAP license
    • Perform the consistency check
    • Configure the Transport Management System
    • You perform post-installation steps for the application server ABAP
      • Upload and set system profiles using transaction RZ10

Configure your Solution Manager 7.2 profile parameters according to the note

2048519 - Profile parameters for SAP Solution Manager 7.2

      • Create logon and RFC server groups using transactions SMLG and RZ12
      • Create operation modes using transaction RZ04
      • Schedule standard jobs using transaction SM36
      • Configuration of SLD data supplier using transaction RZ70 (After installation of Java and configuration of SLD)
      • Perform load generation using transaction SGEN
    • If required, you install additional languages and perform language transport
    • SAP Kernel Release 7.40 and Higher: You perform IP Multicast Configuration
    • You configure the user management
    • You ensure user security
    • If required, you perform the client copy
    • SAP systems based on SAP NetWeaver 7.40 and higher only: If required, you change the keys for the secure storage
    • You apply the latest kernel and Support Packages

You run Maintenance Planner instead of Maintenance Optimizer transaction using the link   Maintenance Planner for applying SP Stack 01. You can have detailed information about planner using Maintenance Tools: Maintenance Planner and Maintenance Optimizer

These are the screenshots from maintenance planner. You can download stack.xml file on download files tab of the application.

SM72_Blog_I_Mplanner_1.jpg

SM72_Blog_I_Mplanner_2.jpg

You get stack.xml file and download Support Packages

 

Before applying the stack you should check below notes and according to directions you need to apply some of them before, some of them during update and some of the others after SUM update.

I advise you to read the notes carefully because this can effect the update and later configurations.

 

2084104 - Central Note - Software Update Manager 1.0 SP14 [lmt_005]

1595736 - Solution Manager: Overview on Release Information Notes

2229953 - Solution Manager 7.2 SP Stack 01S0014395147: recommended corrections

1668882 - Note Assistant: Important notes for SAP_BASIS 730,731,740

2248091 - Change to reimplementation handling

2087917 - SAP Solution Manager 7.20 SP1 - Basic functions

2216794 - ABAP Download Service: Correction of Transformation

2166856 - API roles: Maintenance of organizational levels

2189071 - DGP: Improved clean up for waiting export entries

1472465 - SAP Solution Manager 7.1 and 7.2 - System Landscape Setup Guide

2154957 - Unified Rendering for SAP_UI 740

 

You download SUM also to update the ABAP system and run the tool. You can see some screenshots from the tool below.
SM72_Blog_I_ABAP_SUM_1.jpg

SM72_Blog_I_ABAP_SUM_2.jpg

 

You can see initial and target stack SP versions and levels in below report of SUM.

SM72_Blog_I_ABAP_SUM_4.jpg

    • You perform a full system backup

 

 

3. Install the SAP Solution Manager 7.2 SP01 Java system with SWPM from the Java DVD.

 

Followed below Guide for installing Java part of the system.

Installation of SAP Systems Based on SAP NetWeaver 7.1 to 7.5 Using Software Provisioning Manager 1.0: MS SQL Server, Operating System: Windows, Technology: Java

 

SID

SMJ

Instance Numbers

02,  03

SM72_Blog_I_Java_1.jpg

SM72_Blog_I_Java_2.jpg

SM72_Blog_I_Java_3.jpg

 

Post Installation Steps for Java:

Java component patches shall be downloaded from the Support Portal at https://support.sap.com/swdc -> Software Download -> Support Packages and Patches -> Browse Our Download Catalog -> SAP Technology Components -> SAP Solution Manager -> SAP Solution Manager 7.2 -> Solution Manager JAVA Stack. After download, place the files corresponding to the below software component list, in a preferred folder in order to implement the patches. See the SUM guide for further details (see link above, 'Chapter: 7 Applying Single Component Updates and Patches Using a Manually Prepared Directory').

        • J2EE ENGINE SERVERCORE 7.40 -> OS independent: Patch 20 (or higher) for J2EE ENGINE SERVERCORE 7.40 SP 11
        • J2EE ENGINE LM-CORE 7.40 -> OS independent: Patch 5 (or higher) for J2EE ENGINE LM-CORE 7.40 SP 11
        • J2EE ENGINE CORE TOOLS -> OS independent: Patch 1 (or higher) for J2EE ENGINE CORE TOOLS SP 11
        • J2EE ENGINE APPLICATIONS -> OS independent: Patch 4 (or higher) for J2EE ENGINE APPLICATIONS SP 11
        • J2EE ENGINE FRAMEWORK 7.40 -> OS independent: Patch 6 (or higher) for J2EE ENGINE FRAMEWORK 7.40 SP 11
        • J2EE ENGINE FACADE 7.40 -> OS independent: Patch 1 (or higher) for J2EE ENGINE FACADE 7.40 SP 11
        • LMNWABASICCOMP 7.40 -> OS independent: Patch 1 (or higher) for LMNWABASICCOMP 7.40 SP 11
        • ENGINEAPI 7.40 -> OS independent: Patch 6 (or higher) for ENGINEAPI 7.40 SP 11
        • LM NWA BASIC APPS 7.40 -> OS independent: Patch 4 (or higher) for LM NWA BASIC APPS 7.40 SP 11
        • UME ADMINISTRATION 7.40 -> OS independent: Patch 6 (or higher) for UME ADMINISTRATION 7.40 SP 11
        • LM CONFIGURATION WIZARD 7.40 -> OS independent: Patch 1 (or higher) for LM CONFIGURATION WIZARD 7.40 SP 11
        • In case you do operate Introscope 9.5 (and not yet 9.7):
          WILY INTRO AGT 9.5 MIN J5VIASM -> OS independent: Patch 1 (or higher) for WILY INTRO AGT 9.5 MIN J5VIASM SP 06

 

Use SUM and apply the patches like below.

SM72_Blog_I_Java_SUM.jpg

    • You configure the user management
    • You ensure user security
    • You run automated configuration
      • SLD Configuration

Use http://<hostname>:<port>/sld/fun and enable SLD automatically.

 

SM72_Blog_I_Java_SLD_1.jpg

SM72_Blog_I_Java_SLD_2.jpg

 

    • You perform a full system backup

 

 

And this is the end of the installation phases of Solution Manager 7.2.

I will continue on Configurations blog coming soon.

 

See you soon.




In recent years we got again and again asked by customers whether it would be possible to track how intensive Business Process Analytics and Business Process Operations Dashboards  are used by the user community to which it was rolled-out. As of SAP Solution Manager 7.1 support package 14, this kind of usage analysis is available. This functionality will allow you to track, that you did not just activate another SAP Solution Manager functionality, but that this functionality is really used operationally.

 

If you access the Maintain BPO Reporting Infrastructure section from within your Business Process Operations work center, then you see a new tab strip Usage Analysis.

First you get an overview about the number of times that Business Process Analytics / Business Process Operations Dashboards got executed within a given time frame.

Then you get to see the top 5 users that executed the respective application most often.

Overview and top 5.png

 

After this you get detailed sections per application. In those sections you can also see which key figures were executed when.

Details.png

 

Then comes a section where you can see which key figures have been executed most/least often (no matter if the key figure was accessed via Analytics or Dashboard(s). You can also run an optional analysis if key figures exist where the data collection was activated, but where the collected data was never consumed so far.

Tops and flops and not used.png

 

The last section allows to check for a historic trend for a single selected key figure.

Historic trend.png

 

 

Further reading

You can find all necessary information about Business Process Analytics in this document. More information on Business Process Improvement for SAP solutions can be found here.

 

Frequently Asked Questions about Business Process Monitoring and Business Process Analytics are answered under http://wiki.sdn.sap.com/wiki/display/SM/FAQ+Business+Process+Monitoring and

http://wiki.sdn.sap.com/wiki/display/SM/FAQ+Business+Process+Analytics respectively.

 

The following blogs (in chronological order) provide further details about Business Process Analytics and Business Process Monitoring functionalities within the SAP Solution Manager.

Hello all, this is Evan Stoddard, one of the Product Managers for SAP Solution Manager.

 

SAP Solution Manager Product Management is pleased to announce that SAP Solution Manager 7.2 SPS01 on Linux/SAP HANA was released to customers and partners via the SAP Cloud Appliance Library (SAP CAL) today. This is the first time we have used SAP CAL for the SAP Solution Manager, and also the first time we have done this in the middle of a SAP Solution Manager Ramp-up.

 

The scope of this system is to provide customers and partners an environment where they can upload solution documentation from their own 7.1 systems to the 7.2 system in SAP CAL, and then perform and evaluation the content activation process to make their documentation visible in the new 7.2 solution documentation UI.

 

By using SAP CAL, it's possible to create a system in under 1 hour from a standard solution, and then log on an perform the upload and activation process. The system can be restored over and over from backup via the cloud infrastructure, so that the one-time activation process can be easily repeated.

 

See the official announcement in the SAP CAL SCN community here:

 

http://scn.sap.com/community/cloud-appliance-library/blog/2016/01/18/sap-solution-manager-72-coming-soon-to-sap-cal#

 

The training materials for this scenario are now available on the SAP Solution Manager Early Knowledge Transfer site at http://suppport.sap.com/ekt-solutionmanager -> SAP Solution Manager 7.2 Learning Maps -> Content Activation -> Preparation -> Test and Evaluate the Solution Documentation Activation Procedure With SAP Sol Man 7.2 in SAP CAL.

In 2011 the Business Process Operations dashboards were introduced. Those dashboards are especially used to track progress during business process improvement activities. As those dashboards also used by senior management in order to understand where progress is achieved and where it is not it is always a challenge to provide the right level of granularity. Many large companies who are operating all around the globe and where the organization is split into different markets, regions or business units asked how this can be reflected in our dashboards?! The special challenge is typically the fact that the markets or regions are not directly reflected as such in the respective SAP system, i.e. no company code, sales organization or plant represents a specific market or region. Instead a market comprises several different company codes, sales organizations or plants.

 

Since SAP Solution Manager support package 12, this challenge is solved by so called virtual characteristics. With the help of of those virtual characteristics you are now able to build dashboards that provide a global overview about all your markets, e.g. as shown in the dashboard below the data is split between the 4 markets America, Asia, Europe & Japan. Additionally you see one column comprising possible company codes that are not (yet) assigned to any market.

Dashboard overview.png

If you configured some additional parent child relationships between your panels, then a forward navigation is possible. So if you click on the cell for "Open and overdue FI-AR items" in America, then you get to see which company codes are part of the market.

Dashboard details.png

So how can you get your markets, regions shown in your dashboards?

 

Getting virtual characteristics into a dashboard


If you access your setup environment for Business Process Operations dashboards, then you have to assign the respective virtual characteristic on Analytical Key Figure Instance (AKFI) level to a Category or Drilldown dimension.

Use virt char in dashboard.png

 

Now if you look into your SAP Solution Manager you will not see any such virtual characteristic immediately. You have to create those first, before they can be used.


Defining new virtual characteristics

 

If you want to create and define virtual characteristics according to your needs, then please access the BPO reporting infrastructure from within the Business Process Operations work center. As of support package 12 you should find there one tab strip Virtual Characteristics which will help you with some kind guided procedure. As the data access to the generic Infocube/Twincubes in Business Process Analytics and BPO dashboards happens technically via so called Semantic IDs, you have to create such new Semantic IDs first. The semantic ID defines as an example whether the value '0001' in parameter 1 is representing plant '0001' or company code '0001' or sales organization '0001'. For our dashboard shown above we defined some new semantic ID 'ZVIRT_MARKET'.

1 define semantic ID.png

In a 2nd step we defined a new virtual characteristic ZVIRT_CHARSTIC_MARKET (the one that we assigned to an AKFI as seen above) and assigned to it the newly created semantic ID.

 

2 Map virt char and semantic ID.png

In the 3rd step we defined for our new virtual characteristic that the 'concrete values' for our markets are America, Asia, Europe & Japan. Those are the 4 markets displayed on the dashboard at the beginning of this blog.

 

3 create virtual char.png

 

In the 4th and final step we defined for every possible virtual characteristic value which "real values" from the SAP system are comprised, e.g. our market Europe consists of the company codes 3001 to 9999, DK01, FR01 and IT01. In case of sales key figures you would need to define another mapping for Europe which uses semantic ID ERP_VKORG in order to also map which sales organizations belong to market Europe.

 

4 map virtual to real.png

 

After this mapping definition and assignment of new virtual characteristics to your respective AKFIs used in the dashboard, you can lean back and enjoy your new dashboards which automatically split your data according to the newly defined markets, regions, business units etc.

 

Further reading

You can find all necessary information about Business Process Analytics in this document. More information on Business Process Improvement for SAP solutions can be found here.

 

Frequently Asked Questions about Business Process Monitoring and Business Process Analytics are answered under http://wiki.sdn.sap.com/wiki/display/SM/FAQ+Business+Process+Monitoring and

http://wiki.sdn.sap.com/wiki/display/SM/FAQ+Business+Process+Analytics respectively.

 

The following blogs (in chronological order) provide further details about Business Process Analytics and Business Process Monitoring functionalities within the SAP Solution Manager.

With SAP Solution Manager 7.1 support package 14 another puzzle piece has been added towards a complete "Business Process Improvement Suite" as I would call it. While we provided Business Process Analytics as the root cause analysis tool in 2010 (meanwhile also available in an ad-hoc version and as native iPad app) and added a dashboard layer on top in 2011, we now shipped a new SAPUI5 application called "Dependency Diagrams".

 

Note: Please refer to SAP note 2228248 in order to learn which steps are recommended when moving from support package 5-13 up to support package 14!

 

As we ship such a vast KPI content out-of-the-box with close to 1.000 KPIs, customers can easily lose the overview on what is measured and tracked in what way and for what purpose. With the help of the Dependency Diagrams you can build kind of KPI trees where you bring the different KPIs into some logical, hierarchical order. You can visualize the dependency chains of KPIs and get the "picture" updated with your live data.

 

The easiest way to access the new application, is to define a new favorite in the user menu. Just specify BSP application AGS_KPI_TREE and select WebContent/index.html from the value help as start page.

Note: Remember to activate the corresponding BSP service in transaction SICF.

Runtime BSP.png

 

When you then access the application you can select one diagram that must have been defined beforehand, e.g. looking at a diagram about the typical financial business KPI "Days Sales Outstanding (DSO).

 

Initial select.png

 

After selecting the diagram you get to see the root level (here Days Sales Outstanding itself) and the dependent level 1 KPIs. In our example all five level 1 KPIs are collected via Business Process Analytics, i.e. why you see an Analyze-hyperlink which allows a direct forward navigation into Business Process Analytics. The backend data from your SAP BusinessSuite or SAP S/4 HANA system can be shown as count of documents/items (e.g. 241 deliveries or 310 SD invoices) or as one accumulated monetary value (e.g. 2,7 million Euro or 311,3 million USD).

The tiles that you see could be

  • populated by Business Process Analytics data
  • populated by Business Process Monitoring data
  • populated via query from a connected SAP BW system
  • not populated with any data and just used for modeling/visualizing

 

Below SD Orders not billed and Open customer items we see a '+' icon, so we can further expand the tree in those areas.

 

Small tree.png

 

As we know that the majority of billing documents is created via billing run, we put another KPI below the SD Orders not billed. This additional KPI looks specifically at all error messages that were raised during billing due runs. One of the most typical error messages is the problem of incomplete sales order items and hence you can further expand to see Missing fields in SD documents.

Big tree.png

So with the help of this application you can

  • Bring business BW reporting and operational Business Process Analytics data for root cause analysis together in one view
  • Structure your KPIs in meaningful dependency diagrams, so that every manager and subject matter experts understands the leverage that one low level KPI might have on any (business) KPI on top, like DSO.
  • Set threshold values so that the numbers in the tiles get a green, amber or red rating
  • Decide if you put your focus on document numbers or monetary values (and which target currency)
  • Use the forward navigation to get from this overview into the actual root cause analysis with Business Process Analytics.

 

This application can be used on any device and any screen resolution, because of the SAPUI5 user interface.

 

Configuration

 

There are no diagram templates shipped with this application. Instead you have to model everything yourself. The configuration has some similarities to the configuration of Business Process Operations dashboards in SAP Solution Manager. So you have to create Analytical Key Figure Instances (AKFIs) first, where you define which data should be displayed from which source and define potential thresholds. Then you model the respective Dependency Diagram / KPI Hierarchy and bring the AKFIs into some logical order.

 

In order to access the configuration application it is easiest to create a new favorite in the user menu. For this specify AGS_RI_KPIHIERARCHY_SETUP as Web Dynpro application.

setup webdynpro.png

If you access the setup environment, there is always just one root. After this you always just specify which AKFI is child of which other AKFI (identified by technical name not description). You can always have more than one child for every parent tile. Based on these parent/child relationships the application calculates the hierarchy level automatically and arranges the tiles from top to bottom.

Diagram setup.png

 

So if yo have Business Process Analytics already up and running in your SAP Solution Manager 7.1 with support package 14, then you should be only a few clicks away from creating your own Dependency Diagram and show it to your management in order to get the budget for your desired business process improvement activities.

 

Further reading

You can find all necessary information about Business Process Analytics in this document. More information on Business Process Improvement for SAP solutions can be found here.

 

Frequently Asked Questions about Business Process Monitoring and Business Process Analytics are answered under http://wiki.sdn.sap.com/wiki/display/SM/FAQ+Business+Process+Monitoring and

http://wiki.sdn.sap.com/wiki/display/SM/FAQ+Business+Process+Analytics respectively.

 

The following blogs (in chronological order) provide further details about Business Process Analytics and Business Process Monitoring functionalities within the SAP Solution Manager.


AS ABAP SLD registration process:


You should perform ABAP SLD registration by executing transaction RZ70.



2016-01-21_13-19-54.jpg



in case you have problem with SLD_UC registration  (DETAIL: TP SLD_UC not registered!!!!) please consult this link (read comment from vijendar reddy  )!!



AS Java SLD registration process:



The properly configure this service, the following must be done.

Use the Destinations Service to:

 

1. Set up the registration by creating a destination called "SLD_DataSupplier" of type HTTP. Enter the following configuration settings. (Note: The specified user must have the user role "SAP_SLD_DATA_SUPPLIER" or higher on the target SLD Server.)

  • Appropriate URL (http://<host>:<port>)
  • Authentication should be set to BASIC
  • Appropriate User Name and Password

2. Set up the AS Java access to the SLD by creating a destination called "SLD_Client" of type HTTP.

Enter the same configuration settings as in the SLD_DataSupplier destination.

(Note: The specified user must have user role "SAP_SLD_GUEST" or higher. Aditional write access permissions may be required by certain applications. Refer to the corresponding application documentation for SLD access requirements.)



2016-01-21_13-00-43.jpg

 

2016-01-21_13-08-00.jpg

 

2016-01-21_13-09-17.jpg

2016-01-21_13-10-54.jpg

 

2016-01-21_13-11-03.jpg

 

 

Now you can start registration of yours AS Java in the SLD by executing following action:

2016-01-21_13-15-44.jpg

 

 

pls execute red box button

 

2016-01-21_13-16-28.jpg

 

 

At the ned go tyou SLD and check is there your AS JAVA and AS ABAP present/registered !!

 

Happy registering! 

 

BM

Changing the configuration of the Metrics and Alerts in the template and activating the changed settings can be done from front end applications like System Monitoring and Alert Inbox.  This functionality is provided from front end applications to reduce the number of steps in changing the configuration of Metrics and Alerts and to make the configuration change process fast and simple.

 

Note:The functionality mentioned in this blog is specific to Solution Manager 7.2 release. Also please note that when the document is viewed in the PDF format, Red rating icons are shown in dark blue and Yellow rating icons are shown in light blue.

 

 

Procedure for changing the Configuration from Alert Inbox

 

Settings that can be changed for an Alert from Alert Inbox


Following data can be changed for an alert from Alert Inbox.

  • Alert Active/Inactive status
  • Notification variant data
  • Incident variant data
  • Third part Component variant data
  • Auto Reaction variant data
  • Alert Active/Inactive status

 

 

Settings that can be changed for a metric from Alert Inbox

 

  • Metric Active/Inactive status
  • Threshold Type – It can be changed to Info only
  • Threshold Values

 

Scenario 1 – Custom template has been assigned to the managed object and an alert related to the managed object is available in Alert Inbox.

 

       1.     Navigate to Alert Inbox on “System & Application Monitoring” work center.

       2.     Select a record on System Alerts/Database Alerts/Host Alerts query and click “Change Configuration” button.

       3.     The following pop up appears when a custom template has been assigned to the managed object.

1.png

Following data can be changed for an alert from Alert Inbox.

  • Alert Active/Inactive status
  • Notification variant data
  • Incident variant data
  • Third part Component variant data
  • Auto Reaction variant data


Each wok mode is shown as a tab in which the selected alert is active. User can make the changes at the work mode level also.


Options “Apply changes to template <template name>” and “Apply changes on the managed object only” will be displayed on the pop up.


When a Custom template is assigned to the managed object, then user will have the option to change the settings at the managed object level or at the template level.


4.     Make necessary changes and select the option “Apply changes on the managed object only” and click on “Apply Changes” button.

The changes made are applied only at the managed object level.


5.     Select another record on System Alerts/Database Alerts/Host Alerts query where a custom template has been assigned to its managed object and there are no managed object specific settings and click “Change Configuration” button.


6.     Select the option “Apply changes to template <template name>” and click on Apply changes button.

The alert settings will be changed at the template level and the change is reflected for all the managed objects on which this template has been applied. The list of managed objects using the this template can be found on clicking the link “Show affected managed objects” next to the option “Apply changes to template <template name>”


Clicking on the “Close” button without performing any action on the pop up cancels the operation. Functionality is same as mentioned above while changing the configuration of alert from Alert Group details page.

Scenario 2 – SAP template has been assigned to the managed object and an alert related to the managed object is available in Alert Inbox.


                            The following pop up appears when a SAP template has been assigned to the managed object and the user had selected an alert in Alert Inbox and clicked on “Change Configuration” button.


2.png

User will have the option to change the settings only at the managed object level. Make the changes and click on “Apply Changes” button.


If managed object specific settings are maintained for the managed object already and if user wants to make further settings for the alert, then user will have the option to change the settings only at the managed object level.


            Functionality is same as mentioned above while changing the configuration of alert from Alert Group details page.

 

Scenario 3 – Custom template has been assigned to the managed object and the user would like to change the configuration of the metric from Alert Inbox.

 

On the Alert details table select a metric and click on “Change Configuration” button.

3.png

The following pop up appears when a custom template has been assigned to the managed object. All the Active work modes for the metric will be shown as separate tabs.

 

4.png

 

User will have the option to change the settings at the managed object level or at the template level.


Options “Apply changes to template <template name>” and “Apply changes on the managed object only” will be displayed on the pop up.


If the option “Apply changes to the template” is selected, the metric settings will be changed at the template level and the change is reflected for all the managed objects on which this template has been applied. The list of managed objects using the this template can be found on clicking the link “Show Managed objects where the changes take effect” next to the option “Apply changes to template <template name>”


If the option “Apply changes only on the managed object” is selected, changes made will be applicable only for the managed object.


Scenario 4 –SAP template has been assigned to the managed object and the user would like to change the configuration of the metric from Alert Inbox.

 

1.     If a SAP template is assigned to the managed object, then user will have the option to change the settings only at the managed object. Following pop up will be displayed, and the user should click on the “Apply Changes” button after making the specific settings on the pop up. The changes made for the metric will be at the managed object level.

5.png

2. If managed object specific settings are maintained for the metric then user will have the option to change the settings only at the managed object only. Following pop up will be displayed and the user should click on the “Apply Changes” button after changing the settings on the pop up.

 

6.png

Make necessary changes and click on “Apply Changes” button. The changes made are applied only at the managed object level.

 

3. Clicking on the “Close” button without performing any action on the pop up cancels the operation.

 

Procedure for changing the Configuration from System Monitoring

 

Settings that can be changed for a metric from System Monitoring

  • Metric Active/Inactive status
  • Threshold Type – It can be changed to Info only
  • Threshold Values


Scenario 1 – Custom template has been assigned to the managed object and the user would like to change the configuration of the metric from System Monitoring.

1.     Navigate to System Monitoring application on “System & Application Monitoring” work center.

2.     System Monitoring application is launched.


7.png


3.       Click on any tile shown on “Status Overview” panel and navigate to System View.

4.       Click on any Category icon on the tile related to the system and navigate to “System Hierarchy” view.

5.       Hover on a metric in the “Event and Metric” view.


8.png


6.       Click on “Change Configuration” link.


The following pop up appears when a custom template has been assigned to the managed object and no managed object specific settings exist for the metric.

9.png

    • All the Active work modes for the metric will be shown as separate tabs.
    • User will have the option to change the settings at the managed object level or at the template level.


Options “Apply changes to template <template name>” and “Apply changes on the managed object only” will be displayed on the pop up.

If the option “Apply changes to the template” is selected, the metric settings will be changed at the template level and the change is reflected for all the managed objects on which this template has been applied. The list of managed objects using the this template can be found on clicking the link “Show Managed objects where the changes take effect” next to the option “Apply changes to template <template name>”


If the option “Apply changes only on the managed object” is selected, changes made will be applicable only for the managed object.

 

Scenario 2– SAP template has been assigned to the managed object and the user would like to change the configuration of the metric from System Monitoring.

 

    • User will have the option to change the settings only at the managed object. Following pop up will be displayed, and the user should click on the “Apply Changes” button after making the specific settings on the pop up. The changes made for the metric will be at the managed object level.

10.png


    • If managed object specific settings are maintained for the metric already then user will have the option to change the settings only at the managed object only. Following pop up will be displayed and the user should click on the “Apply Changes” button after changing the settings on the pop up.

11.png

Make necessary changes and click on “Apply Changes” button. The changes made are applied only at the managed object level.

Clicking on the “Close” button without performing any action on the pop up cancels the operation.


 


This setting is global for all users!

 

1. Enter Workcenter "customizing mode"

 

Add "&sap-config-mode=X" to the end of the workcenter-URL:

 

Example:

ags_workcenter?sap-client=100&sap-language=DE&sap-config-mode=X

or

ags_workcenter?sap-config-mode=X



2. Right-click on one of the workcenter tab and select "Settings for current Configuration":

step2.png



3. Click on "Tabstrip Control"

step3.png


4. Click on "Re-Sort"

step4.png



5. Define the order of the tabs using the buttons "Up" and "Down"

step5.png

Hi to all,

during SUM deployment of SP01 of Solution Manage 7.2 I run in to problem where SUM process stopped in the process EHP_INCLUSION in the log file SPDA_EHP_INCLUSION.LOG you can find following line:

 

"2WETN607 The import of Prepackages is not allowed in this system"SAPK-74014INSAPGWFND""SAP_GWFND""740"Solman "

 

 

 

What you should do is following :

 

start the report RSSETPACKAGEDEPLOYMENT and put the following

 

for the Software component SAP_GWFND  :

 

- instead of T put P in the Maintenance  Type

 

sum_prob.jpg

 

I hope this was helpful!

ITSM & ChaRM – Reminder / Escalation emails using Date Management (Dates and Durations) Part 3

 

This is the continuation to the Part 1 and Part 2 blogs.

 

ITSM & ChaRM – Reminder / Escalation emails using Date Management (Dates and Durations) Part 1

 

ITSM & ChaRM – Reminder / Escalation emails using Date Management (Dates and Durations) Part 2

 

 

In this part, the Custom Duration field is made available in the Web UI configuration for the relevant document type.

The sample requirement discussed in Blog 1 and 2 is again used for Part 3.This is the sample requirement in context of Part 1/2 of the Blog –

 

When an Incident has been forwarded, the requirement is to send a Reminder/escalation email after a specific wait time if the Status is still unchanged.


 

 

Below are the Steps:


SPRO Configuration to enable the linking of the custom duration to the BTDateSET

blog-3-1.png

blog-3-2.png

 

 

Custom Enhancement has to be created for the Standard component (In my Case it is Incident) AIC_INCIDENT_H. This has to be done before proceeding with the required settings for the Custom Context nodes.

blog-3-3.png

**Refer the Blog by Harshit Kumar for completing the above step**

How To Enhance a Web UI Component in SAP CRM - CRM - SCN Wiki

 

blog-3-4.png

blog-3-5.png

 

Click Continue till reaching ‘Create Links to Custom Controller’ and then

 

blog-3-6.png

blog-3-7.png

 

The BOL relation as shown in the above screenshot is available only if it has been maintained in the SPRO as shown earlier in this document.

 

blog-3-8.png

 

 

The Superclass in the Context node’s Implementation class is changed to CL_CRM_UIU_BT_DATE_CN to handle dates.

blog-3-9.png

 

blog-3-10.png

 

Delete the Check for the errors (Remove the extra Base_Entity_Name attribute from the class) and activate.

blog-3-11.png

 

Log off and Logon to see the Attribute ‘Date’ available under the new custom node.

blog-3-12.png

 

**The Blog from Chand Shaik is used as the base reference for the next few steps**

Adding Date profile's Date type Fields as Context Attribute to the UI component

 

The below steps were done different from that of the blog to match to the DURATION specific requirement.

 

 

In the ‘ON_NEW_FOCUS’ method the replacement code was updated as below to refer the Z_FWDDURA duration created in SPRO date profile.

blog-3-13.png

blog-3-14.png

TIP : ***For Date, it is T and for duration, it is D for lv_category. The LV_date_type is the Date type or the Duration id defined in the Date Profile***

 

The GETTER and SETTER methods were activated for all the attributes below Date attribute (This may not be required- Did this as trial and error for getting troubleshooting ‘Not Bound’ text in the value of the field in the Web UI).

blog-3-15.png

blog-3-16.png

 

The Web UI configuration now will have the Custom node ZFWDDURA.

blog-3-17.png

blog-3-18.png

blog-3-19.png

 

<---------------End of the blog--------------->

Actions

Filter Blog

By author:
By date:
By tag: