R/3 table to BW via Delta Extraction (Urgent plz)

Hello Experts,
How to load a data from one of the R/3 tables to BW when the table doenst contains either a time stamp, Date field or numeric pointer.
I have PS Table in R/3 (RPSCO) with over 7 hundered thousand records in it. I would like to populate the data to a ODS via delta extraction.
The table doesnt contain either a timestamp, numeric pointer or date. How would I extract a data now to BW via delta. Would it be possible to use Generic extraction.
Thanks and Regards,
Harish

Hi Harish,
If you need ODS to make delta DataMart you can not delete data before every upload.
For spee-up the upload you can follow these solution:
1)Take off from parameters of your ODS Reporting BEx flag. Without this flag the system does not spent time for reporting activation of data.
2)If upload is too slow you can try to make delta in R/3 via a program that compare previous upload and new status of your table, introducing in the tableforthe upload only modified records. It can be very slow, but it is all R/3 time.
Ciao.
Riccardo.

Similar Messages

  • Delta extraction for FI (AR & AP) data sources

    I tried extracting the data from 2 standard SAP data sources under FI module for Accounts Receivable.
    0FI_AR_10(Customer payment history via delta extraction)
    0FI_AR_5 (customer payment history)
    The data to be extracted into 0FIAR_C05(payment history) info cube.I assigned the 2 data sources to an info source and pumped the data into the cube via an ODS.Now the problem is with delta extraction.No records are picked in the delta extraction.So I checked in extractor checker RSA3 with delta update mode.I got the following error.
    "Could not determine BW release of logical system"
    Could some one resolve the issue?Thanks in advance.
    Thanks & Regards
    Vinay

    Hi ,
    Please go through 493422 note  once . see if suits to your requirement  follow it  accordingly .
    Thanks ,
    Anil

  • ALE delta extract for HR master data

    We want to create some R/3 delta extracts based on the HR PA* tables using the ALE delta extract function of generic extractor. Has anyone done this before?  Are there any OSS notes or documents that I should look at?  Thanks!

    Hi Bill Faison,
    This is very old message. I think your problem must be solved. If it is not then: yes we can extract Data from R/3 with ALE Delta .
    You have to perform below steps.
    1.     In your Table you need to activate ALE change   pointer.
    2.     Create change documents for required table.
    3.     Created Generic Extractor with ALE Delta.
    Hope this will help.
    Let me know if you have any concern or issue in this regards
    Best Regards
    Sharad Verma

  • 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.

  • 2LIS_03_UM - FULL LOAD VIA SETUP TABLE NOT EQUAL TO DELTA

    Hello,
    I try to load stock data with 2LIS_03_UM.
    When I extract data using setup table and full load I don't get the same records as I get with delta load. Although the key figures values are the same, the documents numbers are different. Most documents from delta load are ML (material ledger) documents while documents from full load (via setup table) are mainly FI documents.
    What can be the reason? How can I fix it?
    Thank you,
    Hadar

    Hi,
    Delta load extracts data from Delta Queue based on your update mode selected in LBWE.
    Full Load or Init load extracts data from Setup tables, here if you are extracting data from setup tables ? did you fill the setup tables now or not after deleting the existing data of the setup tables?
    are you getting same values when compare to R/3 and BW data for some document numbers?

  • Use of Update Table in Delta Extraction ....

    Hi all ,
           I have a small doubt regarding why there is an update table introduced between statistical table and delta queue in delta extraction process ... why not directly extract data from the statastical table and put it in to the delta queue .....
    Kindly help me regarding this ...
    Regards ,
    Santosh ....

    Hi Santosh,
    I think it is related to resource, batch and memory, problem. Infact you can use only delta queue if you select direct update, but you use this kind of update only for huge amount of data produced in a short period of time.
    The two queue let you divide transaction moment to batch collection moment.
    Hope this help.
    Ciao.
    Riccardo.

  • Time-stamp Table for delta extraction

    Hi SDNers,
    What are the BW Time-stamp Tables for delta extraction in Source System(R/3).
    Thanks,
    Satya

    the tables involved are :
    ROOSPRMS
    ROOSPRMSC
    ROOSPRMSF
    in the second table (ROOSPRMSC) you'll find the timestamp
    M.

  • Delta Extraction: Cross Application Table

    Hello Gurus,
    While enhancing an LO extractor, I understand that we need to create a structure with the fields needed for extraction and then append this to the main extract structure and populate this through the user exit. Now what I am worried about is if the fields happend to be a from a cross application table, how the delta would be taken care of?
    As an Example, if I need to add in couple of fields of the delivery tables (LIPS and LIKP) in the Purchasing extractor (2LIS_02_SCL), am I going to get changed fields during the delta extraction?
    Thanks...

    Is that always true? Please look through the following scenario that Sunmit mentioned in response to Roberto's one of the blogs:
    If a scenario demands a cross application enhancement
    eg: Enhancing shipment relevant field in a delivery data source/extractor or delivery relevant field in an invoice relevant data source.
    Is the delta relevance of these enhanced fields retained by enhancing the datasource at communication structure level? I guess, the delta of these enhanced fields would still be lost, since they are not included in the events that are used to create the delta.
    (ie a shipment document (our field) may change without change in delivery document).
    Any ideas???

  • What are the disadvantages of generic delta extraction

    Hi all,
    what are the disadvantages of generic delta extraction.
    how function module generic extraction works.
    Thanks,
    Madhu.

    hi madhu,
    Pls refer ths,To learn more about Generic Extraction pls read BW350 book.
    Gereric Extraction can be done in 3 ways.
    If you go to transaction RSO2 in R/3 side, provide tech name for data source and click create.
    you will get the 3 options.
    1)From a DB Table
    2)From a DB View
    3)From Functional module/ Infoset Query
    in first option you can directly give a standard or custom build talbe name. in second option you can select the necessary fields from more than one talbe(eiter standard or custom). In third option you will create a function module or Query to extract data. When creating function modules you can use standard function modules as a template e.g. RSAX_BIW_GET_DATA_SIMPLE.
    see weblog : /people/siegfried.szameitat/blog/2005/09/29/generic-extraction-via-function-module
    If you want to enable delta for generic extractor you choose the option delta and provide necessary settings.
    Generic extraction is when your extraction is not satisfied by either BC or LIS/LO. It can be using a view / query/table/FM
    Here the changed records can be isentified by :
    1. Based on the date of creation or last change ( Delta based on 0Calday)
    2. Based on the record number ( Numeric Pointer )
    3. Based on time of change ( Timestamp)
    real time examples would be
    1. Master Record creation like customer ID creation
    2. Timesheets in SAP PS
    3. Invoive details / Sales Order Details.
    Pls check this web logs for clear Idea.
    /people/siegfried.szameitat/blog/2005/09/29/generic-extraction-via-function-module
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33
    Have a look at these threads too.
    Tables
    Transfer Structure
    The steps for creating extractor using Function Module.
    1. Create new Function group (if you have already not done so) in Se80
    2. Copy Function module "RSAX_BIW_GET_DATA_SIMPLE" with suitable name.
    3. Change the code that populate data.
    Following table may give you the guideline for parameters.
    Parameter Description
    I_REQUNR (import) BW provides this request identifier. It is a system-generated identifier in the form REQU_XXXXXX. BW uses this same identifier in all function module calls that relate to a single load.
    I_DSOURCE (import) The name of the generic extractor
    I_MAXSIZE (import) The maximum number of records that BW expects to be in each data packet
    I_INITFLAG (import) A Boolean flag that indicates if this is the initialization (first) call to the function module
    I_READ_ONLY (import) A test flag not needed in most extraction scenarios
    I_T_SELECT (table) This table holds any selections from the BW InfoPackage. The function module should examine these selections and only return data that matches the selections.
    I_T_FIELD (table) This table holds the fields that BW requests
    E_T_DATA (table) The function module fills this table with data records. These records then return to BW as data packets. This table has the same structure as the extract structure defined in the generic DataSource.
    NO_MORE_DATA (exception) The function module raises this exception when no more data is available
    ERROR_PASSED_TO_MESS_HANDLER (exception) The function module raises this exception if an error occurred during the extraction. It alerts BW to check for error logs.
    Change following code to put the selection fields
    Select ranges
    RANGES: L_R_CARRID FOR SFLIGHT-CARRID,
    L_R_CONNID FOR SFLIGHT-CONNID.
    Change following to populate data
    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.
    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.
    Some more links:
    Re: functionmodule
    Re: FM for G. extractor
    with hopes
    Raja Singh

  • Error while doing DELTA Extraction

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

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

  • Error while doing DELTA Extraction (generic data source)

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

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

  • No purchasing date in delta extraction (2LIS_02_ITM, 2LIS_02_SCL)

    Hi.
    We have been experiencing some issues with delta extraction of purchasing data, using 2LIS_02_ITM and 2LIS_02_ITM.
    In particular, the posting date's field (BUDAT) is not always filled: for example, I noticed that when users set the final delivery flag even if the purchase delivered quantity does not correspond to the whole order's quantity or the flag has been set later than the change of the delivery date, the field (BUDAT) in the delta queue is not filled.
    By this way, the field may be overwritten: however, we need to keep the posting date value.
    I am wondering whether I am correct and, in this case, it is possible to keep that value: however, it seems that the only way is to use a full extraction of data.
    Thanks a lot

    Roberto Negro,
    While filling setup table by using T-code OLI3BW (Purchasing) it is taking very long time.
    Please let me is there any way to rerduce this time.
    We are at BW 7.3 version.
    Regards,

  • 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

  • Problem in Delta Extraction

    Hi Firends,
    I created a DS out of a  Function module. The source table is a Z table with following data
    MANDT MATNR                WERKS  STLNR    ANDAT      AEDAT      AENAM        VALUE
    100   000000000000000184   1500   00001500 18.08.2006 15.08.2006 SANDEEP      0000002500
    100   000000000000000364   KOPL   00001825 19.08.2006 17.08.2006 SASI         0000003500
    100   AUDCOMAT12           1111   00001980 22.12.2006 22.12.2006 DEVELOPER    0000005600
    100   AUDCOMAT12           1500   00001500 15.08.2006 15.08.2006 DEVELOPER    0000001600
    My FM is as follows:-
    FUNCTION ZSAN_BIW_MAST1.
    ""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
    *"  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  ZSAN_MAST OPTIONAL
    *"  EXCEPTIONS
    *"      NO_MORE_DATA
    *"      ERROR_PASSED_TO_MESS_HANDLER
    Example: DataSource for table SFLIGHT
      TABLES: ZSAN_MAST.
    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_MATNR  FOR ZSAN_MAST-MATNR,
              L_R_AEDAT  FOR ZSAN_MAST-AEDAT.
    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 'ZSAN_DS_MAST'.
          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.
    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 = 'MATNR'.
            MOVE-CORRESPONDING L_S_SELECT TO L_R_MATNR.
            APPEND L_R_MATNR.
          ENDLOOP.
          LOOP AT S_S_IF-T_SELECT INTO L_S_SELECT WHERE FIELDNM = 'AEDAT'.
            MOVE-CORRESPONDING L_S_SELECT TO L_R_AEDAT.
            APPEND L_R_AEDAT.
          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 ZSAN_MAST
                                   WHERE  AEDAT  gt L_R_AEDAT-LOW.
        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 did the initializiation with out data transfer and it pulled one record as expected.
    But when i do a delta update it dosent pull any record from the table inspite of having ---" AEDAT  gt L_R_AEDAT-LOW. " in my code.
    As per me it should have pulled 2 records from my ZTable, the 2nd and 3rd record, but it dosen't
    I made the delta on AEDAT field and the
    'Date of Last change' in Generic Delta is - '16.08.2006'.
    Can any one suggest what the problem could be ?
    Thanks
    Regards,
    Dutta

    Without knowing everything, here is an example of what I have done. This FM extracts MARC changes on specific fields.
    FUNCTION ZBSV_BW_EXTRACT_MARC_CNGS.
    ""Local interface:
    *"  IMPORTING
    *"     REFERENCE(I_DSOURCE) TYPE  SRSC_S_IF_SIMPLE-DSOURCE OPTIONAL
    *"     REFERENCE(I_INITFLAG) LIKE  RSAAPI_IF-INITFLAG OPTIONAL
    *"     REFERENCE(I_MAXSIZE) TYPE  SRSC_S_IF_SIMPLE-MAXSIZE OPTIONAL
    *"     REFERENCE(I_REQUNR) TYPE  SRSC_S_IF_SIMPLE-REQUNR OPTIONAL
    *"  TABLES
    *"      I_T_SELECT STRUCTURE  RSSELECT OPTIONAL
    *"      I_T_FIELDS STRUCTURE  RSFIELDSEL OPTIONAL
    *"      E_T_DATA STRUCTURE  CDRED OPTIONAL
    *"  EXCEPTIONS
    *"      NO_MORE_DATA
    *"      ERROR_PASSED_TO_MESS_HANDLER
    FM: ZBSV_BW_EXTRACT_MARC_CNGS
    Author: Steve Wilson
    Dev. Class: ZZBW
    Date: 11/29/2005
    Description:
    This FM is used to collect relevant MARC Changes
    This BIW FM uses an SAP Standard FM to collect Change documents.
    There are only 4 fields we care about checking changes on currently.
    Mod date  Programmer    Reference   Description
    06SEP05   Steve W.      CA2K930787  Initial Development ip: 2877190
                   DATA DECLARATION                                      *
      RANGES:  R_DATUM FOR SYST-DATUM.   "Change date
      REFRESH: S_DATUM.
    Maximum number of lines for DB table
      STATICS: S_S_IF TYPE SRSC_S_IF_SIMPLE,
    counter
       S_COUNTER_DATAPAKID LIKE SY-TABIX,
       START_IDX LIKE SY-TABIX,
       END_IDX LIKE SY-TABIX.
                  BEGIN OF PROCESSING                                    *
      IF I_INITFLAG = SBIWA_C_FLAG_ON.
    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.
      ELSE.
    First data package
        IF S_COUNTER_DATAPAKID = 0.
        get changed date selection
          LOOP AT I_T_SELECT WHERE FIELDNM EQ 'UDATE'.
            R_DATUM-SIGN = I_T_SELECT-SIGN.
            R_DATUM-OPTION = I_T_SELECT-OPTION.
            R_DATUM-LOW = I_T_SELECT-LOW.
            R_DATUM-HIGH = I_T_SELECT-HIGH.
            IF R_DATUM-HIGH EQ SPACE.
             R_DATUM-HIGH = '99991231'.
            ENDIF.
            APPEND R_DATUM.
            EXIT. "Only want 1 record, ignore others
          ENDLOOP.
          CALL FUNCTION 'CHANGEDOCUMENT_READ'
            EXPORTING
              ARCHIVE_HANDLE                   = 0
            CHANGENUMBER                     = ' '
              DATE_OF_CHANGE                   = R_DATUM-LOW
              OBJECTCLASS                      = 'MATERIAL'
            OBJECTID                         = ' '
            TABLEKEY                         = ' '
              TABLENAME                        = 'MARC'
              TIME_OF_CHANGE                   = '000000'
            USERNAME                         = ' '
            LOCAL_TIME                       = ' '
              DATE_UNTIL                       = R_DATUM-HIGH
              TIME_UNTIL                       = '235959'
            TABLES
              EDITPOS                          = ITAB_CDRED
           EXCEPTIONS
             NO_POSITION_FOUND                = 1
             WRONG_ACCESS_TO_ARCHIVE          = 2
             TIME_ZONE_CONVERSION_ERROR       = 3
             OTHERS                           = 4.
          IF SY-SUBRC <> 0.
           RAISE NO_MORE_DATA.
          ELSE.
           LOOP AT ITAB_CDRED. "Keep fields
            IF ITAB_CDRED-FNAME+0(5) NE 'DISPO' AND
               ITAB_CDRED-FNAME+0(5) NE 'EISBE' AND
               ITAB_CDRED-FNAME+0(5) NE 'BSTRF' AND
               ITAB_CDRED-FNAME+0(5) NE 'SHZET'.
              DELETE ITAB_CDRED.
            ENDIF.
           ENDLOOP.
          LOOP AT ITAB_CDRED. "Keep Factories
            IF ITAB_CDRED-TABKEY+21(4) NE 'LX01' AND
              ITAB_CDRED-TABKEY+21(4) NE 'LX09' AND
              ITAB_CDRED-TABKEY+21(4) NE 'ZX01' AND
              ITAB_CDRED-TABKEY+21(4) NE 'CE01' AND
              ITAB_CDRED-TABKEY+21(4) NE 'CC01'.
             DELETE ITAB_CDRED.
            ENDIF.
          ENDLOOP.
          ENDIF.
          DESCRIBE TABLE ITAB_CDRED LINES COUNTER.
          APPEND LINES OF ITAB_CDRED FROM 1 TO I_MAXSIZE TO E_T_DATA .
          END_IDX = I_MAXSIZE.
          S_COUNTER_DATAPAKID = S_COUNTER_DATAPAKID + 1.
        ELSE.
          IF END_IDX GE COUNTER.
            RAISE NO_MORE_DATA.
          ENDIF.
          START_IDX = END_IDX + 1.
          END_IDX = ( START_IDX + I_MAXSIZE ) - 1.
          APPEND LINES OF ITAB_CDRED FROM START_IDX TO END_IDX
                                                        TO E_T_DATA.
          S_COUNTER_DATAPAKID = S_COUNTER_DATAPAKID + 1.
        ENDIF.
      ENDIF.

  • PCA doment missing during the delta extraction

    Hi R/3 DBA experts,
    We are using Oracle 10g Data base for our ECC6.0 R/3 system.During BW extraction some of the PCA line item records got missed which gets update in data base table GLPCA in R/3 after successful document creation.
    We are in the process of analysis to find out the root cause of the issue as we are approaching year end close.
    Please let me know how to get the following logs(Information) in R/3
    1.Total time taken in Application server for a particular document which was Entered.
    2.Total time taken for a document from posting(Document entry) to successful data base server update.
    (OR Application server to Data base server update log details OR Document posting to DB write for a document)
    Please treat this as a matter of urgency
    Regards
    Kumar

    Hi,
    To move the data from Update Tables to Delta Queue, u need to run the V3 Job Control in LBWE. Once if the job is successfully completed then all the data from Update tables are moved to Delta Queue. Check once in the job overview of V3 job control is there any errors.
    Hope this helps in solving u r problem
    Regards
    Ramakrishna Kamurthy

Maybe you are looking for