SAP Business Information Warehouse Reporting in Microsoft Office

Generation Code 39 Full ASCII in Microsoft Office SAP Business Information Warehouse Reporting

SAP Business Information Warehouse Reporting
Code 39 Extended Reader In None
Using Barcode Control SDK for Microsoft Office Control to generate, create, read, scan barcode image in Microsoft Office applications.
Generating ANSI/AIM Code 39 In None
Using Barcode maker for Microsoft Office Control to generate, create Code 39 Full ASCII image in Microsoft Office applications.
to you. There are definite uses for both approaches to viewing the data, and identifying them initially will save you tons of time during the reporting process. Now, let s view the data in the InfoCube. The following illustration shows the data stored in the InfoCube, which we will be using for this example. This will be the only data we use during the examples. As you can see, the information is sliced for the periods January 2000 and February 2000, and there are two material groups Food and Chemicals. Notice that the group for the material BBB changed between January and February from the Food group to the Chemicals group. It therefore has a different posting for each month. We will talk more about the materials in the next section. We will execute some basic queries against this information and look at the differences in the data views.
Read USS Code 39 In None
Using Barcode decoder for Microsoft Office Control to read, scan read, scan image in Microsoft Office applications.
Code 3 Of 9 Drawer In C#
Using Barcode creation for .NET framework Control to generate, create USS Code 39 image in .NET applications.
Copyright by SAP AG
Print Code 39 In .NET Framework
Using Barcode encoder for ASP.NET Control to generate, create Code 39 image in ASP.NET applications.
Code39 Printer In Visual Studio .NET
Using Barcode generation for Visual Studio .NET Control to generate, create Code 3 of 9 image in Visual Studio .NET applications.
Historical View
Drawing Code 39 Extended In VB.NET
Using Barcode generation for .NET framework Control to generate, create Code-39 image in Visual Studio .NET applications.
Create ANSI/AIM Code 39 In None
Using Barcode printer for Microsoft Excel Control to generate, create Code39 image in Office Excel applications.
Now, let s say that the business user design documentation requires that we show the historic view, or the view of the data as it was posted. This is required due to the changes that occur in the relationships between the characteristic values. Therefore, we need to data model our InfoCube to reflect this request. This is done by taking the two characteristics that are required to be used in the historic view and using them in the InfoCube as unique characteristics in the dimension of the InfoCube. This is exactly what we have done to obtain the required results. The following illustration shows this configuration.
Creating Code 128 Code Set A In None
Using Barcode maker for Microsoft Excel Control to generate, create Code 128 Code Set A image in Excel applications.
EAN-13 Supplement 5 Drawer In VS .NET
Using Barcode encoder for Visual Studio .NET Control to generate, create GS1 - 13 image in .NET applications.
Copyright by SAP AG
Code 128B Generation In Objective-C
Using Barcode generator for iPad Control to generate, create Code-128 image in iPad applications.
Bar Code Maker In VS .NET
Using Barcode drawer for Reporting Service Control to generate, create bar code image in Reporting Service applications.
13:
Drawing GS1 - 13 In Java
Using Barcode creation for BIRT Control to generate, create EAN 13 image in Eclipse BIRT applications.
Make Code-128 In None
Using Barcode printer for Online Control to generate, create Code 128C image in Online applications.
Advanced Reporting Processes and Functionality
Reading Code 3/9 In None
Using Barcode reader for Software Control to read, scan read, scan image in Software applications.
Bar Code Printer In C#.NET
Using Barcode creation for .NET Control to generate, create bar code image in VS .NET applications.
Now that we have created this linkage in the InfoCube, we can view the information in the query and see what it shows us. Remember that we need to show the historic view of the data. Therefore, we need to review the new product EEE and notice the changes between the months of January and February for this new product and the changed material group for material BBB. In the following illustration, you see the initial configuration of the query on this InfoCube. Notice that we have set the key date as 01.01.2000.
Recognizing Code 128C In VB.NET
Using Barcode scanner for .NET Control to read, scan read, scan image in .NET applications.
Barcode Maker In Java
Using Barcode encoder for Android Control to generate, create barcode image in Android applications.
Copyright by SAP AG
Bar Code Maker In None
Using Barcode printer for Font Control to generate, create bar code image in Font applications.
ANSI/AIM Code 39 Encoder In Objective-C
Using Barcode maker for iPhone Control to generate, create Code 39 Extended image in iPhone applications.
The results of the query are shown in the following illustration.
Copyright by SAP AG
Now, we can go back to the Query Designer and change to key date to 01.02.2000 for February of 2000 and rerun the query. The following illustration shows the Information section of the selections once the query has been executed (notice the Key Date field, which shows 01.02.2000). We can see that the view of the data hasn t changed and that the actual
SAP Business Information Warehouse Reporting
posting process is shown regardless of whether we have the key date set for January or February of that year.
Copyright by SAP AG
This is one approach to showing the historic view of the data and probably the easiest. Therefore, data modeling the relationship into the dimensions in the InfoCube will offer you the historic view of your data.
Current View Now, let s assume that the business requirement for viewing the data is based on the current look of the information. We are now faced with a different challenge. We need to be able to show all the transactions based on the current view of the information, so we ll use a different approach to try to get this view. We need to use a navigational attribute for the material group so that we can reflect the current view of the postings. Therefore, we need to step back into the configuration of the InfoObject material and set the attribute Material Group to be navigational, as shown next.
Copyright by SAP AG
13:
Advanced Reporting Processes and Functionality
We can accommodate the business user by having the material group as a characteristic in the InfoCube and also setting the same InfoObject as a navigational attribute and collecting the data in that manner, thus fulfilling the business requirements for this view of the data. As you can see, the data in the InfoCube has been enhanced by the addition of the navigational attribute (in dark shaded column) in the view of the record. Notice that material BBB, which was in the material group Food before, is now pointed toward the material group Chemicals for the navigational attribute. Therefore, this will show in the query in the Chemicals group instead of the Food group.
Copyright © OnBarcode.com . All rights reserved.