NO MARKER UPDATE

hi all,
what is the use of NO MARKER UPDATE in collapse tab of incube manage for specially inventory infocubes..
plz explain me in detail..
thanks in advance
pinky reddy

Hi,
U will get that option if u are using the Non cumulative key figures......
Well suppose take a simple example.....
U have the opening balance as 10000....
And u are loading Historical movements, Means by generating this movements only the opening balance is generated..... Ok..
While u are extracting the historical movements u have to select the no marker update... if u select this it wont be add value to the opening balance......
and if u are loading the current movements... then no need of selecting the No marker update....
for example...
Opening balance 10000
Historical movements Inflow 15000 and outflow is -5000
By generating the above transaction only the OB is generated...
Current movements....
5000 inflow and outflow -2000
If any one say what is the balance..
10000
+5000
15000
-2000
13000
Balance is 13000. If u select the no marker update it wont affect to the opening balance and if u select the No marker update it will affect the opening balance....
Assign points if it helps
Search in SDN...
Khaja

Similar Messages

Marker update for Inventory data sources

Hi all,
why we use marker update in Cube manage for inventory data sources at the time of loading?
i heard that to avoid the keyfigures cumulation we do check that option ,is that correct/
please clear my doubt
thx

HI
(2LIS_03_BF Goods Movement From Inventory Management-------Unckeck the no marker update tab)
(2LIS_03_BX Stock Initialization for Inventory Management--
---select the no marker update check box)
2LIS_03_UM Revaluations -
Unckeck the no marker update tab)
in the infopackege of "collaps"
Cheers

No Marker Update - 2LIS_03_BF

Hi
I have been having some issues with the Inventory management cube( using 2LIS_03_BF). The data in bw does not reconcile with SAP.
What I have realised is the following:
I have a process chain that loads the data every 3 hours and there is a step to compress the load with the field No Update Marker unchecked.
However the cube has the No Update Marker checked.
So which one would it use?
Could this be the cause of the issue?
Do I compress the delta loads ?
Thanks Again for your help.
Fahed

Dear Fahed,
It is suggested to compress the delta loads here as the incentory cube (0IC_C03) first calcultes forward (to marker then) comes back to the month where report is filtered.
You should check data period wise for locating point of incorrect keyfigure values.
Here are few points:
a) The request in which the opening stock was loaded must always be
compressed with a marker update
b) The request in which the historical material documents were contained
must always be compressed without a marker update and
c) Successive delta uploads must always be compressed with marker
updates.
For better understanding have a look at this document:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f83be790-0201-0010-4fb0-98bd7c01e328
Also see the OSS note 655798 for compression of stock's cube.

Inventory Management (Advanced - Marker update)

I have been following your discussion regarding Inventory Management and the use of 2LIS_03_BX and 2LIS_03_BF extractors, and I have also been studying the How to guide on Inventory Management.
I am currently only using 2LIS_03_BF with no data restriction in the setup-run or in the initialization. The stock balance is correctly even though I am not using 2LIS_03_BX (because the sum of all historical movements equals the current balance).
But I am facing performance problems because I am not using compression. I am considering 2 solutions:
Solution A (the easy)
1. Compression on all request (with marker update)
Solution B (as suggested in the How-to-guide)
1. Delete InfoCube data
2. Generate new balance with 2LIS_03_BX
3. Compression of 2LIS_03_BX (with marker update)
4. Reconstruct old 2LIS_03_BF requests from PSA
5. Compression of old 2LIS_03_BF requests (No maker update - because all these will new be considered historical in relation with the newly generated stock balance).
6. Future deltaloads from 2LIS_03_BF and compression (with marker update).
As I see both solutions will solve the problem but A is by far the easiest. I would like your opinion!
When you do the marker update during compression does it matter wether you do it as described in the how-to-guide I can you do it as follows instead:
1. Compression of Historical Movements (2LIS_03_BF) (with marker update)
2. Compression of Stock balance (2LIS_03_BX) (No marker update)
3. Compression of Future Movements (2LIS_03_BF) (with marker update)
As I see the only important thing is that you do the marker update with eitherHistorical Movements (2LIS_03_BF) or Stock balance (2LIS_03_BX), but not both of them or none of them. I am not 100% sure but please give me your opinion.

