Delta Extraction of CO_OM_CCA_9 after change in BWOM_Settings

Hi Sap Gurus,
We have implemented the SAP OSS note 553561 to modify the safety limit in BWOM_settings for most updated Delta Extraction for CO DataSource 0CO_OM_CCA_9, But when i schedule the delta it brings only the CO documents that have created in the month of September 2011 only and we do have a lot of documents resides in R/3 side. Last Delta run a year ago in Sandbox.
Any idea why its not fetching the complete delta?
All kind of help will be appreciated.

Hi
check how much data you have in RSA7, delta will pick the data in RSA7.
check you have any selections in IP on 0CALMONTH, then remove the selections and run the IP to get all the data.
Before you start delete the previous request to overcome duplicate records.
Regards,
Venkatesh

Similar Messages

How to see deleted records in delta extraction from view

Hi folks,
i am currently reflecting about delta extraction from a view:
The view contains a date field (change date) which is used to identify new or changed records.
So the delta extraction of new and changed records works without problems.
But what is happening with records that are deleted in the source system?
My current understanding is that deleted records will not be shown in the view. Therefore the deletion is not visible in the extraction.
- Is there a workaround for this problem?
- How is deletion of records normaly handled in generic extractors?
- Is it impossible to extract a deletion when using views?
any suggestions and help will be appretiated...
bye

Hello Florian,
Generally records will not be deleted (until if you physically delete it from table) but will have a status deleted.
So it doesn't matter whether you use view or tables the deleted records will be extracted through the view to update the BW data targets.
Thanks
Chandran

Effect of Change in structure for 0FI_GL_4 on Delta extraction

Hi,
We are upgrading our R3 system from 4.7 to ECC6.0.
In 0FI_GL_4 we have a appended one X field and it was working fine. Now the same filed is available in standard content ( In new Version) Which will cause the structure to become inactive ( We came across this situation in testing phase).. We activated the same by removing the field from Append structure and started pulling records for the same.
1. If I change the extractor and continue with my delta extraction will it work???
2. I have not done any changes to the customer exits written for the old field X...but I didn;t get any dump for the same .. Is ithis k????
Regards,
Rangz

Hi Simon,
Thanks for the confirmation.
In our business process we are extracting data for FI with safety interval 1 day, During upgrade activity ( This will be done on the same Server)
Consider If I Shutdown R3 system today 28th Jan and If I try to extract the data, The FI extractor will get the data till yesterday ,same will applicable even If I do the repeat delta extraction.Is it right???
After upgrade( after changing the 0FI_GL_4 structure, after 2 days of upgrade activity), If I continue with my delta extraction, will it work properly for FI Data sources??? Am I going to get the data records for the transaction that happened on 28th Jan this time????
Or If not any other methods to overcome the same???
Regards,
R@ngzz
Edited by: Ranganath Kodiugane on Jan 28, 2009 12:53 PM

How to make JOB CONTROL setting for delta extraction in Production system .

Hello All,
We are in the process to transport our development to PD server in BI . We have transported the data sources to ECC production and now we are filling the setup table for " SD BILLING BW " . After filling Setup table data in full mode through infoPackage we have to load data in delta mode .
How we can set our Update mode(LBWE setting) in PD server ?
Is LBWE T.Code authorisation required in ECC PD server to make the setting of Update mode or We have to set all Job Control Paramater in Dev System at the time of transport the datasource request to ECC production . Is our time which is set in job control of ECC development will be reflected in ECC production ?
can any body tell me about how to make setting for delta extraction in Production system .
Thanks ...

Hi,
How do you load the data in the development system?
- you set up the update mode in the infopackage. There you must customize "Initialization"
- you have to filled the setup table in the production system without laoding the data in the BW? then this step was for nothing. Filling the setup table and do the INIT in the BW, this must be together - during no changing will be done in your R/3 SD.
Sven

Generic Delta Extraction via Function Module

Hello,
i need a help for a generic delta extraction based on a Function Module. As an example i take the function module RSVD_BW_GET_DELTA_DATA.
My generic delta extractor based on the field AEDAT - Change Date and i will extract purchase service orders and entry sheets.
In the sample function module the select for the extraction worked with the table ROBWQTSTAT, but this table ist empty after the initialization.
OPEN CURSOR WITH HOLD G_CURSOR FOR
      SELECT * FROM ROVERCUBE1
               WHERE COUNTRY IN L_R_COUNTRY AND
                     REGION IN L_R_REGION AND
                     KUNNR   IN L_R_KUNNR AND
                     TYPE    IN L_R_TYPE AND
                     GJAHR   IN L_R_GJAHR AND
