Skip to Content

Hi,

 

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.

 

SLD.png

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

 

PMA_Customizing_full_with_setup.png
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’.

 

/wp-content/uploads/2011/09/poc_active_81982.png

 

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.

 

/wp-content/uploads/2011/09/job_scheduler_81995.png

 

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

 

POC_JOB_Release.png

 

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’:

 

/wp-content/uploads/2011/09/sim_def_edit_81997.png

 

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:

 

active_BOR.png

 

Now you can:

 

Run the Setup Check

 

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

/wp-content/uploads/2011/09/check_setup_82002.png

 

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.

 

/wp-content/uploads/2011/09/check_setup_result_82010.png

 

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.

 

/wp-content/uploads/2011/09/check_setup_monitor_82011.png

 

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.

To report this post you need to login first.

4 Comments

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

  1. Kevin Wilson

    Bernd,

    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?

    Thanks

    Kevin

    (0) 
      1. 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?

        Thanks,

        Markus

        (0) 
        1. Bernd Schmitt 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

          (0) 

Leave a Reply