Delta error in ods

hi experts,
if delta load fails b/n ods &infocube
how to rectify that , for that what is the procedure
when we are loading the data ods to infocube how to choose the
keyfields?is it equal to dimensions
thanks in advance
venu

Hi,
It's the same procedure which we follow for the delta from R/3 to the Bw targets.
The only thing is if you can correct it in the PSA then you can correct it there and then load it from there.
Or you can delete the failed delta request from the cube and relaod the delta
it will give you warning that you are repeating the delta.the new delta will bring the records from the failed delta as well as the records from the new delta if any.
Th key fields of the ODS are not equivalent to dimension.
Dimension are for the logical groupings of the objects and are decided in such a way that the size of dimension table should bve as small as possible.
Where as the key fields of the ODS are like the keys of the table if you want to identify a particular value with respect to a char or combination of char.just imagine it as a table with keys.
hope it clears
Thanks

Similar Messages

Error reading 'ods' passwd from wallet!!!!!

I did:
c:\>oidmon connect=hahldap start
(No errors).
C:\>oidctl connect=hahldap server=oidldapd host=192.168.1.100 instance=1 start
gsluwpwaGetWalletPasswd: Opening 2 file failed with error 11005
[gslusw]:Error reading 'ods' passwd from wallet
[gsdsiConnect]:Error reading 'ods' passwd from wallet
Could not connect to the Database.
What could be the reason??? I am running on WinXP Is it the problem?
Installation went fine for both Metadata repository and for the Oracle Internet Directory.
Note: I couldn't find the service OracleDirectoryService_xxx at all, does that mean the installation is incorrect?
thanks.

Any resolution here :
My listener is up
My DB is up and accessible, but when issuing the following command I get following error .
Any chance you can offer some advice ?
oidmon start
2006/03/01:12:58:32 * gsluwpwaGetWalletPasswd: Opening 3 file failed with error 11005
2006/03/01:12:58:32 * [gslusw]:Error reading 'ods' passwd from wallet
2006/03/01:12:58:32 * [gsdsiConnect]:Error reading 'ods' passwd from wallet
2006/03/01:12:58:32 * [oidmon]: Unable to connect to database,
will retry again after 20 sec
Im on Unix

Delta loading from ODS to InfoCube

Hai
Im extracting the data from the custom table into ODS and doing full load everytime for loading delta.
how can load the only delta from the ODS to InfoCube. what are the setting for this one
pls let me know
kumar

Hai Ravi...
Load the Data From ODS to InfoCube:
Clck as right Click in the Specified ODS.....
Select the Option " Update ODS Data in Data Target "......
Then You able to load the Data to any type of DataTarget's(either ODS, InfoCube)
removed...
BalajeeKannan

Error when doing a delta to an ODS without Init

Hello All.
We have a flow for 0FI_GL_4 done an active with delta loads.
Now we have created anew flow for that ODS and inlcude the old delta loads to the new Flow, but we are getting error RSM1 147.
Does anyone had this problem before?
Thanks and best regards
Alfonso.

Hello All.
First thanks for the help.
Our scenario is as follows. We have an ODS with it´s delta initialization and delta running. Then we have created a new ODS and we don´t want to stop the previos delta initialization, because that will mean to reload all the data.
Any ideas?
thanks,
Alfonso.

Error in loading delta request to ODS

Dear All,
i am not being able to load data from ODS to another ODS and Cube. It is saying "the last delta update was incorrect therefore, no new delta update possible".
i guess i need to delete the old delta update request.
can you all help me. its a bit urgent.

i have done all the possible steps as guided by you all. i am still not being able to load it.
i will tel you my process flow:
i have a process chain which is loading data to source ODS and subsequently to another ODS and Cube.
But there was an errror in loading the data to source ODS today. So i deleted the request from the source ODS and from the other ODS and CUBE.
Now i loaded data to source ODS successfuly. and tried loading data from source ODS to other ODS and CUBE.
But the request ended with errors. so i deleted the request again from target ODS and CUBE.
Now when i m again loading data to target ODS and Cube then it is saying
1) "Delta request REQU_CGSYNH9QR02W5WZOQBDPTHP99 is incorrect in the monitor"
2)A repeat needs to be requested
3)Data target 0CRM_C04 still includes delta request REQU_CGSYNH9QR02W5WZOQBDPTHP99
4)Data target 0CRM_OPMO still includes delta request REQU_CGSYNH9QR02W5WZOQBDPTHP99
5)If the repeat is now loaded, then after the load
6)there could be duplicate data in the data targets
7)Request the repeat?
CONTINUE CANCEL
what do i do now?

