1 of 22 International Reports Phase 2/ DA0539-w1 Last updated: International Reports Phase 2

2 of 22 International Reports Phase 2/ DA0539-w1 Last updated: Plan Definitions Introducing the concept of multiple chart of account (or plan) definitions based around a flexible hierarchy environment

3 of 22 International Reports Phase 2/ DA0539-w1 Last updated: This is a new option This new option provides access to both the General Ledger Plan Hierarchy and General Ledger Plan Hierarchy Validation tables for both update and enquiry purposes Plan Maintenance allows hierarchical structures of plan codes to be maintained Plan Validation Maintenance provides all the functionality required to maintain the G/L Plan Hierarchy Validation table Select, for the first part of this walkthrough, the option Plan Maintenance Plan Maintenance option - General Ledger

4 of 22 International Reports Phase 2/ DA0539-w1 Last updated: Plan Maintenance option - General Ledger – Plan Maintenance option The first window of the Plan Maintenance option allows the top level, or root node, of the hierarchical structure to be entered

5 of 22 International Reports Phase 2/ DA0539-w1 Last updated: Plan Maintenance option - General Ledger In this example there are two root nodes defined The root node also links the corresponding validation criteria to its hierarchy Note: This is detailed in slides 13 and 14 … Plan Validation Maintenance Select F8-Add to add further root nodes as required Select Enter-Explode to descend down the highlighted branch – Plan Maintenance option

6 of 22 International Reports Phase 2/ DA0539-w1 Last updated: Plan Maintenance option - General Ledger For this example, root node 1 (Assets) has been exploded and the node code 11 (Cars) is to be added – Plan Maintenance option Note: There is no restriction on the characters that can be used for the node codes, i.e. root node PCs could contain the child codes P166, P200, etc.

7 of 22 International Reports Phase 2/ DA0539-w1 Last updated: Plan Maintenance option - General Ledger This example shows 2 first level nodes assigned to the root node 1 (Assets) At this level, and at all other levels of the hierarchy, ESC-Exit takes the display back up one level Enter-Explode/Details takes the display down one level – descending the branch attached to the highlighted node Note: If no lower level exists below the selected node a pop-up box automatically appears requesting entry of a new node name/code and description – this will be added to the current position in the hierarchy (see slide 11) F8-Add/Single adds a new node to the current level displayed – Plan Maintenance option

8 of 22 International Reports Phase 2/ DA0539-w1 Last updated: Plan Maintenance option - General Ledger Where F11-Copy copies root nodes, and therefore copies entire hierarchies to the new root node name and description entered With the only variation on these functions being at the top level – Plan Maintenance option And F12-Toggle (not shown) switches between the top level and a list of all hierarchy node codes

9 of 22 International Reports Phase 2/ DA0539-w1 Last updated: Plan Maintenance option - General Ledger Where F12-Multiple enables multiple nodes to be added to the top-level selected from a browse list And at other levels – Plan Maintenance option

10 of 22 International Reports Phase 2/ DA0539-w1 Last updated: Plan Maintenance option - General Ledger And F13-Link generates a link between a hierarchy node and a General Ledger code – the entered G/L code is validated according to the information held on the validation record corresponding to the particular hierarchy (identified by its root node) – Plan Maintenance option

11 of 22 International Reports Phase 2/ DA0539-w1 Last updated: Plan Maintenance option - General Ledger – Plan Maintenance option Note: This is detailed in slides 13 and 14 … Plan Validation Maintenance and the section entitled Forming Links

12 of 22 International Reports Phase 2/ DA0539-w1 Last updated: Plan Maintenance option - General Ledger When no lower level exists below the selected node, this window appears automatically when Enter-Details is selected – this new node name / code and description will be added to the current position in the hierarchy – Plan Maintenance option

13 of 22 International Reports Phase 2/ DA0539-w1 Last updated: Plan Maintenance option - General Ledger – Plan Validation Maintenance option Plan Validation Maintenance provides the functionality required to maintain the General Ledger Plan Hierarchy Validation table

