Functionality
You use this function module to change InfoSets. Supported changes:

• Removing InfoProviders (ODS objects or InfoObjects) from the InfoSet or
adding them to the InfoSet.

• Removing fields or attributes contained in InfoProviders from the
InfoSet or reinclude them.

• Changing the ON condition.

Example
See the source code of the test report RSQ_ISET_BAPI_TEST.

Notes


• The system does not check whether fields/InfoProviders that you want to
delete from the InfoSet are being used in queries. This means that somequeries could be invalidated.

• The module saves the InfoSet but does not activate it.


• For documentation on the interface parameters, see the module
BAPI_ISET_CREATE.

Description
Detailled information about InfoSet.
You must at least fill the name of the InfoSet and assign a text.


• INFOSET,,,,InfoSet name,,


• OBJVERS,,,,A, D, M,,


• CONTREL,,,,Content release,,


• CONTTIMESTMP,,Content time stamp: Object last modified by SAP,,


• OWNER,,,,Owner - not used


• BWAPPL,,,,BW application (namespace) - not used


• INFOAREA,,,,InfoArea,,


• BCTCOMP,,,,Obsolete !!! (Component (of BW Business Content)) - not used


• TSTPNM,,,,Name: Last changed by,,


• TIMESTMP,,,,Time stamp: Last changed by,,


• CRNM,,,,Name: Creator,,


• CRTSTP,,,,Creation time stamp,,


• TEXTLONG,,,,Text long,,


• TEXTSHORT,,Text short,,

Description
Technical name of InfoSet currently being edited

Description
This table contains information about attributes/fields of all theInfoProviders (table object) in the InfoSet.


• FALIAS

Field alias - assigned internally and makes attributes/fields in theInfoSet unique

• TALIAS

Table alias - assigned internally and makes the provider in the InfoSetunique. For example, a provider may appear in the InfoSet more than once(self-join). In this case, the name of the InfoProvider (TNAME) isidentical - it is only unique via the table alias.

• EXTALIAS - obsolete

External alias. Must be used to make an InfoProvider, that is in theInfoSet more than once, unique.

• FNAME

Field name - field name as it appears in the maintenance transactions

• TNAME

Name of InfoProvider as it appears in the maintenance transactions/nrsd1, /nrsdods, /nrdscube

• FTYPE

Field type - there are many field types that are always of a technicalnature. Only type 'IO' is interesting. Definitions of field objects arein the type pool: rsqis (rsqis_c_fobj).

• INTIOBJNM

Internal InfoObject name. This is composed of: <(>
<<)>InfoSet>___

• REFALIAS - internal

Reference object (table or field) for additional fields

• REFTNAME - internal

Reference object: Name of InfoProvider

• REFFNAME - internal

Reference object: Name of field

• REXTALIAS - obsolete


• KEYFLAG

'X':,,Key field

• MARK

'X':,,Field is selected and is available in the query

• ADDY

Additional field (internal)

• TEXTLONG

Long text

Description
On condition
This table contains information about how the links/series lines betweenindividual InfoProviders are drawn:


• TNAME_LEFT,,

Name: InfoProvider - left

• FNAME_LEFT

Field name - left

• EXTALIAS_LEFT - obsolete


• FALIAS_LEFT

Field alias - left

• TNAME_RIGHT

Name: InfoProvider - right

• FNAME_RIGHT

Field name - right

• EXTALIAS_RIGHT - obsolete


• FALIAS_RIGHT

Field alias - right

Description
Return parameter of method. The return parameter informs you whether thecall was successful or unsuccessful.
The most important error messages refer to


• no authorization to change the InfoSet


• error in the sources of the InfoSet. In this case, the parameter
RETURNTABLE provides you with an extensive error log.
This table includes information about InfoProviders (table objects)contained in the InfoSet (master-data-bearing characteri
stics, DataStore objects, InfoCubes)

• TALIAS

Table alias - assigned internally and makes the provider unique in theInfoSet. For example, a provider can be in the InfoSet more than once(self-join). In this case, the name of the InfoProvider (TNAME) isidentical - it is only unique via the table alias. The caller should notset the table alias.

• EXTALIAS - obsolete

External alias. Must be used to make an InfoProvider, that is in theInfoSet more than once, unique (also see ON conditions).

• TNAME

