saptechnicalguru – Saptechnicalguru.com

Tables in SAP basis area

As basis you are sometimes confronted with special requests. For these special requests, you will need to know for part SAP uses which tables so you can use SE16N for internal lookup of information.

The below is a list of tables used in SAP basis.

Disclaimer 1: table list is not complete.

Disclaimer 2: tables can change each SAP version.

SAP mail / SCOT

BCSD_BLMODULE
BCSD_BREAKLOOP
BCSD_RQST
BCSD_STML
SXADMINTAB
SXCONVERT
SXCONVERT2
SXCOS
SXCOS_T
SXCPDEF
SXCPRECV
SXCPSEND
SXDEVTYPE
SXDEVTYPL
SXDOMAINS
SXJOBS
SXNODES
SXPARAMS
SXRETRY
SXROUTE
SXSERV
SXTELMOIN
SXTELMOOUT

USMM user management

TUAB_ANNOTATION
TUAB_WF_TYPE
TUAB_WF_TYPE_T
TUAPP
TUAPPT
TUAPUSG
TUCON
TUGRP
TUJOB
TUL_AC_UNIT
TUL_AC_UNITT
TUL_ACRES
TUL_ACTTC
TUL_CLIENTS
TUL_CONTROL
TUL_CPU
TUL_CPU_RAW
TUL_ENG_PL
TUL_ENG_PROT
TUL_ENG_RESULT
TUL_ENG_RESULT_1
TUL_ENGINES
TUL_ENGINEST
TUL_JOB
TUL_MEMOS
TUL_MSG
TUL_TRANS
TUL_TRSTAT
TUL_UNIT
TUL_UNITT
TULAPP_PL
TULTRANS
TUMRES
TUMSG
TUPL
TUPLT
TUPRO
TUSERSETTING
TUSERSETTINGPROD
TUSTAT
TUTYHLP
TUTYP
TUTYPA
TUTYPASYS
TUTYPNOWSYS
TUTYPP
TUTYPPL
TUZUSSYS

STMS transports and settings

TMSBCIBOX
TMSBCIIBOX
TMSBCIJOY
TMSBCINEX
TMSBCINTAB
TMSBCIOBJ
TMSBCIXBOX
TMSCDES
TMSCDES_S
TMSCDESD
TMSCDIST
TMSCDOL
TMSCDOM
TMSCDOMT
TMSCNFS
TMSCNFST
TMSCROUTE
TMSCSYS
TMSCSYST
TMSCTOK
TMSFSYSH
TMSFSYSL
TMSMCONF
TMSPCONF
TMSPVERS
TMSSRV
TMSTCRI
TMSTLOCKP
TMSTLOCKR
TMSTOUT
TMSUCONF

E070L

E071

E071K

STMS History

TMSQLASTWL
TMSQNOTES
TMSQNOTESH
TMSQWL
TMSQWLF
TMSQWLFH
TMSQWLH

Database connections

DBCON

DBCONUSR

Files

FILENAME
FILENAMECI
FILEPATH
FILESYS
FILETEXT
FILETEXTCI
OPSYSTEM
OPTEXT
PARAMVALUE
PATH
PATHTEXT
USER_DIR

STRUST settings

SSF_PSE_D
SSF_PSE_H
SSF_PSE_T
SSFAPPLICT
SSFARGS
STRUSTCAB
STRUSTCERT
STRUSTCRL
STRUSTCRP
STRUSTCRPT
STRUSTCRR
STRUSTCRRT
STRUSTCRS
STRUSTCRT
STRUSTSSL
STRUSTSSLT
STRUSTWSSE
STRUSTWSSET
TWPSSO2ACL
USERINFO_STORAGE
USRACLEXT
USRCERTMAP
USRCERTRULE

Content server and SAP DMS settings

CREP_FTP
CREP_RPC
CREP
CREP_FILE
CREP_HTTP
CREP_LREP
CREP_R3DB
CREP_RFC
CREP_TREE
CREPDESCR
CREPDOCSP

SWU3 workflow settings

SWFGPACTIVITIES
SWFGPCONF
SWFGPDEPLOY
SWFGPGENOBJNUM
SWFGPREUSE
SWFGPROLEDEF
SWFGPROLEINST
SWFGPWULACDEF
SWFGPWULDATOBJ
SWFGPWULFLOWS
SWFGPWULTASKS

