1. Identification
| Parameter | Value |
|---|---|
| Object Type | Catalog |
| Name | SuppliedData |
| Full Name | Catalogs.SuppliedData |
| Synonym | — (no separate synonym assigned; representation matches the name) |
| Configuration | Accounting for Kazakhstan, edition 3.0.74.2 |
| Object Class | Service (technological) catalog |
Purpose. The catalog is intended for storing and accounting for data loaded into the information base from external sources or supplied with the configuration. It provides centralized management of data files of various types with support for multiple storage methods: directly in the database (ValueStorage), on server disk volumes, or via external paths. It is used by administrators and automated processes (configuration updates, periodic updating of classifiers, exchange rates, report templates, etc.). Access is either programmatic or through administrative forms. The frequency of use is determined by the regularity of updates to the supplied data.
Where to find in 1C: section "Service Technology" → "Supplied Data".
Navigation link: e1cib/list/Catalog.SuppliedData
This is a technological object. It does not participate in accounting and tax accounting, does not generate entries, and is not directly related to VAT rates (16%), PIT, social tax, etc. The country norms of RK-2026 do not apply to its logic.
2. Attributes of Header and Table Parts
2.1 Header Attributes
| Name | Type | Mandatory | Purpose |
|---|---|---|---|
| DataType | String |
Not checked | Identifies the category/type of supplied data ("Bank Classifier", "Exchange Rates", "Report Templates", etc.). Used when generating an automatic description of the element. |
| DateAdded | Date (dateTime) |
Not checked | The moment of the initial data upload into the system. Allows tracking of relevance and update history. |
| StoredFile | ValueStorage |
Not checked | Binary content of the file stored directly in the database (storage mode "In the information base"). Used for small files or for complete autonomy of the base. |
| FilePath | String |
Not checked | Relative or full path to the file on disk (storage modes in volumes or via external path). Provides access to large files without overloading the database. |
| Volume | CatalogReference.FileStorageVolumes |
Not checked | The storage volume — the physical location of the file on the server when managed storage is in volumes. |
| FileStorageType | EnumerationReference.FileStorageTypes |
Not checked | Storage method: in the database, in a volume on the server, or via external path. Critical for correct extraction of content. |
| FileIdentifier | UniqueIdentifier (UUID) |
Not checked | Unique identifier of the file for unambiguous addressing in the storage system, especially when working with volumes. |
| Description | String |
Not checked | Automatically generated textual representation of the element (combines DataType and characteristics). Programmatically filled in the BeforeWriting event based on DataType and the table part DataCharacteristics. |
Standard attributes of the catalog: Code, Name, DeletionMark, Predefined (the hierarchy for the object is not used — linear list).
2.2 Table Parts
DataCharacteristics
Purpose. Stores additional attributes and parameters of the supplied data in the form of "key-value" pairs. Allows flexible description of the specifics of the data without changing the structure of the catalog.
| Name | Type | Purpose |
|---|---|---|
| Characteristic | String |
Name of the characteristic — key in the pair ("Version", "Region", "Format", "RelevanceDate"). |
| Value | String |
Value of the characteristic corresponding to the key. The set of strings is used when constructing the automatic Description. |
3. Forms
The service catalog of this type is characterized by a minimal set of managed forms:
| Form | Purpose |
|---|---|
| ListForm | View and administration of the list of uploaded data. Opens via the link e1cib/list/Catalog.SuppliedData. The main tool for the administrator. |
| ElementForm | View/edit a single element: data type, storage method and parameters, characteristics table. May be hidden for purely programmatically filled objects. |
| SelectionForm | Selecting an element during programmatic and interactive links from other objects (usually inherited from the list form, may not be created separately). |
The presence of a separate
ElementForm/SelectionFormis version-dependent: some service catalogs use auto-generated forms. Requires verification in the specific build 3.0.74.2.
4. Key Procedures of Modules
No separate BSL-evidence for modules is attached. For a catalog of this structure, the following typical handlers are characteristic (object module / manager module / form modules).
Object Module:
BeforeWriting(Refusal)— generates the attributeDescriptionbased onDataTypeand rows of the table partDataCharacteristics(combination of "key-value"); may normalize/setDateAddedif it is not filled. According to evidence, this is whereDescriptionis programmatically filled.OnWriting(Refusal)— synchronizes the placement of content (StoredFile/FilePath/Volume) as needed according toFileStorageType.CheckFillingProcessing(Refusal, CheckedAttributes)— generally relaxed: most attributes are marked "Not checked", mandatory control at the platform level is not performed.
Manager Module:
- Functions for accessing the content of the file by element considering
FileStorageType(extraction fromStoredFile, reading from volumeVolume/FileIdentifieror viaFilePath). - Functions for searching/getting an element by
DataTypefor automatic update processes.
Form Modules:
ListForm— handlers for selection and opening elements.ElementForm—OnOpen, updating service fields for displaying file storage.
The exact names and signatures of procedures in build 3.0.74.2 — requires verification in the configurator (evidence for BSL is not provided).
5. Posting and Movements
The catalog is a non-postable object. It is not a document, does not have a posting mechanism, and does not generate accounting entries and movements in registers (accumulation, information, accounting).
Accordingly, it does not relate to accounting elements of the RK: chart of accounts (1210, 1030, 1330, 3310, 3130, 6010, 7010), VAT rate 16%, PIT, social tax 10%, OPP 3.5%, VOSMS 2%, OSMS 3%, CO 5%, social tax 6%, as well as electronic documents (ESF/SNT). All of this is the subject area of accounting objects of the configuration, not the service data storage.
The only "state changes" when recording an element are the updating of the catalog record itself and the associated file content (in the database or in the storage volume).
6. Related Objects and Input Based On
| Relation | Object | Nature of Relation |
|---|---|---|
| Storage in volumes | Catalog.FileStorageVolumes |
The attribute Volume refers to the volume; defines the physical location of the file on the server. |
| Storage method | Enumeration.FileStorageTypes |
The attribute FileStorageType sets the mode (in the database / in the volume / via path). |
| Data consumers | Mechanisms for updating classifiers, loading exchange rates, report templates, etc. | Read content by DataType and storage parameters. |
Input based on for the service catalog is not provided: elements are created programmatically by loading/updating processes or manually by the administrator. As a basis for other objects, the catalog generally does not serve.
7. Extension Points
- New data types.
DataTypeis a string and is not limited by enumeration, so categories can be expanded without modifying metadata: it is sufficient to agree on the value with the consuming process. - Additional attributes. The table part
DataCharacteristics("key-value") allows describing new parameters without changing the structure of the catalog — the preferred method of extension. - Configuration extension. It is possible to add custom attributes/forms and redefine handlers (
BeforeWriting,OnWriting) in the extension without removing the standard from support. - Event subscriptions. For cross-cutting processing of recording/deleting elements, it is permissible to use event subscriptions instead of modifying the object module.
- Storage logic. When adding custom file placement modes, the processing of
FileStorageTypein the manager module is expanded; it is important to maintain consistency betweenStoredFile/FilePath/Volume/FileIdentifier.
When making modifications, consider that the object belongs to the technological layer of the configuration and may be updated by the supplier — changes are safer to implement in an extension.