Infoset and virtual infoprovider

dear all,
a short and simple question, can infoset include virtual infoprovider? if not, what are the work around for this? Thanks.

nope you cant, only standard infocube.

Similar Messages

Difference between General remote cube and virtual infoprovide with service

Hi guys,
I could not understand the difference between general remote cube and virtual infoprovider technically. And I could not find the document about how to set general remote cube.
I only find the following sources.
http://help.sap.com/saphelp_nw2004s/helpdata/en/23/c0234239f75733e10000000a155106/frameset.htm
"In comparison to other VirtualProviders, this VirtualProvider is more generic. It offers more flexibility, but also requires a higher implementation effort.".
I am welcome your lecture. Especially I would like to know how to set general remote cube..
Kind regards,
Masaaki

Hi,
You better take a look on the link:
http://help.sap.com/saphelp_nw04/helpdata/en/8d/2b4e3cb7f4d83ee10000000a114084/frameset.htm
Remote cube uses BAPI
SAP remote cube uses the BW Service API functions of SAP system
In Virtual cube with services, The data source is a user-defined function module.
with rgds,
Anil Kumar Sharma .P

Virtual Infoprovider AND No Marker Update

Hi BW Experts,
I am unable to get an idea when i am reading the following concepts.
1. NO MARKER UPDATE
2. HOW TO CREATE VIRTUAL INFOPROVIDER
Can anyone tell me with example.
I have read forums but i could not get the correct information.
Thanks in advance.
Regards
Anjali

hi anjali i am giving data on wat u asked.pls tell me where u have problem.so that i can clarify you more
InfoProvider
Use
InfoProviders that contain real-time InfoCubes provide the data basis for BI Integrated Planning. Aggregation levels are a type of virtual InfoProvider and are created on the basis of a real-time InfoCube, or a MultiProvider that contains InfoCubes of this type. Aggregation levels are specifically designed so that you can plan data manually or change it using planning functions.
For more information about the types of InfoProvider, see:
●     Real-Time InfoCubes
●     MultiProvider
Integration
In the Modeling functional area of the Data Warehousing Workbench, you create InfoProviders as the data basis for BI Integrated Planning.
For more information, see InfoProviders, Creating InfoCubes, and Creating MultiProviders.
In the Planning Modeler, you select the InfoProvider that you want to use as the data basis for BI Integrated Planning. On the Aggregation Levels tab page, you create one or more aggregation levels for this InfoProvider.
For more information, see Aggregation Levels.
Prerequisites
You have created a suitable InfoProvider as the data basis for BI Integrated Planning and filled it with data.
Features
InfoProvider Selection
You can restrict the number of InfoProviders displayed by specifying the technical name or description or by making an entry for last changed by.
You can change, check and save the selected InfoProviders.
InfoObjects
On the InfoObjects tab page, the system displays the InfoObjects that belong to the InfoProvider (see InfoObject). They are listed in the following tables:
●     Dimensions, with the characteristics assigned to them
●     Navigation Attributesfor the characteristics contained in the InfoProvider
●     Key figures
Under Settings, you can choose to display additional columns.
Characteristic Relationships and Data Slices
In change mode you can define the permitted combinations of characteristic values in the form of characteristic relationships and create data slices for the data that you want to protect for real-time-enabled InfoCubes.
For more information, see Characteristic Relationships and Data Slices.
Default Key Date for Planning
On the Settings tab page in change mode, you can set a Key Date as the default key date for planning. If time-dependent objects, such as attributes or hierarchies, are used in objects of the planning model, you can always refer to the default key date for planning. In this way, you can ensure that a uniform key date is used in the planning model. The objects in the planning model that are relevant for this are characteristic relationships, data slices and parameters of planning functions.
if we choose NO MARKER UPDATE option when compressing non cummulative cube the reference point is not updated but the requests are moved to Request 0
reward me if u felt theses are helpfull to u.
and if not reply me where u are not getting.
thanks
karthikeya

What is Infoset and How to create

HI Experts
Can any one please explain me what is the purpose of INFOSET in BW
and how to create a info Set between A Info Object and Cube
Thanks

