Extraction Queue - SMQ1 - entries..

HI All,
We are running some data loads from source SRM to BI .
We have a Strange Issue:
Without triggering process chains or Infopack groups in BI side, Extraction queues (SMQ1 TRFCs ) are filled automatically with some entries. It will causes the SRM loads in a very slow manner.
Question is :
Why Extraction queues are filled in source sys - SRM without running Infopack /Process chain?
Is there any Background program running in SRM side?
What is the data flow behaviour in BI?
How to resolve this Issue?.
And mainly please let me know the reason? This is an urgent issue.
Thanks in advance.
Cheers.
Sri

Hi,
can you check to which extractor the queue belongs and if somebody has performed a delta init for it.
As soon as you have a delta init, but do not fetch the delta, the queue will start growing. You either have to delete the delta init or schedule the delta load.
Best regards,
Ralf

Similar Messages

ERROR : Entries for application 13 still exist in the extraction queue -

Hi everybody,
While modifying extractor (LO Cokpit) I am getting this error.. I have deleted data through t.code LBWQ & LBWG still I am getting this ERROR,
" Entries for application 13 still exist in the extraction queue -> "
and it is givig the Diagnosis as below
Diagnosis
You are not allowed to change the extract structure MC13VD0ITM forapplication 13. This is because unprocessed entries are still presentin an extraction queue of application 13 for at least one client.
If an extraction structure is changed for which there are still openentries in an extraction queue, these entries can no longer be read andthe collective update terminates.
Please help me out..it is urgent...
Thanks in advance

Hi Sunita,
Do one things, to fix this problem, go to the BW for that info package, it seems
its already exists..if yes..delete the initialization request from the package
and come back to R/3 try to delete the application 13 and it will allow to make
the changes to the struc.
Hope it helps..
Need further help revert..
Assign points if useful..
Cheers,
Pattan.

Urgent Entries for application 11 still exist in the extraction queue

Hi All,
In LBWE when i am trying to mainting structure its not allowing to add fields to ExtractStrucutre.
Following is the error iam getting.
Entries for application 11 still exist in the extraction queue ->
I have set the Update to inactive and trying to add fields to Extract strucutre .
Morover,
I have already deleted setuptable entries for this application Component 11 and i checked in rsa3, no records are there.
Regards,
C.V.
Message was edited by: P.C.V.

PCV,
Here are the steps. Make sure you do them when there is no posting going on.
1) Using transaction SA38, execute program RMBWV311. This will send the data from the extraction queue to delta queue for application 11.
2) Run your 2lis_11_***** info packages to bring the delta records into BW. Make sure to run these info packages twice because the delta is cleared on R/3 only if you run them twice. It is designed this way to accomodate the delta repetition functionality.
Just to make sure, verify that you don't see any data in RSA7, LBWQ and if you use RSA3, the system should not extract any data.
You should be able to change the extract structure now.
Abdul

SRM Extraction Queue is filled Unnecessary -- to BI load

HI
We are running some data loads from SRM to BI .
We have a Strange Issue:
Without triggering process chains or Infopack groups in BI side, Extraction queues (SMQ1 TRFCs ) are filled with some entries. It will causes the SRM loads in a very slow manner.
Question is :
Why Extraction queues are filled in source sys - SRM without running Infopack/Process chain?
Is there any Background program running in SRM side?
What is the data flow behaviour in BI?
How to resolve this Issue..
And Mainly please let me know the reason?
Thanks in advance..
Cheers.
Sri

Hi,
Check whether you are Using Queued Delta or not in LBWE, and if your code working fin meanes you can get the corretc dat ain Queued delta aslo.
See the below article about the RSA7, SMQ1 etc...
Checking the Data using Extractor Checker (RSA3) in ECC Delta Repeat Delta etc...
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/80f4c455-1dc2-2c10-f187-d264838f21b5&overridelayout=true
Data Flow from LBWQ/SMQ1 to RSA7 in ECC and Delta Extraction in BI
http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/business-intelligence/d-f/data%20flow%20from%20lbwq_smq1%20to%20rsa7%20in%20ecc%20and%20delta%20extraction%20in%20bi.pdf
https://wiki.sdn.sap.com/wiki/display/profile/Surendra+Reddy
Thanks
Reddy

MCEX12 Extraction Queue Status

Hi Experts
We are using MCEX12 Extraction Queue in our project
Many a times the status of this queue turns to WAITUPDATE
Thus the V# jobs do not extract data to delta Queue
Then i have to make the status to ready and run the v3 jobs manually
What could be the reason of the Status of the Queue changing to WAITUPDATE?
Regards
Akshay Chonkar

Hi
Check Note 869628 - Constant WAITUPDA in SMQ1 and performance optimization
and also 980221.
Hope it helps

Deleting extraction queue.

Hi,
we r upgrading our source system version from 4.6c to ECC6. before upgradaion taking place in production we have to update all the source system data to BW system. For that we have to update the data from extracting queueu to RSA7 .After updating have to delete the extraction queue.
My question is,
From where to delete the extraction queue ?
Is it from SMQ1? or LBWQ? i can see only one queue name in lbwq with MCEX11. where as i can see more than one queue name in smq1.
Wt is the differance b/w smq1 and smq2?

