RUKKENZH
Задать вопрос AI
SectionsОбъекты конфигурации 1С
Directory "Specifications of Nomenclature" (Accounting for Kazakhstan 3.0)
Язык статьи:🇷🇺 RU🇰🇿 KK🇬🇧 EN🇨🇳 ZH
Версия статьи:📘 Для бухгалтера⚙️ Для тех-специалиста

Directory "Specifications of Nomenclature" (Accounting for Kazakhstan 3.0)

Applies to: 1С:Бухгалтерия для Казахстана, release 3.0.74.2 · by 1C-Sapa Group, 1C partner
СТ
Сапа Т.И. — Эксперт по 1С и бухгалтерскому учёту, преподаватель-практик

1. Identification

Parameter Value
Metadata object type Catalog
Name SpecificationsOfGoods
Full name Catalog.SpecificationsOfGoods / Catalogs.SpecificationsOfGoods
Synonym Specifications of goods
Hierarchy Hierarchical (groups and items)
Owner (subordinate) Catalog.Reference.Goods
Configuration Accounting for Kazakhstan, version 3.0 (3.0.74.2)
Where to find Section "Goods and Warehouse" → "Specifications of goods".
Navigation link: e1cib/list/Catalog.SpecificationsOfGoods

Purpose. The catalog stores the composition of complex products, goods, or sets — from which components and in what quantities they are assembled. It is used in production accounting: when forming production orders, calculating material requirements, assembling/disassembling, and unbundling products. The catalog is subordinate to the catalog Goods, so multiple specification variants can be linked to one item (for example, for different technologies or batches). Typical users are technologists, production managers, and warehouse workers.


2. Attributes and table parts

2.1 Header attributes

Name Type Mandatory Purpose
Quantity xs:decimal (Number) DontCheck (not checked) The base quantity of the finished product for which the specification is calculated (for example, "for 1 pc." or "for a batch of 100 pcs."). Used for proportional recalculation of the need for components.

Standard attributes of the subordinate hierarchical catalog:

Name Type Purpose
Name String Name of the specification variant
Code String/Number Auto-numbering of the item
Parent CatalogReference.SpecificationsOfGoods Grouping of specifications by folders
Owner CatalogReference.Goods The product for which the specification is created
ThisIsGroup Boolean Group indicator
DeletionMark, Predefined system Standard system attributes

2.2 Table part "InitialComponents"

Purpose: a list of materials, semi-finished products, and components necessary for the manufacture of the owner product according to this specification.

Name Type Purpose
Goods CatalogRef.Goods Item used as raw material or component
Quantity xs:decimal (Number) Normative quantity of the component for the base quantity of the finished product (attribute Quantity of the header)

Recalculation of needs. If the product is produced in a batch different from the base, the need is calculated proportionally:

Material_Need = Quantity_in_specification × (Production / Base_Quantity)

3. Forms

The catalog contains 5 forms:

Form Purpose
ElementForm Main form for editing the specification item. Contains 7 input fields, a button for selecting components, and a table part for editing the composition of InitialComponents.
ListForm List of specifications; supports the group change command for selected records.
SelectForm Selecting a specification from the list (with filtering, including by owner-goods).
GroupForm Editing a group (folder) of specifications; 4 input fields.
SelectGroupForm Selecting a group from the hierarchy.

4. Key module procedures

No separate evidence for BSL modules of the catalog is attached. For a catalog of this type (subordinate, without posting), standard handlers are typical; below is a standard layout.

Module of the form "ElementForm" (standard handlers):

  • OnCreateOnServer — initial setup of the form, availability of attributes, setting selection of components by owner.
  • OnOpen — fine-tuning the appearance.
  • Command "Select" / SelectComponents — opening the form for selecting goods to fill the table part InitialComponents.
  • InitialComponentsGoodsOnChange — control of duplicate rows, setting unit of measure/default value.
  • InitialComponentsQuantityOnChange — validation of quantity (> 0).

Module of the object (standard handlers):

  • FillProcessing — filling when entering based on (from goods).
  • CheckFilling — control of mandatory filling of the owner, presence of at least one line of components.
  • BeforeSaving — control of the correctness of the composition (for example, the product should not be included in its own specification — protection against cycles).

