1. Identification
| Parameter | Value |
|---|---|
| Object type | Data processor (DataProcessor) |
| Name | ВыгрузкаЗагрузкаДанныхПотокЧтенияДанныхИнформационнойБазы |
| Full name | Обработка.ВыгрузкаЗагрузкаДанныхПотокЧтенияДанныхИнформационнойБазы |
| Synonym | — (no separate synonym defined; descriptive name "Data export-import information base data reading stream") |
| Configuration | Trade Management for Kazakhstan, edition 3.4.5.21 |
| Owning subsystem | "Data Export and Import" (standard subsystem of the Standard Subsystems Library, SSL) |
| Purpose | Service (technological) data processor. Implements streaming (sequential) reading of information base objects when they are exported to a data file/archive. It is one of the "readers" (data providers) of the SSL export-import mechanism: it encapsulates retrieving a sample of objects from the IB in batches and passing them to the serializer without loading the entire array into memory at once. |
The data processor is not intended for interactive user work and is not an applied (accounting) object. It is called programmatically from common modules of the data export/import mechanism (data transfer between databases, technical IB export, consolidation/exchange). It has no user-facing functional meaning in terms of trade/tax accounting.
Where to find it
There is usually no direct navigation command in the interface (the object is a service one). To open the data processor form in "Enterprise" mode (with administrator rights), use the navigation link:
e1cib/list/Обработка.ВыгрузкаЗагрузкаДанныхПотокЧтенияДанныхИнформационнойБазы
In Configurator: branch Data Processors → ВыгрузкаЗагрузкаДанныхПотокЧтенияДанныхИнформационнойБазы.
2. Attributes and tabular sections
The data processor belongs to the class of technological "streaming readers", where business logic is stored not in form attributes but in module variables and method parameters. Typical composition:
Attributes (properties/variables of the object or form)
| Attribute | Type | Purpose |
|---|---|---|
ИмяФайлаДанных / ИмяФайлаАрхива |
String | Path to the source file (export archive) from which the stream is read. |
КаталогВыгрузки |
String | Working directory of the unpacked export data. |
ПараметрыВыгрузки / ПараметрыЗагрузки |
Structure | Current session settings (metadata set, modes, filters, format version). |
ТекущийОбъект / ТекущаяПорция |
Arbitrary | Pointer to the object/batch currently being read in the stream. |
КоличествоОбъектов |
Number | Counter of processed objects (for progress indication). |
Инициализирован |
Boolean | Flag indicating the stream is ready for reading. |
Tabular sections
There are no applied (persisted) tabular sections. For service data processors of this kind, data is stored in form attributes of type ValueTable/ValueTree only for the duration of the session (for example, the list of metadata types being read, the batch queue). The data processor has no permanent storage — it does not write data to the IB, only reads it and passes it to the calling code.
3. Forms
| Form | Purpose |
|---|---|
| Form (main, if defined) | Technological interface for launching/diagnosing streaming reading by the administrator. Not opened in typical usage — operation runs programmatically. |
| No forms (frequent case) | Many SSL streaming readers have no forms at all: the object is used exclusively as a container for program code (object module methods). |
"Requires verification" for version 3.4.5.21: the presence/composition of the main form is a version-dependent detail; in some releases the object has no forms at all.
4. Key module procedures
No direct BSL evidence for the module body is attached (the reference material contains only the "purpose" facet). Below is the typical composition of export methods of the data processor module for this type of object. This is a stable contract of an SSL "streaming reader"; check the specific signatures against the module of the release.
| Procedure/function | Purpose (typical logic) |
|---|---|
Инициализировать(Параметры) |
Prepares the stream: opens the data file/archive, parses the export header, reads meta-information, positions the cursor at the start of the stream. |
ПрочитатьИнформациюЗаголовка() / ПрочитатьЗаголовок() |
Returns service export data: format version, composition of exported types, completeness/filtering flags. |
ЕстьДанные() / СледующийЕсть() |
Checks for unread objects remaining in the stream (reading loop condition). |
ПрочитатьОбъект() / Прочитать() |
Reads and deserializes the next object (or batch) from the stream, returns it to the calling code. Advances the internal cursor. |
ПропуститьОбъект() |
Skips the current object without deserializing it (for filtering by types/conditions). |
Закрыть() / Завершить() |
Releases resources: closes file streams, clears temporary data. |
ПолучитьПрогресс() |
Returns the fraction read (for a long-running operation indicator). |
The form's own event handlers (if a form exists) are standard: ПриОткрытии, ПриСозданииНаСервере — they only handle UI initialization and contain no application logic.
5. Posting and movements
The data processor is not a document and does not perform posting. It has no tabular section of movements, and no accumulation/information registers or accounting entries are generated.
Accordingly, no Kazakhstan chart-of-accounts accounts or tax calculations apply to this object. For completeness, here are reference values for the Kazakhstan environment for 2026 relevant to applied (accounting) objects of the configuration — but not to this service data processor:
- VAT rate — 16%; VAT payable account — 3130.
- Standard Kazakhstan accounts: 1210 (short-term customer receivables), 1030 (cash on current accounts), 1330 (goods), 3310 (payables to suppliers), 6010 (revenue from sales), 7010 (cost of sales).
- Labor/tax reference values: MCI = 4,325 ₸, minimum wage = 85,000 ₸; basic PIT deduction — 30 MCI/month (no more than 360 MCI/year); PIT 10% up to 8,500 MCI of annual income and 15% above; mandatory pension contributions (OPV) 10% (base cap 50 minimum wages), employer pension contributions (OPVR) 3.5%, employer medical insurance contributions (VOSMS) 2%, medical insurance contributions (OSMS) 3%, social contributions (SO) 5%, social tax 6%.
Once again: the figures listed are provided as configuration context and are not involved in any way in the operation of this data processor — it only transfers IB data "as is", without recalculating amounts or changing accounting values.
6. Related objects and entering on basis
- Entering on basis — not supported and not applicable (the object does not create IB data).
- Related objects — programmatic consumers of the SSL export/import mechanism:
- common modules of the "Data Export and Import" subsystem (export manager, serializer, stream dispatcher);
- the paired stream "writer" (serializer data processor that generates the export file), for which this data processor acts as the reader during the reverse operation;
- maintenance/data transfer procedures that initiate a reading session.
- Kazakhstan electronic documents (ESF via the ESF IS, waybills) — when exporting/importing the IB, data of the corresponding objects is transferred as ordinary stream objects; this data processor has no special integration with the ESF IS.
7. Extension points
- Configuration extension — the preferred method: overriding/extending export methods of the data processor module (
ПрочитатьОбъект,Инициализировать, etc.) via the&Instead,&After,&Beforeannotations. Keep in mind that interfering with the service reading stream can break the integrity of the export — test on a full "export → import" cycle. - SSL programmatic interfaces — instead of modifying the object, hook into the handler procedures of the "Data Export and Import" subsystem (events before/after exporting objects, redefining the set of exported types) — this is the standard and safe mechanism for influencing the stream.
- Filtering types/objects — via session parameters (
ПараметрыВыгрузки/ПараметрыЗагрузки), without modifying the data processor's own code. - Not recommended: changing the serialization format or reading order — this breaks compatibility with the paired writer and with format versions of other releases.
"Requires verification" for 3.4.5.21: exact names and signatures of the module's export methods, as well as the presence of a main form — check against the module of the specific release, as these are version-specific details.