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

Similar Messages

Init Load,Historical Data Load & Delta Load with 'No Marker Update'

What is the difference b/w Compression in Inventroy cube while Init Load,Historical Data Load & Delta Load with 'No Marker Update'???
please help for this quesy..
Thanks
Gaurav

Hi Gaurav,
I believe you will find the answers here...
[http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/e0b8dfe6-fe1c-2a10-e8bd-c7acc921f366&overridelayout=true]
regards
Pavel

SCCM 2012 Update Group inconsistency Problem with Red marked Updates

Hi everybody,
we have a big Problem with our SCCM 2012 R2 CU3 Enviroment, regarding of Update Groups which got out of sync.
we have a SCCM Site Infastructure with one CAS and 4 Primary Sites and on every Site is the SUP Role installed.
I don't know when this failure occours but i think it was after the CU3 Installation. The Installation itself went smooth without any Errors or Warnings.
The Problem is as following. We have some updates in Update Groups (all of them are Core XML Updates) which are out of sync and marked red as an invalid Update on 2 Primary Sites. On the CAS Site and the 2 other Primary SItes they are marked as green (downloaded
yes and deployed yes)
We have no Replication issues regarding the Replication Status (everything is synchronized to 100%) and the Replication Link Analyzer does also show no Problems at all.
I now deleted the Deployments and the SW Update Group waited until the replication was fine and created a new one and downloaded these patches on one of the Primary Sites which had shown this Failure.
The Result was not good. It looks like before. On the CAS and 2 Primary Sites the Deplyment is shown as downloaded but on the other 2 Sites the Status is again Downloaded=no.
Does anybody have any idea what to do now ? I checked objmgr.log and rcmctr. log but found nothing what shows me the way in the right direction.
Thx for your time, and it would be fine if anybody can share knowledge about this failure and how to fix it.
All other Ideas are also welcome.
Thx a lot in advance and have a nice bug free day :-)
Bastian

Hi,
Please try to manually synchronize software updates from the CAS and monitor the WSUSCtrl.log, WCM.log and wsyncmgr.log on the CAS and Primary sites.
Best Regards,
Joyce
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

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.

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.

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.

Marker update problem

hi experts,
i am working the IC_C03,
first i load BX, suppose a record like:
plan material   0calday              received
P1     M1          2009.05.04           100(Received)
then i load BF , there are 3 records :
plan material   0calday              received      issue
P1     M1          2009.02.14           90(Received)
P1     M1          2009.03.18                            50(Issue)
P1     M1          2009.04.21           60(Received)
i set BX with marker update and BF with no marker update,
but after that, there are still 4 records in my cube, so my report get wrong result:
plan material   0calday              received      issue
P1     M1          2009.05.04          100(Received)
P1     M1          2009.02.14           90(Received)
P1     M1          2009.03.18                            50(Issue)
P1     M1          2009.04.21           60(Received)
what the correct result should be after BX(no update) and BF (update)?
i think because the 0calday is different with regard the 4 record, so the 4 record wouldn't be compressed
into one record.
Edited by: liu shaochang on May 4, 2009 4:47 PM

Are you sure your record of 100 has the 0calday as 2009.05.04?
If this record ha 0calday as something like 31.12.9999. Your reult is actually correct.
This is a non-cumulative key-figure. The calculation of stock of a specific day is not a simple summary.
It uses the marker value (100) + all uncompressed records ( in your case, 0) - Compressed records between the date and the current date.
If you try to report stock beyond May 5th. The report should report 100.
If you try to report stock of April 20th, The report should report 100 - 60 = 40.
You might not have done in the right sequence. Immediately after you finish BX, you should do a compress. That would make the entry like the following.
P1 M1 9999.05.04 100 (which i a marker value).

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

What is the use of with and without marker update?

what is the use of with and without marker update?

Hi,
Marker Update Updates the stock values and NO Marker does not.
Generally BX upload has to be compressed with MU and BF(and UM) delta init has to be compressed with NO MU because Stock was updated with BX. And delta loads of BF and UM has to be compressed with MU because these brings new Material movements which will has to give effect to stock.
With rgds,
Anil Kumar Sharma .P

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

What is 'No marker update'? do opening balance have any relation with it?

what is 'No marker update'? do opening balance have any relation with it? i know that 'No marker update' will not update reference point that means it will not change the opening balance date to current data, is it right? please explain.
York

Hi
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 not match with the stock on R/3 side.
Raja

My MacBook pro stop working and it shows folder with question mark after this update, it's not my fault, Apple should solve the problem with out ask me to make payment

After updating my MacBook pro it shows only a folder with question mark on it
It is not my fault, Apple updates problem
They should solve it fir me without make any payment
Thanks

Try starting your computer holding down the option key as soon as you hear the startup sound, and continue holding it. Hopefully, you will see the icon for your startup disk come up on your screen within a minute. Click on that icon and press return. If your machine starts up normally from there, go to System Preferences > Startup Disk and reselect your startup volume

Flashing Folder with Question Mark after Trackpad 1.0 Update

My machine won't boot after installing this update. I get the flashing folder with question mark and can't even boot from the Install DVD either... I just get a frozen spinney wheel at the Apple Logo screen. I've tried resetting the PRAM and everything else that a Googling of the problem suggests. This update bricked my Macbook!!!!
Anybody else having this problem? Anybody have any suggestions or am I stuck with going to see a "genius"?

I've not seen any other posts about it causing problems, worked fine here. You've tried resetting the PRAM the only other thing you could try is:
Boot holding down Apple/S and don't let go until you see scrolling text.
When that stops and you see a root#: prompt enter
fsck -fy
Let it run through all the checks and repairs.
If it fails first time, at any time, or finds and fixes a fault - run the command again and keep doing so (some fixes can take several passes) until it says "Appears to be OK" then enter
reboot

I have macbook mid 2009, with os leopard and I updated it till yosemite now while deleting partition I erased the main hitachi drive , now I have no backups and while switching on it shows folder with question mark,inserting the grey dvd it keep spin

Have macbook mid 2009, with leopard, updated to yosemite, while erasing partition erased hd, dot have backups, powerup shows folder with question mark, inserting grey dvd shows apple and spinning wheel, please help

Clean Install of Snow Leopard
     1. Boot the computer using the Snow Leopard Installer Disc or the Disc 1 that came
         with your computer. Insert the disc into the optical drive and restart the computer.
         After the chime press and hold down the "C" key. Release the key when you see
         a small spinning gear appear below the dark gray Apple logo.
     2. After the installer loads select your language and click on the Continue
         button. When the menu bar appears select Disk Utility from the Utilities menu.
         After DU loads select the hard drive entry from the left side list (mfgr.'s ID and drive
         size.) Click on the Partition tab in the DU main window. Set the number of
         partitions to one (1) from the Partitions drop down menu, click on Options button
         and select GUID, click on OK, then set the format type to MacOS Extended
         (Journaled, if supported), then click on the Apply button.
     3. When the formatting has completed quit DU and return to the installer. Proceed
         with the OS X installation and follow the directions included with the installer.
     4. When the installation has completed your computer will Restart into the Setup
         Assistant. Be sure you configure your initial admin account with the exact same
         username and password that you used on your old drive. After you finish Setup
         Assistant will complete the installation after which you will be running a fresh
         install of OS X. You can now begin the update process by opening Software
         Update and installing all recommended updates to bring your installation current.
Download and install Mac OS X 10.6.8 Update Combo v1.1. From here you can upgrade to Yosemite by re-downloading it from the Purchases page in the App Store.

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

Compressions with No marker updates

Similar Messages

Maybe you are looking for