Here the timerange calculated in form GET_TIME_INTERVAL is evaluated.
                     TSTMP   IN S_R_TSTMP AND
                     OBJVERS = 'A'.
I found the table ROOSGENDLM. In this table i found the field DELTAID with the last date of the extraction and the field REPEATID with the date for the repead-Update.
My Questions:
Is this the right way to build an generic delta extraction with an function module or must i install a coding in my function module for an update of the table ROBWQTSTAT?
Which settings are needed in the table ROOSOURCE for a generic delta extraction via function module?
Best regards
Uwe

Hi Uwe,
please have a look at https://weblogs.sdn.sap.com/pub/wlg/2415. [original link is broken] [original link is broken] [original link is broken] It might help
kind regards
Siggi
PS: We already had almost the same question here today.

Intervals with generic delta extraction

Hello,
Can some1 explain when do we use intervals in generic delta extraction with a good example?
Thanks in advance.
Regards,
KS

Hi,
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.
refer to this link.
http://help.sap.com/saphelp_nw2004s/helpdata/en/3f/548c9ec754ee4d90188a4f108e0121/frameset.htm
Hareesh

Problem while delta extraction

Dear Experts,
I am facing a poblem while delta extraction for AR ODS. When I check the status of delta extraction it shows green and records transferred as well but when i check into BW side I find some records missing. When I faced this problem for first time I did the init load again after which all records came into BW side but subsequently again when some changes were made in R/3 side and delta was uploaded, again the same records were found missing.
If anyone has any idea why this is happening please guide me as to how to go about it. Also I have given no filter conditions in data selection.
Thanks in advance. Will assign points happily for any kind of assistance.
regards
akshat

Hi,
the standard delta extraction is not sensitive to program in the R/3 side that write directly into tables. For my experience, this is the only reason when the delta does not work.
So, check with the R/3 people, if they are input account document by write directly into BSIS or BSAS.
Rgs
Antonino

Repeat delta extraction

Hi,
The Finance data is not coming to BW system.We are suppsed to repeat delta extractions.Can anyone tell me how I can proceed?

Hi Prithwish......
A cube will never be in Overwrite mode.........cube is always additive........due to this in some Delta Process.....we need an ODS inbetween.......bcoz in ODS both the Update mode is possible ie Overwritten or Additive......for an example........An after image provides the status after the change, a before image the status before the change with a minus sign. A reverse image sends the
record with a minus sign too, indicating at the same time that it is to be deleted. The data packages are serialized in the process. The delta process controls whether adding or overwriting is allowed. In this case, both adding and overwriting is allowed. This process permits data to be updated in a DataStore object and in an InfoCube.
In case of ODS.............if u r in BI 7.0 then check the update mode in Transformation and if u r in BW 3.X.....then check in Update rule......
Regards,
Debjani....

Question on SFSF Adapter : Delta sync to fetch only changed records.

Hi All ,
As per the SAP Document on SFSF Communication channel, one of the feature supported by SP00 release of the connectivity add-on 1.0 is :-
1. Delta sync to fetch only changed records
SFSF Adapter: Delta Sync
The delta sync features enables you to fetch only the records that were modified after the last successful data fetch from the SuccessFactors system.
This increases the efficiency of query operation.
So below are my question accross Successfull run date feature :
Is it SAP PI Connector internally maintains this last successful run date ?
what would be Time-Zone of Successful run date : Is it where SF DC is located or where PI Box is Located ?
what is it mean from successful run date ? - is it process successful run date or is it just communication channel successful run date ?
For Delta extraction - This Successful Run Date - Is it maintained internally for Interface wise or Communication Channel wise ?
eg. If i have 5 Delta Interface - will SAP PI maintain 5 Successfull run dates w.r.t to each connector or w.r.t each Process ?
for more information please open below URL.
http://help.sap.com/saphelp_nw-connectivity-addon100/helpdata/en/1e/22aaf0780d4b78b6f889157f6a8035/frameset.htm
Regards
Prabhat Sharma

Hello all,
I have the same question : in the "official" documentation (SuccessFactors (SFSF) Adapter for SAP NetWeaver Process Integration) is mentioned this :
Delta Sync - The delta sync features enables you to fetch only the records that were modified after the last successful data fetch from the SuccessFactors system. This increases the efficiency of the query operation.
Anyway I cant find any specification on how to use this feature. Do you have any suggestion on how to implement it or any reference to an existing documentation?
Do I need to write you an email to get the info?
Regards

Delta extraction not working

