List of values of accumulation registers 1s. Remains and turnovers. Accumulation register measurements

Accumulation registers in the 1C:Enterprise system are divided into two types: accumulation registers leftovers and accumulation registers rpm.

The register type is selected when creating it in the configurator

As the name suggests, some are intended to obtain balances as of a certain date, and the second are intended to obtain turnover for a selected period. Depending on the type of accumulation register, the 1C:Enterprise platform generates a different set of virtual tables. In this article we will look at working with virtual tables of accumulation registers. To do this, we will create a register for accumulating balances - ProductsRemains and the revolution accumulation register - ProductsTurnover.

Now let's look at what virtual tables the platform provides for each of these registers.

Revolution accumulation register

For clarity, let’s open and see which tables are available for the register ProductsTurnover. This is the table of the register itself - ProductsTurnover, which exists physically in the database, and one virtual table - ProductsTurnover.Turnover

With the standard table everything is clear. Let's take a closer look at the virtual one.

Virtual table Turnover

This table allows you to obtain resource turnover in terms of dimensions. In our case we have two dimensions: Stock And Product. And one resource - Quantity

Let our register have the following entries

Let's go back to the query designer and start by simply selecting from the table ProductsTurnover.Turnover all fields

Accordingly, the request will look like this:

SELECT ProductsTurnoverTurnover.Warehouse, ProductsTurnoverTurnover.Product, ProductsTurnoverTurnover.QuantityTurnover FROM RegisterAccumulation.ProductsTurnover.Turnover(,) AS ProductsTurnoverTurnover

The result of the query looks like this:

That is, we received turnover in terms of goods and warehouses for the entire time. Let's assume that we are not interested in warehouses and we want to get turnover only in terms of goods.

To do this, we exclude the dimension from the request Stock

SELECT ProductsTurnoverTurnover.Product, ProductTurnoverTurnover.QuantityTurnover FROM RegisterAccumulation.ProductsTurnover.Turnover(,) AS ProductsTurnoverTurnover

and as a result we will only have two lines left

But as a rule, there is no need to obtain turnover for the entire existence of the register. Basically, they are needed for a specific period: month, quarter, year, etc. Plus, selections by dimensions (Product, Warehouse) are usually needed. This is achieved using virtual table parameters. It is convenient to fill in parameters from the constructor. By button Virtual Table Options A dialog box opens in which you can enter everything we need:

After this, our original request will take the following form

SELECT GoodsTurnoverTurnover.Warehouse, GoodsTurnoverTurnover.Product, GoodsTurnoverTurnover.QuantityTurnover FROM RegisterAccumulation.GoodsTurnover.Turnover(&Beginning of Period, &End of Period, Warehouse = &Warehouse) AS GoodsTurnoverTurnover

As we can see, the difference is that in parentheses after the name of the virtual table there are parameters that must be filled in before executing the query.

Those who are just starting to work with virtual tables are often tempted to set selection in the usual way instead of using parameters:

FROM RegisterAccumulations.ProductsTurnover.Turnover(,) HOW ProductsTurnoverTurnover WHERE ProductsTurnoverTurnover.Warehouse = &Warehouse

When filling out the parameters we missed Periodicity. Let's open the list and choose from the mass of possible options Month. We will remove all other parameters so as not to get confused.

After this, we observe that a field appears in the table fields Period.

By adding it to the selected fields, we get the following request text:

SELECT ProductsTurnoverTurnover.Period, ProductsTurnoverTurnover.Warehouse, ProductsTurnoverTurnover.Product, ProductsTurnoverTurnover.QuantityTurnover FROM RegisterAccumulation.ProductsTurnover.Turnover(, Month,) AS ProductsTurnoverTurnover

We execute the request:

Thus, within the selected time interval, we can divide the revolutions into smaller intervals in accordance with the selected frequency.

Balance accumulation register

Just like with the reverse register, let’s look in the query designer which virtual tables are available for the balance accumulation register

