Objects - Hierarchical Objects
A hierarchical Object is one that consists of a string or sequence of Objects. Instead of having to remember to assign several Objects to each Transaction, when you use hierarchical Objects, you only need assign one Object and the others will be assigned automatically. This makes assigning Objects easier and faster and reduces the risk of making mistakes.
You can define a hierarchical Object in the Object register by entering the string or sequence of Objects in the Hier. Objects field. In the following example, we have defined an Object for the Person NB. In the Hier. Objects field we have entered Objects for the department and the office for which that Person works. These Objects must already exist in the Object register:
When you use the "NB" Object in a transaction of any kind, the string of Objects in the Hier. Objects field (in this case, "DEPT1" and "OXFORD") will also be assigned automatically. The example below shows the "NB" Object being used in an
Expense record recording travel expenses:
In the Nominal Ledger Transaction resulting from this Expense record, the Hier. Objects will be added to the "NB" Object automatically. So, whenever you record a cost incurred by or a sale made by this Person, using the single "NB" Object will guarantee the correct assignment of the "DEPT1" and "OXFORD" Objects as well, in alphabetical order:
Hierarchical Objects are very useful when you need to need to enter Nominal Ledger Transactions (journal postings) manually, because in this case no Objects will be offered by default. They help ensure you always assign the correct Objects, and the correct number of Objects. In the example illustrated below, we are entering a
Nominal Ledger Transaction recording Person NB's salary, and we have just entered the "NB" Object:
As soon as we press the Tab, Enter or Return key to move to the next field, the string of Hier. Objects from the "NB" Object will be added to that Object:
You can include a hierarchical Object in the definition of another. Illustrated below is an Object representing NB's company car:
Since we have entered "NB" in the Hier. Objects field and "NB" itself contains hierarchical Objects, when we use the "Astra_1" Object to record the running costs of this car, it will expand to the combined contents of "ASTRA_1" and "NB", assigning those costs to the correct Person, department and branch:
As already mentioned, when you enter Nominal Ledger Transactions (journal postings) manually, no Objects will be offered by default. The hierarchical Object feature will help ensure that anyone entering a Nominal Ledger Transaction will attach every relevant Object to each posting.
---
In this chapter:
Go back to:
