1. Identification
| Parameter | Value |
|---|---|
| Metadata object type | Report (Reports / "Report") |
| Name | DeferredUpdateDuration |
| Full name | Report.DeferredUpdateDuration |
| Synonym | Deferred update duration |
| Configuration | Accounting for Kazakhstan, ed. 3.0 (version 3.0.74.2) |
| Origin | Library of standard subsystems (BSP), subsystem "Version update of the information base" |
| Purpose | Service (technological) tool for analyzing the performance of deferred update handlers of the information base |
Purpose. The report is intended for administrators and technical support specialists. After transitioning to a new version of the configuration, a significant portion of data migration is performed deferred (in the background, with users active) — by a set of deferred update handlers. The report collects statistics on their execution: for each handler, it records the start time, end time, duration, status, number of processed data, and queue. The result is visualized as a Gantt chart (timeline), allowing one to see the parallelism/sequencing of execution, identify the longest handlers and "bottlenecks," assess the total time of background migration, and optimize the plan for subsequent updates.
This is purely a technological report. It does not relate to the accounting framework: it does not work with the chart of accounts, taxes, electronic invoices (ESF)/SNT, or monetary amounts. The specifics of Kazakhstan 2026 (VAT rate 16%, MRP 4,325 ₸, MZP 85,000 ₸, deduction for individual income tax 30 MRP/month, etc.) are not involved in this object — mentioning it here would be a mistake.
Where to find in 1C:
- Navigation link:
e1cib/list/Report.DeferredUpdateDuration - Through the interface: administration section / service menu of the "Version update of the information base" subsystem (usually available to users with administrator rights). In the standard delivery, the report is called from the deferred update progress/results form.
2. Header attributes and table parts
2.1 Header attributes
| Name | Type | Mandatory | Purpose |
|---|---|---|---|
| (no custom header attributes) | — | — | The report does not have defined user-defined header attributes. Parameterization is performed exclusively through the data composition scheme (DCS) and its parameters. |
2.2 Table parts
There are no table parts. The report does not store data in its own attributes — the result is formed programmatically during composition: the object module fills the external data set of the DCS with records about the execution of handlers (from the service data of the update subsystem, the register of information on the update progress, and the registration log).
2.3 Composition parameters (typical for this report)
Since there are no custom attributes, the actual configuration is provided by the DCS parameters. The typical set includes:
| Parameter | Purpose |
|---|---|
| Period / update date | Limits the selection to a specific session (launch) of the deferred update |
| Filter by status | Shows only completed / ongoing / completed with errors handlers |
| Filter by handler or subsystem | Localizes the analysis to a specific library/data area |
3. Forms
| Form | Availability | Purpose |
|---|---|---|
| Main report form | Autoform DCS | A specialized form in the metadata is not defined. Uses automatically generated report form based on the DCS mechanism: the user receives a standard settings panel (filters, period), a "Generate" button, and a table document field with the result (including the Gantt chart). |
There are no separate list, selection, or auxiliary forms for the report — the entire user interface is provided by the standard data composition mechanism.
4. Key module procedures
The attached evidence does not provide the original BSL code (object module / form module). Below is a typical set of handlers for reports of this type (DCS with programmatic data filling), characteristic of BSP implementation.
Report object module:
OnCompositionResult(DocumentResult, DataDecoding, StandardProcessing)— key procedure. SetsStandardProcessing = Falseand takes the result formation upon itself: retrieves service statistics on deferred update handlers, transforms it into an external data set, initializes the composition processor, and outputs the result (table and/or Gantt chart) toDocumentResult.- Service functions for data retrieval — accessing data from the "Version update of the information base" subsystem (information on handler execution: name, queue, status, start/end, duration, volume of processed data) and forming a value table for the external DCS set.
- Auxiliary procedures for configuring the Gantt chart (setting time intervals "start–end" for each handler row).
Form module (autoform): custom code is usually absent — standard handlers of the report autoform DCS are used (OnCreateOnServer, handling the "Generate" command).
Requires verification (version-specific): exact names of service functions and the data source on update progress may differ between BSP releases supplied in 3.0.74.2. Clarification is needed for the specific object module in the configurator.
5. Posting and movements
The report is not posted and does not generate movements. The report is not a document: it does not have a ProcessingPosting procedure, does not create accounting entries, and does not write to accumulation/accounting registers.
Therefore, for this object the following are not applicable:
- entries according to the chart of accounts of the RK (1210, 1030, 1330, 3310, 3130, 6010, 7010, etc.);
- calculations of taxes and contributions (VAT 16%, individual income tax, social tax, etc.);
- formation of electronic documents (ESF in the ESF IS, SNT).
The report operates in read-only mode: the source is the service data of the update subsystem (register(s) of information on the status of deferred handlers and records from the registration log). The report does not modify any data in the information base.
6. Related objects and input based on
- Input based on: not applicable (reports do not participate in the input based on mechanism).
- Related objects of the "Version update of the information base" subsystem (BSP):
- common update modules (information base update manager, deferred update handlers) — suppliers of analyzed data;
- register(s) of information storing the status and parameters of deferred handlers;
- form of progress/results of deferred updates, from which the report is usually called;
- registration log — source of time and messages for handlers.
- Application (accounting) objects of the configuration (implementation documents, invoices/ESF, accounting registers) are not related to the report — it does not depend on the application accounting model of the RK.
7. Extension points
- Configuration extension: custom filters/fields can be added to the DCS through borrowing the composition scheme, as well as overriding
OnCompositionResultto add custom analytics (e.g., grouping by subsystems or thresholds for "long" handlers). - DCS settings (without modifications): user-defined report options — additional filters, conditional formatting (highlighting handlers exceeding a specified duration), sorting by duration descending.
- BSP programming interfaces: data on the progress of deferred updates is available through the API of the "Version update of the information base" subsystem; if necessary, a custom service report/monitoring processing can be built based on them.
- Limitation: since the report is technological and is updated along with the BSP, customization is preferably conducted in an extension to avoid blocking the delivery when updating the configuration to subsequent releases.