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.
Hello Christoph,
in my workings with SAP PO I have come across a Problem I need to fix.
I have activated SAP PO on two different Systems within my companies landscape. one being restrictive and one being more open.
The one bein more open works without any Problems. The one being more restrictive does not let me Access my newly created BFRplus Rules within the Webdynpros. I have set up both Systems exactly the same way. Both Systems let me use "Maintain BFRplus Rule for Process Status in Process Orchestration" after clicking the "Display BFRplus Rule" in POC_MODEL for the built in processes. If i create a custom process although the ID is being generated and i find it in the table view the webdynpro is not able to access it.
Can you tell me the process of object id Generation and the accessing of it? Are there known Errors? Is there something else required to create These IDs?
Just let me know if there are more Information needed.
Thank you for your help on this interesting Feature of sap!
Best regards,
Marc
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Bernd,
thank you for your answer, SU53 did not Show anything but it was still a Problem of R&A.
In my process of documenting processes I have come up to another Problem/requirement.
In a Sales Order Process I only want SO´s from a selected plant.
My Idea was to assign a BRFplus Rule to the "Crea SO" Activity that checks if the plant is the one I want in this SO if true continue; else Exit.
Is this the supposed way to do so? Are there any easier ways?
BR,
Marc
Hi Marc,
yes, you can implement the BRFplus rule of the 'Task association' in the process definition, as you describe. For the cases where you want the task not to bind, clear the event in the return structure.
As an (easier?) alternative you may also implement the BAdI 'Rule based binding of task to a process activity' (POC_MAIN_TASK_BIND). Implement the interface method in ABAP. Here again, if the task should not bind, just delete it from the change structure CS_TASK_ACT_PROC_IN_BIND.
You find the BAdI here: POC_CUSTOMIZING (transaction) -> Business Add-Ins.
All BRFplus rules in Process Observer have equivalent BAdI-methods that allow alternatively the implementation in ABAP.
Hope this helps you,
Bernd
| User | Count |
|---|---|
| 9 | |
| 5 | |
| 4 | |
| 4 | |
| 3 | |
| 3 | |
| 2 | |
| 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.