1. Identification
| Parameter | Value |
|---|---|
| Object Type | Catalog |
| Name | RemovePropertyValuesOfObjects |
| Full Name | Catalog.RemovePropertyValuesOfObjects |
| Alias | — (marked in the configuration with the comment "Do not use") |
| Configuration | Accounting for Kazakhstan, edition 3.0, version 3.0.74.2 |
| Status | System, marked for deletion (prefix "Remove" in the name) |
| Navigation Link | e1cib/list/Catalog.RemovePropertyValuesOfObjects |
Purpose. System catalog for storing values of additional properties (user-defined attributes) of accounting objects. The object is deprecated: the mechanism for additional properties in the current edition 3.0 is implemented through the BSP subsystem "Properties" (characteristic types plan AdditionalAttributesAndInformation and information register AdditionalInformation), and this catalog is left solely for data migration and backward compatibility with old databases. Users do not work with it directly.
Where to find: the object is intentionally hidden from the interface. Technically available only through the navigation string
e1cib/list/Catalog.RemovePropertyValuesOfObjects(when the display mode for marked for deletion objects is enabled).
2. Attributes and Tabular Parts
2.1 Header Attributes
User-defined attributes are absent (attributes: []). Only standard attributes of the catalog are available:
| Name | Type | Mandatory | Purpose |
|---|---|---|---|
| Owner | Depends on the settings of the catalog owners | Yes | Reference to the owner object to which the property value belongs |
| Name | String | Yes | Text representation of the property value |
| Code | String/Number | No | Unique code of the catalog item |
Note: the list of attributes is derived from the composition of the element form fields (input_fields of the ElementForm).
2.2 Tabular Parts
Tabular parts are absent (tabular_sections: []).
3. Forms
The catalog contains three standard forms:
| Form | Type | Purpose |
|---|---|---|
| ListForm | List | View all items of the catalog. ~32 control elements: list table, command panel, search fields. Key command — "EditSelected" (bulk editing of selected items). |
| ElementForm | Element | Editing a single item: input fields Owner, Name, Code. ~13 elements, minimalist structure without tabs and panels. |
| SelectionForm | Selection | Selection of an item when choosing from other forms of the configuration. ~26 elements: table with search and filtering; no specific action commands. |
4. Key Procedures of Modules
No specific BSL code in evidence for this object is attached — the catalog does not carry business logic. Below are typical handlers characteristic of a system catalog of this type:
- Object Module — usually empty or contains standard stubs. No specific
ProcessingConducting(the catalog is not conducted). - Manager Module — standard; possible
GetSelectionForm/ProcessingGettingDisplayFieldsin the volume of platform stubs. - ListForm → command "EditSelected" — calls the typical BSP processing "Bulk Change of Attributes" (
BulkChangeOfObjects) for batch editing of marked rows. - ElementForm → BeforeWriting/ProcessingWriting — standard check for filling mandatory attributes (Owner, Name).
Requires verification: the presence/content of the object module is version-specific — in different builds 3.0.74.x the code may be completely removed when preparing the object for final removal.
5. Conducting and Movements
The catalog is not a document and is not conducted — it does not generate movements in accumulation registers, information or accounting.
For reference: amounts of additional properties, if they were used in the old mechanism, did not directly enter accounting. Actual accounting entries are formed by configuration documents according to the standard chart of accounts of the RK, for example, when selling goods:
| Operation | Debit | Credit | Comment |
|---|---|---|---|
| Recognition of revenue from sales | 1210 | 6010 | Customer debt / revenue from sales |
| Accrual of VAT payable | 1210 | 3130 | VAT at the rate of 16% (Kazakhstan, 2026) |
| Write-off of cost | 7010 | 1330 | Cost of sales / goods |
| Receipt of payment | 1030 | 1210 | Money in current accounts |
| Settlements with suppliers | 1330 | 3310 | Receipt of goods / liabilities to suppliers |
These entries do not relate to the catalog in question and are provided only as context for the chart of accounts of the RK.
6. Related Objects and Input on Basis
- Input on Basis — not supported (not applicable for value catalogs).
- Owner — the catalog is subordinate; the owner is the objects that carry the properties of the old mechanism.
- Current Replacement — BSP subsystem "Properties": characteristic types plan
AdditionalAttributesAndInformation, information registerAdditionalInformation, catalog of valuesPropertyValuesOfObjects(without the prefix "Remove"). This is where the data is transferred during migration. - Other References — the object may be referenced by outdated exchange nodes/conversion rules when transitioning from old databases.
7. Extension Points
- Do not extend in new modifications. The object is marked for deletion; any logic of additional properties should be built on the BSP subsystem "Properties".
- Data Migration — the only justified scenario for addressing: transferring values from this catalog to the current mechanism through a regulatory task/update processing of the information base.
- Configuration Extension — adding attributes/forms to the marked for deletion object is not recommended: when the object is removed in future releases, the extension will become non-functional.
- Data Exchange/КД 2 or 3 — when exporting from old databases, provide a conversion rule "old catalog → register
AdditionalInformation".