Incorrect data in ODS

Hi All,
we are loading data  from one ODS to another with delta processes.The second ODS got some incorrect data Populated.After that I did a full repair load selectively for one record only from first ODS to another and it went fine.But when I am loading by full repair load the records for entire company code,one particular key figure is getting doubled for most of the records.I've checked there is no problem with the start routine.
Please  let me know if I am missing anything in full repair load.
Thanks in advance.

Hi,
In sequence to this post,now i am getting a differnt and strange error.
the data gets loaded from ODS1(0FIA_DS11) to ODS2(0FIA_DS12).
But for some asset main nos the CACQ_VL_YR and TACQ_VL_YR does not get populated.
WE have a start routine in between.The start routine poplualtes the CACQ_VL_YR .TACQ_VL_YR is polulated with ACQ_VAL_TR.
the routine is as follows:
DATA: lt_trans LIKE table of DATA_PACKAGE,
         wa_trans LIKE LINE OF lt_trans.
  LOOP AT DATA_PACKAGE.
    CLEAR wa_trans.
Nicht-Werfelder 1:1 übernehmen
    MOVE: DATA_PACKAGE-currency   TO wa_trans-currency ,
          DATA_PACKAGE-comp_code  TO wa_trans-comp_code ,
          DATA_PACKAGE-/BIC/ZASS_MAIN TO wa_trans-/BIC/ZASS_MAIN ,
          DATA_PACKAGE-/BIC/Zdep_area TO wa_trans-/BIC/Zdep_area ,
          DATA_PACKAGE-fiscyear   TO wa_trans-fiscyear,
          DATA_PACKAGE-fiscvarnt  TO wa_trans-fiscvarnt.
Wertfelder mit identischer Übertragungslogik bei PLN und ***
    MOVE:
    DATA_PACKAGE-vaw_odp_tr TO wa_trans-vaw_odp_tr,
    DATA_PACKAGE-vaw_sdp_tr TO wa_trans-vaw_sdp_tr,
    DATA_PACKAGE-vaw_udp_tr TO wa_trans-vaw_udp_tr,
    DATA_PACKAGE-vaw_avr_tr TO wa_trans-vaw_avr_tr,
    DATA_PACKAGE-va_rapc_tr TO wa_trans-va_rapc_tr,
    DATA_PACKAGE-va_rodp_tr TO wa_trans-va_rodp_tr,
    DATA_PACKAGE-va_invs_tr TO wa_trans-va_invs_tr.
    CASE DATA_PACKAGE-transtype.
      WHEN '***'.
    Wertfelder kumuliert
        MOVE:
        DATA_PACKAGE-acq_val_tr TO wa_trans-cacq_vl_yr,
        DATA_PACKAGE-inv_sup_tr TO wa_trans-cinv_gr_yr,
        DATA_PACKAGE-ord_dep_tr TO wa_trans-cor_dep_yr,
        DATA_PACKAGE-spc_dep_tr TO wa_trans-csp_dep_yr,
        DATA_PACKAGE-upl_dep_tr TO wa_trans-cup_dep_yr,
        DATA_PACKAGE-res_trf_tr TO wa_trans-cres_tr_yr,
        DATA_PACKAGE-interst_tr TO wa_trans-cinter_yr,
        DATA_PACKAGE-reval_tr   TO wa_trans-crev_rv_yr,
        DATA_PACKAGE-rev_odp_tr TO wa_trans-crev_od_yr.
        COLLECT wa_trans INTO lt_trans.
    Wertfelder geplant
      WHEN 'PLN'.
        MOVE:
        DATA_PACKAGE-acq_val_tr TO wa_trans-acq_val_tr,
        DATA_PACKAGE-inv_sup_tr TO wa_trans-inv_sup_tr,
        DATA_PACKAGE-ord_dep_tr TO wa_trans-plo_dep_yr,
        DATA_PACKAGE-spc_dep_tr TO wa_trans-pls_dep_yr,
        DATA_PACKAGE-upl_dep_tr TO wa_trans-upl_dep_yr,
        DATA_PACKAGE-res_trf_tr TO wa_trans-pln_avr_yr,
        DATA_PACKAGE-interst_tr TO wa_trans-pln_int_yr,
        DATA_PACKAGE-reval_tr   TO wa_trans-prev_rv_yr,
        DATA_PACKAGE-rev_odp_tr TO wa_trans-prev_aodyr.
        COLLECT wa_trans INTO lt_trans.
   'echte' Bewegungen ignorieren.
      WHEN OTHERS.
    ENDCASE.
  ENDLOOP.
  DATA_PACKAGE[] = lt_trans[].
if abort is not equal zero, the update process will be canceled
  ABORT = 0.
Can anyone throw some light on this?
Regards,
Dhanya.

