--- title: "Directory \"Data Exchange Sessions\" — Technical Description" country: KZ lang: en author: Сапа Т.И. (https://buhgpt.kz/authors/sapa-ti) date: 2026-09-07 canonical: https://buhgpt.kz/suraqtar/spravochnik-seansyobmenovdannymi-tehnicheskoe-opisanie-en source: BuhGPT --- # Directory "Data Exchange Sessions" — Technical Description > **TL;DR:** 1. Identification Parameter Value Object Type Catalog Name DataExchangeSessions Full Name Catalog.DataExchangeSessions ( Catalogs.DataExchangeSessions ) Alias — (not specified) Configuration Accounting for Kazakhstan, ed. 3.0 (version 3.0.74.2) Owner Subsystem Library of Stand --- 1. Identification Parameter Value Object Type Catalog Name DataExchangeSessions Full Name Catalog.DataExchangeSessions (Catalogs.DataExchangeSessions) Alias — (not specified) Configuration Accounting for Kazakhstan, ed. 3.0 (version 3.0.74.2) Owner Subsystem Library of Standard Subsystems (BSP), subsystem "Data Exchange" / "Data Synchronization" Element Type Service (automatically filled by exchange mechanisms) Hierarchy No Owner No Purpose. The catalog is designed for the registration and accounting of data synchronization sessions between 1C information bases (nodes of exchange plans). Each element is a log of a data exchange session with a specific node: it records the start and end times, direction (sending/receiving), and performance indicators. The object is used by administrators and technical support specialists to monitor the operation of distributed information bases, diagnose synchronization problems, and analyze performance. It is automatically filled by exchange software and generally does not require manual input. Where to find in 1C. Navigation link: e1cib/list/Catalog.DataExchangeSessions. Access in the interface is usually through the administration/data synchronization monitoring sections (subsystem "Standard Subsystems" → service exchange mechanisms). This is a technical (service) object of BSP. It does not participate in accounting and tax accounting: it does not generate entries, movements in accounting registers, electronic invoices (ESF)/SNT, and is not related to VAT, PIT, social contributions, and other calculations. Rates and norms of the RK do not apply to it. 2. Attributes and Table Parts 2.1. Header Attributes Name Type Mandatory Purpose InformationBaseNode ExchangePlanReference Optional Reference to the exchange plan node with which the synchronization session was performed. Identifies the remote or local information base — participant in the exchange. Start Date (DateTime) Optional Date and time of the session start. Used for chronological analysis and calculation of exchange duration. End Date (DateTime) Optional Date and time of the session completion. Together with Start determines the duration of the exchange. Sending Boolean Optional Indicator that data was sent to the node during the session. Can be set simultaneously with Receiving (two-way exchange). Receiving Boolean Optional Indicator that data was received from the node during the session. Can be set simultaneously with Sending. ExecutionTime Number Optional Execution time of the session in seconds (difference End − Start). Numeric format — for convenience of performance analysis. PerformanceMeasurements ValueStorage Optional Serialized detailed performance measurements of the exchange stages. Decoded in a specialized form. Standard attributes of the catalog: Code, Name, DeletionMark, Predefined (not used), Reference. 2.2. Table Parts Table parts are absent. 3. Forms Form Purpose ListForm List of all registered exchange sessions. Key form for viewing exchange history, filtering by node, direction, date range, and assessing duration. ElementForm View/edit a single session. Contains a command for detailed viewing of performance measurements (decoding of the PerformanceMeasurements attribute). Other forms (selection, groups) are not separately defined — they use auto-generated forms by the platform. 4. Key Module Procedures The attached evidence does not provide the program code (BSL) of the modules. Below is a typical set of handlers for a service catalog of this type; actual implementations should be viewed in the configurator. Module of the form ElementForm: - OnOpen / OnCreateOnServer — preparation of session field display; calculation/output of duration based on Start and End. - Command of the type ShowPerformanceMeasurements (button handler) — deserialization of PerformanceMeasurements from ValueStorage and output of details by exchange stages in a separate form/table. Module of the form ListForm: - OnCreateOnServer — setting up conditional formatting and selections of the list (by node, direction, dates). Module of the object: - Generally empty or contains only service logic for recording. Filling of attributes is performed programmatically by the data exchange subsystem of BSP (when the synchronization session is completed, a catalog element is created and metrics are recorded). Requires verification in the specific build 3.0.74.2: the exact composition of form commands and the presence of user code in the object module — depends on the version of BSP. 5. Posting and Movements The catalog is not a document: it has no posting properties, and it does not generate movements in accumulation/accounting registers. Accordingly: - entries according to the typical chart of accounts of the RK (for example, 1210, 1030, 1330, 3310, 3130, 6010, 7010) are not created; - VAT (rate 16% for RK from 2026), PIT, social contributions (10%), social contributions for the pension fund (3.5%), social health insurance (2%), mandatory social health insurance (3%), social tax (5%) are not calculated and have no relation to the object; - electronic documents (ESF in the ESF IS, SNT) based on the catalog are not issued. The only "result of work" of the object is the record of a catalog element with metrics of the exchange session. The object does not store or post any tax or accounting values. 6. Related Objects and Input Based On - Exchange Plans — through the attribute InformationBaseNode, the object refers to the nodes of the exchange plan(s) of the configuration. This is the main connection. - BSP "Data Exchange" Subsystem — programmatically creates and fills catalog elements upon completion of synchronization sessions; uses data for monitoring and diagnostics. - BSP Synchronization Registers/Services (exchange logs, statistics) — consumers/adjacent mechanisms displaying information about sessions. Input based on: not provided either as a source or as a receiver (the object is service, created automatically). 7. Extension Points - Configuration Extension. Adding attributes (for example, additional metrics, error code, volume of transmitted data) and columns in ListForm for extended analytics of exchanges. - Form Handlers. Redefining/complementing handlers of ListForm/ElementForm through extension — additional selections, conditional formatting, exporting exchange history to external monitoring. - Programmatic Use. Reading the catalog with custom handlers for building reports on the duration and performance of synchronizations (using ExecutionTime and deserialization of PerformanceMeasurements). - Limitations. Since filling is performed by BSP mechanisms, manual modification of elements is not recommended — improvements are better built "on top" (reading), without interfering with the logic of recording sessions. Requires verification: the specific API of the BSP data exchange subsystem that records elements is version-dependent — when making improvements, check the composition of common exchange modules in build 3.0.74.2. --- _BuhGPT — ИИ-помощник для бухгалтеров Казахстана: https://buhgpt.kz_