Additional Characteristic when Reading Reference Data (e.g. Functional Area)

READ_WITH_KEYR

* from Allevo version 3.4 (extended in 3.5)

From version 3.5, the constant is no longer relevant; the associated features are now displayed directly via the new Allevo setting dialog on the row definition.

When reading reference data, restriction to additional characteristics (e.g. functional area) may be useful; especially for profit center planning or in the Reporting. Column keys CY_KEYR and CM_KEYR (or alternatively CY_KEYSA) may be used to transfer the belonging characteristic values.

Note:

This documentation primarily describes the behavior during reading of reference data with selection via an additional characteristic. The function may be applied for CO postings and profit center. The constant may also be useful for planning functions, if postings shall be equipped with additional characteristics (especially applies to profit center postings, see corresponding Allevo manual).

Constant READ_WITH_KEYR (alternatively READ_WITH_KEYRA and READ_WITH_KEYSA) serves to define the characteristic that shall be addressed in this way and the row definition that this shall apply to.

Application areas:

· Planning of overhead costs for primary and secondary costs (not for stat. key figures and activity types).

· With line items, the restriction concerns actual and plan (not commitment).

· Within profit center accounting, the query applies when working with the classical and new general ledger.

The restriction may be activated for any row definitions. You may address different characteristics via the same Master (separated by row definition).

Currently, four additional characteristics are supported:

· FUNCTIONAL_AREA = Functional area
Restriction is performed via field FKBER with CO data and RFAREA with PC

· PARTNER_FUNCTIONAL_AREA = Partner functional area
Restriction is performed via PFKBER in CO line items (COEP, COEJ) or field SFAREA with PC data.

· TRADING_PARTNER = Trading partner
Restriction is performed via field VBUND with CO data (not with secondary costs) and RASSC for PC

· KOSTL_GROUP = Cost center group
A cost center group transferred by Excel is completely resolved before reading data in order to include only values of the desired cost centers. This may sometimes affect the performance (the function is only available for the new general ledger, field RCNTR is queried).  

As an alternative to these predefined characteristics, any field of a summary record table may be entered directly (also considered when reading line items). To avoid a program termination, Allevo independently checks for availability of a field in the relevant target table and complements selection conditions if necessary (otherwise, a value transferred from Excel will be ignored).

Constant READ_WITH_KEYR is activated as follows:

· In column Value from, enter either one of the four characteristic IDs named above (e.g. for the functional area) or the name of a database field used for selection (enter e.g. RBUKRS in order to select via the company code in table FAGLFLEXT in the new general ledger).

· In previous Allevo versions, activation according to row definitions could optionally be performed in column Value to. Multiple entries were possible as comma-separated list (e.g.”C1, C3“). From version 3.5, this assignment is done directly in the Allevo settings per row definition.

Example for application case

In the example above on the functional area, a suitable entry must be made in Excel column CY_KEYR in the Allevo Master:

· This is usually the ID of the desired functional area. Multiple IDs are also possible (comma-separated list in the corresponding Excel cell).

· An empty Excel field selects only posting rows where the respective additional characteristic is not filled in the SAP table (e.g. postings with empty functional area);

· Entry * on the side of Excel on the other hand reads all reference data, e.g. with any desired functional area.

Multiple additional characteristics may be used in the same layout/ Master. Corresponding IDs must then be entered in column Value from separated by colon. The same rule applies for corresponding row definitions in column Value to. Example:

“Value from“: „FUNCTIONAL_AREA:KOSTL_GROUP“.

“Value to“: “C1,C3:B2“

In this example, a functional area in key column CY_KEYR is expected for row definition C1 and C3 on the side of Excel; for row definition B2, the specification on the cost center group.

Note:

Column keys CY_KEYR / CM_KEYR allow up to 255 signs for the list of selection parameters. When using this constant, SELECT_TURBO is automatically deactivated. Alternatively, column key CY_KEYSA may also be used for selection via additional characteristics (controlled by constant READ_WITH_KEYSA). To transfer numeric contents, the corresponding Excel column must possibly be formatted as text (especially in the case of leading zeros e.g. functional area “0100“).

In single cases, it may be necessary to limit data selection in a way that only data records with empty field contents are included (e.g. when reading data for NGL). In this case, constant READ_EXCLUDING_FIELD may also be useful.

* New from Allevo version 3.4.15

The constant now applies also in planning for classical ledger.

The additional characteristic functional area is now also included when reading and writing data on the Allevo object (when working with ACOSx tables).

The list of selection characteristics transferred in CY_KEYR / CM_KEYR may now contain up to 255 signs (before: 24 signs).

* New from Allevo version 3.4.19

Allevo includes the constant now also when writing and reading comments (table /KERN/IPPCOMMENT). Comments may therefore now be saved e.g. with reference to a functional ara as additional characteristic.

* New from Allevo version 3.5

Figure of Allevo setting dialog on the row definition