Master data modeling should be done is such a way that it is integrated across various modules. For example, there is only one customer for entire business regardless of module whether AR or Sales etc.
The master data info objects should be checked against business content and existing objects. If there are already existing objects which fulfill your requirement, then you should avoid creating new objects.
You can use the SAP metadata repository to search for the business content and existing objects.
Options for Modeling Dependent Attributes
Continue reading “BW Development Standards Part 4: Master data Modeling”
SAP BW Modeling:
Multiproviders must always be used as a base for the query.
Every MultiProvider includes a characteristic called InfoProvider (0INFOPROV) in the data package dimension.
Queries can filter on this characteristic to restrict access to one or more specific underlying InfoProviders.
If your MultiProvider definition includes a large number of underlying InfoProviders (such as one per year, one per division, etc.) you can improve query performance by dynamically filtering on the 0INFOPROV characteristic.
A customer exit variable provides a flexible way to Continue reading “BW Development Standards Part 3: Data Modeling in Multiproviders and Infocubes”
LSA stands for ‘Layered Scalable Architecture’. This is followed as a general thumb rule in BW systems running on Oracle database. With the advent of HANA, LSA is now replaced with LSA++
Below is the generic LSA architecture details and guidelines.
Data Acquisition Layer
This layer is the first layer of write-optimized DSOs which have raw data coming from the source.
This layer can be skipped if not required as Continue reading “BW Development Standards Part 2: LSA”
In large projects as well as small implementations, it is always be required of the Developer to follow certain standards.
The client will share his/her own set of standards to the developer before the start of the project.
However there are certain set of generic standards to be kept in mind as a good developer.
Whenever your design needs deviating from the said standards, you need to Continue reading “BW Development Standards Part 1: Architecture”
The number of times users have seen the BI reports can be analyzed in BW. All of this information is recorded as BW statistics automatically by the system provided the setting is activated for the targets.
The data where the information is stored is the cube 0TCT_C01 [Front-End and OLAP Statistics (Aggregated)].
This cube is SAP standard cube and holds the usage statistics data. This comes under Technical Content info area in BW.
The main info objects in the cube and their functions / meanings are summarized below- Continue reading “How to know the Query Usage Statistics in BW”
The sales order status should appear correctly in the BI reports after the daily refresh.
Otherwise the order qty will appear for example under both open and billed and the total order qty will hence show doubled in the sales report.Or, it may happen that the processed orders are not shown in the report.
You will encounter many tickets in SAP BW relating to order status issues. Mostly the tickets will be high priority (either P1 or P2)
In my experience, I have encountered a scenario where order status is a time independent navigational attribute of sales document.
Thus order status was a part of sales order master data.
Technically, status was residing in ‘X’ table of the info object sales order in the back-end BW database.
The business scenario was like below-
- There was a process chain updating the master data of the sales order and rolling these values to BW accelerator.
- Then, the delivery and billing transaction process chains were running. This transaction data was also loaded to BW accelerator.
- When the BI reports were run, the order status shown was not correct or the processed orders were not shown at all in the report.
Continue reading “Sales Order Status not updating in BW system with BWA”
Looking up a table while doing data load is a common scenario in SAP BW.
Here the look up table can be active table of some other DSO.
You can note a point here that cube cannot be used for look up. This is because, a cube has a fact table which is based on star schema. Hence the primary keys in a fact table will be dimension ids instead of the primary key values.
Now coming to our scenario, suppose data is loaded from DSO1 to CUBE1. Continue reading “How to write ABAP routine to look up a DSO Active table”
OEE stands for ‘Overall Equipment Efficiency‘. These reports are required in manufacturing companies to track the machine efficiency and performance in terms of quality and availability.
The efficiency is measured per line (machine) or per material.
OEE calculation has three different metrics: availability, performance and quality.
Generally, OEE is reviewed on a weekly basis as KPI.
Most important, OEE is used to analyze the reason of Continue reading “What are OEE reports in BW/BI?”
Below are some of the HR reports used in BW/BI. These will help you to understand what kind of reports companies want out of their HR data-
Report Name –
Headcount / FTE Report
This report is used to count Continue reading “HR reports in BW/BI”
The companies mainly in the manufacturing business require to see the material master data of their inventory stock after the sales and delivery is done for a period.
These reports mainly show the details of a material produced by the company like Continue reading “What is Material Master Data report in BW/BI?”