Hi
SMQ1 = RSA7 + LBWQ.
SMQ1 is outbound queue.
SMQ2 is inbound queue.
Regards
Sadeesh

Delete Outbound Queue : SMQ1

Dear Friends
I am upgrading my ECC6 PRD Server by EHP5.
My Check Roadmap step has been completed with warnings!
I Knew it to release and delete by the LBWE and LBWQ.
But my question is that i need to delete it now in CHECK and PREPROCESSING phase.
or
Delete it in the DOWNTIME phase ! becuase, the PRD system in integrated with BI PRD server and the data is collecting each hourly.
Please advise.
A2EEMCEX 151 Entries for application "11" still exist in the extraction queue ->
Long text:
    Cause
      Changing extraction structure &V#& for application &V#& is forbidden,
      because there are entries that have not yet been processed into an
      extraction queue for application &V#& for at least one client.
      If an extraction structure is changed to the entries that are still
      open in an extraction queue, then these are no longer able to be read
      and can cause terminations with the collective update.
    What to do
      Start the collective update using the function "Job Control" in the
      <DS:TRAN.LBWE>Logistics Extraction Structures Customizing Cockpit</>.
      To get an overview of the logistics extraction queues, see the
      <DS:TRAN.LBWQ>Logistics Queue Overview</>.

Dear Anwer,
As long as you are in prepare or uptime of the upgrade you can
ignore the errors in the RSVBCHCK which say that there exist
update records (as it is normal that there are update records
in a system which is productively used).
In the downtime there is also a check on update records. In the downtime
this check cannot be ignored.
You can also read note 328181.
Please also refer to the upgrade guide with this regard.
SAP Enhancement Package 4 for SAP ERP 6.0 ABAP:
page 105********************************************************
Outstanding or Incomplete Updates (Phase JOB_RSVBCHCK2)
If there are any outstanding or incomplete updates, the upgrade stops in
this phase with a message.
If errors occur in this phase and you have not stopped production
operation yet, you can skip these
errors with ignore without entering a password. However, we recommend
that you check for these updates and clean them up. The message is:
Update records still exist - Please process
page 103*******************************************************
Update records still exist - please process
Make sure that you have cleaned up all outstanding updates.
Make sure that you have cleaned up all outbound queue RFC calls by the
JOB_RSVBCHCK_R or JOB_RSVBCHCK_D phase (during downtime) at the latest.
If you are still in the preparation phase (before the beginning of the
Preprocessing roadmap step) and therefore in production operation, you
must only delete the terminated updates.
Also during the production downtime for such issues you can check the
following information:
This error is caused because the updates have been deleted but
entries in tables related to the update process are not empty:
- tables VBDATA,VBMOD and VBHDR should all be empty
To avoid the error message , run report RSM13002 with "delete" option
to delete update records as explained in attached note 67014. After
that you can repeat the phase, the incidence should have been solved.
-> 67014 - Reorganizing update requests
Information remains same for EHP5 as well.
Regards,
Abhishek

2LIS_04_P_ARBPL Delta not captured from extraction queue

I am using datasource 2LIS_04_P_ARBPL to load 0PP_C03 cube. I have setup init selections as follows
0PRODORDER     AUFNR     Order Number     6000000000     6999999999
0COORD_TYPE     AUART     Order Type     ZCP1
0PLANT     WERKS     Plant     1010
In short I have the selections for entire range of production orders for a given plant and order type.
I have populated setup tables, did init load with data transfer, activated the update in LBWE, scheduled V3 job, no issues here.
When we create new production orders they are available in extraction queue MCEX04, when V3 job runs it makes it to delta queue, available in RSA7, loads into BW when delta load is done.
Ths issue is when we TECO a production order (status marked complete) to same production order which we just loaded as delta, it does makes it to extraction queue MCEX04, but when V3 job runs it is not available in delta queue, RSA7. May I please know if this is standard behavior of this extractor or I am missing something? Why the same production order is now getting filtered by V3 job?
Any help will be appreciated.

Hello
I am also facing same issue.
but in my case, I not mapped 0recordedmode with rocancel in transformation.
My scenario : DS(2LIS_04_P_ARBPL) ---->DSO(Stranded DSO) ---> Info Cube. DSO and Cube is Z object.
In cube I am having 2 records: 1 is Correct and 2nd is bad(Minus or 0 values) record.
That bad records fetch in report with Minus or 0 values not correct one.
Please let me know if have any concern on this.
Thanks is advance.

CCMS monitoring for Queues(SMQ1/SMQ2)

Hi,
How do we monitor Queues(SMQ1/SMQ2) in CCMS. My requirement is to monitor Queues(SMQ1/SMQ2) in CCMS based on the Queue name. I want to create different nodes in CCMS and I want queue name falling under certain criteria should come and sit in the respective node of CCMS.
Means queue with name High_priority should come n sit under node say Test1, queue name with medium_priority should come n sit under node say Test2 and queue name with medium_priority should come n sit under node say Test3.
Is it possible to do so.

