Delta extraction with errors

Hello experts,
I was faced with a new problem this week, and I dont know the correct procedure to solve the situation. During the definition of BW landscape was decided to use extractors with no delta functionality.
A few months later we decided to change the strategy towards delta instead of the initial approach.
Last Monday our transactional process chains went wrong because, in some of the lines extracted were included incorrect master data. The problem is not in BW, because this master was not supposed to be in BW.
Now, we have to a Delta repeat, but it still doesnt work because of the same lines.
The ECC users said that they were going to correct the FI documents in order to stabilize the problem, but not for now.
As we cant wait for that time what is the best approach to solve this problem.
Best regards,
Points will be awarded.
João Arvanas

Hi,
your assumption is correct. Depending on the solution they will choose in ECC.
Follow the issue closely in order to know what option is retained.
If they cancel the old document and create another; this wrong data will stay like this. The question is: does BW has to show the truth and reflect ECC? In any case you'll have to load this data at least to the PSA. This data will come when you'll perform a full load as well...
So, depending on the number of documents; you could change your PSA and avoid the problem...
please describe your issue with more detail...
hope this helps,
Olivier.

Similar Messages

Error in delta extraction with SAP DataSource 2LIS_11_VAHDR ...

Hi all
I used the old data load process(3.5) in 2004s system.
There are errors in detla extraction with SAP data source
2LIS_11_VAHDR
2LIS_11_VAITM
2LIS_12_VCHDR
2LIS_12_VCITM
The delta data(before/after image) aren't right.
Has anyone experices with this problem?
thanks in advance

No Problems yet,explain the error message with error number in details here for some one to help you.
Hope it Helps
Chetan
@CP..

BI 7.3 delta extraction with SQL Server 2008

Hi experts,
I'm trying to extract data with delta update from a SQL Server with UD Connect, i test this ways:
Field DateTime in SQL Server: The problem is I only can delta within a day, no changes detected in the same day because SAP detects two fields here date and time, and can only can reference date field as a delta field.
Field TimesTamp in SQL Server: The problem seems the same, SAP recognize this as a date and time field.
Can any explain here the correct way for a delta implementation with SQL Server 2008? I would be very grateful.
Regards,

Hi Fernando
That is what I need to do.
Create a Model from an existing SQL Server database with the Import data Dictionary option , be able to modify tables structures, extended properties in the model, and then sync those changes with the database.
So far I can't import the extended properties with DM 3.1.1. If you find a way , please let me know.
Thanks,
Jorge

"Delta" Extraction with Datasource 0FI_TV_01

Hi,
Because the Datasource 0FI_TV_01 doesn't allow delta extraction I would like to know what is the estrategy to get data from ECC without have to always extract full data. Does anybody have some experience with this DS ?
Thanks in advance.
Denny.

Hi
Check in
http://help.sap.com/bp_biv235/BI_EN/BBLibrary/documentation/D17_BB_ConfigGuide_EN_DE.doc
Re: Standard extractor
Thanks

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 .

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

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.

Error while doing DELTA Extraction

Hi BW Experts,
In my R/3, I have a generic data source ZBUT_VW.
It receives data from a View which is created based on couple tables.
When I do full load to the corresponding ODS, it is successful.
But after that I delete the ODS and created CUBE with DELTA
I have Initialized delta.
When I do DELTA extraction, it fails.
The error
The ALE inbox of the SAP BW is identical to the ALE outbox of the source system
and/or
the maximum wait time for this request has not yet run out
and/or
the batch job in the source system has not yet ended.
I delete the initialization load and trying to do DELTA extraction again and it Fails With the same error
Please let me know how can I resolve this problem.
URGENT
gaurav

I dont think it is possible to have to additive delta with creation date.
Try a full load to cube to check if the extractor is working.

Error while doing DELTA Extraction (generic data source)

Hi BW Experts,
In my R/3, I have a generic data source ZBUT_VW.
It receives data from a View which is created based on couple tables.
When I do full load to the corresponding ODS, it is successful.
But after that I delete the ODS and created CUBE with DELTA
I have Initialized delta.
When I do DELTA extraction, it fails.
The error The ALE inbox of the SAP BW is identical to the ALE outbox of the source system
and/or
the maximum wait time for this request has not yet run out
and/or
the batch job in the source system has not yet ended.
I delete the initialization load and trying to do DELTA extraction again and it Fails.
With the same error
Please let me know how can I resolve this problem.
URGENT
gaurav

I dont think it is possible to have to additive delta with creation date.
Try a full load to cube to check if the extractor is working.

Processing overdue error during delta extraction from datasource 0CO_OM_CCA