Hello Thomas,
I have never tried doing the marker update other way around (through BF instead of BX), but I don't see any reason why it will not work. You are right that marker update should be done either with snapshot or material movement as both datasources bring same data at different granularity level. Solution A seems to be simpler and straightforward, but I am not sure if there will be any impact on performance if we update the marker intially with lot of requests from BF instead of a single BX request.
Regards,
Praveen

Use of Marker & No marker Update

Hi All,
I am going through the Inventory Management I want to know the use of Marker update and No marker update.
and also please let me know the below details.
1. First time when we will load the data we will compress the request with marker update and while loading BF&UM we will comopress with No marker Update.Could please brief me explain why we need to do and how it will
effects the data with marker and no marker.
Thanks & Regards
Ajay
"Points will be assigned"

Hi Ajay,
As you asked, Data Mismatch willn't be happened if you compress the cube with "No marker update".
to avoid mismath only we compress "no marker update"
Why mismacth?
Suppose you are taking the opening balance on 01 jan 2008 by using BX datasource.
You have business running for 1 year in R3(2007). There would be some movements happened in all storage locations.
Ex : Storage 1
Material M1 --> Received - 100 ; Issued 60; again Received 30
NOw the current stock available in storage 1 = 100-60+30 =70
When you load BX data source it takes value 70 for storage location 1. Then you compress the cube with "Marker update". SO marker sets a reference point to this 70.
Later when you load BF datasource for the past movements, you get these 3 transactions , i.e 100, 60 and 30. If you compress the cube with these movements againg one more 70 will go and add to the reference point. Because initial 70 has come by calculating these historical movements only.
But that is the wrong value. So to avoid this, we compress the cube with "No marker update".
Since these no marker compressed values are not added to reference point, So your Non Cumulative KF will take the result from that reference point.
Later you can delta movements, i.e from Jan 1 2008 to Feb 1 2008, those will be compressed with "Marker update", because these are new and should be added to reference point.
This is my longest thread ever written Ajay.
Thanks
Sreekanth.

Necessary to see green check-mark (Update Successful) during Airport Firmware Update?

I had just taken the leap of faith and decided to update my current workhorse Airport Extreme to 7.6.1 fro 7.6.
It downloaded and ran successfully all the way to the rebooting of the router. However, the computer I was running my Airport Utility on did not seem to find and connect back to the rebooted router fast enough and the Utility said "No Airport Detected" - so it did not show me the "green check-mark" update succesful page that I was normally used to.
But I was able to restart the Utility again, and connect to it to see if running on 7.6.1. All seems to be well...
However - being the completionist that I am, it bothered me I never got to see this "green check-mark" page. I was wondering if not seeing that confirmation page really mattered in this firmware upgrade - whether I saw it or not in the first place, and whether not seeing it could corrupt or mess up my update process that I did not know about? As long as I see my router showing 7.6.1 after the reboot - I should be fine right?

bump

With marker update.

hi gurus,
Can anybody give me a simple answer for this question?
I loaded the Historical Movements data with posting date Selection ,Now i want to compress the Data.(2LIS_03_BF)
Should i tick the "NO MARKER UPDATE" OR NOT ?.
THANKS IN ADVANCE.

Solved

Marker update or not.

hi xperts,
I am working on Inventory management Can any body give me idea which of the Following are correct
1.2lis_03_bx -- should be "No marker Update" is not set- is it right?
2.2lis_03_bf - should be "No marker Update" should be ticked- is it right?
3.2LIS_03_UM - should be "No marker Update"should be ticked- is it right?
I have to do this in the Compression screen of the manage infocube right?
Please confirm me,as i am not sure.

Hi,
1) correct
2) BF Delta init and BX is not used: then should be "No marker Update" should not be ticked.
BF Delta init and BX is used: then should be "No marker Update" should be ticked.
3) UM Delta init and BX is not used: then should be "No marker Update" should not be ticked.
UM Delta init and BX is used: then should be "No marker Update" should be ticked.
And also see :
Re: 2lis_03_bx not defined in source sys
With rgds,
Anil Kumar Sharma .P

Compressions with No marker updates

