Report "Loading Prohibition Dates" (Reports.LoadingProhibitionDates)

1. Identification

Purpose. The report displays periods during which the upload (modification) of data in certain accounting sections for specific recipients in the data exchange system is prohibited. This is a tool for controlling the integrity of information when working in distributed information bases (DIB) and data synchronization nodes. The report is used by administrators and exchange configuration specialists to monitor existing restrictions on document uploads by periods and sections. Access to the report is episodic — during the configuration of exchange rules, diagnosis of synchronization problems, or audit of modification prohibition policies.

Where to find in 1C: section "Administration" → "Prohibition upload dates". Direct opening — via the navigation link e1cib/list/Report.ProhibitionUploadDates.

The "Prohibition upload dates" mechanism is part of the BSP subsystem (Library of Standard Subsystems), block ProhibitionModificationDates. The report visualizes the settings stored in the information register of the subsystem, dividing them by recipients (exchange nodes) and accounting sections.

2. Attributes of Headers and Table Parts

2.1 Header Attributes

Attributes in the metadata are absent. The object of type "Report" does not use explicit attributes — instead, parameters and settings of the data composition (DCS scheme) are applied.

The actual input parameters of the report are set through DCS settings (parameters and selections), not through the object's attributes. Typical parameters for this class of reports are the analysis period and selection by recipient/exchange section.

2.2 Table Parts

Table parts are absent. Data is generated dynamically through the data composition system based on a query to the information registers of the exchange subsystem; the result is displayed in a tabular document form.

2.3 Forms

The dual-option presentation allows analyzing the same data in different perspectives — for example, "by recipients" and "by accounting sections" (or summarized/detailed), which is convenient for various exchange diagnosis scenarios.

3. Forms — List and Purpose

• ReportForm — user entry point. Through it, the composition is launched, the active option ("FirstOption" / "SecondOption") is selected, and the result is displayed. Since this is a DCS report, the form relies on the standard extended composition mechanism (form attributes Report, CompositionSettings, object Report of type ReportObject.ProhibitionUploadDates).

Separate settings/options forms for the object are not allocated — parameterization and option selection are performed within ReportForm using the platform's standard tools.

4. Key Module Procedures

Evidence with the text of BSL modules (paths/strings) for this object is not attached. Below are typical handlers characteristic of a DCS report with option switching; they correspond to the standard architecture of BSP reports.

Form Module (ReportForm):

• OnCreateOnServer(Refusal, StandardProcessing) — initialization of the composition settings, setting the active option by default, binding the composition scheme.
• OnOpen(Refusal) — if necessary, initial result formation and setting the visibility of control elements for options.
• Command handlers FirstOption / SecondOption — switch the active composition option (SetCurrentOption(...)) and reform the result in SpreadSheetDocumentField.
• Generate(...) (or standard composition command) — launch the composition processor and output to the tabular document.

Report Object Module (ReportObject.ProhibitionUploadDates):

• OnComposeResult(ResultDocument, DecodingData, StandardProcessing) — typical adjustment point: here, if necessary, preliminary reading of upload prohibition settings from the exchange subsystem and preparation/completion of the result before output is performed.

Requires verification on a specific release: the exact list of procedures and the presence of the OnComposeResult override are version-dependent. To obtain the actual code, open the object module and the form module in the configurator version 3.0.74.2.

5. Posting and Movements

The report is not posted and does not generate movements. Objects of type "Report" do not record in accumulation/information/accounting registers and do not create accounting entries — they only read data and output results.

• The 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) this report does not affect — it does not generate accounting entries.
• The data source of the report is the information register(s) of the "Prohibition of Modification/Upload Dates" exchange subsystem, where prohibition settings are stored by recipients (exchange nodes), accounting sections, and dates. The report queries them through DCS and presents them in tabular form.

Thus, the report does not influence regulated accounting, VAT (16% rate in the RK from 2026), PIT, pension contributions, and other calculations — it is a service-administrative tool for exchange control.

6. Related Objects and Input Based On

• Input based on for reports is not supported by the platform — it is absent.
• Related objects:
  • BSP subsystem "Modification Prohibition Dates" (ModificationProhibitionDates) and its information registers — primary data source.
  • Data exchange mechanism / exchange plans (recipient nodes), for which upload prohibitions are established.
  • Common modules of the exchange subsystem that form and verify prohibition dates during synchronization.
• Adjacent interfaces: processing and forms for setting modification/upload prohibition dates in the "Administration" section.

Electronic documents of the RK (ESF through IS ESF, STS) are functionally not related to this report — their export is regulated by separate mechanisms, although upload prohibition settings may indirectly affect the acceptance of documents during database synchronization.

7. Extension Points

• DCS report options. Custom composition options (additional groupings/selections) can be added through "Modify report option" without changing the configuration.
• Configuration extension (Extension). Standard way of refinement without removing from support: overriding/complementing handlers of ReportForm (for example, OnCreateOnServer, commands FirstOption/SecondOption) and OnComposeResult of the object module.
• Data composition scheme. Point for adding fields, data sets, or changing the query to the information registers of the exchange subsystem (when refining — considering compatibility with the BSP mechanism).
• Programmatic generation. The report can be called programmatically (Reports.ProhibitionUploadDates.Create() + composition) in service processing of exchange audit.

When making any refinements, maintain compatibility with the version of the exchange subsystem in release 3.0.74.2 — the signatures of internal BSP methods are version-dependent.