èAn InfoProvider is an object for which queries can be created or executed in BEx. InfoProviders are the objects or views that are relevant for reporting.
èTypes of InfoProviders:
l MultiProviders
l InfoSets
l Remote Cube
l SAP Remote Cube
l Virtual InfoCube with Services
MultiProvider
•A MultiProviders is a type of InfoProvider that combines data from a number of InfoProviders and makes it available for analysis purposes.
•The MultiProviders itself does not contain any data. Its data comes entirely from the InfoProviders on which it is based. MultiProviders only exist as a logical definition. These InfoProviders are connected to one another by a union operation.
•A query based on a MultiProvider is divided internally into subqueries. There is a subquery for each InfoProvider included in the MultiProvider. These subqueries are usually processed in parallel.
lInfoProvider A contains sales actuals. InfoProvider B contains sales plan data. One can combine the two InfoProviders into one MultiProvider to compare actual vs plan sales.
•One can combine InfoCube, ODS objects, InfoObjects and InfoSets in a MultiProvider.
•A union operation is used to combine the data from these objects into a MultiProvider.
•Here, the system constructs the union set of the data sets involved. In other words, all values of these data sets are combined.
Infosets
èThe Infosets offers a semantic view of certain Infoproviders and joins between them. In SAP NW2004s there are performance and usability improvements, as well as the ability to now include Infocubes in Infosets
èInfoSet as InfoProvider
lThere is no physical data storage on InfoSets – a semantic view of DataStore objects, InfoObjects and InfoCubes that allows you to create reports on these objects, particularly on the joins between these objects.
lThere is a new transaction available: RSISET
èSome more new functionality enhances the object:
lInfoCubes are possible for joins.
lTime dependencies can be defined for DataStore Objects and InfoCubes to treat these objects in a way as time dependent attributes.
lSome additional functions are enhanced within the InfoSet Builder.
èSlow-Seller Analysis
lFind articles that have not been sold (àleft outer join of master data to DataStore details)
èJoins Vs Union
lCombining infocubes and details DataStore Objects in a Multiprovider (à Union) can lead to several # lines in the BI application( If a value is available in only one Infoprovider)
lCombining Infocubes and detailed DataStore Objects in an Infosets (àJoin) only combines values that exist in both the Infocube and DSO.
èTransitive Attributes
lBusiness partner is the (consolidated) Infoobject which references infoobjects Vendor and Customer etc. If you want to use attributes of ‘Customer’ in infocubes containing ‘business partner’, we can able to model this via Infosets.
èTemporal join
lHR reporting : Show employees and their assigned organizational unit using time-dependent master data.
0 comments:
Post a Comment