RUKKENZH
Задать вопрос AI
SectionsОбъекты конфигурации 1С
Directory "Order Management Stations and SMP TK" — Technical Description (Accounting for Kazakhstan 3.0.74.2)
Язык статьи:🇷🇺 RU🇰🇿 KK🇬🇧 EN🇨🇳 ZH

Directory "Order Management Stations and SMP TK" — 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 OrderManagementStationsISMP
Full Name Catalog.OrderManagementStationsISMP
Synonym — (not set)
Configuration Accounting for Kazakhstan, edition 3.0 (version 3.0.74.2)
Hierarchy None (flat list)
Owner No (independent catalog)
Purpose Centralized storage and management of configuration data about order management stations (OMS) within the integrated monitoring system of production and technological communications (ISMP). Registers external order management systems by their unique identifiers (OMS ID) for the integration of the 1C accounting system with production and logistics platforms of the goods labeling system (IS MPT) of Kazakhstan.

Scope of Application. The object is used by specialists working with goods labeling and tracking production orders. Access to it is periodic — when connecting a new order management station or changing parameters of an already connected one.

Where to find in 1C:

  • Interface: section “1C Service: Labeling (IS MPT)” → “Order Management Stations (OMS)”.
  • Navigation link: e1cib/list/Catalog.OrderManagementStationsISMP

2. Attributes and Table Parts

2.1 Header Attributes

Name Type Mandatory Purpose
Name (standard attribute) String Mandatory A human-readable name of the order management station. Used for selection and display in lists. Mandatory for any 1C catalog.
Identifier String (xs:string) Mandatory (control ShowError) Unique identifier of the order management station (OMS ID) for integration with external systems. Key field for data synchronization between 1C and production platforms.

2.2 Table Parts

None. The catalog has a simple flat structure: one record = one order management station.

2.3 Versioning

The object has a versioning mechanism (history of configuration changes of stations) — standard subsystem “Object Versioning” of BSL. Allows tracking who and when changed Name or Identifier.


3. Forms

Form Purpose Composition
SelectionForm Selecting a station from the list when filling in fields of documents/integration processing. Supports search and filtering. ~22 control elements: list table, search panel, command panel.
ElementForm (key for the user) Creating and editing an element of the catalog. ~12 control elements. Input fields: Name, Identifier.

The list form as a separate object can use an auto-generated (main) list form; for selection, SelectionForm is used.


4. Key Module Procedures

The attached evidence does not provide the source code (BSL) of the forms and object module. Below are typical handlers for a catalog of this type (simple catalog-registrar with filling control and versioning). Specific implementations should be compared with the modules of the specific version.

Object Module (ObjectModule):

  • CheckFilling(Refusal, CheckedAttributes) — control of mandatory filling of Identifier (mode ShowError) and Name. If the value is empty, sets Refusal = True.
  • OnWrite(Refusal) / BeforeWrite(Refusal) — if there is additional logic (for example, checking the uniqueness of OMS ID).

Element Form Module (ElementForm):

  • OnCreateOnServer(Refusal, StandardProcessing) — initial setup of the form, visibility, and availability of fields.
  • OnOpen(Refusal) — additional setup upon opening.
  • Field event handlers Name, Identifier (OnChange) — if there is control of format/duplicates.

Selection Form Module (SelectionForm):

  • OnCreateOnServer — setting filters and formatting the list, configuring search.

5. Posting and Movements

The catalog is not a document and does not perform postings — it does not generate records in accumulation/information registers and accounting entries. The object stores regulatory and reference (configuration) data for integration with IS MPT and does not participate in the formation of accounting movements directly.

How the object is indirectly related to accounting. The OMS station is used in the turnover chain of labeled products. Financial consequences arise already in the documents of sale/purchase of labeled goods, where the norms of the RK 2026 are applied and the standard chart of accounts:

Operation Debit Credit Comment
Sale of labeled goods 1210 (short-term receivables from buyers) 6010 (income from sales) For the amount of income
Accrual of VAT on sale 1210 3130 (VAT payable) VAT rate 16%
Cost of goods sold 7010 (cost of sales) 1330 (goods)
Receipt of goods 1330 3310 (payables to suppliers)
Payment from the buyer 1030 (cash in current accounts) 1210

Electronic documents. For the labeled turnover in the RK, electronic invoices (ESF) (IS ESF) and SNF are issued — they are generated by the documents of sale/movement, not by this catalog.

Reference values of the RK for 2026 (for related calculations in the configuration): MRP = 4,325 ₸, MZP = 85,000 ₸, VAT 16%, PIT 10% up to 8,500 MRP annual income and 15% above, basic deduction for PIT 30 MRP/month (not more than 360 MRP/year), OPE 10% (base ceiling 50 MZP), OPEP 3.5%, VOSMS 2%, OSMS 3%, SO 5%, social tax 6%. These norms have no direct relation to the catalog — they are provided as context for the configuration.


  • Input on basis / on basis — not provided for this catalog (typical for a configuration adjustment catalog).
  • Related subsystems: “1C: Labeling (IS MPT)”, subsystem for exchange with IS ESF and issuance of SNF.
  • Consumers of the value: processing and regulatory tasks for integration with external order management stations (OMS), where Identifier (OMS ID) serves as the synchronization key; documents of turnover of labeled products, where the station is indicated as an attribute of the order source.
  • Subsystem “Object Versioning” (BSL) — stores the history of changes to records.

7. Extension Points

  • Attributes (configuration extension): addition of information about the station — address/URL of the OMS service, token/connection credentials, status of activity, date of last synchronization, responsible person.
  • Object module handlers: redefinition of CheckFilling (checking uniqueness and format of OMS ID), BeforeWrite/OnWrite (logging, validation of connection).
  • Forms: enhancement of ElementForm (button “Check connection”, displaying synchronization status) and SelectionForm (additional filters by activity).
  • Event subscriptions: integration scenarios when recording/deleting a station.
  • Additional attributes and information (BSL) — for extendable attributes without changing the configuration.
  • Roles and access rights: restriction of editing the catalog to integration administrators of IS MPT.

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

Does this directory generate entries or movements in the registers?
No. This is a configuration directory for integration with the MPT IS; it is not a document, does not generate or create any accounting entries or movements in the registers. Financial entries (for example, sale of marked goods: Dr 1210 Cr 6010, VAT Dr 1210 Cr 3130 at a rate of 16%) occur in the documents of goods turnover, not here.
Which fields are mandatory to fill out?
The standard attribute "Name" and the attribute "Identifier" (OMS ID) with ShowError control are mandatory. The identifier serves as the synchronization key between 1C and the external order management station.
Where can the directory be found in the interface?
Section "1C Service: Marking (MPT IS)" → "Order Management Stations (OMS)". Navigation link: e1cib/list/Directory.OrderManagementStationsMPTIS.
Does the directory have table parts and hierarchy?
No. The structure is flat: one record corresponds to one order management station, there are no table parts, and hierarchy is not used.

Read also

Источники

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