Statistical Setups

• Code (field COD)

It identifies the current statistical code. A set of totals based on one to eight crossed criteria is linked to each statistical code.

• Description (field INTIT)

[object Object]

• Short description (field INTSHO)

This title provides a description of the record.
It is used in some screens or reports when there is not enough space to visualize the long title.

• Active (field ENAFLG)

Select this check box to activate the current record.

Disabled records keep their content and setup but cannot be used (by recalling their code) on other records (documents, settings ...), or for mass processes.

The authorizations to a given function can prohibit the creation of an active record. In this case, the check box is disabled by default. It can only be modified by an authorized user or through a signature Workflow.

• Activity code (field CODACT)

An activity code is used to:

• make optional an element in the dictionary if the value associated with the activity code is null.
• identify the specific/custom elements if they are marked with a code starting with X, Y or Z.
• size a maximum number of lines when the activity code marks elements from a grid.

In this way, if the activity code is disabled, the marked element will not be useable, and the associated code (if any) will neither be generated nor can be activated.

• Access code (field ACS)

This access code makes it possible to prohibit access to the current record for some users.

As a matter of fact, if the field is completed, only the users having this access code with read rights (respectively write rights) can view (respectively modify) the concerned record.

This access code makes it possible to prohibit access to the code for certain users.

If the field is assigned, only those users who have this access code in their profile can modify and/or enter this code according to the rights accorded.

• Module (field MODULE)

[object Object]

• Script (field PERPRG)

When wanting to establish aggregates with a periodicity not predefined in the software, there is the possibility to define the name of a process here where the following sub-programs should be defined :

• # This sub-program is used to recalculate a date (defined by DAT1)
  # which should correspond to the end of the period.
  # The result is DAT2.
  # LIBCLE corresponds to the label for the period in alphanumeric format.
  Subprog BORNES(DAT1,DAT2,LIBCLE)
  Value    Date    DAT1
  Variable Date    DAT2
  Variable Char    LIBCLE
• # This sub-program is used to identify a date (defined par DA1) that will correspond to the start of the period.
  Subprog CADRE(DAT1)
  Variable Date DAT1
• # This sub-program returns in DAT2 the end of the period defined by DAT1
  Subprog DATFIN(DAT1,DAT2)
  Value Date DAT1
  Variable Date DAT2
• # This sub-program returns the number of periods (signed) separating the two dates
  Subprog DECAL(DAT1,DAT2,DECAL)
  Value Date DAT1
  Value Date DAT2
  Variable Integer DECAL
• # This sub-program adds a number of periods (signed) to an end date
  Subprog RECAL(DAT1,DAT2,DECAL)
  Value Date DAT1
  Variable Date DAT2
  Value Integer DECAL

An example of such sub-program can be consulted by looking at the SUBSTADEC process, which defines the sub-program corresponding to management by decade.

• Periodicity (field PERTYP)

Periodicity for which the statistic is to be carried out. A local menu is used to define the different periodicities (daily, weekly, fortnightly, monthly...).

The aggregate records created by the statistical aggregation are dated to the first day of the period.

• Trigger (field RLG)

Code for the triggering of the statistic that is used to identify the element that triggers the statistic.

It must be defined in the table of the triggering events.

• Validity start date (field VLYSTR)

• Validity end date (field VLYEND)

• Update code (field UPDCOD)

This code is by default the statistic code. But it can be different, notably if wanting to create a single aggregate from several different triggering events (which imposes several statistics codes). In this case, the update code will be common to all the statistics codes.

• Data retention days (field TIM)

Life of the statistic expressed in a number of months. This time is used by the management of purging, once the decision has been made to purge the statistical data.

The statistical data normally being strongly aggregated, they take up a limited amount of space and it is often interesting to keep these statistics for a fairly long time.

• Update date (field LSTDAT)

This displayed date is used to identify the last date at which an aggregate has been carried out by recalculation of the statistic.

• Default screen (field SCRDEF)

An enquiry screen can be defined in the case of customisable enquiries. For example, in the case of account enquiries.

• Drill down object (field OBJ)

This field makes it possible to define an object. In the Zoom menu for this object, it is possible to find all the statistics codes with this object code.

In order that the zoom menu appears in the object management, it is necessary to tick the box Zoom in the parameterisation of the object.

• Report (field RPT)

This field allows the entry of the Crystal Reports report associated with the consultation of this statistic code

• Function (field FONCTION)

• Definition level (field UPDLEV)

Used to define the organizational level of the aggregate by period (a global, by company or by site aggregate).

The site level of detail can only be obtained if the triggering event defines a site code; the company level of detail can only be obtained if a site or company are defined in the triggering event.

