1. Identification
| Parameter | Value |
|---|---|
| Object Type | Document (Documents) |
| Name | OrderOfLabelingCodesFromISMP |
| Full Name | Document.OrderOfLabelingCodesFromISMP |
| Synonym | Order for the issuance of labeling codes (IS) |
| Configuration | Accounting for Kazakhstan, edition 3.0 (version 3.0.74.2) |
| Country of Accounting | Kazakhstan (₸) |
Purpose. The document generates orders for obtaining labeling codes from the state system IS MP (Information System for Labeling and Traceability of Goods of the RK) through integration with IS (Order Management System). It is used by manufacturing and importing organizations to submit applications for the issuance of identification codes necessary for labeling tobacco, dairy, textile, and footwear products before they are put into circulation.
The document goes through the life cycle:
Draft Creation → Sending to IS → Receiving Codes
→ Applying to Goods → Actual Introduction into Circulation
Where to find in 1C: section "1C Service: Labeling (IS MP)" → "Order for the issuance of labeling codes (IS)".
Navigation link: e1cib/list/Document.OrderOfLabelingCodesFromISMP.
2. Attributes of Header and Table Parts
2.1. Header Attributes
| Attribute | Purpose | Mandatory |
|---|---|---|
Organization |
Applicant organization on behalf of which the order is formed in IS | Yes |
ProductType |
Product group of IS MP (tobacco, milk, textiles, footwear) — determines the rules for code generation | Yes |
MethodOfIntroductionIntoCirculation |
Basis for introduction into circulation (production in the RK, import, labeling of residues, etc.) | Yes |
ContactPerson |
Responsible person for interaction with the operator of IS MP | Yes |
ProductionIdentifier |
Identifier of the production site in the labeling system | Yes |
CountryOfManufacturer |
Country of the product manufacturer | Yes |
ProductionLineIdentifier |
Identifier of a specific production line | Yes |
Service attributes of the life cycle usually include: order status in IS, order identifier received from the operator, date of sending/receiving, code application indicator. They are filled automatically during the exchange with IS.
If any of the mandatory attributes are not filled in, the platform will not process (will not record with the required status) the document and will issue an error of the type "Field ... is not filled in".
2.2. Table Part "Products"
| Column | Purpose | Mandatory |
|---|---|---|
GTIN |
Global Trade Item Number for which labeling codes are ordered | Yes |
NumberOfPackages |
Number of units/packages for which codes are needed (volume of issuance) | Yes |
Template |
Template for generating the labeling code for this GTIN | Yes |
MethodOfGeneratingSerialNumber |
Method of generating the serial number (generated by the operator / set manually / from a pool) | Yes |
When using the manual method, serial numbers are linked to the rows, editable through the serial selection form (see section 4).
3. Forms
| Form | Purpose |
|---|---|
| Document Form (DocumentForm) | Main form for filling out the order: header, table part "Products", life cycle commands (send to IS, receive codes, arrange application) |
| List Form (ListForm) | List of orders filtered by organization, product type, status in IS |
SerialSelectionForm |
Input and verification of serial numbers for product items when using the manual method of generating the serial number |
4. Key Module Procedures
From the reference evidence, the handlers for the serial selection form are confirmed (release 3.0.68.1, message texts are verbatim):
| Handler | What it does |
|---|---|
Form.SerialSelectionForm / SerialNumbersBeforeEditingEnds |
Validates the entered serial number: checks the required number of characters and prohibits spaces. Message: "Required number of characters for the serial number: %1. Use of spaces is not allowed." |
Form.SerialSelectionForm / SerialNumbersBeforeAddingStarts |
Blocks the addition of extra series when the limit is reached. Condition: RequiredQuantity <= SerialNumbers.Count(). Message: "All series have already been specified." |
Standard document handlers of this type (general logic of 1C; specified for a specific version):
FillingHandler— filling in attributes during input, including based on.FillingCheckHandler— control of mandatory fields (Organization, ProductType, GTIN, etc.) before recording.BeforeRecording/OnRecording— fixing status changes, preparing data for exchange with IS.- Form commands for exchange: generating XML/JSON order package, sending to IS, receiving codes, splitting the order, exporting codes to a file.
5. Processing and Movements
The document does not generate movements in accounting and accumulation registers. In the handler ProcessingHandler, movements are not created — this is a registration document, managing the life cycle of the labeling codes order, not a business operation.
Accordingly, accounting entries according to the typical chart of accounts of the RK (for example, 1330 "Goods", 3310 "Accounts Payable", 3130 "VAT Payable", 6010/7010, etc.) are not generated by this document. Financial consequences (recognition of labeled products, sales, VAT 16%) are reflected by related accounting documents — production and sales — rather than by the order of codes.
The result of the document's work is recorded in the service data of the order and in the subsystem for exchange with IS MP (statuses, received codes, linking of serial numbers), not in accounting registers.
6. Related Objects and Input Based On
- Exchange with IS MP / IS — the document is the core of integration scenarios:
- 3.1 Creating an order for production — planning the release of a batch of labeled products.
- 3.2 Sending the order to IS — registration in the state system.
- 3.3 Receiving labeling codes — receiving codes when the status is "Codes ready" / "Partially ready".
- 3.4 Arranging the application of codes to goods — fixing the physical application of labeling.
- 3.5 Splitting a large order into several documents — when there are excess items/codes for IS.
- 3.6 Exporting labeling codes to a file — transferring to labeling equipment or to a third-party system.
- Production Documents — source of batches of products to which the received codes are applied.
- Sales Documents, ESF, and CNT — use the result of labeling when introducing into circulation and shipping; they reflect income (6010), cost of goods sold (7010), and VAT payable (3130) considering the rate of 16%.
- Input Based On: the order is usually formed based on the production/release plan and, in turn, serves as the basis for documents for applying and circulating codes.
7. Extension Points
- Validation Rules for Serial Numbers — overriding
SerialNumbersBeforeEditingEnds/SerialNumbersBeforeAddingStartsin the serial selection form (length, allowed characters, limits). - Filling Check — extending
FillingCheckHandlerfor additional attributes of the production site/line. - Generating Exchange Package with IS — subscribing/overriding order serialization procedures before sending (adapting to changes in the format of the IS MP operator).
- Processing Responses from IS — points for receiving statuses and labeling codes (custom routing by product types).
- Form Commands — adding custom actions (mass export of codes, automatic splitting of orders by quantity threshold).
- Rights and Status Model — restricting life cycle transitions by roles (draft → sent → codes received → application).
Exchange formats with IS/IS MP and exact texts of handlers are version-dependent (evidence taken from release 3.0.68.1). When modifying for 3.0.74.2, check the composition of exchange attributes and message codes with the current release.