The dataprovider of a report is the component that is bound to a universe or other data source and that provides data back to the report. Webi documents are composed of multiple dataproviders. A dataprovider itself may be composed of one or more queries. The image below depicts how a dataprovider is created in Web Intelligence.
Universe Class |
Object Name |
Description / Purpose |
---|---|---|
is SAP? |
Indicates if the dataprovider is sourced through an SAP connection (Bex or BICS via Universe) |
|
is Sampled? |
Indicates if the dataprovider should only use a data sampling |
|
Universe Name |
Name of the universe (if universe based) |
|
Universe CUID |
CUID of the universe (if universe based - if the report is directly joined to a BEX query, this CUID is really the DATA CONNECTION CUID) |
|
Dataprovider Type |
Type of dataprovider Possible values: ● A universe ● A BEx query ● A Microsoft Excel 2003 or Microsoft Excel 2007 spreadsheet ● A free-hand SQL script (as of BI4.1SP6) |
|
Dataprovider Name |
Name of the dataprovider |
|
Duration |
Duration in time for the dataprovider to refresh |
|
Refresh Date |
Datetime the dataprovider was refreshed (and saved) |
|
Row Count |
Count of rows of data in the dataprovider |
|
Datasource Name |
Source name of the dataprovider (often times the same name as the universe) |
|
Datasource Type |
Type of datasource (often times the same as the dataprovider type) |
|
Dataprovider ID |
ID of the dataprovider |
|
SQL Text |
SQL text generated from the refreshing of the dataprovider. This SQL can change depending on when the report is scheduled and different prompt values are supplied to it, but note that runtime SQL change may not represent the SQL text stored in the report itself which is the SQL MetaMiner captures. |
|
SQL Text Filter (Webi) |
A predefined condition to allow for free text search of SQL text within dataproviders |
See also