Verified on release 3.0.74.2 "Accounting for Kazakhstan" (edition 3.0).
You created an additional attribute "Delivery region" and wanted the manager to select not a flat list of a hundred cities, but a tree: first the region, then the city within it. You checked the box "Values with hierarchy," entered Almaty Region, and within it — Talgar and Kaskelen. Now in the delivery note the field expands as a tree. And these values themselves — "Almaty Region," "Talgar," "Kaskelen" — physically reside in this very catalog. You open it rarely, but when you need to rename a value, move a city to another region, or clean up duplicates — this is exactly where you go.
Let's examine the object honestly and to the point: it is a service catalog of the "Additional attributes and information" mechanism, not a document. It doesn't make postings, doesn't issue ESF. But without understanding how it works, you'll breed duplicate values and break reports by properties.
1. Purpose
Catalog.ObjectPropertyValuesHierarchy stores hierarchical (tree-like) values of additional attributes and information. It is the "twin" of the ObjectPropertyValues catalog, only with hierarchy: any value can be a parent for others. The program itself selects this catalog as storage when, while creating an additional attribute, you enable the "Values with hierarchy" checkbox.
2. Where to find
This catalog has no direct menu item — it is a service catalog. You reach its values through the setup of the attribute itself:
Administration → General settings → Additional attributes and information → open the desired attribute (value type — "Additional value (hierarchy)") → the right part of the form "Values".
To open the entire catalog at once (all values of all hierarchical attributes together), use the navigation link. Menu "Service" → "Go to navigation link" (or Ctrl+F11 depending on the platform), paste:
e1cib/list/Справочник.ЗначенияСвойствОбъектовИерархия
This is a convenient way to search for "orphaned" values and duplicates across the entire database.
2a. How to find out your release
Help → About the program (or the "i" icon in the top right corner). In the window that opens, at the top — the platform version (for example, 8.3.24.xxxx), below — the configuration release "Accounting for Kazakhstan," edition 3.0. The instruction is relevant for release 3.0.74.2. If yours is older — the composition of fields may differ.
3. How to fill in
Values are usually entered directly from the attribute form, but the composition of the card fields is the same.
| Field | Required | Why and what happens on error |
|---|---|---|
| Name | Yes | The text the user will see in the selection list ("Almaty Region"). If left empty — you won't be allowed to save. A typo → a "twin" will appear in reports, and the data will split across two spellings. |
| Owner | Yes (filled in automatically) | A reference to a specific additional attribute (a row of the chart of characteristic types "Additional attributes and information"). Determines which attribute the value belongs to. It is almost never touched manually: it is substituted based on the attribute from whose form you add the value. Change the owner by mistake — the value will "disappear" from your selection list. |
| Parent | No | The top-level value under which the current one resides. This very field builds the tree. Empty → the value is at the top level (the region itself). "Almaty Region" specified → the value becomes a city within it. Make a mistake with the parent — and the city ends up in the wrong region. |
| Code | No (auto) | An internal code, the program assigns it itself. Affects the sort order within a level. Rarely changed manually. |
| Deletion mark | — | Set via "Delete" / Del. A marked value disappears from active selection but remains in old documents until you run Deletion of marked objects. |
Important: this catalog has a hierarchy of items, not groups. There are no separate "folders" here — a regular value acts as the parent. Therefore "Almaty Region" is both a full-fledged value that can be selected in a document, and at the same time a parent for cities.
Practical procedure:
- Open Additional attributes and information, create an attribute, value type — "Additional value", enable "Values with hierarchy".
- In the "Values" block, using the "Create" button, add the top level (region).
- Stand on the region, press "Create" again — the new value will substitute this region in the "Parent" field automatically. This is how you fill in cities.
- By dragging with the mouse or the "Move to group" command, edit the hierarchy.
4. Worked example
A caveat right away: this catalog does not generate accounting postings. It has no debit and credit — it only stores value options. Postings are born by documents (sales, receipt), and the property is only "attached" to them as analytics. I'll show the whole chain on real figures of Kazakhstan 2026.
Task. LLP "Bereke" sells goods and wants to see revenue in reports broken down by delivery region — by regions and cities.
Step 1. Filling in the catalog (our object). Attribute "Delivery region," values with hierarchy:
Алматинская область
├─ Талгар
└─ Каскелен
Туркестанская область
└─ Шымкент
Each row is an item of the ObjectPropertyValuesHierarchy catalog. For "Talgar," the Parent field = "Almaty Region," Owner = the "Delivery region" attribute.
Step 2. Using the value in a document. In "Sales of goods and services" for 1,160,000 ₸ including VAT 16% in the header (on the additional attributes tab), you select "Delivery region" = Talgar.
Step 3. What the sales document does (not the catalog!):
| Dr | Cr | Amount, ₸ | Description |
|---|---|---|---|
| 1210 | 6010 | 1 000 000 | Income from sale to buyer |
| 1210 | 3130 | 160 000 | VAT payable (16%) |
| 7010 | 1330 | 700 000 | Cost of goods written off |
The value "Talgar" itself does not get into the postings — it is written to the information register with the document's additional attributes. But then in the report you filter by "Delivery region = Almaty Region" and get the income amount 6010 = 1,000,000 ₸ already for the entire region, because "Talgar" is subordinate to it in our catalog.
That's the whole value of the object: it turns flat analytics into a collapsible tree. Remove the hierarchy — and you'll have to sum up the cities by hand.
5. Operation types
Unlike a document, the catalog has no separate "Operation type." But the set of actions on a value is fixed:
- Create a top-level value (region).
- Create a subordinate value (city) — with automatic substitution of the parent.
- Move a value to another parent (dragging / "Move to group").
- Mark for deletion / unmark.
- Merge duplicates via the "Search and delete duplicates" processing.
- Set the order of items within a level.
6. What is generated when used
Let me honestly dispel expectations:
- The catalog does not make postings — they are generated by documents where the value is selected.
- It does not issue ESF and SNT; the electronic documents receive the operation's attributes, not the service property values.
- Register movements. When a value is selected in a document or catalog item, an entry goes to the information register "Additional attributes" / "Additional information" — this is exactly where reports take analytics from.
- Hierarchical link (Parent) — that which allows reports to collapse data by regions.
7. Printed forms
The service catalog has no printed forms of its own. Values are displayed:
- in the selection lists of documents and catalogs (as a tree);
- in the universal report and standard reports — as analytics/grouping by the additional attribute;
- in the printed forms of that document where the attribute is configured for output (for example, in the delivery note, if the attribute is added to the template).
8. Common mistakes
"The 'Name' field is not filled in" — you pressed "Save" on an empty value. Enter the value text.
"The value is not a value of the property '…'" / the value is not visible in the document's selection list — the item has an incorrect Owner. The value belongs to another attribute. Open the card, check the "Owner" field; simpler — delete it and create it anew from the form of the desired attribute.
The city is visible at the top level, not within the region — the Parent is not filled in or is incorrect. Stand on the value, "Move to group" → specify the correct region.
"Failed to delete, the object is in use" — the value is used in posted documents. First mark it for deletion, then Administration → Maintenance → Deletion of marked objects: the program will show where the value is involved.
Two "Shymkents" in the report — duplicates (created by hand and by import). Run "Search and delete duplicates" on the catalog, select the main item — the references will be re-linked automatically.
The value is gray, can't be selected — a deletion mark is set. Remove it (Del again / "Unmark").
9. FAQ
How does this catalog differ from "Object property values" (without "Hierarchy")?
Only by hierarchy. ObjectPropertyValues stores a flat list, ObjectPropertyValuesHierarchy — a tree. The program itself places values into the hierarchical catalog if the attribute has the "Values with hierarchy" checkbox enabled.
How to enable hierarchy for an already created attribute? Open the attribute in "Additional attributes and information," check "Values with hierarchy." Attention: for an attribute with already entered flat values, changing the storage type is unavailable — hierarchy is set at creation. It's easier to create a new attribute.
Can the catalog be opened directly?
Yes: "Service" → "Go to navigation link" → e1cib/list/Справочник.ЗначенияСвойствОбъектовИерархия. You'll see the values of all hierarchical attributes at once, grouped by owners.
Does the catalog make postings or affect VAT? No. It does not participate in accounting for amounts. VAT 16%, income 6010, receivables 1210 are generated by the sales document; the property value is only analytics for reports.
Will the value get into the ESF? No. The ESF and SNT receive the transaction attributes (counterparty, item, amounts, VAT), not the service values of additional properties.
How to move a city from one region to another? Stand on the city, drag it with the mouse into the desired region or "Move to group" → select the new region. The parent will change, and old documents will retain the reference to the same city.
I deleted a value — did the old documents "go off"? No. The deletion mark and subsequent deletion do not erase the value from posted documents while it is used there — the program won't let you delete it and will show the list of places of use.
How to merge two identical values? "Administration → Maintenance → Search and delete duplicates," search area — this catalog, filter by the owner-attribute. Mark the original as the main one — the references in documents will be re-linked to it.
Why is the value not in the document's selection list, although it exists in the catalog? Three reasons: a deletion mark is set; an incorrect "Owner" (the value belongs to another attribute); the attribute is not displayed on the form of this document/catalog in the additional attributes settings.
Can values be given an order manually? Yes, with the "Move up/down" commands within a level — it affects the order in the drop-down list.
10. Related objects
- Chart of characteristic types "Additional attributes and information" — the "owner" of the values; this is exactly where the attribute for which values are needed is created.
- Catalog "Object property values" — a flat analog for attributes without hierarchy.
- Information registers "Additional attributes" / "Additional information" — store the fact "object → value," from here reports take analytics.
- Consumer documents (Sales of inventory and services, Receipt of inventory and services, Orders, etc.) — there the value is selected and participates in filters/groupings.
- Consumer catalogs (Counterparties, Items, Contracts) — if the additional attribute is configured for them, values from our catalog are entered in the cards.
How to find out your release: "Help" → "About the program" — there you'll find the platform and configuration release.
This guide was prepared for "Accounting for Kazakhstan," edition 3.0, release 3.0.74.2. On other releases, the composition of fields and commands may differ.