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

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

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

Why do we use Unserialized V3 update for Inventory Management?

Hello Experts,
I have question on LO Cockpit extractor.
Why do we use Unserialized V3 update for Inventory Management (2LIS_03_BF) ?
Are there any reasons behind?
thanks a lot
Padma

Hi,
V3 gives you good performance and you use it when the order of data is not important they way it was posted in OLTP, this method is used.
Cheers,
Kedar

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,

Regarding update rules activation in inventory management(2LIS_03_BF)

Hellow gurus,
i am working on inventory management with snap shot scenario for that we are using 3 business content datasources they are (2LIS_03_BX, 2LIS_03_BF, 2LIS_03_UM), now i want to activate the update rules for infosource(2LIS_03_BF) & cube, when i check the update rules it shows every thing is ok, but not activating ,please could you give me the suggestions
Regards,
Chandra.

bf setuptable filling based on posting date
give the posting date and give the name of job run
give the termination date and time
execute in background.you you can start the more jobs
depending on your data.you have bulk data you can divide the
jobs in based on posting date.
after that check the status in sm37.

Inventory Management Scenario

Hi BW Experts,
I was working on the Inventory Management screnario as in How to Handle Inventory Management Scenarios in BW with cumulative KFs. I read many of the forum postings but I am still little bit confused about the sequence of the loading. As per my understanding, BX goes to 0IC_C03 bus. content cube and snapshot ODS. BX load in 0IC_C03 is compressed. Then BF and UM goes to snapshot ODS, snapshot infocube and 0IC_C03 (initilized for Delta). Then the generic extractor from snapshot ODS goes to snapshot infocube as monthly load and also to ODS itself. Now the questions are:
1-) Is the sequence above correct? If not could you pls. explain? What are reasons behind of this?
2-) What are the functions of these objects exactly, in detailed? How do you validate data (by comparing 0IC_C03 and snapshot cube)?
3-) Why the generic extractor goes to infocube and ODS together, what is the reason?
4-) Is snapshot infocube loaded with BF and UM as delta daily? After initialization am I going to load the snapshot infocube every night or just the 0IC_C03?
5-) Do I have to put 0CALDAY into Agg. Ref. char. in the maintenance screen of the defined custom KFs (Z* keyfigurs for this scenario) or just in the report enough?
6-) Are the routines working correctly except for
diff_month(2) type i-> "i" is going to be changed into "n"
After I loaded in the above sequence when the bx is loaded into 0IC_C03 cube transferred data records are less than added. What is the reason?
Contributions are highly appreciated. Thanks.
Best Regards,
Message was edited by: John Seker
Message was edited by: John Seker

Hi Loic
Can u please see if all the steps listed below are OK.
While setting up the IM Scenario
I have jotted down the steps with valuable inputs from you and paper 'How to Hanlde IM scenarios'
Please find the steps below. Kindly review them and let me know in case I have got anything wrong or missed out on anything.
1. Transfer Business Content Datasources 2LIS_03_BX , 2LIS_03_BF, AND 2LIS_03_UM in RSA5.
2. Go to Transaction LBWE, Activate Datasources 2LIS_03_BF, AND 2LIS_03_UM.
3. Go to Transaction MCB_ select SAP BW usage 'Standard' Radio button.
4. Save it.
5. Go to Transaction MCNB, enter name of run Stock_init. Enter Termination date in future. Enter Datasource as 2LIS_03_BX.
6. Execute the initialisation.
7. Entries can be found in SETUP Table MC03BFSETUP & MC03BFSETUP.
8. Run SETUP for 2LIS_03_BF, AND 2LIS_03_UM using TCodes OLI1BW and OLIZBW respectively.
9. Run the extraction for 2LIS_03_BX in BW.
10. Compress the request with No Marker Update NOT SET i.e. unticked or unchecked.
11. Run the extraction for 2LIS_03_BF in BW.
12. Compress the request with No Marker Update SET i.e. ticked or checked.
13. Run the extraction for 2LIS_03_UM in BW.
14. Compress the request with No Marker Update SET i.e. ticked or checked.
Steps 1 and 2 shall be executed in Development and transported to production and step 3 onward should be carried out in Production itself with Posting Block.
Thanks in advance.
Regards
PB

Indication of documents about Inventory management in BW

H
I've got this excellent document "How to handle inventory management scenarios in BW". Very clear, easy to understand.
I'd like to go into more details about 2LIS_03_BX (initialization of the current stock), compression of requests and marker update.
Does anyone have indication of other documents that deal with these subjects?
Thanks in advance
César Menezes

