1. Identification
| Parameter | Value |
|---|---|
| Object type | Data Processor (DataProcessor) |
| Name | ВыгрузкаЗагрузкаДанныхМенеджерВыгрузкиДанныхИнформационнойБазы |
| Full path | DataProcessors.ВыгрузкаЗагрузкаДанныхМенеджерВыгрузкиДанныхИнформационнойБазы |
| Synonym | No separate synonym set; appears in EOM/metadata as "Export import data infobase export manager" |
| Configuration | Trade Management for Kazakhstan, edition 3.4 (version 3.4.5.21) |
| Owning subsystem | "Infobase Data Export and Import" of the Standard Subsystems Library (SSL) |
| Purpose | A service (programmatically invoked) data processor — a manager that generates an export of the infobase data into a portable format file (XML container) and performs the reverse import. Used when moving a database between platform/DBMS instances, migrating "file ↔ client-server", exporting to/from a service, and preparing data for technical support. |
Important note on object type. This is a data processor, not a document. It is not an element of operational or statutory accounting: it does not post, does not generate register entries or movements, and is not involved in calculating VAT, IIT, OPV, etc. Its purpose is the technical serialization/deserialization of existing infobase data while preserving referential integrity. All application-level values (for example, documents with a VAT rate of 16%, amounts in tenge ₸, counterparty catalogs) are transferred "as is", without recalculation.
2. Attributes and tabular sections
This type of data processor is implemented as an algorithm manager and does not have a user-facing "header" with application accounting attributes. Service data is passed via form/procedure parameters and export settings structures. Typical set of data elements:
Service attributes (form attributes / call parameters):
| Attribute | Type | Purpose |
|---|---|---|
ИмяФайла / АдресФайла |
String / storage | Path or temporary storage address of the export file (*.xml, data container). |
РежимРаботы |
String/Enum | Operation direction: export or import. |
ПараметрыВыгрузки |
Structure | Set of options: full database / selective composition, including users, including shared area data, etc. |
ТипФайла |
— | Container format (data area separator data / full infobase). |
ПропускатьОбъекты, СоставВыгрузки |
Map/Array | Rules for selecting and excluding metadata types from the export. |
Tabular sections: there are no application-level tabular sections (goods, services, payments). Lists of exported/imported metadata types and operation statistics are stored in internal structures and form tables rather than in tabular sections of the metadata object.
3. Forms
| Form | Purpose |
|---|---|
| Data export form | A wizard for selecting the export composition (entire infobase or selectively), the container file path, and starting the process; displays progress and result. |
| Data import form | Selecting the container file, checking configuration/version compatibility, warning about data replacement, and starting the import. |
| Settings/additional parameters form | Fine-tuning of data type selection, exclusions, handling of users and service data. |
In the standard delivery, the data processor is more often called programmatically from the SSL subsystem (administration command interface), so the specific set of forms is version-dependent. Requires verification in the specific 3.4.5.21 build — whether a separate client form exists versus purely programmatic usage.
4. Key module procedures
No direct BSL evidence for this object is attached (only the purpose facet is present in the evidence). Below is a typical set of handlers for the SSL data export/import manager; signatures and presence should be confirmed against the object module of the specific build.
ВыгрузитьДанные(...)/ВыгрузитьИнформационнуюБазу(...)— the main serialization procedure: traversal of the metadata composition, writing objects to the XML container while preserving references (GUID), generating a manifest of the configuration and platform version.ЗагрузитьДанные(...)/ЗагрузитьИнформационнуюБазу(...)— container deserialization: compatibility check, restoration of objects and referential integrity, replacement of existing data.ПроверитьВозможностьВыгрузки/Загрузки(...)— validation: configuration name and version match, operating mode (file-based/client-server), data separation.СформироватьСоставВыгрузки(...)— building the list of metadata types to export, taking into account selections and exclusions.ОбработатьПрогресс(...)/ long-running operation handlers — progress indication, operation in a background job.- Export methods of the manager called from common modules of the subsystem ("ExportImportData" and related), — integration points with the administration command interface.
Requires verification: the exact names of the export procedures and the
Module:Linepath — against the specific object module in 3.4.5.21.
5. Posting and movements
The data processor does not generate accounting entries and does not create register movements — data processors have no posting mechanism at all.
Context for the implementer (standard KZ chart of accounts; data is transferred via export/import without change):
- Accounting entries included in the container as register/document data retain their original amounts and accounts: 1210 (short-term accounts receivable from customers), 1030 (cash in current accounts), 1330 (goods), 3310 (accounts payable to suppliers), 3130 (VAT payable), 6010 (income from sales), 7010 (cost of sales).
- The 16% VAT rate (KZ 2026 norm), amounts in tenge (₸), as well as previously calculated IIT, OPV (10%), OPVR (3.5%), VOSMS (2%), OSMS (3%), SO (5%), and social tax (6%) figures are transferred as ready-made values. The data processor does not recalculate them and does not affect the relevance of the norms (MCI 4,325 ₸, 30 MCI deduction, etc.).
- Electronic document data (ESF from the ESF IS, SNT) is exported/imported together with the application objects, but the status of exchange with external systems is determined by the corresponding subsystems, not by this data processor.
6. Related objects and entry based on
- Entry based on — not applicable (service data processor).
- Related SSL subsystem objects: common modules of the "Infobase Data Export and Import" subsystem, the long-running operations/background jobs mechanism, the administration subsystem (infobase management, updates, exchange with the service).
- Related data transfer mechanisms: export/import via
*.dt(by platform means), exchange plans, data conversion — used for other migration scenarios and do not replace this data processor. - Interacts with system data separation mechanisms (when operating in a service model) to export data of a specific area.
7. Extension points
- Configuration Extension: overriding/extending the manager's export procedures via the
&Instead,&Before,&Afterannotations; adding data type selection rules. - Programmatic embedding: calling export methods from custom administration data processors and scheduled jobs (e.g., planned technical export).
- Composition selections: configuring excluded/included metadata types via export parameters without modifying the data processor itself.
- SSL update: when the library version is updated, the behavior and set of methods may change — it is preferable to place customizations in an extension rather than in the main configuration.
Where to find
1C navigation link:
e1cib/list/Обработка.ВыгрузкаЗагрузкаДанныхМенеджерВыгрузкиДанныхИнформационнойБазы
As a rule, access is via the administration section (maintenance / data export and import) rather than directly from the application interface.