13

F+O workflows for Project Budgets, PO Approvals etc. are limited to a small set of fields to be used as workflow conditions e.g. Project ID. All of which can not be delineated in the Project module to indicate the nature or type of Project which can be a required in respect to who and what approvals are required. E.g. a capital project may have additional approval steps / controls compared to an internal project.


As there is only 1 Project ID number sequence, this field can not be utilized as a workflow condition to dictate workflow branches based on the nature of the Project. The only viable work arounds are to either have a manual Project ID number sequence and inform users of Project ID naming conventions which they will need to enforce on their own or create a Project Group financial dimension.


In respect to the Project Group financial dimension, this is not an ideal candidate for a financial dimension segment as we can dictate postings based on Project Groups and have dedicated accounts for capital v. internal v. revenue etc.


Idea: Utilize the same functionality / logic as Fixed Groups to allow for the definition of unique number sequences by Project Group. This would both enable the use of Project ID in workflow configurations beyond simply 'Is Project? condition' and eliminate the need for customers to create a Project Group financial dimension simply to add improved workflow capabilities.


Alternatively - Add the Project Type field into Project Budget and Purchase / Sales Order workflows

STATUS DETAILS
New

Comments

A

Type in the Idea: Utilize the same functionality / logic as Fixed Asset Groups****

Category: Project Accounting