This blog is part of a blog series.


Scope

The set of work-statuses if defined for data entry in our BPC ‘unified’ model.

Role

LOB expert

User interface

BPC admin UI (HTML5)

In the administration UI we open the ‘Work status’ feature’ and create a work-status for the model we created earlier (00:15). First we add a new workstatus ‘In Process’ with appropriate name and description. Since this is the main data entry status, it shall be controlled by the owner who is also allowed to enter data (00:42).


Subsequently we add two more statuses, ‘Sent for approval’ (00:57) and ‘Approved'(01:33), the former controlled by the data owner with no further data entry, the latter controlled by the manager without the ability to overwrite the plan data. The data ownership is defined per country, which is why TECOUNTRY is picked as owner dimension (02:09). Within this dimension we use the only hierarchy to derive the relation between owner and manager. Owner and team responsibility is picked from the attributes TEOWNER and TETEAM (02:22) which we had seen earlier in the EDW model definition. For every base level member of the hierarchy the data owner is taken from these attributes. The manager is taken from the member attributes of the parent member in this hierarchy.


In addition we pick additional dimensions ‘calendar year’ and ‘version’ which allow more fine granular status setting, but do not control the ownership (02:52). Finally we enable the work status (03:07) and deactivate the option to push e-mails on status change. With that we have the status sequence defined that will be used later on to reflect the progress of planning and controls the input enablement.



To report this post you need to login first.

Be the first to leave a comment

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

Leave a Reply