Set -up tables -delta queue

I have to clear jobs in LBWE. what is the process to do it -how to make sure that all data is is updated and no records in delta Queue at a given time ?

Hi,
I think you mean to say clearing SMQ1 and RSA7 queue. SMQ1 is updated as soon as transaction is done. RSA7 is updated when you run V3 job and pulls data from SMQ1 queue. To clear SMQ1 completely you have to make sure that no transactions are taking place in the system and run V3. After V3 dont allow any transactions in the sytsem.
To empty RSA7 queue run delta package in BW. it will empty the delta queue.
Hope this helps.
Viren

Similar Messages

How to fill set up tables with out missing the delta records

Hi,
I would like fill set up tables in the productioon system of apllication of logistics.
Can you please guide me how do we perform.?
What are points to be considered?
Because,when i start the filling set up table by 10.AM if there are any posting at 10:05,10:06....like that
how can collect them i.e will i miss any records in second delta run?What setps to be taken care?
Thanks in advance
Naresh.

Hi.
You can fill the set-up tables during normal operation hours ,if you load the data into ODS and the update queue is 'Queued delta' .Downtime is needed to avoid the duplicates .But if you use 'Direct delta' you miss the delta documents. Hence it is better to go for downtime approach for this case.
Initially your delta records will be stored in the extraction queue and then when you run the collective job, records will be moved into delta queue. You can run the collective job (LBWE) anytime after the init run.If you need a daily delta ,then schedule this job before the delta loading. You can schedule this job either hrly or daily .This will move your records into delta queue. At the time of delta loading ,all your delta queue records will be moved into BW .
Thanks.

Set up table and transaction data delta load init

Dear experts,
I am following a document left by my predecessor on "post processing activities" for BI prod post go-live.
And for transaction data it says to :
1. execute init with data transfer infopack manually
2. execute delta update infopack manually
3. go to ECC : delete setup data (lbwg)
4. setup the tables for (OLIxxBW)
5. then finally activate Process chains.
Is this sequence correct?
Shouldn't I first delete the setup table, setup the tables and then execute the infopackages??
Regards,
Alice

Hi,
The sequence is correct ,and after this you need to run the job for the collective run in SAP ,which is based on your delta queue.
i.e if you choose direct delta it is not required ,but if you use 'queued delta' then you need to run the collective run to move the delta from the extraction queue to delta queue .This job should run before the delta load.
It is better to fill the set-up table during downtime .ie.no documents posted during the set-up table run. But if you dont have an option you can fill the set-up table during operation hours ,but need fo follow certain steps to get all the delta data. You may need to use 'Init without delta transfer' or early delta initialization in the infopackage .You need ODS as a data target to achieve this . Please search SDN ,you will get more information about this.
Thanks.

Delta queue with transparent tables based on table data changes

Dear all,
once, I was able to find a document (maybe a how-to, if I'm not wrong) that covered a very interesting solution, that I need to implement due to a specific requirement.
Let me explain what's the catch.
In the source system (SAP based), there's a couple of tables that have an unsorted key but doesn't have dates or timestamps. I need to retrieve the information from such tables with a delta procedure. Due to the lack of delta supporting fields, I can't enable generic delta or even FM-based extraction.
The solution I saw once, suggested that Source System's tables could have the change log enabled from within the data dictionary (SE11) and then, that data change monitoring could be coupled with the delta queue mechanism (tRFC or qRFC enabled).
Could you, please, help me with that subject or, if possible, try to recover the document that explained that? Be sure I have put all my efforts trying to find that doc. by myself.
Many thanks,
Michel

Hi Michel,
I'm not aware of any document but I made use of such a delta-mechanism a couple of times. Be aware that you should not use it for large tables or tables of which the content changes a lot (inserts/modifications/deletions). The system will create many huge logs which will consume a lot of disk-space.
Procedure:
1) Activate the logging on your table (SE11 -> enter table name -> go to Technical settings -> flag 'Log data changes')
2) Create a Generic DS based on FM (should be possible!) but do not touch the delta functionality; this has to be build into the FM
3) For the FM e.g. use a copy of RSAX_BIW_GET_DATA_SIMPLE
4) Customize the code to your needs; in the first call fetch the data from the change logs using FM DBLOG_READ_WITH_STATISTIC
5) This FM has dates and times as import parameters. As you don't have them you could create a Z-table in which you keep track of the extractions done. For the next load you then exactly know which logs to fetch (since stored date & time of last load).
Hope this helps you getting up to speed! It's a bit of a hassle but once set up will work fine.
Grtx
Marco

Emptying Delta queues before filling a setup table

