Delta Queue SM13

Hi Frnds,
I am need of changing some standard functionality but no idea where & how ?
here i am explaining the functionality . kindly provide your suggestions
Whenever billing document created ( header , item & condition data ) & saved then respective entry will move to Delta queue sm13 & respective data base table.
how this saving will be done in SM13 & database table ? is there any program to save in Sm13 ?
i am in need of changing standard extraction to BW .
kindly provide inputs on this
Regards
ravi

Hello Ravi,
After any changes in postings, the records are sent to SMQ1 and database tables for all applications. The same program take care of this for all applications like 02, 03, 11, 12, 13 ..... Please dont change this perticular program as it might affect all the applications.
If you need to make some changes in extraction, please use CMOD (Custom modifictaion of BI datasources is done here). Also you could activate the TMCEXLOG log in your transaction system and check its output using ABAP program RMCEXLOG. It will give you a idea of how the postings happen and how you could change CMOD to meet your requirement.
Please let me know if you need any more information.
Regards,
Pankaj

Similar Messages

R/3 Patch Upgrde Problem due BW Delta Queue.

Hi Expert,
I have extracted all the logistic & delta data in BW to make delta queue emplty. My query is that ,should it delete these queue in RSA7 or it should disappear after extraction.
In LBWQ there are only two entry MCEX17 & MCEX17_1 , these queue are still there after extraction.what to do these queue ?
These queues are giving error while upgrading patch.
2LIS_13_VDITM
2LIS_13_VDHDR
2LIS_11_VDITM
2LIS_11_VDHDR
2LIS_17_IONOTIF
Regards,
Anand Mehrotra.

Hello Anand ,
There is no need to delete the queues for the upgrade, you only need to make sure that there is no data in these queues in rsa7 that need to be extracted, if you run the relevant infopackage twice on the BW side then it should clear the data from RSA7 , before doing this please make sure that all data has been updated from lbwq to rsa7 (if using queued delta) and that there is no data in sm13 for the queues. In RSA7 you can double click on the Individual queues and if you check under delta and delta repeat option for these logistics queues you should find 0 records.
Best Regards,
Des

How Delta Queue fetches data in source system.

Hello Experts,
SMQ1 is physical storage of all transactions created in the source system. Delta Queue(RSA7) fetches data from SMQ1. In case of Queued and Unserilized V3 delta where LBWQ and SM13 come into picture. Can you please clarify my doubt.
Thanks in advance.
Zakir.

solved question

Delta Queue no data

Hi guys,
i'm extracting from vahdr and though i can see commit column
numbers increase for direct delta there is no delta data to be displayed and no records extracted to BW, it was the same for unserialized v3 too.
The v1 and V2's were successfully executed in sm13
Thanks,
your help will be greatly appreciated

The question was already raised in your previous thread.
No data in Delta queue
Please dont open new threads for same questions.
Regards,
Jagpreet.
null

R/3 Delta queues in support package upgrade

Hi gurus,
Our team needs to apply a support package upgrade to our BI 7.0 (without an upgrade in R/3 source system).
Do I need to worry about SM13 and RSA7 in my source system R/3 or just my data marts inside 7.0?
Or do I need to empty R/3 delta queues before BI upgrade to prevent data loss?
Best regards,
Enric

You may wish to take a look at below for few insights -
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
https://forums.sdn.sap.com/click.jspa?searchID=10299818&messageID=3221895
Hope it Helps
Chetan
@CP..

Difference between delta queue and unserialized v3 update - lo cockpit

Hi guys,
What is the difference between delta queue and unserialized v3 update.
How does sm13 come into picture. During system outages, how is setup table affected.
Edited by: zsl05 on Apr 22, 2009 11:29 PM

Hi,
In BW there are basically 3 types of delta queue mechanisms
1) Direct Delta: In this, as soon as the data is posted in the application tables, it is transfered to the RSA7 delta queue.
2) Queued delta: In this, as soon as the data is posted, it is first transferred to the Extractor Queue(LBWQ) and then via V3 Collective job to the delta queue periodically. The transfer sequence is the same as the sequence in which the data was created
3) Unserialized V3 : In this,when data is posted to the application table, it is posted into the Update queue first(SM13). It is then transferred to the Extractor queue (LBWQ) and then via V3 jobs to the Delta queue (RSA7). The difference lies in the fact that the sequence in which data was posted in the application table does not matter.
Hope this helps.
Regards.

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.

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

Load data in R/3 BW delta Queue

Hi,
Is there any option to load data in R/3 BW delta Queue. I have done nothing for that. I have found that new record is available in source table. Is there any option to schedule / execute in R/3 end.
Thanks & regards,
Goutam

