1. Identification
| Parameter | Value |
|---|---|
| Object Type | Report |
| Name | VolumeIntegrityCheck |
| Full Name | Report.VolumeIntegrityCheck (Reports.VolumeIntegrityCheck) |
| Synonym | Volume integrity check |
| Configuration | Accounting for Kazakhstan, edition 3.0 (3.0.74.2) |
| Subsystem | Standard subsystems → "File Management" (administration/service) |
| Basis | Data composition system (DCS), external data set |
| Purpose | Diagnostics of the physical integrity of the file storage of volumes: identifying redundant (excess) files on the volume disk that do not correspond to current records in the information base (IB) |
Purpose. The report is intended for monitoring the integrity of the file storage when placing files in volumes on the disk (and not in the IB itself). It builds a list of files that are physically present in the volume directory but are not linked to any current database records. Such files are candidates for deletion to free up disk space. The report is run on demand by the administrator or the person responsible for maintenance — when there is suspicion of a discrepancy in the storage or as part of a scheduled check.
Important: this is a service (technical) report of the "File Management" subsystem. It does not relate to accounting/tax reports and does not operate with amounts, tax rates, chart of accounts, or electronic documents (ESF/SNT). Accordingly, the rates and constants of the RK for 2026 (VAT 16%, MRP 4,325 ₸, MSP 85,000 ₸, etc.) are not applicable to this object — they relate to accounting objects of the configuration, not to this diagnostic tool.
Where to find in 1C. Section "Administration" → "Maintenance" → file management / service functions. Navigation link: e1cib/list/Report.VolumeIntegrityCheck.
2. Header Attributes and Table Parts
2.1 Header Attributes
No custom attributes in metadata. The report does not have saved header attributes. The only significant setting — the volume whose integrity is being checked — is passed not as an object attribute, but as a external parameter of the DCS settings composition.
| Name | Type | Mandatory | Purpose |
|---|---|---|---|
| Volume (DCS parameter) | ReferenceLink.FileStorageVolumes |
Yes | Selects the volume for which redundant files are analyzed. Passed as a parameter of the external data set of the DCS |
2.2 Table Parts
No table parts. The structure of the report's metadata does not contain table sections. The result (list of redundant files) is generated dynamically: the DCS retrieves data from the external set, which fills the service module FileManagementInVolumesService. The output result usually contains the following columns:
| Result Column | Meaning |
|---|---|
| File / File Name | Name of the redundant file in the volume directory |
| Path / Relative Path | Location of the file within the volume structure |
| Size | File size (to estimate freed space) |
| Modification Date | File timestamp on the disk |
2.3 Forms
No custom forms in metadata. The report uses a standard automatically generated report form of the DCS. The user interacts with the standard interface:
| Form Element | Purpose |
|---|---|
| Settings Panel | Selecting the "Volume" parameter |
| "Generate" Button | Starts report generation |
| Table Document Area | Displays the list of redundant files |
3. Forms — List
Since there are no explicit forms in the metadata, a single standard form is used:
- Main report form (auto-generated DCS form) — the single point of user interaction with the report: setting the volume parameter, generating and viewing the result. The object does not contain separate settings forms, list forms, or auxiliary forms.
4. Key Module Procedures
The source code (BSL) of the report module is not provided in the attached evidence, so below are typical report handlers for this type of object. The application logic for forming the data set is implemented in the service module of the file management subsystem.
| Procedure/Function | Module | Purpose (typical logic) |
|---|---|---|
OnResultComposition |
Report object module | Main DCS handler. By default StandardProcessing = False; retrieves the external data set with the list of redundant files and performs composition into a table document |
| Forming the external data set | FileManagementInVolumesService (common module) |
Compares the physical contents of the selected volume directory with current records in the IB and returns a table of files that have no match in the database (redundant files) |
OnServerCreation / initialization of settings |
Report form (auto form of DCS) | Setting the default "Volume" parameter, availability of elements, initial settings of the composition |
Requires verification (version-specific): the exact name of the service function for forming the data set and the call signature in
FileManagementInVolumesServicemay differ between versions of the BSP/configuration.
5. Posting and Movements
The report is not posted and does not generate movements. As an object of type "Report," it does not participate in document flow, does not create postings, and does not write to registers (accumulation, information, accounting). Accordingly, it is not applicable for:
- postings according to the RK chart of accounts (1210, 1030, 1330, 3310, 3130, 6010, 7010);
- movements in VAT registers and entries in the ESF information system / formation of SNT;
- any amount calculations.
The report performs read-only: it analyzes the volume directory and metadata of file records, forming an informational result. Changes (deletion of redundant files) are performed by separate service mechanisms of the file management subsystem, not by the report itself.
6. Related Objects and Input Based On
| Object | Type | Relation |
|---|---|---|
Reference.FileStorageVolumes |
Reference | Source of the "Volume" parameter value; volume directory on disk — object of analysis |
FileManagementInVolumesService |
Common module | Provider of the external data set for the report |
| Registers of information on file storage / service objects for storing file versions | Registers/references of BSP | Reference of current records against which the physical contents of the volume are checked |
| File Management Subsystem (BSP) | Subsystem | Functional container: processing of unused file deletions, transferring files between volumes, etc. |
Input based on is not supported for reports (the mechanism applies to documents). The report is not a basis and is not input based on other objects.
7. Extension Points
- Configuration extension — adding a custom report form instead of the auto form of the DCS for customizing the settings panel and output; adding form attributes for additional filters.
- Handler
OnResultComposition— overriding/extending in the extension for post-processing the result (for example, adding service columns, highlighting large files). - Service module
FileManagementInVolumesService— BSP programming interfaces for obtaining a list of redundant files; when updating BSP, monitor compatibility of signatures. - DCS settings (composition scheme) — extending the composition of fields, groupings, and formatting through the layout of the report's data composition scheme.
- Rights and roles — managing access to the report through roles of the administration subsystem (access is usually only for administrators/maintenance personnel).
Requires verification: the specific composition of the programming interface of the service module and the presence of overridable handlers depend on the version of the BSP supplied with release 3.0.74.2.