Classic TVARV

TVARUVN
TVARV
TVARVC

SICF nodes

ICF_SESSION_CNTL
ICFALIAS
ICFAPPLICATION
ICFBUFFER
ICFDELTA
ICFDOCU
ICFHANDLER
ICFHANDTREE
ICFIMPORT
ICFINSTACT
ICFLOGORDER
ICFNOHANLDER
ICFSECPASSWD
ICFSERVICE
ICFSERVLOC
ICFVIRHOST

Start menu settings

SSM_CUST

Webservices logical ports & soap runtime

SRT_LP
SRT_LP_FEAT
SRT_LP_OP_FEAT
SRT_LP_SXI_ADDR
SRT_LP_T

SPROXMSGREL
SRT_SLT_HOSTS
SRT_ASSIGN_DATA
SRT_ASSIGN_DIR
SRT_ASSIGN_DIR_T
SRT_AU_TEST_RECI
SRT_CACHE
SRT_CC_CHANGES
SRT_CC_CHANGES_H
SRT_CC_MIF_CDATA
SRT_CC_MIF_CDIR
SRT_CC_MIF_LDATA
SRT_CC_PC
SRT_CC_PP
SRT_CC_ST_ACT
SRT_CSTC
SRT_CDTC_C_DET
SRT_CDTC_CHD_ID
SRT_CDTC_DESCR_T
SRT_CDTC_G_DET
SRT_CDTC_S_DET
SRT_CFG_BNDG
SRT_CFG_CFGVAL
SRT_CFG_CHG_TAB
SRT_CFG_CLI_ASGN
SRT_CFG_DATA
SRT_CFG_DEF_ASGN
SRT_CFG_DIR
SRT_CFG_DIR_T
SRT_CFG_ICF_DET
SRT_CGF_ICF_USE
SRT_CFG_LOG_HDR
SRT_CFG_LOG_ITEM
SRT_CFG_LOG_SRCH
SRT_CFG_MLP_DATA
SRT_CFG_SRV_ASGN
SRT_CFG_STS_ASGN
SRT_CFG_SV_ASN_T
SRT_CFG_TPLC_DAT
SRT_CFG_TPLC_DIR
SRT_CFG_TRC
SRT_CFG_TRC_ADM
SRT_CFG_VAL_DET
SRT_CFG_VAL_DIR
SRT_CFG_VAL_UPD
SRT_CFG_VALUES
SRT_CG_SYST_ATTR
SRT_CG_SYST_DIR
SRT_CG_WSDL_CONT
SRT_CG_WSDL_URL
SRT_CHECK_HEADER
SRT_CHECK_RESULT
SRT_CHECK_STATUS
SRT_CLI_NR
SRT_CNTRL_TASKS
SRT_CON_SYSTEMS
SRT_CTRL_TSK_MSG
SRT_DEST_CFGV
SRT_DEST_DATA
SRT_DEST_DIR
SRT_DEST_DIR_T
SRT_DEST_DIR_V
SRT_DEST_WSDL
SRT_DOMAIN_SYS
SRT_DOMAIN_SYS_T
SRT_DOMN_DIR
SRT_DOMN_DIR_T
SRT_DOMN_SYSTS
SRT_DT_CFG_DATA
SRT_DT_CFG_DIR
SRT_DT_CFG_DIR_T
SRT_DT_CHG_DIR
SRT_DT_CHG_DIR_L
SRT_DT_CHG_STAT
SRT_DT_CHG_STATL
SRT_FALLBACK_LPS
SRT_FW_SETTINGS
SRT_GEN_CLNT_DIR
SRT_IDENTIFIER
SRT_ISO_SET_C
SRT_ISO_SET_P
SRT_LOG_TENANT
SRT_LOG_TENANT_R
SRT_LP
SRT_LP_FEAT
SRT_LP_OP_FEAT
SRT_LP_SXI_ADDR
SRT_LP_T
SRT_LP_URL_ASGN
SRT_LRD_HEADER
SRT_LRD_ROUTING
SRT_MED_SYS
SRT_MED_SYS_T
SRT_MIG_HIST
SRT_NAME_CACHE
SRT_OBSERV_DATA
SRT_PEND_TASK
SRT_PRF_CFG_DIR
SRT_PRF_CFGVAL
SRT_PRF_DATA
SRT_PRF_DIR
SRT_PRE_DIR_T
SRT_PRE_DIR_V
SRT_PRO_WKL
SRT_PROF_ASSIGN
SRT_PRULE_ASSIGN
SRT_PRULE_DATA
SRT_PRULE_DIR
SRT_PRX_CLNT_DIR
SRT_PRX_EX_CHECK
SRT_PT_INDEX
SRT_PX_MSG_ASGN
SRT_REG_ADRMAP
SRT_REG_BACKUPR
SRT_REG_BIND
SRT_REG_CONFIG
SRT_REG_OPERAT
SRT_REGISTRY
SRT_REGISTRYT
SRT_REQ_DATA_C
SRT_REQ_DATA_CON
SRT_REQ_DATA_P
SRT_REQ_DATA_PIF
SRT_REQ_DATA_PRO
SRT_REQ_DIR
SRT_REQ_DIR_T
SRT_REV_PROXY
SRT_RTC_BNDG
SRT_RTC_CFGVAL
SRT_RTC_CG_DATA
SRT_RTC_CG_DATAL
SRT_RTC_CG_DIR
SRT_RTC_DATA
SRT_RTC_DATA_RT
SRT_RTC_DATAL
SRT_RTC_DIR
SRT_RTC_DT_IF_SD
SRT_RTC_DT_RT
SRT_RTC_DT_RT_MD
SRT_RTC_WSIL
SRT_RTC_WSILL
SRT_SAVED_SEARCH
SRT_SCP_ASSIGN
SRT_SDN_URL_C
SRT_SECSTORE_LNK
SRT_SOAM_CONNECT
SRT_SR_CLASS_S_T
SRT_SR_CLASS_SYS
SRT_SR_CLASS_V_T
SRT_SR_CLASS_VAL
SRT_SR_SEP
SRT_SR_SEP_T
SRT_SR_SYSTEM
SRT_SR_UDDI_ROW
SRT_SR_VW_ASSIGN
SRT_SR_VM_DETAIL
SRT_SR_VM_HEADER
SRT_SR_WSD
SRT_SR_WSD_T
SRT_ST_ACT_A
SRT_ST_ACT_C
SRT_ST_ACT_C_C
SRT_ST_ACT_P
SRT_ST_ACT_P_C
SRT_ST_REQ_A
SRT_ST_REQ_C
SRT_ST_REQ_P
SRT_SYS_NR
SRT_SYS_SETTINGS
SRT_SYST_APPL
SRT_SYST_APPL_HT
SRT_SYST_CL_DATA
SRT_SYST_CL_DIR
SRT_SYSTEM_DIR
SRT_TEST_CONCATE
SRT_TMP_CG_DATA
SRT_TMP_CG_DATAL
SRT_TRACE_USERS
SRT_TRANSP
SRT_TRANSP_A
SRT_TRANSP_KEYS
SRT_TRC_ASSIGN
SRT_TRC_COUNTER
SRT_TRC_FILES
SRT_U_ASSIGN_DAT
SRT_U_ASSIGN_DIR
SRT_UASSIGN_DIR
SRT_USER_DATA
SRT_USER_DIR
SRT_USER_DIR_T
SRT_WHITE_LIST
SRT_WSDL_CACHE_P
SRT_WSDL_DIR
SRT_WSDL_DIR_T
SRT_WSDL_DS_ASGN
SRT_WSDL_ENTITY
SRT_WSIL_CACHE_C
SRT_WSIL_CACHE_P
SRT_WSIL_TMP
SRT_WSP_WSDL_FLA
SRTFT_ASSIGN
SRTFT_ASSIGN_IF
SRTFT_ASSIGN_SEC
SRTFT_NM_CFG_MAP
SRTFT_QDATA_LOG
SRTFT_QUEUE
SRTFT_QUEUE_DATA
SRTFT_QUEUE_LG_T
SRTFT_QUEUE_LOG

Content server settings

CREP_FTP
CREP_RPC
CREP
CREP_FILE
CREP_HTTP
CREP_LREP
CREP_R3DB
CREP_RFC
CREP_TREE
CREPDESCR
CREPDOCSP

Idoc settings WE20, WE21

EDMA
EDP12
EDP13
EDP21
EDPP1
EDIPO
EDIPO2
EDIPOA
EDIPOD
EDIPOF
EDIPOI
EDIPORT
EDIPOX
EDIPOXH

SAP license key

SAPLIKEY

OS commands SM49, SM69

SXPGCOSTAB
SXPGCOTABE
SXPGHISTOR

SNC

SNCSYSACL

TXCOMSECU
USRACL
TSP0U

RFC’s SM59

RFCTA
RFCTYPE
RFCLIST
RFC_TT_ACL
RFCATTRIB
RFCCBWHITELIST
RFCCHECK
RFCCMC
RFCDES
RFCDESSECU
RFCDOC
RFCGO
RFCSTXTAB
RFCSYSACL
RFCSYSACL_CLNT
RFCTRUST

ALE distribution model BD64

TBDLI
TBDLS
TBDLST
TBDLT
TBDBR
TBDBRF
TBDA2
TBD00
TBD00T
TBD03
TBD05
TBD06
TBD20
TBD30
TBDTPBDF
TBDTPBR
TBDTPMD