Hi Cesar:
Please refer to the documentation below:
"10 important points to consider while working with inventory management", blog by Ranjit Rout.
/people/ranjit.rout/blog/2009/06/14/10-important-points-to-consider-while-working-with-inventory-management
"Non-cumulatives / Stock Handling"
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/93ed1695-0501-0010-b7a9-d4cc4ef26d31?quicklink=index&overridelayout=true
"BI Inventory Management- Data Loading", paper by Gaurav Kanungo.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/906b837a-0d54-2c10-08b8-bde70337547e?quicklink=index&overridelayout=true
"Inventory Management (0IC_C03) Part - 1", paper by Surendra Kumar Reddy Koduru.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/60101663-3cb7-2c10-3687-8d1e0ef51b0d?quicklink=index&overridelayout=true
"Inventory Management (0IC_C03) Part - 2", paper by Surendra Kumar Reddy Koduru.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d0783925-f4be-2c10-9c89-ffa108f72547?quicklink=index&overridelayout=true
"Inventory Management (0IC_C03) Part - 3", paper by Surendra Kumar Reddy Koduru.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e00860a4-350f-2d10-29a0-fc09681a8bae?quicklink=index&overridelayout=true
"Inventory Management in SAP BW", article by Harishraju Govindaraju.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/9054ac59-aac4-2d10-3d9b-df98c52b4f31?quicklink=index&overridelayout=true
"Loading to the Inventory Cube 0IC_C03", blog by Akshay Chonkar.
/people/akshay.chonkar2/blog/2010/05/19/loading-to-the-inventory-cube-0icc03
"Insights into Cube compression", blog by Arun Varadarajan.
/people/arun.varadarajan/blog/2008/08/19/insights-into-cube-compression
SAP Note 643687 - "Compressing non-cumulative InfoCubes"
SAP Note 745788 - "Non-cumulative mgmnt in BW: Verifying and correcting data"
SAP Note 1548125 - "Interesting facts about Inventory Cubes"
Regards,
Francisco Milán.
Edited by: Francisco Milan on May 7, 2011 12:08 PM

How to handle inventory management scenario

Hi All,
In How to handle inventory management scenario whitepaper, I fail to understand the basic difference between 'Inventory Management with non-cumulative Key Figures' and 'Inventory Management with Snapshots'. Can anyone please explain me the basic difference.
Thanks
PB

Hi Loic
Can u please see if all the steps listed below are OK.
While setting up the IM Scenario
I have jotted down the steps with valuable inputs from you and paper 'How to Hanlde IM scenarios'
Please find the steps below. Kindly review them and let me know in case I have got anything wrong or missed out on anything.
1. Transfer Business Content Datasources 2LIS_03_BX , 2LIS_03_BF, AND 2LIS_03_UM in RSA5.
2. Go to Transaction LBWE, Activate Datasources 2LIS_03_BF, AND 2LIS_03_UM.
3. Go to Transaction MCB_ select SAP BW usage 'Standard' Radio button.
4. Save it.
5. Go to Transaction MCNB, enter name of run Stock_init. Enter Termination date in future. Enter Datasource as 2LIS_03_BX.
6. Execute the initialisation.
7. Entries can be found in SETUP Table MC03BFSETUP & MC03BFSETUP.
8. Run SETUP for 2LIS_03_BF, AND 2LIS_03_UM using TCodes OLI1BW and OLIZBW respectively.
9. Run the extraction for 2LIS_03_BX in BW.
10. Compress the request with No Marker Update NOT SET i.e. unticked or unchecked.
11. Run the extraction for 2LIS_03_BF in BW.
12. Compress the request with No Marker Update SET i.e. ticked or checked.
13. Run the extraction for 2LIS_03_UM in BW.
14. Compress the request with No Marker Update SET i.e. ticked or checked.
Steps 1 and 2 shall be executed in Development and transported to production and step 3 onward should be carried out in Production itself with Posting Block.
Thanks in advance.
Regards
PB

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

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...

Sharepoint 2013 Active Directory Import- Manager field not updating

Hi,
SharePoint 2013 Active directory import -Manager field not updating
Concern/Issue-
We are using SharePoint and configured the Active Directory Import .First import it seems everything is working fine and OOB Organization chart built using User profile data is coming out right.
Now the user is moved from one Organization Unit to Another.
Now our Manager field is not Updating .There is change in AD manager attribute but not reflecting in the SharePoint User profile.
Manger field is mapped to "manager" attribute in SharePoint.
We tried removing the user and Re-Import using Incremental import but no luck.
Thanks for help in advance
Sachin

