• 0

    Ability to delete Project Milestones

    Suggested by Jurre Van Loon New  0 Comments

    Once a project milestone is created on the contract line details you cannot delete the record.


    There should be an ability to delete the milestone if the status = not ready to invoice, so that if a mistake is made, the milestone can be deleted


  • 2

    Design Change Request: Option to Retain Item-Level Default Financial Dimensions When Adding Lines to a Project Purchase Order

    Suggested by Ian Luu New  1 Comments

    In the current design of the Project management and accounting module in the Finance and Operations application, when a purchase order is linked to a project, users are prompted to decide whether the vendor’s default financial dimensions on the purchase order header should be overridden with the project’s default financial dimensions.

    However, there is no option that allows users to retain the default financial dimensions for item lines. As a result, users must manually restore the item-level financial dimensions, which is both inefficient and time‑consuming.

    We would like to formally request a design enhancement to introduce an option that allows users not to override the item’s default financial dimensions when adding lines to a project purchase order.


  • 3

    Revenue recognition voucher should not consume multiple number sequence numbers when multiple projects share the same Revenue project ID.

    Suggested by Marco Pham New  0 Comments

    The Revenue Project ID field (Project management and accounting → All projects → Project → Revenue recognition) is designed to give flexibility in how revenue is recognized. When several sub‑projects roll up under a parent project, assigning the parent’s Revenue Project ID to each sub‑project allows the system to combine revenue recognition entries across all those related projects.

    If each sub‑project uses its own Revenue Project ID, running revenue recognition will consume only one number from the voucher number sequence.

    However, when multiple projects share the same Revenue Project ID, the revenue recognition process consumes voucher numbers based on the number of projects included under that Revenue Project ID.


    Example:

    If the current voucher number is PPV_0015, and you have 15 sub‑projects all mapped to the same parent Revenue Project ID, posting revenue recognition will generate vouchers up to PPV_0030.

    It would be very helpful if the system provided a way to track which voucher numbers were consumed during this process, or an option to prevent this kind of voucher number “skipping” from occurring.