Hello,
also for queue monitoring the easier and more flexible way to monitor is via Business Process Monitoring. The configuration is easier than CCMS where you have to use transaction RZ21 and need to transport objects. And the qRFC monitoring is more flexible than in the CCMS. Basically all customers knowing both standard CCMS qRFC monitoring and qRFC monitoring in BPMon chose the later or exchange their existing CCMS monitoring by BPMon.
See also the SDN blog /people/johannes.fleig/blog/2008/06/11/new-business-process-monitoring-functionalities-in-sap-solution-manager-150-qrfc-monitoring
and check out the Interface Monitoring Setup Guide under http://service.sap.com/bpm > Media Library > Technical Information.
Best Regards
Volker
Edited by: Volker von Gloeden on Jul 2, 2010 4:48 PM

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

How to empty extraction queue (LBWQ)

Dear BWers,
How do we empty the extraction queue LBWQ?
Thanks
Raj

Hi,
For emptying the data from the extraction queue, run the collector pgms. They start with R...Then pull that data through delta infopackages so that the delta queue is also empty. But one thing is make sure there are no more transactions posted on the source system during this activity otherwise you'll get data in your extractor queue again.
Cheers,
Kedar

DELTA QUEUE&EXTRACTION QUEUE

hi all,
1.what is differnce b/ween delta queue &extraction queue
2.wt's delta modes adavatages & disadvantages? where we usd these delta modes?

Hi there, I am fine thank you.
[you can call(write) me by my name i.e. Ashish.]
I am sending you all links:
1. SAP Network Blog: LOGISTIC COCKPIT DELTA MECHANISM - Episode one: V3 Update, the serializer
<b>/people/sap.user72/blog/2004/12/16/logistic-cockpit-delta-mechanism--episode-one-v3-update-the-145serializer146
2. SAP Network Blog: LOGISTIC COCKPIT DELTA MECHANISM - Episode two: V3 Update, when some problems can occur...
<b>/people/sap.user72/blog/2004/12/23/logistic-cockpit-delta-mechanism--episode-two-v3-update-when-some-problems-can-occur
3. SAP Network Blog: LOGISTIC COCKPIT DELTA MECHANISM - Episode three: the new update methods
/people/sap.user72/blog/2005/01/19/logistic-cockpit-delta-mechanism--episode-three-the-new-update-methods
<a href="/people/sap.user72/blog/2005/01/19/logistic-cockpit-delta-mechanism--episode-three-the-new-update-methods Network Blog: LOGISTIC COCKPIT DELTA MECHANISM - Episode three: the new update methods</a>
Incase you are not able to find them this time also, you can do one thing, put "Roberto Negro" in search at sdn.sap.com, you surely get his weblogs on first page only. Then take all three episodes of LOGISTIC COCKPIT DELTA MECHANISM.
Regards,
Ashish

Scheduling extraction queue deletion

I need to delete the extraction queue's content, before filling the setup table.
While I can schedule the setup job, I can't schedule a job for deleting the queue. I'd like to schedule both the deletion of an extraction queue and the setup job. The start condition for the setup job would be the end of the deletion job.
I'm annoyed at waiting midnight just for deleting the extraction queue with LBWQ...
But what's the name of the report for deleting a particular extraction queue (e.g. for application 13, invoicing)?
Cheers, Davide

I have at looked the source code of the RSTRFCM1 report, which is called when deleting a queue from LBWQ.
This fragment of code deletes a queue. It needs two input parameters: the queue's name and the destination.
REPORT zbw_extractqueue_delete .
PARAMETER: qname LIKE trfcqout-qname DEFAULT 'MCEX??',
           dest LIKE trfcqout-dest DEFAULT 'NONE'.
DATA sl_entry(96).
CONCATENATE sy-uname '&' qname ','
            dest INTO sl_entry.
CALL 'C_WRITE_SYSLOG_ENTRY' ID 'TYP' FIELD space
                            ID 'KEY' FIELD 'Q22'
                            ID 'DATA' FIELD sl_entry.
CALL FUNCTION 'TRFC_QOUT_DELETE_QUEUE'
     EXPORTING
          qname = qname
          dest = dest.
Cheers, Davide

Extraction Queue

Hi All,
Need a clarification about LO Extraction........
"if the update mode is queued delta..Then transactions will first go to Extraction
Queue and after the LBWE job runs they will be transfered from LBWQ to RSA7..."
Please correct me if my understanding is wrong.
Regards

You got it.

Extraction queue is getting larger

Hello BW Experts,
The extraction queue is getting large every day. What is the solution.
Regards,
BWer

Hi,
Could you tell me under what scenario you are facing this problem?
Check the job scheduling status. Increase the frequency and pull the data into delta queue.
With Regards

Extraction Queue - SMQ1 - entries..

Similar Messages

Maybe you are looking for