Absence of Delta records

Experts,
We are using few CRM data sources.
Recently we have enabled delta in Generic Data source.
Delta option : TIMESTAMP
Upper limit : 1800 sec.
Now When we create records(transactions) in Portals.
These records are normally visible in 0CRM_OPPT_H and the Generic Data Source.
Now the issue is delta records are available in 0CRM_OPPT_H but not in Generic data source. we are receiving the status as 0 from 0 records. Status green.
Please respond.
Thank You.

solved

Similar Messages

Delta Records is not getting updated in delta queus when changes done

Hi All,
In Quality system , when a user makes a change to an order's ship-to address, the changes are "triggering" a delta record into the delta tables for BI to extract. This can be seen via tcode rsa3's delta tester.
In Productionn System, when the user makes the exact same change, nothing is added to the delta table and the changes never come over to BI unless a full extract is request for the order.
Why changes not getting updated, please give your inputs.
Thanks & Regards,
Venkat Vanarasi.

Do you have your V3 update job active and running? THis job wites changes to the delta queue. Of course your datasource has to been initialized and a delta queue should be setup. You can check it in RSA7.
Regards,
Juergen

Impact of Delta Records on Key Figure Summation in DSO

Hi experts,
I have a key figure with aggregation type "summation" in a DSO. I would like to know the impact of delta records on the key figure.
E.g.
source DSO
doc_id (key) | doc_pos | type | amount
4711 | 1 | A | 100 USD
4711 | 2 | B | 20 USD
target DSO
doc_id (key) | amount
4711 | 120 USD
If the first record is modified ("type" from A to C) as follows and delta-loaded to target DSO:
4711 | 1 | C | 100 USD
This will lead to incorrect amount:
target DSO
doc_id (key) | amount
4711 | 220 USD
How can I handle this situation?
Thanks in advance.
Regards,
Meng

Hi..
I believe one document number and document Item will have only one type.
Like 4711 1 should have only one type ( A / B / C).
If the above assumption is true then just remove Doc Type from Key field of source DSO.
Then From Source to Target Change Log table can handle this.
Regards
Anindya

Delta records not updating from DSO to CUBE in BI 7

Hi Experts,
Delta records not updating from DSO to CUBE
in DSO keyfigure value showing '0' but in CUBE same record showing '-I '
I cheked in Change log table in DSO its have 5 records
ODSR_4LKIX7QHZX0VQB9IDR9MVQ65M - -1
ODSR_4LKIX7QHZX0VQB9IDR9MVQ65M -   0
ODSR_4LIF02ZV32F1M85DXHUCSH0DL -   0
ODSR_4LIF02ZV32F1M85DXHUCSH0DL -   1
ODSR_4LH8CXKUJPW2JDS0LC775N4MH -   0
but active data table have one record - 0
how to corrcct the delta load??
Regards,
Jai

Hi,
I think initially the value was 0 (ODSR_4LH8CXKUJPW2JDS0LC775N4MH - 0, new image in changelog) and this got loaded to the cube.
Then the value got changed to 1 (ODSR_4LIF02ZV32F1M85DXHUCSH0DL - 0, before image & ODSR_4LIF02ZV32F1M85DXHUCSH0DL - 1, after image). Now this record updates the cube with value 1. The cube has 2 records, one with 0 value and the other with 1.
The value got changed again to 0 (ODSR_4LKIX7QHZX0VQB9IDR9MVQ65M - (-1), before image &
ODSR_4LKIX7QHZX0VQB9IDR9MVQ65M - 0, after image). Now these records get aggregated and update the cube with (-1).
The cube has 3 records, with 0, 1 and -1 values....the effective total is 0 which is correct.
Is this not what you see in the cube? were the earlier req deleted from the cube?

Delta records are not loading from DSO to info cube

My query is about delta loading from DSO to info cube. (Filter used in selection)
Delta records are not loading from DSO to Info cube. I have tried all options available in DTP but no luck.
Selected "Change log" and "Get one request only" and run the DTP, but 0 records got updated in info cube
Selected "Change log" and "Get all new data request by request", but again 0 records got updated
Selected "Change log" and "Only get the delta once", in that case all delta records loaded to info cube as it was in DSO and gave error message "Lock Table Overflow" .
When I run full load using same filter, data is loading from DSO to info cube.
Can anyone please help me on this to get delta records from DSO to info cube?
Thanks,
Shamma

