Clearing Extraction and Delta Queues

Hi Guys,
I have a quite a problem. I am needed to clear Extraction and Delta Queues, but because there are users in the system they just keep repopulating once i have cleared them. Now these queues have to be cleared for a SAP Upgrade and the Upgrade wont continue until both are clear.
I was wondering is there a way to clear both queues with users in the system making changes?
A quick response would be greatly appreciated!
Thanks in Advance,
Nick

Hi,
There is on program"RMBWV*"
where * is equal to application.
It is used to move the entries from extraction queue to delta queue.
After everthing is there in the rsa7,then you need
to run the info package untill the entries become "zero" in rsa7.
May be try to run more than once.
Note:-You need to take business down time ie lock all the user
so that during that time no one update any data.
Hope this i shelpful.
Thanks,
Saveen Kumar

Similar Messages

Diff between update queue and delta queue

hi all
can anyone tell me wats is the diff between update queue and delta queue? wats is delta queue and update queue?
wats are the possible system generated errors and custom generated errors?
Thanks,
Shreya

Hi Shreya,
Update queue(LBWQ) comes into the picture when you choose Queued Delta for the Datasource. the data first comes to the Update queue and than goes to the Delta queue, however if you have choosen Direct Delta than the posted record will directly go to the Delta queue(RSA7).
Here is the URLS for Roberto's weblog to understand the whole LO-Extraction process.
/people/sap.user72/blog/2004/12/23/logistic-cockpit-delta-mechanism--episode-two-v3-update-when-some-problems-can-occur
/people/sap.user72/blog/2005/01/19/logistic-cockpit-delta-mechanism--episode-three-the-new-update-methods
/people/sap.user72/blog/2005/02/14/logistic-cockpit--when-you-need-more--first-option-enhance-it
/people/sap.user72/blog/2005/04/19/logistic-cockpit-a-new-deal-overshadowed-by-the-old-fashioned-lis
Hope it helps you!!!!
Regards,
Amit
Pls do not forget to assign points, if helpful.

Difference between Direct delta and delta Queue

Hi,
1.ease explain me the concept of Direct delta and delta queue in LO extraction
2.Why set up tables are used and initially why the data is deleted for th setup tables.
3.Please explain me the LO extraction with an example.
Thanks
Alok

Dear Aloka,
1.
Direct delta:
transactional data or application posting will be directly available in the delta queue table with out any intermediate tables. then that data will be extracted from r/3 to bw.
Each document posting is directly transferred into the BW delta queue
each document posting with delta extraction leads to exactly one LUW in the respective BW delta queues
Transaction postings lead to:
1. Records in transaction tables and in update tables
2. A periodically scheduled job transfers these postings into the BW delta queue
3. This BW Delta queue is read when a delta load is executed.
Pros:
Extraction is independent of V2 update
Less monitoring overhead of update data or extraction queue
Cons:
Not suitable for environments with high number of document changes
Setup and delta initialization have to be executed successfully before document postings are resumed
V1 is more heavily burdened
Queued delta:
first the data posting will available in the extraction queue table. then there periodic job run take that data to queued delta table.
Extraction data is collected for the affected application in an extraction queue
Collective run as usual for transferring data into the BW delta queue
Transaction postings lead to:
1. Records in transaction tables and in extraction queue
2. A periodically scheduled job transfers these postings into the BW delta queue
3. This BW Delta queue is read when a delta load is executed.
Pros:
Extraction is independent of V2 update
Suitable for environments with high number of document changes
Writing to extraction queue is within V1-update: this ensures correct serialization
Downtime is reduced to running the setup
Cons:
V1 is more heavily burdened compared to V3
Administrative overhead of extraction queue
2.
Setup tables are used for Full/Initial Update.
Instead of pulling data from DB Tables directly, we r filling Setup tables and extracting data from the Setup tables, which dont have performance impact on DB Tables.
Setup tables are application specific.
It is cautious method to delete Setup tables before filling it for a specific DataSource.
3.
Re: LO-Cockpit V1 and V2 update
http://www.sap-img.com/business/lo-cockpit-step-by-step.htm
Regards,
Ram.

Difference Between Update Queue and Delta Queue

Hi Experts ,
Could u brief out the difference between Extraction Queue , Update Queue and Delta Queue ?

