0CO_OM_CCA_9 - Delta load - after Function Module Enhancement

Hi All,
We are facing issue in 0CO_OM_CCA_9 data source delta load after function module enhancement.
why we went for enhancement -
Vendor (LIFNR)field is getting populated only for Invoice and not for GR entries.
To Solve the issue -
we written an user exit in CMOD, that will fetch the Vendor field(LIFNR) from the table EKKO using the PO Document Number (EBELN) as key.
Issue -
We loaded the data with full load and found after the enhacement data fetched for vendor field.
But after doing the init and started loading the delta we found data is not fetched for vendor field alone.Hence for the delta load we face the same issue of no entries for vendor field.
Can anyone suggest the reason, y delta is not fetching the vendor entries.
I have checked in RSA3, only FULL update option is allowed to check and other update mode is not allowed(greyed).
Thanks in Advance
Ramesh

Hi Ramesh,
What you can do to debug the extraction is adding an infinite loop in the enhacement (before your code) like this:
data: a.
a = 1.
while a = 1.
endwhile.
**your code**
Then, from BW run the extraction, and go to ERP, transaction SM50, look for the extraction process, select it, and go to Process/Session -> Program Debugging. A new window with the debugger will be opened, and you'll be in the while. Change the valiue of a, and start debugging.
Perhaps the problem is that you are trying to modify a value that is not an enhacement, and it doesn't takes your modification when you do a delta.
Hope this helps.
Regards,
Diego

Similar Messages

Generic Delta extraction by Function module issue

Hello Experts,
Please help !!!
I have problem for delta extraction by Function module. For the full load, I wrote function module based on RSAX_BIW_GET_DATA_SIMPLE. It works fine.
But I would like to have the delta load enabled. Therefore, I modified the datasource, add a delta specific field u2018ztimestampu2019, which type is calendar day.
Then I create a function module based on template u2018RSAX_BIW_GET_DATAu2019, as this support the upload mode. But when I test this datasource in RSA3, no matter itu2019s full load or initial delta load, it always send me an error, u201CErrors occurred during the extractionu201D.
I had some debug, and found that there is no value for i_isource when my function module is called. Therefore it raised the exception.
But I do not have the chance to debug my code for the delta logic, can somebody help to check?
I also check the entries in ROOSOURCE,
For my datasource ZTRNREC_FM_DELTA, The DELTA value is u2018AIEu2019, and extraction method is u2018F2u2019, should I change them to DELTA= u2018Du2019 and extraction method to u2018F1u2019? Where to change?
FUNCTION ZRSAX_TRAININGREC_DELTA.
""Local Interface:
*" IMPORTING
*" VALUE(I_REQUNR) TYPE SBIWA_S_INTERFACE-REQUNR
*" VALUE(I_ISOURCE) TYPE SBIWA_S_INTERFACE-ISOURCE OPTIONAL
*" VALUE(I_MAXSIZE) TYPE SBIWA_S_INTERFACE-MAXSIZE OPTIONAL
*" VALUE(I_INITFLAG) TYPE SBIWA_S_INTERFACE-INITFLAG OPTIONAL
*" VALUE(I_UPDMODE) TYPE SBIWA_S_INTERFACE-UPDMODE OPTIONAL
*" VALUE(I_DATAPAKID) TYPE SBIWA_S_INTERFACE-DATAPAKID OPTIONAL
*" VALUE(I_PRIVATE_MODE) OPTIONAL
*" VALUE(I_CALLMODE) LIKE ROARCHD200-CALLMODE OPTIONAL
*" VALUE(I_REMOTE_CALL) TYPE SBIWA_FLAG DEFAULT SBIWA_C_FLAG_OFF
*" TABLES
*" I_T_SELECT TYPE SBIWA_T_SELECT OPTIONAL
*" I_T_FIELDS TYPE SBIWA_T_FIELDS OPTIONAL
*" E_T_DATA STRUCTURE ZTRN_REC_TIME OPTIONAL
*" E_T_SOURCE_STRUCTURE_NAME OPTIONAL
*" EXCEPTIONS
*" NO_MORE_DATA
*" ERROR_PASSED_TO_MESS_HANDLER
The input parameter I_DATAPAKID is not supported yet !
Example: InfoSource containing TADIR objects
Auxiliary Selection criteria structure
DATA: l_s_select TYPE sbiwa_s_select.
Maximum number of lines for DB table
STATICS: l_maxsize TYPE sbiwa_s_interface-maxsize,
 S_S_IF TYPE SRSC_S_IF_SIMPLE,
 S_COUNTER_DATAPAKID LIKE SY-TABIX.
Parameter I_PRIVATE_MODE:
Some applications might want to use this function module for other
purposes as well (e.g. data supply for OLTP reporting tools). If the
processing logic has to be different in this case, use the optional
parameter I_PRIVATE_MODE (not supplied by BIW !) to distinguish
between BIW calls (I_PRIVATE_MODE = SPACE) and other calls
(I_PRIVATE_MODE = X).
If the message handling has to be different as well, define Your own
messaging macro which interprets parameter I_PRIVATE_MODE. When
called by BIW, it should use the LOG_WRITE macro, otherwise do what
You want.
Initialization mode (first call by SAPI) or data transfer mode
(following calls) ?
IF i_initflag = sbiwa_c_flag_on.
Initialization: check input parameters
 buffer input parameters
 prepare data selection
The input parameter I_DATAPAKID is not supported yet !
Invalid second initialization call -> error exit
 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.
Check InfoSource validity
 CASE i_isource.
 WHEN 'ZTRNREC_FM_DELTA'.
 WHEN OTHERS.
 IF 1 = 2. MESSAGE e009(r3). ENDIF.
 log_write 'E' "message type
 'R3' "message class
 '009' "message number
 i_isource "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.
Check for obligatory selection criteria
 APPEND LINES OF i_t_select TO g_t_select.
Fill parameter buffer for data extraction calls
 g_s_interface-requnr = i_requnr.
 g_s_interface-isource = i_isource.
 g_s_interface-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 g_t_segfields.
ELSE. "Initialization mode or data extraction ?
Data transfer: First Call OPEN CURSOR + FETCH
 Following Calls FETCH only
LOOP AT G_T_SELECT INTO L_S_SELECT
 WHERE FIELDNM = 'ZTIMESTAMP'.
ENDLOOP.
 IF G_COUNTER_DATAPAKID = 0.
 IF L_S_SELECT-LOW = '' AND L_S_SELECT-HIGH = ''.
 OPEN CURSOR WITH HOLD G_CURSOR FOR
 SELECT (g_t_fields)
 FROM ZTRN_REC_TIME.
 ELSE.
 OPEN CURSOR WITH HOLD G_CURSOR FOR
 SELECT (g_t_fields)
 FROM ZTRN_REC_TIME
 WHERE ZTIMESTAMP >= L_S_SELECT-LOW
 AND ZTIMESTAMP <= L_S_SELECT-HIGH.
 ENDIF.
 ENDIF.
FETCH NEXT CURSOR G_CURSOR
 APPENDING CORRESPONDING FIELDS
 OF TABLE E_T_DATA
 PACKAGE SIZE S_S_IF-MAXSIZE.
 IF SY-SUBRC <> 0.
 CLOSE CURSOR G_CURSOR.
 RAISE NO_MORE_DATA.
 ENDIF.
 S_COUNTER_DATAPAKID = S_COUNTER_DATAPAKID + 1.
ENDIF.
ENDFUNCTION.
I found some similar issue in this forum by link
Generic Extractor Delta Function Module code, but still I could not get clear answer.
Can you please help me:
1) why there is no value for i_source , how to fix it?
2) For the delta logic for ztimestemp, is it correct?
3) Need I modify the entries in ROOSOURCE ?
Thanks a lot !!!

Hello Andre,
 Thanks a lot for your help. I did some change , but still does not work. Could you please help check.
Now the source code are the following, It's based on the RSAX_BIW_GET_DATA_SIMPLE, as you confirm that this also supply the update mode (full, initial delta, delta).
FUNCTION RSAX_BIW_GET_DATA_TRAININGREC1.
""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 ZTRN_REC_TIME OPTIONAL
*" EXCEPTIONS
*" NO_MORE_DATA
*" ERROR_PASSED_TO_MESS_HANDLER
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_ZTIMESTAMP FOR ZTRN_REC_TIME-ZTIMESTAMP.
Initialization mode (first call by SAPI) or data transfer mode
(following calls) ?
IF I_INITFLAG = SBIWA_C_FLAG_ON.
Initialization: check input parameters
 buffer input parameters
 prepare data selection
Check DataSource validity
 CASE I_DSOURCE.
 WHEN 'ZTRNREC_FM'.
 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.
 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.
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
 IF S_COUNTER_DATAPAKID = 0.
 LOOP AT S_S_IF-T_SELECT INTO L_S_SELECT WHERE FIELDNM = 'ZTIMESTAMP'.
 MOVE-CORRESPONDING L_S_SELECT TO L_R_ZTIMESTAMP.
 APPEND L_R_ZTIMESTAMP.
 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.
 IF L_S_SELECT-LOW = '' AND L_S_SELECT-HIGH = ''.
 OPEN CURSOR WITH HOLD S_CURSOR FOR
 SELECT (S_S_IF-T_FIELDS)
 FROM ZTRN_REC_TIME.
 ELSE.
 OPEN CURSOR WITH HOLD G_CURSOR FOR
 SELECT (S_S_IF-T_FIELDS)
 FROM ZTRN_REC_TIME
 WHERE ZTIMESTAMP >= L_S_SELECT-LOW
 AND ZTIMESTAMP <= L_S_SELECT-HIGH.
 ENDIF.
 ENDIF. "First data package ?
Fetch records into interface table.
named E_T_'Name of extract structure'.
 FETCH NEXT CURSOR S_CURSOR
 APPENDING CORRESPONDING FIELDS
 OF TABLE E_T_DATA
 PACKAGE SIZE S_S_IF-MAXSIZE.
 IF SY-SUBRC <> 0.
 CLOSE CURSOR S_CURSOR.
 RAISE NO_MORE_DATA.
 ENDIF.
 S_COUNTER_DATAPAKID = S_COUNTER_DATAPAKID + 1.
ENDIF. "Initialization mode or data extraction ?
ENDFUNCTION.
I think it already includes the important statements you suggested.
I test this FM in RSA3, for the Full load mode, it works fine. Also if I checked the debug mode in execution , it will stop in the code and let me debug.
But when I choose other mode, like 'initializion of the delta transfer' or simulation of initial delta, I always get error 'error occurs during the extraction' .. even I choose debug mode, but it could not enter the code for debug..
Till now I did not see any parameter or value for the upload mode..
Another questions is that, in RSO2, I define Ztimestamp as my delta field.. But , can I add other field as selection condition in the datasource definition, and has its range table in this function module ?
Should I change the entries in ROOSOURCE for this datasource ??
Please let me know your feedback, do you have some concret example for generic delta extraction ?
Thanks a lot !

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.

Code For Delta Extraction Using Function Module

Dear Experts,
I want a sample code for Delta Extraction using Function Module ( If it is customized already working code very helpful ), I have already created Function Module but Full update is happening. If I give delta update again it is retrieving all records. It is very urgent, if you have please send me to the following mail ID.
[email protected]
Best Regards,
SGK.

Dear KJ,
Thank for your response. I saw the code that you sent, you have used some ztables like ZSC_DELTA_IP, ZSC_SAFETY_DELTA, ZSC_SET_EXT_TIME
What are the fields that you have created in these tables , what is use of these tables, can you send the fields that you have used in these tables.
Thanks & Regards,
SGK

Delta Extraction Using Function Module ( Customization )

Dear Experts,
I want a sample code for Delta Extraction using Function Module ( If it is customized already working code very helpful ), I have already created Function Module but Full update is happening. If I give delta update again it is retrieving all records. It is very urgent, if you have please send me to the following mail ID.
[email protected]
Best Regards,
SGK.

Hi SGK,
I've done this for a delta based on a timestamp and it's actually pretty easy. The basic steps are:
1) Create an extract structure in SE11. Make sure the structure has a date or timestamp field in it that you can use for delta. You'll need to include the field twice if you also want to extract it to BW/BI since once it's chosen as the delta field then it will be hidden in the interface.
2) Create the extractor function module in SE37. You can use RSAX_BIW_GET_DATA_SIMPLE as a template. Make sure your logic restricts the data it retrieves according to the selections that are passed in I_T_SELECT, including restrictions on the delta field.
3) Create a generic DataSource in RSO2. Click Extraction by FM then fill in your extract structure and function module. Click Generic Delta and pick your delta field and the appropriate radio button (time stamp or calendar day). If your delta field is a timestamp field then be sure to set the upper and lower safety limits to -86400 and 86400 respectively. This might not be necessary on your version of SAPI but on mine there is a bug where it doesn't translate between system time and UTC (GMT) correctly so this was necessary.
You don't need to program any special delta handling logic in your function module as long as you restrict the data you retrieve based on the delta field (I_T_SELECT). This is because the SAPI takes care of catching the init, delta and repeat requests, translating them to the appropriate delta field values, and then passing them to your function module as if it was a full extraction for a specific date or timestamp range.
Hope this helps!
Jason

Delta load after upgrade to 2004s - Functional changes

Hi All,
I have some doubts about Delta using DTP.
Our BI landscape has been upgraded to 2004s from 3.1 (technical upgrade). There are many existing delta loads and we cannot afford to mess anything at all. So my question to you all
When we do a functional upgrade...
1. The existing delta from 0FIL_GL_4, AP_4, AR_4, WBS_6, NWA_2 etc all having delta loads right now and go to DSO. The records are in many millions. It is highly unlikely they will allow me to delete the PSA and reload all, because it will take couple of months. So that is out of the question.
We have 3 situations.
1. Delta from Data Source into DSO.
2. Delta from DSO to Cubes
3. Delete from few Cube to Cube.
Questions
1. After converting from Info Package to DTP I will still load the delta from Data Source to PSA, but the data source need to migrated to 2004s. WIll it cause any issues in loading delta data?.
2. The DSO to further targets are using delta info package, I believe I change the info package to DTP with load mode selected as DELTA. Is this correct?
Thanks in advance.
Alex.

DTP is used to load data only from PSA to Datatargets and DELTA DTP Loads the last PSA request which was transferred to PSA from source.
So 2 plausible ways could be -
1)Delete all PSA data and so your DELTA DTP will get the DELTA load only or new changed posted to PSA only and not all the previous requests ..but you may not want to delete the PSA now.
2)Fake the DTP using some infoobject FILTER selection criteria as blank which acts like INIT w/t data transfer and then do DELTA DTP as mentioned below -
https://forums.sdn.sap.com/click.jspa?searchID=10026965&messageID=4743634
1. After converting from Info Package to DTP I will still load the delta from Data Source to PSA, but the data source need to migrated to 2004s. WIll it cause any issues in loading delta data?.
NO
2. The DSO to further targets are using delta info package, I believe I change the info package to DTP with load mode selected as DELTA. Is this correct?
YES
Hope it Helps
Chetan
@CP..

How to create delta extraction through function module?

Hi all,
So far i have created the data source through full load. But currently i would like to convert the couple of function module generic extraction converted through delta.
Can anyone let me know how to convert from full load to delta using generic extraction
thanks

Hi,
Try these Links, helps u in getting an idea.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/30aefb04-7043-2c10-8e92-941536eebc79?QuickLink=index&overridelayout=true
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/30f1a423-02ae-2e10-bd85-bde64e61fe7b?QuickLink=index&overridelayout=true&51947629650864
Regards,
Aravind.

Generic delta extraction using function module

Hi.
I have a generic datasource , extraction being performed by a function module. The extraction works fine in full update mode. The extract structure has a timestamp field.
I have enabled generic delta using this field(i.e., marked this field in RSO2). I understand that with this setting, I should be able to get delta data when I do a delta request. But it does not seem to happen.
I checked the ROOSPRMSC table for the last(local) timestamp stored there. Now when I do the delta upload I expect to see only those records which are younger than the stored timestamp of last upload.
But I still get the entire set of records.
Questions are :
1. Do I need to explicitly code for fetching the delta in the extractor ?
2. If not, what could be the reason why generic delta is not working ?
Thanks and regards,
Anuradha

Hi GFV,
I read-up all the forum entries on this topic but could not find anything specifically dealing with my problem. I have browsed through the how-to paper on generic delta as well.
I am quite sure that we don't need any special coding in the extrator for generating delta generically. Even the how-to paper does not mention that.
I have used the FM RSAX_BIW_GET_DATA_SIMPLE as a template
for my extractor(as suggested by F1 help in RSO2). This FM does not even have the i_updmode flag in its interface.
Thus this function module always does full extraction and I expect the system to take care of delta using the timestamp field.
Are these assumptions incorrect ?
Regards,
Anuradha

Delta load after full load

Hi gurus
We are doing delta loads to a cube which is initialized in 2007.
Now we have some problem with the data cause 2 deltas are missing for Aug
so I just want to selective deletion for aug and i want to do a full load for aug
my doubt is
after that full load daily delta will be sucessfull?
Thanks in advance
Regards
a

Hi,
Before going on with the load, check the following points:
1. Check if all the delta has been moved up to the cube and all the data request in lower level has datamart status set.
2. If there are some request without data mart status move those reqeust to cube before doing the full load.
Then go for the selective deletion from the cube and reload as full update. You should be able to load delta further. There wont be any problem. Even if you have problem, since you have made sure that all the request has gone up and delta mart has been set in lower level you can break the init and reinit from lower level to current cube.
Hope this is clear.
Regards
akhan

How to do delta load after full load

Hi,
I did full loads for my Data target.
I have 15 requests on my Data target.
Now i want to do delta load.
Please help me how to do delta load even after full loads.
Advance thanks.
Regards,
Rafi

Hi,
change in my post!!!
after full load you can go for delta,but it is not viceversa
if you want to run delta
since you have done prior full loads,,do init without data transfer which will sets the init flag
now run delta
please also check is your datasource supports delta or not
try RSA6, datasource and display,
check if 'delta update' is marked
or table ROOSOURCE field DELTA
Cheers,
Swapna.G
Message was edited by:
swapna gollakota
Message was edited by:
swapna gollakota

Generic Delta Update using Function Module........ problem with CURR type

Hi Experts,
I try to create a generic data source using the transaction RSO2. I got the following error message
" Das Einheitenfeld CURR des Feldes ZPKZA1 der DataSource ZBWN_DS_POLPOSP ist ausgeblendet"
"The unit field CURR of the field ZPKZA1 of the DATA SOURCE ZBWN_DS_POLPOSP is not visible/ stopped/ hide".
How shall i handle this issue..........any suggestions please........
thanks in advance
Cheers
Jaya

Hi Jaya ,
The error msg which is coming as...
"The unit field CURR of the field ZPKZA1 of the DATA SOURCE ZBWN_DS_POLPOSP is not visible/ stopped/ hide" may be due to the currency field made hidden at the data source lavel. Also check weather you have included it in your structure (code).
So, to check it and make it unhide go to "Display Field List (F7)" in RSO2.
Hope it helps.

Delta Loads are not working: 0FI_GL_10 With enhancement : HR Data in source

Hello Friends. Thanks for your answer on theory which I know, Please help me with this situation. I read all the sdn response to my message and have below for your suggestion
QUES1: Why the 0RECORDMODE is not coming in Standard DSO and hence it is not there in Transformation in between Infosource and DSO. What do I need to include 0RECORDMODE in standard DSO. What is the correct OSS to Implement on SP 10 to solve this.
Ques2. As suggested by you If I run the Delta loads after waiting for 1 hour of Init load. say init load was done at 11 am . i will do the delta at 12:10 am to psa via Infopack and then wait for an hour to run the DTP from PSA to DSO. Delta Records come in but it also bring in the records in DSO that are not changed from about 7 hours in ECC. and make our total Balance incorrect.
Ques3: We have this Cocatenation of Keys in DSO since we exceeded the total number of 13 key in DSO.
Cocatenation#1 GL ACCT and CHRT OF ACCTS
Cocatenation#1 SEGMENT AND CONT AREA
Cocatenation#1 Version, Value Typem, Valuation view, Currency Type.

Since business want to include HR Data in Keys Like Employee Number, Emp Code, EMPSPIMCODE. Payroll ID and I can not remove these fields from Key in DSO as per the business.
Also the above fields GL ACCT , CHRT OF ACCTS, SEGMENT, CONT AREA
exist in Data FIELDS OF DSO. so what are the steps to modify the design to fix this asap.
Please email me at [email protected] if you have any docs to resolve the above
Thanks
Soniya
null

Did the full load bring all records from sourcesystem to PSA?
Was this an issue with the first delta you have tested ?
Concatentaion of multiple keys into one should not be an issue here as that must have been happening in DSO and delta brings incorrect records to PSA itself.
Are you validating delta records against FAGLFLEXT inputing the timestamp value or RSA3 ..how ?
Check if this note helps
Note 1002272 - NewGL-DataSource 0FI_GL_10, 3FI_GL_*: Missing record.
Is delta bringing incorrect records to PSA or DTP brings incorrect records to DSO from PSA ?
May be you should revisit the logic behind for the enhancement of 0FI_GL_10.
I am facing a similar issue as well but here delta doesnot even bring a single record ( ODS has 20 keys )...will update if resolves and you do the same.
Message was edited by:
Jr Roberto

Generic delta with function module

Hi Gurus,
Is it possible to create a generic DataSource with delta support using function module following the queue delta mechanism (u can get some function moduel in MCEX function group, and check the outbound delta queue before and after update in transaction smq1.
I can store the delta data using qRFC and collective update mechanism. but I don't know how to create a generic data with delta and how to attach a rfc destination (& logical system) to the data source. The Source system information is stored in the table "ROOSGEN". Is there any configuration setting required to do the same.
Regards,
Jugal

Jugal,
What I understand you to be asking is if it is possible to create a generic delta extractor which uses the delta queue. If this indeed is your question the answer is yes.
First you need to create your data source so it is visible via tx RSA5 and need to make sure that the delta type (ie ABR, AIM)is set appropriately for the datasource.
The issue however is determining from where you will associate your delta hook (when will you write to the queue)? I have in the past utilized BTE's, Business Transaction Events to write information out to the delta queue, you can see a list of available BTE's in your system via tx FINF.
Once you find a place to write your deltas from you call the below FM with the appropriate datasource.
RSC1_TRFC_QUEUE_WRITE.
Once you have done this the standard BW extractor for deltas will pull the information from the delta queue. But from what I understand you just want to know how to associate the data with the delta and that is the FM listed above.
Hope this helps,
Cheers,
Scott
> Hi Gurus,
>
> Is it possible to create a generic DataSource with
> delta support using function module following the
> queue delta mechanism (u can get some function moduel
> in MCEX function group, and check the outbound delta
> queue before and after update in transaction smq1.
> I can store the delta data using qRFC and collective
> update mechanism. but I don't know how to create a
> generic data with delta and how to attach a rfc
> destination (& logical system) to the data source.
> The Source system information is stored in the table
> "ROOSGEN". Is there any configuration setting
> required to do the same.
>
> Regards,
> Jugal

Creating a delta against a custom Function Module datasource

I currently created a datasource via RSO2 against a function module. The function module uses the RSAX_BIW_GET_DATA_SIMPLE as a template and I molded this against the data that I need. Full loads for this extractor work without any problems but I'm having issues with creating a delta load. Is there someone that can create a list on how to createa delta against a function module. I believe there is more to do this than just have RSO2 set up against a field. How do I get the new records into RSA7? Thanks for your help.
Tim

We are trying to create the same delta extract from r/3 against a custom z table to an infocube in BW. Were you able to do this successfully using the f RSVD_BW_GET_DELTA_DATA as a template and did u receive the code? If so, are you able to send your code?
My function modules works and fetches the data normally but the info package when scheduled gives an error
Error message from the source system
Diagnosis
An error occurred in the source system.
System response
Caller 09 contains an error message.
Further analysis:
The error occurred in Service API .
Refer to the error message.
Procedure
How you remove the error depends on the error message.
Note
If the source system is a Client Workstation, then it is possible that the file that you wanted to load was being edited at the time of the data request. Make sure that the file is in the specified directory, that it is not being processed at the moment, and restart the request.
You can send the code or procedure to my mail id
[email protected]
Thanks in advance,
Best Regards,
Vishal

Inconsistent Errors when processing IDocs using custom Function Module

I am encountering a most perplexing error. Here is the situation.
We have a custom function module to update data in the EH&S system. We are having a bizarre error occurring. This is the basic processing of the function module:
1. IDoc data is read and loaded into an internal table.
2. Data is run through a series of checks to determine if the data is valid for entry into the system.
3. After validation we use function module C1F2_SUBSTANCES_READ_WITH_REF to read characteristic data for the substance. This data is used to validate whether current data exists to allow for loading of the IDoc data. (This is the step where the IDoc is receiving an error even if the data is valid. This only occurs if we are processing a large amount of Idocs and one IDoc contains valid data and another invalid data for the same substance. It occurs even if the Idocs are not processed in sequence. If individually processed or reprocessed after initial failure they pass. This is what is so confusing!) If it exists, a flag is set and the data is loaded using function module BAPI_BUS1077_CHANGE to modify the data.
4. If the flag is set to allow further processing, the function module C1F2_SUBSTANCES_READ_WITH_REF is used again to select different characteristic data for the substance. A similar validation process occurs and if it passes, data is loaded using BAPI_BUS1077_CHANGE to update and BAPI_BUS1077_CREATE to create new data.
Here is the situation:
When processing one valid record for one substance, the record loads successfully. When processing multiple valid records (all are valid) for one substance, they all load successfully. The problem occurs when attempting to load valid and invalid records for the same substance. Some times the program successfully loads the valid data (as expected). Other times, it will not load any records. It is not consistent!
The order of IDoc processing does not have an impact on the success of the load. Whether the valid or invalid record processes first does not have an impact on the success of the valid substance load.
Does anyone have ANY Idea of what is going on? I am clearing all fields in the function module before processing occurs. I cannot find what is causing the error to occur.
HELP!
Jim Hardy

I have some further information. It seems that if data for a substance is sent in two separate Idocs, one with valid and one with invalid data, As long as the two IDocs are processed consecutively, they process correctly. If they are separated by IDocs containing other substance information, they fail.
thanks
Jim

0CO_OM_CCA_9 - Delta load - after Function Module Enhancement

Similar Messages

Maybe you are looking for