Delta Status in ODS is incorrect

Hi,
I am loading a delta load to an ODS. Today its activation got failed giving message "FAULTY STATUS FOUND FOR DSO, ACTIVATION TERMINATED".
I tried to activate it manually but it is failing giving the same error.
Also I tried t repeat delta by deleting this red request (by making it RED in monitor-->status tab and its QM statu(which is already REd) but this deletion job is also failing giving the same error.
It is also giving messgae"The request is already PARTIALLY activated.No further changes to QM action".
I am unable to find out how to correct it? please help.
Thanks,
Preet

I could delete the red request finally from 4 tables, namely:
1. RSICCONT
2. RSMONICDP
3. RSODSACTREQ
4. RSODSACTUPDTYPE
It got deleted successfully. Then I reconstructed it. But again the problem occured saying 10 duplicate requests found. Cannot activate. Its activation failed after sometime giving message"Partially activated , cannot change the QM status further".
I dont know how to tackle with this now.I have checked in PSA also, there is no bad records present.
Please help.

Delta error in PRD

Hi
We are extracting the deltas into ODS from R/3. There was an error in extraction and activation into ODS didnt take place. The error is of invalid characteristics. The status is RED in monitor where as in data target--> manage the request is in green color but not active. I clicked on activate button and tried to activate manually but it was not getting activated.
I did the following steps.
1. In monitor screen, i converted the request into RED status.
2. In data target, i deleted the request.
3. Went to PSA, Manually changed the record and saved it. AFter changing the record the status in PSA is RED.
4. From PSA i scheduled the upload into data target immedialtely.
5. AFter scheduling, i could see the green request in datatarget with reporting icon. But the strange thing is in monitor screen the status [total] is in RED status and Technical is in GREEN status.
Q1. Now will delta takes place in next schedule, if tis in RED status?
REgards
Rak

Hi
ABY: If i repeat the delta, i will get the same error. Now i know what the error is and fixed up in PSA. We informed client and told them that it should not be done again.
Singh: After editing the record in PSA. i scheduled the upload and upload went fine in ODS. As i mentioned in the earlier thread.
In monitor screen the status is in RED where as in data target the request is in green status.
The editied record in PSA is In GREEN status,,,whereas total status is in RED.
What heppens if i turn that status into GREEN now? As i got the delta records into datatarget now.
Regards
Rak

Load error in ODS

Hi all,
We are doing unit testing.For this i am trying to load the data psa then into ODS.There are three info packages we have created for full,init and delata.One week back we have loaded the data using delta and it was successful.
Now to day i am trying to load the data using it is giving 0 records.
When i am trying to load the data using full it is giving the following error
(Full 2.146 has overlapping selections with init. 0000002056 : No updates into ODS ZXXX )
Please help me out to find the solution for this.
Thanks to all

Hi,
You have to amke your FULL infopackage...as.."Repair full request".
Go to that full infopackage-in menu-Schedule-> Repair full request.
Save.
check out this...
ODS Object switch from Delta to Full Upload
Hope i m clear.
Regards,
San!
Message was edited by: San!

Activation Error in ODS - Record mode 0 unknown (data record REQU_4DPGJKCKN

I created a generic extractor in R3 with a generic delta. In BW, my delta init loads with no errors but when I activate the data in the ODS, I get the activation error.
"Record mode 0 unknown (data record REQU_4DPQ31IK7WM9OTK26S5JMJ6LM/000001/"
I searched SDN but didn't found anything, and I searched help but only found general information about 0recordmode.
Can someone provide a solution and/or some more detailed information about the error message?
Thanks

Hello,
When you have created the InfoSource for the generic datasource, have you added field 0RECORDMODE to the InfoSource? When loading data to a ODS, 0RECORDMODE is essential.
The InfoObject is usually mapped to ROCANCEL (Indicator: Cancel Data Record) field of the extractor. This field is usually present in Standard extractors. But even if the field is not present in your extractor, add it to InfoSource Communication structure and leave it unmapped in transfer rules.
I think this might solve the problem.
Regards,
Pankaj

Regarding error in ODS' activation.

Dear All,
Could you help me to solve this case please..
I've problem like this,, so when i'm trying to load data from CRM i get the strange error.
1. If i get into the monitoring (icon)/tcode : RSRQ. The status is green.
2. BUT, If i manage the ODS (RSA1 - Manage ODS), the status there is red .
3. The error is like this:
Error when assigning SID: Action VAL_SID_CONVERT table ZTPROBDES.
What i've done for solving :
1. delete then reconstruct.
2. re-fetch data from PSA to ods.
But, the outcome is still same.
Btw, i'm using Delta & BI. 7.0. for it.
Could somebody here help me what to do ..
Tks a lot .
Regards,
Niel.

This error came due to master data porblem, that ODS required master data, that master data is not avalible.
procedure:
Delete that record from ODS new tabel and activate. Before doing this inform to further people
OR
Edit PSA data for ZTPROBDES infoobject(field) give some existing value (ie ZTPROBDES value already in master data)and note the which record ur chaning than reload to ODS before to this inform to next level person.
OR
This is the program for repair sid numbers(i.e it will asgin the temp. sid number to that)the try this RSDMD_CHECKPRG_ALL for repairing the SID numbers
i hope this will be help
Message was edited by:
Soma Venkateshwarlu

0FI_GL_10 can't delta :Errors occurred during the extraction.

hi,sdn!
i have 3 DataSources,
0FI_AA_11(FI-AA: Transactions),
0FI_AA_12(FI-AA: Posted Depreciations) and 0FI_GL_10(General Ledger: Leading Ledger Balances).
The initialize and full extraction is ok.
when i delta it in rsa3,the system tell me:Errors occurred during the extraction.
Is Append Structure result in this error?
i want to know the reason,thanks!

For summarization of line items by master record characteristics (such as cost center) during posting of ODS objects to InfoCubes, master data must already exist prior to extraction of transaction data. The following sequence must therefore be kept to during extraction:
0FI_GL_4
General Ledger: line items (if required)
0ASSET_ATTR_TEXT
Asset subnumber (flexible updating)
0ASSET_AFAB
Depreciation area real or derived
then the transaction data
0FI_AA_11
FIAA : transactions and / or
0FI_AA_12
Posted depreciations (period values)

Delta loading daily ods to cube

HI guys
delta not laoding to ods to cube.last laoding in ods 3 /06 .
when m try to loading m getting erorr
subseq. processing(messages) : errors ocuured
Activation of M records from DataStore object 0FIGL_O10 terminated ,
REquest REQU-D3k2lr788qjc4g9w7h8fwbnhk(2.130) has not or not c0rrctely updated;p
same msg showing in
other (messages ): errors occurred
Diagnosis
    Request REQU_D3K2IR788QJC4G9W7H8FWBNHK (2.130 ) for DataSource 0FI_GL_10
    from source system P02CLNT800 has the status green and a lesser SID (and
    is therefore older) than the request that you currently want to update
    into the DataStore object.
    This is not possible because the sequence of requests has to be
    followed.
    Delta- and init requests have to be updated to the DataStore object in
    the request sequence.
please advise on this
Regrds
patel

Patel,
Go to RSRQ. Give this request no. REQU_D3K2IR788QJC4G9W7H8FWBNHK. There you will find the message that this request has not been properly updated. You will find a button to update the request. Update this to the data target and activate. You will be thru this time.
Enjoy!!
Shambhu

Delta Error

Hi,
While loading delta, i got an error.
Record 3873 :InfoObject /BIC/ZWEMPF does not contain alpa-conforming value 092
Record 3874 :InfoObject /BIC/ZWEMPF does not contain alpa-conforming value 092
can anybody can explain what it means.
how to rectify this error.
delta was loaded into PSA but not loaded into ODS.

Hi Rajini,
This ios because the request which is being loaded from PSa to DSo contains some invalid data in the field mentined.
1)go to PSA right click - > manage.
2)select the request and click on display data.
3)go to the record numbers mentioned and check the field ZWEMPF of the records for invalid data.
4)correct this records. and save data.
5)delete the red request from DSO.
6)run the delta DTP again.
Hope this helps.
Cheers,
Srinath.

Delta load from ODS to cube failed - Data mismatch

Hi all
We have a scenario where the data flow is like
R/3 table - >dataSrc -- > pSA - >InfoSrc -> ODS ->Cube.
The cube has an additional field called "monthly version"
and since it is a history cube , it is supposed to hold data
snapshots of the all data in current cube for each month .
We are facing the problem that the Data for the current month
is there in the history ODS but not in the cube . In the ODS ->Manage->requests
tab i can see only 1 red request that too with 0 recs.
However ,In the cube -> manage-> reconstruction tab , i can see 2 Red request
with the current month date. Could these red requests be the reason for
data mismatch in ODS and cube .
Please guide as to how can i solve this problem .
thanks all
annie

Hi
Thanks for the reply.
Load to Cube is Delta and goes daily .
Load to ODS is a full on daily basis .
Can you help me how to sort this issue . I have to work directly in production env . so has to be safe and full proof .
Thanks
annie

Delta error in GE-Function Module

Hi ,
my GE-delta is based on UDATE ( chenged date) from CDHDR table.
i created datasource in RS02 and i defined delta based in UDATE with upper limit 1 day and lower limit is '0'..
i created FM based on RSAX_BIW_GEDATA_SIMPLE.
for full load it working fine.
i put some extra code for delta.
it is not take any records...
i dont know much ABAP.
plz tell me where is wrong in my code for delta..
code ...
FUNCTION ZXBWMM_INV_POT_ID.
""Local Interface:
*" IMPORTING
*" VALUE(I_REQUNR) TYPE SRSC_S_IF_SIMPLE-REQUNR
*" VALUE(I_DSOURCE) TYPE SRSC_S_IF_SIMPLE-DSOURCE OPTIONAL
*" VALUE(I_MAXSIZE) TYPE SRSC_S_IF_SIMPLE-MAXSIZE OPTIONAL
*" VALUE(I_INITFLAG) TYPE SRSC_S_IF_SIMPLE-INITFLAG OPTIONAL
*" VALUE(I_READ_ONLY) TYPE SRSC_S_IF_SIMPLE-READONLY OPTIONAL
*" VALUE(I_REMOTE_CALL) TYPE SBIWA_FLAG DEFAULT SBIWA_C_FLAG_OFF
*" TABLES
*" I_T_SELECT TYPE SRSC_S_IF_SIMPLE-T_SELECT OPTIONAL
*" I_T_FIELDS TYPE SRSC_S_IF_SIMPLE-T_FIELDS OPTIONAL
*" E_T_DATA STRUCTURE ZVSAIPID OPTIONAL
*" EXCEPTIONS
*" NO_MORE_DATA
*" ERROR_PASSED_TO_MESS_HANDLER
Example: DataSource for table SFLIGHT
TABLES: SFLIGHT.
TABLES: EBAN , CDPOS , CDHDR , ZVSAPR.
TYPES : BEGIN OF TY_OBJDATE ,
 OBJECTID TYPE CDHDR-OBJECTID,
 VALUE_NEW TYPE CDPOS-VALUE_NEW,
 VALUE_OLD TYPE CDPOS-VALUE_OLD,
 UDATE TYPE CDHDR-UDATE,
 MINBE TYPE MARC-MINBE,
 BSTMA TYPE MARC-BSTMA,
 WERKS TYPE MARC-WERKS,
 VERPR TYPE MBEW-VERPR,
 STPRS TYPE MBEW-STPRS,
 LBKUM TYPE MBEW-LBKUM,
 BUDAT TYPE MKPF-BUDAT,
 MBLNR TYPE MSEG-MBLNR,
 MENGE TYPE MSEG-MENGE,
 DMBTR TYPE MSEG-DMBTR,
 END OF TY_OBJDATE.
