Home

Key Functionalities of ERPJewels

What is new in ERPJEWELS

Latest Trends

ETL/Trends in Data mining/ Trends in Data mining/ Data tranformation and multi-dimensional repoting capabilites

Download

Docs, Executable, AVI and others in Download Section

Hot Links

Find what is Hot in ERPJewels

Related Links

Jewels of ERPJewels

Jewels of BAAN

Jewels of Excel

Jewels of Data Mining

Parent Child Hierarchies

What is Parent Child Hierarchy

Certain master tables in Baan have parent child relationships ingrained in the very table definition of the tables. These tables have one parent field, description field , sublevel field (optional). Examples of such table are tfgld008 (Chart of accounts), tfgld010 (Dimensions), tccom010 (Customers), tccom020 (Suppliers) etc.

Session Description

Fields

  1. Hierarchy – It’s is the 9 character code in ERPJewels system by which any hierarchy is recognized. This hierarchy code is used while editing hierarchies and linking the same to analyses.
  2. Update Mode - The hierarchy generation mode can be Append / Rewrite. Append  update mode can be useful when the master data are dynamic and user wants to update only new data. With rewrite mode , the hierarchies will be completely overwritten.
  3. Description – 30 character description which is descriptive of hierarchy in functional terms.
  4. Hierarchy Levels – Hierarchy levels can be any number between 2 to 6. Maximum number of hierarchy allowed is 6. Hierarchy levels have to be restricted because of ceiling on length of Baan indices.(which is 120  bytes).
  5. Table name – It is the Baan table name around which the hierarchy revolves. The table chosen should have parent-child relationship in-built in the table structure.
  6. Key field – This is by default the primary index field which has a parent field in the table.
  7. Parent field – The table field which is the parent of the key field value. This also come by default if the table has parent child in-built in the table.
  8. Level field – This has to be valid table field if it is non-blank . This field may be left blank. If there is value in this field, the hierarchy generation will ensure that the all hierarchy elements with same level are stored at the same level thus ensuring data consistency.
  9. Sorting – This field is required only in case the level field is filled. This can be ascending or descending.
  10. Description Field – This is by default 30 + character table field of the main table. This field is used to fill in the hierarchy element descriptions. These hierarchy elements can be used in analyses results in case hierarchy codes do not make any meaning  (i.e. ledger accounts may be numeric and ledgers numbers may not make any meaning to the users)
  11. Condition Field – This is the table field of the table on which expression hierarchy is generated. This is to be filled when the user wish to restrict the hierarchy generation only to certain records of the table based on the value in this field. Text and combined fields are not allowed. Text and combined fields are not allowed in this field.
  12. Operator – All operators for which singular operands exists are allowed here like equal to , greater than, less than , like , not like etc. For string and multibyte field , like and not like can be selected from enum options.
  13. Value – This is the value of the field to which the hierarchy generation is restricted. Value is aligned according to domain. For numeric domains only numbers are allowed. For enum/set fields only valid options can be selected.

Session Logic

The session selects the records from the table depending on the selection criteria. If possible it uses the table index also in order to speed up hierarchy generation.  It explodes hierarchy till the specified level and then it gets the descriptions from the reference table and updates the same hierarchies’ masters.

The session can also be run in job mode to update hierarchy just before the analyses (linked to hierarchies) are run in job.

Example of Hierarchies based on Parent Child in Ledger

NOTES

  1. There are certain table which have parent child relationship ingrained in the very database design itself. It has a parent field, child field, description and sublelvel (optionally) . Examples of such tables are tfgld008, tfgld010, tcocom010, tccom020 etc in Baan.
  2. As soon as the table is specified child field, parent field and description field are defaulted. Level Field is an optional field.
  3. Sort mode for levels can be ascending /descending (depending on the way application treats the levels )



FastTrack to ERPJEWELS :

Latest Trend | Hot Links | Jewels of ERPJewels | Jewels of Baan | Jewels of Excel