ODP Extractor failing in Delta Mode

Hi, We are calling an extractor from ECC (ZBW_DMORDERS_BI) using SAP Data Services. Extractor was working fine for last 1 year but suddenly on 31 Mar it started failing. We checked with SAP BASIS team and nothing changed on that day. When I reimport Extractor and select Query mode then it works fine. When I reimport using CDC ( with out selecting any field as it was previously) then again ift fails. When we execute ABAP program RODPS_REPL_TEST in PROD then it works fine in DELTA and FULL mode. When we try to connect/run to PROD from QA SAP Data Services then also it fails.
We get below error on failure.
5220 7500 VAL-030977 4/3/2015 1:40:54 PM |Data flow ECC_DM_ORDERS_STAGE_DF|Reader Query_1-Mapping1
5220 7500 VAL-030977 4/3/2015 1:40:54 PM ODP source returned error: <E: MESSAGE - Error during delta extraction: DataSource ZBW_DMORDERS_BI. MESSAGE_V1 -
5220 7500 VAL-030977 4/3/2015 1:40:54 PM ZBW_DMORDERS_BI. I: MESSAGE - START_EXTRACTION ZBW_DMORDERS_BI. MESSAGE_V1 - START_EXTRACTION. MESSAGE_V2 - ZBW_DMORDERS_BI. I:
5220 7500 VAL-030977 4/3/2015 1:40:54 PM MESSAGE - INIT_PHASE ZBW_DMORDERS_BI. MESSAGE_V1 - INIT_PHASE. MESSAGE_V2 - ZBW_DMORDERS_BI.>.
Any idea what to try next?
Thanks,
Kalpesh

https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/67efb9bb-0601-0010-f7a2-b582e94bcf8a
No reference here either.
my conclusion that without using pseudo deltas, ie adding a field called delta mode, to the structure
and programming over the simple interface with a extra field
or
build a full F1 complex datasource definition tool,
there is no good standard solution.
Im still interested if anyone has a good approach to this.
regards
phil

Similar Messages

Custom Extractor FM with Delta mode

I have looked a few blogs that dont seem to address the whole picture.
the online help looks to be wrong?
http://help.sap.com/saphelp_nw70/helpdata/en/3f/548c9ec754ee4d90188a4f108e0121/frameset.htm
Im trying to set up an FM to do generic extraction.
Declare Datasource in RSo2. With Generic delta... all looks BUT
RSa3 can call th FM.
Seems the ROOSOURCE entry was with type F2.
If I copied a "proper" generic delta with complex interface and not the simple interface,
the entry in roosurce looks wrong to me.
What is the normal way to maintain the data source so that generic extraction works and can be tested in RSa3.
I also found this blog:
/people/siegfried.szameitat/blog/2005/09/29/generic-extraction-via-function-module
again the issue of deltas is over looked.
The demo function is RSA3_GEN_GET_DATA
BUT when create a dat source with rso2, the function interface used to call teh function
matches function RSAX_BIW_GET_DATA_SIMPLE
and not RSA3_GEN_GET_DATA.
The helpd refers to delta mode, but the interfae does NOT have the upmode flag.
Am i missing something or is this a whole in the RSo2 process.
Custom FM based extractors CAN NOT be called with delta mode.
surely someone knows what the trick is here ?
Cheers
Phil.
Edited by: Phil Soady on Aug 25, 2009 7:00 AM

https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/67efb9bb-0601-0010-f7a2-b582e94bcf8a
No reference here either.
my conclusion that without using pseudo deltas, ie adding a field called delta mode, to the structure
and programming over the simple interface with a extra field
or
build a full F1 complex datasource definition tool,
there is no good standard solution.
Im still interested if anyone has a good approach to this.
regards
phil

Master Data loading got failed: error "Update mode R is not supported by th

Hello Experts,
I use to load master data for 0Customer_Attr though daily process chain, it was running successfully.
For last 2 days master data loading for 0Customer_Attr got failed and it gives following error message:
"Update mode R is not supported by the extraction API"
Can anyone tell me what is that error for? how to resolve this issue?
Regards,
Nirav

Hi
Update mode R error will come in the below case
You are running a delta (for master data) which afils due to some error. to resolve that error, you make the load red and try to repeat the load.
This time the load will fail with update mode R.
As repeat delta is not supported.
So, now, the only thing you can do is to reinit the delta(as told in above posts) and then you can proceed. The earlier problem has nothing to do with update mode R.
example your fiorst delta failed with replication issue.
only replicating and repeaing will not solve the update mode R.
you will have to do both replication of the data source and re-int for the update mode R.
One more thing I would like to add is.
If the the delat which failed with error the first time(not update mode R), then
you have to do init with data transfer
if it failed without picking any records,
then do init without data transfer.
Hope this helps
Regards
Shilpa
Edited by: Shilpa Vinayak on Oct 14, 2008 12:48 PM

0WBS_ELEMT_ATTR Master Data - Delta Mode extraction

Hi experts,
I am trying to test the Delta mechanism for Master Data on 0WBS_ELEMT_ATTR but have a query. Basically, i have set my extractor to Delta mode. then did an INITload - which pulled thought all records. I then made a change in ECC6 to one WBS Element. In BI, i ran the Delta package expecting only the 1 record i amended in source system. However, I got 10 records. Upon further investigation, these additional 9 records are all records which sit within the same hierarchy of the 'amended' WBS element. So, it's pulling through all those records also. I only want 1 record in my Delta load if i make 1 change - Have i missed something or is this normal activity for WBS_ELEMT_ATTR extractor in delta mode?
Thanks in advance.
Munaf.

HI,
Can you check the Log of changes for those extra WBS element in R3 ie whether some other one has changed those WBS element in R3 or the change you made is available in other WBS element also in R3 on the same time and tell us.
What is the change you made in WBS element ie which field in WBS element you changed in R3.
Thanks,
Arun

Delta modes(F,A,D,E)

Hi experts,
This is Rekha, can u plz explain me ,wt is meant by delta modes(F,A,D,E), wen they r used..
wt i the actually purpose of it.....
plz.. plz.... i need a clear explanation..
points assured**

Hi ,
Delta Types
A => User ALE
F => Flat File delta
D => Application Determine delta
E => Extractor determine delta
D, E => Used for transaction data .
D => MM , SD , PP , FI , LO .
Doc change in appl cause a delta queue change via V3 collective run.
E => LIS . FI-SL , CO-PA
If Appl Determine Delta :
The application write delta to queue on transaction .
If Extractor Determine delta:
The extractor program figures ou the chages . Most extractors delendent delta are based on Pointers .
Renjith Kumar

CONVERT_TO_LOCAL_CURRENCY currency conversion errors in Delta mode

Hello,
I have been working with SAP via customer messages for a month now with no resolution. As many of you have experienced, the SAP Level 1 support is pretty useless so I would like to check here to see if I can get some help.
I found a thread where another user has had the exact same problem as I have.
Problem: Exchange rate in Update rules with DELTA mode
However, there was no answer given to him. So, if anyone can help, I appreciate it. Here's the problem:
When a record comes through 2LIS_13_VDITM (for example), it had a document currency of EUR, a local currency of PLN and a statistical currency of USD. The first time the record comes through, it comes through just fine. The exchange rate from EUR to PLN is 3.533. The statistical currency value is calculated by taking the document currency value and multiplying it by the exchange rate from EUR to PLN to get the local currency. Then, this local currency is converted to USD by multiplying itself by the PLN to USD exchange rate of 1.519.
These are the exchange rates that are coming through as key figures on the transaction data. The problem is when a delta occurs. The data goes into the ODS and then once the update rules to the cube get it, the signs are backwards on the exchange rates. This makes sense so that the exchange rate key figures will cancel themselves out, but the SAP code says to calculate the local currency, it must first take the document currency and divide by the exchange rate. It should still be multiplying because the exchange rate from EUR to PLN is still 3.533. The negative on the key figure that is being zeroed out tells the code to divide though.
You cannot simply set the reversal indicator because the values that do come through ok would then be erraneous as the previous poster who had the same issue encountered. This is really causing some bad data for us. This is SAP delivered code. Any help would be appreciated.
Thanks,
Brent

hi,
chk out various application currency conversion links
Need Urgent Help on Currency Conversion Routine
Currency conversion using transformation rule
http://help.sap.com/saphelp_nw04/helpdata/en/bc/058f4073b2f30ee10000000a155106/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/16/088f4073b2f30ee10000000a155106/frameset.htm
Ramesh

Notification classification extractor not trigger delta

I am facing the same .we have created custom data source for Notification classification using notification master data extractor(0NOTIFICATN_ATTR) but delta is not trigger for any changes in the notification line items..

Hi Madhu,
In SAP standard, the DataSource 0NOTIFICATN_ATTR is not DELTA compatible.
Please refer to online documentation below, only a complete upload is
available:
http://help.sap.com/saphelp_nw70/helpdata/en/08/b388017dbff7479cc07f0249
0d60d8/frameset.htm
Thanks,
Vimal