data : int_cdhdr type table of cdhdr with header line,
 int_cdpos type table of cdpos with HEADER LINE,
 INT_OBJDATE TYPE TABLE OF TY_OBJDATE WITH HEADER LINE.
 int_marc type table of marc with header line.
*DATA: int_pr1 TYPE TABLE OF ZVSAIPID WITH HEADER LINE.
DATA : BEGIN OF INT_MATNR OCCURS 10,
 MAtnr like mara-matnr,
 end of int_matnr.
DATA : BEGIN OF INT_MARC OCCURS 10,
 matnr like marc-matnr,
 MINBE like marC-mINBE,
 BSTMA LIKE Marc-bstma,
 WERKS LIKE MARC-WERKS,
 end of int_marc.
DATA : BEGIN OF INT_MBEW OCCURS 10,
 MATNR LIKE MBEW-MATNR,
 VERPR LIKE MBEW-VERPR,
 STPRS LIKE MBEW-STPRS,
 LBKUM LIKE MBEW-LBKUM,
 end of int_MBEW.
DATA : BEGIN OF INT_MKPF OCCURS 10,
 MBLNR LIKE MKPF-MBLNR,
 BUDAT LIKE MKPF-BUDAT,
 END OF INT_MKPF.
DATA : BEGIN OF INT_MSEG OCCURS 10,
 MATNR LIKE MSEG-MATNR,
 MBLNR LIKE MSEG-MBLNR,
 MENGE LIKE MSEG-MENGE,
 DMBTR LIKE MSEG-DMBTR,
 END OF INT_MSEG.
