Info on Delta Queues
Hi,
We have recently activated PM, MM & QM related Business contents and started taking the data in BW. We have following questions / doubts on RSA7 screen.
1. After executing the delta job in R/3, we can see the records in RSA7. There is one column 'Total' against each datasource.
--->Our question is when this column gets updated. Because we are unable to find the count what it is showing.
2. After uploading the delta succesfully in BW, when we return back to RSA7 screen, delta queue becomes empty. i.e when we select a datasource and click on 'Display data entries' button, we gets a message 'List contains no data'.
---> Our assumption is that delta queue becomes empty immediately after loading the delta into BW. But whatif the delta fails at BW side by some reasons ?
Please give your valuable inputs.
Thanks
Ramesh Ganji
Hi,
1. this number is reflecting the number of LUWs (logical units of work) in your delta queue. if you go to SMQ1 you'll see for instance InboundQueue MCEX03 (MM) with a number. These are the numbers of LUW successfully (could be number of documents or not since a LUW may commit several docs) recorded for your datasource.
When the update is fired, the InBoundQueue is passed to the Delta queue enabling you to see it in RSA7, for instance BW<CLIENT>2LIS_03_BF/UM.
2. yes, when you load your delta in BW the delta queue is empty. However we shall be more precise: it is the NEXT delta which doesn't have any data. Indeed you are always able to REPEAT the last delta.
In RSA7, you'll still see a number of LUWs <> 0 because there is still data in the repeat which you can display in RSA7. If you fire a second delta form BW right after the previous and there has been no update in between you shall get 0 records and the number is 0 in RSA7.
A delta gets repeated when you set your delta request status to RED in the monitor in SAP BW. When you'll request the next delta, the system will prompt you if you want to repeat it. If you gave this situation while executing a process chain the system will do it in silent mode if the request is NOT posted in ANY target; if a target still has the request, it won't request it since the system needs clarification from the user.
This is the plugin mechanism used in order to ensure integrity and system communications and I have to admit that's quite clever and reliable...
hope this helps
Olivier
Similar Messages
-
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, RonHi,
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 -
Critical issue - delta queues for LIS empty after upgrade BW3.5
The delta queue in R/3 for LIS sources (S260-261-262) remains empty,
even after a successful init delta. Hence I cannot extract delta
records.
BW3.5
PI2004.1
Does the BW upgrade has an effet on the delta queue management in R/3 ?
The previous configuration BW2.0B PI2004.1 did work fine in that
respect.
Laurent Querella
BI Consultant ALTILaurent,
from OSS Note 534296 'LBW0: DataSource generation possible for SAP info str.' you can read:
"(...)it is no longer possible to generate DataSources for info structures (transfer) Snn delivered by SAP (where nnn is between 001 and 500) in the BW interface for LIS info structures (TR: LBW0) in the OLTP. (...)The corresponding DataSources are delivered with the Business Content."
I think this is the issue...
However, are you saying that all infostructures are empty ?
And from where your init is taking data ?
After an init your delta tables have to be empty...did you empty all these tables before doing your upgrade ?
Bye,
Roberto -
Hi All
Can any body pls tell mme as to what this delta que ais and where is it used and how is it created,and also i want to know what is this XML Data source.
I need to get the data from XI,so i need this integration.
I would be very thank ful if any body cuold suggest me with a link on the notes ar step by step formatt.
Point's will be awarded,Thanks in advance.
KittuHi Jay,
From Delta queue(RSA7) ur BW system is going to fetch the records of R3 or source system.
After extraction process it reaches RSA7 from there when u triggers infopackage
the job is ready to flood ur D.target with records.
Ensure that records are there for corresponding D.source this has to be attained thro' various Update methods(v3).
DataSource that is generated in SAP BW on the basis of a file-DataSource and
that can be used to push data to SAP BW
for more info on creation of XML D.source refer the link
http://help.sap.com/saphelp_nw04/helpdata/en/fe/65d03b3f34d172e10000000a11402f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/0b/3bc73b24062b48e10000000a11402f/frameset.htm
Reward if it's useful.
Thnks,
Karthick. -
Question about Note 886102 - Empty the delta queue of the connected SAP source systems
Dear expert
I'm doing the system refresh from ECC PRD to QAS using the hot backup of PRD
Before i start the database restore i was told to do the following step since this ECC has connection with one BW system
-----------------------Step -----------------------------
2.17 SAP note 886102 scenario C3
Empty the delta queue for all of the connected BW systems.
Execute all delta info packages two times on BW side, to clean up the delta queue in the source system. This is needed, because BDLS cannot rename the still available LUW-s in the qRFC queue.
----------------------Step-----------------------
But unfortunately i missed to execute this step
And the Q11 is now retoreing the backup of the database
My quesion
1. what will be bad consequence due to not execute this step? any way to makeup this error?
Best regards,Hi Kate,
The probably issue which I could forsee is data getting wrongly updated into production if RFC connection from ECC to BW is not stopped.
Solution here could be to disable or deletethe RFC connections between ECC and BW before starting the SAP system at database level.
delete from sapr3.rfcdes where rfcdest = '<name>';
Once the system is up and running you can recreate them if required.
Also before starting SAP set the number of batch processes to 0 on the profile at OS level so that any released jobs don't start as soon as SAP is up.
Once the SAP system is up execute BDLS and change the logical system name.
Hope this helps.
Regards,
Deepak Kori -
Hi,
I did setup all steps for 0PU_IS_PS_44 data extraction from R/3. In doing so I did Initialized Delta process, logged to R/3 RSA7 transaction code to check the queue. At the time of Init I got 300 records. Today I created new Info package to extract the Delta records.
Here my problem is I could not see any Delta extraction to BW. In R/3 I could not see any records in the queue but where as in the RSA3 (Extract checker) the number of records are 324 meaning (324-300) 24 records were created from I did the Init and expected that records to appear in Delta Queue and also while Delta extraction to BW.
Appreciate if one could help me any steps I am missing out or any suggestions to see additional records to extract via Delta.
Thanks in advance.
Best Regards,
Murphy.Hi Bhanu,
Thanks for your response at both places.
I got resolved the FM data source delta extraction. Adam responded to my post stating the IMG setting required for the activating Delta Queue.
I have the same issues with CO and FI data sources. Even the GL Account master data data source does not show the new/changed records/documents at Delta queue.
Appreciate if you could help me in resolving the problem.
Thanks.
Murphy. -
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,
NickHi,
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 -
STEP BY STEP INFO ABOUT DELTAS
hi,
this is ahmed i want info about deltas with t. codes
thanks in advance
my mail id <removed>
regards
ahmedAssuming you are talking about LO extraction:
Transaction postings lead to records in transaction tables
For an initial load a setup needs to be executed which reads the transaction data and stores the data in a setup table
These setup tables are read during an initial or full load
Further transactions are posted into the transaction tables and also caught into Update tables / Extraction Queue.
A periodically scheduled job transfers these postings into the BW delta queue(Data in the update tables is transferred
through a periodic update process to BW Delta queue)
This BW Delta queue is read when a delta load is executed.
First time initialize:
R/3 - Setup table (sbiw)
BW - Initial dataload (rsa1)
Schedule collective run (lbwe)
Re-initialize:
BW Delete initialization record (InfoPackage: rsa1)
R/3 Check delta queue (rsa7)
R/3 Process outstanding updates (sa38/se38 - RMBWV3XX)
R/3 Check delta queue (rsa7)
R/3 Setup table (delete and fill: sbiw)
BW Initial dataload (rsa1)
R/3 Schedule collective run (lbwe)
Setup and Initial load
Run test-setup without blocking to get indication of setup runtime
Split setup of historic data with 1 most current and change-able setup as small as possible
Split initial loads using disjunct selections
Delta load selections will contain union of all init selections
Once setups are done, system is free to post (when using Queued delta and V3), postings are collected in Update Tables /
Extraction queue while initials can be started.
Only after all initials have been successful, start the periodic job to transfer data to BW Delta queue
Schedule the delta load -
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
SSHi,
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 PMhi 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,
GoutamHi 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. -
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
Rohithi 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 AMHello,
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
RajHi 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
Maybe you are looking for
-
How can I take a picture of a camera output on the Front panel
Hi all, I've been fighting this one for a while, But I have a DataRay WinCamD CCD image in my front panel, I need a way of saving that image to a file. I've been crawling through NI Vision and IMAQ VIs and I can seem to piece the process together. Th
-
Ipod shuffle generation 2 not being recognized at all
I just bought a ipod shuffle generation 2, and i went ahead and installed itunes 7.02. I then connected the ipod, but windows did not ask me to install any new software. I then went to Device Manager and looked to see if the ipod was being recognized
-
Change documents in WTY after the Claim is "complete"
Dear All, In WTY transaction, I am unable to view the change documents (Extras --> Change Documents) after the Claim is flagged off as "Complete" Is there a way to overcome this ? Thanks. Raj
-
Help PPLZ How Do You Put The Picture Of the Album Your Listening to (Album Art) ?????
-
Updating a Book During the Review Process
Does anyone have any advice/experience with updating a book while it is still in the review process? I have a book currently being reviewed, but just realized that one of the images in there is reversed. I also heard from a source that needs to chang