Skip to Content

Linking the Application Log with corresponding background job

You surely know this problem, you are executing some important job which is writing interesting information in some spool file and/or an application log file. At the end of an hour-long processing you would like to understanding if the complete job processing was successful or not. What can you do? Scroll through 50 pages of spool file?! Find the right application log via transaction SLG1 which is often very difficult if similar processing took place in parallel during the same time frame?! Anyway it is quite cumbersome and tedious to find a handful exceptions raised by the background job while there might be thousands of successfully processed items.

This blog describes what can be done in order to link application log information with the corresponding background job and how it is possible to navigate from the background job to the respective log file(s).

Technical prerequsisite

As a minimum requirement your respective SAP backend system needs to run on SAP Basis 7.00 or higher. Then you can either implement SAP note 1706526 “BAL_DB_SAVE: save Loghandle also in Batch Context Table” ( or you might have the right support package level. The SAP note is valid for

Software Component          Release                             Package name

SAP_BASIS                             700                         SAPKB70015 – SAPKB70026

SAP_BASIS                             701                         SAPKB70101 – SAPKB70111

SAP_BASIS                             702                         SAPKB70201 – SAPKB70211

SAP_BASIS                             710                         SAPKB71003 – SAPKB71014

SAP_BASIS                             711                         SAPKB71102 – SAPKB71109

SAP_BASIS                             720                         SAPKB72002 – SAPKB72007

SAP_BASIS                             730                         SAPKB73001 – SAPKB73007

SAP_BASIS                             731                         SAPKB73101 – SAPKB73103

Configure the linkage

You have to configure the Criteria Manager which was already mentioned in previous blogs( and So you call transaction CRIT or report CRITERIA_MANAGER and navigate to tab strip Criteria Types. There you click on ‘Add’ and define new criteria type as follows:

Type definition:

     Criterion Type: APPLOG

     Description:    Auto-linking Applog-Handles for jobs

Field definition:

     Field     Description

     CLIENT    Client

     JOBNAME    Job name

     USER    User

Click on ‘Create’ or press ‘Enter’.

Criteria type.png

After creating the new Criteria Type you switch to tab strip Criteria Profiles tab and add a new Criteria Profile of type “Auto-linking Applog-Handles for jobs”. For this type: Add a new criterion specifying for which jobs/client/user combination the Auto-linking Applog-Handles should be activated. The selection in the screenshot below means, that every job created by any user will link its application log information (if a log is written at all).

Criteria profile.png

Activate the newly created profile.

Activate profile.png

After the activation every job that fits to your given criteria will write its log handle information in table TBTCCNTXT with reference type BTC_APPLOG_HANDLE. In order to be able to transport your configuration you have to apply SAP note 1709298 “Criteria Manager: No transport link for criteria types”


Navigating from background job to Application Log file(s)

So what’s the benefit once your background jobs are linked to the corresponding log file? If you naviagte into transaction SM37 and see the list of background jobs that interest you, then you can select one of those jobs and via the menu Goto > Application Log you can directly access the corresponding Application Log file(s).

Navigation job to log.png

In our case you can see that the job has actually written more than one file. Within the application log you can then filter out green and/or yellow messages and only focus on red ones for further analysis.

Log file.png

So with this linkage it becomes much fater and simpler to find out application related error messages that were raised during background processing. You will see that several new SAP APO related key figures (developed for Business Process Analytics and Monitoring in SAP Solution Manager) will make use of this linkage. The upcoming ST-A/PI 01Q* will contain several new exception key figures related to the most typical DP, SNP and PP/DS jobs (see New keyfigures: Analyzing/monitoring exceptions from APO planning runs).


Further reading

Frequently Asked Questions about Job Scheduling Management are answered at

Related previous blogs:

Frequently Asked Questions about Business Process Monitoring and Business Process Analytics are answered at and respectively.

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

You must be Logged on to comment or reply to a post.
  • Hi Volker,


    Very Nice blog, as you mention “configure the Criteria Manager”, is that mandatory? We are using thirdly party tool for scheduling the jobs and I don’t want to activate Interface XBP 2.0 also restriction on users.


    I want to use this feature for one of job “RSAUDIT_SYSTEM_STATUS”. I configured your mention steps but not got any log info.




    • Hi Pravin,


      yes, the Criteria Manager configuration is mandatory. Otherwise the SAP system does not know for which jobs you want to have the linkage stored away.

      I don’t get your point about the XBP interface. If you are using a 3rd party scheduler your XBP interface has to be activated anyhow as every scheduler is supposed to schedule via XBP.


      Kind Regards


  • Hi Volker von Gloeden,


    All your blogs related to BPM was much interesting, I have small doubt, recently I gone through the product POB “Process observer”.. it is also has the feature to monitor the business  process life cycle, Process Observer


    Could you please help us to understand the difference between Solman Business process management and POB,


    if can I am expecting some value proportion for Solution manager BPM,


    Please share.





    • Hi Jansi,


      Business Process Analytics and Monitoring in SAP Solution Manager are complete products that come with out-of-the-box content (key figures for all SAP Business Suite components (ERP Logistic and Finance, CRM, SRM ,SCM). So you can use BPMon for monitoring and alerting on technical (jobs & interfaces) as well as application specific exceptions in your business processes (SAP and non-SAP). You can use Business Process Analytics in order to analyze the application specific exceptions, identify systematic issues (configuration, user handling, master data etc.) and resolve them so that your processes improve.


      Process Observer is more like a flexible infrastructure where you log additional information. This logging data allows more flexible lead time calculations. But you have to enrich this log data  with context information (e.g. sales org, plant etc.), like you bring POB data together with existing BW data. POB data can be consumed by different applications like BW, HANA or Business Process Analytics.


      Kind Regards


      • Hi Volker von Gloeden,


        Thanks a lot for clarification, I am perfectly fine with Business process monitoring concept, where I have done couple of implementation. my current problem is about understanding of POB and relate with BPMon,


        —> in BPMon also we have trend analysis, which stores the data in BI and gives dashboard kinds of reporting, is it?


        —> I read the blog  Monitor Sales Order Processing with Process Observer for Built-In Processes (POB) by  Bernd Schmitt … It looks same as BPMon and find it contains more complex configuration too, where as in Solman the same can be done very simple… ( This is my view, if wrong please correct). 


        Hence please clarify again POB and BPMOn are two different tracks….. both used for two different cabaplities.. or POB is doing same task as BPMon in addtional to that it is handling lots of more information.  if can, any where i can get the use case of POB.


        Thanks again.




        • Hi Jansi,


          POB and BPMon/Analytics are different. POB does not provide out-of-the-box key figures. POB does not support technical monitoirng (jobs & interfaces). POB allows single instance tracking and every instance that shall be monitored needs to be configured accordingly. BPMon/Analytics is not tracking single instances but provides milestone measurements where we list all backlog documents.

          Generally speaking BPMon/Analytics is a foundation of measurements that every customer should do.

          POB is then an infrastructure that can provide answers to additional questions that might occur and that BPMon/Analytics cannot answer, e.g. end-to-end cycle times of a process like Order to Cash. BPMon/Analytics is “only” providing lead times for parts of the process.


          Kind Regards


  • Hello sir,

    I need to Create one class which trace any customized t-code, step by step and i need to display that traces with the application log, I have created One T-code for Monitoring Status for  Delivery and after that it will go for Shipment Create.

    Suggest me how to implement this class