Processing "UploadDownloadDataLinkMappingManager" (UT for Kazakhstan 3.4.5.21)

1. Identification

Purpose. A service data processor of the data export/import mechanism from the SSL library. It is responsible for reference mapping when loading data from a previously generated export: it matches source objects with destination objects by natural keys, identifies unmapped references, and provides the user with an interface for manually resolving conflicts. This is a technical data exchange/transfer data processor — it is not an accounting document, is not reflected in statutory accounting, and does not calculate taxes.

Typical usage scenarios in the KZ configuration: transferring master data and balances between databases (e.g., when deploying a new database, migrating to a new edition, or consolidating), where it is necessary to correctly "link" the counterparty catalog, items, VAT rates (in KZ, from 2026 — 16%), items and accounts of the source and destination KZ chart of accounts to avoid creating duplicates.

2. Attributes and Tabular Sections

The data processor is form-oriented: its data is mainly stored not in object attributes, but in a value table / tree placed on the form and in temporary storage. Typical composition of mapping data:

Attributes (mapping session parameters):

Tabular section / mapping table (ТаблицаСопоставления):

3. Forms

If the set of forms differs in a specific build of 3.4.5.21, this should be verified in the Configurator (version-dependent).

4. Key Module Procedures

No BSL code evidence was provided, so below are typical handlers of this type of object from the SSL "Data export and import" subsystem:

• ВыполнитьАвтоматическоеСопоставление() (object/form module) — iterates over unmapped references and searches for matches in the destination by natural keys (predefined names, GUID, significant attributes).
• НайтиСсылкуПоПолямПоиска(ПоляПоиска) — queries the destination database and returns the found reference or Undefined.
• ЗаполнитьТаблицуСопоставления() — reads data from the export/temporary storage and generates a table for display on the form.
• СохранитьРезультатыСопоставления() — saves the mapped pairs for subsequent data loading.
• ПриОткрытии() / ПриСозданииНаСервере() (form module) — initialization: retrieving loading session parameters, filling the table, counting unmapped items.
• Form command handlers: "Map automatically", "Map"/"Specify match", "Create new", "Write and close".

The exact names and line numbers of the procedures should be confirmed against the object/form module in the Configurator of a specific build.

5. Posting and Movements

The data processor is not posted and does not generate register movements — it is not a document. It has no ОбработкаПроведения procedure, does not create records in accumulation/information/accounting registers, and does not generate accounting entries.

The result of its work is a reference mapping table, which is passed to the data loading mechanism. The data loading itself writes objects (catalogs, documents, record sets) directly to the destination database, substituting the mapped references. All accounting consequences (movements, entries) are determined by the loaded objects, not by this data processor.

For context: correct mapping is important so that after loading, the KZ database retains correct links between objects and accounting entities — the KZ chart of accounts (1210 — short-term accounts receivable from customers, 1030 — cash in current accounts, 1330 — goods, 3310 — accounts payable to suppliers, 3130 — VAT payable, 6010 — revenue from sales, 7010 — cost of sales), VAT rates (16% from 2026), as well as parameters for calculating KZ taxes and contributions dependent on reference data: IIT 10% up to 8,500 MCI of annual income and 15% above, standard tax deduction of 30 MCI/month (no more than 360 MCI/year), MPC 10% (base cap of 50 minimum wages), MPCE 3.5%, VOSMI 2%, OSMI 3%, SC 5%, social tax 6%; MCI = 4,325 ₸, minimum wage = 85,000 ₸, currency — tenge (₸). An incorrectly mapped VAT rate or account will lead to distortion of these calculations in the destination database.

6. Related Objects and Entering Based On

• "Data export and import" data processor (ВыгрузкаЗагрузкаДанных) — the parent data processor of the subsystem; the mapping manager is called from the loading process.
• Common subsystem modules — ВыгрузкаЗагрузкаДанных, ВыгрузкаЗагрузкаДанныхСлужебный (server-side logic for reading exports and writing objects).
• Indirectly affects any catalogs, documents, information registers, and registers of the configuration whose references are involved in the transfer (Counterparties, Items, Organizations, Contracts, chart of accounts, etc.).

Entering based on is not supported for this data processor (data processors do not participate in the entering-based-on mechanism).

7. Extension Points

• Configuration Extension: borrowing the form/object module to override the automatic mapping algorithm or the set of search fields for KZ-specific needs (e.g., prioritizing counterparty search by BIN/IIN).
• Overridable SSL mechanisms: rules for determining natural keys and predefined items are set in the common modules of the "Data export and import" subsystem — logic should be adjusted through them rather than by modifying the service data processor.
• Additional data processors: for non-standard transfers, it is acceptable to implement a custom loading data processor using the subsystem API, leaving the standard mapping manager for interactive conflict resolution.

Requires verification (version-specific): the exact composition of forms, attributes, and procedure names in build 3.4.5.21 — should be checked in the Configurator, as the SSL library is updated between releases.