1. Identification
| Parameter | Value |
|---|---|
| Object type | Report (Отчет) |
| Name | АнализПервичногоИнтереса |
| Full identifier | Отчет.АнализПервичногоИнтереса / Reports.АнализПервичногоИнтереса |
| Synonym | “Initial Interest” |
| Configuration | Trade Management for Kazakhstan, rev. 3.4.5.21 |
| Location in the interface | “Service Subsystems” section → “Initial Interest” |
| Navigation link | e1cib/list/Отчет.АнализПервичногоИнтереса |
Purpose. The report belongs to the configuration’s marketing analytics module and is intended to assess initial interest—the first contact between a potential customer and the company: inquiries, initial applications and deals, acquisition sources, and subsequent conversion into orders and sales. The report reads accounting data from the registers and catalogs available to it and presents the results in tabular form with groupings.
An object of the “Report” type in platform 8.3 is used to present and analyze data. The result can be generated using the Data Composition System (DCS) based on parameters, filters, and groupings set by the user.
2. Attributes and Structure
A DCS report does not have tabular sections or header attributes in the sense in which they are used in documents. Its structure is defined by the data composition schema, datasets, parameters, and settings of the selected report variant. The functional composition corresponding to the report’s purpose is provided below.
2.1. Composition Parameters (Equivalent to Header Attributes)
| Parameter | Type | Purpose |
|---|---|---|
| Период / НачалоПериода, КонецПериода | Date / standard period | Analysis interval for initial inquiries and deals |
| Организация | СправочникСсылка.Организации | Filter by accounting organization |
| ИсточникПривлечения | СправочникСсылка.ИсточникиПривлеченияКлиентов | Initial-interest channel or source |
| ВидСделки / Этап | СправочникСсылка / Перечисление | Restriction by funnel types and stages |
| Ответственный / Менеджер | СправочникСсылка.Пользователи | Filter by responsible person |
| Валюта | СправочникСсылка.Валюты | Currency in which amounts are presented; ₸ is used for tenge |
2.2. Dataset Fields/Resources (Equivalent to Tabular Sections)
| Field | Purpose |
|---|---|
| Partner / Customer | Counterparty or partner who expressed initial interest |
| Acquisition source | First-contact channel specified in the source data |
| Initial inquiry date | Date on which the registered interest arose |
| Number of initial inquiries / deals | Number of objects included in the corresponding report grouping |
| Potential / deal amount (₸) | Monetary valuation of the registered deal or its potential |
| Sales amount (₸) | Sales amount associated with the analyzed inquiries or deals |
| Conversion, % | Ratio of the number of inquiries that reached the target stage to the total number of initial inquiries |
The actual list of available fields is determined by the DCS schema in build 3.4.5.21 and the selected report variant. It can be viewed in the settings form: the platform does not offer fields that are absent from the current dataset for selection, grouping, or filtering.
3. Forms
A compact set of forms is used for the DCS report:
| Form | Purpose |
|---|---|
| ФормаОтчёта (main) | Entering parameters and filters, selecting a variant, executing the “Generate” command, and displaying the result in the spreadsheet document field |
| DCS settings (built-in) | User configuration of filters, groupings, fields, and formatting, as well as work with available report variants |
Separate record, list, and selection forms typical of catalogs and documents are not used for the report. The main form supports work with parameters and results, while the platform provides standard DCS configuration capabilities.
Before generating the report, the user selects a period and, if necessary, specifies the organization, acquisition source, responsible person, or other available filters. After changing the settings, the report should be generated again so that the spreadsheet document reflects the new conditions.
4. Key Module Procedures
The object module code is not included in the description. For a technical review of the DCS report, the following standard processing points are relevant if they are implemented in the configuration:
- ПриКомпоновкеРезультата(ДокументРезультат, ДанныеРасшифровки, СтандартнаяОбработка) in the object module—the handler in which the developer can control result composition, output settings, calculated values, and formatting.
- ПриСозданииНаСервере(Отказ, СтандартнаяОбработка) in the form module—the handler that initializes the form, parameters, and user settings when it is opened.
- Form field change handlers—used to respond to changes in the period, organization, acquisition source, and other available conditions.
- “Generate” command—starts building the result based on the current variant, parameters, and filters.
- Drill-down processing—provides details for an indicator or navigation to a related object when such drill-down is included in the report schema.
If the object module does not contain a custom composition handler, the result is generated according to the declarative DCS settings. The presence of the ПриКомпоновкеРезультата handler is determined from the object module in the configurator for build 3.4.5.21. The procedure parameters and sections of the report’s programmatic configuration can also be viewed there.
When maintaining an extension, it is important to distinguish between standard DCS settings and programmatic processing. Fields, groupings, and filters are usually changed in the report variant, while code is used for logic that cannot be expressed through schema settings.
5. Data Sources (Instead of Posting and Register Entries)
The report obtains information from infobase objects included in its datasets. Initial-interest analysis uses CRM and sales data in the composition provided by the DCS schema of the specific build.
- CRM data: information on customer deals, interactions, deal statuses, and acquisition sources.
- Sales data: information on orders and sales used to compare initial interest with the achieved result.
For accounting interpretation of sales amounts in the accounting database, the following accounts from the standard chart of accounts of the Republic of Kazakhstan may be used:
| Account | Purpose |
|---|---|
| 1210 | Short-term trade receivables |
| 1030 | Cash in current bank accounts |
| 1330 | Goods |
| 3310 | Short-term trade payables |
| 3130 | VAT payable |
| 6010 | Sales revenue |
| 7010 | Cost of sales |
Applicable values in the Republic of Kazakhstan for 2026:
- VAT rate—16%;
- MCI—4 325 ₸;
- minimum wage—85 000 ₸;
- basic personal income tax deduction—30 MCI.
Interpretation example: if the sales amount excluding VAT is 1 000 000 ₸, VAT at the rate of 16% is 160 000 ₸, and the total amount including VAT is 1 160 000 ₸. When analyzing the indicator, it is important to understand which amount is displayed in the selected report variant: excluding VAT, including VAT, or in another presentation defined by the DCS resource.
Electronic document workflow in the Republic of Kazakhstan. Sales-related documents may be accompanied by electronic invoices (ESF) and accompanying notes for goods (SNT). The display of electronic document attributes or statuses is determined by the dataset fields and the report variant settings.
The reported indicator should be compared with its drill-down. The same column name in different variants may correspond to a different data composition, such as the order amount, sales amount, or an amount calculated from related objects.
6. Related Objects and Create Based On
Related objects serve as data sources and report drill-down targets:
- Catalogs: partners, counterparties, customer acquisition sources, users, organizations, and currencies.
- CRM objects: customer deals and registered interactions—calls, meetings, and emails.
- Sales documents: customer order, sale of goods and services—as objects reflecting a subsequent stage of work with customer interest.
- Electronic documents: electronic invoices (ESF) and accompanying notes for goods (SNT), if their attributes are included in the dataset or available through drill-down.
- Other analytical reports: sales funnel and assessment of acquisition source effectiveness, if provided by the configuration.
Navigation to a related object is performed from the indicator drill-down when the corresponding fields are configured in the DCS schema. The availability of navigation also depends on the user’s permission to read the object.
7. Extension Points
- Configuration extension: adding a custom DCS variant, additional fields and groupings, and attaching handlers with &Вместо, &После, or &Перед annotations.
- User DCS settings: saving available variants and configuring filters, conditional appearance, and the grouping structure without changing the object metadata.
- Additional reports: connecting an external report with a similar purpose through the additional reports and data processors mechanism provided by the configuration.
- Source extension: adding the required fields and datasets to the schema while accounting for relationships, parameters, and access restrictions.
- Drill-downs and navigation: configuring indicator details and navigation to a deal, partner, order, or sales document.
The composition of built-in report variants and its module code are determined by build 3.4.5.21. For customization, use the variant tree and the object’s data composition schema: they display the available datasets, relationships, parameters, resources, calculated fields, and drill-down settings.
When adding a field in an extension, it should be aligned with the existing filters and groupings. If the field is obtained by joining several datasets, the relationship cardinality must be controlled to prevent source data rows from being duplicated and totals from increasing.
Questions and Answers
How can I determine which data was used to calculate an indicator?
Open the cell drill-down and the settings of the current variant. The settings show the selected fields, filters, groupings, and resources, while the drill-down shows the rows included in the total.
Why did the result change after selecting a different report variant?
DCS variants may differ in their fields, groupings, filters, calculated resources, and presentation of amounts. To compare results, use the same period, organization, and other filter conditions.
What should I check if an expected deal or sale is missing from the report?
Check the period, organization, acquisition source, responsible person, and other filters that have been set. Then open the source object and make sure that the attributes used to build the query contain values matching the report conditions.
How can I determine whether VAT is included in the amount?
Check the resource name and expression in the DCS schema or the result drill-down. For the example with a base amount of 1 000 000 ₸, VAT at the applicable rate of 16% is 160 000 ₸, and the amount including VAT is 1 160 000 ₸.
Can I save my own filters and groupings?
Use the user DCS settings and save the variant if the corresponding command is available in the form and the user’s permissions allow work with variants. The saved variant should be named so that its periodicity, analysis dimensions, and purpose are clear from the name.