Auxiliary Selection criteria structure
DATA: L_S_SELECT TYPE SRSC_S_SELECT.
Maximum number of lines for DB table
STATICS: S_S_IF TYPE SRSC_S_IF_SIMPLE,
counter
 S_COUNTER_DATAPAKID LIKE SY-TABIX,
cursor
 S_CURSOR TYPE CURSOR.
Select ranges
RANGES: L_R_CARRID FOR SFLIGHT-CARRID,
 L_R_CONNID FOR SFLIGHT-CONNID.
RANGES : ra_OBJECTID FOR E_T_DATA-OBJECTID.
 RA_UDATE FOR E_T_DATA-UDATE.
Initialization mode (first call by SAPI) or data transfer mode
(following calls) ?
IF I_INITFLAG = SBIWA_C_FLAG_ON.
IF NOT G_FLAG_INTERFACE_INITIALIZED IS INITIAL.
IF 1 = 2. MESSAGE E008(R3). ENDIF.
LOG_WRITE 'E' "message type
'R3' "message class
'008' "message number
' ' "message variable 1
' '. "message variable 2
RAISE ERROR_PASSED_TO_MESS_HANDLER.
ENDIF.
Initialization: check input parameters
 buffer input parameters
 prepare data selection
Check DataSource validity
 CASE I_DSOURCE.
 WHEN 'ZOI_MM_INVENTORY_IPID'.
 WHEN OTHERS.
 IF 1 = 2. MESSAGE E009(R3). ENDIF.
this is a typical log call. Please write every error message like this
 LOG_WRITE 'E' "message type
 'R3' "message class
 '009' "message number
 I_DSOURCE "message variable 1
 ' '. "message variable 2
 RAISE ERROR_PASSED_TO_MESS_HANDLER.
 ENDCASE.
Check for supported update mode
CASE I_UPDMODE.
WHEN 'F'.
WHEN 'D'.
WHEN 'R'.
WHEN OTHERS.
IF 1 = 2. MESSAGE E011(R3). ENDIF.
LOG_WRITE 'E' "message type
'R3' "message class
'011' "message number
I_UPDMODE "message variable 1
' '. "message variable 2
RAISE ERROR_PASSED_TO_MESS_HANDLER.
ENDCASE.
READ TABLE I_T_SELECT INTO L_S_SELECT
WITH KEY FIELDNM = 'UDATE'.
 APPEND LINES OF I_T_SELECT TO S_S_IF-T_SELECT.
Fill parameter buffer for data extraction calls
 S_S_IF-REQUNR = I_REQUNR.
 S_S_IF-DSOURCE = I_DSOURCE.
 S_S_IF-MAXSIZE = I_MAXSIZE.
 G_S_INTERFACE-INITFLAG = I_INITFLAG.
 G_S_INTERFACE-UPDMODE = I_UPDMODE.
 G_S_INTERFACE-DATAPAKID = I_DATAPAKID.
 G_FLAG_INTERFACE_INITIALIZED = SBIWA_C_FLAG_ON.
