Summary

The Setup window is used to define how the Project Management module will function.

Step by Step

1     Open the Setup window in the Project Management module (PM> Utilities> Setup).

2     Complete the Settings section.

• The Task 1 Format and Task 2 Format fields are used to define the format of the task code (PM> Maintenance> Task). Enter an “X” for each digit.
  • Once the Task Format fields are set, they cannot be changed.
  • The PM module task code has two parts: Task 1 (task group) and Task 2 (sub-task).
  • The Task 1 Format field sets the format of the task group (PM> Maintenance> Task Group) and is used as the first portion of the task code.
  • The Task 2 Format field sets the format of the sub-task. The sub-task defines a unique task of a certain task group. For example, the task code 001-0001 has a task group of 001 and a unique sub-task of 0001. The format of the sub-task should be large enough to contain all of the sub-tasks of a certain task group. For example, if you have more than one hundred sub-tasks of a certain task group, the Task 2 Format field should contain at least three digits to contain all of the sub-tasks.
• Check the Transactions must have associated budgets toggle if transactions should only be posted to PM tasks that have budgeted amounts. For example, an error message will open in the AP module if you try to add a PM task code that does not have a budgeted amount to an AP invoice line item.
  • Budgets are attached to tasks using the Budget Adjustments process (PM> Budget Adjustments).
  • This toggle does not affect the Time/Materials Entry process in the Project Management module, so when this toggle is checked you can create time/materials entries on tasks that do not have budgeted amounts.
  • This toggle does not add validation to the task code maintenance window (PM> Maintenance> Task). When this toggle is checked you will be able to create task codes that do not have budgeted amounts, but you will not be able to post transactions to those task code using another module.
• Check the Transactions must have GL account numbers toggle if every PM module transaction should be attached to a general ledger account.
• Check the Enable report break on LEMS level toggle to break down the PM Task by Project and PM Distribution reports by LEMS detail.
• Click the Save button when the setup is complete.

3     Track any changes made to the PM Setup window.

• Click the Audit Trail icon to open the Audit Trail window.
• Use the search criteria fields at the top of the screen to sort the displayed audit trail.
• The data grid below will provide details about any changes made to the setup window including the date of the change, type of change made, user who made the change, and data table that was edited.