meta data for this page
  •  

This is an old revision of the document!

Creating a consultation

As long as you have not reached the end of all screens (the last screen being the test screen), your query will not be saved.

Choice of environment

In the case of JDE/World data sources, and the environment is required. Objects and data will be retrieved from this environment.

Selection of tables and subqueries

Detailed page

Joints

Detailed page

Filtering

It is on this screen “Extraction according to the following rule” that the filters on the data will be made, using operations or parameters. see detailed page.

Field Selection

Detailed page

Appendices

For JDE/World data sources, it is possible to retrieve the annexes.

The Generic Text Cible (ex GT4201A) and the field or combination of fields that make up the key must be specified.

#TODO: add example output with appendices.

Currency decimals

If you uncheck the box Use the number of decimals from the data dictionary for currency amounts, the concerned fields will be displayed with the number of decimal places defined in the data dictionary (usually 2 decimals).

Otherwise Vigilens will use the number of decimal places defined in the currency. To find the currency and thus the right number of decimal places to display, the user must define whether the amount depends on the company code currency (the standard cost of an item for example) or the transaction currency (the amount of a sales order for example).

the checkbox Use the number of decimal places in the data dictionary is not available for all users (see Admintool). We can not use it if we have currencies with a number of decimals different from 2.

Standard
  • Update with standard definition: use the known Vigilens definition for the selected field.
  • Save current definition as standard definition: the current setting of the field will be the new standard for Vigilens.

Not all users are allowed to change the standard-setting, special rights are needed, see AdminTool.

Changing the standard has no retroactive effect on queries already saved. If you want them to take into account a modification, you have to edit them, apply the standard with the button, then publish it again.

Parameters

Detailed page

Restitution

Detailed page

Finalization and testing