Functionality
This module is an RFC version of the module RSDRI_INFOPROV_READ, butwith restricted functions.

Further information
See RSDRI_INFOPROV_READ.

Description
The result stored in E_RFCDATA_UC can be converted back to the internaltable using the command IMPORT RSDRI = FROM DATA BUFFER e_rfcdata_uc. The E_RFCDATA_UCformat is also suitable for communicating between systems with andwithout Unicode or between systems with different code pages.

Value range
This field can have two values:

• 'X' : This means that the result of the read is not aggregated
completely. This is caused by multiple DB reads from, for example, amulti-provider or by reads in E and F fact tables.

• ' ' : This means that the result has been aggregated completely.

Description
I_RESULTTYPE specifies the form in which a result is returned:


• space = in an internal table E_T_RFCDATA vom Typ RSDRI_T_RFCDATA


• 'V' = in an internal table E_T_RFCDATAV with type RSDRI_T_RFCDATAV


• 'U' = in a variable E_RFCDATA_UC with type XSTRING

Note that the standard return value (space) causes problems in systemswith differing code pages and in RFC communications between Unicode andnon-Unicode systems.
A vertical return ('V') is a problem if the result is large. As ageneral rule, the table E_T_RFCDATAV must not contain more than 100000entries. This size is calculated as follows: ((no. of characteristics +no. of key figues) * result rows).
A Unicode-compatible return value ('U') is suitable for communicationsbetween systems on at least Basis 6.10. Differing code pages are alsoallowed.

Description
Do you only want to include data that has already been rolled up toaggregates, or do you also want to read the most current data that mightonly exist in the fact table of the InfoCube?
This parameter is ignored if a table of requests (i_t_requid) wasspecified.

Description
You can use the parameter I_S_RFCMODE to pass results data package bypackage. This is necessary in particular when you use RFC to query massdata; there may not be enough system resources available to pass theresult in an internal table.
You specify the package-by-package passing of the data in I_S_RFCMODE.The basic idea is to pass a data package in E_T_RFCDATA format (intowhich a certain number of data records has been passed) to anRFC-enabled ABAP function module in the calling system:


• I_S_RFCMODE-ID: This is a random ID used to permit the receiver function
module to differentiate between packages in parallel requests. This IDis passed to the receiving function module as an input parameter.

• I_S_RFCMODE-RFC_RECEIVER: This is the name of the RFC-enabled receiver
function module in the calling system.

• I_S_RFCMODE-PACKAGESIZE: This is the number of results records that a
package should contain.
The receiving function module (I_S_RFCMODE-RFC_RECEIVER) should bestructured in the same way as the module RSDPL_RECEIVER_PROTOTYPE.

Value range
Make sure that the function specified by I_S_RFCMODE-RFC_RECEIVERprocesses the data speedily. If the data remains in this function toolong, the calling process can be stored in BW, so losing the databasecursor and potentially causing an error. One solution to this would betoo use smaller processing packages (see I_S_RFCMODE-PACKAGESIZE).

Default
Initial (results are not passed to a receiving module in packages)