Hierarchy Maintenance
Why maintain hierarchies
At times, users may need to view the parent child relationships within ERPJewels. As the hierarchy elements are stored in the same table, simple main table view is not at all sufficient. Users need to view the hierarchies in definite hierarchical manner only. Further if there are domains specified at hierarchy master level, then the editing of the hierarchy elements have to be in accordance with those domains. Hierarchy elements can be of 17 characters at the most.
Typically the users will never require hierarchies to be edited manually and this program would be used for viewing only.
How Do we Check the Generated Hierarchies
When the hierarchies are generated through program, hierarchies information come default here in ‘Maintain hierarchies’ Session.
Session Description - tudll9191m000 (Maintain Hierarchies)
Hierarchies master have hierarchy level (between 2 to 6) ,
hierarchy level descriptions , optional hierarchy valid domains of alphanumeric
and numeric types for each hierarchy level.
Hierarchy domain for a specific level may not be required if
the returned values is an expression or particular domain alignment /
conversions / validation is not required when editing hierarchies (see
hierarchy ‘period’ example above)
Transaction level is the information about the hierarchy
levels which will act as an anchor for hierarchies while online analyses are
being carried out. This is set type field which allow multiple selection from
level 1 to the highest level possible for that hierarchy. Normally the lower
level hierarchy elements (towards level 6) occur at the transaction level. (see
hierarchy ‘itm001’ example above)
When hierarchies are generated from parent child hierarchy
program (tudll9291m001) , then the last level occurs in transaction and act as
anchor .e.g 4 level parent child in chart of accounts , the transaction level
could be ‘Level 4’. This is updated as default value which user can change.
In expressions hierarchy normally the pure table field
expressions are selected in deciding transaction level (see hierarchy ‘period’
example above). Only financial year and
period (Level 1 & Level 4 ) are
selected as transaction level. Level 2
and 3 (half year and Quarter) being not-table field in tfgld005 do not form
part of transaction level. This transaction level is the default transaction level
while linking hierarchies to analyses. Users can vary this for each analysis.
Session displays values from the same table in hierarchical
form. There are basically 2 areas where user can do data entry viz. Parent
details and child details.
In parent details, user can edit current level and parent
value only when user has clicked the button ‘Change Parents’. On finishing the
entry, user need to press CTRL+S to get the child of the parent combination
selected.Session Description - tudll9191m000
(Maintain Hierarchies details)
Normal delete / insert /edit, user can maintain only the child details. On deleting a parent , all childs of that parent also are deleted.
If the domain is specified for the hierarchy level then editing the values is allowed only as per the domain entered.
When user selects a record and clicks the button ‘child details’ , all childs of the child along with description are displayed and current level increases by 1. When user clicks ‘immediate parent’, the current level reduces by one and parent records with other records at the new hierarchy level are displayed.
The starting hierarchy level is level 1 and from there user can get to the level he/she desires.
FastTrack to ERPJEWELS :
Latest Trend | Hot Links | Jewels of ERPJewels | Jewels of Baan | Jewels of Excel