Consolidation of Satellite Data

GRP_READ_SATxx

* from Allevo version 3.0 (extended in version 3.4)

In different functions of Allevo, displaying several objects simultaneously is possible; e.g. when selecting a group in the Tree or with multiple selection for the MOD. According to this selection, all reference data are transferred to Excel while data of the satellites are usually read and written only for the representative object.

The active constant GRP_READ_SATxx offers the following additional functions:

· In the simplest case, the constant defines for each satellite if data shall be read and written for all selected objects (and not only for one representative object).

· To reduce the number of read rows, a dynamic aggregation of satellite data is possible: here, the constant defines the columns that shall be used as characteristic for the aggregation and the columns that shall be totaled. This aggregation is especially useful if a great number of data records shall be transferred (e.g. with very large groups).

Example:

The option to aggregate data may for example cause that only one row will appear in excel for each object, including the relevant sum values (or for each cost element or any other characteristics stored as fields in the satellite table).

Originally, the constant was designed for the reading function only (Reporting mode). In current Allevo versions however, data for the different objects may be rewritten (see notes further below).

The required settings apply for each satellite individually (e.g. GRP_READ_SAT05 for parameters of Sat 05). The following entries are possible in column Value from:

· X in column Value from activates the constant: all data stored in the objects of the group are then read from the satellite. Prior to the transfer to Excel, a new row number is assigned (applies equally also for multiple selection or selection via range with a “from/to“ specification).

· Alternatively, you may enter Y. Then, renumbering will be skipped so that data are provided in Excel in precise rows (available from version 3.3, see notes further below)

· Optionally, a list of satellite fields may be specified in Value from (separated by comma): these fields constitute the characteristics of a data summation/aggregation. In the standard case, all fields of type P are aggregated (including fields with decimals, type DEC in the ABAP dictionary).  This option causes Allevo to ensure that the satellite is set up only for reading (planning to aggregated rows in this satellite is not supported).

The option mentioned last (aggregation) may be further specified in column Value to: here, you may explicitly enter satellite fields that shall be totaled (per characteristic combination). The fields must be defined via a numeric type in the Sat table (P or I); entry is again made as comma-separated list.

Note:

Fields without aggregation adopt the content of the last row for the respective characteristic combination.

The constant GRP_READ_SATxx is activated to display satellite data of different objects in a common satellite range in the Allevo Master. Therefore, at least the object number in satellite column 4 should be shown in the Allevo Master (possible from version 3.0 of the Allevo Master, it is recommended to display all columns from the satellite index). Rows always appear in Excel sorted by object number: for this reason, the row number is rearranged prior to the transfer to Excel unless otherwise defined.

Save satellite data

Without the aggregation option, data may also be modified and saved for precise objects in the satellite on the side of SAP (incl. the deletion of previous entries). The function was first only intended for the application in context with the MOD; but may however also be used for calling ProCED or the FP / COPA interface (here, all relevant objects of the selection are transferred for further processing).  

To write satellite data, the specifications on Setclass and object numbers are required on the side of Excel (column 3 and 4 in the satellite index) for the entries to be transferred to SAP. In general, it is recommended to maintain all index columns in the Excel satellite range and fill it with specifications (for future extensions). These specifications are transferred to FP or the COPA interface as well, provided that one of these modules is included.  

The entry in Value from again determines if renumbering is performed upon saving:

· With ‘X‘, the row number is determined for each object, year and version again (numbered consecutively) for clarity per object on the side of SAP. This is especially important for the case that satellites are called via different layouts where the constant GRP_READ_SATxx is not active.

· Renumbering is however disturbing if satellite data shall be arranged in Excel in precise rows. The row numbers defined by Excel will be kept if ‘Y’ is entered in column Value from (from version 3.3).

Important: the constant GRP_READ_SATxx may not be used at the same time as SATxxSELECT since both influence the parameters of the selection according to objects in different ways (see also notes there).

* new from Allevo version 3.1

Reading and writing with MultiObject Dynamics (MOD), before, application was only possible with the selection of group in the Tree (for all object types supported by MOD).

* new from Allevo version 3.3

Suppression of renumbering during reading and writing by entering Y in column Value from

During writing, the Setclass, apart from the object number, must be transferred from Excel as well to enable working with mixed object types in the MultiObject (mandatory from 3.3.18).

Transfer object specifications to FP or the COPA interface

* new from Allevo version 3.4

The constant does now also apply for object type PR. Examples of application: selection of a project / WBS element in the Tree or MultiObject while including ProCED. In both cases, satellite data of all subordinate WBS elements are treated.

The constant may now also be used in the Allevo Single, in order to, for example, perform totaling.