Requires verification in the specific assembly 3.0.74.2: presence and exact composition of the module procedures (in basic versions, the object module may be empty, and the logic may be in common modules/manager).


5. Posting and movements

The catalog is not a document — it is not posted and does not independently generate accounting entries and movements in registers. The specification serves as a source of normative data (composition of the product) for production and warehouse documents.

Movements are generated by documents that use the specification to fill materials/releases. According to the typical logic of the configuration and the chart of accounts of the RK:

Product release / assembly:

Debit Credit Content
1330 "Goods" (or GP account) 1330 "Goods" (materials) Write-off of initial components in the composition of the released product according to the quantity from the specification

Sale of the finished product (for the context of further movement):

Debit Credit Content
1210 "Short-term receivables from customers" 6010 "Revenue from sales" Revenue
1210 3130 "VAT payable" VAT at the rate of 16%
7010 "Cost of goods sold" 1330 "Goods" Write-off of the cost of the product
1030 "Cash in current accounts" 1210 Receipt of payment

Example for VAT: at a selling price of 100,000 ₸, the VAT amount = 100,000 × 16% = 16,000 ₸ (Debit 1210 Credit 3130), total payable 116,000 ₸.

Electronic support for the sale of the released product: ESF (ESF IS) and if necessary SNT — are generated on the side of the sales/movement documents, not the specification itself.


Owner:

  • Catalog.Goods — the product for which the specification is created.

Consumers of the specification (typical documents using the composition):

  • Documents for release/production of goods.
  • Documents for assembly and disassembly (assembly/disassembly of sets).
  • Processes for calculating material needs.

Input on basis:

  • The specification can be created based on the item Goods (with automatic substitution of the owner).
  • In release/assembly documents, the specification is selected in the reference attribute, and by clicking the "Fill by specification" button, the table part of materials is filled with the composition of InitialComponents with recalculation according to the quantity of release.

7. Extension points

  • Configuration extension (Extension): adding header attributes (for example, "StartDate", "TechnologicalOperation", "Active") and columns in InitialComponents (waste norm, coefficient, analog-replacement) without removing from support.
  • Event subscriptions: BeforeSaving/OnSaving of the catalog — to control the uniqueness of the active specification for the product or logging changes in the composition.
  • Common manager modules: methods for obtaining the active specification by goods, unbundling (recursive unfolding of multi-level composition to raw materials).
  • Forms: overriding ElementForm to embed selection by warehouse balances, displaying shortages.
  • Additional reports/processings (BSP): report "Composition of the product", processing of mass recalculation of norms.
  • Access rights / RLS: limiting the visibility of specifications by organization/department through BSP mechanisms, if separation is required.

Частые вопросы

Does the directory "Specifications of Nomenclature" generate entries?
No. This is a directory, not a document — it does not create entries and does not generate movements in registers/accounts. Entries are generated by production, assembly, and sales documents that use the specification to fill in the composition of materials.
Why is the directory subordinate to Nomenclature?
The owner of the directory is Directory.Nomenclature. This allows multiple specification variants to be linked to a single nomenclature item (product), for example, for different technologies or batch volumes.
How is the need for components recalculated with a different production volume?
Proportionally to the base quantity from the header attribute "Quantity": Need = Quantity_in_specification × (Production / Base_Quantity).
What VAT rate applies when selling the produced item?
In Kazakhstan, for 2026 — 16%. For example, at a price of 100,000 ₸ VAT = 16,000 ₸ (Debit 1210 Credit 3130), to be paid 116,000 ₸.
Where can the directory be found in the interface?
Section "Nomenclature and Warehouse" → "Specifications of Nomenclature". Direct navigation link: e1cib/list/Directory.SpecificationsOfNomenclature.

Read also

Источники

Была ли статья полезна?
💼 Нужна помощь с 1С или учётом? Слава КВЦ — многолетняя практика в 1С в Казахстане. Изучите разложенный НК РК 2026 или спросите в чате BuhGPT — ответит за секунды.