SAP Focused Run offers some nice API’s that you can use and re-use.
API’s available:
LMDB API
Work mode management API
Guided procedure API
Advanced analytics API
LMDB API
The LMDB now has a REST API available to read data in structured way. You can search for hosts, technical systems, software components, installed product versions and instances.
The full specification for this API can be found on this link.
Ad hoc work mode creation via function module
Via function module FM_START_ADHOC_WORKMODE you can create an ad-hoc work mode to stop monitoring for a system. You can start monitoring again by stopping the work mode by calling function module FM_STOP_ADHOC_WORKMODE.
Function module FM_EXTRN_GP_EXEC can be used to call a guided procedure. Unfortunately, you need to pass the GUID of the guided procedure to the function module.
In some cases you need to debug the session of another user. This can be needed for example when you need to solve an issue in ABAP for a FIORI app. The end user is doing his work until the break point is reached. Then you take over the session using the normal debugging tools. The basic principle is explained in OSS note 1919888 – Debugging the applications of another user, and in this SAP help file.
Follow the steps explained in this blog to set up a new custom check. We will use these steps to set up an extra SCI class to check if the AUTHORITY-CHECK statement is added in ABAP code or not.
New SCI check coding
Step 1: create the ZCL_CI_SCAN_AUTH class
In SE24 copy class CL_CI_TEST_FREE_SEARCH to ZCL_CI_SCAN_AUTH. In the attributes of the copied class set C_MY_NAME as variable to ‘ZCL_CI_SCAN_AUTH’. Also set the error code MCODE_0001 to ‘Z001’.
Step 2: redo the CONSTRUCTOR
Goto the constructor of the new class and overwrite the existing code with this code snippit:
In some cases you might be asked on the SAP menu. How it is build up, which transaction codes are in there, who is using SAP menu, and how is using the company created menu. And other questions.
From the note: “Through the Compatibility Packages (CP) listed in the attachment “Compatibility Scope Matrix”, SAP provides a limited use right to SAP S/4HANA on-premise customers to run certain classic SAP ERP solutions on their SAP S/4HANA installation. Condition is that these customers have licensed the applicable solutions as set forth in their License Agreements. Compatibility Pack use rights may apply to selected private cloud deployments as well, without the prerequisite of an on-premise classic license.”.
Basically it means SAP did not have time enough to redo all the old solutions for S4HANA, but reserved the rights to do so later.
In the first years of S4HANA this did not used to be a big issue. Now SAP is catching up and will remove compatibility functions in upcoming versions, or will stop support.
Next steps
What do you need to do:
Check if you have any systems with this alert in your EWA. The EWA is detecting this based on system usage/configuration settings.
Determine the impact of the note for your situation with both the functional team and your management (since it can have license impact as well)
Create action plan for your situation
Since the compatibility packs are coming from diverse functional background with diverse solution routes, there is no generic advice possible.
Except one advice: don't ignore this alert, but pick it up seriously. Investigate and take appropriate action in time to avoid license rights discussions and/or support issues.
The snoozing is a very useful function. For example, you detect a red alert on HANA revision, but it will take you a month to implement (due to regression testing, process, etc), you can now snooze the alert for the implementation period:
After the implementation is done, the alert should be gone. If the implementation is delayed, you will be reminded again.