1. Identification
| Parameter | Value |
|---|---|
| Object type | Data Processor (DataProcessor) |
| Name | ВыполнениеОбменаДанными |
| Full identifier | DataProcessors.ВыполнениеОбменаДанными / Обработка.ВыполнениеОбменаДанными |
| Synonym | "Perform Data Exchange" |
| Configuration | Trade Management for Kazakhstan, ed. 3.4.5.21 |
| Subsystem | Standard Subsystems → "Data Exchange" (SSL, ОбменДанными) |
| Where to find | Section "Standard Subsystems" → "Perform Data Exchange". Navigation link: e1cib/list/Обработка.ВыполнениеОбменаДанными |
Purpose. A service data processor of the "Data Exchange" subsystem of the Standard Subsystems Library (SSL). Provides interactive and background launch of a synchronization session for an exchange setting (exchange plan node): sending changes to a file/directory/FTP/service, receiving an incoming message, resolving conflicts and changes rejected due to the edit prohibition date, and outputting the log. This is the transport-execution layer of data synchronization — it is not an accounting document, does not store its own data, and does not generate accounting entries. Through configured conversion rules (CD 2.0/3.0), the data processor transfers and receives application accounting objects: items, counterparties, sales/receipt documents, as well as data for electronic documents of the Republic of Kazakhstan — ESF (ESF IS) and SNT.
2. Attributes and Tabular Sections
The data processor has no permanent storage and operates on form attributes (session parameters). Below is the typical set of data managed by the data processor during an exchange session.
Session parameters (form/module attributes):
| Attribute | Type | Purpose |
|---|---|---|
Узел / УзелИнформационнойБазы |
ExchangePlanRef | Synchronization setting (exchange plan node) for which the session is executed |
ИдентификаторНастройкиОбмена |
String | String identifier of the exchange setting variant (conversion rules) |
ВыполнятьВыгрузку / ВыполнятьЗагрузку |
Boolean | Session direction flags (send and/or receive) |
ИмяФайлаСообщения / Каталог |
String | Path to the exchange message file or directory for file-based transport |
ИнтерактивныйРежим |
Boolean | Flag indicating manual launch by user (as opposed to scheduled) |
ОтменятьЗагрузкуПоДатеЗапрета |
Boolean | Controls handling of objects affected by the edit prohibition date |
Tabular sections (generated during the session):
| Tabular section | Key fields | Purpose |
|---|---|---|
| Execution log | Date, ImportanceLevel, Text, Object | Line-by-line session log: information, warnings, errors |
| Rejected/conflicting objects | Object, ThisBaseVersion, OtherBaseVersion, RejectionReason | List of objects requiring manual conflict resolution |
| Statistics by data type | DataType, ObjectsSent, ObjectsReceived | Summary of the number of objects transferred/received for each type |
3. Forms
| Form | Purpose |
|---|---|
| Data processor form (main) | Launch an interactive synchronization session for the selected setting, choose direction and transport, display progress and results |
| Synchronization assistant form | Step-by-step wizard: analysis of data to be sent/received, preview, confirmation of sending/receiving |
| Log/results form | Detailed session log with filters by importance level, navigation to problem objects |
| Conflict and rejected object resolution form | Manual selection of object version, processing of objects under the edit prohibition date |
The exact set of forms is version-specific and determined by the SSL implementation in 3.4.5.21 — requires verification against the specific build.
4. Key Module Procedures
No separate BSL evidence is attached for this data processor (only the purpose facet is available). Below are the typical handlers and object methods of this type in the SSL "Data Exchange" subsystem; specific signatures are to be verified against the code of build 3.4.5.21.
| Procedure/Function | Location (typical) | What it does |
|---|---|---|
ВыполнитьОбменПоНастройкеОбмена |
Object module / common module ОбменДаннымиСервер |
Entry point: launches a synchronization session for a node — sending and/or receiving |
ВыполнитьВыгрузкуДанных |
Object module | Generates the exchange message: selects registered changes, applies conversion rules, writes XML |
ВыполнитьЗагрузкуДанных |
Object module | Reads the incoming message, applies receiving rules, resolves references, records conflicts |
ВыполнитьОбменВыделеннымиНастройками |
Form | Form command handler: sequential launch of sessions for the selected settings |
ВыполнитьОбменВФоне / ФоновоеЗаданиеЗавершено |
Form / common module | Launches a long session as a background job and handles its completion |
ЗарегистрироватьОшибкуВПротоколе |
Object module | Adds an error/warning entry to the execution log |
ОбработатьНепринятыеПоДатеЗапрета |
Object module | Processes objects rejected due to the data edit prohibition date |
5. Posting and Movements
The "Perform Data Exchange" data processor is not posted and does not generate its own register movements or accounting entries — it is a transport mechanism for synchronization, not an accounting document.
Accounting movements arise indirectly: documents received from the exchange message are recorded and (with appropriate configuration of the ПриЗагрузке conversion rules) posted by the standard logic of the documents themselves. For the Kazakhstan configuration, this includes in particular:
- Sales of goods → sales/cost-of-sales registers and entries of the Kazakhstan standard chart of accounts:
- Dr 1210 "Short-term receivables from customers" — Cr 6010 "Revenue from sales" for the revenue amount;
- Dr 6010 — Cr 3130 "VAT payable" for the VAT amount at the rate of 16% (Kazakhstan, 2026);
- Dr 7010 "Cost of sales" — Cr 1330 "Goods" for the cost amount.
- Receipt of goods → Dr 1330 — Cr 3310 "Short-term payables to suppliers"; input VAT — to 1420.
- Payment → movements on 1030 "Cash in current bank accounts".
Example of VAT on a sale of 1,000,000 ₸ (excluding VAT): VAT = 1,000,000 × 16% = 160,000 ₸, amount payable by customer 1,160,000 ₸ (Dr 1210 1,160,000 — Cr 6010 1,000,000, Cr 3130 160,000). All amounts are in tenge (₸).
Electronic documents ESF (ESF IS) and SNT, when exchanged with services, are also not posted by this data processor — it only transfers their data/statuses; the issuance and sending of ESF/SNT are performed by the configuration's dedicated mechanisms.
6. Related Objects and Entry Based On
- Exchange plans — nodes for which synchronization is performed (source of transport settings and data composition).
- Information register with data synchronization settings and transport parameters (directory/FTP/EDI/service).
- Data conversion rules (CD 2.0/3.0) — define which objects are sent/received and how.
- Change registration of exchange plans — the queue of objects to be sent.
- Scheduled job for data synchronization — automatic launch of sessions on a schedule.
- ESF/SNT services (Kazakhstan) — receivers/sources of electronic documents with the corresponding exchange setting.
Entry based on does not apply to this service data processor (the data processor does not participate in "entry based on" chains).
7. Extension Points
- Conversion rules (CD 2.0/3.0) — the main standard way to change the composition and logic of sending/receiving objects, including ESF/SNT and Kazakhstan specifics, without modifying the configuration.
- SSL programming interfaces (
ОбменДанныеПереопределяемый,ОбменДанныеСобытияПереопределяемый) — override synchronization behavior in overridable modules. - Configuration extension — adding handlers to the data processor forms (
&Insert/&After) and object module methods without removing from support. - Event subscriptions for writing/posting received documents — to fine-tune movements for Kazakhstan accounting policy.
- Data edit prohibition date — regulating the acceptance of historical periods during loading.
The exact names of overridable modules and the presence of specific extension points depend on the SSL version in build 3.4.5.21 — requires verification against the metadata of the specific configuration.