Write Delta-Queue RSC1_TRFC_QUEUE_WRITE

Hello
I have a problem with writing to the trfc-queue.
I have a datasource with Deltatype AIM and I trie to fill
the Queue with al little report which calls the FM RSC1_TRFC_QUEUE_WRITE.
The report works whitout any errors and the sy-subrc is 0 but I cant find anything in the Delta-Queue when I look into the Tr. RSA7.
Can anyone help me please?
Here is the report:
REPORT zv_v4_test_qrfc.
DATA l_v_isource LIKE rssis-isource.
DATA l_t_zcf591 LIKE zcf591 OCCURS 0.
DATA l_v_flush TYPE c.
DATA l_t_arfc LIKE arfccallid OCCURS 0.
l_v_isource = 'ZV_V4_C01_DS_TEMPLATE'.
SELECT * FROM zcf591 INTO TABLE l_t_zcf591.
CALL FUNCTION 'RSC1_TRFC_QUEUE_WRITE'
EXPORTING
    i_isource = l_v_isource
    i_no_flush = l_v_flush
TABLES
    i_t_data   = l_t_zcf591
EXCEPTIONS
    OTHERS     = 1.
WRITE: 'SY-SUBRC=', sy-subrc.
MFG
Michael Ruschmann

Hi,
did you replicate your DataSource from BW and did you send a delta init request?
If the Delta Queue does not expect data for a DataSource it will be just thrown away. So before sending data to the Delta Queue make sure, that there is an entry for your DataSource, when starting RSA7.
Hope that helps,
Bernd Sieger

Similar Messages

Writing to FI-GL records to Delta Queue using a Function Module

Has anyone of you tried to write FI-GL transactions to delta queue using BTE by configuring a function module. I am trying to achieve it for a datasource based on a view on FAGLFLEXA table (GL Line Items). For some reason I am not able to see records in Delta Queue. I am doing this to achieve RDA functionality. If you have done it please sends me step sequence and the name of FM.
Your help would be highly appreciable.
Regards,
Ram

Hello Ram,
See this SAP Network Blog: [Generic Extraction via Function Module|/people/siegfried.szameitat/blog/2005/09/29/generic-extraction-via-function-module]
Have a look at these docs,
[How to Create Generic Data Sources which use the Delta Queue (NW7.0)|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/10b68b99-022e-2a10-999d-c4dc9ec24a59]
[How to Create Generic DataSources Which Use the Delta Queue (NW2004)|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d3219af2-0c01-0010-71ac-dbb4356cf4bf]
[How to Create Generic Delta|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33]
Thanks
Chandran

At what point is delta queue updated?

Hi everbody,
I want to know at what point delta queue is updated? Is it updated after a successful init load in BW or is it updated when the set up tables are filled? If i delete the delta queue do i need to run init load again?
Thanks
Raj

The delta queue is a data store in the source system into which data records are automatically written using an update process in the source system (such as with FI documents) or using extraction using a function module after a data request from the BW
Please cgeck this for more details
Checking the Delta Queue
http://help.sap.com/saphelp_nw04/helpdata/en/6f/66bca6ae43744283d74f1e456ff6c0/content.htm
Update Process
http://help.sap.com/saphelp_nw04/helpdata/en/84/81eb588fc211d4b2c90050da4c74dc/frameset.htm
2 Deleting data from the delta queue does not require the delta method to be reinitialized to write DataSource data records into the delta queue.
Note that data that has yet to be read from the delta queue is also deleted. As a result, any existing delta update is invalidated. So, only use this function when you know what you are doing!
Hope this helps
Thnaks
sat
Message was edited by: Sat

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

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

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

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 ALTI

Laurent,
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

Write Delta-Queue RSC1_TRFC_QUEUE_WRITE

Similar Messages

Maybe you are looking for