Hi all
I have a question on delta extraction. I initialised the first extraction for the DS 2lis_11_vahdr and to test the delta process created a few sales orders after that. and when i check in RSA3 in the OLTP sys. it shows the number of records as in the initialised state the newly created records are not shown in the total numbers.
i also tried a delta extraction from my BI system and it shows teh number of records extracted as 0. But if i delete the extract structure in and fill them again the number of records now is increased.
is there any setttings that i have to do either of the systems to get the delta process going?
Thanx in advance
Sujai

I tried a delta extract manually and no records were updated. The extraction monitor status is green and has the following message
No new data since the last delta update
Diagnosis
The data request was a delta update, meaning, the data basis in the
source system has not changed since the last update.
System Response
Info IDoc received with status 8.
Procedure
Check the data basis in the source system.
In R/3 i have the datasource displayed in RSA7 and in LBWQ i Have the following entries.
Queue Name               Destination                      Entries
MCEX11                   NONE                                56,416
MCEX12                   NONE                                41,836
MCEX13                   NONE                                12,971
MCEX17                   NONE                                   147
MCEX17_1                 NONE                                   102
Should there be a destination described here??
Kindly help as this is getting a little urgent....
Sujai

Delta Extraction Issues

Hi All,
We are doing delta extraction for the all Master Data Objects from R/3, wherever supported by SAP. But, for 0costcenter, 0costelmnt,0profit_ctr and 0G/LAccount from R3 Production System PR1 we are getting few records in Delta.
Scenario is like this: Master Data for these objects is not created in this system, it is created in other Prod System PR5 and Master Data is then ALE'D to all Production Systems.
Problem in Delta : In Delta Extraction for these Master Data Objects, we are not getting any records which are ALE'd to this System. We are only getting some records which are changed in the PR1 system. That Means when Master Data is ALE'd from PR5 to PR1 it is not Populating in the Delta Queue Tables in R3.
Delta is working fine for all other Master Data Objects which are Created in PR1 and MAintained in this System.
Not sure where exactly is the problem, after ALE to PR1 is there any program need to be run in R3 which populates the Delta Queue Tables for these Master Data Objects.
Any IDeas or Suggestions on this.
Regards
Deepak

Hello Deepak,
ideally you should have a single source for your master data (PR5). So why don't you load the master data from this box into BW (and skip PR1)?
If you still do changes in PR1 (would this not make it out-of-sync with PR5?), then you can run the delta extrator as well.
Regards,
Marc
SAP NetWeaver RIG, US BI

Problems with Delta Extraction for 0CRM_OPPT_H (no data found)

Hi,
I've some problems with the Delta Extraction of the Infosource 0crm_oppt_h (CRM Opportunities Header). After initialization I get no delta data from the CRM system.
What I already did:
Activated 0crm_oppt_h Data Source (checked functionality with rsa3)
Started Info Package (Init) on BW side (worked fine)
Checked the status of the Data Source on the CRM system using BWA7 ("initial upload" is unmarked; "delta active" is marked and what makes me worry is that the column "Queue exists" in unmarked...)
If I change anything (like Phase, Expected Sales Vol.) in the opportunity, the Delta Extraction get no changes.
Could You help me out, please?
Best regards,
Markus Svec

hi Markus,
try to check oss note 788172
Release Status Released for Customer
Released on 23.03.2005
Priority Correction with high priority
Category Program error
Symptom
No data exists in delta extraction from the CRM server to the BW system for business transactions, if parallel processing is applied as per note 639072. But Data is extracted if parallel processing is switched off.ie. when BWA_NUMBER_OFF_PROCESSES is set to 1,there is data during delta. This applies to the following DataSources:
0BBP_TD_CONTR_1
0CRM_COMPLAINTS_I
0CRM_LEAD_ATTR
0CRM_LEAD_H
0CRM_LEAD_I
0CRM_OPPT_ATTR
0CRM_OPPT_H
0CRM_OPP T_I
0CRM_QUOTATION_I
0CRM_QUOTA_ORDER_I
0CRM_SALES_ACT_1
0CRM_SALES_CONTR_I
0CRM_SALES_ORDER_I
0CRM_SRV_CODES
0 CRM_SRV_CONFIRM_H
0CRM_SRV_CONFIRM_I
0CRM_SRV_CONTRACT_H
0CRM_SRV_PROCESS_H
0CRM_SRV_PROCESS_I
Other terms
DataSources, BWA, initial extraction, delta init, parallel processing, no data in delta.
Reason and Prerequisites
There is an update on the generated delta table which causes data corruption in running delta initializations as the changed delta sets will be deleted with every further update on documents. An open cursor statement is there without fetch data in SMOX3_GET_DATA.
Solution
The problem is solved with the attached corrections.After applying the corrections a new initialization of the affected datasources is necessary.

