Hi Raj,
In SAP BW, the information which is reported, might not be a real time info. This is primarily because, the information is first <i>extracted</i> from the <i>source system</i>, and then Reported on.
There are also instances, where in only after a predecided time interval, the information is refreshed. This way, information is kind of "Cached". This is helpful if a large number of users are accessing the same information, and repeated extractions would make the system slow.
<b>Virtual InfoCubes</b> allow you to define queries with direct access to transaction data in other source systems. Thus giving you real time information.
Points you would need to take care of, in general are
- You must make sure that master data and hierarchies are already in BW when executing the query, since they are not read directly by the source system.
- TheBW ServiceAPI functionality (contained in SAP R/3 PlugIn) must have been installed.
- The source system must have at least release 4.0B.
- A source system ID must have been created for the source system in BW.
- DataSources from the source system must have been assigned to the InfoSource of the SAP RemoteCube. These DataSources are released for direct access.
- Active transfer rules exist for the combinations.
When a query is executed, data is loaded into SAP BW. For this reason, it only makes sense to use a Virtual Cube when the following prerequisites have been met:
- You require very up-to-date data from a SAP source system
- Only a small quantity of data is transferred.
- Only a small number of users work with queries in the dataset at any one time.
Hope this helps.
Regards,
Sanyam
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.