Verified on release 3.4.5.21 "Trade Management for Kazakhstan" (edition 3.4).
An honest warning before you start. This is not a document and not a report. This is an internal service object of the platform. It has no postings, no e-invoices/e-waybills, no printed forms, and no familiar form with fields like "Counterparty/Amount/VAT." If you were looking for instructions on how to record a sale, an IIT deduction, or 16% VAT — you need a different object, not this one. Below is an honest breakdown of what
DataExportImportInfoBaseDataReadingStreamactually does, so you don't waste an hour "filling in" something that doesn't need to be filled in.
The real situation
You're transferring your "Trade Management for Kazakhstan" database from a file-based version to a server, or handing off an export to the 1cloud/1C:Fresh cloud, or preparing a data archive for tech support. You open the "Data Export and Import" processing, run an import — and suddenly an unfamiliar name flashes in the list of processings (or in an error message, or during debugging): InfoBaseDataReadingStream. You look up "how to fill it in." The answer: it doesn't need to be filled in by hand, and shouldn't be — it's a cog inside the data transfer mechanism. Understanding what it does is useful; "filling it out" is not required.
1) Purpose
DataExportImportInfoBaseDataReadingStream is a service processing from the "Data Export and Import" subsystem (a standard library subsystem, BSP). It is responsible for reading a stream of serialized data during import of a previously made export: it sequentially reads the XML content of the container (objects, references, register record sets) and passes them to the mechanism that writes to the database. It works in tandem with the stream-writing processing (used during export).
Simply put: when you click "Import data," this is the component that "unwraps" the export file and feeds the data in. It has no user scenarios of its own.
2) Where to find it
There is no direct user path to the reading stream itself — it's an internal object. But you can open its (empty, service) form or reach the mechanism that uses it as follows:
- The mechanism that calls it:
Master Data and Administration→Service→ "Data Export and Import" (in some installations —Administration→Support→Data Export and Import). - Opening the service processing directly in 1C — "Main menu" → "File" → "Open" doesn't work here (the processing is built into the configuration). Use a navigation link: Service → "Go to navigation link" and paste:
e1cib/list/Обработка.ВыгрузкаЗагрузкаДанныхПотокЧтенияДанныхИнформационнойБазы
This takes you to the object's service form. This is only useful for diagnostics — an ordinary user has no reason to go there.
2a) How to check your release
Help → "About the program". In the window that opens:
- Platform version (e.g., 8.3.24.xxxx) — at the top;
- Configuration: "Trade Management for Kazakhstan, edition 3.4" and the release (yours is 3.4.5.21).
Always check the release: the location of the "Data Export and Import" item and the set of export options change between releases.
3) How to "fill it in"
The reading stream processing itself has no fields for manual entry. All parameters are set in the form of the parent "Data Export and Import" mechanism, and the reading stream reads what is specified there. Key parameters of the import mechanism worth paying attention to:
| Parameter (in the import form) | Purpose and what happens if it's wrong |
|---|---|
| Export file (.zip archive / folder) — required | The data source for reading. If you specify the wrong or a corrupted file, the import will abort with a stream reading error, and the database won't change. |
| Configuration compatibility | Import is only possible into the same configuration and a compatible release. Trying to import into a different configuration → rejected before data reading even starts. |
| Mode: full / selective import | Determines whether the entire container is read. Wrong mode → some data won't be picked up. |
| Import into an empty / existing database | Importing into an existing database on top of data risks duplication/overwriting. Always import into a clean database or a copy. |
The only thing actually required of you is to make a backup before importing and ensure exclusive mode is available (no other sessions in the database).
4) Worked example
There can't be full-fledged accounting entries here — the object doesn't generate any. So let's look at a real transfer scenario where this stream is involved.
Task. Transfer a working Trade Management for Kazakhstan 3.4.5.21 database from a file-based version to a 1C:Enterprise server.
- In the source database:
Master Data and Administration→ "Data Export and Import" → Export data → you get a filedata_dump.zip(containing an XML container with all catalogs, documents, and registers). - On the server, create an empty database from the same "Trade Management for Kazakhstan 3.4.5.21" template.
- In the new database: "Data Export and Import" → Import data → specify
data_dump.zip. - During step 3, the platform launches
InfoBaseDataReadingStream: it opens the container, sequentially reads the serialized objects and record sets, and passes them for writing.
The "entries" of this process are not debits/credits, but a one-to-one data transfer. For clarity:
| What is read from the stream | Where it lands in the new database |
|---|---|
| Items of the "Items" catalog | "Items" catalog (same codes/GUIDs) |
| "Sales of Goods and Services" documents | Sales document journal |
| Record sets of the "Goods in Warehouses" register | "Goods in Warehouses" accumulation register |
| Settings, permissions, information registers | Corresponding database objects |
After import, all your amounts, the 16% VAT rate, counterparty catalogs, and balances on the standard Kazakhstani chart of accounts (1210, 1030, 1330, 3310, 3130, 6010, 7010) are transferred exactly as they were in the source database. The reading stream doesn't recalculate or tax anything — it copies.
5) Operation types
The processing has no "operation types" in the accounting sense. By role in the mechanism, two stream operation modes are distinguished:
- Reading (import) — this is what the object under review does: it reads the container during restore/transfer.
- Writing (export) — the opposite operation, performed by the paired stream-writing object.
6) What is generated when posted
The processing is not posted and does not generate:
- accounting debit/credit entries;
- electronic e-invoices (ESF) and e-waybills (SNT);
- movements in VAT, mutual settlements, or cost-of-goods registers.
The result of its work is objects and register record sets written into the target database, exactly as they were in the export file. No new business transaction is created: the data is simply restored as-is.
7) Printed forms
None. The service object has no printed forms. The only "reporting" artifact of the mechanism is the import log/protocol (messages about success or reading errors), which the platform outputs as service messages after the import.
8) Common errors
| 1C message | Cause and how to fix |
|---|---|
| "Data import is not possible: the configuration of the export file does not match the configuration of the infobase" | You're trying to import into a different configuration/incompatible release. Only import into "Trade Management for Kazakhstan" of the same release (3.4.5.21). |
| "Data stream reading error" / "Invalid container format" | The .zip file is corrupted or was downloaded incompletely. Re-export from the source database and try again. |
| "Failed to establish exclusive mode" | Other sessions are active in the target database. End all connections (Administration → "Active users") and try again. |
| "Insufficient rights to import data" | The import is being performed by a user without full/administrative rights. Log in as an administrator. |
| Aborted due to insufficient disk space / memory | A large container on a file-based version. Free up disk space; for large volumes, move to a server DBMS. |
9) FAQ
1. Do I even need to open this processing? No. It's called automatically from "Data Export and Import." It's not run separately.
2. Where are its postings, and how do I view them? It has none. This is a technical data transfer object, not a document. Postings are generated by documents (sales, receipts, etc.), not by the reading stream.
3. Does it generate e-invoices or e-waybills? No. It has nothing to do with electronic invoices or accompanying waybills.
4. Will the import change my amounts or VAT rate? No. Data is transferred one-to-one. If the database had a 16% VAT rate and balances on accounts 1210/1030/3310 — they will be imported without recalculation.
5. Can it transfer only part of the data, for example only documents for 2026? The reading stream itself reads whatever is in the container. Filtering is set at export time. For a selective transfer, use the export settings, not by editing the stream.
6. Is it safe to import into a working database on top of existing data? Risky — duplication and overwriting are possible. Import into a clean database or a copy, after making a backup.
7. Is this mechanism suitable for exchange with an accounting database (synchronization)? No. This is a full dump for transfer/restore, not regular synchronization. For data exchange, use synchronization settings, not export/import.
8. The import failed halfway through — is the database corrupted? Consider the target database untrustworthy: delete it and repeat the import into a new empty database from a verified file. The source database is not affected.
9. Can I open the object's form via a navigation link and enter something there?
You can open the form (e1cib/list/Обработка.ВыгрузкаЗагрузкаДанныхПотокЧтенияДанныхИнформационнойБазы), but there's nothing to enter there — no fields for input.
10. Between which configurations does the transfer work? Only between identical ones: the same configuration and a compatible release. Trade Management for Kazakhstan 3.4 ↔ Trade Management for Kazakhstan 3.4.
10) Related documents and objects
- What it's "entered" on the basis of: nothing — it's not a document. It's launched from the "Data Export and Import" processing during import.
- Paired object: the infobase data writing stream (used during export).
- What it affects during operation: virtually all configuration objects — catalogs (Items, Counterparties, Organizations), documents (sales, receipts, payments), accumulation and information registers — since it transfers the entire database.
- Alternatives for other tasks: for regular exchange — data synchronization settings; for targeted transfer of catalogs — universal exchange in the EnterpriseData format.
How to check your release
Help → "About the program" → the "Configuration" line will show "Trade Management for Kazakhstan, edition 3.4" and the release number, and above it — the 1C:Enterprise platform version. If your release differs from the one specified, the location of the "Data Export and Import" item may differ slightly.
This guide was prepared for release 3.4.5.21 "Trade Management for Kazakhstan" (edition 3.4). When updating the configuration, verify the details in "Help → About the program."