As you can see, three virtual tables are available for the balance accumulation register: Revolutions, Leftovers, Remains and Turnovers. Let's consider each of them separately.

Virtual table Turnover

Despite the fact that the register type is Leftovers, we can nevertheless receive turnover from it. Plus we have two additional resources here: Coming And Consumption

Let me remind you that when an entry is made in the balance register, the type of accumulation movement (income or expense) is indicated, whereas for the turnover register the type of movement is not indicated. Therefore, here we have an additional bonus in the form of the opportunity to receive not only the overall turnover for the period, but also income and expenses separately. But of course, if the metadata contains a reverse register with a similar set of measurements, then it is better to use it to obtain turnover. In general, working with this virtual table is similar to working with a virtual table Revolutions the negotiable register discussed above.

Virtual table Balances

This table is used to obtain resource balances by dimension. In the table parameters we can specify the date for which we receive balances and set selections:

Let's look at a small example. We have the following register entries:

Let's select all available fields and set the end of June as the date for receiving balances. We will not select based on measurements. Then the request text will look like this:

SELECT ProductsRemainingsRemainings.Warehouse, ProductsRemainingsRemainings.Product, ProductsRemainingsRemainings.QuantityRemaining FROM RegisterAccumulations.ProductsRemainings.Remainings(&DateRemainings,) AS ProductsRemainingRemainings

And after executing it we get this result

Virtual table Balances and Turnovers

This table combines the two previously discussed ones and allows you to obtain turnover for the selected period of time, as well as balances at the beginning and end of the period. You can also set selection.

The use of this table can be justified when you need to simultaneously obtain both turnover and balances at the beginning and end of the period in one report. In other cases, you should not abuse its use.

Object 1C "Accumulation Registers" - these are applied objects that form the basis of the mechanism for accounting for the movement of funds (finance, goods, materials, etc.), designed for storing operational accounting indicators and allow you to automate such areas as warehouse accounting, mutual settlements, and planning.

In other words, these are application configuration objects that allow you to quickly record and store movements of any assets or liabilities of an enterprise.

The accumulation register is a table with information that collects all certain movements (receipts, write-offs or turnover).

The accumulation register forms a multidimensional measurement system and allows you to “accumulate” numerical data in the context of several dimensions. For example, in such a register you can accumulate information about product balances by product line and warehouse, or information on sales volumes by product line and company division.

Residual register(Residues) stores movements, and also, based on them, the remainders after each movement. Residual accumulation registers are used, for example, to record goods in warehouses.

Negotiable register(Revolutions) stores movements without indicating their direction, and does not imply separate storage of residues. An example of using a negotiable register is recording data on an enterprise's revenue.

From the point of view of the tabular model, the accumulation register contains:

measurements;
resources (can be either numeric or definable);
requisites.

When forming the structure of the accumulation register, a registrar must be appointed, and at least one resource must be created.

[collapse]

A mandatory attribute of the accumulation register is “Period”, and the frequency cannot be adjusted - records are stored accurate to the second. The information stored in the accumulation register is always linked to the time axis.

When writing data to the accumulation register, the “Period” must not be empty. “Period” is a standard detail that must be filled out.

Standard details of the 1C accumulation register are available on the "Data" - "Standard Details" tab.

Period- the date of movement does not have to coincide with the date of the document;
Registrar- a document that makes an entry in the register;
Line Number- serial number of the line in the record set, unique within the registrar;
Activity- is responsible for getting records into virtual tables (a quick way to obtain profile information from registers); cannot be set for each entry individually within the record document (the minimum for a set of records can be set);
ViewDvisions- income or expense.

Uniqueness of records of the 1C object "Accumulation registers"

The system provides control over the uniqueness of records stored in the accumulation register. Thanks to this, the accumulation register cannot contain two entries relating to the same line of the same document.

Uniqueness of entries in the accumulation register movement table determined by the "Registrar" and "Line number" fields.

[collapse]

Accumulation registers are always subordinate to the document registrar. Therefore, among their standard details there is always " ".

Functionality of the 1C accumulation register

