Skip to Content
Author's profile photo Bernd Schmitt

Setup of Component Process Observer for Built-In Processes



This is the third blog post about Process Observer. The previous posts of the series have given an Introducing New Component: Process Observer for Built-In Processes (POB), described the Architecture of Process Observer for Built-InProcesses (POB).

It is now time to tell you how to actually activate and set up the components. I will shortly cover how to set up the component for usage in a single system, and how to run some first setup checks. Setting up Process Observer for cross-system federation and monitoring will be explained in a later blog.


Prerequisites: Installation and Activation of Business Function


1. Installation of Business Suite Foundation Layer


As we already explained, you need to have the appropriate version of the SAP Business Suite Foundation Layer installed in your Business Suite product:


  • Business Suite 7 (for example, SAP ERP 6.0 EhP 4, SAP CRM 7.0, SAP SCM 7.0, SAP SRM 7.0) required components:
    • SAP_BS_FND 701 SP 11


  • Business Suite 7i2010 (for example, SAP ERP 6.0 EhP 5, SAP CRM 7.0 EhP 1, SAP SCM 7.0 EhP 1, SAP SRM 7.0 EhP 1) required components:
    • SAP_BS_FND 702  SP 06
    • SAP_BASIS 702  SP 08 (or note 1488051)


  • Business Suite 7i2011 (for example, SAP ERP 6.0 EhP 6, SAP CRM 7.0 EhP2, SAP SCM 7.0 EhP 2, SAP SRM 7.0 EhP 2) required components:
    • SAP_BS_FND 7.31 SP 01


To find all product versions containing the Business Suite Foundation Layer, you can ask us or check the product information in your System Landscape Directory.



Information on Product Versions containing SAP Business Suite Foundation Layer 702 in the SLD.


2. Installation of Notes and Corrections


Please install the latest Support Package available for your SAP_BS_FND version.

Check and install further notes relevant for Process Observer checking topic area CA-EPT-POC. You should also implement note 1605407 before going live (if applicable for your software release).


3. Activation of Business Function


Activate Business Function FND_EPT_PROC_ORCH_1 “Infrastructure for Core Process Monitoring & Analytics” to use Process Observer.

This also makes the implementation guide (IMG) entries for Process Observer visible. The Process Observer IMG  can then be found in the reference SAP Customizing Implementation Guide under the path:


     Cross-Application Components -> Processes and Tools for Enterprise Applications -> Process Orchestration for Built-In Processes


Process Observer Entries for Setup in the Reference SAP Customizing Implementation Guide.


An alternative way to invoke customizing for Process Observer is to enter the transaction code POC_CUSTOMIZING.


4. Add user role for authorizations

To be able to activate Process Observer, it may also be useful to have a copy of composite role SAP_POC_ADMIN with appropriate authorization settings in the profile assigned to your user.


<< Note on using Process Observer in S/4HANA: Process Observer is part of software component S4CORE and the Business Function is on setting ‘Always On’! >>



Activation of Process Logging (Master Activation of Process Observer)


To activate the logging and the processing of application events via Process Observer in your system client, you have to perform two steps:


1. Activate Process Logging


Execute Activity ‘Activate Process Logging’ in the section ‘Parameter Definition’ of the Process Observer customizing: Set Parameter POC_ACTIVE to ‘X’.




As a result all BOR events registered in Process Observer will be cached in the transparent table SWFREVTPOQ.


The active BOR events can be reviewed in the customizing activity ‘Check Process Monitoring Events for Bus. Object Repository’. As long as no process definition was activated, nor BOR event should be marked as active here.

To ensure the BOR event cache table is processed and cleared, you need to:


2. Schedule the BOR Event Processing


Perform the activity ‘Schedule Business Object Repository Event Processing’ and select the scheduling interval for BOR event processing for Process Observer.




As a result, you receive information about a new scheduled job:




The job ensures the cache table is processed and cleared. Note: If you don’t schedule it, you risk to accumulating data continuously in the cache table.

You can manage this job in the job scheduler (SM36). You need to activate Process Observer and schedule the job for event processing for each relevant client.


You are done setting up Process Observer now. That was not too much effort, right?