TBLSYSDEST
TBSPECDEST

ALV grids

LTDX
LTDXD
LTDXT

Secstore

RSECACHK
RSECACTB
RSECSESSION_CL
RSECTAB
RSECVAL
RSECVAL_CL

Spools and printers

TSP03
TSP03A
TSP03C
TSP03D
TSP03L
TSP03POCCNF
TSP03POCPRE
TSP03T
TSPCMDS
TSPLOMS
TSPROMS
TSPSV

User menu

SMEN_BUFFC

SLT data replication tips and tricks

SAP SLT server can be used to replicate data from SAP system to a target system. In this blog we will not discuss if it is a good or bad architecture to replicate source data directly or not. Focus is on the technical setup and operation of the SAP SLT server for data replication.

SAP references

Help.sap.com reference for SLT can be found here.

SLT performance optimization guide can be found here.

SAP learning on SLT can be found here.

DMIS plugin updates in source and replication server

For replication to work properly, do regularly update the DMIS plugin in both source and replication server. Since S4HANA DMIS is integrated into the core: 2572945 – DMIS compatibility with SAP S/4HANA.

The OSS notes for SLT must be updated on both source and replication server. Read more in this blog.

SLT monitoring

Monitoring is described in OSS note 2008039 – How to monitor the replication process – SLT.

Make sure job /1LT/IUC_HEALTH_C with program R_DMC_HC_RUN_CHECKS runs.

SAP Focused Run has special tools for monitoring SLT. Read more in this blog.

ZDO upgrades and SLT

If you are running SLT and want to use ZDO upgrade, please be aware they use very similar technology. When performing ZDO upgrade when SLT is running, do take the proper upgrade path including SLT.

Change data capture

DHCDCMON (CDS View Replication Monitor) is the monitoring transaction for the SAP Change Data Capture (CDC) framework used by ABAP CDS-based data replication.

SAP has developed a stability contract concept and an annotation that marks CDS Views as extraction enabled, and SAP commits to keep these CDS Views Stable and compatible (or replace them by compatible views, once the original ones get deprecated).

Call CL_DD_RTOBJ_FACTORY=>READ_ACTIVE_RTOBJ( name_of_your_cds_view ). You will get an object offering the method IF_DD_RTOBJ_TBFUNCDEP_SOURCE~GET_TABLE_FUNC_DEPENDENCIES( ). The returned table contains a list of AMDPs that might be called when using the CDS View is used. This list does contain only the AMDPs directly called from the CDS artefacts, but not AMDPs called by the listed AMDPs. If the list is empty, you are safe that no AMDP is called.

Data migration cockpit interference

The new SAP data migration cockpit will use, for some use cases, the DMIS component as well. See S4HANA migration cockpit as successor of LSMW – Saptechnicalguru.com and Setting up SAP S/4 HANA FIORI Migrate Your Data – … – SAP Community.

If you get into issues, check these OSS notes:

OSS notes

Trouble shooting OSS notes:

Functionality related OSS notes:

SAM4U: Software Asset Manager

SAP has released the SAM4U tool to manager your software licenses for SAP. This tool is especially useful in large SAP landscapes.

The SAM4U tool helps you to optimize the licenses. It does not replace the formal license submission tool SLAW2.

Benefits of SAM4U

Improved SAP license cost control
SAM4U continuously analyzes actual SAP usage and compares it with purchased license entitlements. It helps identify: over-licensed users, under-licensed users, users automatically classified into expensive license categories.
Opportunities to reduce license costs through reclassification.
Proactive audit readiness
Instead of waiting for an SAP audit: License consumption is continuously monitored. Compliance gaps become visible early. Entitlements and usage are maintained in one place. This reduces surprises during SAP license audits.
Consolidated View Across Multiple SAP Systems

Usage data from ECC, S/4HANA and other ABAP systems is consolidated. License consumption is tracked centrally. Landscape-wide reporting becomes possible.

User classification optimization

SAM4U analyzes: actual usage, authorizations, assigned roles.

It highlights users who may be consuming more expensive license types than necessary and suggests optimization opportunities.

Authorization analysis

The tool provides: current vs. target user classifications, detailed authorization object analysis, role and profile impact assessments.

This is useful for Basis, Security, and GRC teams performing role redesign or license optimization exercises.

Transaction usage analysis

SAM4U tracks: active user behavior, transaction code usage, historical activity.

Transaction analysis can be leveraged for authorization role redesign.

SAP HANA consumption insights

SAM4U includes: historical HANA memory consumption, database growth trends, HANA enterprise edition analytics. This gives visibility into HANA utilization over time.

Simulation capability

According to the SAM4U user guide, the tool can simulate: changes to roles
changes to authorizations, impact on required license quantities.

This allows “what-if” analysis before implementing role changes.

No data leaves the customer network

License data remains inside the customer’s environment. SAP does not receive operational usage data through SAM4U. This addresses common security and confidentiality concerns.

No additional license cost. SAM4U tool is free of charge.

Time to implement the tool is not for free.

Set up of SAM4U

The setup of the SAM4U tool is clearly described on the SAP help file for SAM4U. SAP also offers help with a service to implement the tool on their SAM4U site.

Central installation

The first part is the installation of the central tool on the central system.

Choose a system with a high S4HANA version. Do not use SAP solution manager.

First make sure on the central system the bug fix notes listed in 3646933 – SAM4U Solution | Fiori Application | V2 are applied. And apply the notes for 3292019 – SAM4U Data Extractor.

Once done goto the installation and upgrade part of the SAP help file for SAM4U:

F0llow all the steps:

Hints: the first 2 steps are confusing. It tells you to start transaction /n/SAM4U/START, but that only works when step 2 is done, where you create the actual start variant.

After completing all the steps when starting transaction /n/SAM4U/START the FIORI page should launch:

Connecting the SAP systems

Per SAP system you want to connect, first apply the notes for 3292019 – SAM4U Data Extractor. The per connected system follow the steps in the SAP help file for SAM4U for the Data Extractor Guide:

Choose between RFC based or file based data extraction. Important in both cases to give the user ID’s the appropriate authorizations as described in both Required Authorizations section as in the Data Gathering section. Make sure the data extractor job runs regularly.

The data of the extractors is stored in table /SAM4U/BEXDUSE. Looking at the content of this table as basis person can also help you to get insights into how end users are using the system. You can find transaction start, but also Remote Function calls.

Administration of systems

Before usage you must administer all your systems in the solution. This part is explained in the SAP help file for SAM4U:

After setting up the proper authorizations go to the Administration section:

In the SAM4U tool add the system by clicking the + sign:

In the popup that comes select the RFC you created from the central system to the backend system. Make sure the user in your RFC has the rights to run and read the SAM4U tables, and has the rights to run the SAM4U RFC modules. If the rights are not ok, the tool will make the connection Red (without further detail). To get the details of what is missing in the target system role, run an ST01 or STAUTHTRACE in the target system for the user ID used in the RFC.

First do one system to test the entire function. When you are happy, repeat for all backend systems.

Next step is to download the ruleset xls which is attached to OSS note 3113382 – Authorization-based SAP S/4HANA User Simulation / FUE Projection. Upload the downloaded xls with the Upload button:

Next step is to download License Entitlement file from me.sap.com. Instructions are given on top. Use the upload button to upload the file:

Running the tool

On the landscape tab run the tool per landscape to gather the data, by pressing the Go button:

Wait until the results are done.

Go to the Consolidation tab and create a consolidation and execute it:

Now the data sections in the Analytics and License entitlement are visible with the data:

For all the functions here, the SAP help file for SAM4U links is excellent to explain the details:

OSS notes and SAP references

If you need bug fix notes search on me.sap.com with the term SAM4U.

Link to the official SAM4U marketing. Small and simple blog on SAM4U.

Link to the YouTube explanation of SAM4U.

SAP GUI 8.10

SAP GUI 8.10 is released now and is supported until 30.06.2029. The first patch level is also release. Future patch levels are published in OSS note 1053737 – Expected release dates for SAP GUI for Windows. PL2 for SAP GUI 8.10 is scheduled for October 2026.

The old SAP GUI 8.00 is supported until 31.07.2027.

General SAP GUI 8.10 help file reference; link. SAP blog page: link.

SAP GUI 8.10 changes

All formal changes are list in OSS note 3549180 – New and changed features in SAP GUI for Windows 8.10.

Caching: 3579956 – Download and caching of multiple types of remote configuration files as of SAP GUI for Windows 8.10.

Custom theming

SAP GUI 8.10 allows custom theming. If you want to use it read the corresponding SAP help file.

32 vs 64 bit

Both are still supported, but only 1 per pc / laptop. See this blog.

Bex components

Bex components are removed from the default SAP GUI 8.10 build. If still needed, read OSS note 3691456 – SAP BW Business Explorer 7.x is no longer included with SAP GUI for Windows 8.10 DVD compilation and must be installed separately.

SAP script components

Some older systems and users might still require SAP script legacy editor: 2221815 – SAPscript Legacy Text Editor controls are not packed in SAP Windows GUI Installation.

Detecting unencrypted GUI and RFC traffic

When protecting SAP landscape with SCN encryption on GUI and RFC, there are 2 parameters that can block all not-encrypted traffic: snc/only_encrypted_rfc and snc/only_encrypted_gui.

Before setting these parameters, you first want to know which interfaces and GUI connections.

Logging settings

To enable the logging, setup in SAP audit log transaction SM20 (or RSAU_CONFIG) the BUJ event for non-encrypted communication:

Next to this set RZ10 parameter snc/log_unencrypted_rfc to value 2 to also log the unencrypted RFC’s.

Warning: if you have many RFC's and start to encrypt them, this event can generate massive amounts of logging. Consider to switch on temporarily to log limited amount of time to get the first work list.

Audit log results for unencrypted RFC and GUI

Use transaction SM20 or RSAU_READ_LOG and select event BUJ.

Unencrypted RFC looks like this for ABAP to ABAP:

And for external RFC to ABAP:

In the details you can find the source IP address.

Unencrypted GUI usage looks like this:

In the Terminal Name column you can find the desktop/laptop of the user still using unencrypted GUI.

SAP Router tips and tricks

This blog will give tips and tricks on SAP Router.

SAP router versions and maintenance can be found in this OSS note: 1897597 – SAProuter: Release rollout.

OSS note 1895350 – Secure configuration of SAProuter covers the security aspects of SAP router. To store encrypted passwords in SAP Router, follow the instructions of OSS note 2046942 – Support encrypted passwords in saprouttab.

SAP router documentation is listed in OSS note 30289 – SAProuter documentation. Public documentation of SAProuter. Help link on help.sap.com on SAP router.

For trouble shooting network issues, follow the instructions in OSS note 1227116 – Creating network traces.

In case you need reverse invoke of the SAP router follow the instructions from this help.sap.com link.

Support backbone configuration

The support backbone configuration is explained in OSS note 2827658 – Automated Configuration of new Support Backbone Communication – Update 02. STC01 task list SAP_BASIS_CONFIG_OSS_COMM can be used to speed up the setup:

When switching SAP router:

Update the SOAMANAGER Consumer Proxy CO_CLS_SCWN__SVT__SNO_ANST_SEA to point to the new SAP Router hostname.
Update the RFC Destination SAP-SUPPORT_PORTAL to point to the new SAP Router hostname.
Update the RFC Destination SAP-SUPPORT_NOTE_DOWNLOAD to point to the new SAP Router hostname.

OSS notes:

Performance monitoring for http(s) and ODATA

You can setup detailed performance monitoring for HTTPs and ODATA calls to show this information in ST03 workload monitoring.

Setup

Run program SWNC_CONFIG_URL and change the settings:

Background OSS note: 2093522 – ST03 Profiles do not show full information (compressed data). This note also warns that for very large volume there might be issues with the data collection. Solution for that issue is explained in OSS note 2059569 – Runtime error EXPORT_TOO_MUCH_DATA when saving statistic data aggregates.

