Adopt Names for Cost Elements / Objects from SAP

READ_ELEMENT_TEXTS

* from Allevo version 3.1 (extended in 3.4)

The name of a cost element or activity type is usually stored in the Allevo Master. Alternatively, the constant READ_ELEMENT_TEXTS allows to dynamically adopt the name from SAP. The constant is mostly useful in the dynamical area of the Allevo Master, since there may be no names of cost elements entered permanently in the Master.  

Transfer of texts to objects is additionally possible from 3.4.

The belonging texts should for this purpose be maintained in the SAP system in the language of login (possibly, EN will be used as default language). When using the constant, double maintenance of master data is omitted in the SAP system and in the Allevo Master.

Names are transferred as done also in planning comments: a column definition (for years) providing the text on the side of SAP must therefore be stored in the system. The texts are consequently updated simultaneously with reference data.  

Activate the constant by entering the intended column definitions:

· Entry of the column definition in Value from for constant READ_ELEMENT_TEXTS activates the reading of texts on cost element or activity types.

· Entry of a column definition in field Value to activates the reading of names for objects (e.g. for cost centers). This feature is especially useful when calling the work in the Allevo MultiObject mode.

Example: Column definition CY_R9 is created for the desired layout; possibly with option “Read only comments“ to deactivate non-relevant characteristics. The column definition is stored for the constant in column „Value from“; in the Allevo Master, CY_R9_N must then be entered in the header of column „Element Description“. A row definition allowing to read comments must additionally be entered (at least T, possibly also in rows where group names shall be read).  

Note:

Constant READ_ELEMENT_TEXTS may not be used in combination with MOD (see documentation on constant DYN_KSTAR_SAT). Here, texts are already being adopted from SAP for all posting combinations anyway, incl. texts for the involved groups.  From Allevo 3.3 onward, there is the additional constant READ_PARTNER_TEXTS to display descriptive texts on partners (senders and/or receivers; see corresponding documentation): partner texts are again useful applicable especially for dynamic rows.

* New from Allevo-Version 3.4

The transfer may now also be used in the Allevo MO.

It is also possible to read texts on groups, if the group ID can be recognized as such: thus defined as 1:n group or defined via entry 2 for constant READ_GROUPS_FROM_SAP. The group ID must be present in the same column as would otherwise be the single posting element (e.g. cost element group in column CY_KEY, possibly instead of the usual sigma sign such as ###).  

T may also be used as row definition.