-
Project Budget Control
Description of problem: Customer has the following business scenario: The goal is to enforce top level budget control with ability to overrun on the project budget lines amount. As such, Subproject budget should allow overruns, but not beyond the Top Project Budget. Engineering team explanation: The Budget control setup under every Project is specifically for it only. It invalidates the main setup from the Project management and accounting parameters which are applicable for all the projects. So as it is in your scenario the Budget control setup of every subproject invalidates every other setup for Budget before that or in other words said: the “Disallow overruns” of the main Project is no longer applicable for its subprojects as their Budget control option is changed to “Warn of overruns”. User would like to have the option to enforce top level budget control with ability to overrun on the project budget lines amount. -
Calendar's view
Description of request:
Customer would like to be able to change the calendar's view in the system.
For now there is no setting/feature/option in the system for changing or customizing the calendar's view and it's possible only to see specific dates and years.
Customer's request is to have the opportunity to see week number too. As this would be more efficient for their work process.
-
Project Invoice Customer Name
Business Scenario: The system takes the Delivery name of the Address instead of the Customer name. This is confusing for Customer as the expectations are that the customer name on the Invoice comes from the customer name, not from the Delivery name.
Request: To change the path from where Customer name on the Invoice to comes from the Customer name in the system.
-
Budget control configuration for Work orders
Business Scenario: Customer inserts numerous work orders per day which automatically creates projects where there is budget control. They can be opened and closed per the same day. It is not possible to insert project budgets for all of them. It was not acceptable to turn off the project budget control as it is already used for the other departments. That is why they need the work order journals to be validated by the Budgeting module with the Budget register entry.
Request: Work orders journals to be included and validated by the Budget control configuration.
-
Project stage to Finished after project elimination
Business scenario: After the project is eliminated, the expectations are not to be able to post against it as it is already finished. For example: the project starts on 01 April and will end on 30 June which means it will hit 3 financial periods. It is not possible to consider the revenue and expenses per period, so the option of WIP transactions is coming here to post expenses and revenue as a WIP and after completion of the project run the estimation and elimination process for transferring from WIP to actual sales and expenses. In this stage the project is considered as a finished project, and there shouldn't be any posting related to it. But if there are received any new transactions and that must be posted, the option of “reverse elimination” will be used to re-open the project again and reverse again to WIP, pass new transactions then close the project again by estimation and elimination.
Request: Removing “set project to finished” option in elimination posting and let the stage changes automatically to Finished, which will then prevent any future postings. And in reverse elimination, changing the project stage to in process automatically.
-
Item requirement project budget consumption
Scenario: When no Cost price is set in the Released Item form/Manage cost section, on created Item requirement, the system does not consume the project budget.
When processing Item journal with no set Cost price (meaning 0.00) the project is consumed properly.
Business demands: Customer does not set the Cost price as its not relevant to the business scenario.
Business requirement: Project budget to be consumed by any transaction based on the actual cost value to the project.
-
Decreased Project Budget Revision
Business scenario: Decreasing the initial Project Budget with Budget revision and posted transactions consumed all of the initial project budget, using Disallow overrun.
Business Request: Validation of the revised budget against previous commitments so that the system not to allow the overrun and the submitting of the Project budget revision.
You’re offline. This is a read only version of the page.