Fill field list table for an optimized select statement
(in case that there is no 1:1 relation between InfoSource fields
and database table fields this may be far from beeing trivial)
 APPEND LINES OF I_T_FIELDS TO S_S_IF-T_FIELDS.
ELSE. "Initialization mode or data extraction ?
Data transfer: First Call OPEN CURSOR + FETCH
 Following Calls FETCH only
First data package -> OPEN CURSOR
LOOP AT S_S_IF-T_SELECT INTO L_S_SELECT
WHERE FIELDNM = 'UDATE'.
ENDLOOP
 IF S_COUNTER_DATAPAKID = 0.
Fill range tables BW will only pass down simple selection criteria
of the type SIGN = 'I' and OPTION = 'EQ' or OPTION = 'BT'.
 LOOP AT S_S_IF-T_SELECT INTO L_S_SELECT WHERE FIELDNM = 'CARRID'.
 MOVE-CORRESPONDING L_S_SELECT TO L_R_CARRID.
 APPEND L_R_CARRID.
 ENDLOOP.
 LOOP AT S_S_IF-T_SELECT INTO L_S_SELECT WHERE FIELDNM = 'CONNID'.
 MOVE-CORRESPONDING L_S_SELECT TO L_R_CONNID.
 APPEND L_R_CONNID.
 ENDLOOP.
Determine number of database records to be read per FETCH statement
from input parameter I_MAXSIZE. If there is a one to one relation
between DataSource table lines and database entries, this is trivial.
In other cases, it may be impossible and some estimated value has to
be determined.
 OPEN CURSOR WITH HOLD S_CURSOR FOR
 SELECT (S_S_IF-T_FIELDS) FROM SFLIGHT
 WHERE CARRID IN L_R_CARRID AND
 CONNID IN L_R_CONNID.
 IF L_S_SELECT-LOW = '' AND L_S_SELECT-HIGH = ''. "FULL or INIT
 OPEN CURSOR WITH HOLD S_CURSOR FOR
 select * from cdhdr where OBJECTCLAS = 'MATERIAL' AND TCODE = 'MM02'.
 ELSE. "DELTA
 OPEN CURSOR WITH HOLD G_CURSOR FOR
 select * from cdhdr where OBJECTCLAS = 'MATERIAL'
 AND TCODE = 'MM02'
 AND UDATE >= L_S_SELECT-LOW
 AND UDATE <= L_S_SELECT-HIGH.
 ENDIF.
 ENDIF.
 ENDIF.
 "First data package ?
 FETCH NEXT CURSOR S_CURSOR
 APPENDING TABLE int_cdhdr
 PACKAGE SIZE S_S_IF-MAXSIZE.
 into table int_cdhdr
 IF SY-SUBRC <> 0.
 CLOSE CURSOR S_CURSOR.
 RAISE NO_MORE_DATA.
 ENDIF.
 SELECT * FROM CDPOS INTO TABLE INT_CDPOS
 FOR ALL ENTRIES IN INT_CDHDR
 WHERE OBJECTID = INT_CDHDR-OBJECTID
 AND TABNAME = 'MARC'
 AND ( FNAME = 'BSTMA' OR FNAME = 'MINBE' ).
 LOOP AT int_cdpos.
 int_matnr-matnr = int_cdpos-objectid.
 APPEND int_matnr.
 ENDLOOP.
 SELECT matnr MINBE BSTMA WERKS FROM MARC INTO TABLE INT_marc
 FOR ALL ENTRIES IN int_matnr
 WHERE MATNR = INT_matnr-matnr.
 SELECT matnr VERPR STPRS LBKUM FROM MBEW INTO TABLE INT_MBEW
 FOR ALL ENTRIES IN int_matnr
 WHERE MATNR = INT_matnr-matnr.
 SELECT matnr MBLNR MENGE DMBTR FROM MSEG INTO TABLE INT_MSEG
 FOR ALL ENTRIES IN int_matnr
 WHERE MATNR = INT_matnr-matnr.
 LOOP AT int_MSEG.
 int_MKPF-MBLNR = int_MSEG-MBLNR.
 APPEND int_MKPF.
 ENDLOOP.
 SELECT MBLNR BUDAT FROM MKPF INTO TABLE INT_MKPF
 FOR ALL ENTRIES IN int_MKPF
 WHERE MBLNR = INT_MKPF-MBLNR.