Hi experts,
What is the purpose of compressing the request of 2lis_03_bx
with No marker update not set and compressing the request of
2lis_03_bf with No marker update set ?
Full points will be assigned.
V N.

Hi,
BX is a one time load used for initializing the stocks and BF and UM are run regularly as deltas. The marker updates are very important so as to give the correct stock values.
For more information check the thread below :
Delta for 2LIS_03_BX
Also please search the forums as these topics have been discussed in great detail.
Cheers,
Kedar

No marker update for delta

Hi,
We compressed our inventory cube as listed below. I realized that deltas can be compressed with "No Marker Update" unselected, in order to update marker. This will improve the query performance. But I compressed deltas with "No Marker Update" Selected for about 3 weeks. Is it possible to compress further deltas with "No Marker Update" unselected.
2LIS_03_BX ---> "No Marker Update" Unselected
2LIS_03_BF Initial ---> "No Marker Update" Selected
2LIS_03_BF Delta ---> "No Marker Update" Selected
Thanks in advance,
Natalia

This is what I did in a similar situation
- Cleared delta queue by running the load twice
- Compressed existing requests without marker
- Identified the marker key (Package dimension table - key for RECORDTP = 1) , this will be one DIMID value
- Deleted all entries for this DIMID from E and F tables and then the P dimension table (effectively removing the marker from the cube). This was done using ABAP
- Ran setup again (with no txn being posted in the system), brought 2LIS_03_BX again, compressed with marker.
Try only if you are comfortable with it. If you prod cube has lots of data, this may be worth a try before you decide to reload.

Marker update

Hello,
I have inventory cube and i am compressing the cube with Marker updates.
I want to know, which request is compressed with marker update and which is not compressed with marker update. is it possible?
Thanks.

Hi Kedar,
Thanks for the reply.
we can find in the logs if a request is compressed with marker update or not .
here is the example
Request with marker update
@5B\QInformation@     START cond CUBE ZSCI0005 at 114826 on 20080725 maxreqid     74438 maxcnsid         0 refpoint update + NO NULL ELIM     @5F\QNo long text exists@
Request with out marker update
@5B\QInformation@     START cond CUBE ZSCI0005 at 114826 on 20080725 maxreqid     74439 maxcnsid         0 No refpoint update + NO NULL ELIM     @5F\QNo long text exists@
But this is possible only if you do a compression manually. But if you do a compress in process chain with process type compress it is not delivering this log.
@5B\QInformation@     FB RSM1_CHECK_DM_GOT_REQUEST called from PRG RSSM_PROCESS_COMPRESS; row 000200
@5B\QInformation@     Request '                                            75068'; DTA 'ZSCI0005'; action 'C'; with dialog 'X'
@5B\QInformation@     Leave RSM1_CHECK_DM_GOT_REQUEST in row 70; Req_State ''
Unfortunately i am using compress in the process chain and i need to test this.
Thanks.
Naga.

NO MARKER UPDATE(INVENTORY)

HI GURUS,
CAN ANYBODY PLS EXPLAIN WHAT IS THE USE OF NO MARKER UPDATE IN INVENTORY MGMT.

Hi,
Marker is used to reduce the time of fetching the non-cummulative key figures while reporting.
This no marker update concept arrises if the cube contains a non -cuumulative key figures. say for example take the material movements cube where stock quantity is a non-cummualtive key figure. there the process of laoding 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 make marker to update( uncheck no marker update) so that the value of current stock quantity is stored in the marker. After that when we r loading the historical movements (stock movements made previous to the time of implementing the cube). at this time we have to check marker update so that the marker should not be updated ( bcs of these historical movemtns 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).
Second after every successful delta loads, we should not check maker update ( we should allow to update marker) so that the chances 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. thats why for every delta load requests the requests should be compressed.
This marker is mainly used to fetch the records value for reporting. it helps easily to get the values of previous stock qunatities while reporting.
pls chk this
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/documents/a1-8-4/how%20to%20handle%20inventory%20management%20scenarios.pdf
compression with marker and no marker update
where u can see the marker update option?
Hope this helps,

Where can i find the option "no marker Update"

Hi ,
i want to know where this No marker update option is?
Thanks in advance
Ravi