Hi Goutam,
What do you mean ...Is it R3 Delta Queue or BW delta Queue???
As far as I consider it is R3 Delta Queue....For loading the data to R3 delta queue...1st let me know which update method you are using...
If its Direct update....document posting will be directly written to Delta Queue---RSA7.
If its V3 unserialised...then the changed document posting wil be captured and will be avaialble in Extraction Queue LBWQ and from there a collective run i.e. control jobs need to be scheduled as per your desired frequency to move it from LBWQ to Delta Queue RSA7.
If it is queued delta
u2022 Extraction data is collected for the affected application in an extraction queue
u2022 Collective run as usual for transferring data into the BW delta queue
Hope it is clear...
Let me know in case you need further details...
Thanks,
Amit Kr.

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.

Delta Queue in BI System

Hello friends
I just wanted to know whether there is any delta queue maintained in the BI source system apart from the R/3 system?
If yes how does it function?
Secondly, what is the max no of char in the Key fields in DSO(BI 7.0) that we can have?
regards
Rohit

hi rohit,
this is what i read in help check it out,
You can create a maximum of 16 key fields (if you have more key fields, you can combine fields using a routine for a key field (concatenate)).
-         You can create a maximum of 749 fields
-         You can use 1962 bytes (minus 44 bytes for the change log)
-         You cannot include key figures as key fields
if helpfull give me points
regards
harikrishna.N

How to load XML File to BW Delta Queue via Webpage

Hello altogether,
I am trying to load an CSV file via Webpage (the Webpage have to change the csv file in a xml/soap file) into BW Delta Queue.
Steps that I have made:
- Create an InfoSource
- Create an BW Data Source with Soap Connection
- Create an initial Delta without Data Transfer
- Create a Web Service with TC - SE37 - Utilities -> More Utilities -> Create Web Service
If I test the Web Service with TC - Soamanager (BW 7.0), the data entered here, are transferred to the BW Delta Queue.
If I test the function module ( TC - SE37), the data also transferred to the Delta Queue.
Now I think, that I have an error in the html file or the html file is not conform to the wsdl document?? Or should I have to create a virtual interface, but I don't find a possibility to creat it...???
Can you please help me????
The coding of the WSDL Document and the Website is attached (I can also send you the coding and error message via mail, if you want). Sorry I don't know how to display here the coding. I try it with symbol "click to display the text code", but afterwards I get an error message from the website... So let me please know your mail address and I send it via mail....
I hope, that somebody can help me!!!!!
Edited by: Alina99 on Sep 8, 2009 11:44 AM
Error Message from BW:
...sap-env:envelope..... soap-env:body><soap-env:fault><faultcode>soap-env:Client</faultcode></faultstring xml:lang="eng">Virtual Interface Method>_-BI0_-QI6AZ_XML_APPL2_RFC::urn:sap-com:document:sap:soap:functions:mc-style<not supported</faultstring>.......
Edited by: Alina99 on Sep 8, 2009 11:56 AM

Hello,
I have done all the necessary config in BW. However, as I mentioned earlier, we are still not up with XI so I am trying to load XML to BW delta queue. The question still remains, how do I make make the XML file (on my desktop say) point to the BW so the InfoPackage picks up and places in the delta queue? Even if I had XI, there has to be a way whereby BW looks for the XML file. That is what I want to know and stuck at.
Any detailed step by step help will be appreciated as always.
Cheers

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

How to delete the delta queue in the ECC

Hi everyone!
After I tryed to save a new Infopackage and I have the error :
(Deltas already loaded for request REQU_41Q82WJLR9AZCE9ZMKQLVG3RG init. selection; no 2. init
Message no. RSM1071
Diagnosis
Deltas have already been loaded for the init. selection of request REQU_41Q82WJLR9AZCE9ZMKQLVG3RG. A second initialization is therefore not possible with these selection conditions.
Procedure
If you want to carry out a new initialization, you have to choose selections that do not overlap.
If you want to repeat the init. for the same selection, you have to delete the delta queue in the source system, and restart the delta process.
As the error says - Deltas have already been loaded for the init. selection.
Can you please give me some links/guids which describes how to delete the delta queue in the source system, and restart the delta process.
thank you, Ron

Hi,
Assuming as you need to the reinit for same selections.
in such case you need to delete old init.
how to delete init:
Go to your info pack screen, menu Scheduler--> initialization options for source system--> here you can see the existing init, select init(green) and delete it.
Later you can trigger your init info pack with selections.
Thanks

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

Delta Queue SM13

Similar Messages

Maybe you are looking for