Delta extraction of modified data in already closed periods

Hi everyone,
we're currently facing a scenario where data in BI does not seem to match R/3. We're using the business content extractors 0ec_pca_3 & 0ec_pca_4 to get data for a balance sheet report, but some of the figures don't match. The client currently uses periods 001 - 013, in other words they have one special period. After much investigation and discussions with the users, we found out that the client sometimes goes back and makes changes to periods that have already been closed. For instance, period 013.2007 is closed in R/3 (and loaded to BI), at some point in 2008 the client "reopens" the period and modifies the data. This data does not seem to be picked up by the BI delta extractor. So our theory is that the two systems don't balance because of this late period modification. My questions are:
Is it part of standard SAP FI process to re-open an already closed period and add/change/delete data?
If so, would this changes be picked up by the standard delta extraction? If not why and is there anything we can do to achieve this?
If not part of standard process, what would the solution be? We've suggested to potentially create a separate period, say period 014, for these changes? Would this be a recommended way forward?
Thanks for your time.
Cheers,
Dion

0EC_PCA_4 does not support delta right?
Have you already checked contraints mentioned in these links?
http://help.sap.com/saphelp_nw70/helpdata/EN/5d/ac7d8082a27b438b026495593821b1/frameset.htm
Can a full load for the missing records be tried?
Also look at Note 577644

Data with delta extraction.

Hi Gurus
I want a small clarification regarding data with delta extraction.
If today the data is extracted from r/3 system with delta to ODS object and the data is activated and datamarted to another ODS and Cube.
Now if tomorrow the same records had changes how will the old data will be changed i.e in cube if we compress the old data what is the scnerio.
Can anyone explain in detail starting from Delta queue to change taking place at cube.
Regards
Raju

Raju,
Don't worry about compression of Cube... Even if you do delta after compression, nothing to worry about Data. Next time you compress it, it will Make 1 record.
Assume...
Initially... in ODS Document 45000001 Item 0001 qty 10 Amount 20
in Cube Document 45000001 Item 0001 qty 10 Amount 20 (After compression)
Qty changed to 5...
In ODS Document 45000001 Item 0001 qty 5 Amount 10. This record will create 2 delta records to Cube.
that is looks like this...
Document 45000001 Item 0001 qty -10 Amount -20 Record mode ' X' (Before Image)
in ODS Document 45000001 Item 0001 qty 5 Amount 10 Recordmode ' " (After Image)
Finally cube contains...
Document 45000001 Item 0001 qty 10 Amount 20
Document 45000001 Item 0001 qty 10 Amount -20
ODS Document 45000001 Item 0001 qty 5 Amount 10
If you compress cube... you will endup with last record.
all the best.
Nagesh Ganisetti.

FI GL delta extraction

Dear friends,
I have a question about GL delta extraction . On my first GL delta update , data load extacts huge amount of data , and on later delta updates data load ends with same data quantity . For example on my first data load 100.000 records updated and on next uploads each time I'm getting 160 records (tried 6 times and all are 160). As far as I know timestamp logic applied on GL side . What is the reason of these extra 160 records , These delta loads suppose to load 0 records on next updates .
Can you please help on GL delta logic please
Thanks in advance

Hi
Delta extraction enables you to load into the BW system only that data that has been added or has changed since the last extraction event. Data that is already loaded and is not changed is retained. This data does not need to be deleted before a new upload. This procedure enables you to improve performance unlike the periodic extraction of the overall dataset.
Financial Accounting line items are read by extractors directly from the tables in the SAP R/3 system. A time stamp on the line items serves to identify the status of the delta data. Time stamp intervals that have already been read are then stored in a time stamp table. The delta dataset is transferred to the BW system directly, without records being transferred to the delta queue in the SAP R/3 system (extraktor delta method).
The Financial Accounting line items are extracted from the SAP R/3 system in their most recent status (after-image delta method). This data method is not suitable for filling InfoCubes directly in the BW system. To start with therefore, the line items must be loaded in the BW system in an ODS object that identifies the changes made to individual characteristics and key figures within a delta data record. Other data destinations (InfoCubes) can be provided with data from this ODS object.
http://help.sap.com/saphelp_bw33/helpdata/en/af/16533bbb15b762e10000000a114084/frameset.htm
Hope it helps

Delta Extraction of CO_OM_CCA_9 after change in BWOM_Settings

Similar Messages

Maybe you are looking for