Map my Tasks
Each of the tasks is mapped to one or more GL code by individual entities using “Map my Tasks” link in the side menu.
Functionalities:
‘Map my tasks’ is enabled only after the GL mapping is completed.
Once the tasks are added by the Ultimate Parent, all the subsidiaries will map the tasks to the GL code(s) using “Map my Task” in the menu bar.
Only the tasks for which the L3 is applicable will be listed in the tasks.
For ex: If there are 50 L3’s in the COA master. Out of this, the ultimate parent has created tasks for 25 L3’s. For entity A, if only 8 L3s are mapped to GL codes in the GL mapping, then only the task against the 8 L3’s will be displayed in the tasks.
If there are 15 tasks against these 8 L3’s, then the user has to map the GL codes against all the 15 tasks.
Each task can be mapped to one or more GL codes.
The GL codes will come from the GL mapping of that particular L3.
The GL codes of the L3 caption ‘Inventory’ will only show up for the tasks under ‘Inventory’ tab
A GL code CANNOT be mapped to more than 1 task.
All the GL codes in the GL mapping should or must have a mapping to task.
For ex: If I have 10 GL codes in the GL mapping of entity A and if there are 3 tasks which are applicable to that entity, then these 10 GL codes should be mapped to these 3 tasks.
If anyone GL code is not mapped to any of the tasks, then the ultimate parent will not be able to include “Book Close” module for that entity during project creation.
However, if the project is created by a subsidiary, then the Book Close module is not enabled, and the “Include Book Close” field will not show up.
If any of the subsidiaries did not map the task to the GL code, then those entities will not be included as part of Book Close.
For ex: If HC is the ultimate parent and A and B are subsidiaries. If H and A completes mapping the tasks and B did not complete, then H and A are eligible for Book Close and by default B’s book close option is selected to ‘No’.
When a new GL code is added in the GL Mapping page, the user should be asked to map the GL code to the tasks through a popup.
The task name contains Task number and the task description.
The task description can be viewed using
button. The task can be mapped to GL codes using “Mapped GL Code” drop down.
The dropdown lists all the GL codes which are mapped in the GL mapping. The user can enter one or more than 1 value from the dropdown
The due date for this task can be entered in the “Due Date” field.
“T” in the “Due Date” refers to the book close due date we enter in the “Publish Calendar”. The user can add or reduce the number of days as a due date for this task using + or – buttons.
The assignee and the reviewer of the tasks can be assigned using “Assignee” and “Reviewer” dropdowns respectively.
The financial controller will assign each task to an assignee and the reviewer.
The reviewer will always be a person from the Finance Controller group for subsidiaries and corporate controller for the ultimate parent.
Also, the corporate controller or the financial controller can add instructions using
button. The maximum character limit for instruction is 7500.
Unmapped Tasks:
The tool will throw an error if the GL code is not mapped to the task.
The user will be able to see the unmapped tasks by clicking on the error button in the top of the page. Refer screenshot below.
The user will not be able to include “Book Close” module if there are unmapped GL codes.
If the holding company does not map all the GL codes to tasks, then the book close cannot be included in the project.
If the subsidiaries did not map all the GL codes, then these entities cannot be included in the book close.
For ex: If the subsidiary 'A' has completed the 'Map my tasks' module by mapping all the GL codes and subsidiary 'B' did not map the GL codes to tasks, then during the project creation, the holding company can choose whether entity 'A' should have book close or not by choosing 'Yes' or 'No'. For entity B, the book close by default will be set to 'No' and this cannot be changed.
Last updated