BPF in Embedded BPC with External Characteristics concept for BPF
An important tool to structure and monitor the course of planning is the business process flow (BPF), which has to be created in the BPC Web client. An advantage of the business process flow is that the planner is guided through the given process steps. The supervisor can see at any time how far the planners are and when planning should be finished. Automatic messages with status change are possible.
It´s possible to integrate the reviewer concept to the business process flow. The reviewer could be a business user who has to check the quality of the plan data before the next process step is executed by all planners.
Usually in standard BPC, we will have Properties called Performer and Reviewer in Costcenter dimension( Driving dimension). From this driving dimension we will specify the members who is going to be an performer and reviewer for the each budgeting approval levels.As per the business process flow, a log on user can only see the activities they are associated with, that is, for which they are assigned as owner (or performer) or reviewer.In the Process template Activities part, we will be defining those performer and reviewer since we have it in dimension level.
Instead having costcenter dimension in standard bpc, for embedded we have info-object: /ERP/COSTCNTR .Since the infoobject(characteristic) /ERP/COSTCNTR doesn´t contain an attribute field for the owner, we need to create custome info-object with attribute Owner i.e. Custom”Z” infoobject with name of ZCOSTCNTR and need to add new attribute for Owner or Performer.
Note: 2 attributes need to created (Performer and reviewer) and add it in ZCOSTCNTR.
Now you have both performer and reviewer in infoobject(ZCOSTCNTR). Then you need to do masterdata maintenance by adding up the performer id’s and OwnerId’s in their respective attributes. so you can use this attributes in BPF to assign the Performer and reviewer in Activity part.
If you don´t use an internal characteristic of the real-time InfoProvider /ERP/SFIN_R01 like /ERP/COSTCNTR, and because you don´t want to complete this field with an owner and reviewer property, you can use the same external characteristic like ZCOSTCNTR in driving dimension, where you can see your both performer and reviewer in the External characteristics dimension.
So this is how you can require and the need of external characteristics to be used in BPF to assign approvals.