Doubts in delta in source system

Hello All
Iam not clear in one of the delta process how it works in the source system
Suppose if an invoice or sales order has been created and on the same day this has been cancelled then how many records ( i mean the LUW's)will this maintains in the RSA7(delta Queue)
Q2
Suppose if an invoice or sales order has been created and on the same day this has been chnaged then how many records ( i mean the LUW's)will this maintains in the RSA7(delta Queue)
Please let me know
regards
Swami

Hi Allen
Thanks for your valuable info.,Yes the LUW will be one only.But am asking like in that LUW's how many records wil that maintain
Anyhow am giving one example can you please me with that,so that it will be clear to me,thanks a lot
Suppose for example a Sales order ( 12345678)is created with Net value as 1000 has been created in the source system . and now the sales order has been cancelled,now how many records it will be maintained in the RSA7 ?
In case of Cancel of the SO
Will this have in RSA7 as
12345678------->1000
or
12345678------->1000 and
12345678------->-1000
In case of changed of the SO
Suppose for example a Sales order ( 12345678)is created with Net value as 1000 has been created in the source system . and now the sales order has been changed the netvalue to 700 ,now how many records it will be maintained in the RSA7 ?
Will this have in RSA7 as
12345678------->1000
or
12345678------->1000 ,
12345678------->-1000 and
12345678------->700
Please let me know in this regard
Thanks & Regards
Swami

Similar Messages

Delta in source system doesn't work

I've created delta-enabled generic datasource. The delta field is timestamp field. I've done Initial Delta run, posted couple new records with appropriate timestamps, tried to run delta but it doesn't work. Even on test delta run RSA3 in source system.
Why?

Hi Gediminas,
You need to maintain safety intervals(at least lower limit)
Check: [How tou2026 Create Generic Delta|https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33]
Hope it Helps
Srini

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

Deltas in source system

hi experts,
what r the deltas in the source system.(in flat file,in r/3 n legacy systems)
regards
venkat

hi,
The data sources will supports different types of delta.
In flat file u can achieve deltas using Additive delta ADD ( from ODS to Infocube)
In the R/3 source system different deltas are possible for a data source. Different types of delta methods are available for a source system and u can check in the table RODELTAM in R/3.
Check these tables also Roosource and Rsoltpsystem in the data dictionary.
AIM:
ABR:After Image before Image reverse Image
ADD:Additive delta
CUBE:Used in Myself system
ODS: Used in Myself system
Assign points if u found helpful.
Message was edited by:
Shahid Syed
Message was edited by:
Shahid Syed

Error while init delta in source system

I use generic data source with generic delta
Delta field - DATUM (Calendar date)
Safety Interval Upper Limit = 1
Delta type = "New Status for Changed Records"
My underline table for data source has 53 records. All records DATUM field value is 2010/09/27.
I'm trying to do Init load today (2010/09/28) and getting no data with error message:
"Data in queue of DataSource Z_PU_IS_PS_98 has been deleted"
Why???? If we count "Safety interval upper limit 1" we'll get 2010/09/28 - 1 = 2010/09/27, so all records in table MUST BE catched by Init!
The data queue for the data source in RSA7 contains " - - " that is an empty value.
My question Why I can't init data source thou

now look that sap.help says http://help.sap.com/saphelp_nw04//helpdata/en/37/4f3ca8b672a34082ab3085d3c22145/content.htm :
+
Safety Interval Upper Limit
The delta-relevant field is a timestamp.
The timestamp that was read last is 12:00:00. Delta extraction begins at 12:30:00. The safety interval for the upper limit is 120 seconds. The safety interval for the delta request is: 12:00:00 to 12:28:00. Upon completion of the extraction, the pointer is set to 12:28:00.
Safety Interval Lower Limit
The delta-relevant field is a timestamp. After images are transferred. In other words, the record is overwritten with the status after the change in BW, for example for master data. Any duplicate records that appear have no effect upon the BW system.
The last changed timestamp is 12:28:00. Delta extraction begins at 13:00. The safety interval for the lower limit is 180secs. The safety interval for the delta request is: 12:25:00 to 13:00:00. Upon completion of the extraction, the pointer is set to 13:00:00.
+
If i'll use LOWER LIMIT I'll get 2010/09/29!

Multiple R/3 Source systems for BW(3.5)

Hi,
A BW system being linked with multiple R/3 source systems , is a very common scenario. But could someone please help me out with a strategy doc / how -to etc. on the best possible way to install business content for multiple R/3 sources .
thanks

Hi Shurobhi,
This is a common scenario. there is not much difference between single source system and multiple source systems.
If you have data coming from 3 source systems you dont need to create 3 cubes and update seperately. you can update 3 source systems data into one single cube. For Example: FI AP Line Item data : You have source systems 1 2 and 3. you can use standard business content ODS and Cube to update FI AP data. Here first, init for source system 1 followed by delta for source system 1, then init for source system 2 followed by delta 2, finally init for 3 followed by delta 3. From here on you can load data to info cube in the above layer.
Thanks
Praveen

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

When are init entries done in source system?And early delta initialization?

Hi Friends,
Q1) When are the init entries done in source system?
If INIT entries are done when I run INIT that means:
If my setup job finishes at 6AM and I run the INIT at 1 PM will I loose all data between 6AM and 1PM?
If INIT entries are done when I run setup table i.e. when setup table load finish then
If my setup job finishes at 6AM and I run the INIT at 1 PM...it will load data till 6AM
and after that data would bere there in Delta queue. So, this is ok...as no loss of data.
Q2) I have read on help.sap that "With early delta initialization, you have the option of writing the data into the
delta queue or into the delta tables for the application during the initialization request in the source
system. This means that you are able to execute the initialization of the delta process (the init request),
without having to stop the updating of data in the source system."
Does this mean when I run INIT at 1PM, no V1 updates will happen for that DS in Source System?
If Yes, that means I should always (when users are online) run INIT with early delta initialization
during times when users would be online?
Thanks!