Moving a user from one OU to another in AD won't normally change the Manager attribute in AD. You would need to edit the user's organization settings to change the manager value in AD. I've also seen these changes not be picked up unless something
other than just the manager field in AD changing. Try changing something like Office location and see if the manager change is picked up by AD Import.
Paul Stork SharePoint Server MVP
Principal Architect: Blue Chip Consulting Group
Blog: http://dontpapanic.com/blog
Twitter: Follow @pstork
Please remember to mark your question as "answered" if this solves your problem.

Stock Valuation - Inventory Management Cube

Dear Sap Gurus,
We have implemented the Inventory Management Cube in BW.
Quantities are correct, but we have difference on the stock valuation.
For some material stock value are correct, for some other they are not correct.
A saw a lot of OSS notes and how to on this subject, I am trying to solve this issue using these documents, but based on your experience could you explain me how you solved this issue ????
Thanks,

Hi
Did you follow the correct steps?
Initialisation of BX data in the first step.(Loading of Opening Stock)
Then The request in which the opening stock was loaded must always be
compressed with a marker update
Init load of BF And UM in the second step
The request in which the historical material documents were contained
must always be compressed without a marker update and
Successive delta uploads must always be compressed with marker
updates
Check this whether you have done this or not.
Because of missing the steps here also would give you wrong values,
Regards
Ram

Queires on Non-Cumulative Inventory Management Cube 0IC_C03 Not Working

Hello all.
I am trying to use the 0IC_C03 Inventory Management cube with non-cumulative key figures. I followed the How to...Handle Inventory Management Scenarios in BW paper to a tee.
Steps I followed:
1. Ran initialization of beginning balance with 2LIS_03_BX
2. Ran the historical job with 2LIS_03_BF
3. Uploaded to BW the Initialization (BX) and compressed without setting the "No Marker Update" flag
4. Uploaded the historical movements (BF) and compressed setting the "No Marker Update" flag
Now, to this point, everything was fine. Quantities were as expected. Dollar values were as expected. The problem occurs once I load deltas:
5. Loaded delta for 2LIS_03_BF and compressed without setting the "No Marker Update" flag as instructed in the How To... paper
Query example:
MATERIALA:
Initial Stock Balance = 1000 EA
Delta had stock issue of 150 EA (so the stock balance should have decreased from 1000 to 850)
Now, I have the record in BW showing the stock issue of 150. However, the non-cumulative key figure within the query still shows 1000. And when I drill down by calendar day, I would expect the result to show 850, but it seems to add the 150 before taking it away resulting in 1000 which is actually the initial stock balance. It is like it is not recognizing the updates.
Any help would be appreciated.
Thanks,
Brent

Hi!
Here is what helped in my case, very similar to your:
In DTP for 2lis_03_bx (not only in infopackage, as it is said in manual!) you have to change "Extraction Mode" parameter to "Initial Non-cumulative for Non-cumulative values"

Inventory management

Hi,
In Inventory management ...for reports i am using standard queries taken from metadata repository but i am not using the standard cube instead using a custom cube and copied all those queries on to custom cube...since for all figures routines have been written in update rules...
please tell me wheather i need to test them with R/3 to know whether data flow or data entries are right or no...
if i have to test from BW to R/3 then i need to test them in Standard reports of R/3 not using RSA3 becoz the values of key figures are calculated during runtime and i dnt get them in RSA3 m i right?
please suggest me where i can search the standard reports in R/3...which transactions i need to use...
e.g.Receipt quantity :Blocked stock(0RECBLOSTC)
WHERE can i get the values for this in R/3?
thanks in advance,
Vijaya

Hi,
The information on "how to validate" given in the note 586163:
TAC MB5B <-> Queries 0IC_C03_Q???
(Stocks/movements R/3 <-> BW)
TACs MC.? <-> Queries 0IC_C03_Q???
(Inventory controlling LIS <-> BW)
Reports MBQUANT and RM07MMFI
(verification of the R/3 data)
Notes 739863 and 745788 provide additional information in this regard, as well as the options that exist to clean up data in BW.
Note 766622 provides you with the option
of creating a LOG file for the extraction.
With rgds,
Anil Kumar Sharma .P

Inventory Management (Advanced - Marker update)

Similar Messages

Maybe you are looking for