Runtime prediction when executing InfoPackage

In the Header tab while monitoring a dataload, there is a field that says runtime. In this field, it says '1h 48m 33s = 0.75 % of the predicted length of 10 Day(s) 0s'
How does the system get this value?  And should this be a guideline on how long it would take?
Im  extracting about 2.5 million records based on a Datasource view with 4 dables

hi,
The runtime tab shows 1hour = 10% of previous maximum length 10hours         means,  this load was taken 10 hours time to complete at certain time in the past, that acts as a base line to the current loads. if current load takes 11 hour then it will be base line.

Similar Messages

  • Runtime error when executing ME2B/ME3B if condition recs 160

    Dear all,
    I have created a vendor rebate agreement and entered condition records for a vendor/material combination.
    Since for this vendor there are 170 materials for which he provides rebate I have created 170 condition records.
    When I am trying to change or display the rebate agreement by executing transaction codes ME2B and ME3B respectively the following run time error occurs (Runtime error when executing transaction codes ME2B/ME3B for condition recrds >160):
    Runtime Errors: DBIF_RSQL_INVALID_RSQL
    Except. CX_SY_OPEN_SQL_DB
    The error is in function module SELECT_TEXT at line 120 "select * from stxh client specified into table stxh_buffer".
    When I debug or test/execute the function module SELECT_TEXT, I find that there are no relevant entries in table STXH for the vendor rebate agreements.
    Please note that if the condition records of the rebate agreement are 160 and less then there is no problem.
    I would appreciate if I could have your expert oppinion on what is causing this runtime error and if it is possible on how to resolve it.
    Thanks in advance.
    Regards,
    Mimis
    Edited by: Mimis1973 on Jan 26, 2011 11:18 AM
    Edited by: Mimis1973 on Jan 26, 2011 11:20 AM
    Edited by: Mimis1973 on Jan 26, 2011 11:23 AM

    There's something similar in OSS note 1002788. Is it relevant to your system?

  • Runtime error when executing F4 help on 0FISPER or 0FISCYEAR

    Hi experts,
    I got a problem on F4 help.
    When executing F4 help on 0FISPER or 0FISCYEAR using tcode LISTCUBE,
    abap dump occurs. The problem also exists when run query in BEx analyzer.
    My BW version is NW2004s. And SAPKW70012 has been implemented.
    Thanks very much for any advices.
    <b>The error message when run in BEx analyzer:</b>
    System error in program SAPLRRS2 and form EXTRA_FIELDS_SET-01- (see long
    text)
        Message no. BRAIN299
    Diagnosis
        This internal error is an intended termination resulting from a program
        state that is not permitted.
    Procedure
        Analyze the situation and inform SAP.
        If the termination occurred when you executed a query or Web template,
        or during interaction in the planning modeler, and if you can reproduce
        this termination, record a trace (transaction RSTT).
        For more information about recording a trace, see the documentation for
        the trace tool environment as well as SAP Note 899572.
    <b>And the ABAP dump log:</b>
    Runtime Errors         UNCAUGHT_EXCEPTION
    Exception              CX_RSR_PROPAGATE_X
    Date and Time          2007.04.28 15:08:47
    Short text
    An exception occurred that was not caught.
    What happened?
    The exception 'CX_RSR_PROPAGATE_X' was raised, but it was not caught anywhere
    along
    the call hierarchy.
    Since exceptions represent error situations and this error was not
    adequately responded to, the running ABAP program
    'CL_RS_BASE====================CP' has to be
    terminated.
    What can you do?
    Note down which actions and inputs caused the error.
    To process the problem further, contact you SAP system
    administrator.
    Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.
    Error analysis
    An exception occurred which is explained in detail below.
    The exception, which is assigned to class 'CX_RSR_PROPAGATE_X', was not caught
    and
    therefore caused a runtime error.
    The reason for the exception is:
    No text available for this exception
    The occurrence of the exception is closely related to the occurrence of
    a previous exception "CX_SY_NO_HANDLER", which was raised in the program
    "CL_RSMD_RS_BUILD_QUERY========CP",
    specifically in line 1 of the (include) program
    "CL_RSMD_RS_BUILD_QUERY========CM00Y".
    The cause of the exception was:
    An exception with the type CX_RS_SQL_ERROR_SILENT occurred, but was neither
    handled locally, nor declared in a RAISING clause
    The occurrence of the exception is closely related to the occurrence of
    a previous exception "CX_RS_SQL_ERROR_SILENT", which was raised in the program
    "CL_RSDRS_SQL_QUERY============CP",
    specifically in line 288 of the (include) program
    "CL_RSDRS_SQL_QUERY============CM00J".
    The cause of the exception was:
    No text available for this exception
    The occurrence of the exception is closely related to the occurrence of
    a previous exception "CX_SQL_EXCEPTION", which was raised in the program
    "CL_SQL_STATEMENT==============CP",
    specifically in line 32 of the (include) program
    "CL_SQL_STATEMENT==============CM004".
    The cause of the exception was:
    Invalid object name 'T009C'.
    How to correct the error
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "UNCAUGHT_EXCEPTION" "CX_RSR_PROPAGATE_X"
    "CL_RS_BASE====================CP" or "CL_RS_BASE====================CM005"
    "X_PROPAGATE"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
    To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
    Display the system log by calling transaction SM21.
    Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
    In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
    4. Details about the conditions under which the error occurred or which
    actions and input led to the error.
    System environment
    SAP-Release 700
    Application server... "sapdev2"
    Network address...... "192.168.1.74"
    Operating system..... "Windows NT"
    Release.............. "5.2"
    Hardware type........ "4x AMD64 Level"
    Character length.... 16 Bits
    Pointer length....... 64 Bits
    Work process number.. 1
    Shortdump setting.... "full"
    Database server... "SAPDEV2"
    Database type..... "MSSQL"
    Database name..... "BW1"
    Database user ID.. "bw1"
    Char.set.... "C"
    SAP kernel....... 700
    created (date)... "Sep 1 2006 00:19:17"
    create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
    Database version. "SQL_Server_8.00 "
    Patch level. 75
    Patch text.. " "
    Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
    SAP database version. 700
    Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
    Memory consumption
    Roll.... 16192
    EM...... 14617568
    Heap.... 0
    Page.... 163840
    MM Used. 4553264
    MM Free. 663776
    User and Transaction
    Client.............. 100
    User................ "HANDLCR"
    Language key........ 1
    Transaction......... "LISTCUBE "
    Program............. "CL_RS_BASE====================CP"
    Screen.............. "SAPMSHLP 0600"
    Screen line......... 7
    Information on where terminated
    Termination occurred in the ABAP program "CL_RS_BASE====================CP" -
    in "X_PROPAGATE".
    The main program was "GP9QWV49ZUMYUSW6JLZIZ85P81N ".
    In the source code you have the termination point in line 12
    of the (Include) program "CL_RS_BASE====================CM005".
    Source Code Extract
    Line
    SourceCde
    1
    METHOD X_PROPAGATE .
    2
    3
    DATA: l_r_x TYPE REF TO cx_rs_no_check.
    4
    5
    TRY.
    6
    l_r_x ?= i_r_root.
    7
    CATCH cx_root.
    8
    CLEAR l_r_x.
    9
    ENDTRY.
    10
    11
    IF l_r_x IS INITIAL.
    >>>>>
    RAISE EXCEPTION TYPE cx_rsr_propagate_x
    13
    EXPORTING
    14
    previous = i_r_root.
    15
    ELSE.
    16
    RAISE EXCEPTION l_r_x.
    17
    ENDIF.
    18
    19
    ENDMETHOD.

    I got reply from SAP. The problem can be solved by running program RSDG_XPRA_IOBJ_TO_NW05. Note 939484 describes this.
    Note 939484 - Input help for tech characteristic and time characteristics
    Summary
    Symptom
    You upgraded to SAP NetWeaver 2004s. An open SQL error occurs when you execute input help for a technical characteristic, a time characteristic or a unit.
    The 'SAPSQL_INVALID_FIELDNAME' short dump in the 'CL_RSDM_READ_MASTER_DATA' class indicates that these characteristics have not been maintained. This error may also occur when you activate InfoProviders, for example.
    The error MAY occur for the following InfoObjects:
    0CALMONTH
    0CALMONTH2
    0CALQUART1
    0CALQUARTER
    0CALWEEK
    0CALYEAR
    0CURRENCY
    0FISCPER
    0FISCPER3
    0FISCVARNT
    0FISCYEAR
    0LOGSYS
    0SOURSYSTEM
    0UNIT
    0WEEKDAY1
    0RATE_TYPE
    0DATE
    0LANGU
    Other terms
    Input help, F4, 0CALMONTH, 0CALMONTH2, 0CALQUART1, 0CALQUARTER, 0CALWEEK, 0CALYEAR, 0CURRENCY, 0FISCPER, 0FISCPER3, 0FISCVARNT, 0FISCYEAR, 0LOGSYS, 0SOURSYSTEM, 0UNIT, 0WEEKDAY1, 0RATE_TYPE, 0DATE, 0LANGU, RSDG_XPRA_IOBJ_TO_NW05
    Reason and Prerequisites
    The problem can have the following causes:
    The characteristic does not have any master data, although you did define a master data read class.
    There is no generated master data table for the characteristic (for example, 0CURRENCY) and you have not defined a corresponding master data read class in the meta data.
    Solution
    Technical characteristics and time characteristics were delivered again for SAP NetWeaver 2004s with new properties. The first time you call the data warehousing workbench, the system activates the technical content. If the (time) characteristic already exists in the active version, the system does not copy it from the technical content again.  For SAP NetWeaver 2004s, however, the following conditions must be fulfilled:
    The characteristic has the property "With master data", which ensures that the master data read class functions correctly.
    If the active version of the characteristic does not have any master data, copy the characteristic from the content again. Make any necessary adjustments. Ensure that the "With master data" property is set.
    The characteristic does not have a generated table, rather it has its own table, delivered by SAP (for example, unit 0CURRENCY -> table TCURC). The definition of the characteristic must include a relevant master data read class (for example, unit 0CURRENCY -> class CL_RSMD_RS_0CURRENCY).
    The RSDG_XPRA_IOBJ_TO_NW05 XPRA defines a master data read class automatically. This XPRA is executed when you upgrade. It may, however, occur, that the XPRA is not executed successfully. If this happens, you can execute the XPRA again manually.
    Start Transaction SE38.
    Enter the name RSDG_XPRA_IOBJ_TO_NW05 in the 'Program' field.
    Choose 'Execute' to execute the program.

  • Portal runtime error when execute a model deployed

    Hy, i have this problem: when execute my model on the portal i receive this error:
    Portal Error run-time
    Error request processing for :
    iView : N/A
    Component : N/A
    Component com.myComp.myProduct.29H.Analisi_agenti_2.AAD29H : JSP file name missing. Please check you profile..
    Exception id: 10:54_29/01/08_0009_3388450
    See the details for the exception ID in the log file
    Thank's a lot.
    Sincerely yours
    Andrea Maraviglia

    Hi Andrea,
    Please check your portal runtime server is running or not. (Management Console)
    I have experienced the same error , when our portal runtime server was stopped. I just restarted it. and problem solved.
    Let me know if you have further problem.
    Thanks,
    Prashant
    (Do reward points for helpful answer)

  • Runtime error when executing smarforms.

    Dear All,
    I am getting the runtime error while executing a smartfrom which I have prepared for payslip display.
    After the completion of smartform, I have tested by using print program, it was working fine. But, when I got the print of the same and I found, little modification it requires to enlarge the views.So, I increased the width of templates, tables and windows which has been used in this smartform.
    After that modification, it is going to reuntime error.
    Please sugget....to rectify this.
    Thanks & Regards
    Nrusingha.

    Please find the below details fr dump.
    Short text                                                            
        Exception condition "ERROR" raised.                                                                               
    What happened?                                                           
        The current ABAP/4 program encountered an unexpected                 
        situation.                                                                               
    What can you do?                                                         
        Note down which actions and inputs caused the error.                                                                               
    To process the problem further, contact you SAP system               
        administrator.                                                                               
    Using Transaction ST22 for ABAP Dump Analysis, you can look          
        at and manage termination messages, and you can also                 
        keep them for a long time.                                                                               
    Error analysis                                                           
        A RAISE statement in the program "SAPLSTXBC" raised the exception    
        condition "ERROR".                                                   
        Since the exception was not intercepted by a superior                
        program, processing was terminated.                                                                               
    Short description of exception condition:                                                                               
    For detailed documentation of the exception condition, use           
        Transaction SE37 (Function Library). You can take the called         
        function module from the display of active calls.                    
    How to correct the error                                                                               
    If the error occures in a non-modified SAP program, you may be able to
        find an interim solution in an SAP Note.                             
        If you have access to SAP Notes, carry out a search with the following
        keywords:                                                                               
    "RAISE_EXCEPTION" " "                                                            
        "SAPLSTXBC" or "LSTXBCU19"                                                       
        "SSFCOMP_GENERATE_SMART_FORM"                                                                               
    or                                                                               
    "SAPLSTXBC" "ERROR"                                                                               
    or                                                                               
    "RS_TESTFRAME_CALL " "ERROR"                                                     
        If you cannot solve the problem yourself and want to send an error               
        notification to SAP, include the following information:                                                                               
    1. The description of the current problem (short dump)                                                                               
    To save the description, choose "System->List->Save->Local File               
        (Unconverted)".                                                                               
    2. Corresponding system log                                                                               
    Display the system log by calling transaction SM21.                           
           Restrict the time interval to 10 minutes before and five minutes              
        after the short dump. Then choose "System->List->Save->Local File                
        (Unconverted)".                                                                               
    3. If the problem occurs in a problem of your own or a modified SAP              
        program: The source code of the program                                          
           In the editor, choose "Utilities->More                                        
        Utilities->Upload/Download->Download".                                                                               
    4. Details about the conditions under which the error occurred or which          
        actions and input led to the error.

  • Runtime error when executing driver program

    when im executing my report after passing smartform to it , by giving invoice number in selectionscreen,it's generating runtime error as
    the call to the function module     '/1BCDWB/SF00000032'   is incorrect:
    in the function module interface, u can only specify fields of a specific  type and
    length under "s_final".although the currently specified field "    " is the correct type,
    it's length is incorrect.
    i declared s_final in forminterface->tables as s_final like zform1.
    i defined zform1 with fields which are in t_final.
    please suggest where im going wrong.
    TYPES : BEGIN OF TY_FINAL,
           VBELN TYPE VBRP-VBELN,"INVOICE NO
            ADRNR TYPE KNA1-ADRNR, "ADDRESS FOR CONSIGNEE
            BSTKD  TYPE VBKD-BSTKD,   "PO NUMBER
            BSTDK  TYPE VBKD-BSTDK,  "PO DATE
             ARKTX TYPE VBRP-ARKTX, "DESCRITION
            PACK TYPE I,           "NO OF PACKAGES
            UMREZ TYPE SMEINH-UMREZ, "AVG. CONTENTS PER PACKAGE IN KGS
             FKIMG TYPE VBRP-FKIMG,  "TOTAL QTY IN KGS
             KNUMV  TYPE KONV-KNUMV,
             KBETR TYPE KONV-KBETR,  "SELLING RATE/KG
            KBETR1 TYPE KONV-KBETR,
             KWERT TYPE KONV-KWERT,
             TARIFF TYPE ZFORM1-TARIFF,
             DUTY TYPE ZFORM1-DUTY,
             AMOUNT TYPE ZFORM1-AMOUNT,
             END OF TY_FINAL.
        TYPES : BEGIN OF TY_ITEM,
                VBELN TYPE VBRP-VBELN,"INVOICE NO
                POSNR TYPE VBRP-POSNR,
                ARKTX TYPE VBRP-ARKTX, "DESCRITION
                FKIMG TYPE VBRP-FKIMG,  "TOTAL QTY IN KGS
                 BSTKD  TYPE VBKD-BSTKD,   "PO NUMBER
                 BSTDK  TYPE VBKD-BSTDK,  "PO DATE
                 AUBEL TYPE VBRP-AUBEL,
                 AUPOS TYPE VBRP-AUPOS,
                END OF TY_ITEM.
    DATA : FM_NAM TYPE RS38L_FNAM  VALUE '/1BCDWB/SF00000032'.
    DATA :IT_ITEM TYPE TABLE OF TY_ITEM,
          W_ITEM TYPE TY_ITEM,
          W_FINAL  TYPE TY_FINAL,
          T_FINAL TYPE TABLE OF TY_FINAL,
         P TYPE I VALUE 250, "total quantity.
          TOTALDUTY TYPE I  VALUE 0,
           CESS TYPE I,
           EDCESS TYPE I,
             VAT TYPE I,
             FREIGHT TYPE I,
             GROSSTOTAL TYPE I,
           TOTAL TYPE I,
           PONUMBER  TYPE VBKD-BSTKD,   "PO NUMBER
           PODATE  TYPE VBKD-BSTDK,  "PO DATE
            ZTERM TYPE VBKD-ZTERM, "PAYMENT TERMS
           INVOICENO TYPE VBRP-VBELN.
    PARAMETERS : XVBELN TYPE VBELN.
    SELECT VBELN
           POSNR
           ARKTX
           FKIMG
           AUBEL
           AUPOS
           FROM VBRP
           INTO CORRESPONDING FIELDS OF TABLE IT_ITEM
           WHERE VBELN =  XVBELN AND UEPOS  = '000000'.
    LOOP AT IT_ITEM INTO W_ITEM.
    *INVOICE NO
    MOVE  W_ITEM-VBELN TO INVOICENO.
    *DESCRIPTION
    MOVE  W_ITEM-ARKTX TO W_FINAL-ARKTX.
    **TOTAL QUANTITY IN KGS
    MOVE W_ITEM-FKIMG TO W_FINAL-FKIMG.
    *PO NUMBER
    SELECT SINGLE BSTKD FROM VBKD
    INTO W_ITEM-BSTKD
    WHERE VBELN EQ W_ITEM-AUBEL.
    MOVE W_ITEM-BSTKD TO PONUMBER.
    *PO DATE
    SELECT SINGLE BSTDK FROM VBKD
    INTO W_ITEM-BSTDK
    WHERE VBELN EQ W_ITEM-AUBEL.
    MOVE W_ITEM-BSTDK TO PODATE.
    SELECT SINGLE KNUMV FROM VBRK INTO W_FINAL-KNUMV WHERE VBELN = W_ITEM-VBELN.
    **SELLING RATE/KG
    SELECT SINGLE KBETR FROM KONV INTO W_FINAL-KBETR WHERE KNUMV = W_FINAL-KNUMV
               AND KPOSN = W_ITEM-POSNR AND KSCHL = 'PR00'.
    **TOTAL TARIFF VALUE
                W_FINAL-TARIFF  =   W_FINAL-KBETR  *  W_ITEM-FKIMG.
    SELECT SINGLE KBETR FROM KONV INTO  W_FINAL-KWERT WHERE KNUMV =   W_FINAL-KNUMV
               AND KPOSN = W_ITEM-POSNR AND KSCHL = 'JEXT'.
    *TOTAL DUTY PAYABLE
               W_FINAL-DUTY  =  W_FINAL-KWERT / 10.
    **AMOUNT
               W_FINAL-AMOUNT =   W_FINAL-TARIFF  +     W_FINAL-DUTY.
    *TOTAL DUTY FOR CESS&EDCESS
                TOTALDUTY  = TOTALDUTY + W_FINAL-DUTY.
                APPEND W_FINAL TO T_FINAL..
                CLEAR  W_FINAL.
    *WRITE : /10   W_ITEM-ARKTX,
            30  W_ITEM-FKIMG,
            60  W_FINAL-KBETR,
            90     TARIFF,
            120  DUTY,
            160 AMOUNT.
    ENDLOOP.
    *SELECT SINGLE KBETR FROM KONV INTO  W_FINAL-KWERT WHERE KNUMV =   W_FINAL-KNUMV
              AND KPOSN = W_ITEM-POSNR AND KSCHL = 'ZECS'.
    *MOVE   W_FINAL-KWERT TO CESS.
    *SELECT SINGLE KBETR FROM KONV INTO  W_FINAL-KWERT WHERE KNUMV =   W_FINAL-KNUMV
              AND KPOSN = W_ITEM-POSNR AND KSCHL = 'ZECX'.
    *MOVE W_FINAL-KWERT  TO EDCESS.
    *CESS
    CESS  =  TOTALDUTY  *  2 / 100.
    *EDCESS
    EDCESS  =  TOTALDUTY  *  1 / 100..
    *TOTAL VALUE AT FOOTER
    TOTAL  = W_FINAL-AMOUNT + CESS + EDCESS.
    *VAT
    VAT  =  TOTAL *  4 / 100.
    *FREIGHT
    *GROSS TOTAL
    GROSSTOTAL   =  TOTAL + VAT.
    CALL FUNCTION 'SSF_FUNCTION_MODULE_NAME'
      EXPORTING
        FORMNAME                 =  'ZSF_SD_INVOICE1'
       VARIANT                  = ' '
       DIRECT_CALL              = ' '
      IMPORTING
       FM_NAME                  =   FM_NAM
    EXCEPTIONS
       NO_FORM                  = 1
       NO_FUNCTION_MODULE       = 2
       OTHERS                   = 3
    IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
             WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    CALL FUNCTION FM_NAM
      EXPORTING
      ARCHIVE_INDEX              =
      ARCHIVE_INDEX_TAB          =
      ARCHIVE_PARAMETERS         =
      CONTROL_PARAMETERS         =
      MAIL_APPL_OBJ              =
      MAIL_RECIPIENT             =
      MAIL_SENDER                =
      OUTPUT_OPTIONS             =
      USER_SETTINGS              = 'X'
        TOTALDUTY                  =  TOTALDUTY
        CESS                       =   CESS
        EDCESS                     =   EDCESS
        TOTAL                      =   TOTAL
        PONUMBER                   =  PONUMBER
        PODATE                     =   PODATE
        GROSSTOTAL                 =  GROSSTOTAL
        VAT                        =  VAT
        INVOICENO                  =  INVOICENO
    IMPORTING
      DOCUMENT_OUTPUT_INFO       =
      JOB_OUTPUT_INFO            =
      JOB_OUTPUT_OPTIONS         =
      TABLES
        S_FINAL                    =  T_FINAL
    EXCEPTIONS
      FORMATTING_ERROR           = 1
      INTERNAL_ERROR             = 2
      SEND_ERROR                 = 3
      USER_CANCELED              = 4
      OTHERS                     = 5
    IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.

    Hi,
    U need to fill the ref_fieldname and ref_tabname or the cfieldname, ctabname for currency fields and qtabname and qfieldname for quantity fields in fieldcatalog.
    santhosh
    Message was edited by:
            Kaluvala Santhosh

  • Runtime Error when executing Query in the web

    Hello,
    when i try to execute a query on the  web, i get the error
    Exception in BI runtime
    Log ID: 005056BD15DA005E000000A900000A3400043C8F00E4DD8B
    Initial cause
    Message:
    'user' missing
    Stack trace:
    com.sap.mw.jco.JCO$Exception: (101) RFC_ERROR_PROGRAM: 'user' missing
    Message:
    No connection possible to BI master system VB0CLNT800
    Stack trace:
    com.sap.ip.bi.base.service.connection.ConnectionException: No connection possible to BI master system VB0CLNT800
    Can anyone please tell me , how to fix this ..
    Thanks
    Raj

    you mwy check this to trouble shoot front end
    Troubleshoot the SAP NetWeaver 2004s BI Frontend Installation

  • Runtime error when executing smartform in se38

    hi,
    i designed a smartform but when iam executing that using se38 am gettin runtime error.can anybody plz help me.
    *& Report  ZDEMOPRG
    REPORT  ZDEMOPRG.
    DATA FNAME(30) TYPE C.
    TABLES: LFA1.
    DATA: BEGIN OF ITAB OCCURS 0.
            INCLUDE STRUCTURE LFA1.
    DATA: END OF ITAB.
    SELECT-OPTIONS S_KUNNR FOR LFA1-KUNNR MEMORY ID 001.
    SELECT * FROM LFA1 WHERE KUNNR IN S_KUNNR.
       MOVE-CORRESPONDING LFA1 TO ITAB..
       APPEND ITAB.
    ENDSELECT.
    CALL FUNCTION '/1BCDWB/SF00000006'
    EXPORTING
        FORMNAME = 'ZEXM_SMART'
      ARCHIVE_INDEX              =
      ARCHIVE_INDEX_TAB          =
      ARCHIVE_PARAMETERS         =
      CONTROL_PARAMETERS         =
      MAIL_APPL_OBJ              =
      MAIL_RECIPIENT             =
      MAIL_SENDER                =
      OUTPUT_OPTIONS             =
      USER_SETTINGS              = 'X'
    IMPORTING
      DOCUMENT_OUTPUT_INFO       =
      JOB_OUTPUT_INFO            =
      JOB_OUTPUT_OPTIONS         =
      TABLES
        ITAB                       = ITAB.
    EXCEPTIONS
      FORMATTING_ERROR           = 1
      INTERNAL_ERROR             = 2
      SEND_ERROR                 = 3
      USER_CANCELED              = 4
      OTHERS                     = 5
    IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    plz help me
    thanks
    sudheer

    Hi,
    Try this and reward points by clicking the star on the left of reply,if it helps.
    data: form_name type tdsfname value 'ZEXM_SMART'.
    data: fm_name type  rs38l_fnam.
    TABLES: LFA1.
    DATA: BEGIN OF ITAB OCCURS 0.
    INCLUDE STRUCTURE LFA1.
    DATA: END OF ITAB.
    SELECT-OPTIONS S_KUNNR FOR LFA1-KUNNR MEMORY ID 001.
    SELECT * FROM LFA1 WHERE KUNNR IN S_KUNNR.
    MOVE-CORRESPONDING LFA1 TO ITAB..
    APPEND ITAB.
    ENDSELECT.
    call function 'SSF_FUNCTION_MODULE_NAME'
      exporting
        formname                 = form_name
      VARIANT                  = ' '
      DIRECT_CALL              = ' '
    importing
       fm_name                  = fm_name
    exceptions
       no_form                  = 1
       no_function_module       = 2
       others                   = 3
    if sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    endif.
    CALL FUNCTION fm_name
      TABLES
    ITAB = ITAB
    EXCEPTIONS
       FORMATTING_ERROR           = 1
       INTERNAL_ERROR             = 2
       SEND_ERROR                 = 3
       USER_CANCELED              = 4
       OTHERS                     = 5
    IF sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    endloop.

  • DB connect Datasource is giving error when executing infopackage from SQL

    Hi,
    I have created DB connect data source for SQL data base. Whenever I will try to execute the Infopackage , it is giving below error and when I checked status of job in data source, it stays in yellow.
    SQL error "99" with message: "[Microsoft][SQL Server Native Client 10.0]Numeric
    Message no. RSDS_ACCESS023
    Any suggestion in this.... Thanks.
    Regards
    Deepa.

    Yes, I resolved it.
    Please ask your admin guys do following steps - it will resolve the issue:
    3. Possible problem areas
    a) Datetime data type in source system tables
    The Datetime DB data type and similar (timestamp, smalldatetime) are not used in SAP installations. This type of data cannot be transferred consistently into the BW system without additional activities.
    Solution:
    You must create a view in the source system to transform the data. Since a field of the type DateTime actually represents two SAP Basis types (DATES, TIMES), you must split it into a maximum of two fields, as appropriate:
      create view <VIEWNAME> as
      select
      VD_1_D = convert(varchar(4), datepart(yyyy, d_1))
             + case len(convert(varchar(2), datepart(mm, d_1)))
                  when 1 then '0' + convert(varchar(1), datepart(mm, d_1))
                  else convert(varchar(2), datepart(mm, d_1))
                  end
             + case len(convert(varchar(2), datepart(dd, d_1)))
                  when 1 then '0' + convert(varchar(1), datepart(dd, d_1))
                  else convert(varchar(2), datepart(dd, d_1))
                  end,
      VT_1_T =  case len(convert(varchar(2), datepart(hh, t_1)))
                  when 1 then       /* Hour Part of TIMES */
                        case convert(varchar(2), datepart(hh, t_1))
                          when '0' then '24'    /* Map 00 to 24 ( TIMES ) */
                          else '0' + convert(varchar(1), datepart(hh, t_1))
                        end
                  else convert(varchar(2), datepart(hh, t_1))
                  end
             + case len(convert(varchar(2), datepart(mi, t_1)))
                  when 1 then '0' + convert(varchar(1), datepart(mi, t_1))
                  else convert(varchar(2), datepart(mi, t_1))
                  end
            + case len(convert(varchar(2), datepart(ss, t_1)))
                  when 1 then '0' + convert(varchar(1), datepart(ss, t_1))
                  else convert(varchar(2), datepart(ss, t_1))
                  end
      from <TABLENAME>
    The t_1 Basis field in the table is converted into a DATES field VT_1_D      and a TIMES field VT_1_T. During the generation of the VT_1_T field, the value for 00:00 hours is also converted to 24:00 hours. This conversion may be omitted if not required.
    b) Float data type in source system tables
    In accordance with the IEEE standard regulations, MS SQL Server supports a value range of 1x10E-307 to +go- 1x10E+308. This also applies to the corresponding ABAP data type. However, the BW database in question may restrict this. Depending on the system, a restriction to 1x10E-25 is possible.
    c) Nvarchar data type in source system tables
    The length information displayed is twice as big as the number of characters you specified when you created the column.
    d) Writing names in the source system
    Since the R/3 kernel used in BW can only process table and column names written in upper case, on the source system, you must create DB views that convert the original names in accordance with this rule.
    e) Code page and sort sequence of the source system
    R/3 kernel-based systems such as BW basically assume that the database being used was created using code page cp850 and with the sort sequence 'bin2'.
    The configuration of the source system may differ. If the sort sequence is different, operations for string search (like) and area search (between, >, <) on character fields may return different results.
    Solution:  There is currently no solution.
    If you use multibyte code pages in the source system to save data with character sets of more than 256 characters (Kanji, Hiragana, Korean, Chinese and so on), the characters may be corrupted as a result.
    Solution:  There is currently no solution.
    f) Authorizations and visible objects
    BW DB Connect uses a remote server as a source system to extract data. The data already exists in that remote system. To use BW DB Connect, you will create a new login and new views which the SAP BW system will use when connecting.
    You must remember only the DB objects (tables and views), which directly belong to the new database login are visible.
    You cannot use a login that belongs to the Sysadmin server role, (for example 'sa').
    To create the new login and views:
    1. Create a new login and map it to a user in the database with membership in db_ddladmin
    2. Grant the new user (SELECT at least) access to the original data tables.
    3. Login as this new login and create the views in the database/schema of that user, referring to the original (source) data tables.
    4. Specify this new login in the data extraction and this login/user will read from his own views in his own schema.
    5. Optionally you can switch the new user's role to db_datareader which is sufficient for reading data. Further changes to the remote system e.g. new views or changed views will require the db_ddladmin role again.

  • Runtime error when executing transaction 'PPOME'

    Hi all,
    <br>
    <br>
    <br>I 'm new to SAP and would like to beg a helping hand.
    <br>I had tired the 'free search' function in PPOME.
    <br>and I m not sure what mistake I make. When I execute t-code PPOME again, it is getting the runtime error.
    <br>
    <br>the following are the descritpion of exception by T-code ST22.
    <br>the error is related to u201CSAP_IN_ITAB_ILLEGAL_OPTIONu201D and I read the its SAP NOTE(1256059).
    <br>However, I don't how to do so that fix this problem.
    <br>May anyone help me~
    <br>
    <br>----
    <br><b>Short text</b>                                                                        
    <br>Invalid value in OPTION field of value table for IN itab operator.                           
    <br>
    <br><b>What happened?</b>                                                                               
    <br>    Error in the ABAP Application Program                                                        
    <br>                                                                               
    <br>    The current ABAP program "%_T0DQG0" had to be terminated because it has                   
    <br>    come across a statement that unfortunately cannot be executed.
    <br>
    <br><b>Error analysis</b>                                                                               
    <br>    The current ABAP/4 program attempted to execute an ABAP/4 Open SQL                           
    <br>    statement in which the WHERE condition contains an IN itab operator.                         
    <br>                                                                               
    <br>    The IN itab operator is used with internal tables which                                      
    <br>    have the following structure:                                                                
    <br>                                                                               
    <br>       SIGN(1)   OPTION(2)   LOW LIKE db_field   HIGH LIKE db_field                              
    <br>                                                                               
    <br>    The OPTION column should contain only one of the following values:                           
    <br>                                                                               
    <br>       "EQ LE GE CP BT NE LT GT NP NB"                                                           
    <br>                                                                               
    <br>    The value " " is not allowed here.                                                           
    <br>
    <br><b>How to correct the error</b>                                                                        
    <br>    Use only one of the permitted values in the OPTION column.                                   
    <br>                                                                               
    <br>    If the error occures in a non-modified SAP program, you may be able to                       
    <br>    find an interim solution in an SAP Note.                                                     
    <br>    If you have access to SAP Notes, carry out a search with the following                       
    <br>    keywords:                                                                               
    <br>                                                                               
    <br>    "SAPSQL_IN_ITAB_ILLEGAL_OPTION" " "                                                          
    <br>    "%_T0DQG0" or "%_T0DQG0"                                                                     
    <br>    "GET_OBJECTS"                                                                               
    <br>                                                                               
    <br>    If you cannot solve the problem yourself and want to send an error                           
    <br>    notification to SAP, include the following information:                                      
    <br>                                                                               
    <br>    1. The description of the current problem (short dump)                                       
    <br>                                                                               
    <br>       To save the description, choose "System->List->Save->Local File                           
    <br>    (Unconverted)".                                                                               
    <br>                                                                               
    <br>    2. Corresponding system log                                                                  
    <br>                                                                               
    <br>       Display the system log by calling transaction SM21.                                       
    <br>       Restrict the time interval to 10 minutes before and five minutes                          
    <br>    after the short dump. Then choose "System->List->Save->Local File                            
    <br>    (Unconverted)".                                                                               
    <br>                                                                               
    <br>    3. If the problem occurs in a problem of your own or a modified SAP                          
    <br>    program: The source code of the program                                                      
    <br>       In the editor, choose "Utilities->More                                                    
    <br>    Utilities->Upload/Download->Download".                                                       
    <br>                                                                               
    <br>    4. Details about the conditions under which the error occurred or which                      
    <br>    actions and input led to the error.                                                          
    <br>
    <br><b>User and Transaction</b>                                                                            
    <br>                                                                               
    <br>    Client.............. 300                                                                     
    <br>    User................ "xxxxxxxx"                                                             
    <br>    Language key........ "E"                                                                     
    <br>    Transaction......... "PPOME "                                                                
    <br>    Transactions ID..... "26F031E14FDBF1E0BB3500155D7F2106"                                      
    <br>                                                                               
    <br>    Program............. "%_T0DQG0"                                                              
    <br>    Screen.............. "SAPMSSY0 1000"                                                         
    <br>    Screen line......... 6                                                                       
    <br>
    <br>
    <br><b>Information on where terminated</b>                                                                 
    <br>    The termination occurred in the temporary subroutine pool "%_T0DQG0" in                      
    <br>    "GET_OBJECTS".                                                                               
    <br>    The main program was "OM_START_NF ".                                                         
    <br>                                                                               
    <br>    The point of termination in the source code is in line 69 of                                 
    <br>    the temporary subroutine pool "%_T0DQG0".
    <br>
    <br>Edited by: jack22000011 on Dec 29, 2011 9:05 AM
    Edited by: jack22000011 on Dec 29, 2011 9:11 AM

    Hi all,
    I am getting the exact same dump.
    And in my case, I am not providing any input.
    I have made a non-obligatory selection screen  parameter, and then appended that to a table type of the local structure of select options that i made.
    Then i am passing this to a fm as an importing parameter.
    And it is giving dump on the first query in the fm.
    If I don't use the fm, then in that case, it is working fine, and if the field is blank it fetches all records,
    but why it is not working now..., any ideas???

  • Many processes consumed in  ECC server when executing infopackage in BW

    Hi,
    I know this question was asked many times but I can't figure out why it's not working.
    In fact, when i execute an infopackage, a lot of dialog process are used in the backend , making the system not accessible (windows server)
    I tried to make some changes in SMQS and RSA1_TRFC_OPTION_SET but it has no effect in the system.
    Can someone please, explain step by step what can I do to configure the 2 systems ?
    Thanks a lot,
    Regards,
    Chea-Lie

    HI,
    You can maintain the Control Parameters for Data Load in your ECC system.
    Goto Transaction SBIW
    General Settings->Maintain Control Parameters for Data Transfer
    Refer OSS Note : 417307
    This should help.
    Please check the following documents on Load Performance.
    [Performance Tuning Massive SAP BW Systems - Tips & Tricks|http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/ce7fb368-0601-0010-64ba-fadc985a1f94]
    Do go through the checklist in the below document.
    [BW Performance Tuning|http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/701382b6-d41c-2a10-5f82-e780e546d3b6]
    Regards,
    Gaurav

  • Runtime Error When executing Method from JavaScript

    Greetings In the name of the creator of all things, space, and time. I have a problem with scripting an applet using Javascript (JScript). The problem is as follows: I receive the runtime error - An outgoing call cannot be made since the application is dispatching an input-synchronous call.
    I invoke the applet from a JavaScript from within a web page. The applet populates and display a JTable. From the Table I select an element in a row and press a button which kicks off another page. From within the page I called one of the applet's method i.e. _applet.cfquery(window, hastable).
    This method connects to a data source and returns some data. When the method is invoked I receive the runtime error.
    What is the problem and How do I resolve it? Note: The same code works with Netscape 7.0 with out any problems.
    Particulars:
    Browser: Internet Explorer 6.0 - Version 6.0.2800.1106C (SP1)
    Operating System : Windows 2000 (Service Pack 3)
    Scripting Interface: LiveConnect.
    Scripting Version: JavaScript (1.5)
    I know Microsoft Uses ActiveX to support embedded object. I recently came up on the JavaScript Object
    ActiveXObject(appname.className [,remoteServiceName]). Could I use it to access my applet and how would I specify the name of my applet's? What do they mean by class name. Please help me I have searched the Internet until my eyes almost fall out by I have not found any solutions.

    If the javascript to invoke applet.cfquery(window, hastable) happens automatically (onload,...), try adding a button to your page and using that to invoke applet.cfquery(window, hastable). See if waiting until the applet loads and settles down makes a difference.

  • Execute Infopackage Through BAPI Using Excel Macro (BAPI_IPAK_START)

    Hi everyone,
    I have a problem when execute infopackage through BAPI using excel macro. I have create a button in macro. When this button is clicked, BAPI for trigger InfoPackage will executed (BAPI_IPAK_START) and this button will disabled.
    After this process completely done (traffic indicator for the request is green in update rules), the button will enabled again.
    Here the subroutine or pseudocode that i will write :
    Private Sub ClickButton()
    Begin
    1. ThisButton.Activated = False   --> Disabled Button
    2. Call BAPI/custom Function Module to execute InfoPackage (BAPI_IPAK_START)
    4. ThisButton.Activated = True   --> Enabled Button
    End
    The problem is i need some statement like this between statement no 2 and statement no 4
    Statement That I Want :
    3. Wait Until BAPI Execute Completely
    So user can click this button again only after the process is finished completely. I don't know how to do this in macro (in ABAP i know i can use "WAIT ... SECOND"), others said this can be done using event in schedule option at infopackage. Anyone,please help me.
    Thank you.
    Regards,
    Satria B

    Enter that req number in RSRQ and monitor the load
    or  right click on the DS - manage - you will req in yellow status which is in progress and you can click on the ...takes you monitor screen
    Edited by: Srinivas on Jul 6, 2010 7:51 AM

  • Runtime error when i try to execute this program

    I get a runtime error when i run this file using appletviewer. Please help me in getting out of this problem.
    The runtime errror is:
    C:\prashanth>appletviewer HelloMedia.java
    java.lang.NoClassDefFoundError: javax/media/ControllerListener
    at java.lang.ClassLoader.defineClass0(Native Method)
    at java.lang.ClassLoader.defineClass(ClassLoader.java:486)
    at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:11
    1)
    at sun.applet.AppletClassLoader.findClass(AppletClassLoader.java:142)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:297)
    at sun.applet.AppletClassLoader.loadClass(AppletClassLoader.java:108)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:253)
    at sun.applet.AppletClassLoader.loadCode(AppletClassLoader.java:373)
    at sun.applet.AppletPanel.createApplet(AppletPanel.java:579)
    at sun.applet.AppletPanel.runLoader(AppletPanel.java:515)
    at sun.applet.AppletPanel.run(AppletPanel.java:293)
    at java.lang.Thread.run(Thread.java:484)
    The code is :
    <applet code=HelloMedia.class width=500 height=400>
    <param name=FILE value="globe.avi">
    </applet>
    import java.applet.*;
    import java.awt.*;
    import java.net.*;
    import javax.media.*;
    public class HelloMedia extends Applet implements ControllerListener
    Player player;
    public void init()
    setLayout(new BorderLayout());
    String mediaFile = getParameter("FILE");
    try
    URL mediaURL = new URL(getDocumentBase(), mediaFile);
    player = Manager.createPlayer(mediaURL);
    catch(Exception e)
    System.err.println("Exception : " + e);
    player.addControllerListener(this);
    public synchronized void controllerUpdate(ControllerEvent event)
    if(event instanceof RealizeCompleteEvent)
    Component compVisual = player.getVisualComponent();
    Component compControl = player.getControlPanelComponent();
    if(compVisual != null)
    add("Center", compVisual);
    if(compControl != null)
    add("South", compControl);
    validate();
    public void start()
    player.start();
    public void stop()
    player.stop();
    player.deallocate();
    public void destroy()
    player.close();

    My classpath has the following value
    .;.;.;C:\PROGRA~1\JMF21~1.1\lib\sound.jar;C:\PROGRA~1\JMF21~1.1\lib\jmf.jar;C:\Program Files\CosmoSoftware\CosmoPlayer\npcosmop211.zip;%systemroot%\java\classes;.;
    Please help me out.
    Prashanth

  • SQL error 3113 occurred when executing EXEC SQL.

    Hi,
    We are facing one typical problem, One background is failing regularly with
    below dump. as we now got all notes giving information, if database  restarted
    taking backup, these type of failures occur, but our database is only down for backup once in a week, but it is failing with frequenly.
    in this two servers are located in different place, in this job tries to connect
    another server to get material statistics.
    It is giving some error message in sm21 with
    SQL error 3113 occurred when executing EXEC SQL.
    work procees in reconnect mode.
    all notes saying these types of dump occur when database restared, but this dump
    even though database is up.
    below is short dump, please can anyone help me from this problem.
    ABAP runtime errors    DBIF_DSQL2_SQL_ERROR
          Occurred on    08.01.2007 at 00:30:28
    >> Short dump has not been completely stored. It is too big.
    SQL error 3113 occurred when executing EXEC SQL.
    What happened?
    The error occurred in the current database connection "AZ1".
    What can you do?
    Note the actions and input that caused the error.
    Inform your SAP system administrator.
    You can print out this message by choosing "Print". Transaction ST22
    allows you to display and manage termination messages, including keeping
    them beyond their normal deletion date.
    Error analysis
    How to correct the error
    Database error text........: "ORA-03113: end-of-file on communication channel#"
    Triggering SQL statement...: "select mara.groes, mara.brgew, mara.ntgew,
    mara.gewei, mara.volum, mara.voleh, mara.mstae, mara.mstde, mara.prdha,
    marc.matnr, marc.werks, marc.mmsta, marc.mmstd from sapr3.mara, sapr3.m
    where sapr3.mara.mandt = sapr3.marc.mandt and sapr3.mara.matnr =
    Internal call code.........: "[DBDS/NEW DSQL]"
    Please check the entries in the system log (Transaction SM21).
    If the error occurred in a non-modified SAP program, you may be
    able to find a solution in the SAP note system.
    If you have access to the note system yourself, use the following
    search criteria:
    "DBIF_DSQL2_SQL_ERROR"
    "ZM2431216 " or "ZM2431216 "
    "EXTRACT_GENERAL_DATA"
    If you cannot solve the problem yourself, please send the
    following documents to SAP:
    1. A hard copy print describing the problem.
      To obtain this, select the "Print" function on the current screen.
    2. A suitable hardcopy prinout of the system log.
      To obtain this, call the system log with Transaction SM21
      and select the "Print" function to print out the relevant
      part.
    3. If the programs are your own programs or modified SAP programs,
      supply the source code.
      To do this, you can either use the "PRINT" command in th
      print the programs using the report RSINCL00.
    4. Details regarding the conditions under which the error o
      or which actions and input led to the error.
    System environment
    SAP Release.............. "46C"
    Application server....... "essceu3"
    Network address.......... "172.19.119.198"
    Operating system......... "AIX"
    Release.................. "5.3"
    Hardware type............ "00C7ADBD4C00"
    Database server.......... "ukblx176"
    Database type............ "ORACLE"
    Database name............ "EU3"
    Database owner........... "SAPR3"
    Character set............ "es_ES.ISO8859-1"
    SAP kernel............... "46D"
    Created on............... "Jul 9 2006 20:26:33"
    Created in............... "AIX 1 5 00447C4A4C00"
    Database version......... "OCI_920__OCI_7_API "
    Patch level.............. "2257"
    Patch text............... " "
    Supported environment....
    Database................. "ORACLE 8.0.5.., ORACLE 8.0.6.., ORACLE
    8.1.6.., ORACLE 8.1.7.., ORACLE 9.2.0.., ORACLE 10.2.0.."
    SAP database version..... "46D"
    Operating system......... "AIX 1 4, AIX 2 4, AIX 3 4, AIX 1 5, AIX 2 5, AIX 3
    5, , System build information:,                                      , LCHN :
    841480"
    User, transaction...
    Client.............. 600
    User................ "MPZMMES"
    Language key........ "S"
    Transaction......... " "
    Program............. "ZM2431216 "
    Screen.............. "SAPMSSY0 1000"
    Screen line......... 6
    Information on where termination occurred
    The termination occurred in the ABAP/4 program "ZM2431216 " in
    "EXTRACT_GENERAL_DATA".
    The main program was "ZM2431216 ".
    The termination occurred in line 980
    of the source code of program "ZM2431216 " (when callin
    The program "ZM2431216 " was started as a background jo
    Source code extract
    009500              mara.ntgew,
    009510              mara.gewei,
    009520              mara.volum,
    009530              mara.voleh,
    009540              mara.mstae,
    009550              mara.mstde,
    009560              mara.prdha,
    009570              marc.matnr,
    009580              marc.werks,
    009590              marc.mmsta,
    009600              marc.mmstd
    009610        into :w_ops-groes,
    009620              :w_ops-brgew,
    009630              :w_ops-ntgew,
    009640              :w_ops-gewei,
    009650              :w_ops-volum,
    009660              :w_ops-voleh,
    009670              :w_ops-mstae,
    009680              :w_ops-mstde,
    009690              :w_ops-prdha,
    009700              :w_ops-matnr,
    009710              :w_ops-werks,
    009720              :w_ops-mmsta,
    009730              :w_ops-mmstd
    009740        from sapr3.mara, sapr3.marc
    009750        where sapr3.mara.mandt = sapr3.marc.mandt
    009760          and sapr3.mara.matnr = sapr3.marc.matnr
    009770          and sapr3.mara.mandt = :p_mandt
    009780          and sapr3.mara.matnr = :w_ebs-matnr
    009790          and sapr3.marc.werks = :p_owerks
        >    ENDEXEC.
    009810  endform.                    " extract_general_data
    009820  *&
    009830  *&      Form  append_i_ops
    009840  *&
    009850  *      Appends W_OPS to I_OPS
    009860  *
    009870  form append_i_ops.
    009880    append w_ops to i_ops.
    009890  endform.                    " append_i_ops
    009900  *&
    009910  *&      Form  extract_material_description
    009920  *&
    009930  *      Extracts a Material Description from the remote database an
    009940  *      modifies the current record in I_OPS.
    009950  *
    009960  *        >P_SPRAS  Language Key
    009970  *
    009980  form extract_material_description using    p_spras.
    009990    EXEC sql performing set_langauge.
    Contents of system fields
    SY field contents..................... SY field contents............
    SY-SUBRC 0                            SY-INDEX 0
    SY-TABIX 1                            SY-DBCNT 1
    SY-FDPOS 18                            SY-LSIND 0
    SY-PAGNO 0                            SY-LINNO 1
    SY-COLNO 1
    Chosen variables
    Name.......................... Contents.1........2........3....+..
    W_EBS-PRAT4
                                  2
                                  0
    W_OPS-GROES
                                  22222222222222222222222222222222
                                  00000000000000000000000000000000
    W_OPS-BRGEW                    #######
                                  0000000
                                  000000C
    W_OPS-NTGEW                    #######
                                  0000000
                                  000000C
    regards,
    krishnaiah.

    Hi,
    This is usually a SERVER SIDE DATABASE PROBLEM or SQLNET LISTENER (server side) PROBLEM.  The client side should initially be ignored and instead the server should be investigated. In rare cases, this can be caused by client
    side memory or other resource problem, or a DLL version mismatch, but this is
    unlikely.
    Enlist the assistance of your DBA.  Then reproduce the ORA-3113 error on your
    client application.  Ask your DBA to look at the database side Alert.log and
    trace files and look for ANY activity.  Any activity that coincides with your
    ORA-3113 will be a clue.
    REgards
    Vinod

Maybe you are looking for

  • Can't access the Time Capsule Drive and attached USB drive

    I bought the 3 TB Time capsule a couple of months ago.  I am using it as my wireless router for a cable modem and have attached a USB drive (seagate) to the TC.  I use the TC drive for time machine only.  It worked well at first, for about the first

  • Writing to file that is in application system

    Hi all, The following code creates such a display in file: open dataset filename for output in text mode   ENCODING    non-UNICODE IGNORING     CONVERSION ERRORS.    loop at line.    CONDENSE line.   transfer line to filename. endloop. close dataset

  • Partitioning Fact Tables -- experiences, notes, documentation

    I have gone through section 3.8 of the OBIA Installation and Configuration Guide -- "Partitioning Guidelines for Large Fact Tables". Frankly, I find that documentation inadequate and using a poor example. I am looking at partitioning W_GL_BALANCE_F .

  • Stack over after Calling a module pool N times

    Hi Experts, There is a module pool 'A' which exports to memory a table and executes a CALL TRANSACTION 'B' (another module pool). After saving program B, I must execute it again 'n times' without returning to caller program 'A', until I choose BACK.

  • Enhancing PD Infotype

    Hi all, How to enhance the Table Infotype in PD (as I know to enhance Field Infotype through PPCM) and may I know is it possible to enhance Table Infotype. If possible, pls help in this regard. Regards, V Kumar