Data load error in Delta mode

Hi,
I have a DSO as an infoprovider and in a process chain I am loading data in delta mode into it and then transforming it in the next step into an infocube.
Everything was ok until I got an error in request id 1571 and process chain is finished with error. After this request I have request ids 1624, 1682, 1802 and 1854. The QM status and Technical status for these four requests are ok. I spot an invalid character is source of error. How should I fix it in PSA? As you know for editting data into PSA I have to delete it from target infoprovider and I don't want to do this. Is there any other solution to fix a invalid character in this situation?
By the way, is it possible to attach a screenshot of error to message in sdn forums?
Regards,

What is the source for this DSO from which you are loading deltas?
If the request number 1571 is the latest in the DSo you can just directly delete the request 1571 and edit the data in PSA.
If not if you have the rest of the 4 request on the top of the request 1571 and they are activated then you need to delete the complete 5 request and reload them all.
If the top 4 requests are not activated you can delete the single request 1571 and edit the data and proceed further.
To attach the screen shot directly not possible, just upload the error screen shot in the private URL and paste that URL .
Edited by: prashanthk on Nov 15, 2010 11:49 AM

Problem: Exchange rate in Update rules with DELTA mode

Hi experts,
During the loading since the ODS13BIL towards the CUBE, I use in the update rule the function
"CONVERT_TO_LOCAL_CURRENCY" to convert a currency.
The loading mode is DELTA.
If I modify an invoice in the system source (R/3) for example: "change on" (0CH_ON), during the loading delta since the ODS towards the cube, the exchange rate is reversed (sign), which implies that the values of the ratios during the conversion with the function module " CONVERT_TO_LOCAL_CURRENCY" are false.
How could I resolve this problem?
Example:
1-First load:
R/3:
Key figure 1 :100
Exchange Rate :-1,2
Document currency :USD
Local currency :EUR
Change on :00.00.0000
ODS13BIL:
Key figure 1 :100
Exchange Rate :-1,2
Document currency :USD
Local currency :EUR
Change on :#
CUBE:
Key figure 1 :100/1,2
Currency :EUR
2-Seconde load:
R/3:
Key figure 1 :100
Exchange Rate :-1,2
Document currency :USD
Local currency :EUR
Change on :06/01/2006
ODS13BIL:
Key figure 1 :100
Exchange Rate :-1,2
Document currency :USD
Local currency :EUR
Change on :06/01/2006
CUBE:
Key figure 1 :100/1,2
Currency :EUR
and
Key figure 1 :-100*1,2 <-- False
Currency :EUR
Thank you for your precious help.

Hello,
Thank you for your answer but that still not works: Give erroneous data is corrected but the data which are not erroneous become erroneous.
I think that if I manage to return the field "Exchange misses" (0EXCHG_RATE) nonmodifiable by the DELTA mode, I cross that will resolve the problem.
With what is used following fields in the definition of the ODS, and it is what impacts it on the existing data: "Non cumulative value" et "Cumulative value"
thanks a lot.

Infospoke DELTA Mode

Hi All
we are using an infospoke to update data from an Infocube to ext DB table
The infocube is having daily delta requests and is exported thru this infospoke to a db table
the infospoke extraction mode is FULL mode and now i have a requirement to change it to DELTA mode
how to change Infospoke extraction mode to Delta from FULL
any pre-requisites or settings to be done here?
appreciate your early reply
thank you

Hello All,
Kindly help me in updating the settings..
we are using an infospoke in production system, which updates the data from BW to external DB tables
the extraction mode is full mode, now i need to change the mode to "Delta"
are there any settings to make or follow before changing the mode
inputs are rewarded
thank you

Difference between FIL0 and FIL1 delta modes

Say for eg I have loaded a DSO from a flat file with Full Upload. Now I am making changes only to the key figures and not to the characteristcs in the flat file. So is it my responsibility to choose FIL0 as the Delta mode in the DataSource (and then upload the data)? And if the flat file has changes to both key figures and characteristics, do I then again go into the DataSource and change it to FIL1 before uploading the data again
What I want to know especially is that is this setting dependant on the type fo file being uploaded
Type1 - Only changes to key figures are recorded. (In which case use FIL0)
Type2 - Changes to both key figures and characteristics are recorded. (In which case use FIL1)

