Directory "Object Property Values Hierarchy" — Technical Description (Accounting for Kazakhstan 3.0.74.2)

1. Identification

Purpose. The catalog stores hierarchical values of additional properties (characteristics) of accounting objects — for example, multi-level product classifiers, categories of counterparties, types of assets. It is part of the subsystem for managing object properties (BSP, "Properties") and works in conjunction with the flat catalog ObjectPropertyValues: this catalog is used when a property with the value type "Additional Value (Hierarchy)" requires a tree structure of values with grouping.

The catalog is subordinate: each of its elements is necessarily linked to a property through the attribute Owner. Values are used when filling additional attributes and information of objects (documents, catalogs), for analytical accounting and selection. Multilingual representations are supported.

Where to find in the interface: section "Administration" / "Settings" → working with properties (additional attributes and information); the values themselves are opened from the property card with the type "Additional Value (Hierarchy)" or directly via the navigation link e1cib/list/Catalog.ObjectPropertyValuesHierarchy.

2. Attributes and Table Parts

2.1 Header Attributes

Standard attributes of the hierarchical subordinate catalog:

2.2 Table Parts

Representations — storage of multilingual variants of the value name.

When working in a multilingual interface (in the RK, typically Russian + Kazakh), the value is substituted from the row of the table corresponding to the current session language; if there is no row, the main attribute Name is used.

3. Forms

The group form is typically not described separately — the general element form is used with the group indicator or an auto-generated group form of BSP.

4. Key Module Procedures

No separate application BSL code in evidence for this object is attached, so below are typical handlers characteristic of the subordinate hierarchical catalog of property values in BSP.

Object Module:

• FillProcessing(FillData, ...) — when entering based on/from selection, substitutes Owner (property) from the context.
• BeforeSaving(Refusal) — control of hierarchy correctness (parent belongs to the same owner), synchronization of the main Name with the Representations row for the current language.
• OnCopying(CopyingObject) — clearing service fields when copying a value.

Element Form Module:

• OnCreatingOnServer(Refusal, StandardProcessing) — setting visibility of attributes (full name, weight), initializing the representation table by configuration languages.
• OnSavingOnServer(...) — updating representations.

List Form Module:

• OnCreatingOnServer(...) — setting selection by Owner (current property), configuring the dynamic list as hierarchical.

Requires verification: the presence and exact signature of handlers may differ in the specific build 3.0.74.2 — when modifying, clarify regarding the object/form module in the configurator.

5. Posting and Movements

The catalog is not a document and is not posted: it does not generate accounting entries and does not create movements in accounting or accumulation registers. Its role is a storage of analytical values.

Impact on accounting — indirect: values of this catalog are substituted in additional attributes/information of objects and can be used as analytics, selection, grouping in reports. The entries themselves are generated by documents referring to objects with these properties.

For reference — typical accounts of the RK chart of accounts, the analytics of which can be detailed by properties (product classification, categories of counterparties):

Electronic documents of the RK (ESF in the ESF IS, STS) are generated by documents of sales/receipts; property values can participate in their analytics and selections, but the catalog itself does not create them.

Numerical norms of the RK for 2026, relevant for calculation documents of the configuration (for reference): MRP = 4,325 ₸, MZP = 85,000 ₸; VAT rate 16%; basic deduction for PIT — 30 MRP/month (not more than 360 MRP per year); PIT 10% up to 8,500 MRP of annual income and 15% above; OPE 10% (base cap 50 MZP), OPEI 3.5%, VOSMS 2%, OSMS 3%, SO 5%, social tax 6%. The norms do not have a direct relation to the catalog of property values.

6. Related Objects and Input Based On

• Property Catalog — owner; defines to which property the values belong.
• Catalog ObjectPropertyValues — "flat" analog for properties without hierarchy; the choice between them depends on the configuration of the property value type.
• Information Register "Additional Information" and sets of additional attributes of objects — consumers of values.
• Objects carrying properties — catalogs and documents of the configuration (nomenclature, counterparties, etc.), in the additional attributes/information of which these values are used.

Input based on for this catalog is typically not provided. New values are created:

• from the property card (type "Additional Value (Hierarchy)") — with auto-substitution of the owner;
• from the selection field of the object's additional attribute — with quick addition;
• directly from the list form via the navigation link.

7. Extension Points

• Configuration extension for element/list form: adding hierarchy checks, additional attributes, buttons.
• BSP handlers of the "Properties" subsystem — overriding the logic of filling and displaying values.
• Additional attributes of the object — standard mechanism for extension without changing metadata.
• Multilingualism: filling the Representations table for new interface languages.
• Event subscriptions (BeforeSaving, OnSaving) for integration with external classifiers.

When modifying, adhere to the principle of subordination (owner is mandatory) and do not violate the integrity of the hierarchy within one owner.