Report "Analysis of the Registration Journal" - Technical Description (Accounting for Kazakhstan 3.0.74.2)

1. Identification

Purpose. The report analyzes the technical activity of the 1C system based on the data from the registration log. It is intended for system administrators and technical specialists and is used periodically — during performance problem diagnostics, user action audits, and the configuration of scheduled operations. It generates several views:

• Gantt charts for visualizing simultaneous user sessions;
• User activity tables broken down by days / weeks / hours;
• Analysis of the duration of scheduled and background tasks;
• Monitoring errors and warnings recorded in the registration log.

Important limitation. The report is not available in the cloud version of 1C:Fresh when data separation is enabled (in the service model, the registration log of the data area is not fully accessible to the subscriber).

The report is service-technical in nature and is not related to accounting data (VAT, IIN, contributions, chart of accounts, etc.) — it operates on platform events, not transactions.

2. Header Attributes and Table Parts

2.1 Header Attributes

The report does not contain its own attributes in the metadata. All selection and grouping parameters are passed through the DCS mechanism and are saved in the report variant settings. Typical parameters of the composition scheme:

• analysis period (start date / end date);
• selection by users (sessions);
• selection by event importance (Error, Warning, Information, Note);
• selection by event name in the log (_$Session$_.Start, _$Job$_.Start, etc.);
• selection by metadata / name of the scheduled task.

2.2 Table Parts

None. Data is dynamically generated from the registration log during the report execution; the object does not have permanent table parts.

2.3 Summary

The structure of the object is minimal: all business logic is encapsulated in the data composition scheme, data sets, and predefined report variants.

3. Forms

4. Key Module Procedures

In the evidence reference, the original BSL code is not attached, so below are typical handlers for the report on DCS in configurations based on BSP. Specific lines/names are clarified according to the object module version 3.0.74.2.

Report Object Module:

• OnResultComposition(DocumentResult, DataDecryption, StandardProcessing) — intercepts the formation of the result: programmatically reads the registration log through UnloadRegistrationLog() / ReadRegistrationLog, transforms it into a value table, and outputs it through the composition processor. For the registration log, this is a key handler, as the data is not taken directly from the DBMS.
• DefaultDataCompositionSetup() / overriding variants — sets predefined variants (Gantt chart, hourly activity, errors, etc.).

Form Module InformationAboutScheduledTask:

• OnCreateOnServer(Failure, StandardProcessing) — fills in the form attributes based on the passed session/task from the decryption.
• Handler for decryption/DecryptionProcessing of the main form — opens this form when clicking on the line of the scheduled task.

Requires verification (version-specific): the exact composition of predefined report variants and the signature of the log reading procedure may differ in the specific build 3.0.74.2.

5. Posting and Movements

The report is not posted and does not generate movements in the registers — it is an object of type “Report”, not “Document”. It does not create entries according to the standard chart of accounts of the RK (1210 “Short-term receivables from buyers”, 1030 “Cash in current accounts”, 1330 “Goods”, 3310 “Payables to suppliers”, 3130 “VAT payable”, 6010 “Revenue from sales”, 7010 “Cost of sales”, etc.), does not affect VAT registers, and does not influence the calculation of taxes and contributions (VAT 16%, IIN 10% / 15%, OPV 10%, OPVR 3.5%, VOSMS 2%, OSMS 3%, SO 5%, social tax 6%; MRP 4,325 ₸, MZP 85,000 ₸).

Data source — not the tables of registers, but the system registration log of the platform. The report performs only reading of events (start/stop of sessions, execution of scheduled tasks, errors), outputs them to a tabular document and charts. It does not make any entries in the information database.

6. Related Objects and Input Based On

• Subsystem “Report Variants” (BSP) — storage and selection of report variants, standard output form.
• Platform Registration Log — the only data source (session events, scheduled/background tasks, errors).
• Scheduled and Background Tasks — analysis objects; the form InformationAboutScheduledTask shows the details of a specific task.
• Input Based On — not supported and not applicable for the report.
• The report is not related to sales/purchase documents, electronic invoices (ESF), SST, and other accounting objects — they are not its data sources.

7. Extension Points

• Configuration Extension — adding custom report variants through the “Report Variants” subsystem; overriding OnResultComposition for additional filtering/aggregation of log events.
• Additional DCS Variants — saving user settings (new groupings: by computer, by application, by return code).
• External Reports / Additional Processing — BSP mechanism “Additional Reports and Processing” for distributing custom versions without changing the standard configuration.
• Decryption Processing — drill-down extension: opening custom diagnostic forms over the form InformationAboutScheduledTask.
• Limitation for Fresh — when making modifications, keep in mind that in the service model with data separation, direct access to the registration log is not available; custom log reading logic will not work in this mode.