Dear bw user,
Check the below link
http://help.sap.com/saphelp_nw04s/helpdata/en/ed/084e3ce0f9fe3fe10000000a114084/content.htm
Purpose is,
1.To join required data from basic InfoProviders
2.This allows building a relational BI data model with unified views for reporting (seeveral InfoProviders,but only one view). Therefore, we recommend keeping data in smaller, basic InfoProviders that can be flexibly joined for reporting purposes.
3. To allow BEx Reporting on a DataStore object without turning the BEx Reporting indicator on
4. To evaluate time dependencies (for example, join time dependent master data InfoObjects)
5. To be able to create self joins and left outer joins
Creatind in simple steps
Infoset is a Virtual Infoprovider.
Click on InfoProvider under modeling in RSA1 > Select InfoArea > right click Create Infoset > give name and description.
Select the ODS / Master Data Object or more than one ODS and maintain the link.
Infoset works on Join operation.
you can include Infocube if it is BI 7.
chk this link...
http://help.sap.com/saphelp_nw70/helpdata/en/a3/96663bd194a978e10000000a11402f/frameset.htm
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/2f5aa43f-0c01-0010-a990-9641d3d4eef7
Aslo see this link contents
Creating InfoSets
Prerequisites
Make sure that the objects for which you want to define the InfoSet are active. Create any required InfoObjects that do not
exist already and activate them.
Instead of creating a new InfoSet, you can transfer one of the InfoSets that are delivered with SAP Business Content.
Procedure
1. You are in the InfoProvider tree of the Modeling function area in the Administrator Workbench.
Choose the Create InfoSet function from the context menu (right mouse-click) of the InfoArea in which you want to create an
InfoSet. You get to the Create InfoSet dialog box.
2. Type in the following information for your new InfoSet:
¡ technical name
¡ long description
¡ short description
3. In the Start with InfoProvider section, you determine which InfoProvider you want to use to start defining the InfoSet.
¡ Select one of the object types that the system offers you:
ODS Object
InfoObject
Choose an object.
If you want to choose an InfoObject, it must be a characteristic with master data. The system provides you with the
corresponding input help.
4. Choose Continue. You get to the Change InfoSet screen. For more information on editing InfoSets see Editing InfoSets.
When you create an InfoSet, the system generates a corresponding entry for this InfoSet in the subtree of the InfoArea. The
following functions are available from the context menu (right mouse-click) of this entry:
Change
Delete
Object overview
Editing InfoSets
Prerequisites
Before you can get to the screen where you edit InfoSets, the following prerequisites have to be met:
You have created a new InfoSet.
You have selected the Change function from the context menu of an InfoSet entry in the InfoProvider tree of the Modeling
function area in the Administrator Workbench.
You have called the InfoSet Builder transaction, and selected the Change function. You can find additional information
under Additional Functions in the InfoSet Builder .
Procedure
1. You are in the Change InfoSet screen.
Choose a layout for the InfoProvider tree:
InfoArea
InfoProviders Used
All ODS Objects
All InfoObjects
For more information on the screen layout, particularly the layout of the InfoProvider tree, see Screen Layout: Changing
InfoSets.
2. Use the function Where-Used List via AWB to determine which BW objects use the InfoSet that you have selected. You get to
the Administrator Workbench: Where-Used List screen. You are able to work out what would happen in the system if you made
changes to the InfoSet. This helps you to decide whether or not it is sensible to make these changes at this particular point
in time.
3. You define the InfoSet by inserting one or more InfoProviders into the join.
There are several ways of inserting an InfoProvider into the join control:
¡ From the InfoProvider tree:
§ In the InfoProvider tree, double-click on the entry that corresponds to the InfoProvider that you want to add to the join
control.
§ Use the drag-and-drop function to move the InfoProvider into position.
¡ Choose the Add InfoProvider function, to add a particular ODS object or a particular InfoObject independently of the
current layout of the InfoProvider tree. You get to the dialog box of the same name. Enter the data that the system asks you
for.
If you know the technical name of the InfoProvider that you want to add, this method is quicker than switching the layout of
the InfoProvider tree.
When this function is complete, the InfoProvider that you selected is displayed in the join control. For more information on
the structure of the join control, see Join Control.
4. Define the join conditions. For more information see Defining Join Conditions.
5. You can get general information such as object version, date created and date changed via Goto ® Global Settings. You can
also set the indicator Most recent Reporting for InfoObjects from here. You can find additional information under Most recent
Reporting for InfoObjects.
6. Via the button Documents, which appears on the pushbutton bar, you can access document editing for this InfoSet.
7. You can use Check to check the correctness of the InfoSet definition. The log display is shown in the screen area under
the join control.
8. Save the InfoSet. The log display is shown in the screen area under the join control.
9. Activate the InfoSet. After activation, the system executes the checks. The result of the activation is displayed in the
log in the screen area under the join control.
Additional Functions in the InfoSet Builder
You can also use transaction RSISET to call up the InfoSet Builder when you want to edit an InfoSet. Select the InfoSet that
you want to edit. Value help is available for this. Additional functions are also available to help you edit and manage your
InfoSet.
Compare
You use this function from the main menu to check if the InfoProviders used in the InfoSet have been changed and the InfoSet
needs to be adjusted as a result. For more information, see Matching InfoSets.
Jump to object maintenance
You use the InfoObjects and ODS Objects functions to jump to the maintenance screen for the InfoProviders included in the
InfoSet definition.
Info functions
There are various info functions on the status of the InfoSets:
The Object Catalog Entry
The log display for the save, activate, and delete runs of the InfoSet.
Display in tree
You use this function to display in a tree structure all the properties of the A version (active) of the selected InfoSet.
Header data
InfoProvider and its fields
On condition
Wherecondition
The display is empty, if no active version is available.
Version comparison
You use this function to compare the following InfoSet versions:
The active (A version) and modified (M version) versions of an InfoSet
The active (A version) and content (D version) versions of an InfoSet
The modified (M version) and content (D version) versions of an InfoSet
The Display InfoSet screen appears. Depending on which option you choose, the system displays either all of the differences
between the two versions of the selected InfoSet or all of the properties of both versions in a tree structure.
Transport connection using AWB
You use this function to transport an InfoSet into another system.
The Administrator Workbench: Transport Connection screen appears.
The system has already collected all the BW objects that are needed to guarantee the consistency of the target system.
InfoSet data display
You use this function to access the data target browser. If you have already loaded data into the InfoProviders included in
the InfoSet, you can display this data.
Delete
You use this function to delete an existing InfoSet.
Copy
You use this function to copy an existing InfoSet and, if necessary, edit it further.
Show/hide technical names
You can use this function to show alias names for fields. These alias names are necessary in InfoSets, for example to be able
to map self joins. Field alias names start with F, followed by a five-digit number.
Defining Join Conditions
Use
A join condition determines the combination of records from the individual objects that are included in the resulting set.
Before an InfoSet can be activated, the join conditions have to be defined in such a way (as equal join condition) that all
the available objects are connected to one another either directly or indirectly.
Usually, however, only rows containing a common InfoObject or rows containing InfoObjects that share the same basic
characteristic are connected to one another.
Connect tables T1 and T2 using a join and set as a join condition that the F1 field from T1 must have the same value as F2
from T2. For a record from table T1, the system determines all records from T2 for which F2(T2) = F1(T1) is true. In
principle, as many records from T2 can be found as required. If one or more records are found, the corresponding number of
records is included in the result set, whereby the fields from T1 contain the values from the record from T1 under
consideration, and the fields from T2 contain the values of the records found from T2.
Procedure
There are various ways of defining join conditions:
Using a mouse-click
Position the cursor over a row in an InfoObject. Press the left mouse-button and, keeping the left mouse-button pressed down,
trace a line between this row and a row in another object. Providing that the join condition between the two rows that you
have indicated is a valid join condition, the system confirms the join condition by displaying a connecting line between the
two rows.
Using the Link Maintenance pushbutton
You get to the Link Maintenance dialog box.
In a tree structure on the left-hand side of the screen, all of the InfoProviders that are already included in the join are
displayed along with their fields or attributes. If you double-click on one of these fields or attributes, the system
displays on the right-hand side of the screen all of the fields or attributes with which you are able to create a join
condition.
In the Selection column, set one or more of the indicators for the fields or attributes for which you want to create a join
condition. The system generates valid join conditions between the fields or attributes that you specify.
You use the Delete Links pushbutton to undo all of the join conditions.
You use the All Characteristics or the Basic Characteristics Only pushbutton to choose between the corresponding display
variants.
We recommend that you use the Basic Characteristics Only option. The All Characteristics setting displays all of the
technical options involved in a join. If you are not able to find a join condition on the basic characteristic level, then
the All Characteristics setting is useful, but this is an exceptional case.
When you have finished making your settings, click on the Continue icon.
We recommend this method, because the system searches for all the possible join conditions for any field or attribute that
the user specifies, ensuring that the join conditions are defined without errors.
Using the Context Menu Left Outer Join Inner Join
Usually inner-join operators connect all the objects in a join to one another. You can also connect each object with any of
the many other objects by using a left outer join operator.
You can find additional information about usage and special features under Left Outer Join.
If you want to use a left-outer join operator to connect an object, select the object and choose the corresponding function
from the context menu.
The system displays all of the valid join conditions that originate from this object. The connecting lines that represent
these join conditions are labeled as Left Outer Join . InfoProviders, on which a left outer join condition is affixed, are
differentiated by color from the InfoProviders that are connected using an inner join operator.
If you used a left outer join operator to connect two objects, you have to make sure that all on conditions are linked except
for these two objects with the formulation of join conditions.
Note that you cannot add an object, which you have already connected by using the left outer join operator, to another
object.
If you want to use an inner-join operator instead of the left-outer join operator, select the object that you want to
connect, and choose the Inner Join option from the context menu. Again the system displays all the valid join conditions that
originate from this object, and labels the connecting lines accordingly.
Result
Once the join conditions have been defined in such a way as to connect all the available objects to one another, either
directly or indirectly, the InfoSet is ready to be activated.
You click on the Check pushbutton in the pushbutton toolbar to find out if these preconditions for the activation have been
met.
For objects that are joined by a left-outer join operator, there is one extra condition that has to be met, namely that all
the other objects have to be connected to one another either directly or indirectly.
http://help.sap.com/saphelp_erp2004/helpdata/en/ed/084e3ce0f9fe3fe10000000a114084/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/ed/084e3ce0f9fe3fe10000000a114084/content.htm
http://help.sap.com/saphelp_nw70/helpdata/en/a3/96663bd194a978e10000000a11402f/frameset.htm
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/2f5aa43f-0c01-0010-a990-9641d3d4eef7
Hope itr helps
Regards
Bala
Also