hi ravi..
In the context menu of cube >Manage>Compression tab, u will find this check box.
It holds the non-cumulative value(like stock balance).
If you choose this option when compressing Non cumulative cube; the reference point is not updated but the request are moved to Request 0(usual compression); you must do this for compressing historical data; for example use this option to compress data before Jan 2005.
Marker updates do not summarize the data. In inventory management scenarios, we have to calculate opening stock and closing stock on a daily basis. In order to facilitate this, we set a marker which will add and subtract the values for each record.
In the absence of marker update, the data will be added up and will not provide the correct values.
Compression makes the stock calculation(updation) as on the last date for which the records uploaded.So it is nothing but doing calculation inadvance rather the making system to do this calculation at the time of query execution.
The same explained in the how to handle inventory in BIW in better way with example.
If we donot do this compression of delta loads, the result does not be wrong but system takes more than time to do forward and then backward calculation.
For non-cumulative InfoCubes, you can ensure that the non-cumulative marker is not updated by setting the indicator No Marker Updating. You have to use this option if you are loading historic non-cumulative value changes into an InfoCube after an initialization has already taken place with the current non-cumulative. Otherwise the results produced in the query will not be correct. For performance reasons, you should compress subsequent delta requests.
See:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/documents/a1-8-4/how%20to%20handle%20inventory%20management%20scenarios.pdf
When you load historic non cummulatives you need to set the "No Marker Updating" indicator if initalization has already taken place otherwise your data will be erroneous.
chk this thread too..
No marker update
hope it helps...

No Marker Update in InfoCube compression

Hi,
Please explain me how the No Marker Update works in InfoCube compression of inventory management.
Best Regards,
Ramesh

Marker update when uploading/compressing
We will use an example to explain the procedure for a stock InfoCube
when executing a query. The scenario is as follows:
     Current date: 31.03.2002
     You have set up an opening balance of 100 units on 01.01.2002 and loaded it into the stock InfoCube.
     Historical material movements from the three previous months (October 2001:10 units; November 2001: 20 units; December 2001: 10 units) are loaded into the BW.
     Since this point, successive material movements have been transferred into the BW in the delta process. Delta requests transferred at the end of January (20 units) and February (10 units) were already compressed after successful validation, the last delta request from the end of March (10 units) is still in the InfoCube in uncompressed form.
To help explain the role of the marker (= reference point), the different upload steps are considered over time.
After uploading the opening balance, the InfoCube looks like this:
You can see that the opening stock is not assigned to the actual date, but posted to a
point in infinity (0CALDAY= 31.12.9999, for example).
After the three previous months have been uploaded and compressed, the InfoCube
content looks like this:
Note here that the marker value remains unchanged at 100 units. This can be achieved
using the No marker update indicator during compression (see section 3.2.2, step 6).
The marker is thus not changed.
After successively uploading deltas from January to March, of which only the first two are
compressed, the InfoCube content has the following appearance:
Compressing the requests for January and February executes a marker update that can
be seen by the marker now having the value 130 units. The values for March have not
been included in the marker yet.
Please go though the document:
How ToHandle Inventory Management Scenarios in BW
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f83be790-0201-0010-4fb0-98bd7c01e328
Cheers
Pagudala

Inventory - No Marker update is set for delta loading, any impact ?

Dear all,
Since several days the daily delta on inventory cube is done with flag "no marker update set".
What are the possible issue ?
Do we have to reload the data or can we just set the flag as unchecked ?
Thanks for your help
Best regards
Christophe
Edited by: Christophe Courbot on Sep 15, 2011 5:04 PM

Hi,
Pl check below
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.
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:
1) 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).
2) 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 maker => check the marker update option.
Relevant FAQs:
1) The marker isn't relevant when no data is transferred (e.g. during an delta init without data transfer).
2) 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).
Reference information:
Note 643687 Compressing non-cumulative InfoCubes (BW-BCT-MM-BW)
Note 834829 Compression of BW InfoCubes without update of markers (BW-BEX-OT-DBIF-CON)
Note 745788 Non-cumulative mgmnt in BW: Verifying and correcting data (BW-BCT-MM-BW)
Note 586163 Composite Note on SAP R/3 Inventory Management in SAP BW (BW-BCT-MM-IM)
Thanks and regards

NO MARKER UPDATE

Similar Messages

Maybe you are looking for