cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Process Observer Discussion

JChristophNolte
Product and Topic Expert
Product and Topic Expert
0 Likes
9,124

This thread is dedicated to questions and discussions around the Process Observer component that is part of Business Suite.

Process Observer is used in different scenarios, including and prominently with Operational Process Intelligence.

For details on what Process observer is see here.

View Entire Topic
itsrahulmehta
Explorer
0 Likes

Hi All

I was looking for some blog posts on Process Observer and found this. Now I am pretty sure that experts here will provide answer for my queries

Here is what I want to understand

1. We have procure to pay process running between ERP and SRM. Both the systems are separate installations and its not Business Suite

2. I want to capture PR create and update events in Process Observer. Is PR creation or update will raise BOR events as part of standard process or I need to enable this in ERP system?

3. If BOR event is not possible then can I call direct event api through some BADI to log these events in Process Observer?

4. In SRM for most of Business Objects, we have BOR events. Does this mean we just need to enable Process Observer in SRM and we are good to go or there are other settings required?

Regards

Rahul

JChristophNolte
Product and Topic Expert
Product and Topic Expert
0 Likes

Hi Rahul,

good that you found us.

  1. This is not really a question, right?
  2. We deliver a template for procure-to-pay; it should be in your ERP system. In the process definition (TA POC_MODEL) check process definition PROCURE_TO_PAY (maybe this is not in your client, it's delivered as template content, which is available in client 000; maybe you can get that copied into your test client). - When you look at the content, you can see that the purchase order (001) is mapped to BOR object BUS2012 and the events CREATED, CHANGED and RELEASED are available and mapped to tasks (001-21, 001-88, 001-62) accordingly. The process definition also contains more activities:
    • Create Purchase Requistion (Item)
    • Post Goods Receipt (Item)
    • Cancel Goods Receipt(Item)
    • Process Invoice Verification (Item)
    • Cancel Purchase Requsition (Item)
    • Change Purchase Requistion - Purchasing Group
    • Change Purchase Requisition
    • Release Purchase Requistion (Item)
    • Create Purchase Order (Item)
    • Change Purchase Order (Item)
    • Delete Purchase Order (Item)
    • Approve Purchase Order
    • Send PO (Header)
      In my understanding these events are always raised and do not need to be activated. You need to set up Process Observer so that the events are consumed (see our blog post about setting up Process Observer). There is also a separate blog post on specifically procure-to-pay: Instrumentation for Procure-to-pay process on item level in Process Observer

  3. Yes, there is an API to directly raise events for Process Observer, it is explained in details in blog post Process Observer (POB) Direct Event API for Logging Processes from SAP and Non-SAP Systems

  4. Yes, you're good to go. Set up Process Observer (activation, see above). Check if the required events are raised (that's standard BOR; use e.g. SWEL to see which events are raised). Map the events to tasks (POC_FACADE) and create a process definition (POC_MODEL). Don't forget to check your process definition (POC_MODEL_CHECK).

Let us know if you have further problems - or how this has helped you.

Best regards & good luck,

Christoph