Welcome to the Sensor Board

You've found the manual for the Sensor Board - home of sensors that keep an eye on details of your S/4 Hana system. This manual covers the individual sensors that are available on the board.

---

Welkom op het Sensor Bord

Je hebt de handleiding gevonden bij een Nederlands- en Engelstalig sensor bord, thuishaven voor sensoren die een oogje in het zeil voor je houden voor het S/4 Hana systeem. De handleiding is alleen in het Engels beschikbaar. Deze handleiding behandeld de individuele sensoren op het bord.

Overview of groups for sensor types

The Sensor Board is a product that was designed and developed in Abap on S/4 Hana. The actual board is shown in a SAPGUI screen as HTML (CSS, JavaScript) document. The board refreshes automatically. Details from the board are also available as a service (oData) - which can be used to project the board content just about anywhere.

Preview of the sensorboard with errors and warnings

Types of sensors

Each sensor on the sensor board is in fact an implementation of a Sensor type. Some of the sensor types are very specific to a subject and some could be applied to e.g. a company code (of which there may be many).

When a sensor is added to the board, a group needs to be selected. It is not possible to add a sensor with the same sensor type and the same parameter settings to a group. Here's the rule:

Sensor = Sensor type + Parameters

In the paragraphs below all sensor types that are available as standard are briefly explained. Sensor types that share main subject are grouped together.

Batch jobs

Batch jobs cover an important and continuous workload of tasks that need to be done. Keeping a close eye on batch jobs is good sensor-ship.

Types of issues on batch jobs

1. Batch jobs can be cancelled for several reasons. A job can "cancel itself" by throwing an error message. Jobs can also cancel because of e/g a programming error resulting in a dump (ST22).
2. It is also possible to cancel a job manually, e.g. when it is running too long.
3. Jobs can run too long
4. Jobs can produce logs about problems that don't stop the job.

Transaction SM37 will show details on batch jobs, from where all available batch job information is accessible.

Types of batch sensors

• SM37 Batch jobs
  
  This sensor focusses on failing jobs. The simplest form is the total number of failed jobs on the current day. The sensor works with the TIMING and DATING parameters, which control how long the sensor should look back.

  The sensor can also be set up to focus on a specific job. Parameter NAME can be used to specify the focussed job. This can be used to compose a group specific for a process. The SM37 sensor can be set up to focus on batch job used by the process (covered in a group).
  
  
  
  

• SM37ALL Batch job overview
  
  This sensor composes a list of the (all) batch jobs that ran somewhere in the past 45 days (alternative date can be specified). This list is used to compose a list of unique batch jobs and their steps.

  This sensor helps to check the overal health of the batch job administration. The sensor lists the active jobs and caters for an in-sensor registration. The sensor long text can be used to specify each specific job. Contact information (who to contact for this job) and a description (which has no max length) can be specified - information will be displayed on the overview.

  The KPI on this sensor is the counter of non-registered batch jobs. This could be used to keep an eye on newly created (periodic) batch jobs.

  The sensor-reported content can also be composed as a list of job-steps. Instead of batch job names, the reports that are executed for the jobs are the main subject of the overview. Actual batch job information is also made available.
  
  
  
  

• SM37LOGS Batch job logs details
  
  This sensor checks the logs of a job for specific entries. Jobs that reveal an issue in the joblog without stopping the job, can still be monitored on a sensor.

  For custom developments, this means that the developer has an easy way to link the batchjob to a sensor.
  
  
  
  

• SM37LONGEST Longest batch job
  
  This sensor focusses on long running jobs. The simplest form will determine which of the active jobs has been active for the longest time.

  Long running jobs can indicate problems like dead locks or processing loops.
  
  
  
  

• SM37SINGLE Batch job details check
  
  Some health checks that apply to specific batch jobs can be checked by this sensor. Expectations on the longest runtime, or the maximum time between jobs can be tested. In some cases the job should be scheduled by a system user, which can also be tested.
  
  
  
  

Runtime errors

Any system will have problems that can't be resolved. On an SAP system these end up in the ST22 dumps overview. Dumps are the generated logs for processes that were stopped - by the system. A division by zero, a timeout on a user process that ran too long or even a programming error.

The thing with runtime errors

There are so many processes running on the system all day (and night), that some will inevitably be stopped. The system will automatically gather available information - and create a detailed logging for it: the dump. The log is a "dump of the details" for a runtime error. They can be found in transaction ST22.

So what's the concern ? There can be many, as a runtime error on a process can happen on any process. A few points of interest - on runtime errors:

• A runtime error halted a process - "in mid-air". This process thus didn't get the chance to finish it's task (and the process doesn't know about this). A runtime error is an interruption of a process.
• A common reason for runtime errors is the TIME_OUT. A user starts a report which selects so much data, that the time-out time is exceeded (something like 20 or 30 minutes). The system will stop the process and log it's details in a dump. This type of dump is usually low priority and no concern, as it does not involve updates and there is only 1 disappointed user.
• To avoid the TIME_OUT, the user could schedule the report to run in the background, to which TIME_OUT is not applicable.
• For other dialog or background processes, many things could go wrong. Sometimes even as a series of runtime-errors, which could seriously influence the system.
• Is your system using system-users for batch jobs ? This would be a very useful feature, as the jobs and the runtime-errors they may throw can easily be recognised as system-relevant (making them more important).
• Is the actual runtime-error related to an issue that has an effect on all processes ? E.g. memory related runtime errors ? When memory is running out, eventually all processes are involved. Another way to prioritize runtime errors.
• It is not uncommon for runtime errors to appear during or after transports were applied. A faulty or incomplete transport can damage coded objects leading to syntax errors.

There is only 1 sensor on runtime errors available on the sensor board.

• ST22 Runtime errors
  
  Checks for (new) runtime errors.

  This sensor works with a blacklist and a whitelist for runtime error codes. Errors that are deemed irrelevant (like TIME_OUT) can be whitelisted (will not be reported) and the errors that need attention are blacklisted giving them a hogher priority. Memory-related runtime errors would be suitable candidates for the blacklist.

  The sensor allows selection refinement - to e.g. a system user.
  
  
  
  

Idocs

It's becoming a bit old-fashioned, but Idocs ir Intermediate Documents are a common means to interface data (documents) between systems.

The Idoc processes has 3 sensors in it's sensor-suite. For change pointers - effectively a triggering mechanism for outbound Idocs. For inbound Idocs and for outbound Idocs.

• BD21 Change pointers
  
  Checks the queue of change pointers.

  Change pointers can be set based on e.g. change documents, to ensure that relevant updates are sent out as outbound Idocs. It's a queue and queues should be processed. The sensor gives an insight on what is in the queue. Transaction BD21 is available on this.
  
  
  
  

• BD87INB Inbound Idocs
  
  Checks the Idocs that are sent out from the system.

  The inbound Idocs, or Idocs that are presented to the system, should be processed into actual documents. Whenver this fails, the sensor will respond. Transaction BD87 shows Idoc traffic and status (for both in- and outbound Idocs).
  
  
  
  

• BD87OUTB Outbound Idocs
  
  Checks the Idocs that are sent to the system.

  The outbound Idocs, or Idocs that are pushed out of the system, should be created when relevant (e.g. triggered by change pointers). Whenver this fails, the sensor will respond. Transaction BD87 shows Idoc traffic and status (for both in- and outbound Idocs).
  
  
  
  

Users

The system is a servant to it's users. The sheer number of (dialog) users that are active on the system can itself become a concern. Especially when some of them run heavy reports.

The sense of how crowded the room is (was) during the day is a good indication on why the system seems slower. Thus a logged sensor on this topic, is a nice to have you should have. The SUIM sensor will cater for this.

• SUIM User activity
  
  Checks the number of active users.

  A system is sized on the number of users. Serving users is the system's main task. One can imagine that serving 100 users or 1000 will make a huge difference in required CPU time (and memory). This Sensor keeps track on active users. When KPI logging is switched on for this sensor, a measurement on how many users the system is serving during the day is available.
  
  
  
  

• SUIMHISTORY User history
  
  Focus on the user ID's that have not been used for a longer period of time - which are also flagged as inactive. Users which have an end-date in the past.
  
  
  
  
• SUIMSLEEPERS Inactive users
  
  Focus on the user ID's that are no longer used. This sensor identifies potential candidates that can be removed from the system - which saves licence costs.

  User ID's that have not been active for a longer period of time could lead to an overhead of licence costs. The inactive users or sleeping users sensor reports on the users with their last login date. Especially dialog users that have not logged on can be considered inactive.

  Use the parameters to specify how many days you regard as "enough to be a sleeper", e.g. 180 or 365 days. If you know what licence costs per user apply, this sensor can be set up to report actual saving costs (use parameter FEE:35 for this - when a user licence fee is 35 euro). Parameters can also be used to focus on a user class or only dialog users.

  The sensor determines up to 3 dates:

  1. The date that user was added to the system.
  2. The date the last user activity was measured, on a table - this is explained below.
  3. The date the user last logged on.

  The date the user was created will always be available, the other dates can also be blank. A background user can't log in, but a background user can temporary be a dialog used. And the activity determination does not necessarily pick up on all user activity.

  Measure the last user activity

  The Inactive users sensor can detect user activity by selecting the most recent create or change date on a table. The most common tables for this are the Change Document log (table CDHDR) and the Business Application Log (table BALHDR). Your own choice of tables can be added to this setup, through sensor longtext settings. Here's how it works:

  The sensor can be provided with the following info:

  • Table name
  • Field name for the user ID
  • Field name for the date to be checked
  • Optional field name for the client, if it is not called MANDT.

  The sensor will use this information to effectively perform a selection of the most recent available date on the system. Multiple tables can be added, which will make the sensor look for the most recent activity date on the combined tables. The result is a single date for the user.

  Check the sensor longtext settings for details on how to add table information. This text will show the following example:

  /: CDHDR/USERNAME/UDATE/MANDANT

  The sensor will pick up on this and report it as settings on the sensor. What the sensor will to with this is execute the following SQL query:

  SELECT username as USER, max( UDATE ) as LAST_ACTION  
    from CDHDR 
    group by username
  

  Note that the fieldnames and table name are applied from the sensor text settings (CDHDR, USERNAME and UDATE). Results will be returned like this:

  USER	LAST_ACTION
  MAASDAMW	2025-03-12
  MOONSY	2023-12-02
  MUNSTER	2025-01-21

  Sensor logic will compose these results for multiple selections and merge them into a single result holding the last action dates. Any table which holds a user name and a create or change date can be used to capture activity.
  
  
  
  

Queues

Work that can't be processed immediately can be processed from a queue. So whenever the job to be done gets somewhat serious, the workload is captured in a queue and processed from there.

The system has many variations on these queues. The amount of work that is being piled up on the respective queues - can become a concern. One thing to remember here is the simple fact that the use of queues relieves the system from having to do it immediately.

• SMQ1 Outbound tRfc queue
  
  

  Queue entries can be faulty or unprocessed for a long time. Both potential issues can be monitored with this sensor.
  
  
  
  

• SMQ1LONGEST Outbound tRfc queue
  
  

  When a queue holds old information that is not processed, processing the information may no longer be relevant. This sensor focusses on the oldest queue entries.

  When old entries are left unattended, there is the risk they would get reprocessed. Reprocessing old queue entries is much like going back in time. The subject of these queue entries may have been sent out again (and again) after failed message.
  
  
  
  

• SMQ2 Inbound tRfc queue
  
  

  Queue entries can be faulty or unprocessed for a long time. Both potential issues can be monitored with this sensor.
  
  
  
  

• SMQ2LONGEST Inbound tRfc queue
  
  

  When a queue holds old information that is not processed, processing the information may no longer be relevant. This sensor focusses on the oldest queue entries.

  When old entries are left unattended, there is the risk they would get reprocessed. Reprocessing old queue entries is much like going back in time. The subject of these queue entries may have changed in the mean time.
  
  
  
  

• SM58 Rfc queue
  
  

  Queue entries can be faulty or unprocessed for a long time. Both potential issues can be monitored with this sensor.
  
  
  
  

• SM58LONGEST Rfc queue
  
  

  When a queue holds old information that is not processed, processing the information may no longer be relevant. This sensor focusses on the oldest queue entries.

  When old entries are left unattended, there is the risk they would get reprocessed (even by accident). Reprocessing old queue entries is much like going back in time. The subject of these queue entries may have changed in the mean time.
  
  
  
  

• SWEQADM Workflow event queue
  
  

  Workflow events can be set up to execute immediately or via a queue. The event queue should be processed in full which can take a while when the system is busy. In addition to that the processing of an event can throw an error, which will show on the queue. This sensor keeps a close eye on the event queue.

  Old events could no longer be relevant for processing. Hence this queue (like many other queues) should be kept clean and fresh. Consider deleting the old entries - once the risk of reprocessing them is too high.
  
  
  
  

Logs

The system is set up to keep track of what happened, for which many logging setups are available.

• SM21 System Logs
  
  

  The log of all logs is the system logs. Dedicated to keeping the system up and running. Not the place where transactional data issues should be logged.

  It is possible to let custom build logic drop a message on the SM12 log, but it is not recommended. the SM21 log is for standard SAP matters which include logon fails, connection fails, dumps, break-point interruptions, memory issues, space issues and much much more. When a system goes down, the role of SM21 in determining the root cause is very important.

  Note that the sensor will only report on the error messages on SM21.
  
  
  
  

• SLG1 Business Application Logs
  
  

  The business application log or BAL is for transactional logs. These should be made available for actual identifyable topics such as documents (an purchase order, a sales order, or even an Idoc). Business application logs are accessible through transaction SLG1 (there's also SLG0 and SLG2) and these logs are made visible on a dedicated sensor only when they contain errors.

  The sensor can work with a specific object and subobject, which allows linking it to a given process. The sensor also measures the total size of BAL logging information available - with a hint on how to clear it.

  I it's not only errors that need to be monitored, consider using the SQL sensor on table BALHDR.
  
  
  
  

• SXIMONITOR Processed XML messages
  
  The XML message monitor or SXIMONITOR logs XML traffic for the system. This setup also carries a log, for which the sensor was set up.
  
  
  
  
• DBTABLOG Changelog on tables
  
  Tables changes can be logged by setting the "Log changes" indicator on the definition of the table. These changes are captured in the DBTABLOG table, which is known for it's serious size. This sensor has a double function: (1) monitor the size of a serious database space consumer and (2) monitor changes on a specific table of interest.

  The sensor information text reveals some of the available reports available for housekeeping on DBTABLOG.

  This sensor can be used in 2 "modes". DBTABLOG logging details are captured per table (field YABNAME) and KPI details are reported as such (unit of measure: Tables). It is also possible to run the checks for a specific table, which will report its KPI as the number of changes (unit of measure: Changes). Make sure you change the UoM descriptor from Tables/changes to either Tables or Changes.
  
  
  
  

• SM37LOGS Batch job logs details
  
  This sensor checks the logs of a batchjob for specific entries. Jobs that reveal an issue in the joblog without stopping the job, can still be monitored as a sensor.

  Every job has a job log which holds the messages that were thrown. When a job throws an error message, the job (and it's processing) will automatically be cancelled. Other messages are logged and can be checked at later. This sensor can do the check for you. Set up the sensor and specify which message you want to find.

  The longtext for this sensor should look something like this:

  /: NAME_OF_THE_JOB
  *  MSGID:00
  *  MSGNO:001
  *  TEXT:Sensor controle afgerond
  *  MSGV1:variable value
  *  MSGV2:another variable value
  

  Only specify what you want to check - for a KPI hit on the sensor.
  
  
  
  

Performance

When the system performance is low, there are a number of root-causes to consider. The sensors listed here have a focus on system-wide performance. This includes CPU utilization on dialog processes and background processes, memory usage and the SM21 system log - which will reveal the first signs of system struggles.

• ST06CPU CPU utilization
  
  This sensor checks CPU utilization on the system. Processors can be idle or occupied, the over-occupied Processors will have an impact on the performance. An S/4 Hana system is equipped with multiple processors, thus the information on CPU utilization is monitored in clusters. The sensor's purpose is only to warn on excessive CPU utilization. For more detail - check out transaction ST06.
  
  
  
  
• ST06MEMORY Memory usage
  
  This sensor checks Memory usage on the system. An S/4 Hana system is all in memory, but part of this is process memory used by processes (and limited). The sensor's purpose is only to warn on excessive memory usage. For more detail - check out transaction ST06.

  Note that memory is an application server matter, hence the calculated percentage is for all application servers combined. The sensor can also be set up to measure a single application server. Thus a sensor for each server can be set up.
  
  
  
  

• SM50 Work processes
  
  The system has dialog processes and background processes which are made available. The number of processes in use versus the number of available processes is returned as percentage KPI. Dialog processes and background processes can be separated through parameter settings. Application server can also be specified.

  For more detail - check out transaction SM50.
  
  
  
  

• SM21 System Logs
  
  

  The log of all logs is the system logs. Dedicated to keeping the system up and running. Not the place where transactional data issues should be logged.

  It is possible to let custom build logic drop a message on the SM21 log, but it is not recommended. the SM21 log is for standard SAP matters which include logon fails, connection fails, dumps, break-point interruptions, memory issues, space issues and much much more. When a system goes down, the role of SM21 in determining the root cause is very important.

  Note that the sensor will only report on the error messages on SM21.
  
  
  
  

Workflow

Workflow processes run well if everything is set up and operational. There are background tasks that need to be scheduled, there is a queue for events that controls processing and individual work items could end in error without anyone noticing.

• SWI1 Workflow work items in error
  
  This sensor checks for workflow work items in the Error status - which will stop the workflow. Check out transaction SWI1, SWI5 or SWI6.
  
  
  
  
• SWI1ACTIVE Active workflow work items
  
  This sensor checks for active workflow work items in a normal status. These are sitting in someone's inbox waiting to be processed. Check out transaction SWI1 or SWI6.
  
  
  
  
• WORKFLOW Workflow operations
  
  There is a small suite of batchjobs that should be up and running for Workflow to be operational. These jobs (or rather job steps) are checked here. This sensor reports on the batch job steps that are not executed regularly - which will affect the Workflow system.
  
  
  
  
• SWEQADM Workflow event queue
  
  

  Workflow events can be set up to execute immediately or via a queue. The event queue should be processed in full which can take a while when the system is busy. In addition to that the processing of an event can throw an error, which will show on the queue. This sensor keeps a close eye on the event queue. Check out transaction SWEQADM.
  
  
  
  

Files and folders

Each application server lives on a file system, which will have a limited space for it's files and folders. So what would happen if this file-space runs out because large files are created ? The application server would be stopped. Hence the FILES sensor was made available.

• FILES Files
  
  This sensor checks a series of file-related measurements. Settings for this are captured in the sensor long-text, which can hold details on multiple groups.
  
  For this sensor to work, the folders that need to be checked should be set in the sensor long-text. This is done "under an ID". The ID specifies the group to be checked and the details that should be checked. The sensor can then be added to the sensor board. If the sensor is created without ID: parameter, all checks that don't have SKIP:Y will be checked.

  If the sensor is used to monitor a certain process, an ID for this process can be added and the Sensor will focus only on the given ID.

  For each folder several measurement points can be checked.:

  • MAXFILECOUNT - for the maximum number of files that are expected in the folder
  • MAXTOTALSIZE - for the maximum total filesize on the folder
  • MAXFILESIZE - for the maximum allowed size of a single file

  • SUBDIRECTORYLEVEL - Can be used to specify the number of subdirectory levels should also be checked.

  Use transaction AL11 to find details on the server folders and files.
  
  
  
  
• ST06SPACE Server space
  
  This sensor checks the available space on mount-locations available to the (application) server. These locations add up to a total storage capacity and all locations should have space available. The highest occupance percentage is also the sensor KPI.
  
  Transaction ST06 reveals more detailed information on available space.
  
  

Number ranges

SAP and any other database system has dealt with number ranges since forever. Number ranges control what the next order number should be, when created through a BAPI or API or through whichever available means. Ranges have a starting point, an endpoint and a current value. When the highest value of a number range has been consumed - no new numbers will be available.

• SNRO Number ranges
  
  The number range sensor will check all number ranges on the system. It determines which of the ranges are "getting close" to their respective high values. The KPI for this is expressed as a percentage.

  The sensor longtext caters for settings that can be used to ommit a number range object from the checks. And a sensor parameter can make the sensor focus on a specific number range, to make it relevant specifically for a certain process.
  
  
  
  Transaction SNRO reveals more detailed information on number ranges.

Emails

The system can compose and send out emails to notify users (or other receivers). When the system fails to deliver, the sensor can make users aware.

• SOST Outbound emails
  
  The sensor board relies on email itself as well. A mail notification should be sent out to the subscriber of a sensor group when one of it's sensors turns red. This sensor monitors failing outbound email messages.

  It is also possible to utilize this sensor on inbound emails. Set the DIRECTION:R parameter for this.
  
  
  
  Transaction SOST reveals more detailed information on sending emails.

Printer output

Printer output or spools can accumulate as output from batch jobs that are not necessarily printed.

• SP01 Printer output
  
  An overflow of spool output can become quite an issue for the system, as all processes that generate spool output will be affected. This sensor reveals the state of affairs on printer output - with errors.

  The PAGECOUNT parameter can be set to select larger spool outputs. E.g. PAGECOUNT:500 will also list any spools (printer output) that are larger than 500 pages.
  
  
  
  Transaction SP01 reveals more detailed information on spools.

Locks and updates

Any updates need to be locked and the actual update process (database process) can fail leaving update errors.

• SM12 Locks
  
  The system hosts a locking mechanism that ensures our updates are protected. In extreme cases, there can be so many locks generated by some update process, that the locking mechanism itself needs attention. Are old locks released ? Is some automated process claiming too much ?
  
  
  
  Transaction SM12 reveals more detailed information on locks.
  
  
• SM13 Update failures
  
  A database update is a series of events that should lead to your changes being applied. The database should accept the changes - which is not always possible. An update error queue is available for this. Some errors can be reprocessed from the queue.
  
  
  
  Transaction SM13 reveals more detailed information on update errors.
  
  
• SM13LONGEST Oldest update failure
  
  It is good practice to clear the SM13 queue regularly. If this is not done, there is a change that an update error is reprocessed long after it's relevance sell-by date. The update would be done on a document that may have been updated since the update error. This sensor warns about old (aged) update errors.
  
  
  
  Transaction SM13 reveals more detailed information on update errors.

Housekeeping

The system relies on housekeeping actions to clean up on data that is no longer required. Old logs for batch jobs, dumps from over a month ago, Idocs which have been processed into actual documents a long time ago. It is easy to overlook these steps, as they cause no immediate harm. Until they do.

There are many cleanup jobs available as delivered by standard SAP. These sensors see to these jobs getting scheduled.

A custom setup that produces data, should also be set up to clear this data. House keeping on custom tasks can be added to these sensors.

• AIF AIF housekeeping
  
  This sensor ensures that a set of AIF related housekeeping jobs are scheduled. Check the sensor itself for a listing of these jobs.
  
  
  
  
• SYSTEM System housekeeping
  
  This sensor ensures that a set of general system housekeeping jobs are scheduled. Check the sensor itself for a listing of these jobs.
  
  
  
  
• CUSTOM Custom housekeeping
  
  This sensor ensures that a set of general customer housekeeping jobs are scheduled. Check the sensor itself for a listing of these jobs.
  
  
  
  
• SAPAPO APO housekeeping
  
  This sensor ensures that a set of SAP APO housekeeping jobs are scheduled. Check the sensor itself for a listing of these jobs.
  
  
  
  
• WORKFLOW Workflow housekeeping
  
  This sensor ensures that a SAP's Workflow housekeeping jobs are scheduled. Check the sensor itself for a listing of these jobs.
  
  
  
  

Self service

The sensor board is a sub-system that itself could run unto some trouble. The board is set up to refresh every 20 seconds or so - for the end user. But the actual sensor updates are processed from a batch job, that should be up and running for the board to work. A sensor - for the sensorboard itself.

• SENSOR Self service
  
  The self service sensor ensures the board is operational. This implies that sensor KPI values are updated regularly, but also that emails are being sent out when applicable. The sensor will gather potential problems and report on them.

  As the main engine behind the sensor framework is a batch job, elaborate reporting on what each available batch job is tasked with is reported on this sensor.

  Note tbat this sensor is also executed when the ZEN transaction is started. Whenever this sensor errors, it is visible in the selection screen of transaction ZEN.

  The sensor self-service sensor is embedded in the framework as it deserves a "special place".

  There are a few settings that are applied on the sensor board, which are customizable for the whole framework. These are:

  1. The background image of the sensor board, which covers the whole sensor board (unless dark mode is selected). (BACKGROUND)
  2. The location of the manuals, which is accessible from the Sensor editor (DOCUMENTATION and DOCUMENTATION-DETAIL)
  3. The names of batchjobs that perform sensor-related tasks, such as board feeder jobs (job feeder: a report that is scheduled to follow-up on the content of a sensor, so-called automatic fix jobs). (BATCHJOBS).

  These settings are covered/explained in the sensor long text for the Self-service sensor (SENSOR).

  Note that the self-service sensor also shows an overview of all available sensor types and an indication on their usage or usage count.
  
  
  
  

• REMOTE Remote sensor boards
  
  Whenever the sensor board is used on multiple SAP systems, the "other" board can be checked through a sensor. The REMOTE sensor can be set up with an RFC (Remote Function Call) name of the target system.

  The sensor reports sensors in error, on the other board.
  
  
  
  

• VERSION Version check
  
  The sensorboard framework components are rolled out to multiple installations at multiple customers. With it's version management sensor, it can detect the smallest of changes on the framework components that should not be changed. Why should an open source solution not be changed ? Because changes are in the way of upgrading, as a custom change would get overwritten.

  Version checking is done using a hash-technique. A GUID-like hashcode is generated for the source coding of relevant components and these are embedded into the version control class (hardcoded). This hardcoded class it itself also hashed into a code, which is available centrally. Validity of this code can be checked any time.
  
  
  
  

Open SQL selection

Any selection that can be executed in the SQL console of Eclipse, can also be executed in this sensor. The sensor will report on the results and determine what the KPI value should be.

As this sensor should support multiple selections, the setup caters for NAME-usage, which should alway be filled in. Thus: the NAME parameter should be set.

• SQL SQL selection
  
  A simple selection like SELECT * FROM T000 would already be sufficient to make this sensor work. The sensor KPI would be the number of entries on T000 and the first 8 columns of this table would be listed as sensor detailed output.

  The sensor long text plays an important role in using this sensor. Make sure you check the explanation on the sensor long text, which is available from a button on the sensor settings. It explains all details.

  This is the most versatile sensor the board holds. It can capture any selection or any result(count) that can be captured in an SQL selection. This includes JOIN or CDS view selections. Don't underestimate this sensor. It can capture the logic from several other sensors.

  Example 1: minimal

  As a minimalized example, a single-line selection is done on the T001 table, which holds the company codes that are set up for the system.

  	SELECT mandt, bukrs, butxt from t001 
  	

  Note that the client (mandt) needs to be specified (or set in selection) for client-dependant tables.

  To apply this selection to the sensor, simply create a sensor from Sensor settings. Select a group and fill in SQL for the Sensor type, press enter. If this sensor is already available, consider copying it.

  The sensor text for this sensor should be edited, as per example:

  	/: T001
  	*  This sensor lists the T001 entries / companies.  
  	/: SQL
  	*  SELECT mandt, bukrs, butxt from t001 
      

  To use the sensor, set it's parameter to:

  	NAME:T001
  	

  When the sensor is executed, the KPI will be set to the number of selected entries and the sensor content will show a table with MANDT (Client), BUKRS (Company code) and BUTXT (Company description) of all the available clients. Adjust the selection to the required client:

  	SELECT bukrs, butxt from t001 where mandt = '120'
  	

  Note that the KPI is delivered as the number of selected records.

  Example 2: using a result counter

  If one of the fields is named RESULT, this will be used to determine the selection KPI. To demonstrate, we will use the DBTABLOG table (always packed with data).

  	SELECT count( distinct tabname ) as RESULT from DBTABLOG 
  	

  This selection will return a single counter which will be recognized as the sensor KPI.

  Another example using counters:

  	select tabname, count(*) as result
        from dbtablog
        group by tabname
      

  This will compose a KPI for the total number of records on DBTABLOG, with detailing to the counters on the table per tablename.

  Example 3: involve date and time

  Sensors often use DATING and TIMING to limit the selection to a specified period of time. If the results should be for the past 10 days only, the SQL selection can be adjusted to:

  	select tabname, count(*) as result
        from dbtablog
  	  where logdate IN DATING
        group by tabname
      

  Parameters on the sensor should then specify DATING, like so:

  	NAME:DBTABLOG-EX3;DATING:10
  	

  The sensor will apply this to the selection and report the results.

  The same setup can be applied as TIMING for time fields:

  	select tabname, count(*) as result
        from dbtablog
  	  where logdate IN DATING and logtime IN TIMING
        group by tabname
      

  Parameters on the sensor should then specify DATING and TIMING, like so:

  	NAME:DBTABLOG-EX3;DATING:0;TIMING:3
  	

  
  
  
  
  
• SQLINDX SQL indexing
  
  This is largest sensor in coded logic. It is designed to determine a growth-index on a KPI, measured over a period of time and the same period before that time. KPI measurements from the 2 periods are compared and the growth or shrinkage are displayed as a percentage (either positive or negative). Much like the AEX-index.

  The versatility of this sensor is the fact that the KPI selection can be done in open SQL - so you get to decide what is being indexed. Factors at play:

  • KPI calculation results are to be made available in a column named RESULT.
  • The KPI can be a count, but also a value (or sum of values).
  • To determine a period, there should always be a date on the selection. Option IN DATING should be used (once) on a relevant date (mostly the create date).
  • Whenever the date is used (without time), the current date is not selected. This will have an effect on sensors that are refreshed all day - as these will return the same information all day.
  • When in addition to a date (e.g. create date) a time is also available, the sensor will become near-real-time. The period is calculated from the current time, as reported on the sensor. This is the preferred way of using the sensor.
  • Sensor parameters should include DAYS or HOURS (or both), which is a requirement on determining the selection periods.

  The sensor long text plays an important role in using this sensor. Maks sure you check the explanation on the sensor long text, which is available from a button on the sensor settings. It explains all details.

  Example 1: minimal

  To clarify how this sensor works, let's go through an example. Table DBTABLOG holds table changes for a wide variety of changes. Let's assume this is interesting information - as it "shows system activity", which can be interpreted as "In business as usual".

  An SQL selection would be required, with an outcome (KPI) on a selection that involves a date:

  	  SELECT count(*) as RESULT from DBTABLOG 
  	    WHERE logdate IN DATING
  	

  In this example the RESULT and IN DATING segments are needed to link the selection results to the sensor. The "IN DATING" part is not standard SQL (it was cooked up by the creator of the sensorboard).

  The above selection can be implemented on the sensor longtext. To do this, the selection would require a name, an optional description and the SQL selection. This would look like this:

  	/: TABLOG-ACTIVITY
  	*  This sensor measures the number of changes logged on the DBTABLOG 
  	*  table, as an indication of system activity. 
  	/: SQL
  	*  select count(*) as RESULT from DBTABLOG 
  	*    where logdate IN DATING
  	

  The sensor can now be set up for the above selection. Go to sensor settings, on the Sensors tab, select a group and fill in Sensor type SQLINDX, press enter. If it already exists, consider copying it. The parameters on this sensor require NAME and DAYS (or HOURS). In our example, set the sensor parameter to:

  	NAME:TABLOG-ACTIVITY;DAYS:10
  	

  The sensor is now ready to be used. It will:
  • Execute the selection for LOGDATE = 10 days ago until (and including) yesterday for period T
  • Execute the selection for LOGDATE = 21 days ago until 11 days ago - for period T-1
  • Report on the results where T-1 and T selections are shown together
  • Calculate the deviation percentage from period T-1 to T - as KPI percentage with 3 decimal positions

  Example 2: involve timing

  The most up-to-date index results can be determined when time is available. Applied to our example:

  	  SELECT count(*) as RESULT from DBTABLOG 
  	    WHERE logdate IN DATING and logtime IN TIMING
  	

  This will change the selection setup quite a bit. It will involve the time in such a way that link date and time together. So when IN TIMING is used with DAYS:1 (or HOURS:24) and the current time is 13:15, it will select data from yesterday 13:15 until today 13:15.

  Note that the date and time information that is used for the selections is reported on the sensor.

  Example 3: add columns

  In the above example, the outcome of the selection is a single counter. It is however also possible to involve other columns - elaborating on where the counter information comes from. To demonstrate this, the table name is involved. Counter results will be grouped by this table.

  	  SELECT tabname, count(*) as RESULT from DBTABLOG 
  	    WHERE logdate IN DATING and logtime IN TIMING
  		GROUP BY tabname
  	

  The effect of this will be that more information is revealed on the sensor report. To take this a bit further, let's also add the description of a TABNAME:

  	SELECT log~tabname as table, DT~ddtext as description,
        count( * ) as result
        FROM dbtablog as log
         LEFT OUTER JOIN DD02T as DT on DT~tabname = log~tabname and
           DT~ddlanguage = 'N' and DT~as4local = 'A' and
           DT~as4vers = 0000
        WHERE log~logdate IN DATING and log~logtime IN TIMING
        GROUP BY log~tabname, DT~ddtext
      

  Note: the LEFT OUTER JOIN is used, because not all table descriptions are available in English (and the slection outcome should not be influenced when a description is missing).
  
  
  
  

Tables

Home of data.

This sensor has focus on tables, record counts, size and growth.

• TABLES Table information
  
  Every bit of information is held on a table. The S/4 Hana database is one that grows and grows with every minute of every day.

  The TABLES sensor type keeps track of the tables of your choice. The sensor long text holds information on which table to track. The sensor produces a report of the settings and a report with the focussed tables. It calculates the number of entries and the estimated size on the database (record size x record count). The sensor settings can be used to specify what maximum table size is acceptable. When this maximum is breached, the sensor KPI is increased.

  For tables with a creation date, it is also possible to specify a maximum table growth. Specify which field is the (create) date on the table and how many days the check-period should be. The sensor will determine record counts for 2 periods (T-1 and T) and calculate the growth percentage. A growth spike can be measured on the sensor, on any (transparent) table the system uses.

  To check these tables, transaction DB02 can be used (on most systems), or SE16 and SE16N, SE17 or the SQL console in Eclipse.
  
  
  
  

Save space save money

An S/4 Hana database is superfast because of clever architecture (column based), it caters for working with multiple processors (even within a single selection statement) and it operates from memory. Operation from memory with a backup to disk - is costly. Thus removal of data that is no longer needed, is a way to save money. These are a set of sensors that keep you informed on where table space can be saved.

These sensors target the most common standard SAP tables that hold change logs, processing logs and tables that contain information that is also applied somewhere (e.g. Idocs). This in itself holds a lot of knowledge if the system. Which tables are about change documents ? What report is available to clear aged documents ? These are all part of the sensors.

There is an overview sensor and there are detailed sensors which also have a FIXER or FXR report. A fixer report will take care of clearing old data for a retention period.

Clean cash

House keeping tasks used to be important because it would lead to poor performance. With S/4 Hana the importance shifted to operational costs. As each system fills up with data, it is good practice to keep an eye on retired data.

An example case: workflow. A classic workflow setup used a workflow container which held the full payload of an XML message. The table for this workflow container contained 130Gb of data. Only 1% of these workflows were still active. SAP hosts a report that removes old workflows, including their containers.

130Gb at 300euro per month (source unconfirmed) is 39.000 euro. Completely unused storage space.

How was this discovered ? SAP's DB02 reveals information about the largest tables on the system, the fastest growing tables and so much more. Go and investigate what is happening on your system.

• SAVER_ALL Overview of space saver candidates
  
  Todays information will age until it is no longer relevant at all. This sensor composes a list of database consumers (tables) with record counts and storage size. For each of the subjects (e.g. Change Documents, Idocs) a retention period can be defined. The sensor calculates the amount of storage Mb's that have aged, forming the sensor KPI.

  The SAVE_ALL sensor should be used as an overall trigger. Add your own tables by filling in the sensor settings text. Use transaction DB02 on your system to find the top consumer tables - and decide how long the information is required.

  With every reported subject, the report that can be used to perform housekeeping cleanup actions is also mentioned as a hint. So to action the savings, start scheduling jobs.

  Simply stop hanging on to aged data.

  The going price for an Mb is 30 cents per month. Every month. And not just on the production system.
  
  
  
  

• SAVER_BAL Business Application Log
  
  Business Application Logs (transaction SLG1) hold processing logs. Not just for errors, these logs are created by numerous processes. This sensor focusses on these logs, per object. A retention period can be applied, per object. And a FIXER report is available for this sensor. Simply schedule report ZSENSOR_FIXER_SAVER_BAL to automatically follow up on the AUTOFIX option on this sensor.
  
  
  
  
• SAVER_CD Change documents
  
  Change documents hold change logs. These are created for numerous objects, standard SAP and custom build. This sensor focusses on these logs, per object class. A retention period can be applied, per object class. And a FIXER report is available for this sensor. Simply schedule report ZSENSOR_FIXER_SAVER_CD to automatically follow up on the AUTOFIX option on this sensor.
  
  
  
  
• SAVER_DBTLOG Table change Log
  
  The DBTABLOG table holds change logs for tables, applied whenever the table is updated. This sensor focusses on these logs, per logged table. A retention period can be applied, per logged table. And a FIXER report is available for this sensor. Simply schedule report ZSENSOR_FIXER_SAVER_DBTLOG to automatically follow up on the AUTOFIX option on this sensor.
  
  
  
  
• SAVER_IDOC Idocs
  
  Inbound and outbound Idocs are created and processed, after which they become disposable. This sensor focusses on Idocs, per message type. A retention period can be applied, per message type. And a FIXER report is available for this sensor. Simply schedule report ZSENSOR_FIXER_SAVER_IDOC to automatically follow up on the AUTOFIX option on this sensor.
  
  
  
  
• SAVER_WF Workflows
  
  When a workflow or seingle step task completes it's processing, it becomes disposable. Workflows and their containers should never be the single source of information. The container is designed to reference existing documents and carry content that is relevant to the flow itself. As the workflow ended (status COMPLETED) it can be removed (with transaction SWWL). This sensor focusses on workflows, per workflow ID and/or single step task ID. A retention period can be applied, per workflow or task. And a FIXER report is available for this sensor. Simply schedule report ZSENSOR_FIXER_SAVER_WF to automatically follow up on the AUTOFIX option on this sensor.
  
  
  
  

Sensor controls

Sensors are very customizable creatures. It's behaviour can be customized to respond with a warning or an error (general settings). But it can also be set up to just report on KPI's without further action. In addition to that, sensors can be fine-tuned with settings that are relevant to only that sensor.

Sensors can be fine-tuned to respective requirements. This is done through sensor parameters of which there are 2 types:

1. The sensor parameter, a series of control settings
2. The sensor long text, a much more elaborate set of settings, available as a text.

The sensor general settings together with both types are considered controls for the sensor.

General settings

Settings that can be applicable to any sensor are called general sensor settings.

None of the general settings are mandatory, as defaults are available. It is however possible and even recommended to personalize sensors to what they do. Feel free to supply a new name to the "Dumps" sensor if they are about the dumps for today only. "Todays dumps" would be a suitable title.

The general settings include details like

• Title and UoM - these will appear as texts on the sensor tile and sensor full description.
• Warning and errorlevel - these will determine the sensor behaviour. The status of the sensor is determined with warning level and/or error levels.
• Delay - this controls how often the sensor should be checked. As it's pointless to have a sensor about yesterdays data redetermine the same results all day.
• Sequence - determines where the sensor is shown within the group.
• Documentation link - this will present a documentation link on the sensor tile and sensor detail overviews.
• Logging - controls the logging options. Makes sense for some sensors, makes no sense on others.

General settings - are specific to the sensor

General settings are called as such, because they are the same settings that can be applied to each and every sensor. They are very specific to the sensor though. Just like the sensor parameters (next paragraph) and unlike the sensor long text settings (which apply to all sensors with the same sensor type).

Sensor parameters

The sensor parameter is a short 1-liner that consists of upper-cased instructions for the sensor. A common example would be

DATING:10

Which instructs the sensor to select data from the past 10 days. Sensors can be added to a group on the board without limits - however there is one limit: the parameter settings for a sensor should be unique within a group. Thus no 2 sensors can deliver the same information in the same group. Makes sense when you think about it.

Feel free to compose a new group with the best of relevant sensors from other groups.

To find out what parameters are available on the sensor you want to use, simply use the F4 function on the parameters field (which lives on the Sensor settings editor). Only (and all) relevant parameters will be listed here.

Sensor variations

As a sensor can often be controlled with a parameter, a variation on your sensor can be introduced by simply copying a sensor with alternate parameter settings. A common example would be date-ranges. The sensor that is reporting on information from today (DATING:0), can also be set up to report on yesterday (DATING:1-1). And a third sensor could report on the week before (DATING:8-2) that.

The TIMING parameter

Some of the parameters require a bit more detailed explanation. The TIMING and DATING parameters are available for date-specific sensors. As we're not too interested in yesterday's news, these parameters allow you to control the time-frame in which the sensor should operate. When these parameters are not specified, the system will assume a sensible default.

Usually, there is only one of DATING and TIMING specified. An example:

TIMING:180

This means nothing older than 3 hours is selected.

TIMING:180-5

This means nothing older than 3 hours is selected and the last (most recent) 5 minutes are also not selected.

The DATING parameter

For dating, the same formatting is used. There is however - this thing called "today". The most common examples of DATING:

DATING:1

This means yesterday and today. The current day is almost always included in the selection.

For only yesterday (and not today) use this:

DATING:1-1

And if it's only today then use This

DATING:0

If a sensor throws errors in an item that can age, then simply fill in the DATING parameter with the number of days you want to look back. E.g. DATING:30. And add a backup sensor with parameter value DATING:120-30 for the old cases (90 days).

The DATING can also be used to select dates older that a given date. Some sensors work with a retention period, for which the following setup can be used:

DATING:-90

Specifies a date as 90 days or older.

Find sensor parameters

Use the F4 function on the parameters field on the sensor (first focus on the sensor in the settings editor).

Sensor long text

The sensor long text holds sensor settings that are applicable to all sensors of the same type. There is no limit to the settings, lower cased values are supported and there is usually a mechanism like ID or NAME in place to link the settings to a specific sensor from the board. The ID or NAME would need to be specified on the sensor parameters.

The documentation on the sensor long text is available only for sensors that use the long text. A documentation button is shown in the Sensor settings editor.

Note that this documentation is available only in English. And for those who will add their own sensors to the framework: the sensor long text documentation is derived from comments in your coding. Make sure you also add such comments - to serve our end users.

The (prehistoric) long text editor

The sensor type long text utilizes SO10 texts in the English language. As the actual contents of the settings is up to the sensor type logic, the sensor long text is the standard for these settings. Each text line is preceded with a line type, which is either /: or * . The /: for upper-cased values, everything else for regular text.

Versions

A product like the sensorboard is never completely finished and finalized. New sensors are created regularly at the customer site. Some of these sensors may me applicable for other customers as well, thus new sensors (sensor type logic) can be added to the suite over time.

The board itself may also be improved. As we are working with customer requirements, there may be requirements that can be useful for other customers too.

This overview is the version or release blog, briefly explaining what was added/changed with the release. When this page is called directly from the sensor board (click on version number), a version-check is done.

To do the check:

1. Click on the "Version ... " at the left-bottom of the sensor board main overview.
2. Set up a sensor with sensor type VERSION which reports on anomalies. The sensor also hosts a link to check the overall board.

Version check fails ? No drama ! Just a little extra checking when performing an upgrade.

Version check

A version number was passed, which is now checked to determine which current version is being used.The check code that was passed is "64E36029F9D95EB0061255241BB5CCCD467759BB", which is also displayed on the self-service sensor.

The check code was incorrect.

What does this mean ?

If the check was done directly from the sensorboard (SAPGUI, transaction ZEN) then the coding of the sensorboard framework has been changed (is no longer original). There may be good reason for the changes, but an upgrade will overwrite custom changes.

The self-service sensor from the board will report this and the actual altered component is listed on the sensor.

Version overview

Version	Added features
2025-03 unreleased	Trial rounds on letting ChatGPT assist in translating the application. Turns out that ChatGPT successfully supplied the missing 4 languages and applied it directly in JSON. The JSON results could then be uploaded. Editor functionality for translations (internationalization). Backup for sensor settings, for groups, for the whole board and automatic (into a table) Alias support, where an alias of a sensor type can be made available in about 12 lines of coding. Introduction of the GRIP ON SPACE sensors, which calculate the Mb's that can be freed up based on supplied retention periods. A main sensor plus 4 detailed sensors (Business Application logging, Idocs, Change documents and DBTABLOG logging). Introduction of the FXR autofix reports for BAL, Idocs, change documents and DBTABLOG logging. Introduction of BEL - Business Event Logging - initial version. Sensor(s) to be added later. Licence checker sensor SUIMSLEEPERS was enhanced. It can now monitor user activity on tables of your choice and KPI can also be reported in Euro. ...
2025-01	As preperation for the first main go-live with the sensorboard - lots of effort was put into delivering a good solid product. The available documentation made available as website (sensorboard framework and individual sensors) Internationalization: addition to the translation setup, which now involves a translation table. Translating existing texts or adding new texts in NL, EN, DE, IT, FR and ES. Next release will also contain an editor. A boardfeeder example program for creating a series of sensors through Bapi. Trial rounds on Bapi-sensors. Support for indexed data for sensors (like the AEX index, a deviation percentage measured over a period of time) Content of the sensor report (as displayed in a popup and sent out to email receivers) was redesigned. The board was operational and active search on problems was done. Numerous minor details were addressed. Added click functionality on the board. With ALT-click, the sensor main data is displayed as an ALV report.Using CTRL+click on a sensor will open the sensor editor. And CTRL+ALT+click will log it's details so comparison to earlier saved logs can be done. General-use sensor for indexed data (as above, but in free-style sql definitions - no Abap) Sensor for Remote access to the boards from other systems. This sensor type uses the errors from another board as it's KPI.
2024-11	After full design and development rounds, the framework was applied to a new system where it was demonstrated to the customer. Installation time under 2 hours. First version-managed release.