Directory "Additional Reports and Processes" (Accounting for Kazakhstan 3.0)

1. Identification

Purpose. The catalog is designed for the registration and administration of additional (external) reports and data processors that extend the functionality of the configuration without modifying the source code (without removing from support). It allows you to upload a file .epf (data processor) or .erf (report) into the database, set the publication status, define the visibility of commands in the interface, assign data processors to users, and distribute their commands across menu sections and object forms.

Work with the object is not frequent — during the implementation of a new data processor, updating its version, or changing publication. This is a service (administrative) catalog: it does not participate in accounting and does not store accounting data of the enterprise by itself.

Where to find in 1C: section “Administration” → “Printed forms, reports and data processors” → “Additional reports and data processors”. Navigation link: e1cib/list/Catalog.AdditionalReportsAndDataProcessors

2. Attributes of Header and Table Parts

2.1 Header Attributes

The attribute Name (standard) stores the representation of the data processor in the list. The attribute Parent is absent if the catalog is non-hierarchical; grouping is performed through assignment by sections (see Table Part “Sections”).

2.2 Table Parts

Commands — a list of commands (menu items) that the data processor provides to the user.

Sections — sections of the command interface and destination objects where the commands of the data processor are available (for types “Data Processor”, “Additional Report”, “Printed Form” — binding to sections; for “Object Filling”/“Printed Form” — binding to types of owner objects).

Destinations (in standard BSP implementation) — a list of document/catalog types for which the data processor is applicable.

PermissionsForUsingSecurityProfiles / Permissions — a list of permissions requested by the data processor (access to files, internet, external components) used when working through server security profiles.

3. Forms

The forms of the data processor itself (SettingsForm, arbitrary forms) are stored within the uploaded .epf/.erf and are called dynamically, not described in the metadata of the catalog.

4. Key Procedures and Mechanisms

Evidence with the original BSL is not attached, so below are the typical mechanisms of this object within the BSP subsystem “Additional reports and data processors”. The main logic is extracted into common modules AdditionalReportsAndDataProcessors (client/server) and AdditionalReportsAndDataProcessorsServerCall.

• Loading the data processor into the database. When selecting a file, binary data is read, placed in DataProcessorStorage, and InformationAboutExternalDataProcessor() is extracted — type, version, information, command composition. The attributes Type, Version, ObjectName, Information, and Table Part “Commands” are filled automatically.
• ConnectExternalDataProcessor / GetExternalDataProcessorObject. Creates an instance of the external object from DataProcessorStorage for executing the command. When SafeMode is set, the connection is performed with isolation through SafeMode.SetSafeMode().
• ExecuteCommand. By the command identifier and LaunchOption, opens a form, calls a client/server method of the data processor, or generates a printed form. For long operations, a background task with an indicator is used.
• Permission check. Before connecting, the permissions requested by the data processor (PermissionsForUsingExternalResources) are checked considering CompatibilityModeForPermissions and enabled server security profiles.
• Publication control. When the status Publication = Disabled, commands are not displayed in the interface; Debugging — the data processor is available only to the author/administrator for debugging.
• Filling handler (FillingProcessing). By default, sets Responsible = Users.CurrentUser() and Publication = In Use.
• FillingCheckProcessing. Controls the filling of mandatory Responsible and Publication.

Requires verification (version-specific): the exact composition of common modules and method signatures depend on the version of BSP embedded in 3.0.74.2.

5. Posting and Movements

The catalog is not a posted object and does not generate accounting entries and movements in accounting registers. It does not have a PostingProcessing handler, does not create records in the accounting register (the standard chart of accounts of the RK — 1210, 1030, 1330, 3310, 3130, 6010, 7010 — is not affected by this catalog), does not influence the calculation of VAT (16%), PIT, WHT/WT, OSS/VOOS, social tax, and does not participate in the formation of ESF/SNT.

All results of work (entries, printed forms, filling of attributes) are created by the connected external data processor itself when the user launches its command — for example, an additional data processor can post a sales document, which will already generate income on account 6010, cost on 7010, and VAT payable on 3130 at a rate of 16%. Responsibility for the correctness of such movements lies with the external data processor, not the catalog.

Changes to the catalog item are only recorded in the service registers of the platform (registration log, object versioning, if enabled).

6. Related Objects and Input Based On

• Enumeration.TypesOfAdditionalReportsAndDataProcessors — defines the type and method of invocation.
• Enumeration.PublicationOptionsForAdditionalReportsAndDataProcessors — publication statuses.
• Enumeration.CompatibilityModesForPermissionsOfAdditionalReportsAndDataProcessors — permission check mode.
• Catalog.Users — attribute Responsible and assignment of command visibility by users.
• Catalog.MetadataObjectIdentifiers — binding commands to sections and destination objects.
• Information Register “CommandSettingsForAdditionalReportsAndDataProcessors” / “ScheduledRegulatoryTasks” — schedules for executing commands by regulation.
• Regulatory task “RunAdditionalDataProcessorsBySchedule” — background execution of data processor commands.

Input based on is not provided for this catalog: it is not a source and does not accept input based on. Loading is performed from an external file .epf/.erf, not by copying from other objects.

7. Extension Points

• External data processors as such — are the main built-in mechanism for extending the configuration without removing from support; this catalog is the entry point for them.
• Configuration extensions — you can add attributes to the catalog, change forms (ElementForm, ListForm) and override handlers through subscriptions and extension modules.
• Module AdditionalReportsAndDataProcessorsOverridable — a typical configuration point: allowed types of data processors, sections for placement, restrictions on safe mode.
• Server security profiles — managing the rights of external data processors to access files, the internet, and external components.
• Event subscriptions (BeforeWriting, WhenSettingStandardSectionSettings) — for controlling publication and assignment when implementing your own policies.

Requires verification: the availability of safe mode and security profiles depends on the mode of operation (file/client-server) of the specific information base.