Data is loading in case of full load with the same filter, so I don't think filter is an issue.
When I follow below sequence, I get lock table overflow error;
1. Full load with active table with or without archive
2. Then with the same setting if I run init, the final status remains yellow and when I change the status to green manually, it gives lock table overflow error.
When I chnage the settings of DTP to init run;
1. Select change log and get only one request, and run the init, It is successfully completed with green status
2. But when I run the same DTP for delta records, it does not load any data.
Please help me to resolve this issue.

Delta Records not coming from sm13 to rsa7

Hi,
We have found that for the application 02, delta records are coming in RSA7(delta queue) even if these are coming in sm13.
It appears that some protocol responsible for bringing the delta records from sm13 to rsa7 is failed.
Fact is that for the data sources related to application 02 (purchasing: LO Cockpit), we did some enhancements through LBWE.
But before transporting the relavant requests to production, we did not delete sm13 and rsa7 entries and also at the time of transpoting the requests in production, postings were made by several users and the entries for those were appearing in sm13.
Thing to notice is that whatever fields were shifted in LBWE, those changes have successfully appeared in production after transporting ( LBWE and relavant Extract Structure in Production are containing the required changes)
Now each time to load the data in BW, we have to delete and refill the set up tables and schedule full update which is taking a lot of time and not advisable.
Each time when we are running job control in LBWE, it is throwing dump in ST22 with the heading CONNE_IMPORT_WRONG_STRUCTURE.
It appears that some internal problem has occured in the structure of rsa7/sm13 for application 02.
Also it is written in the dump that:--
When attempting to import data, the structure of the complex object
"MC02M_0ITM_TAB"
was not compatible with the target object. The error occurred with
component no. 24.
Try to find out why the structure of the object is unsuitable.
There are several possible reasons:
|
--- In the ABAP Dictionary, the structure of the imported
|   object has changed. Make sure that the structure of the imported
|   object matches that of the Dictionary structure.
|
|   If the data could not be restored from another source, this data
|   must be read with the "old" structure, then converted and exported
|   back with the new structure, so that future IMPORTs always work
|   with the new structure.
|
--- A new program version is active, and it no longer matches the
    dataset. Try to solve the error by generating the program "SAPLMCEX" again
    as follows:
    In the SAP System, choose the transaction SE38. Enter the program
    name "SAPLMCEX". Then choose the "Activate" function.
Now how to make the things back on track so that delta records come in rsa7 from sm13 so that we schedule delta update in info package.
Is there any OSS Note or Standard SAP Report which we have to run for getting the solution.
If not, please suggest the solution.
Thanks in advance,
Tarun Brijwani.

Hi,
1. Check whether your Extractor will support Early Delta Inti or not..
See this link for Early Delta Initia...
http://help.sap.com/saphelp_nw04s/helpdata/en/80/1a65dce07211d2acb80000e829fbfe/frameset.htm
Minimize downtime for delta intia..
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5d51aa90-0201-0010-749e-d6b993c7a0d6
Perform this activity on Weekends,
Also see 436393 - Performance improvement for filling the setup tables
Note 753654 - How can downtime be reduced for setup table update
2. Obviously Background job.
BG jobs can be monitored thru SM37 and maintain Logs thru SM21 and can be easier for administration
Thanks

PSA had delta records but while updating to DSO it shows zero records.

Hi all,
I have a delta info package which picks up the delta records. The data is successfully extracted from source system and updated in the PSA. But the no of records extracted to the DSO are zero. Couldnt understand what is the problem. Request your valuable inputs on this issue.

