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

Similar Messages

Data transfer (Export & Import) of Delta Queue between two system.

We are planning to implement the following senario for a certain R/3 and BW system.
1. Implement storage snap shot copy solution for R/3 database and create replicated system of production R/3 every day in order to avoid load of production R/3 to BW directly. That is to say, we will extract business data from the replicated R/3 system and forward to BW.
2. We need to utilize Delta Queue function in order to feed the only gap data between production R/3 and BW. but as stated in 1. the source data will be replicated from the production R/3 every day and so we could not keep the Delta Queue data in R/3.
3. So, we are examining the following method in order to keep the Delta Data in the replicated R/3 system. i,e after feeding business data from the replicated R/3 to BW, we will extract the following Delta Queue table and keep it.
- TRFCQOUT (Client Dependent pointer table per queue name and destination.
- ARFCSSTATE: Likn between TRFCQOUT and ARFCSDARA
- ARFCSDATA: Compressed data for tRFC/qRFC
And then, next day, after replicating R/3 system, we will import those Delta data to the replicated R/3 system before stating extract business data and feed to BW.
Is the such method realistic? if not, is there any alternative?
Please advice!
Best regards,

I found the following document and this is one that I want to inplement.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5d51aa90-0201-0010-749e-d6b993c7a0d6
Additionaly, I want to execute this senario repeatedly. Does someone have experience such implementation?
Eguchi.

Logical System name in RSA7 Delta Queue wrong because of BW System Change

Hello All,
we changed our BW System landscape. Before we had one BW development system (System ID: DBW) and now we are using BW development system (System ID: EBW).
Now we face the problem, that in our R/3 system in the delta queue the wrong / old development system is written (DBWCLNT100), but instead of this there should be EBWCLNT200.
Has anyone of you got a clue where we can change this?
BR
Ilona

Hi,
hope you can do the client copy function to transfer the things from one client to other client no.
before doing the operation. please read the oss note carefully
Please refer to Note 552711 - FAQ: Client copy - subsequently See Note 557132 for further information.
and also check these threads
Remote Client copy error
how to do remote client copy ?
Regards
Harikrishna N

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

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

Delta Queue (Source System or BW)

Hello all,
Is the delta Queue present in the source system or BW or Both?
Thanks
SD

Hey!
R/3 delta records are gathered in R/3 in a queue for BW extraction purpose. So this queue is in R/3.
When a delta run is scheduled from BW, using the delta infopackage, then records from this queue in R/3 is extracted.
Trust this answers your question.
Prakash

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

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.

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

Effect of SAP R/3 upgrade on Delta Queue

Hi Gurus,
We have our SAP upgrade scheduled to go-live in some time. My problem is that we have 2 loads based on Direct Delta queue concept.
As per my understanding, the approach that we need to follow is that we should get all the users locked and then load the data into BW system from delta queue. Once this is done and the delta queue is cleared, we can bring the R/3 system down for upgrade.
The approach adopted for Upgrade is Downtime minimised, wherein for most part of upgrade, system will be down and for some part of upgrade the production will be up and running. In such a scenario where system will be up and upgrade will be running simultaneously, will there be any impact on the delta queues or rather shall I say that 'Will the delta queues affect upgrade process'

Hey. In my experience, you never want the system to be "up" during an upgrade. You will, or have, probably run accross the problem in dev or QC with doing the upgrade while the delta queues are populated. You will often get an error message that queues still have data to be transfered.
So I guess the simplest answer is that you do run the risk of having problems with the upgrade. If thre is no choice but to do the upgrade partially doing productive hours, I would just clear all the queues and hope for the best. Not a great answer, but not sure what the best answer would be in your scenario.
Thanks

BW Upgrade - Down time - Delta queue

Hello Experts,
We are in the process of upgrading the BW system from 3.1 to BI7 but not the R3.
Do we need to drain the delta queue from R3 before the upgrade or we can only go ahead about the BW Delta queue only?
As per the note: 506694, its talks about the BW alone when we are performing the BW upgrade but not R3.
Also let me know whether we need to take R3 down time when we do the BW upgrade alone?
Thanks
Raman

Dear Kedar,
Can we perform the left out steps directly in production? As per my understanding there wont be any issues if we perform the left over steps in production.as this will checks for the consistency check alone.
Interestingly I tried checkcing this program(RSUPGRCHECK).. for the infoobjects in my dev system. its trying to activate some of the infoobjects as well.
It showed a message like this: Activate all Dictionary objects ( 1422 )
I tried checking the number of objects in the system using RSDIOBJ.. where I can see that there are 2600 objects are in A version.!!
Does this message tells that this program has activated this many number of the infoobjects out of 2600? I tried this after the upgrade in the D.
Can you please clarify me on this.?
Final Question: How much period that we need to maintain the Down time in R3. Is it till the Upgrade starting from the PREPARE and till the end of the Post Upgrade activities and the Unicode? I will close this thread after this.
Many thanks again..
Raman
Edited by: Raman R on Aug 28, 2008 3:16 PM

Delta queue & XML data source

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.
Kittu

Hi 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.

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

Problem with initialization Delta queue

Hi Gurus,
I have problem with initialization of delta queue when I try load transaction data from R3 (FM) to BI.
Error message: Deviation of (64 seconds) between qRFC counter (000012365466830000080000) and actual time (08.03.2009 21:10:19).
I have no idea where is the problem because this problem occurs only in PRD systems. In DEV and QUA system everything is OK.
System BI: BI 7.0
Source system: ECC 6.0
Thank you for all answers!
mp

Hi,
Replicate the DS in BW Prod and then Activate Transfer rules and then try.
First you delete the DElta quae in RSA7 for the particular datasource in the R/3
source system then you try to intialize, here you are trying to intialize datasource with
same selection conditons . thats why it is giving shortdump
Check
Business Content and Extractors
Thanks
Reddy

Delta Queue in BI System

Similar Messages

Maybe you are looking for