Hi,
I'm getting "Processing overdue error" in BW while extracting delta from datasource 0CO_OM_CCA_9. all other extraction jobs from R3 -> BW are successful. Even Delta init on this datasource is successful & problem is only with delta package.
I appreciate if someone could provide information based on the following error details on this issue.
here are the extraction steps we followed.
Full load of fiscal years 2006 & 2007 Into transactional cube.
load budget data into transactional cube.
compression of the cube with "0 elimination"
Delta Initialization with fiscal period selections 1/2008 to 12/9999
all the above steps were successful.
and when delta package is scheduled, we are getting following errors.
BW system log
BW Monitoring job is turning red with following message.
Technical : Processing is overdue
Processing Step : Call to BW
Sending packages from OLTP to BW lead to errors
Diagnosis
No IDocs could be sent to the SAP BW using RFC.
System response
There are IDocs in the source system ALE outbox that did not arrive in
the ALE inbox of the SAP BW.
Further analysis:
Check the TRFC log.
You can get to this log using the wizard or the menu path "Environment -> Transact. RFC -> In source system".
Removing errors:
If the TRFC is incorrect, check whether the source system is completely
connected to the SAP BW. Check especially the authorizations of the
background user in the source system.
R3 Job Log
Even after BW job turns to red, R3 job continues to run for 2 hours and
eventually gets cancelled with an ABAP dump & here is the log.
Job
started
Step 001 started (program SBIE0001, variant &0000000110473, user ID
BWREMOTE) DATASOURCE = 0CO_OM_CCA_9
Current Values for Selected Profile Parameters
abap/heap_area_nondia.........2000000000 *
abap/heap_area_total..........2000000000 *
abap/heaplimit................20000000 *
zcsa/installed_languages......EDJIM13 *
zcsa/system_language..........E *
ztta/max_memreq_MB...........2047 *
ztta/roll_area................6500000 *
ztta/roll_extension...........2000000000 *
ABAP/4 processor: SYSTEM_CANCELED
Job cancelled
Thanks,
Hari Immadi
http://immadi.com
SEM BW Analyst

Hi Hari,
We were recently having similar problems with the delta for CCA_9. And activating index 4 on COEP resolved our issues.
Yes, by default there is a 2 hour safety interval for the CCA_9 DataSource. You could run this extractor hourly but at the time of extraction you will only be pulling postings through 2 hours prior to extraction time. This can be changed for testing purposes but SAP strongly discourages changing this interval in a production environment. SAP does provide an alternative described in OSS note 553561. You may check out this note to see if it would work for your scenario.
Regards,
Todd

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 <i>unmarked</i>...)
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.

Error in Extraction with Generic Datasource via Function Module

Dear Gurus,
Iam working for BI-HR module.We are extracting data with generic data source via function module. The client some more extra fields in already existing DS. So we made a copy of that Function module and tried to create new generic DS, we got error while extraction like "Error occured during the extraction process". Can you please help in resolving this issue, your valuable suggestion would be highly appreciated.
Thanks and regards
Arun S

Hi,
Which structure are you using??
Are you using the same old structure for this function module as well.
Have you enhanced the structure with new required fields.
New extrac fields needs to be added to existing structure if you are using the same or create a new one and make sure that you have all the fields in the structure which you are going to use in the data source.
You need to take care for the append as well and the issue could be in the code as well.
Make sure you have written the proper code and just for the new fields done an append
Thanks
Ajeet

Error in LO Extraction with BI7 .

Hi All,
Can anyone suggest me as to how to proceed with LO extraction with Queued Delta method. do we need to activate the Queue manually to work with Delta in LBWQ , I am unable to get the Init load running. I have filled up the setup tables aswell..
Thanks,
Krish..
Points are awarded for a solution.

Hi,
1) Stop all your R/3 users to stop the creation or changing the records in case your R/3 system is PROD
2) set the update mode is Queue delta in LBWE
3) Fill the setup table
4) Create and execute the info package with delta init
5) Schedule the collective run from Tcode LBWE
6) Create and execute the info package with delta load.
With rgds,
Anil Kumar Sharma .P

Installing InDesign CC 2014 on Windows 7 fails with error EX11 (error extracting to temporary folder).

@

Hi Jeff,
I finally resolved the problem. I was trying to install CC 2014 on a 32 Bit system not being aware that CC 2014 is 64 bit only!
Thanks for your help
Jo
Am 24.07.2014 um 19:13 schrieb Jeff A Wright <[email protected]>:
Installing InDesign CC 2014 on Windows 7 fails with error EX11 (error extracting to temporary folder).
created by Jeff A Wright in Creative Cloud Download & Install - View the full discussion
Jolauterbach the error indicates that your User account is not able to properly write to the temporary directory. Please make sure you have sufficient disk space and proper rights to modify the temporary directory.
Please note that the Adobe Forums do not accept email attachments. If you want to embed a screen image in your message please visit the thread in the forum to embed the image at https://forums.adobe.com/message/6580278#6580278
Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page:
To unsubscribe from this thread, please visit the message page at . In the Actions box on the right, click the Stop Email Notifications link.
Start a new discussion in Creative Cloud Download & Install by email or at Adobe Community
For more information about maintaining your forum email notifications please go to http://forums.adobe.com/thread/416458?tstart=0.

Error in Delta extraction of Material using MDM_CLNT_EXTR

Hi All ,
I am facing the following error while doing the delta extraction for material by using MDM_CLNT_EXTR.
ABAP/4 processor: MESSAGE_TYPE_UNKNOWN
I used MATERIAL_EXTRACT stucture, and successfully run the intial load.
Any help will be appriciated
BR
Syam

Hi Syam,
Just check whether the target system defined in XI and the extraction object that you are selecting are in sync.
Such error is possible when there is a conflict in the same.
You can also refer to the below link.
Delta Extraction Using MDM_CLNT_EXTR (Urgent)
Hope it helps.
Thanks,
Minaz
Edited by: Minaz Kathawala on Sep 30, 2008 4:14 PM

Delta extraction with errors

Similar Messages

Maybe you are looking for