Work Reporting MOD009ABV Up to DB 39.5.13

• Depending on whether the hours to be worked function is (de)activated, the module is divided into one or two areas.
  • Hours to be worked (only if hours to be worked are activated)
    • The hours to be worked are displayed for each day of the period defined for hours to be worked.
    • The displayed value is compared for each day against the total value of work reporting for this day. For this purpose see traffic light information in the Total area.
  • Total
    • In the Hours worked rep. only until end of current week subarea, projects are displayed for which the Time recording also in future (overh. costs) value is selected in the Posting type parameter in the Project Core Data module.
      • In this area, you can report actual hours until the last day of the current week.
    • In the Hours worked rep. also for the future (overhead costs, ...) area, projects are displayed for which the Time recording also in future (overh. costs) value is selected for the Posting type parameter in the Project Core Data module.
      • In this area, you can also report future hours
    • If the hours to be worked function is activated, a traffic light function which displays whether the hours to be worked have been exceeded (red) or fallen below (yellow) is additionally placed below the scale in this area. If the number of reported hours is the same as that defined as hours to be worked, there is no color highlighting.
      • If the hours to be worked function is activated but the hours to be worked values have not yet been defined for a resource, the traffic light for this resource is always red.

• In this module, only those projects and tasks are displayed for which the current resource is scheduled and which are not locked (e.g. via the Locked parameter in the Project Core Data or the Task locked parameter in the Schedule).
• If you enforce the display of locked projects or tasks and try to report hours worked, one of the following messages is displayed: Project/Task locked or Invalid work reporting period.
• NEW The tasks that were finished in the current week are displayed in the Completed tasks of current week section.

• In the right window you can scroll to another week
  • via the arrow buttons or
  • by selecting the respective calendar week in the date listbox.
• This enables you to post actual hours to tasks which are not planned for the current week but which have been planned for previous weeks.
• You can only scroll back beyond the invoicing date. However, it is not possible to record hours which lie before the invoicing date. If a user tries to report hours worked anyway, the Recording not possible: date is earlier than key date. notice is displayed.

Note

• The browse function uses the calendar predefined in the @G150 variable. It can but does not necessarily have to match with the project, proposal, or resource calendar.

• You can scroll to other weeks using the arrow buttons in Window 2.
• This enables you to post actual hours to tasks which are not planned for the current week but which have been planned for previous weeks.
• You can only scroll back beyond the invoicing date. However, it is not possible to record hours which lie before the invoicing date. If a user tries to report hours worked which are earlier than the invoicing date anyway, the Reporting not possible: date is before invoicing date. notice is displayed.

• Click on the NEW Post to further projects/tasks button.
  • As a result, you switch to the Reporting Hours Worked module.
  • In this module, the employee can report his/her hours worked for tasks and process steps for which he/she is scheduled, as well as for those tasks in which the resources the current employee has access to are planned (controlled by the resource structure code).

• Move to the week for which you want to report overhead costs by pressing the arrow buttons.
• In the Time recording also in future (overh. costs, ...) area, overhead cost projects are displayed with their corresponding tasks.
• Click on the line of the required overhead cost task in the scale area below the required date and enter the hours.
• Save.
  • A load record is created and can be viewed and edited in the left window by expanding the tree structure of the respective task.
    • In the Comment field you can write a comment on the load record.
    • If the date is changed manually in the Load date field, the load record is automatically moved under the scale as well.
• Enter the hours for all required days in the same way and save.

• Select the Forecast module variant from the toolbar.
• Enter the estimated remaining effort in the Forecast field and save.
• Click on the Send forecast button.
• The Send Info module is opened including an automatically created message.
• The message contains the following data: sender, planned and NEW actual values of the current week, remaining and forecast values for effort as well as NEW the expected completion date, if it is filled.
  • The project manager of the project is automatically entered as the recipient.
• Click on the Send button.

• Select the Forecast module variant from the toolbar.
• Enter the estimated remaining effort in the Forecast field and save.
• Click on the Send forecast button.
• The Send Info module is opened including an automatically created message.
• The message contains the following data: sender, planned, actual, remaining, and forecast values for the effort.
  • The project manager of the project is automatically entered as the recipient.
• Click on the Send button.

• Select the Forecast module variant from the toolbar.
• Enter the estimated remaining effort in the Forecast field and save.
• Click on the Send forecast button.
• The Send Info module is opened including an automatically created message.
• The message contains the following data: sender, planned, actual, remaining, and forecast values for the effort.
  • The project manager of the project is automatically entered as the recipient.
• Click on the Send button.