1. Identification
| Parameter | Value |
|---|---|
| Metadata object type | Report (Отчет) |
| Name | ДатыЗапретаЗагрузки |
| Full name | Отчет.ДатыЗапретаЗагрузки |
| Synonym | "Data Import Restriction Dates" |
| Configuration | Trade Management for Kazakhstan, edition 3.4 (version 3.4.5.21) |
| Subsystem | Standard Subsystems → "Data Change/Import Prohibition Dates" mechanism (SSL) |
| Layout basis | Data Composition System (DCS), runtime generation |
Purpose. A service (administrative) report from the Standard Subsystems Library (SSL). Displays in a clear form the current settings for data import prohibition dates — cutoff dates before which it is forbidden to import/accept data into the information base via data exchange mechanisms (DIB, synchronization, website exchange, import from external sources, EDF). The report helps the administrator and implementation specialist monitor for which exchange nodes, accounting sections, and objects restrictions are set, so that old "closed" periods are not overwritten by incoming external data.
It is important to distinguish two related SSL mechanisms:
- Change prohibition dates — block manual editing of documents by a user in a closed period.
- Import prohibition dates (this object) — block data changes specifically during import from external sources/exchanges, without affecting interactive user work.
Where to find it in 1C: "Standard Subsystems" section → "Import Prohibition Dates". Navigation link:
e1cib/list/Отчет.ДатыЗапретаЗагрузки.
2. Attributes and structure
The DCS report has no own header attributes or tabular sections like a document. The data is generated by the composition schema based on the SSL service mechanism, which stores settings in the prohibition dates information register. Logical structure of the output data:
| Field (report column) | Purpose |
|---|---|
| Prohibition date setting method | General date, by section, by object, by users/exchange nodes |
| User / Exchange node | Whom/which node the setting applies to (empty value — "for everyone") |
| Section (data type) | Accounting section to which the restriction applies (e.g., data exchange, import) |
| Object | Specific object/organization, if the restriction is detailed to the object level |
| Prohibition date | Cutoff date: data with a date ≤ the specified one is prohibited from import |
| Relative option | Date calculation method: fixed date or "offset" (end of last month/year, etc.) |
Report generation parameters (filled in on the form, not stored in the object):
- Relevance date — the point in time as of which to show the current settings.
- Filter by exchange node / user — filtering of the displayed list.
3. Forms
| Form | Purpose |
|---|---|
Main report form (ФормаОтчета) |
Setting parameters, running generation, and displaying the composition result. Standard DCS report form. |
| Settings form / report variants | Managing composition variants, filtering, and formatting (standard DCS mechanism). |
The object generally does not contain its own custom forms — standard DCS report forms provided by the platform and SSL are used.
4. Key module procedures
No application evidence (path:line) is attached for this object — the evidence contains only the "Purpose" facet. Below are the typical DCS report handlers for this object type in the SSL:
Object module → OnCompositionResult(...)— overridable DCS handler; adjusts the dataset, adds drill-down or service columns before output if needed.Report form → OnCreateAtServer(...)— form initialization, setting default parameters (relevance date = current session date), configuring element availability based on rights.Report form → BeforeGeneration / OnCompositionResult— substitution of filter parameters (user, exchange node) into the composer.- SSL common modules (
ДатыЗапретаИзменения,ДатыЗапретаИзмененияВызовСервера, and related) — provide functions for reading the current import prohibition dates, which the composition schema uses as a data source.
Specific procedure names and lines depend on the SSL release included in 3.4.5.21 — this is a version-specific point, to be verified against the object module in the specific build.
5. Posting and movements
The report is not posted and does not generate movements. This is a metadata object of type "Report": it only reads data and displays the composition result. It creates no records in accumulation/information registers and no accounting entries.
Consequently, entries on the standard Kazakhstan chart of accounts (1210 "Short-term receivables from customers", 1030 "Cash in current accounts", 1330 "Inventory", 3310 "Payables to suppliers", 3130 "VAT payable", 6010 "Revenue from sales", 7010 "Cost of sales") are not applicable to it, nor are tax calculations (VAT 16%, IIT, mandatory pension contributions, social tax, etc.) — these amounts are generated by accounting documents (sales, receipt, tax accrual), not by the service settings report.
The report's role in the accounting loop is indirect: the set import prohibition date prevents already posted and closed periods (including periods with generated e-invoices/waybills and calculated 16% VAT) from being overwritten by data coming from exchanges. The report only visualizes these restrictions.
6. Related objects and input based on
- SSL mechanism "Data Change/Import Prohibition Dates" — the source of the settings displayed by the report; stored in the service prohibition dates information register.
- "Data Exchange" / "Data Synchronization" subsystem — exchange plan nodes for which import prohibition dates are set; the date is checked precisely when importing from these nodes.
- EDF (e-invoices via the e-invoice IS, waybills) — receiving electronic documents is also subject to import prohibition date control in closed periods.
- "Change Prohibition Dates" report — a "mirror" service report on interactive editing prohibitions.
Input based on is not applicable to the report (not applicable to the "Report" type).
7. Extension points
- Configuration extension. Adding a custom composition/formatting variant or an additional filter column by extending the main report form.
- Overridable SSL modules. Adjusting the set of sections and the rules for calculating current dates — via the prohibition dates configuration modules (
ДатыЗапретаИзмененияПереопределяемыйand similar in the release). OnCompositionResult— programmatically adding service information/drill-downs to the result.- Additional reports (external). Connecting via the "Additional Reports and Data Processors" subsystem if custom analytics on the prohibition date are needed without modifying the standard configuration.
- Rights and access profiles. Restricting report visibility to administrator roles via access group profile settings.
For update resilience, perform all customizations in an extension without removing the object from support.