|
Read and Plan Data for the Object Group |
|
MULTI_WITH_GROUPS
* available from version 3.0.11 (extended in 3.3)
Normally, Allevo reads its data from the SAP system following the object number indicated, for instance, in the header of the Excel sheet (or in column MO_AO for the MultiObject mode). The constant here allows to read all data on the group in total by indicating the group ID (e.g. cost center group) on the Excel page. The constant also ensures that groups are not interpreted as object numbers by mistake (with the risk of reading false data).
The constant MULTI_WITH_GROUPS is activated by an entry in column Value from. The following two options are available:
1 if the ID specified in Excel is found as a group in SAP, data on the group are read; otherwise, Allevo interprets the ID as an object number. For determination of the relevant objects of a group, the entire time span according to the column definition is considered. Groups with no valid objects may be logged via constant TEST.
2 in this case, the group must be stored in the Allevo 1:n table. Only then, data on the group are read.
Important for reading satellite data: the first element of the group is automatically used as the representative object. If satellite data shall be read for all objects of the group, the constant GRP_READ_SATxx may be useful.
Write planning data: in current versions, the constant allows also to enter planning data for a group. Consequently, the same behavior as with cost element groups applies: planning data are written to the stored representative object:
· For mode 1 in “Value from“, Allevo uses the representative object stored in the SAP reporting (e.g. according to the entry in KSH3 on the cost center group: context menu “Settings for reports“ and there “repres. cost center“).
· For mode 2 in “Value from“, an entry must be stored in the Allevo 1:N table.
With no representative object, Allevo does not save any planning data in SAP.
Behavior in the Inplace panel: the constant may NOT be active when working with the object Tree, especially not if evaluations shall be performed on the level of groups (when selecting a group in the hierarchy, Allevo would only transfer the first object).
|
Note: |
The constant MULTI_WITH_GROUPS was originally created for applications in MultiPage; especially also for the case that different object types are processed on different Excel sheets in the MO mode. The constant may overlap with READ_GROUPS_FROM_SAP. |
New from version 3.1:
The constant is now also applicable for the usual list display in MOM. This may be useful if, for example, a group is selected via the Tree in order to read all data for this group (applies during planning and in Reporting transactions).
If the constant is active in MO, the planning mode will be kept when calling a group in the Tree, i.e. the function “Adopt planning data“ is available (effective from version 3.3, before, the program always switched to the Reporting mode). Direct planning for a group is of course not possible; in this way, however, you may superiorly record satellite data for all objects of the group (together with constant GRP_READ_SATxx). To prevent entries in the main planning range, appropriate additional functions should be stored on the side of Excel.
New from version 3.3.10
The constant now includes not only SAP groups stored in the tables common today such as SETHEADER, but also old entries in table T800S (SAP R/3 before version 4.0).
New from version 3.3.20
The constant is now also considered during the entry planning data if “1“ is entered in Value from to refer to 1:N groups.
New from version 3.5
The constant here may NOT be set if the Inplace panel is active with the object Tree (otherwise, only the first object will be transferred and read when selecting a group in the hierarchy).