Custom Analytics
Custom Analytics is a charged Add-On and must be licensed separately.
Custom Analytics is a premium add-on that enables you to generate tailored reports for in-depth analysis of key performance indicators. It supports tracking essential metrics and empowers data-driven decision-making to drive business growth and success.
Overview
In the overview you see all existing Custom Analytics. You can also search for a specific Custom Analytic or adjust the columns shown in the overview.
Creation
To create a Custom Analytics, click on Content Studio > Custom Analytics > + Custom Analytic. Enter a name for the new Custom Analytic. You can also add a description.
Dependencies
In the Dependencies dropdown list you can select one or more Analytic Steps. Depending on which Analytic Steps you choose, you'll see the Available Parameters of them on the bottom left. You can also define Output-Tables.
Parameters
In the section Custom Parameters you can Add Parameter. Set an identifier (ID), a name (Displayname) and optionally a description. Define the Data Type (string = character string, integer = number, date = date value) and specify whether this parameter can have multiple values. After you've saved, the new Custom Parameter is marked as Optional. Click on Optional if you want to set it to Required, and vice versa..
There are two different types of Parameters:
- User-defined Parameter: are created and linked in the same step as the user-defined Analysis itself
- Standardparameter: from the Content Suite
Handling Parameter values
Parameter vales are separated by a Semicolon ;.
Example:
- Your Input: 2022 and 2023 > Parameter Value: 2022;2023
Range values display a filter condition and are separated by the Dollar Sign $.
Example:
- Your Input: 0000 to 9999 > Parameter Value:
0000$9999 - Your Input: AAAA to ZZZZ > Parameter Value:
AAAA$ZZZZ - If you want to use both range values at the same time, they are separated by a Semicolon
;>0000$9999;AAAA$ZZZZ
Parameter
They are entered by simply replacing the values in curly brackets, so you must surround them with appropriate quotation marks.
Custom Parameters
User-defined parameters are referenced by their names, which are enclosed in two curly brackets. For example, the parameter Test is mapped as {{Test}}. The values are passed as explained above.
Content Suite Parameters
The following standard parameters are available in the integrated Content Suite:
| Parameter | Reference | Description |
|---|---|---|
| Analytic Closing Date | {{Common.Filters.AnalyticClosingDate}} | Optional - For analyses that require some kind of cut-off date. If no value has been defined, the current date is used |
| Company Code | {{Common.Filter.CompanyCode}} | Company Codes taken into account for the analysis |
| Currency Conversion Date | {{Common.Filters.CurrencyConversionDate}} | Optional - to specify a reference date for currency conversion transactions. If empty, the date of the transaction is used |
| Exchange Rate Type | {{Common.Filters.ExchangeType}} | Exchange rate type to be used for currency conversion |
| Fiscal Year | {{Common.Filters.FiscalYear}} | Financial year for relevant financial transactions |
| Language | {{Common.Filters.Language}} | Single-digit language identifier for localization-dependent filtering |
| Reporting Currency | {{Common.Filters.ReportingCurrency}} | Currency into which financial values are to be converted in order to be able to compare amounts in different currencies |
| Time Period | {{Common.Filters.TimePeriod}} | Period defines the time frame to be used for the analysis |
| Source ID | {{srcId}} | Table structure of raw data or extracted data |
| Destination ID | {{dstId}} | Table structure of analytic results |
Shortcut for Parameters
To make things even easier, there are integrated parameter value tables for the previously introduced parameters.
| Parameter | Table-Name | Columns |
|---|---|---|
| Analytic Closing Date | @filterAnalyticClosingDates | AnalyticClosingDate |
| Company Code | @filterCompanyCodes | CompanyCode |
| Currency Conversion Date | @filterCurrencyConversionDates | CurrencyConversionDate |
| Exchange Rate Type | @filterExchangeTypes | ExchangeType |
| Fiscal Year | @filterFiscalYears | FiscalYear |
| Language | @filterLanguages | Language |
| Reporting Currency | @filterReportingCurrencies | ReportingCurrency |
| Time Period | @filterTimePeriods | TimeStart, TimeEnd |
Additional Variables
To simplify the handling of the values even further, some additional variables are provided.
| Parameter | Variable-Name | Description |
|---|---|---|
| Analytic Closing Date | @envAnalyticClosingDate | Value of the analytical cut-off date |
| Currency Conversion Date | @envCurrencyConversionDate | Value of the currency conversion date |
| Language | @envLanguage | First language parameter value entered |
| Language | @envLanguageFallback | If second language is specified, this value is filled in |
| Reporting Currency | @envReportingCurrency | Value of the reporting currency |
| Time Period | @envTimeStart | Start date of the period |
| Time Period | @envTimeEnd | End date of the period |
Edit
You will get a warning message when you try to change a Custom Analytic, that is already being used by active (scheduled) Tasks. Please keep in mind, that any changes will affect these active Tasks and may result in failed Runs.
You can edit an existing Custom Analytic by clicking on it's name in the overview.
Deletion
If you delete a Custom Analytic that is used in an active (scheduled) Task, this Task will be deactivated and cannot be reactivated again. This deletion cannot be undone.
Example
Example 1 - srcId and dstId
SELECT
BSEG_MANDT,
BSEG_BUKRS,
T001_BUTXT,
BSEG_GJAHR,
BSEG_BELNR,
BSEG_BUZEI,
BKPF_BUDAT,
BSEG_LIFNR,
LFA1_NAME1,
LFA1_LAND1
INTO {{dstId}}.Accounting_Result
FROM {{srcId}}.BSEG
LEFT JOIN {{srcId}}.BKPF ON BSEG_MANDT = BKPF_MANDT AND BSEG_BUKRS = BKPF_BUKRS AND BSEG_GJAHR = BKPF_GJAHR
LEFT JOIN {{srcId}}.LFA1 ON BSEG_MANDT = LFA1_MANDT AND BSEG_LIFNR = LFA1_LIFNR
LEFT JOIN {{srcId}}.T001 ON BSEG_MANDT = T001_MANDT AND BSEG_BUKRS = T001_BUKRS;