Nomenclature Series Movement" Report — Technical Description (UT for Kazakhstan 3.4.5.21)

1. Identification

Where to find it in 1C: "Service subsystems" section → "Item series movement". Navigation link: e1cib/list/Отчет.ДвижениеСерииНоменклатуры

The report is a service (utility) tool for register analysis. It does not modify data and does not generate postings/movements — it only reads and displays already registered turnovers and balances by series.

2. Attributes (parameters, fields, and DCS filters)

The report has no header attributes or tabular sections in the sense of a document. Its "fields" are the parameters, fields, and filters of the data composition scheme. Typical composition:

2.1. Composition parameters

2.2. DCS fields (dataset)

2.3. Filters, groupings, resources

• Resources: quantitative fields (Количество...), summed by groupings.
• Typical option groupings: Organization → Warehouse → Item → Item Series → Recorder.
• Filters are available for all dimensions (organization, warehouse, item, series, characteristic).

The report is quantitative: it does not contain amount (value) indicators, VAT rates (16% in Kazakhstan since 2026), or postings — value and tax accounting are maintained in other reports and registers.

3. Forms

The report generally has no dedicated additional forms (list, selection) — the general DCS form mechanism is used (ОбщаяФорма.ФормаНастроекОтчета, the variant selection form, etc.).

4. Key module procedures

Evidence with BSL code for this object is not attached (only the "purpose" facet was provided). Below are typical handlers characteristic of a DCS-based report in TM 3.4; in the specific 3.4.5.21 build some of these may be absent if the behavior is entirely declared by the scheme.

Report object module:

• ПриКомпоновкеРезультата(ДокументРезультат, ДанныеРасшифровки, СтандартнаяОбработка) — an intervention point in result output (conditional formatting of rows, programmatic layout finalization).
• НастройкиДляТехнологииАнализаДанных() / ПриОпределенииНастроек(Настройки) — registration of report variants and generation parameters (for SSL).

Report form module:

• ПриСозданииНаСервере(Отказ, СтандартнаяОбработка) — initialization of the default period, setting filters from the opening context, restoring user settings.
• ПриОткрытии(Отказ) — command interface adjustment.
• Panel command handlers ("Generate" calls КомпоноватьРезультат).

The main business logic (connection to the register, calculation of balances "opening/receipt/expense/closing") is implemented declaratively in the data composition scheme itself, not in BSL.

5. Data sources (registers) — the report does not generate movements

Since the object is a report, it is not posted, does not create movements or postings. It reads data from accumulation registers where series accounting is stored.

Movements to this register are recorded by goods movement documents (receipt, sale, transfer, capitalization, write-off). It is their postings that determine the accounts under the Kazakhstan standard chart of accounts:

Example: sale of a series for 116,000 ₸ with 2026 Kazakhstan VAT rate of 16% — value excluding tax 100,000 ₸ (Cr 6010), VAT 16,000 ₸ (Cr 3130), total receivable 116,000 ₸ (Dr 1210). For this sale, an ESF is issued in the ESF IS, and when moving/selling controlled goods — an SNT.

The report itself will only show the quantitative disposal of the series (КоличествоРасход), without amounts.

6. Related objects and entry based on

• The report does not participate in entry based on (it is not a document, cannot be a basis, and nothing is entered based on it).
• Related objects:
  • Catalog СерииНоменклатуры — the subject of analysis; drill-down to the catalog item is available from a report row.
  • Catalog Номенклатура (series owner), Склады, Организации.
  • Goods movement documents — recorders of the series register's movements; drill-down "to the recorder" with document opening is available from the report.
  • Accumulation register of series at warehouses — the data source.

7. Extension points

Standard ways to customize without losing support/with minimal intervention:

1. Additional report variants (DCS) — creating custom variants via "More → Change Variant" (groupings, filters, conditional formatting) and saving them as shared.
2. Configuration extension — adding a custom composition scheme/variant or overriding form attributes via an extension object, without modifying the standard one.
3. Object module handlers — ПриКомпоновкеРезультата (programmatic formatting, adding columns), ПриОпределенииНастроек (registering new variants in SSL).
4. Form module handlers — ПриСозданииНаСервере/ПриОткрытии for presetting the period and filters when opened from other places in the configuration.
5. Dataset extension — adding links to other registers in the DCS (e.g., displaying expiration date/days remaining from series attributes) via an extension.

Requires verification for build 3.4.5.21: the exact name of the series source register and the presence of a ПриКомпоновкеРезультата handler — these are version-dependent; check the DCS dataset composition and the object module of the specific delivery in the configurator.