Skip to main content
insightsoftware Documentation insightsoftware Documentation
{%article.title%}
Published:
Was this article helpful?
0 out of 0 found this helpful

Check Sums

Table of Contents

  • 1 Control Values

1 Control Values

What is a control value in IDL Konsis?

A control value (sometimes called check digit) is a sequence of 32 bits, which is represented in IDL Konsis as a 10-digit numeric value. When displayed in a column for amounts, two decimal places (".00") are added.

How is a control value formed?

The calculation of a control value in IDL Konsis is carried out according to the CRC-32 procedure. The relevant attributes of a set of data records are thus converted into a control value in their internal program presentation.

For what data are control values made?

  • For account balances and their details (IC and controlling balances, transactions, IC fixed asset transactions, IC holdings), control values are created per key combination <accounting period / fact / company / business unit>. These control values are saved in the table of the Processing control (overview VERARB).
  • One control value per voucher is set up for postings. This control value is saved in the document header (overview BEL).
  • For consolidation postings, one control value is formed per consolidation voucher. This control value is saved in the document header (overview KONBEL).
  • A separate control value is created for each currency (country/group/parallel currency). Rows with zero values are not included in the checksum calculation. Thus, for example, the control values for the local currency by the currency conversion remain unchanged.
  • Relevant attributes include account number, debit/credit indicator and amount as well as (depending on the table) posting key, IC-company, IC-business unit, controlling object, product/product group and/or fixed asset object. Since the company is also included, different control values arise for different societies, even if the values are identical.

How is the calculation of control values controlled?

Control values are now calculated as a matter of principle. Steering options are no longer provided for.

What are control values used for?

  • Control values are almost certainly a state of the data concerned. Any change to the relevant attributes will result in a change in control value.
  • The change of a control value in the VERARB table results in an entry in the change log of the Processing controls (overview VERARBLOG), so that it is logical when, by whom and by which application the data inventory was last changed.
  • When a report is created, the control value of the basic data to be included is saved (per currency) or a new report control value based on the same algorithm is created from the control values of the basic data (e.g. balances of several companies, several consolidation documents).
  • If a report is displayed (REP report overview or REPERG report display), this step is repeated and the control value determined is compared with the saved control value. Deviations are visualized by a message or by red cells in the control value state columns. They show a change in the basic data after the reporter was prepared.

Can control values be formed and compared in other systems?

Although the CRC-32 algorithm is a standard procedure that can be used in other systems, the control values calculated in IDL Konsis require some special prerequisites in order to achieve reproducible results:

  • For alphanumeric attributes, a special character set (IBM 850) is used.
  • Numeric values are available in special formats of the COBOL (BCD) programming language.
  • Since the sequence of the data is decisive, a certain sort must be observed.
  • In addition to the data transferred from pre-systems, there are also computational values (e.g. annual profit or loss, carries forward) in IDL Konsis, which are also included in the control value.

For these reasons, it is virtually impossible for control values to be created in pre-systems (e.g. accounting, Excel entry forms) or downstream systems and to be used for coordination with the control values in IDL Konsis.
Published:

Check Sums

Table of Contents

  • 1 Control Values

1 Control Values

What is a control value in IDL Konsis?

A control value (sometimes called check digit) is a sequence of 32 bits, which is represented in IDL Konsis as a 10-digit numeric value. When displayed in a column for amounts, two decimal places (".00") are added.

How is a control value formed?

The calculation of a control value in IDL Konsis is carried out according to the CRC-32 procedure. The relevant attributes of a set of data records are thus converted into a control value in their internal program presentation.

For what data are control values made?

  • For account balances and their details (IC and controlling balances, transactions, IC fixed asset transactions, IC holdings), control values are created per key combination <accounting period / fact / company / business unit>. These control values are saved in the table of the Processing control (overview VERARB).
  • One control value per voucher is set up for postings. This control value is saved in the document header (overview BEL).
  • For consolidation postings, one control value is formed per consolidation voucher. This control value is saved in the document header (overview KONBEL).
  • A separate control value is created for each currency (country/group/parallel currency). Rows with zero values are not included in the checksum calculation. Thus, for example, the control values for the local currency by the currency conversion remain unchanged.
  • Relevant attributes include account number, debit/credit indicator and amount as well as (depending on the table) posting key, IC-company, IC-business unit, controlling object, product/product group and/or fixed asset object. Since the company is also included, different control values arise for different societies, even if the values are identical.

How is the calculation of control values controlled?

Control values are now calculated as a matter of principle. Steering options are no longer provided for.

What are control values used for?

  • Control values are almost certainly a state of the data concerned. Any change to the relevant attributes will result in a change in control value.
  • The change of a control value in the VERARB table results in an entry in the change log of the Processing controls (overview VERARBLOG), so that it is logical when, by whom and by which application the data inventory was last changed.
  • When a report is created, the control value of the basic data to be included is saved (per currency) or a new report control value based on the same algorithm is created from the control values of the basic data (e.g. balances of several companies, several consolidation documents).
  • If a report is displayed (REP report overview or REPERG report display), this step is repeated and the control value determined is compared with the saved control value. Deviations are visualized by a message or by red cells in the control value state columns. They show a change in the basic data after the reporter was prepared.

Can control values be formed and compared in other systems?

Although the CRC-32 algorithm is a standard procedure that can be used in other systems, the control values calculated in IDL Konsis require some special prerequisites in order to achieve reproducible results:

  • For alphanumeric attributes, a special character set (IBM 850) is used.
  • Numeric values are available in special formats of the COBOL (BCD) programming language.
  • Since the sequence of the data is decisive, a certain sort must be observed.
  • In addition to the data transferred from pre-systems, there are also computational values (e.g. annual profit or loss, carries forward) in IDL Konsis, which are also included in the control value.

For these reasons, it is virtually impossible for control values to be created in pre-systems (e.g. accounting, Excel entry forms) or downstream systems and to be used for coordination with the control values in IDL Konsis.
For an optimal Community experience, Please view on Desktop
Powered by Zendesk