--- title: "Report \"Analysis of Object Versions\" - Technical Description (Accounting for Kazakhstan 3.0.74.2)" country: KZ lang: en author: Сапа Т.И. (https://buhgpt.kz/authors/sapa-ti) date: 2026-09-07 canonical: https://buhgpt.kz/suraqtar/otchet-analizversiyobektov-tehnicheskoe-opisanie-buhgalte-en source: BuhGPT --- # Report "Analysis of Object Versions" - Technical Description (Accounting for Kazakhstan 3.0.74.2) > **TL;DR:** 1. Identification Parameter Value Object Type Report Name ObjectVersionAnalysis Full Name Report.ObjectVersionAnalysis Alias — (not specified in the provided metadata) Configuration Accounting for Kazakhstan, edition 3.0.74.2 Subsystem Standard subsystems → "Object Versioning" --- 1. Identification Parameter Value Object Type Report Name ObjectVersionAnalysis Full Name Report.ObjectVersionAnalysis Alias — (not specified in the provided metadata) Configuration Accounting for Kazakhstan, edition 3.0.74.2 Subsystem Standard subsystems → "Object Versioning" mechanism (BSP) Where to find Navigation link: e1cib/list/Report.ObjectVersionAnalysis. In the interface — section "Administration" (service functions for working with object versions). Purpose. The report is intended for analyzing the history of changes to objects in the information base (documents, directories, registers, and other objects for which versioning is enabled). It allows comparing versions of the same object recorded at different times, identifying discrepancies between versions, tracking who made changes and when, and restoring the previous state of the object. The tool is classified as service/administrative rather than accounting. It does not participate in accounting and tax accounting, does not generate journal entries, and does not affect the calculation of VAT, PIT, pension contributions, social tax, and other indicators. Typical use cases include: incident investigation (who changed the amount or counterparty in the document), data auditing, control of the correctness of mass processing, rollback of erroneous changes. 2. Header Attributes and Table Parts According to the provided metadata, the report does not have its own header attributes and does not have table parts — this is a standard situation for a service report operating on top of the versioning subsystem. - 2.1 Header Attributes — absent. - 2.2 Table Parts — absent. - 2.3 Selection Parameters are formed dynamically on the form/in the composition scheme and usually include: - object (link) whose versions are being analyzed; - period (date range of version creation); - author of changes (user); - type of comparison (two selected versions or the entire chain of versions). The data source for the report is the object version storage, populated by the information register of the versioning subsystem BSP (InformationRegister.ObjectVersions), not the report's own attributes. 3. Forms The report's metadata does not define its own forms. This means that the automatically generated report form by the platform is used (default form). Functionally, the following are utilized: - Report Form (main, auto-generated) — input of selection parameters (object, period, author), initiation of generation, and output of the comparison result of versions. - Service Forms of the BSP Versioning Mechanism — list/comparison form of versions of a specific object, called from the object card with the "Change History" command. The report uses the common module for version comparison from BSP. 4. Key Module Procedures Evidence with specific paths and line numbers of modules is not attached, so below is a typical set of handlers for a report of this type (report object module / report form module in BSP): - OnCompositionResult(ReportDocumentResult, DataBreakdown, StandardProcessing) — data composition scheme handler: prepares a selection of versions based on specified parameters, disables standard processing if necessary, and manually generates the result (comparison of version fields). - OnCreationOnServer(Error, StandardProcessing) (form module) — form initialization, substitution of default selection parameters. - Calls to the common BSP module ObjectVersioning / ObjectVersioningService — obtaining a list of object versions, deserialization of a version, pairwise comparison of attributes and table parts, generating a discrepancy table. - Functions for comparing versions that return a structure of differences (attribute, "was" value, "became" value, author, date). Requires verification in the specific build 3.0.74.2: the exact set and signatures of module procedures, as the report implementation relies on the BSP version supplied with the release. 5. Posting and Movements The report is not posted and does not generate movements in any accumulation registers, accounting registers, or information registers. As an object of type "Report," it does not have a posting procedure, does not create accounting entries, and does not affect the chart of accounts of the RK (including accounts 1210, 1030, 1330, 3310, 3130, 6010, 7010) and tax registers. The data for the report output is read from the information register of the versioning subsystem (InformationRegister.ObjectVersions BSP), where serialized versions of objects are stored. The version recording is performed by the versioning mechanism itself when recording/posting application objects, not by this report. 6. Related Objects and Input Based On - Input Based On — not supported (not typical for reports). - Related Objects of the BSP Versioning Subsystem: - InformationRegister.ObjectVersions — version storage (data source for the report); - common modules ObjectVersioning, ObjectVersioningService, ObjectVersioningClientServer; - information register with versioning settings by object types (which objects and how are versioned). - Analyzed Objects — any documents, directories, and other objects of the "Accounting for Kazakhstan" configuration for which versioning is enabled in the settings (for example, payment and commodity documents affecting ESF/SNT and VAT calculations of 16%). 7. Extension Points - Configuration Extensions — adding attributes/fields to the auto-generated report form through an extension, embedding a custom command in the forms of application objects. - BSP Versioning Settings — defining the list of versioned objects, version retention period, version recording mode (upon recording/upon posting). This affects the completeness of the report data. - Data Composition Scheme — when refining, it is possible to expand the set of output comparison fields, add groupings by author/date/object type. - BSP Programming Events — overridable procedures of the module ObjectVersioningOverridable for managing the composition of versioned attributes and comparison rules. Requires verification: the exact composition of overridable procedures and versioning settings depends on the BSP version in release 3.0.74.2. --- _BuhGPT — ИИ-помощник для бухгалтеров Казахстана: https://buhgpt.kz_