Ideas for Acumatica

Important! Please note that we do not reply to all messages, but we do read them, analyze them, and work to improve Acumatica based on the feedback we receive.
This portal is for product ideas and feedback only. If you need customer service assistance, please contact your Acumatica Support Partner or submit a support case.  You can also get assistance from community resources:  LinkedIn Group or StackOverflow
No Reliance: Information is maintained on a best-efforts basis and may be changed without notice. Acumatica cannot guarantee the accuracy of the information provided or guarantee completion of features/ideas described on this portal. 

Add branch to project/project task

Although branch accounting is turned on it is not possible to directly associate a project/task with a branch.  In multi-branch project based businesses it is often necessary to assign projects/tasks to branches and also restrict access by branch.

  • Rick Baccari
  • May 15 2017
  • Gathering Feedback
  • Attach files
  • Gabriel Michaud commented
    April 05, 2018 14:40

    In Acumatica 2017R2, it is possible to specify branch for a project and override in a project task to use the needed entity in a billing rule as the source of the branch for invoice lines.

  • Laura Collins commented
    December 06, 2018 14:09

    We first assign unique project numbers that start with the branch number in the number scheme.

     

    We then assign employees to groups and then use row level security to restrict access to projects as well as visibility of those projects.

     

    This works well.

     

    However, if the branch could be assigned at the project level it would reduce the complexity is creating the needed restrictions.

  • Tim Rodman commented
    February 28, 2019 16:16

    This one really burned a client of mine recently because they assumed that the Branch security was restricting access to Projects, when in fact everyone across the 10+ locations could see the Projects for all locations. This was a big confidentiality violation.

    I can totally understand why they assumed the Branch security would restrict access.

    The Access Role field on the Branches (CS102000) screen controls what Branch data a user can see, including which Warehouses and Cash Accounts.

    For example, if you use the SalesDemo data and give the andrews user access to the BRANCH HQ role, but not the BRANCH CAP and BRANCH VA roles, then login as the andrews user, you will see the following in the lookup window on the Warehouses (IN204000) screen:

     

    The VA-RETAIL warehouse isn't listed in the screenshot above because it's restricted by the Access Role on the Companies (CS101500) screen.

    The admin user can see the VA-RETAIL warehouse because the admin user has access to all Companies:

     

    The same behavior is experienced with Cash Accounts.

    So it doesn't make any sense that we don't have the same behavior on the Projects (PM301000) screen. The andrews user can access the FIXEDP05 Project even though that Project belongs to the SERVICES Company which the andrews user doesn't have access to:

  • Ekaterina (Kate) Stepalina (Product Manager Project) commented
    March 04, 2019 12:16

    Hi Tim,

    Thank you so much for the detailed comment! It's clear about the Projects PM301000 form for me now.

    Question: What's the expectation about document entry?

    Should users be able to select only allowed for them projects in document lines of PO orders, AP bills? Project transactions and GL transactions? Time cards and expense receipts/claims?

    Should users be able to see documents that refer to projects they don't have access to? There can be a situation when a PO order has one line for project A, another line for project B. What should a user see in this PO order if such user has access to project A and doesn't have access to project B? 

    K

  • Tim Rodman commented
    March 05, 2019 03:33

    Thanks for the reply Kate.

    My expectation was that it would work the same as the Warehouse field. As far as I can tell there, it restricts every lookup field to only the Warehouses that you have access to.

    I was expecting that the Project field would function the same way on all project lookups, including when running ARM reports.

    I did a test with the Warehouse field where I added two lines to a Sales Order for Warehouses in different Branches. The user who only had access to one Branch could still see both lines on the Sales Order. The only restriction that kicks in is that you won't see the Sales Order if you don't have access to the Branch that's on the FINANCIAL SETTINGS -> Branch field of the Sales Orders (SO301000) screen. So my expectation with Projects would be the same like with your PO example. The user could see all lines if they have access to the PO.