Report "Prohibition Change Dates" (Reports.ProhibitionChangeDates)

1. Identification

Purpose. The report is designed for visualizing and controlling periods during which editing of accounting data in the information base is prohibited. It is used by accountants and administrators to check the configured closing dates for various accounting sections (financial, tax, HR) or for specific accounting objects. It is automatically generated upon opening the form, without a preliminary parameter dialog, and provides two display modes:

• By Accounting Sections (summary option);
• By Objects (detailed view by organizations, users, document types).

It is regularly used in preparation for closing the month/quarter (for example, before generating electronic invoices (ESF) and declarations) and during audits of access rights to data modification.

Where to find in 1C: section “Administration” → “Prohibition Change Dates”. It can also be called from the “Service” section of the main menu.

The prohibition date mechanism is system-wide (provided by the standard subsystem library, BSL), so its behavior and structure are the same for RK configurations and do not depend on country-specific numerical norms (VAT rates, MRP, deductions). The report only displays the already configured date values.

2. Attributes and Tabular Parts

2.1 Header Attributes

The report does not contain its own attributes at the metadata level (attributes: []). All selection parameters (prohibition addressees, dates, objects, sections) are set through the data composition mechanism and the composition scheme embedded in the report layout. The user manages the selection through the standard report settings panel.

2.2 Tabular Parts

The report does not have tabular parts (tabular_sections: []). The result is formed in a tabular document using DCS based on data obtained from the prohibition change date subsystem.

2.3 Logical Fields Output (formed by DCS)

Although there are no own attributes, the resulting tabular document displays fields characteristic of the subsystem:

3. Forms

Key Form: ReportForm. All user work occurs through it: opening immediately initiates report generation, switching between summary and detailed options is done via the identically named buttons.

4. Key Module Procedures

No own BSL code (evidence at the module level) is attached, so below are typical handlers for reports of this type in DCS in configurations on BSL. Exact names and contents of procedures are version-specific.

Form Module (ReportForm):

• OnCreateOnServer(Refusal, StandardProcessing) — initialization; sets the default report option and prepares DCS settings.
• OnOpen(Refusal) / auto-generation — starts composition immediately upon opening (parameter dialog is not shown).
• FirstOption(Command) — switches the composition scheme/option to the “by accounting sections” view and rebuilds the tabular document.
• SecondOption(Command) — switches to the detailed view “by objects” (organizations, users, documents).
• GenerateReport() / calls the composer — fills the data source with prohibition date values from the subsystem and outputs the result in the tabular document field.

Object Module / Report Manager Module:

• OnComposeResult(ResultDocument, DataDecoding, StandardProcessing) — if necessary, intercepts the standard DCS composition for programmatically filling in prohibition date data.
• Procedures for obtaining data from the general BSL mechanism (e.g., calls to the module ProhibitionChangeDatesService / ProhibitionChangeDates) to read current prohibition settings.

“Requires verification” (version-specific): exact names of service common modules of BSL and handler signatures may differ in a specific build 3.0.74.2.

5. Posting and Movements

The report does not perform postings and does not generate movements in registers and postings according to the chart of accounts. This is a metadata object of the type “Report”: it only reads and displays data.

The data source of the report is the settings of the “Prohibition Change Dates” subsystem (stored in service information registers of the BSL mechanism, where pairs “addressee/section → prohibition date” are recorded). The report aggregates this information using DCS and outputs it in a tabular document.

For context: the prohibition dates restrict editing of accounting documents (e.g., sales documents that generate income on account 6010 and VAT payable on 3130, payments on 1030/1210, goods receipts on 1330/3310) after the period is closed. However, these postings generate application documents, not this report. The report only shows until which date such changes are prohibited.

6. Related Objects and Input Based On

• Input Based On: absent. For reports, the input based on mechanism is not applied.
• Related Objects:
  • Subsystem “Prohibition Change Dates” (BSL) — data provider; configuration is performed in the prohibition date settings form (section “Administration”).
  • Service information registers of the prohibition mechanism — actual storage of date values.
  • Application documents of the configuration (sales, receipts, cash/bank, HR), editing of which is regulated by established dates. Electronic documents of the RK — ESF (ESF IS) and SNT — are generated based on these documents, so the prohibition of changes indirectly protects already uploaded ESF/SNT from desynchronization with accounting.

7. Extension Points

• Report Options DCS — adding custom display options (e.g., only for regulated accounting) through the report options storage, without removing from support.
• Configuration Extension — overriding handlers of the form module ReportForm (OnCreateOnServer, commands FirstOption/SecondOption) and adding custom form elements/commands.
• Subscriptions and Service Modules of BSL — influence on the composition of data through overridable modules of the prohibition date subsystem (configuration of addressees and sections), which will automatically reflect in the report.
• User DCS Settings — selection, grouping, and conditional formatting are available through the standard settings panel without modifications.