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

Reference "Classifier of Measurement Units" — Technical Description (Accounting for Kazakhstan 3.0.74.2)

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

1. Identification

Parameter Value
Object Type Catalog
Name MeasurementUnitsClassifier
Full Name Catalog.MeasurementUnitsClassifier
Synonym — (uses the object name)
Configuration Accounting for Kazakhstan, edition 3.0, version 3.0.74.2
Hierarchy Flat (no groups) — linear list of measurement units
Owner No (independent catalog)

Purpose. The catalog stores and manages measurement units in accordance with the National Classifier of Measurement Units of Kazakhstan (NCMU). This is a basic reference catalog that is referenced by the attributes of the nomenclature, lines of incoming and outgoing documents, specifications, as well as mechanisms for generating electronic documents. When exporting to the ESF information system and when generating the tax return form (SNT), the unit code from the classifier of the ESF information system is taken from the element. The catalog is used daily by everyone who works with nomenclature and primary documents.

Where to find in 1C: section “Nomenclature and Warehouse” → “Measurement Units Classifier”. Navigation link: e1cib/list/Catalog.MeasurementUnitsClassifier.


2. Attributes of Headers and Table Parts

2.1 Header Attributes

Name Type Mandatory Purpose
Code Standard attribute (String) Automatically filled Code of the catalog item. Typically synchronized with the numeric code of the NCMU (for example, 166 — kilogram, 796 — piece)
Name Standard attribute (String) Mandatory Short designation of the unit (for example, “kg”, “pcs”, “l”) — what the user sees in documents
FullName xs:string Not mandatory (DontCheck) Full expanded name of the unit according to the NCMU (for example, “Kilogram” instead of “kg”)
ESFCode xs:string Not mandatory (DontCheck) Code of the measurement unit according to the classifier of the electronic invoice information system; used when exporting to the ESF and generating the SNT

2.2 Table Parts

Table parts are absent.

The practical meaning of separating codes: Code — internal/NCMU, ESFCode — code from the unit classifier of the ESF information system. They may not match, so for correct export of electronic documents, the ESFCode field must be filled for all units that actually go into the ESF/SNT.


3. Forms

The catalog contains 4 forms:

Form Purpose
ElementForm Main form for creating/editing a measurement unit. Here, Name, FullName, ESFCode are filled in
ListForm List of all measurement units; supports selection from the classifier and bulk modification of attributes
SelectionForm Form for selecting a unit from the list when filling in the attributes of the nomenclature and document lines; supports selection from the classifier
ClassifierSelectionForm Special form for loading units from the external NCMU classifier (tabular document), allows marking and transferring the necessary positions to the catalog

4. Key Module Procedures

Evidence with the text of BSL modules is not attached, so below are typical handlers characteristic of the classifier catalog of this type. Specific procedure names should be checked against the modules of the specified version.

Module of the form “ClassifierSelectionForm” (core loading of NCMU):

  • OnOpen / OnCreateOnServer — displays the tabular document with the predefined classifier of units (NCMU template).
  • Select / LoadSelected — creates or finds catalog items based on marked rows, filling in Code, Name, FullName, ESFCode.
  • SearchExistingElement — prevents duplication by NCMU code.

Module of the form “ElementForm”:

  • BeforeSavingOnServer / CheckFillingProcessing — controls the filling of Name; for units involved in ESF/SNT, controls the presence of ESFCode.

Module of the form “ListForm” / “SelectionForm”:

  • handlers for the command “Select from classifier” — open ClassifierSelectionForm and process the return of the selection.

Module object (typical):

  • FillingProcessing — when entering based on/copying.
  • BeforeSaving — service checks for code uniqueness.

Requires verification: the exact composition and names of export procedures of the module object in version 3.0.74.2 (may differ between releases).


5. Posting and Movements

The catalog is not a document and does not create movements in registers — does not create postings to accounts. This is an element of NSI.

Impact on accounting — indirect, through documents that refer to the measurement unit. The unit is substituted in the lines of primary documents and participates in the formation of standard postings according to the typical chart of accounts of the RK, for example, when selling goods:

Operation Debit Credit
Revenue recognized (with VAT) 1210 “Short-term receivables from customers” 6010 “Revenue from sales”
VAT accrued for payment (16%) 1210 3130 “VAT payable”
Cost of goods written off 7010 “Cost of sales” 1330 “Goods”
Receipt of goods from supplier 1330 3310 “Payables to suppliers”
Payment from current account 3310 1030 “Cash in current accounts”

Example: when shipping 10 kg of goods at a price of 5,000 ₸, the amount excluding VAT is 50,000 ₸, VAT 16% — 8,000 ₸, total payable 58,000 ₸. The unit “kg” (its ESFCode) is exported to the ESF and to the SNT. All amounts are in tenge (₸).

The role of the catalog in these movements is to provide the correct measurement unit and its code for quantitative accounting and for electronic documents; the unit itself does not affect monetary postings.


Referencing the catalog (consumer types):

  • Catalog.Nomenclature — attribute of the main measurement unit / unit for reports.
  • Table parts of incoming, outgoing, transfer, inventory documents (attribute “MeasurementUnit” of lines).
  • Specifications, assembly, production documents.
  • Mechanisms for generating ESF (ESF Information System) and SNT — take the ESFCode of the unit for the attribute “Measurement unit” of the electronic document.

Input based on: for the classifier catalog, input based on is not provided. The main method of mass filling is the command “Select from classifier” (form ClassifierSelectionForm), loading positions from the NCMU.


7. Extension Points

Recommended mechanisms for modifications without removing from support:

  • Configuration extension for forms ElementForm/ListForm — adding form attributes, commands, additional checks for filling ESFCode.
  • Additional attributes and information (plan of types of characteristics of the properties mechanism) — for storing non-standard attributes of the unit without changing the structure.
  • Event subscriptions BeforeSaving / CheckFillingProcessing — for implementing custom validation rules (for example, the mandatory presence of ESFCode for active units).
  • Overridable ESF/SNT export modules — for non-standard mapping of units with codes of the ESF information system.
  • HTTP/web services for exchange — if synchronization of the catalog with external systems is required.

Requires verification: the presence of specific overridable procedures of the ESF/SNT export modules in version 3.0.74.2 — the composition depends on the release of the electronic document library.

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

What is the difference between the "Code" field and "ESF Code"?
"Code" is the internal code of the reference directory element, usually matching the numerical code of OKEI (for example, 166 — kilogram). "ESF Code" is the unit code according to the classifier of the electronic invoice information system; it is the one that is exported to the ESF and STS. The values may not match, so the ESF Code needs to be filled in for all units that actually appear in electronic documents.
Does the directory generate entries or movements in the registers?
No. This is an element of the NSI, it is not a document and does not create movements. It indirectly affects accounting — through documents where the unit is used in quantitative accounting and when generating ESF/STS. The entries for RK accounts (1210, 6010, 3130, 7010, 1330, 3310, 1030) are generated by the documents themselves.
How to quickly fill the directory with units of measurement?
Use the "Select from classifier" command — it opens the Form for Selecting from Classifier with the tabular document of OKEI. You mark the necessary positions, and the system creates elements with filled Code, Name, FullName, and ESF Code, checking for duplicates by code.
What will happen when exporting the ESF if the ESF Code is not filled in?
The "Unit of Measurement" attribute of the electronic document will be either unfilled or invalid, which will lead to a format and logical control error in the ESF information system. Therefore, for units involved in sales and issuing ESF/STS, filling in the ESF Code is mandatory in practice, although at the metadata level the attribute is marked as DontCheck.

Read also

Источники

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