Diff b/w Infoset and multiprovider BI 7.0 onwards

Hi gurus,
Could somebody tell me the difference b/w Infoset and multiprovider BI 7.0 onwards. I mean earlier we were not able to add cube to an infoset. It allowed us to add only ODS and info object . Since the new version allow us to add cubes too then what is the diff b/w Infoset and multiprovider. Since both of them are full filling the same purpose ?
Thanks in advance.
Ashu Gupta.

Hi,
Follow there links.
An InfoSet describes data sources that are usually defined as joins for ODS objects or InfoObjects (characteristics with master data). A time-dependent join or temporal join is a join that contains an InfoObject that is a time-dependent characteristic.
MultiProvider is a type of InfoProvider that combines data from a number of InfoProviders and makes it available for reporting purposes. The MultiProvider does not itself 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.
InfoProviders and MultiProviders are the objects or views that are relevant for reporting.
Infoset- Join
Multiprovider-Union
Follow there links for multiprovider and infoset.
http://help.sap.com/saphelp_nw04/helpdata/en/52/1ddc37a3f57a07e10000009b38f889/frameset.htm
need documentation on Multiprovider
Multiprovider
reporting on two cube without multiprovider or multicube
MultiProvider -Options
<removed>
Regards,
Senthil Kumar.P

