|
Transfer Informationen from SAP Master Records |
|
MAP_FIELDxx
* available from version 2.9 (extended in 3.5)
The Allevo Master offers global parameters (global information) and cell definitions (CC fields) to adopt information from the SAP system, which is either transferred once planning is started or when switching the planning object. Already in the standard, Allevo offers a variety of standard information that may be called in the Master (see Allevo Excel manual, e.g. user, controlling area, transaction codes etc.).
The constant MAP_FIELDxx allows to transfer up to 10 further pieces of information from SAP master records to Allevo (xx = consecutive numbering; MAP_FIELD1 to MAP_FIELD10). Further application cases result from MOD functions (see notes below).
The table name of the relevant SAP master record is to be entered in column Value from. A distinction is made here in tables with master data and tables with text elements. It is partly also possible to read information from tables that are assigned to the actual object only indirectly (e.g.: Allevo starts with WBS elements but additionally reads a field from the master record of the responsible cost center).
Depending on the object type, data from the following tables are currently available:
|
Cost center |
Data of master record CSKS, CSKT |
|
Order |
Data of master record AUFK |
|
Profit center |
Data of master record CEPC, CEPCT |
|
WBS element |
Data of master record PRPS |
|
Business process |
Data for master record CBPR, CBPT (from 3.3) |
|
Allevo object |
Data for master record /KERN/IPPVIRTOBJ, /KERN/IPPVIRTOBT (from 3.3) |
Due to the selected object type, the name of the respective master record table is usually already known. Therefore, the following entries are alternatively possible in column Value from:
§ ELEMENT: refers to data in the relevant master record table
§ TEXT: refers to data from the text table (if available, also with KS and PC)
You may additionally add an “_EXT“ in the general entries in order to adopt the content of a field to the external display (in analogy to the project number). "ELEMENT_EXT" and "TEXT_EXT" are consequently to be used in this case. – For technically interested users: the field content is written in the target field through the ABAP command “WRITE“.
Enter the table field to be read in column Value to. If table or field name are not given correctly, the whole entry will be ignored. No error message will be displayed.
In newer versions, there are not only master data fields available but also further additional information (see the following notes).
Additional Information about EXTRAS
Besides the object specific master data tables, a general “table name“ EXTRAS may be used in Value from in order to provide Allevo specific information (e.g. the name of a group when working with 1:N objects). The fields that are available in this case for entering in Value to can be recognized from the structure /KERN/IPP_S_EXTRAS in the ABAP dictionary (see TA SE11). Currently available components:
· GROUP_1N shows the name of a group stored in 1:N.
· ACTIVE_REP transfers “1“ if Allevo has been called in the Reporting mode, otherwise “0“ (application for example with groups in the Tree, query in Excel via CC_CUSTINFOx).
· BUDGET shows budget for the start object (only for orders or WBS elements).
· SAP_STATUS_LIST system and user status for the start object (same structure as with ProCED constant FD_STATUS_LIST, see F1 documentation there). The specifications may be useful to set up filters for objects on the side of Excel.
The mentioned structure /KERN/IPP_S_EXTRAS is extended where necessary.
Transfer any constants to Excel (“Table name“ CONST)
By entering CONST in Value from, it is now possible to transfer contents of any Allevo constants to Excel. The name of the relevant constant must be entered in Value to. The characteristics of such a constant may then also be evaluated in Excel. The following rules apply:
1. If the relevant constant is active, contents of both parameters are transferred with colon as separator (Example: Query of constant PC_INT delivers “X:KSL“ if the constant is active and KSL is entered as currency type there).
2. If the queried constant is not set (or Value from and Value to are both blank), Allevo will transfer the name of the queried constant (“PC_INT“ in the previous example). This allows to control whether the transfer to Excel is successful.
3. A further general function results from the description under (2): the entry in column Value to may also be viewed as parameter content. Example: constant MAP_FIELD1 with “CONST“ in Value from and entry “abc“ in Value to transfers this exact letter sequence “abc“ to Excel.
As an alternative to CONST, also the “table names“ CONST_F and CONST_T may serve to enable direct access to single columns “Value from“ and “Value to“ (functions are otherwise the same).
Since these are layout specific parameters that may not change during planning in the Allevo Master, transfer to Excel is only performed when calling from Excel. They may consequently only be called via GLOBAL_CUSTINFOxx.
Application areas
Currently possible variants for the transfer of master data information to Excel with the following references:
· To the representative object via global parameters (global information provided on the side of Excel via GLOBAL_CUSTINFO1 to GLOBAL_CUSTINFO10).
· To the leading object on an Excel sheet (provided on the side of Excel via cell definitions CC_CUSTINFO1 to CC_CUSTINFO10).
· For each object that has been predefined in the current start selection (e.g. with MOD functions); see constant DYN_SAT_OBJECTS.
· As an alternative, constant READ_ELEMENT_DATA allows to transfer the information using comment columns (beneficial in the MultiObject mode).
---------------------------------------------------------------------------------------------------------------------------------------
* New from version 3.2
First special function via EXTRAS
* New from version 3.3
Transfer contents of any constants to Excel (“table name“ CONST)
* New from version 3.4
For applications in the MultiObject mode, the transfer is now also possible using comment columns (see the additional constant READ_ELEMENT_DATA).
* New from version 3.5
Scheduling data for the project item (table PRTE)
System and user status for the start object via EXTRAS
Data provision via constant DYN_SAT_OBJECTS (see documentation there).