Variables in Customer Exit -SAP Bi.

Wlhat variables would you typically use when making use of

the user exit RSR00001 in BEx reporting?

 I - STEP is used in ABAP code as a conditionalcheck. 

The following values are checked:

1.)I_STEP1 Before processing of the variable pop-ups and

gets called for every customer variable.

2.)I_STEP2 Is called after variable popup for variables not

marked as "Ready for input" and are set to

required entry.

3.)I_STEP3 Is called after all variables are processed (only

once and not for each variable).

 I - VNAM: It is the variable containing the variable

name within ABAP Typically you lvould do aCASE statement on this variable to get the

variable working.

E - T - RANGE: This is the internal table populated

with variable values in a customer exit.

 L S RANGE: This is the structure to populate

E- --T_R ANGE

LOW low end value

HIGH high end value

SIGN 'I' to include, etc.

OPT gives the options like 'BT' for between,

'EQ' for equal, ecc.

 I - VARTYP- variable type

1 Characteristic

2 Hierarchy node

3 Text

4 Formula

5 Hierarchy

 I - IOBJNM: name of the Infoobject.

 I -P ERIV: fiscal year variant.

 I - T - VAR - RANGE: table with all variables and

their values.

Marker Update In Inventory Management

Marker Update

Marker Update is used to reduce the time of fetching the non-cumulative key figures while reporting.
It helps to easily get the values of previous stock quantities while reporting.
The marker is a point in time which marks an opening stock balance.
Data up to the marker is compressed.

No Marker Update

The No Marker Update concept arises if the target InfoCube contains a non-cumulative key figure.
For example, take the Material Movements InfoCube 0IC_C03 where stock quantity is a non-cumulative key figure. The process of loading the data into the cube involves in two steps:

In the first step, one should load the records pertaining to the opening stock balance or the stock present at the time of implementation. At this time we will set marker to update (uncheck 'no marker update') so that the value of current stock quantity is stored in the marker.After that, when loading the historical movements (stock movements made previous to the time of implementing the cube) we must check marker update so that the marker should not be updated (because of these historical movements, only the stock balance / opening stock quantity has been updated; i.e. we have already loaded the present stock and the aggreagation of previous/historical data accumulates to the present data).

After every successful delta load, we should not check marker update (we should allow to update marker) so that the changes in the stock quantity should be updated in the marker value. The marker will be updated to those records which are compressed. The marker will not be updated to those uncompressed requests. Hence for every delta load request, the request should be compressed.

Check or uncheck the Marker Option
Compress the request with stock marker => uncheck the marker update option.
Compress the loads without the stock marker => check the marker update option.

Relevant FAQs

The marker isn't relevant when no data is transferred (e.g. during an delta init without data transfer).
The marker update is just like a check point (it will give the snapshot of the stock on a particular date when it is updated).
The request in which the opening stock (Initialization) is loaded must always be compressed WITH a marker update.
The request in which historical material documents are contained must always be compressed WITHOUT a marker update. This is necessary because the historical material movements are already contained in the opening stock.
Successive delta uploads must always be compressed WITH marker updates.