SAP Program RSQ_ISET_BAPI_TEST_700 - Test Report for InfoSet BAPIs

Purpose
Test Report for InfoSet BAPIs
This report is used to call and test the common InfoSet BAPI functionmodules, and as a template for user-specific reports/modules that usethe InfoSet BAPI functions.
Note: The InfoSet interface is available as of Release 7.0. When you usethe BAPI modules, ensure that you reference the relevant types of theinterface. With the upgrade to Release 7.1, the length of the ALIASchanges (data element rsqalias changes from char6 to char19).

Prerequisites
On the selection screen, the name of the InfoSet, what is to begenerated or changed, and the object version must all be specified.

Features
BAPI_ISET_CREATE - Creating an InfoSet
You can use the input help to select an InfoProvider (characteristicbearing master data, DataStore, or InfoCube). An InfoSet is builtinternally, which joins this InfoProvider twice with itself (self join).The first two fields are also joined. This is the simplest way to definean InfoSet.
Additional options are:

  • Key Date Definition

  • If the InfoProvider has an attribute of type Date, this isdefined as the key date.
    • Key Date Derivation

    • If the InfoProvider has 0fiscper or 0fiscyear as an attribute, the keydate is derived from it. Otherwise, the InfoProvider is checked for the0calmonth, 0calquarter, or 0calyear attributes. If one of theseattributes are present, the key date is derived from it.
      • DataStore/InfoCube Dates

      • Pseudo time dependency: The InfoProvider is checked for two attributesof type Date. If two attributes of type Date are present,they are treated as interval limits.
        • DataStore/InfoCube Time Derivation

        • Pseudo time dependency: The InfoProvider is checked for the 0fiscper or0fiscyear attributes. If these attributes are present, they are treatedas interval limits. Otherwise, the InfoProvider is checked for the0calmonth, 0calquarter, or 0calyear attributes. If these attributes arepresent, they are treated as interval limits.
          Internally, the InfoSet is first generated without incorporation of theadditional options. It is then activated using the BAPI_ISET_ACTIVATEmodule and its information is read using BAPI_ISET_GETDETAIL. This isenhanced by the additional options (this primarily changes the internaltable temponcondition), and the InfoSet is modified usingBAPI_ISET_CHANGE.
          BAPI_ISET_ACTIVATE - Activating an M version InfoSet
          BAPI_ISET_GETDETAIL - Reading the internal table of an existing InfoSet
          BAPI_ISET_CHANGE - Changing an existing InfoSet
          BAPI_ISET_GETLIST - Returns a list of InfoSets
          The object version (A, M, or D) must be provided. You can specifyrestrictions using the SELINFOSET table. The structure of the row typeis the same as that of a standard RANGE table.

          Example
          See Report or Executing Reports Using the Debug Option.