Inside the InfoPackage which you ran, click on the Monitor button or hit F6. In the next screen, open up the folder with the correct run date and select the node - on the right hand side of the screen, click on the tab named Details. Click on No to the subsequent dialog box. Here, open up the last node named "Processing (data packet)" then open up node named "Data Package". Open up all nodes under this one and you'll probably find that either there is a custom start/end routine in the Transfer Rules or in the Update Rules which is filtering out the records from the PSA from updating the target (Cube/ODS). One of these nodes will show you the exact count of how many records came into PSA and how many were passed on to the data target to update it and the reason behind it, for e.g. "Number of data records changed form 16 to 2 in start routine".
Hope this helps.
Cheers,
Sougata.

How to reprocess delta records during subsequent update of data targets

Hi,
I have an ODS which sends in delta records to a cube above it. Now there is a data load, happening monthy from a flat file, which was successful upto the ODS, but failed in the cube due to one invalid record. How do I reprocess this data load after correction of the invalid records in the source flat file?
The method I currently follow is to delete the failed request from the cube and then do a selective delete of records from the ODS and then reload the last data after correction.
Is there a better way to just reprocess the last load from the flat file?
Thanks & regards,
Nikhil

Hi Bhanu,
Thanks for the response. I will explain a bit more in detail. Suppose there are 5 records coming in from the flat file - now 4 of those records are correct and one has invalid data.
All 5 records get loaded to the ODS successfully but in the cube we have a function module which works on the data and aborts the entire data package if it finds even one invalid record. So nothing gets loaded into the cube at all.
Now if we correct the one invalid record and then reload into the ODS - it will just send this corrected record over to the cube and we will miss out on the other 4 records which were originally correct since the ODS does not detect them as changed.
If we delete the request from the ODS (rather than doing the selective delete) then it disables the delta in the ODS asnd we have to reinitialise everything - which we cannot afford to do in a production environment.
Hope the problem is a bit more clear now.
I was looking for some way to just resend all the five records - with the one corrected record to the cube without going through this selective delete process sinc eits too cumbersome and we run the risk of messing up with actual data ina production environment.
Thanks for the help,
regards,
Nikhil

Loading Last three days of delta records in Production Server

Hi
I have a Process Chain in BI-Production Server which runs dailiy and loads the delta records dailiy . I have 'Custom DataSource' which loads the data from QM-Tables .
My Process Chain is failied due to the "Caller 09 Error for the datasource". So now i transported that datasource from R/3-Dev To R/3-Production and replicated into BI-Production Server .
So how can i load the delta records of last three days . I mean , how can i scehdule the last three days of delta updated records .
pls let me know
regards
Kumar

Remove the failed request. Repeat the delta. This will upload previous failed request
Repeat the delta again with infopackage selection for 3 days

Short dump error when extracting delta records from R/3

I am working on BW 3.5 and I am facing some short dump error when extracting delta records from the r/3 to BW.
Below is the error message
Kindly do the needful ASAP.
Job started
Step 001 started (program SBIE0001, variant &0000000024277, user ID BWREMOTE)
Asynchronous transmission of info IDoc 2 in task 0001 (0 parallel tasks)
DATASOURCE = 0ISCM_PAYMENT_01
         Current Values for Selected Profile Parameters               *
abap/heap_area_nondia......... 2000000000                              *
abap/heap_area_total.......... 2000000000                              *
abap/heaplimit................ 40000000                                *
zcsa/installed_languages...... DE                                      *
zcsa/system_language.......... E                                       *
ztta/max_memreq_MB............ 2047                                    *
ztta/roll_area................ 6500000                                 *
ztta/roll_extension........... 2000000000                              *
2,454 LUWs confirmed and 2,454 LUWs to be deleted with function module RSC2_QOUT_CONFIRM_DAT
ABAP/4 processor: MESSAGE_TYPE_X
Job cancelled

Hi,
I look at the transaction ST22 to see which type of error has given you. Take a look at the notes to correct the error.
Another option is to look at OSS notes, because the error is giving you a standard extractor.
Greetings,

Missing Delta Records for 2LIS_02_ITM & SCL

