1. Identification
| Parameter | Value |
|---|---|
| Object Type | Document (Documents) |
| Name | AggregationOutsideProductionISCEDM |
| Full Name | Document.AggregationOutsideProductionISCEDM |
| Synonym | Aggregation of marking codes (outside production) (IS CEDM) |
| Configuration | Accounting for Kazakhstan, edition 3.0 (version 3.0.74.2) |
| Navigation Link | e1cib/list/Document.AggregationOutsideProductionISCEDM |
Purpose. The document registers aggregation operations of product marking codes outside the production cycle within the integration with the Information System for Control (IS CEDM) of the Republic of Kazakhstan. It is used by warehouse workers and logisticians when forming transport packages (boxes, pallets) from individual consumer units of goods that already have individual marking codes. The document ensures bilateral synchronization with the state CEDM system, tracking the statuses of sending and registering aggregates. Input is automated through barcode scanners, TSDs, and mobile applications.
Where to find in 1C: section “1C Service: Marking (IS CEDM)” → “Aggregation of marking codes (outside production) (IS CEDM)”.
Important: this is an integration document for marking. It is not an accounting document for the movement of goods or money and does not generate accounting entries (see section 5). Tax rates and the chart of accounts of the RK do not apply directly to it.
2. Header Attributes and Table Parts
2.1 Header Attributes
| Attribute | Type (standard) | Mandatory | Purpose |
|---|---|---|---|
| Organization | ReferenceLink.Organizations | Yes | The organization on behalf of which the aggregation and exchange with CEDM is performed |
| SupplierIdentificationNumber | String | Yes | The identification number of the participant in the turnover (BIN/IIN of the supplier), used when registering the aggregate in CEDM |
| ProductType | Enumeration / String | Yes | Product group of marked goods (determines the exchange scheme and the composition of the marking codes attributes) |
| Date, Number | Date, String | — | Standard document attributes |
| Status / ExchangeStatus | Enumeration | — | Current state of the document in the exchange cycle with CEDM (draft, sent, registered, error) |
| Responsible | ReferenceLink.Users | — | Author/responsible for the document |
| Comment | String | — | Arbitrary note |
Mandatory attributes for evidence: Organization, SupplierIdentificationNumber, ProductType. If any of them are not filled, 1C will not allow the document to be processed and will issue an error “Field … is not filled”.
2.2 Table Parts
| Table Part | Purpose |
|---|---|
| Aggregation Codes (codes of nested units) | List of individual marking codes of consumer units placed in the transport package; filled by scanner, from TSD or by uploading from CSV |
| Aggregates (codes of transport packages) | Generated codes of boxes/pallets and the relationship “package → nested codes” |
| Typical Errors | Service table for registering validation and exchange errors with IS CEDM |
Table Part “Typical Errors”:
| Name | Type | Purpose |
|---|---|---|
| Text | String | Description of the error |
| Field | String | Name of the attribute or table field that caused the error |
3. Forms
| Form | Purpose |
|---|---|
| Document Form (DocumentForm) | Main form for input/editing: filling in the header, working with codes via scanner/TSD, uploading from CSV, initiating exchange with CEDM, viewing statuses and error tables |
| List Form (ListForm) | List of aggregation documents with exchange status columns; opens via link e1cib/list/Document.AggregationOutsideProductionISCEDM |
| Selection Form | Selection of documents in related objects and commands |
| Auxiliary Exchange Forms | Dialogs for sending to CEDM, obtaining additional information on codes, displaying exchange results and errors |
4. Key Procedures of Modules
In the attached evidence, the original BSL code of procedures is not provided (scenarios and structure are given). Below are the typical handlers of documents of this type and procedures implementing the scenarios described in the evidence.
4.1 Typical Handlers (object module / form)
HandlingFilling— filling in default attributes (organization, date, responsible) when creating.HandlingCheckFilling— control of mandatory fields (Organization, SupplierIdentificationNumber, ProductType) and correctness of the composition of codes; filling the table part “Typical Errors”.BeforeRecording/OnRecording— recording the exchange status, validating codes before saving.HandlingConducting— empty in the logic of the object (the document does not generate movements, see section 5).
4.2 Scenario Procedures (evidence 3.1–3.5)
- Creating a document with a scanner (3.1) — scanner/TSD event handler: receiving code, checking format and uniqueness, adding a line to the table part of codes.
- Loading codes from CSV (3.2) — mass import command: reading the file, parsing lines, filling the table part, registering incorrect lines in “Typical Errors”.
- Sending the document to IS CEDM (3.3) — forming an exchange package, calling the web service/integration handler, setting the status, parsing the receipt.
- Receiving information on codes from CEDM (3.4) — requesting status and owner of codes for controlling the legality of goods, displaying the result.
- Copying the document (3.5) — standard copying with resetting the exchange status and service attributes of registration in CEDM.
Requires verification: exact names of procedures and module keeper (object module, form module, or common module of the marking subsystem) — version-specific for 3.0.74.2 and clarified in the configurator.
5. Conducting and Movements
The document does not create movements in the registers (the field register_records is empty). It serves for data exchange with the external CEDM system and does not directly affect accounting and warehouse records.
Therefore:
- Accounting entries (according to the standard chart of accounts of the RK: 1210, 1030, 1330, 3310, 3130, 6010, 7010, etc.) are not formed by this document.
- Tax calculations (VAT 16%, PIT, social tax, etc.) do not apply to the document — it is not a sales, receipt, or settlement document.
- The result of “conducting” — recording the status and registering the aggregate in CEDM; the accounting movement of goods is performed by other documents (receipt/sale/movement).
6. Related Objects and Input on the Basis
| Connection | Description |
|---|---|
| IS CEDM | External state system — receiver of data on aggregates and source of information on codes |
| Marking Codes | Individual codes of consumer units received earlier (marking, receipt from the supplier) |
| Documents of Goods Movement | Receipt/sale/movement of marked goods — form the accounting and movements that are not present in this document |
| Electronic Documents (ESF IS ESF, STS) | Formed as separate objects during sale/movement; aggregation ensures the correct composition of packages for subsequent STS/ESF |
Input on the Basis. Typical scenario — copying a previously created document (evidence 3.5) for repackaging similar goods. Direct mechanisms for “input on the basis” from other objects for this document are not declared.
7. Extension Points
- Scanning/TSD Handlers — enhancement of code reception and validation (custom formats, additional checks).
- CSV Import — extension of the parser for non-standard file formats from suppliers.
- Exchange Rules with CEDM — changing the composition of the package, processing receipts, logging in “Typical Errors”.
- HandlingCheckFilling — additional business rules for controlling the composition of the aggregate.
- Configuration Extensions (CfE) — adding attributes/commands without removing from support; subscriptions to document recording events.
- Status Model — extending the list of exchange statuses for internal warehouse regulations.