On restitution, there is the possibility to request either the most detailed parametized, or an aggregate level (by company, or global if the aggregated is managed by site).

• Type (field TYP)

Used to define if the aggregate in the statistical records is updated in real time or in batch mode.

It is important to note that only the standard triggering events can give rise to real-time aggregations (each time an update is made, the update is carried out). Except in the case or customized statistics, the statistics based on non standard triggering events that can only be updated in batch mode.

For performance reasons, the use of numerous standard aggregations based on a given triggering event can slow the corresponding transaction. It is therefore prudent to have batch based statistics and to plan to have a regular batch task to update them.

• Table (field TBL)

Define the table in which is found the grouping criterion for the line of the statistic.

• Abbreviation (field TBLABR)

When the previous table is on line several times in the trigger event, the abbreviation to be used in this specific case is defined here.

• Field (field FLDNAM)

Define the field code such as it is known in the table.

• Index (field FLDIND)

When the criterion chosen is multi-occurrence, the value of this field is used to give an index (from 0 to N-1, if N is the number of occurrences of the field).

• Description (field FLDINTIT)

Define the title of a criterion as it will appear during an interrogation of the statistics. By default, the title of the field is picked up from the dictionary and so can be displayed in the connection language of the user.

But it is also possible to modify it to give a different title, so that other languages can be used to define it.

In translatable fields such as this one, you can enter a description in a language other than the connection language: Click On line translations from the Actions menu.
 For further information, see On line translation of descriptions.

• Group (field FLDGRP)

• Position (field FLDPOS)

When the criterion field is a string of characters, it is possible to define the aggregation on a sub-string of characters by defining the position of the first character retained (1=start of the string) and the length.

For example :

• if it is necessary to aggregate the total of the first two characters of a post code of 5 characters, it is necessary to give position 1 and length 2.
• if wanting to structure the aggregate of the last three characters of a code of 8 characters, it is necessary to give position 6 and length 3.

• Length (field FLDLON)

• Type (field FLDTYP)

Display only field that indicates the data type (character,numeric, local menu, date...) corresponding to the criteria entered on line.

• Variable (field VARNAM)

Defines the title proposed by default with regard and the statistical total.

• Description (field AMTDES)

Define title for the stock totals in statistics record.

• Formulas (field AMTFOR)

This calculated formula, can call all variables and tables on line at the time of the aggregation, is evaluated and its result is aggregated in the statistic aggregate corresponding to the period an the organizational level of the defines aggregation.

• Forecast (field FRTFLG)

If this indicator is set toYes, it is possible to define the provisions for the corresponding aggregate amount.

These provisions can be entered, calculated from actuals or from provisions in another period and this in an aggregation field freely defined from the criteria defined for the statistic.

On the restitution of the statistic, there is the possibility to present both the calculated aggregates, the corresponding provisions and any expression that acts on the two (this is parameterized in the tab Advanced of the statistic).

• Conversion (field CNV)

This indicator is used to specify if the previous expression is expressed in a currency, where there is then the possibility to give the currency by calculate expression, as well as the common currency in which it should be converted.

The conversion is made at the historic rate defined on the reference date for the triggering event, the exchange rate type used for the conversion being defined by the parameter CHGTYP (the first type if nothing is defined).

Thus it is possible to get amount totals expressed in a homogenous fashion.

• Source currency (field DEVORG)

When the statistical amount is expressed in currency, this field is used to identify the code for the destination currency, in order to be able to convert the amounts in a current currency before aggregating them.

It is a calculated expression either constant type, or via the intervention of a common variable for example GSYSCUR.

• Destination currency (field DEVDES)

The statistical amount is expressed in currency, this field is used to identify the original currency code, in order to be able to convert the amounts in a common currency before aggregating them. It is a calculated expression either of the constant type, or via the intervention of fields that are online at the time of the aggregation.

• Titles (field INTITFRM)

Enter the column title.

In translatable fields such as this one, you can enter a description in a language other than the connection language: Click On line translations from the Actions menu.
 For further information, see On line translation of descriptions.

• Formulas (field AMTFRM)

Enter the formula that is used to calculate the total for the column.

The Selection button makes it possible to choose the available variables.

• Column type (field CUMFRM)

Enter the column type :

- Normal : Column total.

- Progressive total : the cumulative line total by line without re-zeroing.

- % of the total : line total percentage with respect to the overall total.

- cumulative % : the cumulative line % of the total by line without re-zeroing.

• Format (field FMTFRM)

Used to define, in the decimal format, the number of integers used before and after the decimal point. If this field is not entered, the value of the FMTSTA parameter is used.

• Criteria (field CRI)

In the case of multiple lines, the criteria are linked by an AND logic.