Framework:FKT Aggregat
Function
FKT_Aggregat(<value>,<restriction 1 till n>)
| Parameter | Description |
| value | Here you have to enter the data path corresponding to the field whose value is to be determined. This could be all fields and calculated fields of a table defined for an aggregate (SUM or AVG) (see table designer). If, for example, you wish to determine the sales table from the sales proceeds_PLAN field, you have to enter the following:
Sales proceeds_PLAN.sales Here you can use any table, not just the source or target table, as with all the other functions. Warning! The column name is a parameter. Tables and column names must not be put in square brackets. (Wrong: [Sales proceeds_PLAN.sales]) |
| restriction 1 till n | These are filter restrictions for LookUp dimensions. Each restriction consists of three parts: the dimension to be restricted, an operator and the restriction itself. Example: Company !me @Session_Company_ID@.
The dimension to be restricted always refers to the table which was indicated in the value field. Therefore it is only to be indicated with its name. If a dimension is present several times in the table (e. g. cost center dimension in the contribution table), then the desired dimension can be indicated by means of the LookUp-Appendix. If no appendix is indicated, the LookUp dimension _1 will always be used. Example: Company_1 !me @Session_company_ID@ The restriction may also be applied to a LookUp dimension of the dimension. Let’s assume we had entered the company dimension as LookUp dimension in the PC/Cost center dimension and entered a company for each element of the PC/Cost center. Then the filter restriction could be used as follows: PC/CostCentre.company !me @Session_company_ID@. The operator must be entered with an ! (exclamation mark) and a relational type, whereby the following are permissible:
The restriction != is always interpreted as !me with dimensions and is only included for reasons of compatibility. The restriction itself may be any data path, variable or function which supplies a valid COPSYS_ID. It is also possible to carry out filtering with regard to the attributes of a LookUp dimension. Dimension.Dimensionattribute !me … If, for example, in the sales proceeds type dimension the P&L structure dimension is included as LookUp dimension, then the following restriction may also be used for filtering based on the Sales proceeds_ACTUAL table: Types of sales proceeds.P&L structure != [sales proceeds_VAT.sales proceeds types_1.COPSYS_ID] |
This function belongs to server-side functions.
An example is the “Sales proceeds_P&L_ACTUAL” formula.
fkt_Aggregat ( Umsatzerloese_IST.Umsatz ,Zeit !me [Umsatzerloese_IST.Zeit_1.COPSYS_ID] ,
Umsatzerloesarten.GuV-Gesamtkostenverfahren-Struktur != Umsatzerloese_IST.Umsatzerloesarten_1.COPSYS_ID] ,
Unternehmen !me [Umsatzerloese_IST.Unternehmen_1.COPSYS_ID] ,
PC/KST !me [Umsatzerloese_IST.PC/KST_1.COPSYS_ID] )
fkt_Aggregat( Finanzplan_Direkt_PLAN.Wert , Zeit != [Finanzplan_Direkt_PLAN.Zeit_1.COPSYS_ID] , Unternehmen !me [Finanzplan_Direkt_PLAN.Unternehmen_1.COPSYS_ID] , Finanzplan-Direkt-Struktur !me+under @FP_CashAB@ )
