Similar to what we saw when upgrading to Microsoft Dynamics GP 2013 R2 from a lower release, we noticed that when upgrading to Microsoft Dynamics GP 2015 from a lower release, the following security roles and security tasks were not getting created and are missing:
ESS EMPLOYEE MANAGER* ESS EMPLOYEE* ESS EMPLOYEE-BSS* ESS PTE EMPLOYEE* ESS PURCHASE REQUESTER* HR ADMIN-BSS* LIMITED USER - FIN* LIMITED USER - INV* LIMITED USER - PAYRL* LIMITED USER - PURCH* LIMITED USER - SALES*
ADMIN_BSS_01* ADMIN_BSS_02*ADMIN_COMPANY_013* ADMIN_PURREQ_021* ADMIN_SYSTEM_SL06* EMP_BENEFITS_EMPLOYEE_01*EMP_BSS_EMPLOYEE_01* EMP_DIRECTDEP_EMP_01* EMP_PAYSTUBS_EMPLOYEE_01*EMP_PROFILE_EMPLOYEE_01* EMP_PROFILE_MANAGER_01* EMP_SKILLS_EMPLOYEE_01* EMP_SKILLS_MANAGER_01* EMP_TIME_EMPLOYEE_001* EMP_TIME_MANAGER_001* EMP_W4_EMPLOYEE_01* INQ_PURREQ_005* PTE_EXPENSE_ENTRY_001* PTE_TIME_ENTRY_001* RPT_PURREQ_006* TRX_PURREQ_026* TRX_PURREQ_027*
This is noted in the Upgrade Instructions manual that you will need to add these on an upgraded install.
A new install of Microsoft Dynamics GP 2015 will create these for you.
A new install of Microsoft Dynamics GP will have these roles, but during an update it is by design that we would not roll down new security roles to your existing solution that may cause issues with your current security design. Thus we release them as a script.
The SCRIPTS will create these missing security roles and security tasks for you, when run against the DYNAMICS/system database.
I discovered that the script is missing a resource in the task to allow a user to open the Lookup form to select an existing Employee Expense that was previously saved, but not submited.
Role : ESS PTE EMPLOYEE*
Task : PTE_EXPENSE_ENTRY_001*
missing : 22541: Employee Expense Lookup (PTE_Employee_Expense_Lookup)
Thanks for correcting the SQL script for those who upgrade from a previous GP version.
Hello Beat, What build of Dynamics GP 2015 are you currently using? I tested an upgrade and then a direct install to the 14.00.0801 version/build and on both, I have the following 11 security roles giving users access to the PADEFAULTUSER* security task, which then gives users access to the 'Employee Expense Lookup' window you mentioned:
ESS PTE EMPLOYEE*
PA BILLING CLERK*
PA EQUIPMENT CLERK*
PA EXPENSE CLERK*
PA INV TRANSFER CLERK*
PA MISC CLERK*
PA PURCHASING CLERK*
PA REVENUE CLERK*
PA TIMESHEET CLERK*
This 'Employee Expense Lookup' window (PTE_Employee_Expense_Lookup) is part of the Project Accounting dictionary/feature.
Based on this, it doesn't appear that by default, the 'PTE_EXPENSE_ENTRY_001' security task gives users access to this window, but let me look at this and verify that as well.