Hi
a) Serialized V3 Update(If you set this as your delta mode then data will populated into extraction queue tables)
This is the conventional update method in which the document data is collected in the sequence of attachment and transferred to BW by batch job.The sequence of the transfer does not always match the sequence in which the data was created.
b) Queued Delta(If you set this as your delta mode then data will be populated into update queue tables)
In this mode, extraction data is collected from document postings in an extraction queue from which the data is transferred into the BW delta queue using a periodic collective run. The transfer sequence is the same as the sequence in which the data was created
Delta queue is a table which collects data from extraction queue/update queue tables based on the frequency you have set(daily/hourly etc)..from these tables we will get delta records to bw with infopackage delta run..
Hope it helps
Thanks
Teja

Regarding LIS Extract Structure and Delta Queues

Hi All,
We are extracting data using 2LIS_01_S001. But we are unable to pull Delta loads. When we verified we found that the structure (Fields)of the Delta queues are not in same order as S001 table. So, we modified the structures of delta queues using the access key. Now the order of fields in S001, S001BIW1 and S001BIW1 are all same. Till now I was unable to load the deltas for the data source. Now my doubt is should I have to do the LIS setups again (Statistical Information Setup)or can I do a Full Load and do deltas directly???

Hi,
You have to setup the tables once again.If your requirement is to load the customer data donot depend on LIS because there are lot of problems with this LIS.SAP is not recommending this LIS.Simply load customer attribute data and load transaction LOS also.
This is a better option.
Hope this helps.
Assign points if useful.
Regards,
venkat

How to delete the data in update queue and delta queue for Queued delta?

Dear BWers,
How do i delete the delta queue and update queue data before i fill the setup tables for a extraction based on Queued delta. Please help.
Thanks
Raj

Hi Raj,
I think you need some ground work for the LO extraction same as others here. Please read the 3 blogs expliciltly created for LIS by Robert Negro.
/people/sap.user72/blog/2004/12/16/logistic-cockpit-delta-mechanism--episode-one-v3-update-the-145serializer146
/people/sap.user72/blog/2004/12/23/logistic-cockpit-delta-mechanism--episode-two-v3-update-when-some-problems-can-occur
/people/sap.user72/blog/2005/01/19/logistic-cockpit-delta-mechanism--episode-three-the-new-update-methods
As well, the OSS 380078 would clear your doubts reagrding the the BW QUEUE mainatinance.
Please let me know if these material has been suffecient enough.
regarda,
raj

Wxtract and Delta Queues

Hi All
In order to patch our ECC system one of the pre requisites is to clear all the BW Extract & Delta Queues.
I am aware that Logistics uses these Queues and I can clear them from LBWE.
How can I tell if any other areas of ECC also use these queues.
Can you tell which modules do or can I looks for certain processes on ECC.
All help most appreciated
HKF.

Hi,
These data source use delta queue to send data to the BW and not the extraction queue.
There are two sets of data sources in BW ...for one which the delta is maintained through the extaction queue like LO data sources and another set like FI data source which use the delta queue directly and there delta is trigerred by scheduling an infopackage in BW...like FI-GL data sources
For FI data sources delta records will get fetch directly from the underlying tables when the infopackage is scheduled in BW and will delta queue to store the delta records for the repeat of the delta.
But in first case i.e. LO data sources the delta is generated by the R/3 system and is sent to the delta queue at regular interval by controlled jobs.
There are lot of links which tells you the difference between the FI and LO data sources and you can search for them...but they all contain the same thing which I have mentioned.
Thanks
Ajeet

ODS Delta Process, DataSource and Delta Queue

Hi to all,
loading data from a SAP source system into SAP BW 7.0 via generic 3.x datasource causes problems.
Here is a short description:
The data flow is from a source table using a generic extractor into a target ODS in full update mode.
Update rules should move data from table structure into ODS structure in this way:
Source table structure
CustKey1     Key2
13386          C23
13386          B14
13387          A13
13387          E25
ODS structure
CustKey1     col1     col2
13387          A13     E25
This works pretty well - as long as all records with the same CustKey1 are transfered in the same data package. Data Browser (SE16) shows the situation in ODS-"New data" view (data is not activated):
Request    Data_packet_number     Data_record_number      CustKey1
112           000003                  1.061              0000013386
112           000004                      1              0000013386
112           000004                      2              0000013387
There are two records for CustKey1 0000013386 with
data record 1.061 in data packet 000003   and
data record       1 in data packet 000004.
The obove constellation is the cause for errors in the ODS Delta Queue and subsequent data processing.
I think there may be one solution to solve the problem by changing the Delta Process of the Data Source.
The properties are:
- Record type: Full, delta, before, after images
- Delta type: Delta from delta queue or from extractor
- Serialization: No serialization, serialization of request, serialization of data packages
But how can I change these settings? Transactions RSA2 RSO2 RSO6 RSO8 don't do this.
What is the right delta process to use?
I have tried changing the delta process generating several 3.x datasources with the following delta processes (see table RODELTAM)
- " " (Full-upload)
- AIE
- ADD
Unfortunately with no effect.
Who can help?
Regards
Josef
Edited by: Josef L. on Mar 20, 2009 7:44 PM

