on ‎2013 Jul 19 2:57 PM
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.
Request clarification before answering.
Hi guys,
Again working with POB and trying to add some new Business Object Types to the POC FACADE; these are Plant Maintenance objects like BUS2038 Maintenance Notification or BUS2080 Service Notification, for example.
1. I select an existing applicable SOA BO Type, and then try to add this as an entry to the "Business Object Type" view. I was expecting that these would not need to be named as Z-objects as they are SAP standard, but I get a message about the wrong namespace.
Is it normal that i would need to create a ZBUS2080 entry, or should I be able to use BUS2080?
2. The other areas that is unclear is mapping the "Map BOR Event to Task" entry. For a SAP standard object how do I know what Events (like CHANGED or CREATED) are available? It all seems to be very trial and error. Can I use SWEC to examine the events for objects like BUS2038 and relate those to the BOR Events?
It would be great to have some more custom POB examples available, as the provided standard POC examples don't help when we need to add new Facade types etc.
I am working in ECC6.0 with EHP7
Thanks,
Andy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Andy,
hope this will help you:
1. when you enter a BO Type from the SOA BO Type list into the Business object Type view you get a warning (yellow) that you can ignore, just go ahead with a <return>. When you enter own/custom objects - not yet contained in the SOA BO Types list - you should use the customer namespace to avoid conflicts. Note we have only 5 characters here, and are normally not using the BUSxxx ID here. But you can map it in POC_BOR (I think you have found this). [The BO Type is a more general concept than the BOR object type].
2. In transactions like SWO1 you can browse the existing BOR objects with their defined events.
The availability of an event in the BOR repository however does not automatically mean that is automatically thrown at runtime (that means when you expect it). There may be configuration or specific conditions required to activate it. Therefor it is necessary to run a BOR event trace before using BOR events and check what BOR events are actually available. You can do this using transactions SWELS and SWEL.
For missing events you can still use the direct event API, the generic BOR event or custom BOR events. You find the information here:
To find another sample for a process instrumentation, you may check this document:
Best regards,
Bernd
Thanks Bernd,
That did help me - using SWEL is a key step to getting the right events.
One problem I had was with the way that BOR objects work in ECC was not intuitive in terms of normal OO behaviour - I was expecting that I should refer to the ZBUS2080 object or class, as that had the custom events defined. In fact I needed to reference the BUS2080 object, and that fired the custom events in SWEL and POB.
Andy
| User | Count |
|---|---|
| 8 | |
| 4 | |
| 4 | |
| 4 | |
| 3 | |
| 3 | |
| 3 | |
| 2 | |
| 2 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.