Processing "Group Modification of Details" (UT for Kazakhstan 3.4.5.21)

1. Identification

Purpose. The data processor is designed for mass (batch) changing of attribute values and tabular sections for an arbitrary set of infobase objects — catalog items, documents, charts of characteristic types, etc. It allows an administrator or a responsible user to assign the same value to a selected attribute of hundreds and thousands of objects in a single run, apply a formula/custom algorithm, select objects by condition and (if necessary) re-post the changed documents. This is an administrative data maintenance tool; it carries no domain-specific (accounting) logic of its own.

The data processor changes attributes "as is", therefore it must be run under a user with rights to modify the corresponding objects and, as a rule, when no other users are actively working with this data.

2. Attributes and tabular sections

The data processor does not store data in the database (it is a data processor, not a document); all parameters exist only on the form during the session. The following groups of data are used logically:

Selection parameters

Tabular section "Attributes to change" (list of change rules)

Execution parameters

3. Forms

The specific composition of auxiliary forms is version-specific and depends on the edition of the SSL built into 3.4.5.21 (requires verification against the form composition of the specific build).

4. Key module procedures

No evidence with BSL paths/lines has been attached for this data processor, so the typical handlers of this type of object (the SSL "Group Object Modification" data processor) are listed below. The names correspond to the standard implementation; exact signatures should be verified against the build's module.

Form module

• ПриСозданииНаСервере (OnCreateAtServer) — form initialization, populating available object types, restoring saved user settings.
• ТипОбъектовПриИзменении (ObjectTypeOnChange) — rebuilding the composition of available attributes and filter fields when the type of objects to change is switched.
• ДобавитьИзменение / ИзменениеРеквизитаПриИзменении (AddChange / AttributeChangeOnChange) — creating and editing change rule rows.
• ИзменитьРеквизиты (ChangeAttributes, the run command) — validating settings and launching the background job for processing.

Object module / common server module

• ИзменитьОбъекты(ПараметрыОбработки) (ChangeObjects(ProcessingParameters)) — the main loop: selecting objects by filter/list, applying rules, writing and (optionally) posting, accumulating the result.
• ПрименитьИзменения(Объект, ПравилаИзменения) (ApplyChanges(Object, ChangeRules)) — assigning values to attributes/tabular section columns of a single object, calculating formulas.
• ЗаписатьОбъект(Объект, РежимПроведения) (WriteObject(Object, PostingMode)) — writing with lock and exception handling, taking into account the "re-post/write only" mode.
• ЗарегистрироватьОшибку(...) (RegisterError(...)) — accumulating error messages for the results report.

5. Posting and register movements

The data processor does not generate its own register movements or postings. This is a service tool: the data processor has no register tabular sections and no ОбработкаПроведения (DocumentPosting) procedure — it is not a document.

The impact on accounting arises indirectly:

• when changing attributes of documents with the "Re-post" mode enabled, the standard posting of the changed documents is invoked, which generates movements according to its own rules;
• when changing attributes of catalog items (items, counterparties, organizations, warehouses), no movements are created, but the new values start being used in subsequent document postings.

Therefore all postings are the result of the re-posted documents' operation, not of the data processor itself. For the Trade Management for Kazakhstan 3.4 configuration, the standard Kazakhstani accounts involved in the subsequent re-posting of trade documents are:

Example of impact: when the VAT rate/analytics is mass-changed in sales documents and they are subsequently re-posted, the VAT amount is recalculated at the rate effective in 2026 of 16% (for example, on a base of 100,000 ₸, VAT = 16,000 ₸, reflected as a credit to 3130; revenue as a credit to 6010, cost as a debit to 7010). Electronic documents (ESF in the ESF IS, waybills (SNT)) are not automatically regenerated by the group change — their generation is performed by separate scheduled procedures, and incorrect mass editing of attributes of already issued documents may lead to discrepancies with the submitted ESF/SNT.

Mass retroactive re-posting of documents recalculates batches and cost (7010) along the entire chain — the operation should be performed in exclusive mode with subsequent monitoring of the sequence of calculations.

6. Related objects and entering based on

• There is no "enter based on" — the data processor does not participate in "enter based on" schemes either as a source or as a target.
• Objects targeted by changes — any catalog or document of the configuration available for group modification (items, counterparties, contracts, agreements, prices, orders, sales, etc.).
• SSL subsystems: "Group Object Modification", "Additional Attributes and Information" (allows changing additional attributes), "Settings Storage" (saving run settings), "Background Jobs" (long-running execution).
• Registers are affected only indirectly — through re-posting of the changed documents.

7. Extension points

• Configuration extension (Extension): borrowing the object/form module of the data processor to add custom value validation rules or post-processing after writing.
• Formulas/algorithms in change rules — the standard way to calculate a new attribute value with an expression in the built-in language without modifying the configuration.
• Programmatic call of the data processor's server methods from custom data processors/jobs to automate regular mass edits.
• Access rights restriction: it is advisable to restrict the run command to the administrator/master data owner role, since the data processor bypasses the business logic of input forms.
• Event subscriptions for writing the changed objects are triggered normally — they can be used to audit group changes.

Direct modification of the standard data processor's module is not recommended: the changes will be overwritten when the SSL release is updated. Extensions and external handlers are preferred.