Hello,
You will find the answers to the questions that you ask and the correct procedure to follow in the SAP note 602260.
Best Regards,
Des

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

Problems Delta Extractor after Homogeneous Source System Copy

Hi,
We have R/3 system landscape HUD, HUQ, HUP. And we have BW system landscape BWD and BWP.
We connect BWD to HUQ and BWP to HUP.
We made a homogeneous system copy from HUP to HUQ.
We haven´t made any homogeneous system copy from BWP to BWD.
We have applied the next OSS note after source system copy:
325525 Copying and renaming systems in a BW environment
184322 Procedure after DB copy of BW source system
184754 Procedure after BW database copy.
But we have problems in our BW Development (BWD), and we have the next Dump "MESSAGE_TYPE_X" when we can change any delta infopacket, the next text are from Dump:
"MESSAGE_TYPE_X" C
"SAPLRSS1 " or "LRSS1F11 "
"RSM1_CHECK_FOR_DELTAUPD"
I think that the problem is about inconsistencies between RSSDLINIT/SEL tables in BW side and ROOSPRMSC/F tables in R/3 side.
Please could you tell how can i solve this Dump, because i can restrart and initial and delta packet for different Datasource and i can´t do anything.
Thanks in advanced,

Hi,
We are upgrading our R/3 system from 4.7 to Ecc 6.
While copying database tables we are using Clinet Carrier tool which is considering only clinet dependent tables. Hence we are loosing our BW delta queue entries in RSA7 of ugraded system.
We found ROOSPRMSC and ROOSPRMSF tables and copying these 2 tables may resolve the issue and We copied and delta went fine.But we are not sure of only these are the tables to be considered.
Please let us know what are the relevent tables to be considered to make the Delta to work while copying Data base tables from one system to another.
Thanks in Advance
Regards,
R@ngzz

We would like to test old deltas from the source system( copied to new)

Hi Gurus,
The scenario is
They will make a DB copy of the Prod system onto a QA system, the Copied system will have
its system ID changed(SID) to a new one.
There will be deltas available in the RSA7, as this is a copy of the 3 weeks old prod
system. Now the delta's will be available on the Copied system pointing to the BW Prod system.
We would like to test these delta's to BW Dev. why we would like to do the delta's to the
BW dev system is to check whether we can do system copies without clearing the delta's on
the source system.
After the system copy we will do all the activities necessary to reflect the system changes
a. Like BDLS, We20, we21,ALE checks, RFCDES, RSLOGSYSDEST, RSBASIDOC, etc on the source system to
reflect the changes of the BW Prod system to BW Dev system.
b. Likewise, we will perform all the above activities on the BW dev system by changing the
existing source system to the new source system( performing BDLS,we0, we21, etc)to reflect
the new Source system with the new (SID).
c. We will check the source system connection
d. Replicate the datasources on the new source system
e. Activate the Transfer rules for the new source system.
Now for us to do delta's from the new source system to the Bw dev system we need to change
underlying tables in source system to point the delta's, arfc TID's etc to the BW dev system.
We can change the entries in the TRFCQOUT, ARFCCSTATE, ARFCDATA tables to point the LUW's and
destination to the BW dev system.
What I presume is if we run the BDLS on the Copied system to change the BW prod system to BW
and also the underlying Tables for the LUW's and etc will still be pointing to BW Dev. I would
like to know if this is the case .
Lastly, appreciate if anyone can say if this is possible to do without having to clear the
BW delta queue on the source system.

