1 of 22 international reports phase 2/ da0539-w1 last updated: 05-00 international reports phase 2

International Reports Phase 2/ DA0539-w1

Last updated: 05-00 1 of 22

International ReportsPhase 2

International ReportsPhase 2



‘Plan’ Definitions‘Plan’ Definitions

Introducing the concept of multiple ‘chart of account’ (or

‘plan’) definitions based around a flexible hierarchy

environment



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

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 Maintenance allows hierarchical structures of ‘plan’ codes to be maintainedPlan Validation Maintenance provides all the functionality required to maintain the G/L Plan Hierarchy Validation table

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

Select, for the first part of this walkthrough, the option Plan Maintenance

Plan Maintenance option - General Ledger



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

The first window of the Plan Maintenance option allows the top level, or root node, of the hierarchical structure to be entered




In this example there are two root nodes defined

In this example there are two root nodes definedThe root node also links the corresponding validation criteria to its hierarchy

The root node also links the corresponding validation criteria to its hierarchy

Note: This is detailed in slides 13 and 14 … Plan Validation Maintenance

Note: This is detailed in slides 13 and 14 … Plan Validation Maintenance

Select F8-Add to add further root nodes as required

Select F8-Add to add further root nodes as required

Select Enter-Explode to descend down the highlighted branch

Select Enter-Explode to descend down the highlighted branch

– Plan Maintenance option




For this example, root node 1 (Assets) has been exploded and the node code 11 (Cars) is to be added

For this example, root node 1 (Assets) has been exploded and the node code 11 (Cars) is to be added


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.

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.




This example shows 2 ‘first level’ nodes assigned to the root node ‘1’ (Assets)

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

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

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)

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

F8-Add/Single adds a new node to the current level displayed





Where F11-Copy copies ‘root’ nodes, and therefore copies entire hierarchies to the new ‘root’ node name and description entered

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

With the only variation on these functions being at the top level


And F12-Toggle (not shown) switches between the top level and a list of all hierarchy node codes

And F12-Toggle (not shown) switches between the top level and a list of all hierarchy node codes




Where F12-Multiple enables multiple nodes to be added to the top-level selected from a browse list

Where F12-Multiple enables multiple nodes to be added to the top-level selected from a browse list

And at other levelsAnd at other levels





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)

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






Note: This is detailed in slides 13 and 14 … Plan Validation Maintenance and the section entitled Forming Links

Note: This is detailed in slides 13 and 14 … Plan Validation Maintenance and the section entitled Forming Links




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

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 - General Ledger– Plan Validation Maintenance option

Plan Validation Maintenance provides the functionality required to maintain the General Ledger Plan Hierarchy Validation table

Plan Validation Maintenance provides the functionality required to maintain the General Ledger Plan Hierarchy Validation table



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 window is only displayed if the validation table is empty – it enables the validation criteria for a particular hierarchy to be recordedThis field identifies the particular hierarchy that these details refer to – as defined via the Plan Maintenance option

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

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 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

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 1-2-2-2-3 (defined by the two system keys NLCODESTR and NLACSTR which are set to 1-2-2-2-3 and 2-2-3 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 2-2-3

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 1-2-2-2-3 (defined by the two system keys NLCODESTR and NLACSTR which are set to 1-2-2-2-3 and 2-2-3 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 2-2-3

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



Forming LinksForming Links



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

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

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-LinkThis field is optional and is used to

identify which particular hierarchy the parent and child link nodes you enter are linked to

This field is optional and is used to identify which particular hierarchy the parent and child link nodes you enter are linked toThe Parent fieldThe Parent fieldAnd the Child field are both mandatoryAnd the Child field are both mandatory

Note: A General Ledger Posting Code can only be linked to one hierarchy node

Note: A General Ledger Posting Code can only be linked to one hierarchy node





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)

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)




Note Also: A General Ledger Account Code can also only be linked to one hierarchy node

Note Also: A General Ledger Account Code can also only be linked to one hierarchy node





The option Plan Maintenance also allows a link to be generated between a hierarchy node and a General Ledger code

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)

These hierarchy codes are at the bottom level of the hierarchy ‘1’ (Assets)




Slide this bar across to view the

additional functions available 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


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





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

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



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

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

1 of 22 international reports phase 2/ da0539-w1 last updated: 05-00 international reports phase 2

Documents

level plan maintenance

plan definitions

new option

international reports

general ledger code

hierarchy node codes

new root node

selected node