The BW statistics provide us with the information on technical content and runtime of a query or an info provider.
On clicking on the status definition tab, you will be able to see the query and info provider names along with author name and the last changed date and time. If the statistics on/off column shows ‘D’ it is the default setting or if it shows ‘X’ it means statics data on and if the column is blank it means it has statics data off.
You can drill down on the settings drilldown box if you choose to view only query and info providers that have statics data on or off or with the default setting.
You can also view only aggregated data or choose only frontend /calculation layer date where the system writes only the general data manager event 9000 in the OLAP context as well as the aggregation information or choose to display all data from the area for the front end and calculation layer by choosing all or no data where the data record for the BEX Web templates and workbooks are stored.
Query runtime statics creates a large amount of statistical data so, you can choose to delete the statistical data by click on the delete statistical data button.
A pop up will appear where you can select which all tables to delete and choose how many day’s data you want to keep in the system. We can deactivate the query and info provider which have their statics data maintenance on by clicking on the deactivate statistics button.
Datastore objects runtime parameters
Datastore objects runtime parameters help us to make a number of changes to ADSO’s runtime properties and give fixed values to general properties to improve performance.
On clicking datastore object runtime parameters tile, you will able to see all the ADSO in the system from which you select the ADSO for which you need to improve the performance.
Below is the area where you can choose to change.
- Generic settings: you can choose to edit the number of records in each data package, SID creation and you can define the wait time for activation and rollback.
- Expert setting: you can choose to edit the number of packages, can choose either standard or full table scan or antijoin or distinct value for SID scan in data store context, you can enable or disable supress option and choose to either compress or decompress change clog.
- Process settings: you choose to run the activation/rollback/SID generation process in either dialog or background, how many numbers of the process can run at a time and can also choose the server group by clicking on the edit button.
You can discard the changes that you have made to the ADSO’s particular parameter setting by clicking on the back to the standard button. If you want the entire ADSO’s parameter setting back to system default you can click on the change default button.
BW workspace is a dedicated area where new models can be created based on central BW and local system.in a workspace, we define setting such as lifetime, maximum disk space and the BW Info Providers.
The below are steps to create/edit workspace in B4HANA cockpit.
Step 1: enter the name of workspace and click on create.
Step 2: Enter a suitable description
Step 3: Settings tab
In the settings section under the general settings, you can mention the expiry date for the workspace once the expiry date is exceeded the workspace will not be available. You can mention the prefix for the workspace and all the object created under this workspace will automatically follow this prefix. You can also mention the contact of the developer who needs to be contacted if the workspace encounters any errors.
In the settings for main info provider section, we need to mention the main provider for the workspace in the settings for local providers/Data section, you can mention the number of providers and maximum memory space for the data in the workspace .for every data source a provider is created.
In the setting for the provider and workspace query section, you select what kind of data is allowed.
If local master data values allowed is checked it allows entering data which is not present in the master while loading data. If non-unique join column allowed is checked then it allows multiple key figure columns to be created in the composite provider joins. If the queries on non-workspace provider allowed are checked then you can create a query in the workspace which uses an info provider that does belong to the workspace. If analysis authorization restricted is checked then there is a restriction on who can view and access the data and the providers.
Step 4: Central provider tab
In this tab, you can choose the provider from the BW repository and add it to the main info provider. You can check on the usable checkbox if you want the datastore object, key figure and characteristics to be used for modelling in the workspace.
Step 5: Submission targets provider
In this tab, you choose the info provider to transfer data to central BW info providers. There are 2 properties writable and mandatory that you can enable and disable for each object you drag and drop. Provider submission setting button allows you to specify whether the data should be transferred data after activation along with filters.
In the local provider’s tab, you will see the list of local provider created during the data load along with its statuses such as whether the info provided is active or inactive or with errors, its memory consumption, number of records and last access information.
In the local composite provider’s tab, you will see the list of composite providers created in the workspace designer along with its active/inactive status.
In the local data tab, you will see the list of local characteristics and hierarchies created in the workspace designer along with its active or inactive status, changed on, at and by whom information.
In the workspace queries tab you will see the list of queries created in the workspace designer along with its active or inactive status, changed on, at and by whom information.
In the user tab, the list of users who are authorised to use and edit in the workplace are mentioned.
Step 6: Check and activate the workspace. Only the active workspace can be used in the workspace designer.
Customization– Edit Projects
There are 2 types of customising project in SAP they are:
- SAP System implementation – The administrator determines the scope of the project by selecting the countries and function which they want to implement from the SAP reference IMG.
- System and Release Upgrades – The administrator release specific project views on a customized project for and changed functions.
In B4HANA cockpit the customization-edit project shows the list of projects available in the system.
The SAP Reference IMG button will give information about the general setting, notes available to be implemented,application-level details and full functionality details of the all possible sap customizations.
The IMG information button provides us insight us the Customizing activities available over the customized project.
In the project, the analysis button helps to view analysis of data activity and documentation types, progress control, the scope of one or more customizing project, analyses for a specific day or period. All this information is gathered by the status the developer enters and the result is more accurate only when the developer enters detailed information.
BW search allows you to perform a search in the metadata of the objects and a search for connections between these objects in the where-used list.
In B4HANA Cockpit click on the BW search tile and enter the TLOGO object name in the metadata object search box.
And click on the go button, the object is displayed along with active/inactive status, description and where used list option.
You can either choose to click on the result show where used list or the tab, where used list gives us information about the TLOGO object dependent the main TLOGO object with its association type.
BW search maintenance
The BW search maintenance tile in B4HANA cockpit show us all the TLOGO object available along with overall status, view status, database status, authorizations, last changed and last deployed details.
You can click on a TLOGO object and check if any inconsistency exists and choose to activate or deactivate it. By clicking on the show association button, you can view its associated types.
BW Search Configuration
- BW search configuration gives us information about the status of the BW search, a number of logo objects, meta-view and where-used list. Here you can edit the basic settings and buffer setting for the BW search.
The overall status indicates whether the BW search is active or inactive.
The shared buffer status shows us whether the buffer is completely available where search details are stored in application server of shared buffer to improve performance when called multiple times., partially available wherein only the metadata of the TLOGO is written to the buffer or not available where all the data is read from the database directly.
You can change the configuration for BW search by click on edit. In the basic setting, you can enter any other package if you do not want the standard sap package and change the buffer time before the system checks for any views.
In search runtime setting, you can choose to store the runtime information and message of each application log. In general buffer setting, you can disable the buffer, mention how long the buffer should hold on to the values before refreshing it and maximum number entries the buffer should hold.
In the detailed buffer setting, you choose to restrict data on the buffer by choosing either to write all the data or only the processed input or generated SQL statements or generated field list or result tables. After configuring the BW search according to your preference click on save.