Selection Criteria of a Satellite

 

SATxxSELECT

* from Allevo version 3.0 (previously applied to SAT00 only)

This constant allows changing selection conditions for a satellite (depending on the satellite number, e.g. SAT03SELECT, SAT04SELECT…).

If information of general nature (meaning they are applicable to more than one object (COOBJECT)) are stored in a satellite, it makes sense to exclude the object as a selection criterion (in order to avoid having identical information stored for all objects).

In field Value from, the following fields can be specified as those that should not be included in the selection from the table (in brackets: equivalent specifications via position in table index, as it is possible since version 3.1):

0 = as standard selection, however, Value to is additionally included (see below)

1 = COOBJECT is not used as selection criterion (X11011)

2 = COOBJECT, SETCLASS are not used as selection criteria (X10011)

3 = COOBJECT, SETCLASS, JAHR and VERSION are not used as selection criteria (X10000).

With the option X in column Value from, each index field of the satellite can be individually configured as a selection element. Here, the Value from consists of a leading X and a sequence of numbers with 5 decimal places corresponding to the index fields of the satellite table (as a sequence of 0 and 1).

·         Example: The entry X11100 determines data about the controlling area and set class, at the same time object number, year and version are ignored.  Without any additional restrictions, the data for the respective object on all the years and versions will be read.

In column Value to, a specific query can be deposited for the excluded fields (or any other fields in an individual satellite). The related instruction corresponds to a SQL-query in ABAP with WHERE condition (important: as common for ABAP, you need to observe blanks within the instruction):

·         Example: the entry PYEAR = '2014' AND (VERSION = 'A11' OR VERSION = 'A12') reads data for the planning year 2014 using both the A11 and A12 versions. The comparison values (e.g. year 2014 in this case) can again be placeholders themselves, in the way they have been applied in the Allevo specific file manager. E.g. parameter <LAYOUT> during the query for comparing the content of a field with the relevant layout (see corresponding notes on file management in the manual). Important: these placeholders must be enclosed by apostrophes (actually ‘<LAYOUT>' in our example).

With a WHERE condition entered, the satellite may only be included for reading. The corresponding flag must then be set in the Sat.Assistant.

The current planning layout can alternatively be used as selection criterion (entry in column Value to): for this purpose, a field for the Allevo planning layout is required in the Append of the satellite. Now that this field name is entered in column Value to, reading will only be performed for the rows of the satellite in which the entry with an actual planning layout is contained in the affected field.

Note:

If constant SATxxSELECT is set for a satellite, ProCED will not be executed automatically even if the satellite was activated for this purpose via constant ACTIVE_PROCED.

Save satellite data:

In principle, if selection via Value to is not restricted, writing satellite data is also possible regardless of data of the Allevo start (application must however be considered individually). Important: to do so, the missing index fields must be provided by Excel, i.e. the index columns must be as usual included in HR- and RW-areas: it is also recommended to use only these areas and avoid using special types of the satellite area. Further settings are not necessary.

Important:

When saving independently from the object, Allevo first deletes all available data records (without restriction to objects).

During saving, the line number will be renumbered consecutively for each object, year and version (also important for accessing via other layouts in which the constant SATxxSELECT might not be activated).

No information must be written in satellites if any restriction to selection is applied via Value to. The satellite should thus be restricted to the read mode in Sat.Assistant.

The constant cannot be set in combination with GRP_READ_SATxx since both change the selection according to objects, regardless of each other (see also the notes).

 

* new from version 3.1

New option X with “Value from“ in order to individually activate each index field of the satellite as selection element.

Additional WHERE condition in “Value to“ with restriction for writing.