How do I empty the delta queues? I want to carry out this task just prior to filling a setup table. Thanks

Hi Sekhar,
Thanks for that, I was on a flight anyway, just got home. I was thinking on the plane about the previous point that you mentioned wrt the collection run. I think I understand the point that you were trying to make is this a correct understanding
1) System is locked
2) Do a collection run - the reason for this is that there may be postings which have not been placed on the RSA7 queue since the last collection run
3) Do Delta load twice
Does that make sense. The points that you have raised otherwise, I will post a question otherwise on the steps I will look to take just to get confirmation I am not missing anything

Number of records in Delta Queue in table level.

Hi All,
I want to know the number of records in Delta Queue for a particular database in Table level. Right now in Production, i dont have access to TCODE RSA7. I just trying to check the Table TRFCQOUT but i am unable to see the exact count of records specific to data source. Can you please provide any other table to see the data and the count of records in delta queue specific to each data source.
Thanks.

Hi Jalina,
Check the follwing tables:
-ARFCDATA
-TRFCQOUT
-ARFCSTATE
In case you can't find what you need in the above tables. You can always ask a temporary access to RSA7 transcation to your basis team or ask them to give you the required information from RSA7 themseleves (of course provide to them a step by step procedure) .
Hope it helps.
Amine

Deleted Delta Queue and setup tables on R/3 side

Hi Gurus,
We are in the process of BW upgrade to NW 2004s. There was some confusion and I deleted the delta Queues in RSA7 (delete button on top) and setup tables too.
Now we have refilled the setup tables but nothing is appearing in RSA7 now.
Do we need to reinstall datasources and then replicate in BW?
Please help.
Regards,
Anil

Hi,
You'll need to initialize the datasources again for anything to show up in RSA7.
Now are the R3 users also locked out on the R3 side ? Are any Master data being converted, created ?
If that's the case and users are doing any transactions on the R3 side, you've basically lost the delta data from when you deleted the delta queues to the time you are going to run the inits. There's no way excpet a full update for you to recover all that data. So if R3 side processing is happening as usual, would suggest you start planning on getting the lost data back into BW post upgrade.
Cheers,
Kedar

Filtering Setup-Table and same filtering for Delta-Queue needed

Dear All,
I'm looking for the best solution to do the filtering for the delta-queue.
In program RMCVNEUA I'm filtering (excluding specific SalesOrg) data for the setup-table creation. I'm loading these data to the BW system.
BUT now my issue is, that with the delta-queue I'm getting also data for the SalesOrg I have excluded in the setup-table, as I have no filter for the delta-queue.
My Question: Where/How to filter by the same criteria the entries for the delta-queue?
Thanks for your support,
Peggy
some more details: Application 11; Queue-Name MCEX11; using 2LIS_11_VAHDR, 2LIS_11_VASTH, 2LIS_11_VAITM, 2LIS_11_V_SSL

Dear Arvind,
if there is no way in R/3 the solution must be in BW, but how exactly should that look like in the best/smartest way?
Let us look in detail at an Example:
DSO 0SD_O03 is getting data from 2LIS_11_VAHDR and 2LIS_11_VASTH.
1) For VAHDR I have the chance to delete not needed VKORG already in the InfoPackage, or load first to PSA and than filter in DTP or delete in Startroutine in Transformation.
2) BUT for VASTH, which has no VKORG information at all, I'm only able to delete the Dataset after it's loaded/activated in the DSO, as the rubbish-Dataset won't have any 0SALESORG. How to do that?
Thx,
Peggy

Filling of set up tables for Full and Delta updates

Dear Gurus,
How do I go about filling the set up tables if I want to load historical data to BW using LO **** pit when set up table is running on delta ?
I want to know how many set up tables will be there for each data source, Because if set up table is running on delta and using the same table I want to load historical data also then will I have to delete and fill set up tables or there will be a separate set up table for full upload and delta ?
If we have multiple set up tables for one data source then in the T-code OLI*Bw, where * -> App logistics num, so to fill I just say OLI6BW, then which set up table it is going to refer.
Clarify my doubt and get rewarded with plenty of points.
Regards
Mohan

Hi,
Filling up the set up tables depends on the datasource.
there are different T-codes for the respective extract structures
OLIIBW transaction PM data
OLI1BW INVCO Stat. Setup: Material Movemts
OLI2BW INVCO Stat. Setup: Stor. Loc. Stocks
OLI3BW Reorg.PURCHIS BW Extract Structures
OLI4BW Reorg. PPIS Extract Structures
OLI7BW Reorg. of VIS Extr. Struct.: Order
OLI8BW Reorg. VIS Extr. Str.: Delivery
OLI9BW Reorg. VIS Extr. Str.: Invoices
OLIABW Setup: BW agency business
OLIFBW Reorg. Rep. Manuf. Extr. Structs
OLIIBW Reorg. of PM Info System for BW
OLIQBW QM Infosystem Reorganization for BW
OLISBW Reorg. of CS Info System for BW
OLIZBW INVCO Setup: Invoice Verification
OLI7BW is the tcode for Sales Order.
Hope this solves Ur issue....
Assign points if helpful..
Rgs,
I.R.K