hi venkat,
whenever you load a delta from ods to cube , whatever the data changed in ods since last delta will be updated, hence from you case, both req1 and req2 will be loaded to cube.
Assign Points if useful
Ramesh

What is differences extraction queue, delta queue and uddate queue ?

hi guru's
What is differences between extraction queue, delta queue and uddate queue ? can u describe briefly?
Thanks & Regards
nandi

Dear Prabha,
Basically when any document is posted in R/3, it is updated to the update table, from there it is taken to our delta queue for send it to BW side.
When extraction starts, data is sent to BW from delta queue. then again this cycle starts.
When you post any document in OLTP system (eg SAP R3),
say create sales order by VA01, then posting is made to application tables (VBAK/VBAP) through V1 and also to sm other tables through V2, Communication structure written to update queue/extraction queue/delta queue(directly) as per the update mode selected. V3 is always followed by V2 and we are supposed to schedule it.
From this delta queue, data is extracted by BW infopackages.
There are various update methods according to which extraction or delta queue are used, so when document posting takes place it also write data into extraction queue (through V1 update) and if we use queued delta method then this data is collected in collection run and written to delta queue and from this delta queue we request for data from BW.
There are lots of posts on SDN for this, please have a look on those.
one for your reference...
https://www.sdn.sap.com/irj/sdn/profile?userid=3507509
Hope it helps...
Message was edited by:
Ashish Tewari

View data in Delta Queue (RSA7)

Hi,
We want to see data records available for extraction in delta queue.
Data source is 0CO_OM_NWA_2. In RSA7 it is showing 5 in total column for this datasource. When we select "Diaplay Data Entries (F2) , select update mode Delta and execute it is displaying "List contains no data"
How to view this data ?
Regards
SS

Hi,
Once you schedule the infopackage , it will pick up the data from RSA7 . Afterwards when you check the data in RSA7 by selecting update mode as delta - you won't find any records . but you can see the data in by selecting update mode - delta repetition - execute it. It will show the records which has been already transferred to BW side.
Update mode - repetition , will hold the data until the next delta is successful..
Hope i am clear..
Regards,
Siva.

How to deal with delta queue when importing Support Package/Kernel Patch

Hi,
From my experience, when importing a Support Package for an installation, the system will issue an error message and get stuck if this Support Package is about to alter the structures used in delta loads.
But I would like to double with you if there is possible that the support packet which is going to alter structure, but no error message. If so, the delta data will be lost.
Do we need to clear down the delta queue every time we import support package?
Anyway, is there anyone have any suggestions or steps regarding this question?
Many Thanks
Jonathan

Hi,
Delta queues during support package upgrade
Its always better to drain the delta queues before an upgrade.
As a standard practice we drain the delta queues by running the IP/ chain multiple times.
As a prerequiste we cancel/reschedule the V3 jobs to a future date during this activity.
The V3 extraction delta queues must be emptied prior to the upgrade to avoid any possible data loss.
V3 collector jobs should be suspended for the duration of the upgrade.
They can be rescheduled after re-activation of the source systems upon completion of the upgrade.
See SAP Notes 506694 and 658992 for more details.
Page 17
Load and Empty all Data mart Delta Queues in SAP BW. (e.g. for all export DataSources)
The SAP BW Service SAPI, which is used for internal and BW to BW data mart extraction, is
upgraded during the SAP BW upgrade. Therefore, the delta queues must be emptied prior to the
upgrade to avoid any possibility of data loss.
upgrade preparation and postupgrade checklist
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/472443f2-0c01-0010-20ab-fbd380d45881
/message/3221895#3221895
OSS notes 328181 and 762951 as a prerequisites.
Failure to follow the instructions in those notes may probably result in data loss.
https://websmp207.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700002662832005E
/thread/804820
Effect on BW of R/3 Upgrade
How To Tackle Upgrades to SAP ERP 6.0
/people/community.user/blog/2008/03/20/how-to-tackle-upgrades-to-sap-erp-60
Start with the Why Not the How When You Upgrade to SAP ERP 6.0
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/008dddd1-8775-2a10-ce97-f90b2ded0280
Rapid SAP NetWeaver 7.0 BI Technical Upgrade
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e0c9c8be-346f-2a10-2081-cd99177c1fb9
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c2b3a272-0b01-0010-b484-8fc7c068975e
Hope this helps.
Thanks,
JituK

