Skip to Content

Abstract


This document explain the basic introduction of Usage Procedure Logging, its data flow and some example of its use cases


1. Introduction

UPL is a Kernel based logging technology with no measurable performance impact and available in any ABAP based system based on the core functionality of SAP Coverage Analyzer. It is used to log all called and executed ABAP units like programs, function modules down to classes, methods and subroutines.

UPL result will be more accurate compared with workload statistic (ST03N) because UPL is able to detect submitted programs or dynamic calls additionally. Also you can detect the usage of any ABAP based unit down to subroutines which will give you the transparency about used modifications, user exits, classes and also single method executions.

2.     Objective

The objective of this document is to give basic understanding of Usage Procedure logging and its capability.

3.     UPL Data Flow

3.1    UPL Data Flow for Managed System


MANAGED SYSTEM FLOW.JPG


Once the daily job is finishes, the extractor framework from SAP Solution Manager will pull the data from the Managed System into the SAP Solution Manager BW info cube.


3.2       UPL Data flow for Solution Manager


SOLUTION MANAGER FLOW.JPG


4. Quick Check for Validation of UPL activation


4.1.Extractor Framework Activation Check

You can check the same in SM_WORKCENTER –> Administration –>Infrastructure –> Extractor Framework –> Filter *UPL*


EXTRACTOR.jpg


4.2.Managed System Check

  • /SDF/UPL_CONTOL Activation check and /SDF/SHOW_UPL : Direct online view
  • RFC Function Modules

     /SDF/UPL_GET_USAGE                    :               Read UPL data for defined days

     /SDF/UPL_SYSTEM_STATUS            :               UPL availability

     /SDF/UPL_CHECK                            :               RFC for quick check of UPL availability

4.3.Solution Manager System Check

BW Access cube (0SM_CCL_UPL  : Info Provider 0SM_UPL)

Few Predefine UPL BW Queries by Transaction RSRT2

  • 0SM_CCL_UPL_CUSTOBJ_AGGR       :               CCL Customer Objects UPL aggregated
  • 0SM_CCL_UPL_MONTH                      :               UPL monthly Report
  • 0SM_CCL_UPL_CUSTOB                    :               CCL Custom Objects UPL
  • 0SM_CCL_UPL_OBJM                         :               UPL Data for Object
  • 0SM_CCL_UPL_CUSTOBJ                  :               CCL Customer Objects UPL
  • 0SM_CCL_UPL                                    :               UPL Report

You can make your own query on info cube and predefine query.

5. Example of Few Use Cases of UPL

5.1.Solution Documentation Assistant

Within the Solution Documentation Assistant, a new check step type is introduced to access UPL usage data.

The tool Solution Documentation Assistant (SDA) is able to evaluate UPL data in check item, only if there is at least one month of data available. The BW will aggregate the daily data slices to a monthly aggregate.

You can create UPL check step with help of subtype like Report, Method or Functional Module. Assign this check step to analysis project process step. This check step plays an important role to identify customize report, program or object.


CHECK STEP.jpg


In SDA Analysis detail of your analysis project, at process step level you will get the result of your check step.


CHECK STEP RESULT.jpg


5.2.Business Process Change Analyzer (BPCA)

The BPCA can make use of the UPL data sources to improve the automation of the technical bill of material (TBOM) creation process. Using the UPL, it will enable to create a new “semi-dynamic” TBOM automatically for business transactions of the customer. Here system will first look at the source code of a business transaction, start collecting all the technical objects, and then it will filter the object list for only the used call stack elements as collected in the UPL data.


TBOM.jpg

You can create a semi-dynamic T.BOM using UPL data for your project in following manner

Go to TBOM utility via Test Management –> Administration.

BPCA_1.jpgBPCA_2.jpg

Once your job get finished you can check the created T.BOM in SOLAR01 –>Business Process Step –> Transaction Tab –> Attribute

BPCA_3.jpg


Please click on display content to check T.BOM

BPCA_4.jpg

6. Conclusion

This document explains basic information of Usage Procedure Logging (UPL), its capability, data flow and some use case examples, which can help the user to start work with UPL. You will get detail information by referring to the document Usage and Procedure Logging (UPL) for set up guide, system precondition, troubleshooting, FAQ etc.

About Author :

He is part of TCS RunSAP CoE team having expertise in SAP Solution Manager functionalities from ALM & RSlaF like Solution Documentation, SoDocA, Test Management, BPCA, BPMon, BP Analystic JSM etc.

To report this post you need to login first.

7 Comments

You must be Logged on to comment or reply to a post.

  1. Bjoern Panter

    Hi Ashish,

    nice desciption of the UPL process flow. Under chapter 3.2 the screenshot you took from the SAP slidedeck had a small bug we already fixed. please ensure at the bottom that the cubes are named Weeks/Months/Years instead of twice the months.

    Also remark the data BW design will be changed with SP12 to a much better and improved design.

    Regards

    Björn

    (0) 
  2. Yvonne Jutz

    Hello,

    very helpful, but can someone tell me which job in Solution Manager collects the data for cube 0SM_UPL?
    We have each day four requests in this cube, always a different time.

    Regards
    Yvonne

     

    (0) 

Leave a Reply