Copyright by SAP AG in Microsoft Office

Drawing Code 3/9 in Microsoft Office Copyright by SAP AG

Copyright by SAP AG
Reading Code-39 In None
Using Barcode Control SDK for Microsoft Office Control to generate, create, read, scan barcode image in Microsoft Office applications.
Make Code 39 Full ASCII In None
Using Barcode generator for Microsoft Office Control to generate, create USS Code 39 image in Microsoft Office applications.
FIGURE 2-15 InfoObject Master Data/Texts tab for the eld entry for InfoArea
Code 39 Extended Reader In None
Using Barcode reader for Microsoft Office Control to read, scan read, scan image in Microsoft Office applications.
Print Code 39 Full ASCII In Visual C#.NET
Using Barcode encoder for VS .NET Control to generate, create Code 3/9 image in Visual Studio .NET applications.
SAP Business Information Warehouse Reporting
Code39 Printer In VS .NET
Using Barcode encoder for ASP.NET Control to generate, create Code39 image in ASP.NET applications.
Code39 Maker In VS .NET
Using Barcode creation for VS .NET Control to generate, create Code 39 Extended image in .NET framework applications.
Copyright by SAP AG
Code 3/9 Creator In VB.NET
Using Barcode maker for Visual Studio .NET Control to generate, create USS Code 39 image in .NET applications.
DataMatrix Drawer In None
Using Barcode encoder for Font Control to generate, create Data Matrix ECC200 image in Font applications.
FIGURE 2-16 InfoObject used as an InfoProvider in Query Designer view
Make Data Matrix ECC200 In None
Using Barcode encoder for Online Control to generate, create ECC200 image in Online applications.
Bar Code Generator In Java
Using Barcode generation for Java Control to generate, create bar code image in Java applications.
requirement. For example, let s suppose we would like to create a report that uses time to integrate with the General Ledger accounts and generate a report for the AR/AP aging process. We would not be able to do that type of reporting on a specific InfoObject, so we need to organize an InfoSet to accomplish this. We will discuss the required fields for an InfoObject that are of interest to business users later in this chapter. As a summary of the functionality of the DataStore object and the InfoCube, refer to Table 2-4.
Barcode Scanner In Visual C#.NET
Using Barcode reader for .NET Control to read, scan read, scan image in .NET applications.
ECC200 Generation In None
Using Barcode generation for Software Control to generate, create Data Matrix image in Software applications.
Non Data Targets
Bar Code Creation In Java
Using Barcode encoder for BIRT Control to generate, create bar code image in BIRT reports applications.
Code39 Encoder In Visual Studio .NET
Using Barcode generator for ASP.NET Control to generate, create Code 39 Full ASCII image in ASP.NET applications.
Non Data Targets are those InfoProviders that are created to be used as a view of the data from other sources. Therefore, as the naming convention suggests, these InfoProviders do not hold any data but rather create a union or join of the data during the query execution process. The architecture of these InfoProviders is unique for this purpose. As mentioned before, the Data Target InfoProviders are only able to show you events that have happened, but with Non Data Targets you have the ability to create combinations so that additional reporting requests can be satisfied. The types of Non Data Targets are MultiProviders, InfoSets, Virtual InfoProviders, and InfoSet Queries. We will discuss each of their advantages as we work through these InfoProviders.
Recognize ECC200 In Java
Using Barcode reader for Java Control to read, scan read, scan image in Java applications.
Making EAN 128 In None
Using Barcode creation for Online Control to generate, create EAN 128 image in Online applications.
2:
Bar Code Creator In Visual Basic .NET
Using Barcode maker for .NET framework Control to generate, create barcode image in VS .NET applications.
GS1 - 12 Scanner In C#
Using Barcode scanner for VS .NET Control to read, scan read, scan image in .NET framework applications.
Storing the Data SAP/Business Warehouse InfoProviders
Code 128 Code Set A Maker In Objective-C
Using Barcode creation for iPad Control to generate, create Code-128 image in iPad applications.
GS1 128 Generator In Objective-C
Using Barcode drawer for iPad Control to generate, create USS-128 image in iPad applications.
Object/Property Method/purpose
DataStore Object Harmonization/consolidation and mass storage (as part of the warehouse data layer of an EDW architecture) Storage for transaction data and, less often, consolidated master data: permanent, one to ten years Cleansed data (source system independent) Change/Add/Delete Relational DB tables, normalized, records have business meaningful keys High data granularity (flat reporting)
InfoCube Aggregation/optimization of query performance
Data storage
Storage for transaction data: permanent, five to ten years Cleansed data (source system independent) Add BW extended star schema: denormalized Low data granularity (multidimensional reporting)
Source of data Manipulation Architecture Reporting
TABLE 2-4 Comparison of DataStore Object and InfoCube Parameters
MultiProviders
A MultiProvider is a type of InfoProvider that combines data from a number of InfoProviders and makes it available for analysis purposes. The MultiProvider itself does not contain any data. Its data comes entirely from the InfoProviders on which it is based. These InfoProviders are connected to one another by a union operation. A MultiProvider can consist of different combinations of the following InfoProviders: InfoCube, DataStore object, InfoObject, InfoSet, Virtual Provider, and aggregation level. Figure 2-17 shows an example of the combinations possible. A union operation is used to combine the data from these objects in a MultiProvider. Here, the system constructs the union set of the datasets involved; all the values of these
FIGURE 2-17 MultiProvider graphical model view
MultiProvider
Do not Contain Data
Contain Data
Virtual Providers
InfoCube
InfoObjects
DataStore Objects
Copyright by SAP AG
Aggregation Levels
InfoSets
SAP Business Information Warehouse Reporting
datasets are combined. As a comparison, InfoSets are created using joins. These joins only combine values that appear in both tables. In contrast to a union, joins form the intersection of the tables. In a MultiProvider, each characteristic in each of the InfoProviders involved must correspond to exactly one characteristic or navigation attribute (where available). If this is not clear, you have to specify the InfoObject to which you want to assign the characteristic in the MultiProvider. You do this when you define the MultiProvider. It is important that in the process of creating a MultiProvider you have at least one characteristic that is in both tables so that a successful set of combinations can be generated. For example, if you have DataStore objects one with sales order data, one with billing data, and another with delivery data and you are using these in a MultiProvider, it s very important that a characteristic that s an intersection of all DataStore objects be available (such as sales order number) so that the information generated will have a unique value that can be linked. As another example, suppose you have actual data in one InfoCube and planned data in another InfoCube, and you have to report on the data in combination/comparison. The answer is to build a MultiProvider to offer you information from two separate InfoCubes. The underlying concept here is that a query can only be created based on one InfoProvider, but with a MultiProvider you can create a query on many InfoCubes via the structure of the MultiProvider. Attempting to organize the information into a query without a characteristic that is the same in both InfoCubes would be difficult, if not impossible. In Figure 2-18, you can see that during the
Copyright © OnBarcode.com . All rights reserved.