The main functionality that the accumulation register provides to the developer is:

selecting records in a given interval according to specified criteria;
selection of records by registrar;
obtaining balances and turnover at a specified point in time based on specified measurement values;
mode of operation with division of totals, which provides higher parallelism of writing to the register;
disabling the use of running totals;
calculation of results for the specified date;
reading, modifying and writing a set of records to a register;
the ability to write to the register without recalculating the results;
a complete recalculation of the results and a recalculation of the results for the specified period.

For accumulation registers, the totals separation mode can be enabled:

If separation is enabled, then an additional column with a value of the “Number” type will be added to the register totals table, which will act as a separator for the remainder of the data in the event of simultaneous writing to the register by two documents.

[collapse]

Structure of the 1C object "Accumulation Registers"

Information in the accumulation register is stored in the form of records, each of which contains:

measurement values (describe the sections in which information is stored);
the corresponding resource values (accumulate the necessary numerical quantitative data).

An accounting section can be, for example, warehouse, item, product characteristics, product series, quality.

By specifying the measurements we are interested in, we can obtain the quantity - resource - at any time.

In the context of different dimensions, in the future, for example, you can obtain balances for a specific date.

Design features of the accumulation register:

Above all, it is necessary to put the measurements that will be most often requested in the system;
property "Index" accumulation register measurements must be set to measurements in cases where it is planned to frequently apply selections for the measurement when obtaining data and this measurement can have a large number of variants of value. For example, we have a register “ProductsInWarehouses” (dimensions “Warehouse, Nomenclature”, resource - “Quantity”). It is more correct to index the “Nomenclature”, but the “Warehouse” field should not be indexed, since the number of warehouses in the system, as a rule, is not significant.

Accumulation Register Entry Set

This is a collection of its strings (records) existing in the computer's memory.

A set of records is always associated with a specific record document (i.e. determined by the registrar document), since there cannot be independent accumulation registers. Operating with a set of records, you can read this data from the database, delete it, change it, and add it under certain conditions. When writing, it usually replaces all records available in the database for a given condition with the records contained in the set. If records are not replaced, then the set is cleared after the write is completed.

The maximum number of records in a set is 999,999,999.

Accumulation Register Entry Setcan be used:

to change accumulation register entries for a specific registrar;
to add accumulation register entries for a specific registrar;
to delete accumulation register entries for a specific registrar;
to read a set of records for a specific recorder.

Important! Selection can only be based on equality.

Since the accumulation register is used to accumulate numeric values, each entry makes a change to the stored resources - movement. Movements, in general, can either add some increments to stored resources or subtract them:

parish movement(“+”) - if an increase in stored resources should be performed;
flow movement(“-”) - if a reduction of stored resources should be performed.

Along with each entry in the accumulation register, additional arbitrary information can be stored. The accumulation register details are used for this purpose.

The required standard requisite for the accumulation register is the registrar.

[collapse]

Registrar - this is a document during which register entries are generated (i.e. it is a document that can make movements in the accumulation register).

Records are only meaningful if the recorder exists; When deleting a record document, the records will also be deleted.

The list of registrar documents is specified on the corresponding “Registrars” tab of the window for editing the “Accumulation Register” configuration object.

Figure "Recorders" tab of the window for editing the configuration object "Accumulation register"

[collapse]

However, you can programmatically make a record without a recorder document (but it still assumes that there is a recorder). Also, the creation of records can occur not only during events, but also for some other events; there are no strict restrictions here.

Most algorithms for creating movement in the accumulation register are formed when posting a document (procedure “Processing Posting”).

Connection of the 1C object "Accumulation registers" with the registrar

A change in the state of the accumulation register usually occurs when a document is posted. Therefore, each register entry is associated with a specific document - the registrar, the line number of this document, and the date - period.

[collapse]

In general, the value of the "Period" field may not coincide with the document date. For example, the Sales Plan document can record the company's expected sales on several different dates in the accumulation register.

The composition of documents that can create entries in the accumulation register is specified by the developer during the creation process.

