SAP Business Information Warehouse Reporting in Microsoft Office

Drawer Code39 in Microsoft Office SAP Business Information Warehouse Reporting

SAP Business Information Warehouse Reporting
Decoding Code 39 Full ASCII In None
Using Barcode Control SDK for Microsoft Office Control to generate, create, read, scan barcode image in Microsoft Office applications.
Code39 Generator In None
Using Barcode maker for Microsoft Office Control to generate, create ANSI/AIM Code 39 image in Microsoft Office applications.
Reporting
Code 39 Decoder In None
Using Barcode reader for Microsoft Office Control to read, scan read, scan image in Microsoft Office applications.
Encode Code 39 In C#
Using Barcode generation for .NET framework Control to generate, create Code39 image in VS .NET applications.
Manual Planning
Code-39 Maker In Visual Studio .NET
Using Barcode creator for ASP.NET Control to generate, create ANSI/AIM Code 39 image in ASP.NET applications.
ANSI/AIM Code 39 Printer In Visual Studio .NET
Using Barcode maker for .NET Control to generate, create Code 3/9 image in .NET applications.
Planning Functions
Painting Code 3/9 In VB.NET
Using Barcode creator for .NET Control to generate, create USS Code 39 image in VS .NET applications.
Barcode Reader In Java
Using Barcode Control SDK for Java Control to generate, create, read, scan barcode image in Java applications.
Aggregation Level
Drawing Linear 1D Barcode In .NET Framework
Using Barcode printer for ASP.NET Control to generate, create Linear Barcode image in ASP.NET applications.
Drawing Matrix Barcode In .NET
Using Barcode printer for VS .NET Control to generate, create Matrix Barcode image in .NET applications.
Data Transfer Process Actual Plan
Encoding Barcode In Objective-C
Using Barcode generation for iPad Control to generate, create bar code image in iPad applications.
Recognizing Bar Code In VS .NET
Using Barcode Control SDK for ASP.NET Control to generate, create, read, scan barcode image in ASP.NET applications.
Data Load
Recognizing DataMatrix In None
Using Barcode decoder for Software Control to read, scan read, scan image in Software applications.
Generating Bar Code In Objective-C
Using Barcode drawer for iPhone Control to generate, create bar code image in iPhone applications.
Copyright by SAP AG
Paint Code 3 Of 9 In VS .NET
Using Barcode creation for ASP.NET Control to generate, create ANSI/AIM Code 39 image in ASP.NET applications.
Creating GTIN - 13 In None
Using Barcode generation for Software Control to generate, create EAN13 image in Software applications.
FIGURE 17-19
Bar Code Decoder In VB.NET
Using Barcode Control SDK for .NET Control to generate, create, read, scan barcode image in .NET applications.
DataMatrix Generation In None
Using Barcode printer for Excel Control to generate, create ECC200 image in Excel applications.
Con guring the IP architecture using two InfoCubes
Printing Code-39 In Java
Using Barcode generator for Java Control to generate, create Code-39 image in Java applications.
Recognizing Barcode In Visual Studio .NET
Using Barcode reader for Visual Studio .NET Control to read, scan read, scan image in VS .NET applications.
NOTE Remember that during this process, we are switching the functionality of an InfoCube from
being available for uploading to being available for planning and yet not changing the type of the InfoCube.
InfoProvider
Based on these different scenarios, we can see that there needs to be a Real-time InfoCube and an aggregation level involved in the architecture somewhere. In terms of these two objects, we went over the basics in 2. However, one additional item needs to be
Manual Planning
Reporting
Planning Functions
Aggregation Level Actual Data
Plan Data
Data Load
Copyright by SAP AG
FIGURE 17-20 Con guring the IP architecture using one InfoCube
17:
Other Options with the Analyzer
brought to your attention, at the minimum, concerning the functionality of the Real-time InfoCube. Once there are postings from the user interfaces into the InfoCube, the data is saved in request IDs. These request IDs are a bit different from those generated when the data is uploaded into the InfoCube via the normal structure and process. The data is posted into the InfoCube (fact table) and the request ID is yellow (not green) at this point. This is not a problem or an issue, unlike what you would be going through if this were to have happened with a normal upload. The request ID stays yellow until there are a total of 50,000 records in that one request. Once that number of records is hit, the InfoCube will automatically generate another request ID and that one will be yellow, as shown in here.
Copyright by SAP AG
Suppose you are posting data and the total record count in the current request ID is 49,950. You post 100 records. All 100 records will be posted to that request ID and then another one will be generated. I bring this up for the following reason: If you are reporting on this InfoCube and there are yellow requests, the data within that request ID will not be available for reporting because the reporting flag can t be displayed for a yellow request. Therefore, you will need to include a specific standard-delivered variable in your query configuration to make sure you show all the data within your InfoCube, including the data in the yellow request ID, as shown here. This variable can be inserted into the Filter section of the BEx Query Designer, and this will allow the query to read the yellow request ID data. Specifically, variables 0S_RQMRC (Most Current Data) and 0S_RQTRA (Most Current Data Transactional InfoCube) are the ones available.
SAP Business Information Warehouse Reporting
NOTE You can also change the read mode of the query in transaction RSRT to allow the display of
all the data in the InfoCube, whether the request ID is open or closed. This is more of a technical solution, but is available nonetheless.
Copyright by SAP AG
Planning Modeler
Now we move into the basic components of the IP architecture. This involves the Planning Modeler and the location where all the objects specific to IP are created. The aggregation level, filter, planning functions, and planning sequences are created in the Planning Modeler. A basic diagram of the connections between each of these objects is shown in Figure 17-21. As you can see, the Real-time InfoCube is used as the basis for the aggregation
Real-time InfoProvider
Aggregation Level Filter Filter BI Integrated Planning
Copyright by SAP AG
FIGURE 17-21 Object architecture of IP
17:
Other Options with the Analyzer
level, and from this level the filter is built. We then use the filter as a basis for the planning functions. The planning sequences are groupings of planning functions. We will work through a high-level discussion of these objects because they will be configured by the IP group or other business users involved with the planning process, so it is important that you have an understanding of these objects when interacting with them. An example of the Planning Modeler is shown in Figure 17-22. This figure shows the initial execution of the transaction code RSPLAN to access the Planning Modeler. As you can see, there are two options to start the planning process: Start Modeler and Start Wizard. The wizard steps you through setting up the IP process, and the Modeler offers all the same options but you drive the process. We will look at the Modeler in this case. Once you click Start Modeler, you enter a web-based configuration screen. The Modeler offers a full web-based configuration process. The following illustration shows the results of this activity. As you can see, the request for an InfoProvider field is available. We will review the InfoCube U_AMER_1A, which is the underlying InfoCube for the example we reviewed previously for the cost and sales planning. Notice that all the activities are available from this view. Once you have identified the InfoCube to use, the process moves to the Aggregation
Copyright © OnBarcode.com . All rights reserved.