*BREAK-POINT.
 LOOP AT INT_CDPOS.
 READ TABLE INT_CDHDR WITH KEY OBJECTID = INT_CDPOS-OBJECTID .
 IF SY-SUBRC = 0.
 INT_OBJDATE-OBJECTID = INT_CDPOS-OBJECTID.
 INT_OBJDATE-VALUE_NEW = INT_CDPOS-VALUE_NEW.
 INT_OBJDATE-VALUE_OLD = INT_CDPOS-VALUE_OLD.
 INT_OBJDATE-UDATE = INT_CDHDR-UDATE.
 READ TABLE INT_MARC WITH KEY MATNR = INT_CDPOS-OBJECTID .
 IF SY-SUBRC = 0.
 INT_OBJDATE-MINBE = INT_MARC-MINBE.
 INT_OBJDATE-BSTMA = INT_MARC-BSTMA.
 INT_OBJDATE-WERKS = INT_MARC-WERKS.
 ENDIF.
 READ TABLE INT_MBEW WITH KEY MATNR = INT_CDPOS-OBJECTID .
 IF SY-SUBRC = 0.
 INT_OBJDATE-VERPR = INT_MBEW-VERPR.
 INT_OBJDATE-STPRS = INT_MBEW-STPRS.
 INT_OBJDATE-LBKUM = INT_MBEW-LBKUM.
 ENDIF.
 READ TABLE INT_MSEG WITH KEY MATNR = INT_CDPOS-OBJECTID .
 IF SY-SUBRC = 0.
 INT_OBJDATE-MBLNR = INT_MSEG-MBLNR.
 INT_OBJDATE-MENGE = INT_MSEG-MENGE.
 INT_OBJDATE-DMBTR = INT_MSEG-DMBTR.
 ENDIF.
 READ TABLE INT_MKPF WITH KEY MBLNR = INT_MSEG-MBLNR .
 IF SY-SUBRC = 0.
 INT_OBJDATE-MBLNR = INT_MKPF-MBLNR.
 INT_OBJDATE-BUDAT = INT_MKPF-BUDAT.
 ENDIF.
 APPEND INT_OBJDATE.
 ENDIF.
 ENDLOOP.
*SELECT * FROM EBAN
 INTO CORRESPONDING FIELDS OF TABLE INT_PR1
 FOR ALL ENTRIES IN INT_OBJDATE
 WHERE BAnfn = int_objdate-objectid.
*ZZPRREL
 LOOP AT INT_OBJDATE.
 E_T_DATA-OBJECTID = INT_OBJDATE-OBJECTID.
 E_T_DATA-UDATE = INT_OBJDATE-UDATE.
 E_T_DATA-VALUE_NEW = INT_OBJDATE-VALUE_NEW.
 E_T_DATA-VALUE_OLD = INT_OBJDATE-VALUE_OLD.
 E_T_DATA-MINBE = INT_OBJDATE-MINBE.
 E_T_DATA-BSTMA = INT_OBJDATE-BSTMA.
 E_T_DATA-WERKS = INT_OBJDATE-WERKS.
 E_T_DATA-VERPR = INT_OBJDATE-VERPR.
 E_T_DATA-STPRS = INT_OBJDATE-STPRS.
 E_T_DATA-LBKUM = INT_OBJDATE-LBKUM.
 E_T_DATA-MBLNR = INT_OBJDATE-MBLNR.
 E_T_DATA-MENGE = INT_OBJDATE-MENGE.
 E_T_DATA-DMBTR = INT_OBJDATE-DMBTR.
 E_T_DATA-BUDAT = INT_OBJDATE-BUDAT.
 APPEND E_T_DATA.
 CLEAR E_T_DATA.
 ENDLOOP.
Fetch records into interface table.
named E_T_'Name of extract structure'.
 S_COUNTER_DATAPAKID = S_COUNTER_DATAPAKID + 1.
ENDIF. "Initialization mode or data extraction ?
ENDFUNCTION.
i assign points....
Regards,
PSR.

Hi ,
i am not find any sollution for this..
any body help me for this problum...
i assign points..
Regards,
PSR

Delta error in ods

Similar Messages

Maybe you are looking for