How To Find The Delta Queue Table

Hi All,
Can anybody guide me, how and where can we find the table for the delta queue.
Regards
rahul
Message was edited by: rahul kharya

Hi Rahul,
You can find the delta queue in RSA7.
Check this post:
Delta Queue
Bye
Dinesh

Delta package not fetching all records from Delta queue in r/3

Hello,
I have loaded Goods Movement Data using 2LIS_03_BF datasource into my BI system.
The Delta has been initialized and everyday the delta is being moved from r/3.
I observed that when I execute my delta package not all delta records are fetched into PSA from r/3.
For Ex: Before starting my delta package I checked in SMQ1 of my R/3 system and see that there are around 1000 records.On executing the delta package I see that the record count is reduced from 1000 to 400 in SMQ1.On executing the delta package again I get the remaining 400 records into my PSA.
Shouldn't the delta package get all records from the queue on single execution??
Is there some setting to define the nr of records to be loaded?
I'm confused with this behaviour.Please help me understand this behaviour.
Thank You.

Hello,
First thing: the data is not transferred from the SMQ1 queue, rather the data is transfered to BW from the RSA7 Delta queue. You need to check the number of records present in the RSA7 queue.
Since SMQ1 is involved, i think you are using the unserialized V3 update method. In this method, when data is first written to the application tables, it is first transferred to the SMQ1 update queue,then via a job to the LBWQ extractor queue and then to the RSA7 delta queue. So the number of entries that you see in the SMQ1 queue are not the number of entries that have to be transferred to BW but rather the records that are waiting to be transferred to the extractor queue in LBWQ. Similarly, in LBWQ, the number of entries displayed here are not the no of entries that are going to be transferred to BW, they are the no of entries that will be transferred to the delta queue RSA7 when the next v3 update job runs.
If you want to check the number of records that will be transferred to BW, select the datasource in rsa7 and then click on the display data entries button.
Hope this helps.
Regards.

Not getting set up record in Set up tables

Hi ,
I am able to see revaluation records in MB5B (Stock on posting date) for one perticular posting date. but this record i am not able to see in Bw side ,even its not avail in RSA3 level.
So wat cud be the reason its avail in data base table but not filled in Set up tables ?
regards
raja

Hi vishwanath,
This is bcoz of
U have not done the delte delta queue( In LBWQ "MCEX03" entries).
first U have to delete the MCEX03 Entries ---> then only u have to do fill the setup tables.
follow these steps:
1.First goto LBWQ --> delete the MCEX03 Entries.
2.Refresh .
3.Check the datasources in RSA3 ( Datasources Should show Zero Records )
4.Do the Fill setup table.
5.Then check once again LBWQ ---> It should not have MCEX03 Entries.
6. Check Datasources in RSA3 ( Datasources should have data).
7.Do replication & Extarct data.
for ur problem this is the solution ( I have faced this).
Thanks,
kiran.

LO Set up tables deleted while upgrading the source sys from 4.6c to ECC6

As a part of ECC6.0 upgrade tasks, our BASIS team deleted all the LO set up tables in the source system(4.6C) and . After the upgrade, we are not finding any queues in RSA7 or in SMQ1. But, we have a lot of Delta's and few full loads are running on BW (3.1) side for these LO's.
1. What are the steps we need to take inorder to enable/ work the existing delta's and Full Loads in BW(3.1). With the new ECC6.0, we don't have plan to enhance any data sources. So, do we need to set up / fill up the tables again for LO's? If yes, Since we have huge data in source system , it will take a lot of time to fill the tables,,,,Is there any option to fill the tables only for the specific period and enable deltas?
Please help urgently interms of providing step by step guidelines.
2. We also have the following DS (Delta enabled) with the existing source system. Please advise how to make to work for these delta's once after the source system upgrade.
0PM_OM_OPA_2
0PM_OM_OPA_1
0FI_AR_4
COPA DATA SOURCE
Advance Thanks.