Similar Messages

  • Error Assigning SID-cannot load data in ods

    Hi
    I have data in ODS coming from R/3.
    Uptil today data was loading and working fine.
    When i tried to load the data today, i am getting an error. Data is in PSA
    Data is also seems to be in ods, because the request is in red color, but reporting icon is still available.
    and Datamart status is empty.
    I checked the call log and found the following error.
    Overview of Call log is as follows
    Activation of Data
    SID Generation
    Data package 3 : Error when assigning SID: Action VAL_SID_CONVERT InfoObject 0DATEFROM
    Value '01012009' of characteristic 0DATE is not plausible
    Data package 6: Error when assigning SID: Action VAL_SID_CONVERT InfoObject 0DATETO
    Value '31122009' of characteristic 0DATE is not plausible 1
    Rest all packages for the various infoobjects are loaded successfully
    I think there is a problem in data, but i dont know how to resolve the issue
    please help
    Regards

    Hi,
       The problem that you are facing is that your format is YYYYMMDD and you are trying to load data in format DDMMYYYY.
       The error is the current request, you dont need to touch anything else. As i said earlier, goto the RSMO transaction, find your failed load. Click on it. On the right side of your screen, you will get the individual monitor, which has a status tab. On this tab, there would be a button which says error message. Click on it.
    It will give you several messages. If you scroll to the right, there would be a ? symbol for long text. Click on it.
    This will give you further info. One of these messages will have the record no and package no. You need to check all messages. Then go to your PSA, to the same package and record and check the date format
    Another way is to goto SE16-> find the active table of your DSO, it will be named as /BIC/A<DSO NAME>40
    Search the respective date field for the value thrown in the error, or you can use the record no obtained from above to find the value. Find the key fields and note them down.
    You then need to delete the incorrect request from your DSO. You can then correct the incorrect record in your PSA ,using the key fields,save and reconstruct this request.
    Hope this helps.
    Regards.

  • Is there any way for updating wrong data in ODS and infocube?

    Hi all
        Is there any way for correcting wrong data in ODS and infocube?

    You could do a selective deletion, by specifying the filter values, so that you only delete a subset of the entire data. You could then do a re-load for the same selection so that there is no duplication of records.
    This is on the assumption, that your incorrect data is due to some incorrect update or transfer rules, which you have now corrected (before the re-load).
    mate, you have mentioned that You could then do a re-load for the same selection .
    could you please tell me how to do a re-load ?   thank you very much

  • Append data in ODS

    Hey Folks,
    I load data into an ODS, weekly. The data contains status information of a product.
    The source system delivers only data where the status has changed.
    If the status for on product is constant over two or more weeks, I get no record of this product for the current week. But I want to display the status for this product in the current week.
    So I need to insert records in my ODS for all products where I don't get a record from the source system for the current week.
    I got the information that I need a start routine and implement my logic with ABAP
    There are any other ways, or can somebody explain me, how to do this with ABAP?
    Thanks for your help!
    Stephan

    Hi Stephan,
          Please try this logic.
    Load the transaction data for the ODS weekly as per you source sytem data.
    Now you need to update based on constant status. You can write a ABAP program with the below logic.
    Create internal tables for Master Data and ODS and read all the contents into it.
    Get the details from Master Data and manually update the status field (No data from source system)and store it in a internal table (Internal table - Same strcuture as that of active records table /BIC/AZ***)which has records to be appended to the ODS.
    Append it to the active records table of the ODS.
    Hope this helps.
    Thanks,
    Srinivas.

  • Activate data in ODS

    Hi Gurus,
    Im loading data from ods to ods thru full update and after that I have to activate that ODS,
    Kindly let me know the steps for activating the ODS,
    right click on the ods and press activate data n  ods
    or before i have to do Update ods in data target.
    Raj

    1ST we have to go for ODS in Data target and right click on the ODS.
    In that options click on Generate Export Data Source.Then go to Source system to identify the Data Source.
    It will starts with 8 later What everyou had given the ODS name you have to give in Search.
    Later you have to create infopackage for that ODS and load data in to that IP.
    next come to Data Target and create the new ODS.
    Give the update rules with the data source what ever you had created now.
    later you have to create info Package for that ODS and load the data for that IP.
    Hope it will helps you..........

  • Activating Data in ODS

    Hi
    I have got one ODS, for which my infopackage is desigen as do not update data if no master data exists for a characteristic.
    But one of my request which is having only the entries in master data, is not getting activated in ODS.Its failing with the error "No SID found for value '00DU023R ' of characteristic 0MATERIAL". but the material 00DU023R is not there in the request at all.
    Doest anyone phased this scenario before? how to activate the data in ODS?
    Regards
    Sriram

    Hi Sriram,
    What SSree is trying to see.
    Go to your ODS, right click manage.
    In the requests tab, choose a very old date and choose refresh.  Now check if you see any red requests.  These requests will prevent from activating.
    On the other hand, when I see your first error, I would go to transaction RSRV, and do some consistency checks on your ODS and master data.
    kr,
    Tom

  • No data in ODS

    Hi Friends,
               I don’t see any data in my ODS, My loading went fine, then I went to my ODS , Right click > Activate data in ODS , what must be the problem??
    thanks in advance,

    ODS >Context Menu>Manage
    Go to content tab, check the tables (active, new). It should be in one of the tables.
    Is activation over?

  • Deleting data in ODS

    HI Kudos!
    Please let me know the methods of deleting the data in ODS of all the tables before and after activation. Let me know if any blogs are there.
    thanks in advance.
    kalyan Pidugu.

    Hi Kalyan,
    As Malli mentioned those are the ways you can delete the data...again it depends on the update mode used for data loads. If it is a delta load from R3 make sure u mark it as red before deleting so you dont loose data from subsequent deltas.
    if it is full update and if u wish to delete it u can simply delete it coz BW will mark it as red.
    What is it do u want to know abt activation?
    Assign points if useful
    Arun

  • Data in New Data in ODS

    Hello,
    I am trying to load data from r/3 into the ODS.
    When i check in the monitor its saying that
    07:37:12 ( 549741 from 549741 Records )
    But its not turning green.Its still yellow.
    I checked the new data in the ODS. The number of entries in it is 0.

    Hi
    You can view the data in ODS only after the status is green.
    Check if it is showing any error in the description.
    If not then wait for some time. we can't do anything as is it showing yellow(in process) status
    Cheers
    SM

  • Data in ods

    Hai Experts,
    Can any body tell me data is present in active data table, new data table, change log table and as wel as with this there is a content button it is asking for the table name what is that button consists of can any body help me out
    Regards,
    Vikram

    Hi Vikram,
    If we right click ODS --> go to Manage --> contents Tab
    You will find three Tables
    1. New Table : when you load Data initially it gets into New Table and if you click on that you can see the Content
    2. Active and Change Log : when you Activate data in ODS the Data moves from new to active and change log Tables and used for futher processsing to other Data Targets like Cube or ODs again.
    Change Log Table records all the changes happend to the data.
    Check this blog for more  info
    /people/raj.alluri/blog/2006/11/24/the-tech-details-of-standard-ods-dso-in-sap-dwh
    Hope this helps,
    Sudhakar.

  • Data in ODS, Info cube ans Multiprovider(List cube) are in Sync.

    Hi,
    My query is built on multiprovider. The data flow is data source u2013 ODS then ODS u2013 Info cube and multiprovider contains  Info cube only.
    Data in ODS, Info cube ans Multiprovider(List cube) are in Sync.
    The query results are not tie up ODS, Info cube ans Multiprovider(List cube).
    Any one let me know why this is happening and how do I resolve it.
    Regards,
    Sharma.

    HI;
    thanks for help.
    I resolved the issue in my own.
    Regards,
    Sharma.

  • Errors when loading data to ODS

    Hi,
    I am getting the following dump when loading data to ODS
    whta might be the problem
    Runtime Error          MESSAGE_TYPE_X
    Date and Time          29.09.2006 14:26:52
    ShrtText
    The current application triggered a termination with a short dump.
    What happened?
    The current application program detected a situation which really
    should not occur. Therefore, a termination with a short dump was
    triggered on purpose by the key word MESSAGE (type X).
    What can you do?
    Print out the error message (using the "Print" function)
    and make a note of the actions and input that caused the
    error.
    To resolve the problem, contact your SAP system administrator.
    You can use transaction ST22 (ABAP Dump Analysis) to view and administer
    termination messages, especially those beyond their normal deletion
    date.
    is especially useful if you want to keep a particular message.
    Error analysis
    Short text of error message:
    Test message: SDOK_GET_PHIO_ACCESS 001
    Technical information about the message:
    Message classe...... "1R"
    Number.............. 000
    Variable 1.......... "SDOK_GET_PHIO_ACCESS"
    Variable 2.......... 001
    Variable 3.......... " "
    Variable 4.......... " "
    Variable 3.......... " "
    Variable 4.......... " "
    How to correct the error
    Probably the only way to eliminate the error is to correct the program.
    You may able to find an interim solution to the problem
    in the SAP note system. If you have access to the note system yourself,
    use the following search criteria:
    "MESSAGE_TYPE_X" C
    "SAPLSDCL" or "LSDCLF00"
    "INTERNAL_ERROR"
    If you cannot solve the problem yourself and you wish to send
    an error message to SAP, include the following documents:
    1. A printout of the problem description (short dump)
    To obtain this, select in the current display "System->List->
    Save->Local File (unconverted)".
    2. A suitable printout of the system log
    To obtain this, call the system log through transaction SM21.
    Limit the time interval to 10 minutes before and 5 minutes
    after the short dump. In the display, then select the function
    "System->List->Save->Local File (unconverted)".
    3. If the programs are your own programs or modified SAP programs,
    supply the source code.
    To do this, select the Editor function "Further Utilities->
    Upload/Download->Download".
    4. Details regarding the conditions under which the error occurred
    or which actions and input led to the error.
    System environment
    SAP Release.............. "640"
    Application server....... "bomw093a"
    Network address.......... "132.186.125.66"
    Operating system......... "Windows NT"
    Release.................. "5.2"
    Hardware type............ "4x Intel 801586"
    Character length......... 8 Bits
    Pointer length........... 32 Bits
    Work process number...... 16
    Short dump setting....... "full"
    Database server.......... "BOMW093A"
    Database type............ "ORACLE"
    Database name............ "BIW"
    Database owner........... "SAPDAT"
    Character set............ "English_United State"
    SAP kernel............... "640"
    Created on............... "Nov 4 2004 23:26:03"
    Created in............... "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
    Database version......... "OCI_920_SHARE "
    Patch level.............. "43"
    Patch text............... " "
    Supported environment....
    Database................. "ORACLE 8.1.7.., ORACLE 9.2.0.."
    SAP database version..... "640"
    Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
    Memory usage.............
    Roll..................... 8112
    EM....................... 6271776
    Heap..................... 0
    Page..................... 24576
    MM Used.................. 3921120
    MM Free.................. 258392
    SAP Release.............. "640"
    User and Transaction
    Client.............. 800
    User................ "IC881147"
    Language key........ "E"
    Transaction......... " "
    Program............. "SAPLSDCL"
    Screen.............. "SAPMSSY0 1000"
    Screen line......... 6
    Information on where terminated
    The termination occurred in the ABAP program "SAPLSDCL" in "INTERNAL_ERROR".
    The main program was "RSRD_BROADCAST_PROCESSOR ".
    The termination occurred in line 25 of the source code of the (Include)
    program "LSDCLF00"
    of the source code of program "LSDCLF00" (when calling the editor 250).
    The program "SAPLSDCL" was started as a background job.
    Job name........ "SECOQUERY"
    Job initiator... "IC881147"
    Job number...... 14265102
    Source Code Extract
    Line
    SourceCde
    1
    2
      INCLUDE LSDCLF00                                                   *
    3
    4
    5
    6
          FORM INTERNAL_ERROR                                           *
    7
    8
          Handles unexpected error conditions (internal errors)
    9
    10
    -->  VALUE(U_ROUTINE)    Routine/function module where error occured
    11
    -->  VALUE(U_ERROR_CODE) Identifier in routine (e.g. number)
    12
    -->  VALUE(U_VAR1)       Variable containing further information
    13
    -->  VALUE(U_VAR2)       Variable containing further information
    14
    -->  VALUE(U_VAR3)       Variable containing further information
    15
    -->  VALUE(U_VAR4)       Variable containing further information
    16
    17
    form internal_error
    18
    using value(u_routine)
    19
    value(u_error_code)
    20
    value(u_var1)
    21
    value(u_var2)
    22
    value(u_var3)
    23
    value(u_var4).
    24
    >>>>>
    message x000 with u_routine u_error_code u_var1 u_var2.
    26
    27
    endform.
    28
    29
    30
    *&      Form  BAD_OBJECT_TO_SYMSG
    31
    32
          maps error information in u_bad_object into system message
    33
          variables
    34
    35
    -->  VALUE(U_BAD_OBJECT)  structure containing error information
    36
    37
    form bad_object_to_symsg
    38
    using value(u_bad_object) type sdokerrmsg.
    39
    40
    sy-msgid = u_bad_object-id.
    41
    sy-msgty = u_bad_object-type.
    42
    sy-msgno = u_bad_object-no.
    43
    sy-msgv1 = u_bad_object-v1.
    44
    sy-msgv2 = u_bad_object-v2.
    Contents of system fields
    Name
    Val.
    SY-SUBRC
    0
    SY-INDEX
    0
    SY-TABIX
    1
    SY-DBCNT
    4
    SY-FDPOS
    0
    SY-LSIND
    0
    SY-PAGNO
    0
    SY-LINNO
    1
    SY-COLNO
    1
    SY-PFKEY
    SY-UCOMM
    SY-TITLE
    Report Dissemaintion Framework: Executing the Transferred Settings
    SY-MSGTY
    X
    SY-MSGID
    1R
    SY-MSGNO
    000
    SY-MSGV1
    SDOK_GET_PHIO_ACCESS
    SY-MSGV2
    001
    SY-MSGV3
    SY-MSGV4
    Active Calls/Events
    No.   Ty.          Program                             Include                             Line
    Name
    15 FORM         SAPLSDCL                            LSDCLF00                               25
    INTERNAL_ERROR
    14 FORM         SAPLSDCI                            LSDCIU13                              303
    PHIO_GET_CONTENT_ACCESS
    13 FUNCTION     SAPLSDCI                            LSDCIU13                              113
    SDOK_PHIO_GET_CONTENT_ACCESS
    12 FUNCTION     SAPLSKWF_CONTENT                    LSKWF_CONTENTU02                       63
    SKWF_PHIO_CONTENT_ACCESS_GET
    11 METHOD       CL_RSRA_KWF_UTILITIES=========CP    CL_RSRA_KWF_UTILITIES=========CM00B    50
    CL_RSRA_KWF_UTILITIES=>COPY_MIME_TO_FOLDER
    10 METHOD       CL_RSRA_KWF_TMPL==============CP    CL_RSRA_KWF_TMPL==============CM002    28
    CL_RSRA_KWF_TMPL=>GET_STYLESHEET
    9 METHOD       CL_RSRA_KWF_TMPL==============CP    CL_RSRA_KWF_TMPL==============CM001   227
    CL_RSRA_KWF_TMPL=>CONSTRUCTOR
    8 METHOD       CL_RSRA_ENGINE_BC=============CP    CL_RSRA_ENGINE_BC=============CM010     9
    CL_RSRA_ENGINE_BC=>SET_TEMPLATE_FOLDER
    7 METHOD       CL_RSRA_ENGINE_BC=============CP    CL_RSRA_ENGINE_BC=============CM001    75
    CL_RSRA_ENGINE_BC=>CONSTRUCTOR
    6 METHOD       CL_RSRA_JOB===================CP    CL_RSRA_JOB===================CM003    47
    CL_RSRA_JOB=>EXECUTE_SINGLE
    5 METHOD       CL_RSRA_JOB===================CP    CL_RSRA_JOB===================CM00E    14
    CL_RSRA_JOB=>EXECUTE_SINGLE_RC
    4 METHOD       CL_RSRD_PRODUCER_RA===========CP    CL_RSRD_PRODUCER_RA===========CM001   147
    CL_RSRD_PRODUCER_RA=>IF_RSRD_F_PRODUCER_RT~PRODUCE
    3 METHOD       CL_RSRD_SETTING===============CP    CL_RSRD_SETTING===============CM005    28
    CL_RSRD_SETTING=>EXECUTE_NODES
    2 METHOD       CL_RSRD_SETTING===============CP    CL_RSRD_SETTING===============CM002    73
    CL_RSRD_SETTING=>EXECUTE
    1 EVENT        RSRD_BROADCAST_PROCESSOR            RSRD_BROADCAST_PROCESSOR              197
    START-OF-SELECTION
    Chosen variables
    Name
    Val.
    No.      15 Ty.          FORM
    Name  INTERNAL_ERROR
    U_ROUTINE
    SDOK_GET_PHIO_ACCESS
    54445445554445444455
    34FBF754F089FF133533
    SY-MSGV1
    SDOK_GET_PHIO_ACCESS
    54445445554445444455222222222222222222222222222222
    34FBF754F089FF133533000000000000000000000000000000
    U_ERROR_CODE
    001
    333
    001
    SY-MSGV2
    001
    33322222222222222222222222222222222222222222222222
    00100000000000000000000000000000000000000000000000
    U_VAR1
    2
    0
    SY-MSGV3
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    SDOKI_MODE_DELETE
    5
    0000
    5000
    U_VAR2
    2
    0
    SY-MSGV4
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    No.      14 Ty.          FORM
    Name  PHIO_GET_CONTENT_ACCESS
    SYST
    ####################################################A#######P###############è#################
    0000000000000000000000000000000000000000000000000000400000005000000000000000E00000000000000000
    0000000010002000000000000000000000000000400000001000100010000000000000000000840000000000000000
    PHIO_OBJECT_ID-CLASS
    2222222222
    0000000000
    DUMMY_VERSTYPE
    0
    3
    0
    DUMMY_FCT_EXPORT
    222222222222222222222222222222
    000000000000000000000000000000
    DUMMY_FCT_IMPORT
    222222222222222222222222222222
    000000000000000000000000000000
    DUMMY_FCT_DELETE
    222222222222222222222222222222
    000000000000000000000000000000
    FCT_VIEW
    222222222222222222222222222222
    000000000000000000000000000000
    BUFF_XPIRE
    000000000000
    333333333333
    000000000000
    NO_BUFFER
    2
    0
    SUBRC_AUX
    3
    0000
    3000
    SDOKA_EVENT_PH_FROM_REL_PRE
    0022
    3333
    0022
    SCREEN
    %_17SNS0001592815_%_%_%_%_%_%_
    2533545333333333352525252525252222222222222222222222222222222222222222222222222222222222222222
    5F173E30001592815F5F5F5F5F5F5F0000000000000000000000000000000000000000000000000000000000000000
    <%_TABLE_SDOKSTRE>
    SY-XFORM
    CONVERSION_EXIT
    444545544454545222222222222222
    3FE65239FEF5894000000000000000
    CONTEXT[]
    Table IT_5544[0x89]
    FUNCTION=SKWF_PHIO_CONTENT_ACCESS_GETDATA=CONTEXT[]
    Table reference: 324
    TABH+  0(20) = 00000000801CE03C0000000044010000A8150000
    TABH+ 20(20) = 0000000059000000FFFFFFFF047B0200D00E0000
    TABH+ 40( 8) = 10000000C1248000
    store        = 0x00000000
    ext1         = 0x801CE03C
    shmId        = 0     (0x00000000)
    id           = 324   (0x44010000)
    label        = 5544  (0xA8150000)
    fill         = 0     (0x00000000)
    leng         = 89    (0x59000000)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000058
    occu         = 16    (0x10000000)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 1
    collHash     = 0
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = Not allocated
    pghook       = Not allocated
    idxPtr       = Not allocated
    refCount     = Not allocated
    tstRefCount  = Not allocated
    lineAdmin    = Not allocated
    lineAlloc    = Not allocated
    store_id     = Not allocated
    shmIsReadOnly = Not allocated
    >>>>> 1st level extension part <<<<<
    regHook      = 0x00000000
    hsdir        = 0x00000000
    ext2         = 0x381CE03C
    >>>>> 2nd level extension part <<<<<
    tabhBack     = 0x98DC033D
    delta_head   = 000000000000000000000000000000000000000000000000000000000000000000000000
    pb_func      = 0x00000000
    pb_handle    = 0x00000000
    CONTEXT
    22222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    PROPERTIES[]
    Table[initial]
    PROPERTIES
    22222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    No.      13 Ty.          FUNCTION
    Name  SDOK_PHIO_GET_CONTENT_ACCESS
    ALLOW_MODEL
    2
    0
    CACHE_SERVER
    0000000000
    2222222222222222222222222222222222222222222222222222222222222222333333333322222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    CLIENT
    800
    333
    800
    CONTENT_ONLY
    X
    5
    8
    CONTENT_OR_URL_ONLY
    2
    0
    OBJECT_ID
    222222222222222222222222222222222222222222
    000000000000000000000000000000000000000000
    RAW_MODE
    2
    0
    TEXT_AS_STREAM
    X
    5
    8
    USE_URL_AT
    2
    0
    ACCESS_MODE
    00
    33
    00
    DOCUMENT_HTTPS_URL
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    DOCUMENT_URL
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    MODEL_RETURNED
    2
    0
    COMPONENTS[]
    Table[initial]
    COMPONENT_ACCESS[]
    Table IT_5533[0x8616]
    CLASS=CL_RSRA_KWF_UTILITIESMETHOD=COPY_MIME_TO_FOLDERDATA=L_T_COMPONENT_ACCESS
    Table reference: 337
    TABH+  0(20) = 00000000481BE03C00000000510100009D150000
    TABH+ 20(20) = 00000000A8210000FFFFFFFF04C5010088190000
    TABH+ 40( 8) = 01000000C1248000
    store        = 0x00000000
    ext1         = 0x481BE03C
    shmId        = 0     (0x00000000)
    id           = 337   (0x51010000)
    label        = 5533  (0x9D150000)
    fill         = 0     (0x00000000)
    leng         = 8616  (0xA8210000)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000107
    occu         = 1     (0x01000000)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 1
    collHash     = 0
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = Not allocated
    pghook       = Not allocated
    idxPtr       = Not allocated
    refCount     = Not allocated
    tstRefCount  = Not allocated
    lineAdmin    = Not allocated
    lineAlloc    = Not allocated
    store_id     = Not allocated
    shmIsReadOnly = Not allocated
    >>>>> 1st level extension part <<<<<
    regHook      = 0x00000000
    hsdir        = 0x00000000
    ext2         = 0x001BE03C
    >>>>> 2nd level extension part <<<<<
    tabhBack     = 0x985D043D
    delta_head   = 000000000000000000000000000000000000000000000000000000000000000000000000
    pb_func      = 0x00000000
    pb_handle    = 0x00000000
    CONTEXT[]
    Table IT_5544[0x89]
    FILE_CONTENT_ASCII[]
    Table IT_5534[0x1022]
    CLASS=CL_RSRA_KWF_UTILITIESMETHOD=COPY_MIME_TO_FOLDERDATA=L_T_FILE_CONTENT_ASCII
    Table reference: 312
    TABH+  0(20) = 00000000B01BE03C00000000380100009E150000
    TABH+ 20(20) = 00000000FE030000FFFFFFFF04C50100D81A0000
    TABH+ 40( 8) = 10000000C1248000
    store        = 0x00000000
    ext1         = 0xB01BE03C
    shmId        = 0     (0x00000000)
    id           = 312   (0x38010000)
    label        = 5534  (0x9E150000)
    fill         = 0     (0x00000000)
    leng         = 1022  (0xFE030000)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000113
    occu         = 16    (0x10000000)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 1
    collHash     = 0
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = Not allocated
    pghook       = Not allocated
    idxPtr       = Not allocated
    refCount     = Not allocated
    tstRefCount  = Not allocated
    lineAdmin    = Not allocated
    lineAlloc    = Not allocated
    store_id     = Not allocated
    shmIsReadOnly = Not allocated
    >>>>> 1st level extension part <<<<<
    regHook      = 0x00000000
    hsdir        = 0x00000000
    ext2         = 0x681BE03C
    >>>>> 2nd level extension part <<<<<
    tabhBack     = 0xB813043D
    delta_head   = 000000000000000000000000000000000000000000000000000000000000000000000000
    pb_func      = 0x00000000
    pb_handle    = 0x00000000
    FILE_CONTENT_BINARY[]
    Table IT_5535[0x1022]
    CLASS=CL_RSRA_KWF_UTILITIESMETHOD=COPY_MIME_TO_FOLDERDATA=L_T_FILE_CONTENT_BINARY
    Table reference: 325
    TABH+  0(20) = 00000000181CE03C00000000450100009F150000
    TABH+ 20(20) = 00000000FE030000FFFFFFFF04C50100101B0000
    TABH+ 40( 8) = 10000000C1248000
    store        = 0x00000000
    ext1         = 0x181CE03C
    shmId        = 0     (0x00000000)
    id           = 325   (0x45010000)
    label        = 5535  (0x9F150000)
    fill         = 0     (0x00000000)
    leng         = 1022  (0xFE030000)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000114
    occu         = 16    (0x10000000)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 1
    collHash     = 0
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = Not allocated
    pghook       = Not allocated
    idxPtr       = Not allocated
    refCount     = Not allocated
    tstRefCount  = Not allocated
    lineAdmin    = Not allocated
    lineAlloc    = Not allocated
    store_id     = Not allocated
    shmIsReadOnly = Not allocated
    >>>>> 1st level extension part <<<<<
    regHook      = 0x00000000
    hsdir        = 0x00000000
    ext2         = 0xD01BE03C
    >>>>> 2nd level extension part <<<<<
    tabhBack     = 0xC08FD33C
    delta_head   = 000000000000000000000000000000000000000000000000000000000000000000000000
    pb_func      = 0x00000000
    pb_handle    = 0x00000000
    PROPERTIES[]
    Table[initial]
    COMPONENT_ACCESS
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    FILE_CONTENT_ASCII
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    FILE_CONTENT_BINARY
    0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.1.
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    OBJECT_ID_AUX
    222222222222222222222222222222222222222222
    000000000000000000000000000000000000000000
    X_DOCUMENT_URL
    X
    5
    8
    X_DOCUMENT_HTTPS_URL
    X
    5
    8
    X_COMPONENT_ACCESS
    X
    5
    8
    SUBRC_AUX
    0
    0000
    0000
    %_DUMMY$$
    2222
    0000
    %_SPACE
    2
    0
    SY-REPID
    SAPLSDCI
    5454544422222222222222222222222222222222
    310C343900000000000000000000000000000000
    No.      12 Ty.          FUNCTION
    Name  SKWF_PHIO_CONTENT_ACCESS_GET
    CACHE_SERVER
    0000000000
    2222222222222222222222222222222222222222222222222222222222222222333333333322222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    PHIO
    2222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000
    USE_URL_AT
    2
    0
    X_ALLOW_MODEL
    2
    0
    X_CONTENT_ONLY
    X
    5
    8
    X_CONTENT_OR_URL_ONLY
    2
    0
    X_RAW_MODE
    2
    0
    X_TEXT_AS_STREAM
    X
    5
    8
    ACCESS_MODE
    00
    33
    00
    DOCUMENT_HTTPS_URL
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    DOCUMENT_URL
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    ERROR
    000
    2222222222222222222223332222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    X_MODEL_RETURNED
    2
    0
    COMPONENT_ACCESS[]
    Table IT_5533[0x8616]
    CONTEXT[]
    Table IT_5544[0x89]
    FILE_CONTENT_ASCII[]
    Table IT_5534[0x1022]
    FILE_CONTENT_BINARY[]
    Table IT_5535[0x1022]
    PROPERTIES[]
    Table[initial]
    SKWFA_C_ACT_READ
    03
    33
    03
    SYST-REPID
    SAPLSKWF_CONTENT
    5454545454445445222222222222222222222222
    310C3B76F3FE45E4000000000000000000000000
    %_ARCHIVE
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    PHIO+1(42)
    222222222222222222222222222222222222222222
    000000000000000000000000000000000000000000
    CL_ABAP_TABLEDESCR=>TABLEKIND_STD
    S
    5
    3
    SKWFC_YES
    X
    5
    8
    No.      11 Ty.          METHOD
    Name  CL_RSRA_KWF_UTILITIES=>COPY_MIME_TO_FOLDER
    I_S_MIME_IO
    FM_FOLDER  3AA00E1E0D0E3DCBE10000000A1144B5
    4454444452234433434343434444333333334333343
    6DF6FC4520031100515040534325100000001114425
    I_S_FOLDER_IO
    FBW_FLD    08BSWBLVV6N1IJCIG3VHEX2H8
    4455444222233455445534344444354453432222222
    627F6C40000082372C666E19A397368582880000000
    L_T_PROPERTY_REQUEST
    Table IT_5512[1x25]
    CLASS=CL_RSRA_KWF_UTILITIESMETHOD=COPY_MIME_TO_FOLDERDATA=L_T_PROPERTY_REQUEST
    Table reference: 316
    TABH+  0(20) = 28D5D23C68D5D23C000000003C01000088150000
    TABH+ 20(20) = 0100000019000000FFFFFFFF04C5010038110000
    TABH+ 40( 8) = 10000000C1248400
    store        = 0x28D5D23C
    ext1         = 0x68D5D23C
    shmId        = 0     (0x00000000)
    id           = 316   (0x3C010000)
    label        = 5512  (0x88150000)
    fill         = 1     (0x01000000)
    leng         = 25    (0x19000000)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000069
    occu         = 16    (0x10000000)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 1
    collHash     = 0
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 1
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0xC00BE03C
    pghook       = 0x00000000
    idxPtr       = 0x00000000
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 16    (0x10000000)
    lineAlloc    = 16    (0x10000000)
    store_id     = 3644  (0x3C0E0000)
    shmIsReadOnly = 0     (0x00000000)
    >>>>> 1st level extension part <<<<<
    regHook      = 0x00000000
    hsdir        = 0x00000000
    ext2         = 0x600DE03C
    >>>>> 2nd level extension part <<<<<
    tabhBack     = 0x98D5033D
    delta_head   = 000000000000000000000000000000000000000000000000000000000000000000000000
    pb_func      = 0x00000000
    pb_handle    = 0x00000000
    L_S_PROPERTY_REQUEST
    KW_RELATIVE_URL
    4555444545455542222222222
    B7F25C14965F52C0000000000
    L_T_PHIO
    Table IT_5494[1x43]
    CLASS=CL_RSRA_KWF_UTILITIESMETHOD=COPY_MIME_TO_FOLDERDATA=L_T_PHIO
    Table reference: 309
    TABH+  0(20) = E8D4D23CE0D3D23C000000003501000076150000
    TABH+ 20(20) = 010000002B000000FFFFFFFF04C5010018120000
    TABH+ 40( 8) = 10000000C1248000
    store        = 0xE8D4D23C
    ext1         = 0xE0D3D23C
    shmId        = 0     (0x00000000)
    id           = 309   (0x35010000)
    label        = 5494  (0x76150000)
    fill         = 1     (0x01000000)
    leng         = 43    (0x2B000000)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000073
    occu         = 16    (0x10000000)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 1
    collHash     = 0
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0x2010E03C
    pghook       = 0x00000000
    idxPtr       = 0x00000000
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 16    (0x10000000)
    lineAlloc    = 16    (0x10000000)
    store_id     = 3643  (0x3B0E0000)
    shmIsReadOnly = 0     (0x00000000)

    Hi priya,
    Not sure: check syntax in your Update Roules, also at level of start routine.
    Ciao.
    Riccardo.

  • How to delete the data in ODS

    Hi,
    I am working for production support project.I want to delete the data(error data) from ODS and willing to reload the data again to ODS with different data(Corrected data).
    Can any body throw some light on this please.
    karunakar reddy

    hi karunkar,
            I am also in production support but new . I have some queery can I have your mail id to contact you.currently I a, located in singapore at client side. I will appritiate you if you we can have some knowledge sharing.
      With best Regards
         Vikas Sharma

  • How to extract data from ODS to non-SAP system

    Hi,
    Can anybody tell me, step by step, how to extract data from ODS to a non-SAP system?
    Is it possible to do it without programming effort? And is there volume limits for this kind of extraction?
    The non-SAP system is an unix system.
    Thanks in advance
    Ella

    Ella,
    You can look at it from the concept of a BADI / Infospoke
    Extract the data from the ODS to a Flat file / RDBMS using an infospoke. I am not sure as to how the infospoke loads data into the RDBMS ( did it very long ago ) but then you can push it into an RDBMS and I am sure it will be system neutral.
    Hope this helps...
    Arun
    Assign points if it helps

  • DBIF_RSQL_SQL_ERROR while activating data in ODS

    Hi,
    I'm getting the following error when I try to activate the data in ODS. This is happening for all the ODSs in the system.
    SQL-ERROR: 603 ORA-00603: ORACLE server session terminated by fat al error
    System error: RSDU_ANALYZE_TABLE_ORA/ ORACLE
    ABAP/4 processor: DBIF_RSQL_SQL_ERROR
    Job cancelled
    Any suggestion is greatly appreciated.
    Thanks,
    Vish

    hi,
    if not help, check oss note
    840552
    Symptom
    On BW tables that belong to an InfoCube, statistics are calculated (COMPUTE) instead of estimated with the set percentage (ESTIMATE). This results in high runtimes.
    Other terms
    InfoCube, database, Oracle statistics
    Reason and Prerequisites
    In the Oracle-specific RSDU_ANALYZE_TABLE_ORA BW function, in some situations an estimation is made as to how many records are in the table to be analyzed. A SELECT in the USER_TABLES table is specifically used for this. If there is no value there now, 0 is returned and a COMPUTE is carried out. COMPUTE is considerably fasterer than ESTIMATE on small tables (under 10000 approximately).
    However, if the table is too big and if the statistics were deleted by a brconnect run that ran shortly beforehand, the above situation of long runtimes mentioned above can occur.
    Solution
    BW 3.0B
               Import Support Package 27 or 3.0B (BW3.0B Patch 27 or SAPKW30B27) into your BW system. The Support Package will become available oncenote 723258 with the short text, "SAPBWNews BW3.0B Support Package 27", which describes this Support Package in more detail, is released for customers.
    BW 3.10 Content
               Import Support Package 21 for 3.10 (BW3.10 Patch 21 or SAPKW31021 ) into your BW system. The Support Package will become available once <Z1>note 723263 with the short text, "SAPBWNews BW3.1 Content SP 21", which describes this Support Package in more detail, is released for customers.
    BW 3.50
               Import Support Package 13 for 3.5 (BW3.50 Patch 13 or SAPKW35013) into your BW system. The Support Package will become available oncenote 783254 with the short text, "SAPBWNews BW SP12 NetWeaver'04 Stack 13", which describes this Support Package in more detail, is released for customers.
    In urgent cases, you can use the correction instructions.
    To provide information in advance, the notes mentioned may already be made available before the Support Packages are released. However, the short text in this case will still contain the words "Preliminary version".
    769416

Maybe you are looking for