How to create Virtual InfoProvider with Services - Virtual Characteristic

Hi all,
I need to create a virtual infoprovider that also fills a virtual characteristic in order to display custom characteristics and calculated values based on user selection.
Basicaly what I want to do is send a variable in a virtual characteristic equal to the values I want to fill in the characteristic. So for instance if my base cube contains the infoobjects Brand, Product Line, Region and Country I want a have a new infoobject that has no data, but fills itself with the vales of the infoobject I specify at query time on the virtual cube.
The reason for this is I am trying to create a WAD using the delta chart (waterfall graph) that will show the difference between the plan and actual totals for a specific characteristic in Profitibility analysis.
I have a document that explains the situation. Send me your mail address and I will send you the document.
Kind Regards

We found a way to build the structure for this.
Regards

Issue with Query on a virtual infoprovider

Hello,
I am getting the following error message while executing a query on a virtual infoprovider. We have recently gone through upgrade from BI 3.5 to BI 7.0 EHP1 (SP5) and from SEM BCS 4.0 to BCS 6.0.
EVersion not specified or not unique                                                             UCR0                006
EError reading the data of InfoProvider ZBCS_CV11                                    DBMAN             305ZBCS_CV11
EError while reading data; navigation is possible                                          BRAIN               289
I>> Row: 11 Inc: RAISE_READ_ERROR Prog: CL_RSDRV_VPROV_BASE   RS_EXCEPTION        301CL_RSDRV_VPROV_BASE
this query has been running fine before the upgrade. In the selection screen there are two fields - version1 and version2, if I am specifying same value in both the fields then the query runs fine and if I am providing different values then the above stated error message appears.
I have tried different settings with properties - Read mode: H,A,X and also different combination from the properties of the virtual infoprovider - with and w/o hierarchies; with and w/o navigation attributes but it did not workout.
the only thing which has changed on this virtual provider is that I had enabled delta caching as this was supposed to be used in a multiprovider.
Has anyone experienced similar issue or have an idea as to what is going wrong here. Please advice.
Regards,
Manish

