1. Identification
| Parameter | Value |
|---|---|
| Object type | Catalog (Reference book) |
| Name | ВидыПланов |
| Full name | Справочник.ВидыПланов |
| Synonym | "Plan types" |
| Configuration | Trade Management for Kazakhstan, edition 3.4 (version 3.4.5.21) |
| Subsystem | Service subsystems → planning section (sales/procurement/warehouse) |
| Navigation link | e1cib/list/Справочник.ВидыПланов |
| Where to find in 1C | "Service subsystems" section → "Plan types" |
Purpose. The catalog is a classifier (a list of configurable "templates") of plan types used by the configuration's planning subsystem. A catalog element defines the rules and boundaries of a specific plan type: scenario, periodicity, analytics (items / item groups / managers / partners / warehouses / organizations), data entry method, and unit of measure for planned indicators (quantity, amount in tenge ₸). When creating a "Sales Plan" document (procurement, assembly), the user selects a plan type from this catalog, and the plan type settings control the composition and filling of the document.
The catalog is a service (configuration) catalog, not an operational one: it does not itself generate business transactions and does not participate in tax calculations. Currency-denominated planned indicators are maintained in the national currency — tenge (₸).
2. Header attributes and tabular sections
Below is the typical composition of attributes for the service classifier catalog of plan types in edition 3.4. In a specific build, the set of attributes may differ — verify via Configurator (see "Extension points" section).
2.1. Standard attributes
| Attribute | Type | Purpose |
|---|---|---|
Код |
String/Number | Unique element code, auto-numbering |
Наименование |
String | Plan type representation in lists and documents |
ПометкаУдаления |
Boolean | Deletion mark flag |
Предопределённый |
— | Some plan types may be predefined by the configuration platform |
2.2. Header attributes (plan type settings)
| Attribute | Type | Purpose |
|---|---|---|
Наименование |
String | Plan type name ("Sales Plan by Managers", "Procurement Plan by Warehouses", etc.) |
Сценарий / ВариантПланирования |
Reference / Enumeration | Planning scenario (main, optimistic, pessimistic) |
Периодичность |
Enumeration | Plan step: day / week / ten-day period / month / quarter / year |
ЕдиницаИзмеренияПлана |
Enumeration | Unit of measure for indicators: quantity, amount (₸), quantity and amount |
Валюта |
Reference Справочник.Валюты |
Currency for amount indicators (default — tenge ₸) |
ДетализацияПоНоменклатуре |
Enumeration / Boolean | Analytics level: item / item group / item type / no detail |
ДетализацияПоПартнёрам |
Boolean | Maintain the plan by partners/customers |
ДетализацияПоМенеджерам |
Boolean | Maintain the plan by managers |
ДетализацияПоСкладам |
Boolean | Maintain the plan by warehouses |
ДетализацияПоОрганизациям |
Boolean | Maintain the plan by organizations |
СпособЗаполнения |
Enumeration | Manual entry / based on prior period sales data / by formula |
Комментарий |
String | Free-form description of the plan type |
2.3. Tabular sections
For a classifier catalog, tabular sections are generally not provided, or service tabular sections for settings are used (e.g., НастройкиДетализации — list of enabled dimensions, ИсточникиДанных — auto-fill rules). If no tabular sections exist, all settings are stored in header attributes.
3. Forms
| Form | Type | Purpose |
|---|---|---|
ФормаСписка |
List form | View and filter the list of plan types; opened via e1cib/list/Справочник.ВидыПланов |
ФормаЭлемента |
Item form | Create/edit settings for a single plan type |
ФормаВыбора |
Selection form | Selecting a plan type in planning documents and reports |
| Auto-generated | — | If no custom forms exist, the platform generates list/item/selection forms automatically |
4. Key module procedures
The attached evidence does not include a facet with BSL code (paths/lines) — only the naznachenie facet is present. Therefore, listed below are typical handlers for a service catalog of this kind; specific module lines should be verified via Configurator.
Item form module:
ПриСозданииНаСервере— initial form setup, setting the availability of detail attributes depending on periodicity and unit of measure.ПриИзмененииЕдиницаИзмеренияПлана/ПриИзмененииПериодичность— control field availability (e.g., hiding currency for a quantity-only plan).ОбработкаПроверкиЗаполнения— validation of setting combinations correctness (e.g., currency required for an amount-based plan).
Object module:
ОбработкаЗаполнения— filling default attributes when creating a new plan type.ПередЗаписью— consistency check for detail settings.ПриКопировании— adjustment of settings when copying an existing type.
Manager module:
- Procedures for programmatically creating predefined plan types and retrieving settings by reference (used by planning documents).
Requires verification: the presence and exact signature of the listed handlers depend on build 3.4.5.21 — verify via Configurator.
5. Posting and register movements
The catalog is not a posted document — catalog elements are not posted and do not independently generate register movements or accounting entries.
The catalog's role in the accounting circuit is that of a dimension (analytics) for planning documents and registers. The selected plan type appears:
- in the "Sales Plan", "Procurement Plan", "Assembly (Disassembly) Plan" documents as a setting attribute;
- in planning accumulation registers (e.g.,
РегистрНакопления.ПланыПродаж/ПланыЗакупок) as a "Plan Type / Scenario" dimension.
Actual register movements and accounting entries are generated by operational documents, not by the catalog. For reference, the standard Kazakhstan chart of accounts used by related operational documents (sales/receipts), not by this catalog:
| Account | Purpose |
|---|---|
| 1210 | Short-term accounts receivable from customers |
| 1030 | Cash in current bank accounts |
| 1330 | Goods |
| 3310 | Short-term accounts payable to suppliers |
| 3130 | VAT payable (VAT rate in Kazakhstan from 2026 — 16%) |
| 6010 | Sales revenue |
| 7010 | Cost of sales |
Kazakhstan electronic documents (ESF in the ESF IS, SNT) are generated by operational sales/transfer documents and are not related to the "Plan Types" catalog.
6. Related objects and entry based on
Used in objects:
- Planning documents:
Документ.ПланПродаж,Документ.ПланЗакупок,Документ.ПланСборки(as a plan type selection attribute). - Planning registers — "Plan Type" dimension.
- Planning subsystem reports: "Plan-Fact Analysis of Sales/Procurement", "Plan Fulfillment" — selection and grouping by plan type.
- Automatic plan generation processing — "Plan Type" parameter.
Related catalogs: Сценарии (planning options), Валюты, Номенклатура/НоменклатурныеГруппы, Партнёры, Пользователи/Менеджеры, Склады, Организации — used as detail dimension values.
Entry based on. For a service classifier catalog, the "entry based on" mechanism is generally not configured: elements are created manually in the list/item form or are predefined. The reverse scenario — selecting an element of this catalog when entering planning documents.
7. Extension points
- Attributes and tabular sections. Adding custom detail attributes (e.g., an additional "Project" or "Business Line" dimension) via a configuration extension without removing support status.
- Form handlers. Subscribing to/overriding
ПриСозданииНаСервере,ОбработкаПроверкиЗаполненияin an extension for additional settings compatibility checks. - Manager module. Adding functions to retrieve pre-configured plan types for custom auto-fill processing.
- Predefined elements. Ability to add custom predefined plan types (keeping in mind that the set of predefined elements may change when updating the standard configuration).
- Roles and RLS. Restricting access to specific plan types via roles and RLS settings of the planning subsystem.
Requires verification: the exact composition of attributes, presence of tabular sections and custom forms are version-dependent; verify against the specific 3.4.5.21 build in Configurator.