[collapse]

Features of working with registrars when processing documents:

Entries in the accumulation register can be formed:
- when carrying out a document;
- when recording a document;
- when filling out the document.
Mandatory condition in relation to the Registrar when recording data in the accumulation register: The record document must be recorded. Until the document is recorded, there is no link to it in the system, and the link must be indicated in the "Registrars" field.
The "Registrars" field can contain a non-empty link only to the registrar document(type controlled).
Type field data "Registrars" determined on the "Registrars" tab in the configuration object editing window.
For the "Registrars" field, you can define the typeDocumentLink.<ИмяДокумента>. WITH The list of recorder types is quite specific (screenshot above).
Things to remember:
- one accumulation register can be associated with any number of document types;
- one document type can be associated with any number of accumulation registers;
- when deleting a document-recorder, records are automatically deleted from the database;
- records may exist without the presence of a record document when using an exchange plan, which may lead to to violation of referential integrity information base.
The date of the registrar's document is in no way related to the period of the register. The date of the register entry is determined programmatically and can either coincide with the date of the document or be completely different.

1C object movement designer "Accumulation registers"

The algorithms by which register entries are generated are described using the built-in language in the procedures of the corresponding documents. The system contains, which helps the developer create algorithms for document processing.

Balance registers and turnover registers

There are two types of accumulation registers:

balance accumulation registers(stores the total values of resources - balances);
revolution accumulation registers(stores only changes in these resources - revolutions).

The existence of a register for accumulating turnover is due to the fact that when automating economic activities, there are a large number of situations when it is only necessary to accumulate turnover, and the values of the balances do not make sense. A typical example of using a turnover accumulation register is the “Revenue and Cost of Sales” register, which stores information about sales volumes.

Since the turnover accumulation register does not accumulate the remaining resources, the “direction” of the movement of resources (income or expenditure) does not make sense for it; Only the amount of change in resources is accumulated. Therefore, all entries in the revolution accumulation register are marked with the same icons.

Units of registers for accumulating revolutions

For negotiable accumulation registers, the platform supports a special aggregate mechanism, which can significantly speed up the retrieval of data from registers containing a large number of records - hundreds of thousands and millions of records.

Aggregates- this is a special mechanism implemented in circulating accumulation registers and allows to significantly reduce the time for generating reports.

Each aggregate is a specialized storage containing aggregated register data in various sections, convenient for generating reports in this information base. The system automatically evaluates the intensity of users’ work with certain sections of information and, based on accumulated statistics, selects the optimal composition of supported aggregates.

The use of aggregates allows analysts and managers to analyze available information by switching between different viewing views with a short system response time. At the same time, the system uses accumulated aggregated data and always ensures that the reports received are up to date.

Multiple aggregates can be created for any register.

The platform contains a special one, with which you can change the composition of units and configure their use.

The aggregate designer can be called from the window for editing the circulating accumulation register (the "Data" tab).

List form and record set form of the 1C object "Accumulation registers"

In order for the user to view the data contained in the accumulation register, the system supports the following views of the accumulation register:

accumulation register list form- allows you to sort and select the displayed information according to several criteria; the system can automatically generate this form;
accumulation register record set form- allows you to add, change and delete entries.

Along with this, the developer has the opportunity to create his own (custom) forms, which the system will use instead of the default form.

The task of any accounting system is to store and promptly display information for the user, i.e. The goal of any system design is to promptly provide the user with a report. With the help of the data obtained, as a rule, management decisions are made at enterprises.

Let's assume that we have 1000 different documents: receipt of goods, write-off, return, sale, etc. And each of the documents changes the quantity of a certain product in the warehouse. To get information about the current quantity in the warehouse, you need to go through everything: some increase the quantity of goods, some decrease, some can increase or decrease. And if it is also necessary to take into account the warehouse, the organization?.. Such a system is very resource-intensive.

To simplify this process, 1C developers came up with special configuration objects. They are used for the convenience of storing and retrieving information; in 1C 8.3 and 8.2 all kinds of registers are used; in this article we will talk specifically about Accumulation registers.

