MultiPage: Temporary Storing Selection Characteristics

READ_MULTI_AREAS

This constant serves to accelerate Allevo Multi under certain conditions.

In the MultiPage mode, Allevo creates a worksheet for each object (e.g. cost center). When reading reference data from SAP, each worksheet is processed individually. Consequently, the information about cost elements, activity types etc. are transferred for each worksheet from Excel to SAP (so that data selection can be performed in SAP).

This process is somewhat time consuming but nevertheless necessary if, for instance, the details on cost elements are generated individually for each worksheet (e.g. depending on a cost center). In this case, the selection information for each worksheet must also be transferred to SAP.

However, if the structure of the Master is equal for all objects, it is sufficient to transfer this consistent selection information to SAP only once (for the first worksheet only), and store it temporarily for the following worksheet: this means the structure of the first worksheet will always be used for the following worksheets.

An entry X in column Value from activates temporary storing.

You may additionally enter row definitions that shall apply as exceptions in column Value to: the corresponding Excel rows will therefore transfer each work sheet again.

Example:          Column Vale from        =          X
Column Value to          =          M, C (etc. selection, separation by comma)

Note:

In the MultiObject mode of Allevo, the Setclass and object information is usually defined in the Allevo Master and then transferred to SAP. This function must NOT be applied in combination with constant READ_MULTI_AREAS.    From version 3.2, Allevo automatically switches off the constant once this typical MultiObject constellation is recognized.