Setup table and delta mechanisim

Hi,
Can anyone explain in detail setup table concept in LO extraction and
Delta mechanisim?
Sridhar

Hi
LO Cockpit Step By Step
Here is LO Cockpit Step By Step
LO EXTRACTION
- Go to Transaction LBWE (LO Customizing Cockpit)
1). Select Logistics Application
       SD Sales BW
            Extract Structures
2). Select the desired Extract Structure and deactivate it first.
3). Give the Transport Request number and continue
4). Click on `Maintenance' to maintain such Extract Structure
       Select the fields of your choice and continue
             Maintain DataSource if needed
5). Activate the extract structure
6). Give the Transport Request number and continue
- Next step is to Delete the setup tables
7). Go to T-Code SBIW
8). Select Business Information Warehouse
i. Setting for Application-Specific Datasources
ii. Logistics
iii. Managing Extract Structures
iv. Initialization
v. Delete the content of Setup tables (T-Code LBWG)
vi. Select the application (01 u2013 Sales & Distribution) and Execute
- Now, Fill the Setup tables
9). Select Business Information Warehouse
i. Setting for Application-Specific Datasources
ii. Logistics
iii. Managing Extract Structures
iv. Initialization
v. Filling the Setup tables
vi. Application-Specific Setup of statistical data
vii. SD Sales Orders u2013 Perform Setup (T-Code OLI7BW)
        Specify a Run Name and time and Date (put future date)
             Execute
- Check the data in Setup tables at RSA3
- Replicate the DataSource
Use of setup tables:
You should fill the setup table in the R/3 system and extract the data to BW - the setup tables is in SBIW - after that you can do delta extractions by initialize the extractor.
Full loads are always taken from the setup tables
1. Data Flow
Relevant T-Codes
a) Initializtion
LBWE: Maintain Extract Structure, DataSource, Active Status, Job Control, Update Mode
SBIW, then follow tree menu path: Settings for App-Specific DS(PI) -> Logistics -> Managing Extract Structures -> Initialization -> App-Specific Setup of Statistical Data -> Choose XX Application -> Delete/Fill Setup(reconstructing) Table content
RSA3: Check content of setup table
b) Delta upload
SM13: Display update table/Extraction Queue content
RSA7: Display Delta Queue content
Edited by: Tapashi Saha on Jul 24, 2008 7:33 AM

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

DUMMY_BW (0FI_GL_04) delta queue not getting cleared

Hi,
We're using minute based extraction approach for 0FI_GL_04 and thereby have two delta queues for the 0FI_GL_4 extractor in the SAP ERP ECC system: One for the ‘DUMMY_BW’ and the other for the 'real' BI system. The delta queue for DUMMY_BW is not getting cleared automatically in production system and it keeps on adding more records in the queue which is in turn consuming memory in ARFCSDATA. Any thoughts on this would be really helpful.
Regards,
Karthik

Hi Gurus,
Please help me on how can I check that on what fields 0FI_GL_20 is pulling delta.
I tried to find the MSG Type to check in BD52 for relevant field list, in ROOSGEN table. the entry for MSG type is blank there.
Any help on this is appreciated.
Thanks,
Sourabh Deo

Enhance extract structure and deltas

Hi All,
We are modifying our first extract structure (well looks like it). We need to determine a key figure based on lookups and values of other fields.
Should we enhance the extract structure to pass these fields and then determine the key figure in the update rules to the cube or should we determine the key figure on the SAP side and pass to BW? If we determine the key figure on the SAP side does it update the delta queue with this value?
So does the delta queue get updated with this key figure? Meaning, does the code in the extract structure get executed during the update to the delta queue or do we have to pass the "lookup" values (basically characteristics) to BW and then determine the value of the key figure?
Thanks so much!

Hi,
This can be done at either of the places. This is all dependant on where can we afford to.. in terms of system uitlization. That is, if the look up table is too big in SAP and we have a small volume in BW then its better in BW and the viceversa of it.
Either in BW or in SAP, the logic is going to take some time to execute and hence the decision relies mostly on this.
Yes the delta queue would be filled with this logic, if we add the key figure in SAP.
Hope I am clear.
Naveen.A

Clearing Extraction and Delta Queues

Similar Messages

Maybe you are looking for