Delta in Inventory

HI All,
Please clarify:
1.Does delta is working on what fileds in Inventory (2LIS_03_BF)? (MBELNR,MJAHR,ZEILE)?.
2.In RSA6 we checked this Delta enabled Data source. But how do we check the fields those are using for Delta extraction?.
Thanks in advance.
Sri.

To answer your questions..
(1) Delta is by document via LO cockpit, this means as the document is changed/created then they are added to the LBWQ then later to RSA7.
(2) Please look in transaction LBWE under area "03" for the datasource and how to enhance it.
cheers!
/smw

Similar Messages

Records is not coming in Delta for Inventory Cubes.

Hi..All
We are working on BW3.5 SP11 since 01.07.2005.
We are facing a very serious problem in Inventory management data extraction from R/3 since 24.08.2005.
Our active data sources of Inventory Mangement are as follow.
     2LIS_03_BF
     2LIS_03_BX
     2LIS_03_UM
We were regularly getting records through delta as per given schedule after intialisation on 01.07.2005 to till 23.08.2005.
On 24.08.2005 -- Delta schedule we had find out there are some records that were created in R/3 did not come in BW.
On 24.08.2005 -- records loaded in PSA was 20550. The same is appering in RSA3(EXTRACTORS) also.
The Last material document loaded was 4900154552 date 23.08.2005 time 16:56:05 of R/3, but there are many other material documents that were created on the same day but are missing in the extraction.
On 25.08.2005 delta schedule records are getting 0 (Zero). Not a single record is getting in RSA3 (Extractor).
on 26.08.2005 situation is still as it is. No record is coming.
Where as our average records per day is approx. 20000 nos.
The update mode for inventory is Unserialised V3 update, and the update program in R/3 is running perfectly fine as per schdule with no errors.
We could not understand why suddenly stop the extraction of records FOR INVENTORY MANAGEMENT. Because rest all
data sources like Purchasing,Sales and Distribution,Quality Mangement, and PP is working fine on same date.
We checked the data in extractor checker with giving UPDATE MODE "F"-Transfer all requested data.
Still it is showing 0 (Zero Records) for data sources 2LIS_03_BF,2LIS_03_UM.
The situation is still as it is as of now.
This is very crutial for our business. All inventory reports are showing data which is 3 days old.
Please give your advice on this issue. And how to get the records in PSA from R/3.
Regards,
Navin

Hi Ravindra,
Thanks for giving input. The problem got solved.
There was a problem with QRFC Table. Tcode LBWQ
Status was wait.
Thanks for giving feedback.
Regards,
Navin

Deltas of inventory

Hi experts,
Should we compress the requests of delta loads of inventory.
Thanks & Regards,
V N.

VN,
We need to compress the request with the marker update, then only the values for these requests will be considered in the query calculation. Without that u will get the wrong results in the output.
U need to follow this sequence:
1] Run the extraction for 2LIS_03_BX in BW.
1-a] Compress the request with No Marker Update NOT SET i.e. unticked or unchecked. This is one time activity.
2] Run the extraction for 2LIS_03_BF in BW.
2-a]. Compress the request with No Marker Update SET i.e. ticked or checked.
3]. Run the extraction for 2LIS_03_UM in BW.
3-a] . Compress the request with No Marker Update SET i.e. ticked or checked.
http://help.sap.com/saphelp_bw33/helpdata/en/5b/8dc73cee4fb55be10000000a114084/frameset.htm
Refer
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/0ea8a990-0201-0010-2796-fa9ae8691203
Re: Inventory Management
Re: 2lis_03_BX
Re: Inventory Modelling
Re: 0IC_C03
U need to compress the regular Delta requests to get the proper values at the report level.
Thanks
Assign points if this helps

Delta - Purchasing , Inventory Cubes

I want to set up the delta mechanism for 0PUR_C01 , OPUR_O01 , 0PUR_C08 , 0IC_C03 and 0COPC_C04 business content cubes.
In RSA7 , for the relevant datasources , I see 0 records. Can some one tell me , how to enable the delta for these datasources:
2LIS_02_ITM
2LIS_02_SGR
2LIS_02_SCN
2LIS_02_CGR
2LIS_03_BF
2LIS_03_UM
0CO_PC_ACT_02
0CO_PC_ACT_05
Thanks

Hello Jimmy,
Assuming that you have installed these from the business content and the respective datasources on r/3 side are also active(i.e u can see all of these in rsa6),
you need to run the setup on r/3 side in the logistic cockpit section for the respective application component.
The set up tables when filled, can be pulled(the data) in bw with initialisation option.
Once the init requests in these cubes are loaded, you need to set up delta jobs on the r/3 side. please refer to the types in the earlier answers/posts like direct delta etc.
once the delta jobs are scheduled on r/3 side, you can view them in rsa7. the delta queues are populated after the delta runs on r/3 side and seen in rsa7.
these then can be pulled in bw by schduling bw jobs with delta options.
the selections used in inits can be automatically picked up in these delta jobs(on bw side).
hope it helps..
thanks,

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