Hi Manish,
I have exactly the same issue with a query on a virtual infoprovider after upgrading from BI 3.5 to BI 7.0 EHP1 (SP5) and from SEM BCS 4.0 to BCS 6.0.
Would you be so kind to tell me how you fixed this. (other queries seem to be working)
Kind regards,
Jamie Flaxman

How to find source of Virtual Infoprovider

Hi HANA Experts,
Greetings of the day.
I created a virtual infoprovider by using a HANA Calculation view. So far so good.
Per say if some body looking at my Virtual Provider want to know what is the source of it. Is there way where i can find this information like Table or HANA view or FM in BW ......some thing like that.
I know one hard way which is by running the Sequel Trace (ST05) when i say display data on Virtual provider....Then we need to analyse the SQl to get the info.
One more way is by going into the Extras -> Information logs -> Types/Attributes then you can see.
I Hoping somebody would know some easy way here
Thanks,
Shanthi Bhaskar.
Message was edited by: Shanthi Bhaskar

See also:
*Firefox > (Web) Developer > Page Source
*Tools > Web Developer > Page Source (Ctrl+U)
*right-click on a web page and select View Page Source in the context menu

BAPI based virtual infoprovider

Hi,
in our scenario we'd like to access the data in a cube in an external BI system without having to load the data into our BI. I thought there would be a standard way to do that, but I can't find anything. I was experimenting with BAPI based virtual infoprovider, but I dont see, how can I assign a specific BAPI to my infoprovider, where can I specify what data is to be read an so on. The SAP documentation is a little mysterious about this infoprovider type.
Another solution would be to create a virtual infoprovider based on a function module with the same structure as the source cube and then read the data in the function module over RFC. However, this requires some programming.
Does anyone have a better suggestion for such a requirement?
How exactly does the BAPI based infoprovider work ?
Thanks,
Marek

Just a sugguestion.
If the DataSource is based on a function module, the function module may not be able to process the characteristic value selection. Consider changing the funtion module.
John Hawk
Edited by: John Hawk on Oct 13, 2010 1:38 PM

Virtual Infoprovider with DB2 as source system.

Hi Experts,
Can we create a Virtual / Remote Cube with DB2 as a source system.?
Are there any specific systems that are supported by SAP to create a Virtual infoprovider.
Thanks in advance.
Regards,
Hardik Luthra

Hello
we have the same problem.
the problem is a security-problem that the user SAPServiceSID isn't in the group DB2ADMNS.
After Restart Service and SAP the db2-connect runs fine
regards Siegfried Dörfler / W&W-Informatik

Using Virtual InfoProvider with DBConnect

Hi all,
I'd want to use a virtual InfoProvider in order to acces Teradata database live. Can I use DBConnect? I know that it is possible to use UDC with the version 3.5. But in my case, we have the version 3.0.x. Is there somedy that can help me to align me with the best solution or some documentation.
Thanks very much!

