|
Activate MOD Dynamic Cost Element Structure |
|
DYN_KSTAR_SAT
* from Allevo version 2.8 (extended in version 3.4)
This constant activates the dynamic cost element structure in the Allevo Master.
The classical MultiObject List Form (MOM) has a fix object and cost element structure that must be defined centrally in Excel or via satellite 0. This might lead to double maintenance of master data, since both cost elements and object groups are already available in SAP.
In the variant of the dynamic cost element structure (MOD = MultiObject Dynamics) however, relevant rows are generated automatically with cost elements – based on the group assignments stored in SAP (by now, this may for special cases also be called in the Single mode, see note below). Possible execution variants:
· Structure according to object group (planning according to objects)
· Structure according to cost elements or the cost element group; this structure is beneficial when planning single cost elements with different objects.
Filling the Master with objects and cost elements requires an own satellite with a prescribed structure (see structure /KERN/IPP_S_DYN_KSTAR_SAT as sample for the append). At least six fields (columns) are required in order to efficiently use MOD functionalities on the side of Excel (see note on the structure further below).
Further settings:
· Flag “ROS“ must additionally be set for the MOD satellite (definition of the reading sequence) so that data can be adopted from SAP on time; i.e. before reading the actual reference data.
· In single cases, it may be useful to insert only these posting combinations in Excel that data are already stored for in SAP (beneficial e.g. when using Allevo as Reporting tool). This function additionally requires constant DYN_KSTAR_PRE to be active. Possibly, also control levels / hierarchies will be deleted in case that no data were found in the elements of the groups).
· Alternatively, it may be important to transfer only objects to Excel that have a valid status (see constant DYN_KSTAR_SAT_STATUS).
· When calling “Close planning“, all objects of a group with status “3 = planned“ will be closed (in previous Allevo versions, it was only the representative object)
In a simplified form, MOD functions may also be set up for statistical key figures (see constant DYN_STAGR_SAT).
|
Note: |
The MOD is available for all object types supported by Allevo except for PR (projects/WBS elements). |
To activate the constant DYN_KSTAR_SAT, column Value from must contain the number of the intended satellite (e.g. “19“; from version 3.4, multiple entries are also possible; see notes further below).
Column Value to then describes the display of posting rows in the Allevo Master (sort sequence). The following entries are possible (see also application examples at the end of this F1 documentation):
1
Planning according to objects:
Objects are displayed as leading characteristic in alphabetical sequence with
one row per cost element, (sub) total per cost element group (structure is
therefore similar as in the Allevo standard Master). This is also the default
if Value to is empty.
2
Planning according to cost elements:
Cost elements as leading characteristic in alphabetical sequence; one row per
object on the cost element and subtotal per object group.
Other sort sequences (from version 3.2):
3 As (1), but sequence of objects is now in accordance with the affiliation to object groups, sub and sum totals for each object group (on the level of the cost element).
4 As (2), but sequence of cost elements is now in accordance with the belonging to cost element groups; no sums for object groups; instead, sum totals of all cost element groups.
5 As (1), but sequence of objects is now in accordance with the belonging to object groups; in addition, sums per cost element group are shown also for all object groups.
6 As (2), but sequence of cost elements is now in accordance with the belonging to cost element groups; in addition, the sums per object group are shown also for all cost element groups.
The MOD may transfer the list of posting combinations also without any summation levels. This may be beneficial if there are explicit ranges in the Master intended for output (e.g. OAAS) or input (see functions of OnePageMulti). See constant DYN_SAT_CHAR for further details.
The MOD is also included during Allevo offline transactions: the level of group resolving may be predefined as in the MultiPage mode (DYN_KSTAR_FIX must be simultaneously active).
|
Note: |
The Allevo MO Master must be adjusted in the following points: ▪ Setup satellite range ▪ Entries in the Customizing settings with specifications on row definitions during reading and planning ▪ Activation of special macros to automatically enter the intended row structure in the Allevo Master (contained in the standard Master from version 3). ▪ From Allevo version 3.4, there are functions available to automatically adjust the relevant Excel table range to the respective need (settings for “ExpandLeadSat“). See also notes in the Allevo Excel manual. |
Use two MOD satellites simultaneously
Two satellites may be transferred to Excel at the same time for the MOD with cost element structure. This serves to, for example, get a display with two different sort sequences on two separated sheets (although, of course, entry and planning may only be done using one of the sheets). This function may be an interesting extension of the Allevo Reporting.
Both satellites are to be entered in column Value from separated by comma (e.g. “18, 19“). The desired sort sequences consequently must also be entered comma-separated in column Value to.
Cooperation with ProCED:
In addition, ProCED may be activated for the selected satellite (via “Sat.Assistant“ in the Allevo constant management). This primarily results in two advantages:
· All other satellite fields provided by ProCED via the field mapping may be used.
· ProCED checks if data records for the intended posting combinations are already available in the SAP system (similar to DYN_KSTAR_PRE).
For collaboration with ProCED, the satellite must contain individual Append fields to transfer the additional information.
Structure satellite append (structure /KERN/IPP_S_DYN_KSTAR_SAT)
Filling the Master with posting combinations from objects and cost elements requires an own satellite with a prescribed structure (see structure /KERN/IPP_S_DYN_KSTAR_SAT). In current program versions, Allevo generates these fields itself if no append is available in the satellite (data are anyway only held temporarily and are thus not saved in the satellite).
At least the first 6 fields (columns) are required to efficiently use MOD functionalities on the side of Excel.
|
Column |
Sat Field |
Description |
|
8 |
OBJECT |
Object number (e.g. the cost center) |
|
9 |
LTEXT |
Object description With time-based objects – e.g. cost center – the respective latest text will be transferred to Excel (highest date for validity start). |
|
10 |
OBJ_SETCLASS |
Setclass |
|
11 |
KSTAR |
Cost element ID (or STAG with statistical key figure) |
|
12 |
KTEXT |
Text on cost element (or GRTXT with statistical key figure). If an entry for the cost element is stored in the master record, this is a long text (40 signs); otherwise short text (on the language login respectively). |
|
13 |
KATYP / GRTYP |
Cost element type (or GRTYP as category with statistical key figure) |
|
14 |
INVALID_FOR_CXWW |
Optional and only with cost element MOD with cost centers: marks rows with cost centers that may carry old data but are no longer relevant for new planning (e.g. due to end date or deletion flag). |
|
15 |
IS_TOP_KSTAR_GRP |
Optional and only with cost element MOD: marks rows with the highest summation level for cost element groups. |
|
16 |
OBJECT_AND_GROUP |
Optional und only with cost element MOD: contents as in column OBJECT, group ID is transferred in totals lines (instead of the usual special characters ###) |
|
17 |
KSTAR_AND_GROUP |
Optional and only with cost element MOD: contents as in column KSTAR, cost element group ID is transferred in totals lines |
The number at the beginning of the description is the satellite column that is usually also used to address an information in Excel.
-----------------------------------------------------------------------------------------------------------------------------
New from version 3.1
Sort sequences 3 to 6
New from version 3.2
Collaboration with ProCED
New from version 3.3
MOD satellite without append automatically uses the structure /KERN/IPP_S_DYN_KSTAR_TAB for data transfer to Excel (combination with ProCED, however, still requires an individual append).
“Close planning“ for all objects in a group
The MOD may now also handle hierarchies that are stored on different levels (a control level might start with two special characters ** instead of only one *. This is especially important for the display of combined summation levels (3 to 6).
List of posting combinations in Excel without summation levels (constant DYN_SAT_CHAR)
New from version 3.4
Simultaneous transfer of two satellites to Excel.
Treatment of all objects of the selection in “Close planning“.
The MOD may now be used with direct entry of the cost element in the start screen also in the Allevo Reporting (before, a fixed specification via DYN_KSTAR_FIX was required).
If constant DYN_KSTAR_PRE is active together with the MOD in order to avoid useless rows in Excel, this could previously result in “gaps“ in the display of hierarchy levels. Now, missing totals lines are inserted automatically.
Long text (40 sings) on the cost element; before, it was only short text.
Latest description with time-based object types, e.g. with cost center.
New from version 3.5
By now, the MOD functions are also available when calling in the Single mode of Allevo. This may be beneficial when working with only one object anyway and if fields for multiple selection or group shall not even appear on the start screen. The cost element selection must be permanently stored (via DYN_KSTAR_FIX).
------------------------------------------------------------------------------------------------------------------------
Examples for display formats / sort sequence
Display format (1): Planning according to objects
The structure corresponds to the usual display in a MOM Master; if different objects are planned subsequently.
|
100002 |
Development-Project: Hyper Pumps |
403000 |
Hilfs- / Betriebsst. |
|
100002 |
Development-Project: Hyper Pumps |
410000 |
Verbr. Handelswaren |
|
100002 |
Development-Project: Hyper Pumps |
# |
Materialkosten |
|
100002 |
Development-Project: Hyper Pumps |
415000 |
Kosten Fremdbezug |
|
100002 |
Development-Project: Hyper Pumps |
# |
Fremdleistungen |
|
100002 |
Development-Project: Hyper Pumps |
## |
Sonstige Primäre Kosten |
|
100002 |
Development-Project: Hyper Pumps |
### |
Primärkosten |
|
100003 |
New Generation of Turbo-Pumps |
400000 |
Verbr. Rohstoffe 1 |
|
100003 |
New Generation of Turbo-Pumps |
400010 |
Verbr. Rohstoffe 2 |
Display format (3) is like (1) with additional sum per object and across all cost elements (i.e. possibly one row for the cost element group from the Allevo start).
Display format (5) has the same structure as (1) with additional sum totals according to object groups.
The last two rows of the following range are sums on the level of cost element groups (for the top cost element group respectively, in this example primary costs).
|
100004 |
Development Long-Life-Bulbs |
415000 |
Kosten Fremdbezug |
|
100004 |
Development Long-Life-Bulbs |
# |
Fremdleistungen |
|
100004 |
Development Long-Life-Bulbs |
## |
Sonstige Primäre Kosten |
|
100004 |
Development Long-Life-Bulbs |
### |
Primärkosten |
|
# |
Gruppe A Stufe 1 |
#### |
Primärkosten |
|
## |
Einstiegsgruppe |
##### |
Primärkosten |
Display format (2): Planning according to cost element
This structure is beneficial when planning single cost elements for different objects (columns might in this case of course also be arranged differently)
|
100005 |
Long-Life-Bulbs (16V) |
400010 |
Verbr. Rohstoffe 2 |
|
# |
Gruppe B Stufe 1 |
# |
Verbr. Rohstoffe 2 |
|
100002 |
Development-Project: Hyper Pumps |
400010 |
Verbr. Rohstoffe 2 |
|
100003 |
New Generation of Turbo-Pumps |
400010 |
Verbr. Rohstoffe 2 |
|
100004 |
Development Long-Life-Bulbs |
400010 |
Verbr. Rohstoffe 2 |
|
# |
Gruppe A Stufe 1 |
# |
Verbr. Rohstoffe 2 |
|
## |
Einstiegsgruppe |
## |
Verbr. Rohstoffe 2 |
|
100002 |
Development-Project: Hyper Pumps |
403000 |
Hilfs- / Betriebsst. |
|
100003 |
New Generation of Turbo-Pumps |
403000 |
Hilfs- / Betriebsst. |
|
100004 |
Development Long-Life-Bulbs |
403000 |
Hilfs- / Betriebsst. |
|
# |
Gruppe A Stufe 1 |
# |
Hilfs- / Betriebsst. |
|
## |
Einstiegsgruppe |
## |
Hilfs- / Betriebsst. |
Display format (6) with additional sum totals
|
100002 |
Development-Project: Hyper Pumps |
415000 |
Kosten Fremdbezug |
|
100003 |
New Generation of Turbo-Pumps |
415000 |
Kosten Fremdbezug |
|
100004 |
Development Long-Life-Bulbs |
415000 |
Kosten Fremdbezug |
|
# |
Gruppe A Stufe 1 |
# |
Kosten Fremdbezug |
|
## |
Einstiegsgruppe |
## |
Kosten Fremdbezug |
|
# |
Einstiegsgruppe |
### |
Sonstige Primäre Kosten |
|
# |
Einstiegsgruppe |
#### |
Primärkosten |