The accumulation register itself is a table with information that collects all movements (receipts/write-offs or turnover) of certain documents. Let's look at what the movement table looks like using the example of a typical accumulation register “Goods in warehouses” in the “Trade Management 10.3” configuration:

Here we see that 1C “Sales” documents reduce the quantity of a certain product in a certain storage location, and receipt documents, on the contrary, increase the quantity. As a result, we get an overall picture in which we can clearly see what, when and in what quantity was received (written off) according to accounting. It is much more convenient to build a report using such a table.

Accumulation register in the configurator

What is an accumulation register from the point of view of configuration development? Let's start by looking at the fields of the accumulation register in:

Get 267 video lessons on 1C for free:

The accumulation register has Dimensions, Resources, Details and Standard details.

Let's first consider the standard details of the accumulation register:

period— the date of movement does not have to coincide with the date of the document;
registrar- a document that makes an entry in the register;
line number— serial number of the line in the record set, unique within the registrar;
activity— is responsible for getting records into virtual tables (more about them below);
viewmovement- income or expense.

Accumulation register measurements

A dimension is a section in which records are kept. In the above example, the accounting section is: warehouse, nomenclature, product characteristics, product series, quality. That is, by specifying the measurements we are interested in, we can obtain the quantity—resource—at any time. In the context of different dimensions, in the future, for example, you can obtain balances for a specific date.

Accumulation register resource

A resource is a numeric field in which information is stored in the context of the dimensions described above.

Otherwise, the interactions of dimensions/resources can be schematically depicted as a coordinate system:

Two dimensions - abscissa and ordinate of the coordinate system, i.e. in this example, the dimensions are warehouse and item. At the intersection of dimensions we can get a quantity - a resource. For example, at the “main” warehouse of the product “pencil” there is 1 piece in stock.

Details of the accumulation register 1C

Accumulation register details serve as a “comment” or additional information; in terms of measurements, balances/turnovers cannot be obtained. Used quite rarely.

Types of accumulation register

There are two types of accumulation register − turnovers and balances.

If the purpose of the accumulation register is not to obtain balances, it is necessary to use the type of accumulation register - rpm. A typical example of using a turnover register is recording sales volumes. In this case, we only need to know what sales were over a certain period of time; balances in this case do not make sense.

If the purpose of using the accumulation register is to obtain balances for a certain period, we need a register with the form leftovers. This type allows you to receive both balances and turnover. For such a register, the system automatically calculates balances. An example of a “residual” register is goods in warehouses, money in the cash register.

Using a register type leftovers where you can get by rpm, is considered a blunder in the design of the accumulation register from a system performance perspective.

Depending on the type of register, the system will create different virtual tables for the accumulation register. A virtual table is a quick way to obtain profile information from registers.

For the accumulation register it is:

Leftovers;
Revolutions;
Remains and turnovers.

For the solution developer, the data is taken from one (virtual) table, but in fact the 1C platform takes it from many tables, transforming them into the required form.

Proper design of accumulation registers

Accumulation registers must be designed from the required reports. The most difficult thing in the 1C 8.3 system is storing information correctly so that it can be easily retrieved at any time.

Among the features of register design, it should be noted the need to correctly arrange the dimensions in the register. Above all, you need to put the measurements that will be requested most often in the system.

Indexing accumulation register dimensions

Accumulation register measurements have the property of “indexing”. This property must be set to measurements in cases where it is planned to frequently apply selections to the measurement when receiving data and this measurement can have a large number of value options.

For example, the register is “ProductsInWarehouses”, the dimensions are “Warehouse, Nomenclature”, the resource is “Quantity”.

It is more correct to index the “Nomenclature”, but the “Warehouse” field should not be indexed, because the number of warehouses in the system, as a rule, is not significant.

