1. Identification
| Parameter | Value |
|---|---|
| Object type | Catalog |
| Name | ГруппыДоступаНоменклатуры |
| Full name | Справочник.ГруппыДоступаНоменклатуры |
| Synonym | "Item Access Groups" |
| Configuration | Trade Management for Kazakhstan, edition 3.4 (build 3.4.5.21) |
| Subsystem | Service subsystems (data access restriction mechanism) |
| Purpose | Classifier for grouping item entries in order to configure record-level access rights (RLS). Allows dividing visibility and availability of items between users/user groups without listing individual item cards. |
Where to find in 1C: "Service subsystems" section → "Item access groups".
Navigation link: e1cib/list/Справочник.ГруппыДоступаНоменклатуры
The catalog is a service (administrative) one. It is not directly involved in inventory or financial accounting — it does not generate warehouse or accounting movements. Its sole function is to serve as an "access tag" referenced by items, which access restriction templates use for processing.
2. Header attributes and tabular sections
The catalog is simple (not subordinate to an owner); hierarchy is generally not used, or a group hierarchy is used. There are no tabular sections.
Standard attributes
| Attribute | Type | Purpose |
|---|---|---|
Код (Code) |
String/Number | Unique code of the item. Assigned automatically. |
Наименование (Description) |
String | Name of the access group (e.g., "General", "Alcoholic products", "Labeled goods", "Almaty branch goods"). |
ПометкаУдаления (Deletion mark) |
Boolean | Flag indicating the item is marked for deletion. |
Предопределённый (Predefined) |
Service | Flag indicating a predefined item. Usually there is a predefined item used by default (e.g., "MainAccessGroup" / "General"). |
Ссылка (Reference), ЭтоГруппа (IsFolder) |
Service | Standard platform fields. |
Own header attributes
For a service classifier, the set of own attributes is minimal. As a rule, besides Наименование (Description) there are no additional application attributes — the entire application load lies in the "Item → Access group" link and in the permission settings register.
"Requires verification" (version-specific): the presence in the specific build 3.4.5.21 of an additional description attribute or a "Used by default" flag — to be clarified in the Designer, as the composition may differ between 3.4 releases.
3. Forms
| Form | Purpose |
|---|---|
ФормаСписка (List form) |
Viewing and maintaining the list of access groups by an administrator. The main working form of the catalog. |
ФормаЭлемента (Item form) |
Creating/editing an individual access group (description, deletion mark). |
ФормаВыбора (Selection form) |
Selecting a value when filling in the "Item access group" attribute in the item card and in permission settings. |
ФормаГруппы (Group form) |
Used if group hierarchy is enabled for the catalog. |
If no forms are explicitly specified, the platform uses automatically generated default forms with the same purpose.
4. Key module procedures
The attached evidence does not include the module (BSL), so below are typical handlers characteristic of a service catalog of this kind. Specific lines are indicated when a module export is available.
Object module (ОбработкаЗаполнения (FillingProcessing), ПередЗаписью (BeforeWrite), ПередУдалением (BeforeDelete)):
ОбработкаЗаполнения(FillingProcessing) — filling default attributes when interactively creating a new item.ПередЗаписью(BeforeWrite) — correctness control (e.g., prohibiting clearing the description); if necessary — prohibiting the deletion mark on the predefined item used by default.ПередУдалением(BeforeDelete) — usually empty; referential integrity control is performed by the platform.
Manager module:
- May contain procedures for obtaining the default group value (for substitution in new items) and functions for the access rights mechanism.
Form modules:
ФормаСписка.ПриСозданииНаСервере(List form.OnCreateAtServer) — configuring filters/appearance (hiding service items).ФормаЭлемента.ОбработкаПроверкиЗаполнения(Item form.FillCheckProcessing) — checking that the description is filled in.
Since the catalog is a service one, no heavy business logic is expected in the modules: the main logic is implemented not in the catalog itself, but in the access restriction templates (RLS) and in the permission settings register.
5. Posting and movements
The catalog is not posted and does not generate movements in accumulation registers, information registers, or accounting entries. As a "Catalog" type metadata object, it has no posting mechanism.
The object's role in accounting is indirect, through the access restriction mechanism:
- In the item card (
Справочник.Номенклатура), the "Item access group" attribute is filled in, referencing this catalog. - In the permission settings subsystem, the administrator specifies which item access groups are allowed for user profiles/groups.
Thus, the catalog itself does not set accounts. At the same time, items assigned to an access group participate in standard KZ operations that generate entries under the standard Kazakhstan chart of accounts — for example, when selling goods:
| Operation | Dr | Cr |
|---|---|---|
| Revenue from sales | 1210 (short-term accounts receivable from customers) | 6010 (income from sales) |
| VAT on sales (16% rate) | 1210 | 3130 (VAT payable) |
| Cost of goods sold write-off | 7010 (cost of sales) | 1330 (goods) |
| Payment from customer | 1030 (cash in current accounts) | 1210 |
| Goods receipt | 1330 | 3310 (accounts payable to suppliers) |
These entries are generated by sales/receipt documents, not by the access groups catalog. The access group only determines which users will see this data. Electronic documents (ESF via the ESF IS, SNT) are also issued based on items, but the issuing is performed by the corresponding documents, not by the catalog under consideration.
6. Related objects and input based on
References to the catalog:
Справочник.Номенклатура(Item catalog) — the "Item access group" attribute (main link).- Possibly — item types/groups that set a default access group for the items belonging to them.
- Information register of item access permission settings (stores the correspondence "user group ↔ allowed access groups").
- Access restriction templates (RLS) of configuration roles.
Input based on: not provided (not applicable for a service classifier).
Data exchange / DIB: catalog items, as a rule, migrate to all nodes, since access rules must be consistent across the distributed database.
7. Extension points
- Configuration extensions: adding own attributes (e.g., "Responsible", "Comment"), overriding the list/item forms, adding
ПередЗаписью(BeforeWrite)/ОбработкаПроверкиЗаполнения(FillCheckProcessing) handlers without removing the configuration from support. - "Properties" subsystem: connecting additional attributes and information to the catalog via the additional attributes mechanism.
- Access restriction mechanism: refining RLS templates and access group profile settings to extend item visibility logic.
- Default filling: overriding the procedure for substituting the access group into a new item (e.g., determining it based on item type or organization).
- Programmatic interface: accessing the catalog from common modules for bulk assignment/change of the access group for items during data loading or permission reorganization.
"Requires verification" (version-specific): the exact set of roles and RLS templates using this catalog, and the presence of a functional option enabling the item access groups mechanism — to be clarified in the specific build 3.4.5.21.