Reference Guide "Sets of Additional Attributes and Information" (Accounting for Kazakhstan 3.0.74.2)

1. Identification

Purpose. The catalog stores sets of additional attributes and information — configurable lists of dynamic fields that can be added to accounting objects (documents, catalogs, elements of business processes) without changing the metadata structure. Each catalog item corresponds to a specific "owner of properties": for example, a set for counterparties, for contracts, for nomenclature. The set defines which additional fields will be displayed in the input forms of the corresponding object and available in selections/reports.

Sets are used by administrators and users with extended rights during initial setup and periodic updates of accounting policies. This is purely a configuration (metadata) catalog — it does not participate in economic accounting, does not generate entries and movements, and does not operate with amounts, rates, or accounts. Numerical norms of the RK (VAT 16%, MRP 4,325 ₸, MSP 85,000 ₸, etc.) do not directly relate to this object — it merely describes the fields whose values are used by other objects.

Where to find in 1C:

• Command interface: "Administration" → "General Settings" → "Additional Attributes and Information".
• Direct navigation link: e1cib/list/Catalog.AdditionalAttributesAndInformationSets

2. Attributes of Headers and Table Parts

2.1 Header Attributes

Standard attributes of the catalog (Code, Name, Parent, ThisIsGroup, DeletionMark, Predefined) are present by default and are not described separately in evidence. Name stores the representation of the set (usually coincides with the synonym of the owner object to which the set is linked).

2.2 Table Parts

AdditionalAttributes

List of additional attributes — fields whose values are stored directly in the owner object and filled in its input forms.

AdditionalInformation

List of additional information — data that is stored not in the object itself, but in a separate information register AdditionalInformation. Used for information that changes independently of the object or has a history.

The key difference: attributes live in the object (attribute of the owner object), information — in an independent information register. This affects behavior regarding historical data and during export/exchange.

3. Forms

The catalog uses standard forms of the BSP subsystem "Properties":

Additionally, the subsystem involves auxiliary common forms of BSP (not forms of this catalog): property editing form (AdditionalAttributeAndInformation), value type selection form, visibility and mandatory settings form. They are called from ElementForm.

4. Key Procedures of Modules

There is no direct BSL-evidence for the modules of the object. Below are typical handlers for the service catalog of the BSP subsystem "Properties"; their presence/signatures are version-specific and require verification in the specific build 3.0.74.2.

Object Module (ObjectModule):

• BeforeWriting(Refusal) — recalculation of caching attributes NumberOfAttributes, NumberOfInformation, NumberOfTags based on the current composition of table parts; control of duplicates of properties in the set.
• FillingProcessing(FillingData, FillingText) — initialization of a new set (for example, linking to the owner object).
• OnCopying(CopyingObject) — clearing service fields NameOfPredefinedSet when copying, so that the copy is not considered predefined.

Manager Module (ManagerModule):

• Functions for obtaining the set by owner object and by name of the predefined set.
• Procedures for processing during the update of the IB (matching predefined sets by NameOfPredefinedSet).

Element Form Module:

• OnCreateOnServer — building dynamic tables of properties, configuring command availability by rights.
• Commands AddAttribute / AddInformation / Create / ChangeProperty / HighlightInSeparateGroup — managing the composition of the set through calls to the common module ManageProperties (server methods of BSP).

The main business logic is extracted into common BSP modules (ManageProperties, ManagePropertiesService, ManagePropertiesServiceServerCall), not in the module of the catalog itself.

5. Posting and Movements

The catalog is not posted and does not generate movements — it is an object of type "Catalog", not "Document". It does not create records in accumulation registers, accounting registers, and does not generate entries.

Indirect connection with accounting registers:

• Values of additional information of owner objects are stored in an independent information register AdditionalInformation (dimensions — object and property), but records there are written by the owner object, not the set itself.
• Values of additional attributes are stored in the table part of the owner object.

Since the object is a configuration one, it does not operate with accounts of the standard chart of accounts of the RK and amounts. For comparison, we will show where numbers actually arise — in other objects, whose forms this catalog merely supplements with fields:

• Sale of goods: income — account 6010 (income from sales), cost of goods sold — 7010, write-off of goods — 1330, accounts receivable — 1210, VAT payable at a rate of 16% — 3130.
• Example: sale of 1,000,000 ₸ excluding VAT → VAT 16% = 160,000 ₸; entries Dr 1210 Cr 6010 1,000,000 ₸ and Dr 1210 Cr 3130 160,000 ₸; receipt of money Dr 1030 Cr 1210; purchase from the supplier — Dr 1330 Cr 3310.

These entries form documents of sales/receipts; the set of additional attributes merely adds user-defined fields (for example, "Sales Channel", "Region") to such documents and does not affect amounts/accounts.

6. Related Objects and Input Based On

Related Objects:

• PlanOfCharacteristicTypes.AdditionalAttributesAndInformation — source of the properties (attributes/information) that are referenced by the table parts of the set.
• InformationRegister.AdditionalInformation — storage of values of additional information of owner objects.
• InformationRegister.PurposeOfAdditionalAttributesAndInformation (if present in the build) — correspondence of the set to owner objects.
• Owner objects (Counterparties, Contracts, Nomenclature, documents, etc.) — consumers of sets; fields from the set are dynamically inserted into their forms.
• Common BSP modules ManageProperties* — API for working with sets and values.

Input Based On. The classic "Input Based On" mechanism for this catalog is not applied (the object is configuration). An analogy is the service copying of properties between sets and the automatic creation/matching of predefined sets during configuration updates.

7. Extension Points

• Adding Custom Properties. The main standard customization scenario: creating user-defined additional attributes/information through the plan of characteristic types and including them in the necessary set — without removing the configuration from support.
• Configuration Extensions. Borrowing forms ElementForm/ListForm and adding handlers &After/&Before/&Instead for additional logic (for example, auto-filling the composition of the set, additional validation).
• Subscriptions to Events of catalog record — for auditing changes in the composition of sets.
• Programmatic Control through the common module ManageProperties (creating a set, adding properties, reading/writing values) — the preferred way instead of direct work with table parts.
• Rights and Access Profiles — restricting editing of sets by roles of property administration.

Version-specific and requires verification in 3.0.74.2: exact names of auxiliary references...