Delta in generic extractor.

Hi Everyone,
I have created one of the generic extractor on a table and the other one on a view. While selecting the GENERIC DELTA, I let the numeric pointer selection checked.
Now, my question is will it allow me to do delta load in my cube using this extractor?
2nd question is how?
3rd question is if not then what is the change that I need to make so that it allows me to load the delta load. How this changes need to be made can you please explain step by step. thanks in advance.
My issue arose after loading the data when I went to change the InfoPackage to load the delta part, I realised in my InfoPackage I do not have the choice to load delta. How do I settle this. Actually this is an inventory cube where the data is loaded at the end of each month and now when I wanted to test it for today's month I realised that I do not have the choice to load delta for inventory load.
Please explain. Thank you once again in advance.

1. my question is will it allow me to do delta load in my cube using this extractor?
Yes... you build Generic Extractor with Delta based on Numeric Pointer. Material Documents is the Perfect Example for that (We can't Sales Document or Purchase Document for this).
2. 2nd question is how?
Simple enable Material Document Number Fileds for Numeric Pointer (Select Numeric Pointer... provide Mat. Document No. field i.e. MBLNR).
3rd question is if not then what is the change that I need to make so that it allows me to load the delta load. How this changes need to be made can you please explain step by step. thanks in advance.
you need to create Material Documents in SAP R/3. If you build your Extractor on MSEG Table. You need to create any Material Document which populates in MSEG.
I don't remember wht exactly option we will get in Infopackage for Numeric Pointer. To my knowledge, it should give Delta only in Update Tab page.
Hope this helps.
Nagesh Ganisetti.
Assign points if it helps.

Why we use unserialized specially for inventory

Hi
Lo extraction mostly we use queue delta, only inventory purpose we use unserialized v3 we use , what is specific reason use this
regards
suneel.

Hi ,
Unserialized V3 is used only when you dont require the document serialization, for example in inventory extraction i.e., if you are loading data into 0IC_C03, u can use unserialized V3 update.
Pls check this blog,
/people/happy.tony/blog/2006/11/24/gist-of-lo-cockpit-delta
find the blog series from Roberto Negro
/people/sap.user72/blog/2004/12/16/logistic-cockpit-delta-mechanism--episode-one-v3-update-the-145serializer146
Hope this helps...
Regards
CSM reddy

Inventory doubts 1

Hello Friends,
Please help me understand some terms and concepts of inventory:
1. why / is it : always direct delta for inventory ?
2. Why Post Stock before filling setup tables?
Thanks in advance. Hope you could help.
extr-bw

HI the tcode to fill the inventory setup tables and purchasing is different.
inventory 03
purchasing is 02
you can load using the posting date for inventory.
what i have done is if i am getting data from table vbak
and if i want to load the data from 01.01.06 to 31.03.06
go to se15
give 01.01.06 in the fiels AEDAT.
Copy the the first document number
give 31.03.06
same way copy the last documeny number
and give them in
olixbw
and start
if you try to run the setup for years together it will take more 1 day sometime depending upon the system again
cut it to pieces and schedule as background
hope this helps
let me know if unclear

R/3 problem

hello, can somebody tell me how to check the schedule for lbwe jobs? if i have queued delta for inventory control which is number 3. i want to know what schedules documents in that extractor are following to go from lbwq to rsa7( like hourly, daily, etc.) how can i find out?thanks.

LIS-BW-VB_APPLICATION_XX_xxx(XX - job application, i.e 03 for inventory, xxx- client no) is job name for LBWE jobs.
U can check in sm37 by giving this job name..U get the jobs scheduled, released and finished. If you check the start condition of this job, u come to know the frequency of this job running in the system.
Hope this helps..
Thanks & Regards,
Pradeep

Full and delta inventory

Hi all,
I'm studing the new "System planning Deployment and BP Guide" of 10.3 beta.
I see that in a "Daily use test" they schedule "One full and three delta inventory scans per devices".
I did not know that in ZCM10 there were two types of inventory. Is it a new functionality? Anybody can explain to me some info?
Thank you

mauro,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://support.novell.com/forums/

Inventory delta load problem

Hi,
We are facing inventory data load getting below error, Main problem is they got below error in PSA level from 16th june still they changed red icon into green and loaded to incube and compressed. when running process chain they getting same error daily.
Error:
Caller 09 contain an error message
Problem:
-> Data flow PSA->IC, 20th request (it look like have 16th to 20th data) they have changed PSA red request into green and loaded to cube and compressed.
21th request (it look like have 16th to 21th data) they have changed PSA red request into green and loaded to cube and compressed.
Kindly guide me what solution we can give.
thanks

I suggest that you handle this with utmost care. Since it does not look like you have the DSO in the dataflow, recovering the data would be impossible if the cube data is corrupted.
Need to understand the details to be able to give a proper solution.
You can consider request reverse posting option which will post reverse images of the PSA requests under the scope and nullify the value from the cube. Please try this in Dev and quality system, before trying this in Production.
Else, you can create a custom datasource based on this PSA table and reverse the values in the transformation.
If you could identify the documents, created after this delta corruption, you could set them up in source and do a repair full upload.
Please let me know whether it helps.

Inventory Delta Load

Hi All,
for inventory cube ZIC_C03 we ran the init successfully, we are using the deltamechanism as Unserialized Delta,
but when i am running the V3 job it successfully ran with job status is finished,
but when i am checking in RSA7 no records are present, but in SM13 there is records.
could you please anyone give the solution, please suggest me, its very urgent.
Thanks & Regards
Suresh

I suggest that you handle this with utmost care. Since it does not look like you have the DSO in the dataflow, recovering the data would be impossible if the cube data is corrupted.
Need to understand the details to be able to give a proper solution.
You can consider request reverse posting option which will post reverse images of the PSA requests under the scope and nullify the value from the cube. Please try this in Dev and quality system, before trying this in Production.
Else, you can create a custom datasource based on this PSA table and reverse the values in the transformation.
If you could identify the documents, created after this delta corruption, you could set them up in source and do a repair full upload.
Please let me know whether it helps.

Any changes to BI for procument and Inventory in Delta Fun & release notes

Hello Guru's
Are they any changes to BI for Procurement and Inventory, in the DELTA Functionality and release notes. Will anyone reply me any link that will be of great help.
Full points to the link / oss

Hi,
See
Treatment of historical full loads with Inventory cube
Setting up material movement/inventory with limit locking time
The steps in BI 7.
In R3
0. Delete previous data: TC lbwg, application 03.
1. Delete Queue in LBWQ/SMQ1 related to 03.
2. Lock the system, don't allow any transactions from Users.
3. Stock initialization: TC MCNB, structure 2lis_03_bx. (Here Select All Stocks(Including Non-Valuated)).
4. Statistical setup of mat movements: TC OLI1BW or sbiw path
5. Statistical setup of mat movements: TC OLIZBW or sbiw path for 2LIS_03_UM load.
In BI
0. Load initial stock: datasource 2lis_03_bx using InfoPackage and then Run DTP with the following options.
In DTP: Extraction Tab--->Extraction Mode = Initial Non-Cumulative for Non-Cumulative..select this and then Execute.
1. Cube>Manage>Collaps-->Don't select "No Marker Updating indicator" and then compress.
2. Load 2LIS_03_BF and 2LIS_03_UM Initial runs using InfoPackages and then Cube>Manage>Collaps-->Select "No Marker Updating indicator" and then compress.
Now check the data with MB5B In ECC and recon data with Report on 0IC_C03 Cube.
Thanks
Reddy

Inventory Management :Delta IP of BF runs with selection from Init IP of BF

I have an init IP for BF DS which i ran with selection on posting date.
I have another IP for delta for BF without any selection criteria.
But, when i run the delta IP, it runs with the selection on posting date, the same value that i used for init.
Even if i modify and clear the delta IP of any selection, and run it, it still runs with the selection.
How do i rectify this.
Thanks,

that is the correct process. if u do init with some filters then those would be applied to Delta by default. u cannt remove those filters from delta. if u want to do it anyway u have to delete the last init request then the filters wodnt be applied. but in this case u have to rerun ur init again without any filters so that u can get delta.

Non-cumulative Values not showing in Inventory Management Queries

Hi:
Has anyone had a problem with the new version and Non-cumulative key figures not showing up in Bex for Inventory Managemet reports? Specifically, they showed and validated back to ECC for our Development and QA boxes but now in our Regression box they are all showing zeros. Our Cumulative values are all showing correctly still within the Regression box. For example, Total Receipts and Total Issues are correctly poplating values but Total Stock is not.
I have checked and validate that the configuration in the Regression box matches or Dev and QA box.

Found the problem. It had to do with the compression variant in the delta process chain. The compression was set to 'no marker update'. Since we only started receiving measureable deltas in or regression box this is where the incorrect setting showed up. Reinitalized and the deltas are working correctly now.

Delta in Inventory

Similar Messages

Maybe you are looking for