14 of 22 International Reports Phase 2/ DA0539-w1 Last updated: Plan Maintenance option - General Ledger – Plan Validation Maintenance option This window is only displayed if the validation table is empty – it enables the validation criteria for a particular hierarchy to be recorded This field identifies the particular hierarchy that these details refer to – as defined via the Plan Maintenance option If you check this field, the hierarchy / General Ledger link will be validated when entering hierarchy node codes against account codes via the G/L options Posting Codes and Account Codes This field allows the the hierarchy node codes to be linked to either General Ledger account codes (A) or posting codes (P) This field accepts a single digit which corresponds to the number of elements against which the General Ledger link code is matched – appropriate to the particular General Ledger file For example: The General Ledger has cost centres enabled and a posting code structure of (defined by the two system keys NLCODESTR and NLACSTR which are set to and respectively) – using 3 elements, the following G/L codes will be accepted (depending upon the G/L file in use): The Account Code file validation will accept codes of the format The Posting Code file validation will accept codes of the format 1-2-2, i.e. only the first three levels of the posting code can be linked to a hierarchy For example: The General Ledger has cost centres enabled and a posting code structure of (defined by the two system keys NLCODESTR and NLACSTR which are set to and respectively) – using 3 elements, the following G/L codes will be accepted (depending upon the G/L file in use): The Account Code file validation will accept codes of the format The Posting Code file validation will accept codes of the format 1-2-2, i.e. only the first three levels of the posting code can be linked to a hierarchy

15 of 22 International Reports Phase 2/ DA0539-w1 Last updated: Forming Links

16 of 22 International Reports Phase 2/ DA0539-w1 Last updated: This option has been amended as follows: This option has been modified to form links between the General Ledger posting codes and the hierarchy nodes entered via the option Plan Maintenance Posting Codes option - General Ledger In this example, as the validation via Plan Validation Maintenance on the node 1 is set to 5 for posting codes (P), this bottom-level posting code, i.e. that is to 5 levels, can be linked to a hierarchy node by selecting F12-Link This field is optional and is used to identify which particular hierarchy the parent and child link nodes you enter are linked to The Parent field And the Child field are both mandatory Note: A General Ledger Posting Code can only be linked to one hierarchy node

17 of 22 International Reports Phase 2/ DA0539-w1 Last updated: This option has been amended as follows: Posting Codes option - General Ledger Note: The General Ledger option Account Codes has also been modified to form links between the General Ledger posting codes and the hierarchy nodes entered via the option Plan Maintenance – again using the new function F12-Link where the validation is set to Account codes (A)

18 of 22 International Reports Phase 2/ DA0539-w1 Last updated: Posting Codes option - General Ledger Note Also: A General Ledger Account Code can also only be linked to one hierarchy node This option has been amended as follows:

19 of 22 International Reports Phase 2/ DA0539-w1 Last updated: Plan Maintenance option - General Ledger – Plan Maintenance option The option Plan Maintenance also allows a link to be generated between a hierarchy node and a General Ledger code These hierarchy codes are at the bottom level of the hierarchy 1 (Assets)

20 of 22 International Reports Phase 2/ DA0539-w1 Last updated: Plan Maintenance option - General Ledger – Plan Maintenance option Slide this bar across to view the additional functions available Then select F13-Link to generate a link between the highlighted hierarchy node and a General Ledger code – the G/L code is validated according to the information held on the validation record corresponding to the particular hierarchy (identified by its root node)

21 of 22 International Reports Phase 2/ DA0539-w1 Last updated: Plan Maintenance option - General Ledger – Plan Maintenance option For example, as the validation via Plan Validation Maintenance on the node 1 is set to P (Posting codes) to 5 levels, this bottom-level posting code, i.e. that is to 5 levels, can be linked to the highlighted hierarchy node

22 of 22 International Reports Phase 2/ DA0539-w1 Last updated: As the hierarchies, Account codes and/or Posting codes are stored on the database they can be accessed using Report Writer and/or SQL – this provides you with unlimited reporting functionality for all General Ledger transactions