Report "Data Area Update Progress" - Technical Description (BK 3.0.74.2)

1. Identification

Purpose. A service report for monitoring deferred (background) updates of data areas in the information base operating in data separation mode (service model, SaaS). It shows the status and progress of data processing by sections (areas) when transitioning the configuration to a new version.

Intended for service administrators and technical support specialists. Used episodically — during version update periods when it is necessary to track which data areas have been updated, which are in the queue, and which have completed with errors. Formed programmatically through the data composition system (DCS) based on information from the information base update subsystem.

This is a technical infrastructure report, not related to the enterprise's accounting data. It does not reflect economic operations, taxes, or calculations with counterparties, therefore the accounts of the Kazakhstan chart of accounts, VAT/individual income tax/social tax rates, etc., are not applicable (see section 5).

2. Attributes, Table Parts, and Forms

2.1 Header Attributes

The object does not contain its own attributes. All output data is dynamically generated during composition from external sources (registers and data from the information base update subsystem / queues of deferred handlers).

2.2 Table Parts

None. The result rows (list of areas and their statuses) are formed by data sets of DCS, not by stored table parts of the object.

2.3 Forms

No own forms are defined in the metadata. An auto-generated report form of the platform with a built-in data composition form is used. The user works with the standard settings panel and the result field of DCS.

The typical composition of output columns of the result (formed by the DCS schema):

3. Forms (List)

The object does not have separate forms. Interaction occurs through:

• Report Form (auto-generated) — launch, setting the period/filter by area, output of DCS result;
• if necessary — report variant form / composition settings of the platform.

4. Key Module Procedures

The text of the modules (BSL) is not attached in the reference evidence, so below are typical report handlers in DCS for this type of object (report object module and form module). Specific lines are indicated when there is a module export.

Report Object Module (ObjectModule):

• OnResultComposition(DocResult, DataDecoding, StandardProcessing) — intercepting composition: programmatic filling of the result with data from the update areas queue (when data cannot be obtained by a clean DCS query), setting StandardProcessing = False and manual output through the composition processor.
• SettingsForTechnicalSupport() / OnDeterminingReportSettings() — registering the report in the "Report Variants"/"Report Management" subsystem of BSP, marking it as "service/technical", restricting availability by administrator role.

Report Form Module:

• OnCreateOnServer(Error, StandardProcessing) — initialization, checking service administrator rights and data separation mode; when operating outside separation — message about inapplicability.
• OnOpen() / RefreshReport() — primary or manual formation.
• Handlers for update/filter commands by specific data area.

Requires verification on a specific version: the exact composition of software methods of the update subsystem, from which progress is read (names change between BSP releases).

5. Posting and Movements

The report is not posted and does not generate movements. Objects of the type "Report" in 1C do not participate in posting, do not create records in accumulation/information/accounting registers and do not generate accounting entries.

As a result, this object does not relate to elements of the RK accounting model:

• chart of accounts (1210, 1030, 1330, 3310, 3130, 6010, 7010);
• VAT rate 16 % and VAT register / ESF issuance, CIT;
• calculations for individual income tax (10 % up to 8,500 MCI annual income, 15 % above; basic deduction 30 MCI/month, no more than 360 MCI/year), social tax 10 % (base ceiling 50 MZP), social tax rate 3.5 %, VOSMS 2 %, OSMS 3 %, CO 5 %, social tax 6 %;
• constants for 2026: MCI 4,325 ₸, MZP 85,000 ₸, currency — tenge (₸).

These indicators are provided only to note: the report is infrastructure-related and is not influenced by them. The data source of the report is service information from the information base update subsystem (queue of deferred handlers, status of data areas), not accounting registers.

6. Related Objects and Input Based On

• Input based on — not supported (not applicable for reports).
• Related subsystems/mechanisms: subsystem "Information Base Version Update" (UpdateInformationBase), "Operation in Service Model" / "Data Separation" of BSP, queue of deferred update handlers, information registers of the update subsystem from which progress is read.
• Logically related to other service administration reports (task monitoring, status of areas).

7. Extension Points

• Configuration Extension: borrowing the report object/form module, intercepting OnResultComposition to add custom columns or filters by areas; adding form attributes through extension.
• DCS: additional report variants (user settings, groupings, selections by status/version) through the "Report Variants" subsystem.
• Rights: managing availability through roles (only service administrator) and functional options.
• Programmatic Call: generating results in the background/schedule using DataCompositionSettingsComposer + DataCompositionProcessor for automatic monitoring of update progress.

Requires verification: the presence and names of procedures in the update subsystem called during composition — version-dependent; before modification, check with the object module in the specific build 3.0.74.2.