In any configuration of 1s 8.2 you can see this type of objects as registers. Their main purpose is to optimize data acquisition for reports. There are four types of registers: information registers, accumulation registers, accounting registers and calculation registers. And although these types are intended to solve different problems, just by the fact that they are all called “registers” one can guess that they also have something in common.

Firstly, as already mentioned, as configuration objects they are needed to more quickly read information from the database, for example in queries. The registers can be compared to a book library catalog (previously they were compiled on paper cards). That is, this is not only the storage of information (data), but also its systematization (creation of a certain structure), when data enters a specific register (for example, from documents of various types) and, if necessary, it can be quickly retrieved from there and displayed, for example, in report or otherwise process. In general, the main use of registers in 1C can be illustrated by the following scheme: “Document - Register - Report”, although there are exceptions.

Secondly, all registers, regardless of their type, have resources, dimensions and details. That is, it is determined What(resource) in what sections(measurements) need to be taken into account. Applicable to the library - we take into account books by author, genre and publisher. And with the help of details you can supplement the information, for example, with the year of publication. And here there is one important point - the structure of the register must be determined very carefully, depending on what information we are going to extract from it. For example, if in our library the search is most often carried out by the author’s last name, the card should first contain the author (the first dimension), and only after that should the genre (the second dimension).

Third, registers have a table structure, but it differs from the structure of object tables. So you won't find classes like RegisterReference or RegisterObject. The composition of the register table depends on its properties.

Fourthly, data is written to registers in the form of sets of records. Each set consists of one or more records. However, the record in the set cannot be referenced or accessed. And neither a set of records nor a record in a set can have a “mark for deletion” state.

Fifthly, when accessing registers in queries to obtain data, it is possible to access not only the physical register tables, but also virtual tables, which are a nested query that obtains data based on certain parameters. The virtual table parameters are set depending on the specific needs for obtaining data from register tables.

Now let's talk about the features of each type of registers:

1. Information registers

Perhaps the simplest type of register. Unlike other types of registers, its resource can be named not only as a numeric value, but also as another data type.

It has a special property that is not used in other types of registers - periodicity.

It may not have a registrar, that is, be independent; in this case, entries are made directly into the register, bypassing the registration document (this is the very exception to the general scheme of using registers in 1c). Whereas other types of registers must have at least one document-recorder.

In addition, this type of register has automatic control of the uniqueness of records by period (frequency specified in the register properties) and dimensions. That is, among the register entries there cannot be more than one entry with the same indicators period + measurement + recorder (if there is one). The uniqueness of records in other types of registers is determined by the registrar.

2. Accumulation registers

Designed to accumulate numerical indicators (resources) and is divided into two subtypes - Remains and Turnovers. The difference between them is that the Accumulation Register Balances is intended to obtain information about the state “at a point in time,” and Turnovers is intended to obtain information about data “for a period.”

The accumulation register data is stored in the database in the form of two tables - a movement table and a totals table. Direct access is only possible to the motion table.

3. Accounting registers

It is similar to an accumulation register, but is designed to systematize data on accounting entries. However, it can be used not only for accounting, but also for any other type of accounting.

Its main feature is the ability to record data using the double entry method using the Debit-Credit principle. To implement the possibility of generating transactions, the Accounting Register must be associated with a special object - Chart of Accounts.

4. Calculation registers

This type of register is intended not only for storing, accumulating and systematizing data, but also for implementing complex mechanisms for periodic calculations. To do this, in the properties of the calculation register, you need to define another 1C object - a plan of calculation types. That is, the operation of a register of this type is impossible without defining a specific plan for calculation types for it.

We can say that the calculation register is used to store information about the types of calculations, and to store the results of calculations, and for intermediate values of calculations. Its main purpose in 1C configurations is to calculate accruals, for example, wages and other payments to employees. And to implement these tasks, when determining the parameters of the calculation register, it is possible to indicate in it a connection with a time schedule, which allows calculations to be made depending on the time specified in this schedule. The time schedule itself must be defined using the appropriate information register.

Thus, we can say that the calculation register ultimately has the most complex structure compared to other types of registers in 1s.