BW USA,
I think the options are given clearly. You will have to reload the data and I hope you have the DSO(Dataware House Layer) used in your BW side before the data is going to the Cube, otherwise you would have to do a slective delete and load that data to avoid duplication.
There is one other way, but I have never tried it. I am sure your Basis team would have taken a backup of the system before upgrade. Try to find whether you can restore the delta queue (advice from SAP would be helpful as there are many control tables need to be in sync). If this option is not possible then you would have to do what is already given.
Any 0FI_* data sources, you can go by the last available period and you can reinitialize without data transfer and load the missing whole period, as these are after image data you would have a DSO inbetween and you should not have any problems.
For CO-PA whether it is Account or Cost based you can easily re-establish the delete and covere the missing by fiscal period load with repair.
The steps for FI & CO are below.
1. Reload missing data by period with FULL LOAD WITH REPAIR option.
2. Re-init with conditions (if you already had any) without data transfer.
I think this should fix your issues. I have not used the other two data sources.
Goodluck,
Alex(Arthur Samson)

Problem about fill set up table

Hi all,
I got a problem when I run the fill set up table for sales billing data source. what I did is:
first delete the setup table then oli9bw->type in a sales document no.(as I only want this order data), then give a run name, last execute, but I got the message as follow:
Data source 2LIS_13_VDITM contains data still to be transferred
Could you pls explain what this means, and what should I do to solve the problem
Thanks

Set up table definition
Setup table is store the historical data, where as the delta records are updated in delta queue not to set up table.
So once historical data is loaded you can delete the contents of the set up table.
name is extract sturcture of your data source + setup
also data is taken from setup table when an init / full/ full repair load is done.
so in order to take ur records from the table delete the setup table(LBWG) and initialize it with ur records.
You can find the contents SE16
Filling set up tables
transac LBWG
+ SBIW -> Logistics -> Managing Transfer Information Structures-> Setup of Statistical Data-> Application-Specific Setup of Statistical Data
set up tables
Set up tables
Set up tables
view of set up tables data in se11??????????
Set Up tables..
lo: delete set up tables: DOUBT
LBWQ is the extraction queue and RSA7 is delta queue. Data is sent to delta queue from extraction queue through collective job scheduled in transaction LBWE.
when we want to extract the data using LO Cockpit, the data will be come to the extraction queue first and from there it will processed to the delta queue. SO lbwq works as a outbound queue.
If the update mode is Unserialised V3 then as soon as the document is posted it comes update table which you can see in Tr. Code SM13. After the jonb is scheduled the records come to RSA7 i.e delta queue from which BW pulls the data
If you use u201CQueued Deltau201Dupdate method then the data moves to Extraction queue(LBWQ). Then run Collective update to move the data from LBWQ into Delta Queue (RSA7). Then schedule the data using the infopackage by selecting Delta Load in the update tab.
So in If you are going to do Setup table filling, delete the data from LBWQ.
The usage of Extraction queue(LBWQ) comes in to picture in delta loading. But actually system starts collecting the data (whenever there is document creation in R/3) after activating the EXtraction structure.
Steps to Be Performed
We know that there are 4 types of delta extraction that are available in LO. If you use u201CQueued Deltau201Dupdate method then the data moves to Extraction queue(LBWQ). Then run Collective update to move the data from LBWQ into Delta Queue (RSA7). Then schedule the data using the infopackage by selecting Delta Load in the update tab.
Here is Roberto's weblog:
/people/sap.user72/blog/2005/02/14/logistic-cockpit--when-you-need-more--first-option-enhance-it
/people/sap.user72/blog/2004/12/16/logistic-cockpit-delta-mechanism--episode-one-v3-update-the-145serializer146
/people/sap.user72/blog/2005/01/19/logistic-cockpit-delta-mechanism--episode-three-the-new-update-methods
check this out...
LBWQ - T code is for what?
Ttransaction LBWQ
What is LBWQ?
Assign points if it helps
Hope it helps
regards
Bala

Purchasing set up table

hello,
i am customizing the lo cockpit for purchasing in the following datasources:
2lis_02_hdr
2lis_02_itm
2lis_02_scl
the problem lies when i am filling the set up table using oli3bw. i get the following message:
"DataSource 2LIS_02_HDR contains data still to be transferred"
this activity was performed 3 days back & that point of time i had given the next day as the termination date.
can anyone help me out on this issue?
any help would be greatly appreciated.

"DataSource 2LIS_02_HDR contains data still to be transferred"
this means that there is data in the update queue or delta queue for this extractor. if your in production follow the exact guidelines that you can find on this forum. you have to do this in the weekend. stop the v3 update job (run it one last time manually), extract your delta twice and transport the modifications.
if you don't care too much about your data cause you have to reinit anyway, just kill the delta queue

Set -up tables -delta queue

Similar Messages

Maybe you are looking for