With report SWNC_CONFIG_PATH you can reduce the path in the recording. See also OSS notes 2285159 – ST03n: Normalization of background job names and URLs in VC/WM profiles and 3070839 – MON-TUN: Extension of length and starting Position for the Normalization of URLs. By doing this, you get more aggregation and also less issues: 3297874 – How to improve the performance of transaction ST03/ST03N on systems with high http(s) workload.

Result in ST03

In ST03 you can now see the results in the part for transaction profile standard overview:

Good background SAP blog: reference.

Funny ABAP code blocks

Just for fun: funny ABAP code block comments….

When we cannot call our own function modules properly, we do deserve a short dump (program LSZA0F34):

Spaceship BERID, MRP area, has adventures (program LATPCFA6):

Program LSHI0F02 has road construction (Baustelle):

Trigger an error or end up in FI hell (program LWOST_CR_IMG01FNG):

A nice golden rule: do not touch coding if you don’t know what you are doing, and if you do it is night work for you in the office to repair it (program SAPMSSYD):

It will be painful (program RPCMSAG0PBS_FORMS):

Program RSORAF01 show life is sometimes terrible:

Complaints in function module ADDR_GET_NEXT_COMM_TYPE about junior programmers:

Some commented out Scheisse (shit in German) in program RV14B000:

Program RSDBPREV calls out to Helga:

ADT-VS: ABAP development tools for visual studio

SAP ABAP on Eclipse will be replaced with ABAP on visual studio (background is explained in this blog). Developments in the RAP framework and AI Joule will be done in ADT-VS. If you are looking for Eclipse ADT installation, read this blog. Both Eclipse ADT and ADT-VS require the ABAP backend installation of the ADT tools, which is the same for both and described in this blog.

Installation and connection to backend

Frequently asked questions blog refers to the formal help.sap.com page on ADT for visual studio code.

Simple steps:

Install Visual Studio Code on your laptop from this URL Download Visual Studio Code – Free AI Code Editor for Mac, Linux, Windows.
Launch the newly installed tool
Go to the Extension on the left hand side:

Search for the ABAP Development tools and install them:

4. Wait for the installation to finish and restart the Visual Studio

5. To add an ABAP destination, click in the menu View and select Command Pallette, and key here ABAP: New Destination

6. In the popup select on the right hand side the + button:

7. Select RFC to backend or HTTP to cloud system:

If you take RFC, the popup will show entries from your SAP GUI.

8. Enter User ID, password, client (be careful here: default it will give you 000, this is NOT what you want), language and password if SSO is not setup

Using the studio

On the left hand side the connections are visible. Right click on any and select the option Logon to Destination:

Rest is same as ADT. Do realize that not all editors are yet working in Visual Studio.

Background references

ABAP AI Joule: read this blog, and this blog. Do realize AI ABAP Joule is licensed and not free of use.

All about ABAP for VS code: blog.

Transport RC-8 errors, reasons and solutions

This blog will list several RC-8 transport errors, explanation of the reason, and solution to solve the RC-8.

Import options

The transport import has a tab for options:

In the below solutions there is reference to the use of these options.

Adding transport again to the import queue

To re-import transport again, go to transaction STMS, go to the import queue, select the menu Extra, Other Requests, Add. Enter the transport request and tick the box Import Again:

Local repair

For some reason the ABAP code was changed locally in the target system.

The text looks like “was repaired in this system”:

Solution: re-import with the overwrite originals flag, and set the flag overwrite objects in unconfirmed repairs.

Component version mismatch

A very frequent cause of transport errors can be component version mismatch. This means that the system detects a difference in components between the source and target (more on components in this blog). That can be a component (like add on) that is already installed on the source , but not yet on target. Or that in the source the ST-PI or ST-A/PI is already patched, but not on the target.

In most cases this version mismatch can be ignored and you can set the “Ignore Invalid Component Version” flag.

When not to set this flag:

Transports related to newly installed addon like customizing/workbench needing the new component
Transports with OSS notes related to this component (for example OSS notes on top of ST-PI)

Missing ABAP object references

A very common cause of RC-8 is that an ABAP program needs an object, which the developer stored in a different transport. To fix the RC-8: import first the transport with the object, then the ABAP program transport. Or import them both at the same time.

To avoid such RC-8’s always run the transport sequence check tool, as explained in this blog.