Hi:
The main difference between the FIL0 and FIL1 Delta Procedures is explained below.
- FIL0 is used to "Overwrite" data, so your Data Targets could be either DSOs or Master Data.
- FIL1 is used to "Add" data, so your Data Targets could be either DSOs or InfoCubes.
Since your Data Target is a DSO you could use either the FIL0 or FIL1 Delta Procedure, but you should take into account the settings you have on the Update Rules/Transformation Rules to update each Key Figure on the DSO ("Overwrite", "Addition").
For more information take a look a the links below:
"Using Generic BW Deltas"
http://help.sap.com/saphelp_nw73/helpdata/en/cc/3c3473cd93460b9ed506e7f25cd3a7/content.htm
"Settings for Delta Transfer"
http://help.sap.com/saphelp_nw73/helpdata/en/4a/1d039e24521977e10000000a42189c/content.htm
Regards,
Francisco Milán.

SAP ECC 6.0 extractor 0FI_GL_4 -extracting GL data in delta mode into MSSQL

Hi,
Currently we are having the following need. We have to build delta interface from SAP ECC into MSSQL for G/L data. If possible, we would like to use for this standard ECC extractor: 0FI_GL_4. As far as I know this extractor is dedicated for SAP BW, but can we apply it for MSSQL? Does anyone has any experience with similar task? Any help will be appreciated.
Regards,
Marek

Hi,
I'm using the data source 0SEM_BCS_10.
I have created my staging cube similar to my Totals cube (0BCS_C11).
I'm stuck in creating update rules for this staging cube, particularly with respect to the follwing feilds:
1) Posting level
Pls let me know how to update this.
Also, help me understand in general, how to write update rules to feilds which exist only in BCS.
2) F Yr of the first acquisition posted
3) Period in which first acq was posted
(Mapping for these will be constant values (actual dates) - correct me if wrong)
4) Mov Type
I guess we need to just map this with the transaction type in ECC.
Many Thanks,
Kumar

Extractor not picking delta data

Hi All ,
I have a very peculiar problem with extractor 2LIS_02_SCN .
The Delta data's are not getting captured in BW as well as in the RSA3 .This is happening for few PO's .
I checked the extractor debugger as well (in RSA3) , but it shows only 1 record which is already there in BW , but the new delta data is not available in RSA3 as well .Deltas are running fine everyday . I also checked in the underlying table EKES for the Vendor Confirmations , I can see 2 records ie the previous as well as the changed records . Now my Problem is why the extractor is not pulling the new changed record . We have Update Mode in R/3 as Direct Delta
Note : There were no filling of set tables done since long time. set up tables are working fine .
Could anybody help me in this issue .
Thanks & Regards
Zeenath Syeda

Hi sidhartha,
SAP says :
To improve performance, this DataSource contains no information about scheduling agreements. This also applies to returns items, service items, and limit items.
So check whether your records(which are not extracted) are belongs to any one of above types.
With rgds,
Anil Kumar Sharma .P
Message was edited by: Anil Kumar Sharma

Setup table Administration with Direct Delta mode

Hi guys,
I have a direct delta as update mode for my 2LIS_11_VAITM extractor in R/3.
I'd like to know if I have to manage the relative setup table (MC11VA0ITMSETUP) with this update mode also.
For instance, If I delete an ODS content and restart a new INIT on BW system, do I need to delete and then to fill the setup table?
In general, Do I need always to menage the setup table with each kind of update mode (direct delta, queued delta and V3 update)?
if you know the answers, please reply me direcly without insert link.
Many Thanks.

yes, you do....the initial loads for lo datasources are completely independent of the delta loads and hence of the delta method...
/people/sap.user72/blog/2005/01/19/logistic-cockpit-delta-mechanism--episode-three-the-new-update-methods
M.

Extension of LIS extractor - possible to delta enable field from Z-table?

Hi Experts
We have to get data from a date field in a custom Z-table (delivery related) in R/3 to BW.
We would like to get the date by extending a delivery LIS extractor with a new field and make some ABAP to lookup the correct value in the custom Z-table.
A requirement is though that if the date in Z-table is changed then we need to get the update value to BW. Therefore, we need to delta enable the new field in the append structure - but that ain't possible is it?
Alternatively will we have to make a new DataSource based on the custom Z-table and somekind of full load (with a fake delta).
Thanks.
Kind regards,
Torben

Torben,
If your custom Z-table does not contain too much data and doesn't change too often it might be an option to turn on DB logging (Technical settings -> Log data changes). Do not do this for large tables containing transactional data as the logs will consume a lot of diskspace!
Each insert/mod/deletion will be logged and in in a user-exit you can use FM DBLOG_READ_WITH_STATISTIC to check if something has changed and then append the corresponding data to your data package.
Grtx!
Marco

ODP Extractor failing in Delta Mode

Similar Messages

Maybe you are looking for