Processing "UploadProductDatabaseToTSD" (Uploading the product database to TSD)

1. Identification

Purpose. A service (non-posting) data processor for preparing and exporting reference product information to a data collection terminal (DCT) — a mobile barcode scanner. It generates a selection of items with key attributes (SKU, barcode, unit of measure, price, stock balance) and transfers it to the device or to an intermediate exchange file, so that the warehouse keeper/operator at the DCT can identify products autonomously, without a permanent connection to the database. The processor does not handle reverse data loading (receiving, inventory count, order picking) — these are separate DCT interaction mechanisms.

The data processor is a service object: it is not an accounting document, does not participate in posting, and does not create register records or accounting entries (see section 5).

2. Attributes and Tabular Sections

The data processor does not store data in the database; its attributes are form parameters (data processor/form attributes) that define the selection and export conditions. The exact composition and names of attributes are version-dependent (requires verification in the specific build 3.4.5.21); below is a typical set for this kind of data processor.

"Header" attributes (export parameters)

Tabular section Товары (form attribute of type ValueTable)

Populated by the generation command and serves as a preview of the exported dataset.

3. Forms

A service data processor of this kind typically has a single main form; additional settings and item selection forms are usually not separated out (the exact list of forms requires verification in build 3.4.5.21).

4. Key Module Procedures

The BSL source code is not attached in the evidence, so below is a typical set of handlers for this kind of data processor (names are approximate).

Form module:

• ПриСозданииНаСервере — initialization: default substitution of organization/warehouse/price type, reading the saved exchange directory path from settings storage.
• ЗаполнитьТоварыНаСервере ("Fill" command) — builds the item selection via a query against the registers, populates the Товары table.
• Выгрузить (client) → ВыгрузитьНаСервере — generates the exchange file in the specified format and writes it to the directory/passes it to the DCT driver.
• ПроверитьЗаполнение — checks required parameters (warehouse, price type, export path) before export.
• Interactive file/directory selection handlers (НачалоВыбораФайлаВыгрузки).

Object module:

• ПолучитьДанныеДляВыгрузки(Отбор) — server function for collecting data via a query.
• СформироватьФайлВыгрузки(ТаблицаТоваров, Формат) — serialization into the target format.

The fill logic relies on a query against:

• the Products catalog and the Product Barcodes information register — identifiers and barcodes;
• the Product Prices information register — the price of the selected ВидЦен;
• the Products in Warehouses accumulation register (virtual table Остатки) — warehouse stock balances.

5. Posting and Register Movements

The data processor is not posted and does not generate register movements. As an object of type "Data Processor", ВыгрузкаБазыТоваровВТСД has no posting mechanism, does not create accumulation/information/accounting register records, and does not generate accounting entries. It works read-only: it selects data and exports it to an external file/device.

Accordingly, entries under the standard chart of accounts of Kazakhstan — sales, cost of goods sold, settlement, and VAT accounts (e.g., 1210, 1030, 1330, 3310, 3130, 6010, 7010) — are not applicable to this object; they are used by accounting documents (sale, receipt, inventory count), not by this data processor. The only "numeric" involvement of the data processor is the exported price in tenge (₸), which upon sale is subject to 16% VAT (the rate applicable in Kazakhstan for 2026); the VAT amount is typically not broken out in the export itself — the sales price is transmitted.

6. Related Objects and Input Based On

Read (data sources):

• The Номенклатура catalog, ХарактеристикиНоменклатуры, УпаковкиЕдиницыИзмерения.
• The ШтрихкодыНоменклатуры information register.
• The ЦеныНоменклатуры information register (for the selected ВидЦен).
• The ТоварыНаСкладах accumulation register (stock balances).
• The Организации, Склады, ВидыЦен catalogs — filter parameters.

Input based on. Not supported: the data processor is not a source object and is not part of "input based on" chains. It is not directly related to Kazakhstan's accounting and electronic documents (ESF in the ESF IS, SNT) — these documents are generated based on goods movement transactions, not on the fact of export to the DCT.

Related mechanisms. The reverse side of DCT exchange — loading the scanning results (for receiving, inventory count, order picking) — is implemented by separate data processors/documents in the configuration and is not covered here.

7. Extension Points

• Configuration extension. Borrowing the object/form module to override ПолучитьДанныеДляВыгрузки and СформироватьФайлВыгрузки — adding custom fields (grade, expiration date, country of origin, HS code for SNT) and supporting the format of a specific DCT model.
• Item selection. Extending the fill query (additional filter by item type, segment, "export to DCT" flag).
• Exchange format. Adding a new ФорматВыгрузки value and a serialization branch for a non-standard driver.
• Settings storage. Saving/restoring export parameters (warehouse, price type, path) for repeated sessions.
• Scheduled execution. Calling the server export function from a scheduled job for automatic periodic preparation of the DCT file.