Hi Deepu
As I wrote, I have allready set the cache Mode to "0 Cache is Inactive". But this is the the general data cache i.e. reuse of data among users this is not deep enough. I need to make sure that each and every query step goes to the DB for new data.
WKR
Kristian

Virtual InfoProvider with Function module, how to u0094bypassu0094 OLAP memory

Hi
I have created a Virtual Infoprovider with services as described in the How to Implement a VirtualProvider with Services (SAP NetWeaver 2004s). It works and I have even been able to make some special calculations within the code. But how do I make sure that the OLAP engine always fetches data from the source table eg when drilling or filtering in the front-end? I have disabled the query cache but I also need to disable the OLAP engines own cache / memory how do I do that? I need the functionality as the implemented calculations depend on the overall report result and they must be calculated before aggregation.
Hope that you can help
Kristian

Hi Deepu
As I wrote, I have allready set the cache Mode to "0 Cache is Inactive". But this is the the general data cache i.e. reuse of data among users this is not deep enough. I need to make sure that each and every query step goes to the DB for new data.
WKR
Kristian

APO DP V5 - ad hoc reporting via a Virtual InfoProvider

I am using APO DP V5, and want to do ad hoc reporting on the planning area via a Virtual InfoProvider ('Remote Cube')
Can anyone provide a simple list of steps required to do this - the help text is not especially clear on this topic.
I believe the process is something like:
1. generate export data source for planning area
2. replicate data sources
3. assign InfoSource to data source
4. set up transfer/communication structures
5. create Virtual Provider, based on InfoSource
6. activate Virtual Provider
7. set up BEX query
Thanks,
Bob Austin, Atos Origin

Prafulla,
Thanks for your reply - very useful.
Can you clarify these points:
1. InfoSource should be of type 3.x
2. Replicated data source should be of type 3.x
3. At the moment I have a data source of type BW version v 7 defined for the planning area. Is it possible to replicate this as a type 3.x
Thanks, Bob.

Explorer - indexing on a Virtual Infoprovider.

Hi Folks,
i have a customer using: SBOP Explorer 3.1 SP01 \ BO Enterprise XI 3.1 \ SAP BW 7.01
Data model: Information Space \ Universe \BEx query \Virtual info cube
My customer asks how the indexing will work for them as they are working on top of a Virtual Infoprovider (cube).
How is it possible to run the indexing on a virtual infoprovider, when this one does not contain data?
I could not find anything documented on this topic - is it not supported?
Regards,
John

Hi John
We had a similar scenario and there is a some answers to your question:
- The information space itself only contains meta data
- Meta data is generated when scheduling the indexing process to run
An according to the guros here on the forums the Virtual InfoProvider is supported for universe connectivity.
Cheers,
Anders

Exclude selections not working on virtual infoprovider

Hi,
I have a Bex report which is based on virtual infoprovider. This virtual infoprovider have load structure of BW Datasource -> IP (PSA) -> DTP
Infopackage runs every night in FULL mode and brings in latest data in PSA, and whenever report is executed, inturn DTP is executed in background to fetch data at runtime. Query works fine when run open or with INCLUDE selections on variable screen. But whenever it is run with EXCLUDE selections on variable screen, it gives below error -
- Error reading the data of InfoProvider
- Invalid selection condition in the data request
- Error in substep
Is there any restriction using virtual infoprovider like you cannot query with exclude selections? I also tried running report with "<> 10" selection on variable screen but still get same error. Any ideas on this?
-Abhijit

Do both sets not say to
set Client certificates, select Ignore?
I'm skimming so may be missing something.
You can have session persistence using IP affinity, but depending on what you want to publish and achieve you may need to inspect the traffic on the LB. I was curious as it adds a bit more complexity.
And is Outlook 2010 upto date? What is the exact build string on a client that is getting the prompt please? This is a person bugbear of mine:
http://blogs.technet.com/b/rmilne/archive/2013/07/18/patching-exchange-don-t-overlook-outlook.aspx
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter:   LinkedIn:
  Facebook:
  XING:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Infoset and virtual infoprovider

Similar Messages

Maybe you are looking for