This blog will explain the actions you need to perform to enable an ABAP backend for ABAP Eclipse tools (ADT = ABAP Development Tools).
Questions that will be answered are:
How to enable ABAP backend for ABAP Eclipse?
Where to find more background information on ADT (ABAP Development Tools)
For the installation of the front end tool ABAP Eclipse (ADT tools) read this blog.
Background information
The up-to-date information on the ABAP Development Tools and how to install ABAP Eclipse with the correct versions can be found on the SAP site. This site contains on the ABAP tab also the most up-to-date manual on the backend configuration.
The section below will describe the main steps.
Enabling ABAP backend for ABAP Eclipse
In transaction SICF enable node ADT:
Also activate the ABAP documentation tool nodes:
If not yet active, also activate SICF node wdy_aie_vd_preview.
Now start to test ABAP in Eclipse. Pending on the authorizations it might already work. If it does not work, check the standard SAP manual on the required RFC authorizations you need as ABAP developer to run ABAP in Eclipse.
In the manual you will read about SFW5 switch SRIS_SOURCE_SEARCH. Be very careful to switch this on. It is very resource intensive and there is limited added value.
Bug fix OSS notes
There might be bugs in Eclipse backend code. In SAP OSS search for component BC-DWB-AIE.
In S4HANA the SSCR and developer key procedure are no longer present. This means you have to use proper authorization concept to determine which person is allowed to developer Z ABAP code and which developer is allowed to modify standard SAP ABAP code.
Questions that will be answered in this blog are:
Why has the has the procedure been removed?
How do I protect code adjustments from unauthorized changes?
S4HANA developer key
The title is a bit misleading. In S4HANA there are no developer keys and object keys any more.
So in S4HANA, you must set up authorizations for S_DEVELOP properly. The development key and SSCR procedure are hacked anyhow (see blog).
With S_DEVELOP you have to set create/change rights for the packages and or objects. For custom code only hand out Z* privileges.
If you hand out a * for the objects or classes, then the developer can also change standard SAP.
Changes to standard SAP in S4HANA
The SCCR procedure is gone in S4HANA. This means if you want to adjust standard SAP code and you have the authorizations, you can without any SSCR screen asking you for the modification key.
Again also here: i you hand out a * for the objects or classes, then the developer can also change standard SAP.
All protection of ABAP code in S4HANA is arranged via authorization.
Developer license measurement in S4HANA
The move away from DEVACCESS has also made the developer license measurement in S4HANA complex. Read more in this blog.
With the new S4HANA custom code migration FIORI app you can include system usage data (from productive system) to see which code blocks are used and which ones are not.
This blog will give answers to the following questions:
How to collect usage data from productive system?
How to include the usage data in the S4HANA custom code migration FIORI app?
This blog assumes you have already setup the S4HANA custom code migration FIORI app. If you have not done this, follow the instructions in this blog.
Collecting usage data in production with transaction SUSG
If SUSG does not start in your productive system it needs to be installed first. To install SUSG apply OSS note 2643357 – Installation of Transaction SUSG. This is a TCI based OSS note (see blog).
Now that the data collection and aggregation is activated, you will need to be patient. Let the system collect the data for the next few days. Now go to transaction SUSG and check the log that the aggregation went fine:
Now you can create a snapshot in the Manage Snapshots section:
Create the snapshot and download it to a file on your desktop or laptop. If wanted you can setup RFC connection as well.
The security and basis team normally does not like any RFC going from production system to non-production system. So the file option is normally the best way.
Loading the data into your upgraded S4HANA system
In your S4HANA system where your custom code analysis runs now start transaction SUSG and make sure it is active. Now you can upload the snapshot from the productive server you have downloaded in the previous step.
Please make sure that the OSS notes on both your productive system and your S4HANA system are identical. The notes have changes to file format of the download file. If the notes are notes identically applied, you will have file format upload issues. Recommendation is to apply all recent SUSG note to both your productive server and the S4HANA system.
S4HANA custom code migration app with usage data
Now you can finally launch the S4HANA custom code migration app. Create a new analysis. In the usage data part of the app, you can assign the snapshot you have uploaded in the previous section:
Now start the custom code analysis and let it run.
The end results of code being used or not can be seen in the column Usage Information in the Analyze Findings section:
If you have followed all the instruction in the blog about embedded FIORI activation in S4HANA, you will find that the my Inbox app is still not working.
This is correct since extra steps are required to setup the FIOIR my inbox app. This blog will answer the following questions:
Which extra steps to perform to activate the FIORI my inbox app?
Where to find more background information on the FIORI my inbox app?
Now setup an extra system alias, name can be freely chosen:
It is very important here to notice 2 things:
The local GW (gateway) tickbox must be set
The software version MUST be set to /IWPGW/BWF
In transaction /IWFND/MAINT_SERVICE activate the service TASKPROCESSING version 2 for the system alias you just created.
It is very important to take version 2 and not the version 1.
In SICF activate the FIORI inbox tile itself: CA_FIORI_INBOX.
In PFCG activate role SAP_BR_MANAGER and assign it to your user.
MyInbox app
Now goto the FIORI launchpad (/ui2/flp transaction) and the MyInbox tile should be visible with the number showing you the amount of workflows:
If you see the number zero, you might not have any workflows assigned to your user. See the blog on S4HANA workflow activation to make sure the workflow system is properly activated and instruction to generate some test items for you.
When you have installed and activated SAP enqueue server 2 (this will happen when you move to S4HANA), the transaction SMENQ is available to manage lock entries. This replaces transaction SM12.
Questions that will be answered in this blog are:
Where to find more information on SAP enqueue server 2?
What are the new functions in SMENQ?
How to solve lock overflow issues?
SMENQ transaction
When you start SM12 you see that a new button SMENQ is available if you have activated SAP enqueue server 2:
You can enter this way, or directly via transaction SMENQ:
From the start screen you can search for locks, just like SM12 can. The new functions are in the Server Administration button.
Enqueue server administration
From the start screen of SMENQ goto the Server Administration:
Now you can launch a lot of tool.
Interesting tool is the Functional Tests tool to quickly check the correct functionality of the enqueue server to be fully working:
This blog will explain how to activate workflow in S4HANA. If you have to activate workflow in classic ECC system use this blog.
Questions that will be answered in this blog are:
How to activate workflow in S4HANA?
What do I need to do with the workflow activation in case of an upgrade to S4HANA?
Where to find more background information on workflow activation in S4HANA?
Why is WF-BATCH replaced with SAP_WFRT user?
Workflow activation in S4HANA
First make sure you have created system user SAP_WFRT. Start with assigning SAP_ALL to this user. You can replace it with lower rights after the activation is done properly according to OSS note 1574002 – WF-BATCH and SAP_WFRT Authorizations.
Start transaction SWU3:
Select the Edit Runtime Environment and press the button Execute Activity. This will activate all the actions below.
After it is done you can press the button Start Verification Workflow to check if the workflow runs properly. After 1 minute (it needs compilation in the background) start transaction SBWP.
If the lights are not green and/or the workflow verification is not ok: the basis setup is NOT ok. Investigate and fix.
Transaction RSTCO_ADMIN: this one might not have gone right.
Re-install the content if required.
In case of issues with BGRFC supervisor destination: Use transaction code SBGRFCCONF and check the last tab that the supervisor destination is assigned. In systems with CUA there might be an issue with creating the supervisor destination. In this case follow the steps of OSS note 2775490 – Error in customizing while creating supervisor destination.
In SJOBREPO, more background information can be found by clicking the button Monitor help:
A very important remark is made here that it can take up to 1 hour before changes to SJOBREPO are visible in the monitoring overview. This is a very annoying feature.
This blog will describe the steps in activating search in S4HANA. We will explain both new fresh installation and upgrade from system which has search already activated.
Questions that will be answered in this blog are:
How to activate search in S4HANA for an initial installation?
How to activate search in S4HANA after upgrade when search was already active?
Activating search in S4HANA new installation
To activate search goto transaction STC01 and select task list SAP_ESH_INITIAL_SETUP_WRK_CLIENT:
Open the details:
Make sure that you set the TREX destination to SAP HANA DB:
Then select the search model. For most use cases this will be SAPAPPLH:
Now run the task list and be patient. This can take quite some time. If the task list finishes correctly start transaction ESH_COCKPIT to check that all search connectors are correctly activated.
Search after upgrade to S4HANA
If you upgrade your existing system and have search already active, you get this message after launching ESH_COCKPIT:
Run report ESH_CDSABAP_ACTIVATION with default parameters:
This might be a long run:
If you run into issues, check that the following OSS notes are applied:
Next step: in transaction PFCG create a new role (for example Z_CUSTOM_CODE_APP). Add catalog SAP_BASIS_TCR_T as a launchpad catalog:
Save and activate the role. Assign the users to the role.
In transaction /IWFND/MAINT_SERVICE add the following services (and activate them):
Component
External
Technical Name
Custom
code migration projects
SYCM_APS_C_PROJECT_CDS
Analysis
of SAP S/4HANA custom code check findings
SYCM_APS_C_ATC_FIND_ALP_CDS
Custom
code scoping by request entry points
SYCM_APS_C_SCP_BY_EP_CDS
Custom
code scoping by packages
SYCM_APS_C_SCP_BY_PK_CDS
In transaction SICF activate the following nodes:
NW_APS_CCM_PRJ
NW_APS_EXT_LIB
NW_APS_LIB
The core activation actions are now done.
Start transaction /UI2/FLP to start the FIORI launchpad. You will not find the tile. Change the homepage and add the following tile from the catalog:
Before starting, make also sure that in ATC setup the RFC object providers are setup:
You can name the ID, description and group ID the same if you want. Make sure to use RFC destination none.
Creating a project in the app
Now you can start creating a project in the app. Click on the + symbol to add a project;
In the destination fill out the system you have put into the ATC object provider configuration. Than save the project and let it run. In the background the full ATC check is now carried out. This can take some time. You can refresh the project to see the status:
Scoping the results
In the scope block you can exclude packages by clicking on the Change scope button:
Packages that might be excluded:
Z packages from SAP
Z packages from 3rd party tools
Analyzing the results
When the run is done, you can now analyze the results on the Analysis tab:
A bit below on the Analysis tab is the burn down chart:
For the burn down chart you need to run the custom code run again on several days. Check for tool issues and solve them. Solving tool issues makes the amount of issues go up as you can see on the sample screen above.
Important here is that you have to press the Analyze Findings button to go into the detailed analysis overview:
On the top are the graphical overviews. In the bottom is the detailed list:
You can use the download to excel button for further processing.
During the custom code clean up you can redo the same project, by rerunning the analysis. Or you can decide to run a new project.