Name of InfoProvider as it appears in the maintenance transactions/nrsd1, /nrsdods, /nrdscube

• BNAME

If necessary, the system fills name of assigned basic characteristic(only for characteristics, if available)

• TTYPE

Type of InfoProvider:
- CP:,,time-independent characteristic
- CQ: ,,time-dependent characteristic
- OA:,,time-independent DataStore object
- OQ:,,pseudo time-dependent DataStore object
- IC:,,Standard InfoCube
- IQ:,,pseudo time-dependent standard InfoCube

• OUTERFLAG

X: InfoProvider connected by Left Outer Join. Otherwise InnerJoin

• TEXTLONG

Description of InfoProvider (if empty, the short text from the system isused).

• ALLFIELDS

X' All fields/attributes of the InfoProvider are included in the InfoSet
. The caller must not fill the FIELDOBJECTS table.
We recommend creating an InfoSet with BAPI_ISET_CREATE, whereALLFIELDS='X' is set for all included InfoProviders. Then, you can useBAPI_ISET_CHANGE to hide individual fields from the InfoSet, wherenecessary.
Contains information about time-dependency

• TEMPONTYPE,,

01: rsqis_c_tmop_simple

• OPERANDTYPE

rsqis_c_tmop_cha,,,,Time-dependent characteristic
rsqis_c_tmop_date,,,,Key date
rsqis_c_fobj_tm_fix,,,,Key date derivation
....

• TNAME

Name: InfoProvider

• FNAME

Field name

• EXTALIAS,,


• TFALIAS

Alias

• CTNAME

Compound: Name: InfoProvider

• CFNAME

Field name

• CEXTALIAS,,- obsolete


• CFALIAS

Alias

• TIMESHIFT

FIRST - rsqis_c_shift_first
LAST - rsqis_c_shift_last
offset (for example, 5 - fifth of the month for 0calmonth)
Examples for temporal operands:
1) 0calday (internal field alias F2) defined as key date
TEMPONTYPE :,,01
OPERANDTYPE: ,,DT
TFALIAS: ,,,,F2
CFALIAS:
TIMESHIFT:
VARNAM:
2) Key date derivation from 0calmonth (first of the month)
TEMPONTYPE: ,,01
OPERANDTYPE: ,,TX
TFALIAS: ,,,,F3
CFALIAS:
TIMESHIFT: ,,,,FIRST
VARNAM:
3) Key date derivation from 0fiscper (first of the month)
TEMPONTYPE:,,01
OPERANDTYPE: ,,TX
TFALIAS:,,,,F7
CFALIAS: ,,,,F9
TIMESHIFT: ,,,,FIRST
VARNAM:
with:
f7: 0fiscper
f9: 0fiscvarnt
4) Pseudo time-dependency for DataStores/InfoCubes - 2 date valuesare used as interval limits.
TEMPONTYPE: ,,01
OPERANDTYPE: ,,TD
TFALIAS: ,,,,F12
CFALIAS: ,,,,F13
TIMESHIFT: ,,,,
VARNAM:
with:
f12: Date1
f13: Date2
5) Pseudo time-dependency for DataStores/InfoCubes - 0calmonth isderived and the derived date values are used as interval limits.
TEMPONTYPE: ,,01
OPERANDTYPE: ,,TI
TFALIAS: ,,,,F3
CFALIAS: ,,,,
TIMESHIFT: ,,,,
VARNAM:
with:
f3: 0calmonth
6) Pseudo time-dependency for DataStores/InfoCubes - 0fiscper isderived and the derived date values are used as interval limits.
TEMPONTYPE: ,,01
OPERANDTYPE: ,,TI
TFALIAS: ,,,,F7
CFALIAS: ,,,,F9
TIMESHIFT: ,,,,
VARNAM:
with:
f7: 0fiscper
f9: 0fiscvarnt
7) Time-dependent characteristics
TEMPONTYPE: ,,01
OPERANDTYPE: ,,CH
TFALIAS: ,,,,T00002
CFALIAS: ,,,,
TIMESHIFT: ,,,,
VARNAM:
with T00002 as the table alias of the time-dependent characteristic

Description
Contains information about where conditions


• FALIAS

Field alias (left operand)

• OPTION

Operator: EQ, BT,#

• LOW

Low value

• HIGH

High value

• FIELDFLAG

X = right operand is field object

• CFALIAS

Field object (right operand)