Hi Experts,
this is how my problem goes.
i have done my set up table filled on 12th Dec 2010 and from that time onwards the delta were running everyday and filling the DSO and Cube.
Accidently by some others PC in prod all my delta loads and the setup table load is being deleted except yesterday in PSA for these 2 extractors and now because of some change i have to do a full load to DSO.
But as the PSA is emply and have only yesterday's request i have, deleted that one as well and done a Init Delta to it and i found out that only the Set up table is comming now and all the deltas in between are missing.
i have tried a full LOAd to PSA and the result is same.
How can i get those missing delta records from 12th Dec last year till today with out doing another set up table fill or Do i have to have fill the set up table again till today and thats the only way? i will set the delta again after that.
Do we have to have all the user locked for the setup table fill (for Queued Delta type) ? Lot of people says yes you have to and others says no you don't require. i got one white paper and it clearly says no user locking is required. please find the link below. what is the correct way?
[http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d019f683-eac1-2b10-40a6-cfe48796a4ca?quicklink=index&overridelayout=true]

Hi,
As per my knowledge you want load particular period of data try repair request may issue solve.
Regards
Sivaraju

Problem in getting Generic Delta records to BW

Hi BW Gurus,
I have got one issues with which I have been struggling a lot for several days . i.e
I am extracting data from R/3 using Generic Extractor (View) from CATSCO and CATSDB. At the time of delta, I tried using Personal No with Time Stamp giving Upper limit as 1800 seconds. I executed Infopackage in BW immediately. But it didn't work out. So plz guide me how I can get Delta Records to BW. Or should I do any necessary factors apart from these in Generic Delta Screen (RSO2).
It is very urgent.
I will be thankful for solving this issue.

Hey I am "Intros" again,,
I am sorry man for giving the wrong T-code mistakenly in my last reply..
To solve the proble...the whole process is same what I told u before..
But... you got to go to T-Code : BD87 , then execute the IDocs manually to bring them in to BW
identify your IDocs which are missing in Monitor screen, then goto BD87 and select those IDocs and click execute... )you can search the IDoc's based on selection conditions)
I hope this will help u...
cheers man..
---Intros

Delta record not getting created

Hello Experts -
I'm working with 0mat_plant_attr datasource.
In ECC, I made changes to some materials in MM02. I changed the values of MRP Type and Rounding Value in MRP1 tab. The data is saved correctly but a delta record is not getting created. In RSA7, no records are there for 0mat_plant_attr. MRP Type, Rounding Values are attributes of 0mat_plant. I did run the initial infopackage from BW to enable the delta.
Can someone please help me with this? I'm not doing something correctly.
Thanks!

Hi Syed,
I think you may have to run an attribute change run after executing your infopackage to see the changes. The modified attribute needs to be set as active in by the attribute change run.
Master data & attribute chage run
Regards,
John

Problem in extracting Generic Delta Records

Hi BW Experts,
I have an issue. I am using Generic Extractor using View from Tables CATSCO and CATSDB. At the time of Generic Delta, I am using the field PERNR(Personal Number) to use Generic Delta. I am using Time Stamp. For this I have selected Safety Interval Upper Limit 100 seconds.But now I am testing whether we get delta records or not. But I am not getting records to BW. They are changed in R/3. So please guide me whether I should use Calday or Time Stamp . How can I get delta records to BW.For testing , I am executing InfoPackage immediately after changes in R/3 like for two or three minutes. Once I will be sure on getting records to BW, then I can move to Production where we execute process chain at 1:00 a.m
there I can use Calday giving Safety Interval Upper Limit as 1 day. Considering the above factors please guide me .
I will be thankful for solving my issue.

PERNR doesn't contain a date right? so timestamp tells the system PERNR is a date field... That will never work.
What kind of value does PERNR contain, is it an incremental value that adds up at every new entry?
Generic delta needs a field that changes in a way that can be predicted.

Procedure to know No of delta records

Hi All,
There were some changes done in CRMPRD for the DS:Business datasource.
So we want to compare the changes is DELTA records in CRM loaded to BI server.
Now,
Is there any way to know the no. of delta records in the R/3 production(here CRM) for partiular dates.
For eg: business partner delta records in CRM production.

Hi,
You can try in RSA3 by giving this data source, select delta upload and in the field selections tab give the dates and run it, here you can get the no.of records extracted for that data source on that day.

Absence of Delta records

Similar Messages

Maybe you are looking for