Table of Contents maxLevel 2
...
Datavard Insights BW analysis BW module enables you to analyze data distribution and the usage of InfoProviders in in a particular system based on a characteristic (usually on time characteristic). The characteristic you choose splits data into groups, which enables us to analyze the distribution of data. Here is an example.
...
Ja ako user potrebujem vediet kedy ja a kedy system urcuje split characteristic. Mozno osobitny clanok o Split charact,
. Current version of BW module support analysis based on only one specified characteristic.
There is one exception to this rule. BW module is shipped with one predefined data distribution setting with
...
technical name "STANDARD". This data distribution
...
does not use only one specific
...
characteristic to split data in InfoProviders
...
. It uses set of standard time characteristics (0CALYEAR, 0CALMONTH, 0CALWEEK, 0FISCYEAR, 0FISCPER, 0CALDAY, 0DATE, 0CALQUARTER). Each InfoProvider is searched for one of these
...
(or referenced
...
) characteristics (in a left to right order) and then
...
data distribution
...
is
...
done using the first one found while values are transformed to years level. If Extended query statistics are enabled, relevant time characteristic that was most used in query filters
...
for particular InfoProvider (and its reporting parents
...
) is preferred. However, if an InfoProvider is a DSO or an InfoCube and a DAP (Data archiving process) is created,
...
the time characteristic
...
The current version of the Data distribution analysis is based on only one specified split characteristic. The only exception is the above mentioned data distribution setting with the technical name "STANDARD".
It is possible to enhance a used in DAP is used. It is possible to enhance set of used time characteristics by additional ones. See section (DI-1811) Define the Data Distribution Analysis#Additional Additional Time Characteristics for more information.
...
Data distribution definition (new analysis)
You can define a new Data analysis for data distribution analysis of InfoProviders in your monitored systems following the your monitored system InfoProviders following steps described in this section. This results will result in the creation of a new tile in Insights Fiori front-end frontend in "Data ManagementManagement" tabarea.
Custom Data data distribution analysis tile
- To define
...
- new
...
- data distribution analysis (technically called
...
- as Subgroup)
...
- Run the run transaction SE38 and execute the program "/DVD/HS_CENTRAL_SUBGROUP" or the transaction /DVD/HS_SUBG. The following screen appears. Define the following Data Following screen will be displayed.
In this screen you need to define following data distribution analysis attributes:- Subgroup ID - unique identifier of Data data distribution analysis.
Split Characteristics - defines which InfoObjects are used for the Data Here you define what InfoObjects will be used for creation of data distribution analysis. In the current version only 1 characteristic can be defined as a split characteristic and used for in data distribution. During the Data distribution analysis What will happen during analysis is that each analyzed InfoProvider is searched for the will be searched if it does contain that characteristic. If the characteristic is found , all the InfoProvider data is are split to the groups , which are created based on the distinct values of the split this characteristic.
We implemented aNote Info There is safety check that allows to split object data only up to 100 distinct values to prevent generation of too much data generation in the system.
Data groups definition area - in this table you can define data groups. Each data group is identified by its ID (DATA_GROUP), it's description and id (first column). It has its own description and then set of conditions. These conditions define how InfoProvider data groups created by split using specified characteristic is grouped into resultswill be grouped in Fiori analysis output.
Click Save on save button to save the definition of the Data data distribution analysis . To execute ...analysis we should
add this new data distribution to our collector. whar are we doing next and what for?
Tip definition.
- If you would refresh Fiori after this step, frontend of Insights now you should see a new tile there already but without data. To execute analysis we need to add this new data distribution to our collector.
- Execute the /DVD/MON transaction on ... central system.
- Click on "Monitoring settings under Settings" in Settings menu of the transaction.
- In the tree on left side of the screen double click on the "KPI collectors" folder.
- In the displayed list of collectors search for "/DVD/MON_HM_CL_COL_DU" collector and select its row.
- While the collector row is selected double click on "Collector's inputs" folder in the left tree.
- In the displayed list of collector input input tables click on "Display/Change" button for /by the input table "/DVD/HS_IT_DU1".
- In table maintenance maintenence view switch to the edit mode. tu to ako pokracuje a naco totu robime
- Click Create on create new record button.
- Fill the following fieldsnew row while providing:
- Subgroup ID - same Same ID as was / you defined for Data data distribution analysis definition in the first step 1.
Number - number of days to update update size data of data groups. no entiendo
Note Data distribution analyses collector is executed every day for all defined Data data distribution analyses. Doing size update of all InfoProviders data everyday would not be possible due to long runtime of this action. Therefore it is recommened to update sizes of data in InfoProviders only once per some period. Minimal recommended value is two weeks. Update of usage of InfoProvider data is done everyday as it is much faster.
- Click on Save button.
- A new Data
New data distribution analysis is now defined.
The analysis is automatically - Analysis will be automaticaly executed on all systems where the Data Distribution Collector is scheduled. See Data Distribution Collector is schedulled. See BW add-on setup section on how to schedule a collector.
- You can view the results in Fiori front-end.
Results can be seen in Fiori frontend of Insights application.
Info |
---|
Please note that ...collector collector always gathers analysis results from monitored system created on its previous run (if already finished). Therefore , the first results are will be visible in Fiori front end, one frontend day after the first run of analysis run is completed finsihed on .. monitored system. |
...
Example
Here is an example how would be one InfoProvider data processed with whith data distribution specified as in previous step list. We will use in this example the InfoProvider /DVD/IC_CUBE InfoProvider as example that contains the characteristic 0CURRENCY.
The ....analysis finds Analysis will find this characteristic in structure of the InfoProvider and selects will select all distinct values while it calculates calculating their respective sizes (to co piseme hore sme vynechali). In our example the . Lets pretend that InfoProvider has size of 10 GB in total. Results of such(what is such ) split would be in our example as followsfollowing:
- 0CURRENCY - EUR - 1 GB
- 0CURRENCY - USD - 3 GB
- 0CURRENCY - NZD - 3 GB
- 0CURRENCY - JPY - 2 GB
- 0CURRENCY - CHF - 1 GB
As we don't dont want to see results for all available distinct currencies separately, sepparatly we have defined 3 data groups (See step 1 above). The previous results are will be assigned to the specified appropriate data groups based on the selection defined for them./ definition
- Data group 1 - data with 0CURRENCY EUR belongs will belong here (1 GB).
- Data group 2 - data with 0CURRENCY USD belongs will belong here (3 GB).
- Data group 3 - groups will group all other data (6GB).
After execution of ... collector , we can view see in Fiori front-end frontend three columns for Data Group sizes and three columns for Data Group usages and not other columns for all distinct values/ currencies. The grouping makes it possible to focus on the usage/ analysis values sepparatelly. This way we can only focus on usage of data that are important for us. big screen
Restricting
...
InfoProviders to be
...
analyzed
As it is not always necessary needed to analyze analyzed all InfoProviders based on a some characteristic. You can restrict for which InfoProviders the Data each data distribution analysis should be executed. To restrict a specific analysis you need to change the input table "/DVD/HS_IT_DU2" of ... collector in the following way:
- Add a new row to the table with the following content (append or where)
- Subgroup ID - ID of Data data distribution analysis for in which you want to restrict InfoProviders which schould to be analyzed,
- Number - Unique number for each new line in the table
- Object type - INFOCUBE, DSO or ADSO - for type of InfoProvider which selection should be restricted.
- Select option - Standard select option format to filter on technical name on InfoProvider
- Bellow is an example of new rows that we would add to restrict our CURRENCY Data data distribution analysis to analyze all DSO and ADSO InfoProviders in the system but only one InfoCube with technical name "/DVD/IC_CUBE"
Additional Time Characteristics AnchorAdditional Time Characteristics Additional Time Characteristics
Additional Time Characteristics | |
Additional Time Characteristics |
"Standard" Data data distribution analysis can be enhanced on monitored system v to take into account not just standard time characteristics (already present) but also additional ones. The only Only requirement for adding a additional time characteristic to the analysis is that its values must contain a year value in the standard format YYYY somewhere. Additional time characteristics are specified are specified on monitored / satellite and not central system. - aktiv
For their specification you must execute the report "/DVD/HS_SET_ADD_TIME_CHAR" or the transaction /DVD/HS_ADDTCHA. After execution an ALV table is displayed. In this table you can add rows . Each while each row defines one additional time characteristic , which may to be used in .. analysis.
In the first column you specify the technical InfoObject name and second column the contains position of the year value in standard format YYYY in values of characteristic. What is it? After specification of the additional time characteristic click .Navigational attributes(not too much tech?) Navigational attributes can be also defined as an additional time characteristic.
...
characteristics
...
.
...
Examples of viable additional time characteristics are:
InfoObject: 0BIRTHDAY Year Value Position: 1 - example of characteristic values: 20160101, 20170101, 20171231
...
InfoObject: ZDVD_FXYEAR Year Value Position: 4 - example of characteristic values: BCD2016, BCD2017, DGG2017
Info |
---|
Order in which additional time characteristics are defined in table is important. As during data distribution analysis characteristics defined on top will have higher priority to be used than the ones defined bellow them. |
After specification of additional time characteristic you can save their definition by clicking on save button in toolbar.
Info |
---|
Additional Time characteristics are will be used during durring next size recalculation. ???? Size recalculation isn't performed for is not done each collector run , but only once per a specific time period. The , default parameter is 14 days. |
Data distribution analysis customization
"STANDARD" Data data distribution analysis analsysis can be customized according to your requirementto fullfil user's specific needs. By default, analysis is providing following 6 data groups, in which group where data sizes and usages are will be distributed in ascending order:
...
e.g. <=2013, 2014, 2015, 2016, 2017 ,>=2018
You can change this behavior This behaviour can be changed by using the expert settings (transaction transacation /DVD/RL_SETT_EXPERT) with the Tool tool name 'HM_BW' by following parameters:
co za tabulka
Parameter technical name | Default value | Description |
---|---|---|
HM_BW_STD_DATA_GROUPS_ASC | X | Set whether data groups are will be displayed in ascending order |
HM_BW_STD_DATA_GROUPS_NUMBER | 6 | Set how many data groups are will be created including current year. e.g. If if you put put here 7 following data groups will be created (consider 2018 as current year) <=2012, 2013, 2014, 2015, 2016, 2017 ,>=2018 |
Data groups are will be re-created during the next collector execution (e.g. with the HMBW_1DAY monitoring profile).
...