Hi Ramesh,
Appreciate a lot for your response, but i would like to know if we can reflect the entries in table RSSDLINIT(Last Valid Initializations to an OLTP Source) and RSSDLINITSEL(Last Valid Initializations to an OLTP Source) in the BW system on the copied source system
tables ROOSPRMSC(Control Parameter Per DataSource Channel), ROOSPRMSF(Control Parameter Per DataSource Channel) by executing the ABAP program RSSM_OLTP_INIT_DELTA_UPDATE after we do the BDLS conversion on the new copied source system.
After the BDLS conversion I reckon the entries in the RSA7 queue, ARFCCSTATE, TRFCQOUT tables willl reflect the BW Development system instead of the BW Production system isnt it.
response much appreciated.
Kalyan

Delta loading master data errors in source system Message RSM340 quality

Hi,
I'm trying to load with delta master data for standard data sources.
In dev, everything seems fine.
I' ve transported the same elements to QA. I've done init, it is ok. I do delta, I get red status: Errors in source system, message no. RSM340. I've tried to put my delta on green, I've remade my init, I've reloading with delta, and I get the same problem.
I have this problem for all master data loading.
Should I install some infoobject from Bi Content?
Thanks a lot !

Hi,
Check following threads
[3003 + R3299 + RSM340] error messages loading an ODS
Extraction failed with error Message no. RSM340
BW Data Loading - Delta Processes
Thanks and regards
Kiran

Delta Loads failling after system copy with error in source system(RSM340)

Hi Guru's
We recently performed system copy in BI side.I am facing same issue in couple of chains.Process chains are failing at delta loads with error in source system(ERROR IN SOURCE SYSTEM-message no-RSM340 ).When I go for repeat option ,delta loads are running fine.I did some research regarding RSM340 and I found note:1576331.
But my system is not showing any 'Time Inconsistencies'.So.I was not able to find any clue about it.
Could anybody help me out in this aspect.
Thanks!!!
Kuldeep

Hi,
Check whether the profiles that ran in background have the following authorizations.
The RFC user on BW, receiving data from OLTP system, should have S_BI-WHM_RFC and S_RS_ALL in the user profile.
The RFC user on OLTP, receiving request from BW system, should have S_BI-WX_RFC, S_IDOC_ALL, and, B_ALE_ALL in the user profile.
Regards .

Error in Delta load; error in source system

Hi,
I'm extracting from 0FI_AA_11.
Performed a full load.
Then initialized without data transfer.
When i run delta (0 records) , it fails with 'error in source system' .
Strangely, when I run delta again in REPEAT mode, it runs succesfully.
this is happening everytime i run delta.
Please help

FI_AA_11 is sure capable of handling delta.
It does have some dependencies with master data and these are pretty awkward sometimes.
I don't know when you are running your deltas (during opening hours from the office?) but in your process chain also the MD objects must be present.

When exactly source system recognizes the last delta is succesfull/failed.

When exactly does the source system recognizes the last delta is successful/failed?
Case -1: In logistic applications..
             What if I changed quality status to red for a successfully completed delta, and then requested new delta?
Case -2 : In Financial applications..
              When exactly BWOM2_TIMEST fields updated. I mean BW acknowledges to the delta load immediately saying it is successful or fail, or at the time when we request the next delta?
              What if I changed quality status to red for a successfully completed delta, and then requested new delta? It executes repeat or returns 0 records.

Hi,
Here's the explanation:
Scenario 1 -Logistics Delta
Sinc logistics delta comes from Delta Queue (RSA7) and IP takes daa from Delta queue so betwen RSA7 and BW, IDocs are transferred which sends messages for successful completon of extraction. As soon as extraction is over and a particular IDoc is sent to BW the BW marks the delta s successful. This happenes exactly when job is Source system completes Now if you make a successful delta as red then the IP identifies that last delta was not successful and requestes a repeat of last delta which again goes to RSA7 and picks the last delta and also the new deltawhich has come in RSA7. Note: RSA7 stores both new delta records and one last successful delta records(for delta repeat)
Scenario 2 - FI Delta
Sinc FI deltas are based on timestamp mechanism there are 2 possibilities:
a) The extraction fails while picking records from R/3 table (G/L, Ap and AR tables). In this case the timestamp isnot registered in BWOM2_TIMEST table and arepeat will work fine.
b) The load fails during procssing in BW (e.g update rules processing) and the job has completed in R/3 and has set the timestamp in table BWOM_TIMEST. In this case we will have to reetthe tmestamp and run the delta again.

Doubts in delta in source system

Similar Messages

Maybe you are looking for