You may wish to check if the setup is successful now, so you need to:


Activate Process Definition for Setup Check


For the setup check, one process definition is required that needs to be activated. Call transaction POC_MODEL and for process definition POC_SIM3, change the log level to ‘Standard logging’:




If you cannot find model POC_SIM3, make sure that the default customizing is copied to your client from client 000.

In the IMG activity ‘Schedule Business Object Repository Event Processing’ you find the corresponding BOR events activated:




Now you can:


Run the Setup Check


To perform the setup check,run transaction POC_CHECK_SETUP. Enter Number of Events ‘1’ and execute.



This will throw a series of BOR events for a pair of test objects ‘POC_OBJ1’ and POC_OBJ2’ that are delivered as part of Process Observer.




Open the process monitor using transaction POC_MONITOR, to check whether a process instance was logged for process definition ‘POC: Simulation Model 3 – POC Objects’. Execute the search with the default settings. When there is only one process instance found, you can navigate to the process instance details screen. Depending on your interval setting for the job scheduler above, there may be a short delay between the execution of the setup check and the process visibility in the monitor.




Congratulations if you see this, BOR events have been thrown and processed by Process Observer! Now you are ready to create process definitions to monitor real application processes.


The next blog post explains how to use Process ObserverMonitor Sales Order Processing with Process Observer for Built-In Processes (POB). After this, my colleague Jens-Christoph Nolte will give an introduction into Create Process Definition for Process Observer for Built-In Processes (POB) with Process Observer.

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Kevin Wilson
      Kevin Wilson


      What is the best way to copy the POC_SIM3 model over from client 000 to our dev client? Do we simply manually create a transport and link the table entries from POC_MODEL?



      Author's profile photo Bernd Schmitt
      Bernd Schmitt
      Blog Post Author

      Hi Kevin,

      you need an R/3 connection to client 000 then you can use the menu functionality in Utilities -> Adjustment to copy entries. More details are explained in this article about SAP Customizing tools: SAP Customizing Tools - frequently asked questions - ABAP Development - SCN Wiki

      A transport however should also work.



      Author's profile photo Markus Greutter
      Markus Greutter

      Hi Bernd,

      I followed the steps described in the wiki but it only copies the header entires and not the entries below in the view cluster. Is there a trick to copy the complete customizing for POC_SIM3?



      Author's profile photo Bernd Schmitt
      Bernd Schmitt
      Blog Post Author

      Hi Markus, this is a standard SAP functionality. You have to copy table by table, view clusters are not specificly supported it seems. Packing viewcluster enties to a transport in client 000 and import to the target client seems as another viable alternative. Regards, Bernd

      Author's profile photo Phuong Truong
      Phuong Truong

      Hi, I have follow the instruction, however, I don't see the same screen when execute the last step POC_MONITOR. It shows 'No data found for the entered criteria'. Do you have any idea on how I can solve this? Thank you very much!

      Author's profile photo Bernd Schmitt
      Bernd Schmitt
      Blog Post Author

      Hi Phuong,

      please check the following:

      1. Have you created and activated a process definition for monitoring, see for example:
      2. Do the selection criteria of the process monitor match your needs: it starts with the selection of processes that started within the last one hour...
      3. Process observer will monitor only new processes (since activation of the process definition). Older data could be transferred using a custom report.
      4. If you do not see processes, do you at least see the monitored events/tasks (check in transaction POC_TASK)

      Hope this will help you further.

      Best regards, Bernd

      Author's profile photo Hartmut Engel
      Hartmut Engel


      in the standard delivery, there are 2 P2P processes.



      Only the latter one seems to start, but also does not continue after the PO creation process. Id doesn't react on the MIGO nor on the MIRO.

      Please help to clarify.


      Kind regards


      Author's profile photo Bernd Schmitt
      Bernd Schmitt
      Blog Post Author

      Hi Hartmut,

      we rather recommend to go with the PROCURE_TO_PAY process definition rather than with PURCHASE ORDER PROCESS. The latter was more intended for illustration purposes at the very beginning.

      A documentatio of PROCURE_TO_PAY can be found at: