Repeat Delta mechanism for FI-CO & Generic extractor.

Hello Guys,
Can any one please let me know whether there is repeat delta is possible for FI/CO data sources if we miss any daily dela loads.
If its there, how it works.
thanks in advance
peter.

Hi,
Yes, it is possible to repeat the failed delta for FICO extractors. One thing you need to note is that you need to request the delta second time only then you will get records to BW. First time repeat will fetch 0 records.
Hope this helps
Regards.,
Srni

Similar Messages

Delta Mechanism for LO Cockpit

Hi All,
Currently I am having an issue with an implementation on Sales Order. As understood from Generic DataSource that is available in transaction code SBIW. We are able to create a datasource with the ability to trace the changes that is occuring in a particular transaction by using either addtive delta or new status for changed record.
In Data Source, 2LIS_11_VAITM, which is only available in LO Cockpit, is it possible to have the same tracing too? As I know in LO Cockpit, we have the queued delta, direct delta and the unserialized v3 update, but this is not the delta that we would want.
Really need help urgently on this matter.
Thanks.

It works with the Business content datasource (because it is built in the extractor logic), eg 2LIS_11_VAITM.
This is what is confusing to many people. And it is same as file source system. In the file based DS, you do have an option of specifying whether it is a additive delta (in the datasource editor screen, at least it was till 3.5). This doesn't mean that the file will be read and system will compare from ? PSA or earlier load of the file and determine the delta to be pushed to BW. It means that we are saying that the file already contains delta.
Same here. When we specify additive delta, we are saying that the table/view already contains additive delta (and not that the generic extractor will apply the logic to derive the delta values for the KF).
Let us take an example, say you are storing stock market quotes in a spreadsheet or a table, and you want to move it to BW using generic extractor which loads the current prices to an ODS/Cube.
Let us say the data is like this
STOCK-ID--CLOSING_PRICE--
Movement_since_last_price
NYDE -
60 - -
3.5
HWP -
125 -
-1.25
and so on.
Now, if from this table (or file), you push STOCK_ID, and CLOSING_PRICE using your generic extractor, it is a 'new image' and that is what you should specify.
But, you can also instead push STOCK_ID and 'MOVEMENT' in which case it is an 'additive delta' and you should specify your DS as such.
If you only had STOCK_ID and MOVEMENT data in your table, your DS would have to be 'additive delta'.
I hope you understand it now. Your table data determines what delta type the generic DS is, you can not just specify it as you wish.
Why this setting is there - it tells BW what type of DS it is, so it can warn you if you are trying to load it to incompatible target. For example, if you had a 'new image' type DS, and you tried to load it directly to a cube, the system will give you a warning/error about it being incompatible.

Delta mechanism for 0fi_gl_14

Hi,
We are using 0fi_gl_14 DS for extracting leading ledger's line item data.
But when I checked table BWOM2_TIMEST, there is no entry for the above data source.
Could someone help me understand delta mechanism for 0fi_gl_14?
Is it not similar to 0fi_gl_4 delta?
What is the difference between 0fi_gl_4 and 0fi_gl_14?
Regards,
Shravani

Hi,
Most of the extractors (specially one in question 0FI_GL_14) in FI related extractors work on pull mechanism via Extraction method: F1 (function module (complete interface))
Extractor: FAGL_GET_SI_DATA
1. 0FI_GL_14 extractor, considers all data from the tables FAGLFLEXA (or similar customer tables), BKPF, BSEG, and BSEG_ADD. we use this extractor if New GL configuration done in ECC or otherwise 0FI_GL_4 still holds good.
2.Coming to Delta are picked from BWFI_AEDAT table where all the changed documents/new are maintained as part of changed status.
Hope i have addressed your question!
Regds,
Karunakar P

Delta Mechanism for LO Extraction.... urgent plz

hi experts,
Could you plz.. give me the details below for LO EXTRACTION DELTA MECHANISM.
for the first time load i have done initialize with data transfer. what should i do if i want to extract the new data(Changed Records) from r/3. what are all the settings i need to give. i am using BI7.
plz provide me the documentation for LO EXTRACTION DELTA MECHANISM.
regards
vadlamudi

Hi,
After initialization you need to check the deltas in RSA7 after the load.
For further explanation check these blogs by Roberto Negro:
Episode one:
/people/sap.user72/blog/2004/12/16/logistic-cockpit-delta-mechanism--episode-one-v3-update-the-145serializer146
Episode two:
LOGISTIC COCKPIT DELTA MECHANISM - Episode two: V3 Update, when some problems can occur...
Episode three:
LOGISTIC COCKPIT DELTA MECHANISM - Episode three: the new update methods
Also check
Gist of LO Cockpit Delta
Assign points if this helps........
Rgs,
I.R.K

Check delta definition for standard R/3 extractor

Hi,
we are trying to create a copy of a standard extractor on R/3, it has a delta extraction associated. How can i find the 'Delta-Specific field' and 'Settings' for the definition of the standard extractor.
thanks in advance
JP

Thanks for the answer Roberto, we still have problems trying to copy the extractor structure, it seems that some settings are just used for the standard. Is there any way to copy the standar extractor ?
any tips will be helpfull, thanks.
JP

Delta mechanism for LO Cockpit and COPA datasources

What is the trigger for creating a delta for LO cockpit datasources. Is it a result of calling the LIS exit or the actual creation/change to the transaction?
I have this same question for the COPA datasource.
Thanks
Jim Goodwine

The trigger that you are talking about must be running of a infopackage in BW that extracts data from R/3. When transactions are posted in R/3 (both LIS and COPA), they start accumulating in the delta queue of that datsource in R/3.
A infopackage is scheduled to execute at regular intervals that pull the data from this delta queue into BW.

Delta Mechanism for BPC to BI

Hello Guru,
I have below scenario configured for BPC. Do please let me know your thoughts.
I have 0FIGL_C10 infocube configured in BW where i have data for Entity 1000, 2000& 3000. Data is available from the year Jan 2006 till Nov 2011. 0FIGL_C10 infocube gives data in 3 currencies (00, 10 & 20)
My requirement is below.
1. Entity 1000 is discontinued but data still comes in 0FIGL_C10 infocube. How should i restrict this entity in BPC ? Data manager package doesn't have any selection criteria option like Transformation file has..
2. I have 2 reports. P&L and Balance Sheet. for Balance Sheet , I want to select 100000 to 200000 G/L Account with Currency Type 30 & for P&L, I want to select 300000 to 400000 G/L Account with Currency Type 10. Do let me know how this can be done ?
3. I have data from Jan 2006 till Nov 2011 in my BI Infocube but i want to load only 2011 data into my BPC. So, with that said when i do initialization from BI to BPC, i should be able to extract data from Jan 2011 till Nov 2011 and from December onwards i should be able to extract data for December and then onwards month. How should i manage this because in BI i have data for last 4 years.
Do let me know your valuable thoughts.
Regards,
Komik Shah

Hi,
The set selection feature should serve your puprose.
Have you considered an integration layer with in BW from where you can do the data loads into BPC? You can check the pros and cons of having a new layer.
If you have then, you could use DTP filters when loading to the infocube in the integration layer from FIGL. You need to have other criteria as well to have the staging layer. Just check.
- Restricting Entity 1000....Do you have the conversion file for Entity. You could do *SKIP in a conversion file for this entity.
You could have a routine in BW integration cube to force a particular currency type for PL accounts & GL accounts. Try also looking at using an IF condition in transformation file for currency type selection
RPTCURRENCY=*IF(0CURTYPE=*STR(10) then *STR(LC); TC)
RPTCURRENCY is a currency type dimension in your application. LC and TC are members of this dimension in BPC.
Thanks,
Sreeni

How to do Delta upload using Generic Extractor built on Function Module?

Hello Guys,
I have never created a Generic Extractor using a Function Module. I wanted to know how can we support Delta mechanism if we create Generic extractor using Function Module.
Regards,
Abhishek

Hi Abishek,
Please check the standard Function Module RSAX_BIW_GET_DATA for your delta mechnism.
Hope it will help you.
Thanks,
Chandra

Error in delta generic extractor

I made a generic extractor using a Module Function. And I used the RSVD_BW_GET_DELTA_DATA function, as an example to implement the Delta process for my own generic extractor.
Although when I executed the Delta process in the RSA3 transaction, the program did not use the function I made, but used the RSC1_DELTA_BIW_GET function! So the delta process did not extract any data.
I also modified EXMETHOD field from the ROOSOURCE table:
I changed the status from F2 to F1.
Could you explain me how the delta process works in a Generic Extractor?
Is any special configuration that I missed?
Thanks for your cooperation and regards.

Hi Sirneni,
Is your Init load in BW successfull. Only after
successfull completion of init load in BW the data source appears in delta queue RSA7 in R/3. Also check whether any materials are being changed in R/3 because u r delta is based on last changed date.
Regards,
Prakash B

Delta mechanism setting on R/3 side for a datasource from the FI area

Hi,
How to activate delta data transfer on the R/3 side for a FI related datasource?
For sales and logistics related datasources, there's LBWE where you can activate the delta mechanism.
I have a datasource called 'Committment line items for Funds Management' that comes under FI Management. What is the procedure to activate the delta mechanism for this datasource?
Thanks
Edited by: Sanjeev Koganti on Mar 21, 2008 2:07 PM

Hi,
Financial Accounting line items are read by extractors directly from the tables in SAP R/3.
A time stamp on the line items serves to identify the status of the delta data.
Time stamp intervals that have already been read are stored in a time stamp table.
The delta dataset is transferred to BW directly, without records being transferred to the delta queue in SAP R/3 (extractor delta method).
The FI Extractors are typically function module extractors. The function module for the extractors are as follows:
0FI_TX_4 - BWFID_GET_FITAX_ITEM
0FI_GL_4 - BWFID_GET_FIGL_ITEM
0FI_GL_2 - FBIW_DATA_TRANSFER_GL_2
0FI_GL_1 - FBIW_DATA_TRANSFER_GL_1
0FI_AR_3 - FBW4_DATA_TRANSFER_AR_3
0FI_AP_4 - BWFID_GET_FIAP_ITEM
0FI_AP_3 - FBW4_DATA_TRANSFER_AP_3
Refer.
FI-SL Extraction
http://www.jt77.com/business-warehouse/work-flow-13393.html
http://www.saptutorials.com/list/1/,B,BW,xhtml
Steps to move data from SAP r3 into BW
http://www.jt77.com/business-warehouse-q/index20.html
http://jt77.com/business-warehouse/work-flow-15111.html
http://help.sap.com/saphelp_sm32/helpdata/en/f9/eb7641b61b5858e10000000a1550b0/RN_353_e.pdf
CO-PA and FI-SL EXTRACTIONs
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/FISL/FISL.pdf
http://help.sap.com/saphelp_47x200/helpdata/en/66/bc7d2543c211d182b30000e829fbfe/frameset.htm
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/a7f2f294-0501-0010-11bb-80e0d67c3e4a
Re: Which tables for LO and FI...
http://help.sap.com/saphelp_nw04/helpdata/en/af/16533bbb15b762e10000000a114084/frameset.htm
Difference between FI and LO extraction
Extraction Steps for FI Data Sources
FI-GL Extraction steps
Re: FI Extraction Steps
http://help.sap.com/saphelp_bw32/helpdata/en/af/16533bbb15b762e10000000a114084/frameset.htm
Thanks,
JituK

REPEAT DELTA WILL WORK FOR MASTER DATA DELTA LOADS

Hi Guru's,
REPEAT DELTA WILL WORK FOR MASTER DATA DELTA LOADS?
AS I AM NEW TO SAP-BI CAN ANY ONE GIVE THE DETAIL EXPLANATION ON IT.
IT WILL BE GREAT AND HELPFULL.
Thanks and Regards,
CM

Hi CM,
yes you can perform the repeat delta even for the master data if the datasource which was supplying the data was delta capable.
You can do the repeat delta only in case if your previous request was erroneous and dont forget to make the request red in the status,so that system will treat like you are requesting the failed request once again where in case you will miss the previous request, i,e erroneous request if you dont make the request red.
when you make the request red manually in the status,the pointer will move to the previous request once again in the delta queue and there will be no chance of missing the delta records.
This process was same for both transaction as well as master data.
Regards,
Sunil...

Difference between Customer Generated Extractors and Generic Extractors

Hi all,
Can anyone please tell me the difference between Customer Generated Extractors and Generic Extractors. I know that for all modules Generic extraction is possible by creating a datasource(RSO2) on top of a table, View or SAP Query in SE11. What are customer generated extractors like LIS, CO/PA and FI/SL.
What kind of extraction is used for FI/AR and FI/AP. To my understanding we have BW Content Extractors. Can anyone explain the extraction method and delta extraction for AR and AP.
Thanks,
Sabrina.

Hi,
Customer generated extractors are running on top of statistics data collection process in R/3. They extract data from statistical tables already available in R/3 and also use the mechanism already provided in R/3 to capture the delta.
For example, PO data goes to statistical table S012 (it is an LIS table) and you can build a generated extractor on top of it. The difference between such extractor and a generic one is the fact that these extractors (eg LIS) use the same mechanism of capturing delta that the statistics table was doing (for example data that goes into S012 is also captured by these generated extractors). Some system tables and structures are generated automatically to support this functionality, you do not have to develop anything for this.
Generic extractors on the other hand simply let you pull data from table/view/query etc. You have to develop code/functionality to support delta capturing for such extractors. If you built a generic extractor on top of S012 (it is a statistical table - LIS), you can pull its data to BW, but you do not have the delta capturing functionality in such case, you will have to code it yourself.
As a thumb rule, you go with the standard/generated extractors, and use generic extractors only if it is necessary to be so.
FI/AR and FI/AP extractors are part of business content (I think) and support delta functionality. To get detailed info on these, you can also look at help documentation -
http://help.sap.com/saphelp_nw04/helpdata/en/ee/cd143c5db89b00e10000000a114084/frameset.htm
cheers,

Is Delta possible for the below mentioned data sources in your systems?

Hi All,
I am strongly belive that these below datasources are not having delta.
By any change recently is there any ECC systme new plugins may having these datasources also delta's?
0FUNCT_LOC_ATTR
0EQUIPMENT_ATTR
0NOTIFICATN_ATTR
0ASSET_ATTR
0CS_ORDER_ATTR
0EMPLOYEE_ATTR
Please confirm me if any of your case having delta's for these datasources?
Regards
Srini
Edited by: Srinivas Gogineni on Feb 27, 2010 10:38 PM

Hi,
SAP Note #1619612 will be released in a few days to enable deltas on 0CS_ORDER_ATTR.
[1619612 - Delta mechanism for 0CS_ORDER_ATTR.|https://websmp107.sap-ag.de/sap/support/notes/1619612 ]
Kind Regards,
Paulo Jr.

Delta update for generic extractor ?? Urgent!!!!

Hi All
In my project I am pulling data from 4 R/3 tables... I have created view & then Generic DataSource.
Can a delta update be set-up for the generic extractor based on adds/changes to the R/3 tables?
Thanks & Regards,
Sheetal
Message was edited by:
Sheetal Dhore

Hi,
Please take a look at the following doc.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d3219af2-0c01-0010-71ac-dbb4356cf4bf
Regards,
®

Delta fo Generic extractor using function module

Hi,
I am using the following function module for generic extractor but its always showing me extraction error.Could anyone please suggest to resolve the issue.
Thanks in advance fo rsuggestion.
FUNCTION Z_BW_SALESDATA_EXTRACT_CHNG2.
""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 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
TABLES: VBFA,VBRK,tadir.
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.
user defined variables.
DATA : X_UPDMODE(1) Type c,        " Update Type
        X_LastUpdate Like Sy-Datum. " Last Update Date
         X_LastUpdate TYPE RODELTAID. " Last Update Date   "TCS_KAP
Select ranges
RANGES: L_R_VBELN   FOR VBAK-VBELN,
          L_R_AUDAT   FOR VBAK-AUDAT.
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 'Z_BW_SDDATA_CREATEON'.
      WHEN 'Y'.
      WHEN 'Z'.
      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 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
   READ TABLE i_t_select INTO l_s_select WITH KEY fieldnm = 'VBELN'.
   IF sy-subrc <> 0.
     IF 1 = 2. MESSAGE e010(r3). ENDIF.
     log_write 'E'                    "message type
               'R3'                   "message class
               '010'                  "message number
               'PGMID'                "message variable 1
               ' '.                   "message variable 2
     RAISE error_passed_to_mess_handler.
   ENDIF.
   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.
Store Update mode in static variable...
   X_UPDMODE = I_UPDMODE.
    Select Single DELTAID
           Into   X_LastUpdate
           From   ROOSGENDLM
           Where OLTPSOURCE = 'Z_BW_SDDATA_CREATEON'.
    If X_LastUpdate Is Initial.
      X_LastUpdate = '19800101'. " The oldest..., this should not happen
    Endif.
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
X_UPDMODE = I_UPDMODE.
First data package -> OPEN CURSOR
    IF g_counter_datapakid = 0.
Fill range tables for fixed InfoSources. In the case of generated
InfoSources, the usage of a dynamical SELECT statement might be
more reasonable. BIW will only pass down simple selection criteria
of the type SIGN = 'I' and OPTION = 'EQ' or OPTION = 'BT'.
      LOOP AT g_t_select INTO l_s_select WHERE fieldnm = 'VBELN'.
        MOVE-CORRESPONDING l_s_select TO L_R_VBELN.
        APPEND L_R_VBELN.
      ENDLOOP.
      LOOP AT g_t_select INTO l_s_select WHERE fieldnm = 'AUDAT'.
        MOVE-CORRESPONDING l_s_select TO L_R_AUDAT.
        APPEND L_R_AUDAT.
      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 InfoSource table lines and database entries, this is trivial.
In other cases, it may be impossible and some estimated value has to
be determined.
*added by Yogesh
      DELETE FROM ZBWSALEDATA.
*ended by Yogesh
      l_maxsize = g_s_interface-maxsize.
Check for supported update mode
      CASE X_UPDMODE.
        WHEN 'F' Or 'I'. " Full or Init
**get sales orders
          SELECT *
                       INTO CORRESPONDING FIELDS OF TABLE I_SALESDATA
                       FROM VBAK AS K
                       INNER JOIN VBAP AS P
                             ON PVBELN = KVBELN
                       WHERE K~VBELN IN L_R_VBELN
                       AND   K~AUDAT IN L_R_AUDAT
                       AND   K~VBTYP = 'C'.
          IF I_SALESDATA[] IS NOT INITIAL.
            PERFORM F_GET_DATA.                   "get data
            PERFORM F_DEL_VATCOND.                "delete vat conditions
            PERFORM F_GET_TAR_COSTUNIT.           "get tariff cost unit
            PERFORM F_GET_NETVAL TABLES IT_VBDPA1. "get net val of the item
            PERFORM F_GET_SALESDATA.
*write perform with name F_INSERT_DB_ZBWSALEDATA.
            PERFORM F_INSERT_DB_ZBWSALEDATA.      "insert into table ZBWSALESDATA
           LOOP AT I_SALESDATA WHERE NETPR = 0.
             MOVE-CORRESPONDING I_SALESDATA TO I_SALESDATA_FIN.
             APPEND I_SALESDATA_FIN.
           ENDLOOP.
           SORT I_SALESDATA_FIN BY VBELN POSNR KSCHL.
           DELETE ADJACENT DUPLICATES FROM I_SALESDATA_FIN
                                           COMPARING VBELN POSNR
                                                     KSCHL.
           INSERT ZBWSALEDATA FROM TABLE I_SALESDATA_FIN.
          ENDIF.
        WHEN 'D'. " Delta
          SELECT *
                         INTO CORRESPONDING FIELDS OF TABLE I_SALESDATA
                         FROM VBAK AS K
                         INNER JOIN VBAP AS P
                               ON PVBELN = KVBELN
                        WHERE K~ERDAT >= X_LastUpdate
                         WHERE K~ERDAT >= X_LastUpdate+0(8)          "TCS_KAP
                         AND   K~VBTYP = 'C'.
          IF I_SALESDATA[] IS NOT INITIAL.
            PERFORM F_GET_DATA.                   "get data
            PERFORM F_DEL_VATCOND.                "delete vat conditions
            PERFORM F_GET_TAR_COSTUNIT.           "get tariff cost unit
            PERFORM F_GET_NETVAL TABLES IT_VBDPA1. "get net val of the item
            PERFORM F_GET_SALESDATA.
*write perform with name F_INSERT_DB_ZBWSALEDATA.
            PERFORM F_INSERT_DB_ZBWSALEDATA.      "insert into table ZBWSALESDATA
           LOOP AT I_SALESDATA WHERE NETPR = 0.
             MOVE-CORRESPONDING I_SALESDATA TO I_SALESDATA_FIN.
             APPEND I_SALESDATA_FIN.
           ENDLOOP.
           SORT I_SALESDATA_FIN BY VBELN POSNR KSCHL.
           DELETE ADJACENT DUPLICATES FROM I_SALESDATA_FIN
                                           COMPARING VBELN POSNR
                                                     KSCHL.
           INSERT ZBWSALEDATA FROM TABLE I_SALESDATA_FIN.
          ENDIF.
        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.
**end get sales orders
      OPEN CURSOR WITH HOLD g_cursor FOR
      SELECT (g_t_fields) FROM ZBWSALEDATA.
     WHERE pgmid IN l_r_pgmid AND
                                    object IN l_r_object.
    ENDIF.                             "First data package ?
Fetch records into interface table. There are two different options:
- fixed interface table structure for fixed InfoSources have to be
named E_T_'Name of assigned source structure in table ROIS'.
- for generating applications like LIS and CO-PA, the generic table
E_T_DATA has to be used.
Only one of these interface types should be implemented in one API !
    FETCH NEXT CURSOR g_cursor
               APPENDING CORRESPONDING FIELDS
               OF TABLE E_T_DATA
               PACKAGE SIZE l_maxsize.
    IF sy-subrc <> 0.
      CLOSE CURSOR g_cursor.
      RAISE no_more_data.
    ENDIF.
    g_counter_datapakid = g_counter_datapakid + 1.
ENDIF.              "Initialization mode or data extraction ?
Best regards,
Yogesh

Dear Yogesh,
Try to debug the code by putting a break point at select statement...is the FM Syntactically correct ??
Check the Select statements..if all fields are not required avoid using Select * , and use always for all entries rather than JOINS..
Note : For Joins you have to specify the Fields in the Select...Dont use Select * ....
Hope it helps..
Thanks,
Krish

Repeat Delta mechanism for FI-CO & Generic extractor.

Similar Messages

Maybe you are looking for