Report “Balances and Turnovers” created for receiving a statement of balances and turnover.

The statement is displayed in the form of a table with columns “Starting balance”, “Receipt”, “Expense”, “Final balance” and detailing columns.

This report can be built for any balance accumulation register present in the configuration.

Path: Reports – Universal – Balances and turnover

After opening the main report form, you need to do this, which can be done directly on the main form. In this case it is necessary:

in field " Accounting section" select the balance accumulation register for which you want to generate a report (selection is made from the proposed list);
in field “The period from ... to ....”— specify the period for which the report will be generated.

NOTE: if the field “The period from ... to ....” is left blank, the report will be generated for the entire period of operation of the system;

To generate a report in a form convenient for us, we configure it using the button “ Settings".
When using the button, you can configure the selection of data displayed in the report. ( In addition, selection can be configured on the “Selection"settings forms.)

By the button " Form" The report is generated in accordance with the current settings.

Button " Heading" allows you to get a more compact view of the report by hiding its header.

Also, the report can be initially configured using "Settings" buttons which will allow you to set all possible report parameters, incl. and those that are specified on the main form.

The form contains the following tabs:

Are common;
Groups;
Selection;
Fields;
Sorting.

On the bookmark "Are common" you can set the reporting period, select an accounting section, other general parameters and indicators.

As parameters suggested:

"Use Properties and Categories"— after checking the box, it becomes possible to select and group data by properties, select by categories of objects;
"Color the factions"— report groupings will be highlighted in different colors;
“Summarize all levels” - When grouping the report, total data for each group will be displayed.

"Index"— numerical values summarized in the report. These values are displayed in the columns “Begin Balance”, “End Balance”, “Income”, “Expense”.

“Output in different columns”— with the checkbox checked, each indicator will be displayed in a separate column; if the checkbox is unchecked, the indicators will be displayed one below the other.

On the bookmark Groups You can customize the report detail:

— Grouping lines will contain the total values of the selected indicators;

— Type of totals determines whether additional hierarchical groupings need to be added to the report

The system offers the following types of data grouping:

Elements– generating a report on the elements that are included in the selected accumulation register

Hierarchy— generating a report on groups that include elements,

Hierarchy only used only if totals for elements are not needed, but only totals for groups are needed

— To build a report by groups, you need to select a characteristic by which the report will be detailed. For this it is necessary to Row Grouping add grouping view from popup window "Field Selection".

On the bookmark "Selection" data, conditions for generating a report are established

Each line specifies one selection element containing:

Field, the values of which are subject to selection conditions.
Checkbox for using selection element . Allows you to easily disable and enable individual selection elements without removing or adding elements.
Comparison type– selection condition for which the report will be generated.

The system offers the following comparison types:

Equals— the report will be built only on the selected attribute;

Not equal— the report will be based on all characteristics except the selected one;

On the list— the report will be based on a list of features;

Not on the list— the report will be based on all characteristics, except for those that were selected;

In Group— the report will be built based on all the characteristics located in the selected folder from the corresponding directory.

Not in group— the report will be built based on all characteristics, except for items located in the selected folder from the corresponding directory.;

In a group from the list— similar to comparison In the list, only several folders from the corresponding directory are selected as list values;

Not in a group from the list- similar to the comparison Not in the list, only several folders from the corresponding directory are selected as list values.

Meaning, values are indicated to determine the selection conditions for entering the interval, which is specified by two values - the boundaries of the interval. If a condition is imposed on being in a list, the comparison values are specified by a list of values.

On the tab " Fields" You can specify a list of fields to be displayed in the report. By default, if the list is empty, the fields selected in the grouping list are displayed in the report.

The fields display additional information that will be displayed when generating the report in columns.

On the tab " Sorting" You can set the order in which report lines will be displayed.

Each line specifies the field and sort order. If sorting is not specified, then automatic ordering is used (character strings - alphabetically, numbers - ascending, etc.). Indicator fields can be selected as ordering fields, which allows you to sort report lines in descending or ascending order of the indicator.