DYNPRO_FIELD_CONVERSION when executing tcode DB02

Hi All,
We are getting dump DYNPRO_FIELD_CONVERSION when we trying to go to tcode DB02 or DB02old in our SAP CRM 7.0 System.
We have also got one Note 488812 - Shortdump Dynpro_Field_Conversion in DB02 but this note id for SAPKB610 release and we are on SAPKB701 and program RSMSQ060 mentioned in Note also doen not exist in our system.
Please check and suggest.
Shivam Mittal

Hi
Please check the note
Note 1291119 - DBACOCKPIT: Short dump for detailed display Oracle session.
According to it apply latest BASIS support patch or apply corrections mentioned in the Note.
Let us know whether it helps you.
Regards

Similar Messages

  • ABAP Dump when executing tcode CATS_APPR_LITE for multiple selection.

    Dear Members,
    Issue:
    When executing tcode CATS_APPR_LITE for Time Approval from the remote R/3 by selecting multiple selections and click on Approve, if you get a dump saying CALL_FUNCTION_REMOTE_ERROR
    Analysis:
    If there is an SAP Note applied in 1368487 and at CALL FUNCTION CATS_CHECK _PTEXDIR FM getting the dump because in source system for this function module Remote Enabled Module option is not checked.
    To resolve this correction note 1430042 has to be applied.
    Regards
    Durga

    Dear Members,
    Issue:
    When executing tcode CATS_APPR_LITE for Time Approval from the remote R/3 by selecting multiple selections and click on Approve, if you get a dump saying CALL_FUNCTION_REMOTE_ERROR
    Analysis:
    If there is an SAP Note applied in 1368487 and at CALL FUNCTION CATS_CHECK _PTEXDIR FM getting the dump because in source system for this function module Remote Enabled Module option is not checked.
    To resolve this correction note 1430042 has to be applied.
    Regards
    Durga

  • Event flow in ABAP is different when executed via SE80 vs. via TCODE

    Hi,
    We have many existing custom ABAP report pgms that have a custom transaction code that executes them.  Regardless of how the pgms are invoked, the event sequence in the pgm is INITIALIZATION, AT SELECTION-SCREEN, START-OF-SELECTION. etc. 
    Now, when I create a new pgm with a transaction code to invoke it, the event sequence when executing the pgm via SE38 is as before (All 3 events above are triggered).  However when I invoke the pgm via the custom transaction code, only the event At SELECTION-SCREEN is executed.  (Not the INITIALIZATION or the START-OF-SELECTION events).
    We have upgraded our SAP GUI from 6.4 to 7.1.   We are upgrading our system from 46.C to ECC6.  I get this error in ECC6 and also in the old system 46.C which is causing me to question whether the SAP Gui is involved.  We are using SAP GUI 7.1 in both the 46.C and ECC6 systems.
    Any help will be appreciated!
    Thanks,
    Deb

    Hi All,
    Here is my ABAP Code.  I have put break points in the code so I can track the sequence.
    REPORT ZDEBNEW .
    data zdeb(2) type c.
    tables kna1.
    SELECTION-SCREEN BEGIN OF BLOCK A WITH FRAME TITLE TEXT-002.
    SELECT-OPTIONS: I_KTOKD for KNA1-KTOKD.
    SELECTION-SCREEN END OF BLOCK A.
    INITIALIZATION.
      zdeb = '1'.   "break
      sy-subrc = sy-subrc.
    PAI
    AT SELECTION-SCREEN.
      zdeb = '2'.  "break
      sy-subrc = sy-subrc.
    START-OF-SELECTION.
      zdeb = '3'.  "break
      sy-subrc = sy-subrc.
    END-OF-SELECTION.
      zdeb = '4'.   "break
      sy-subrc = sy-subrc.
    As for the type of transaction I am using...I created it via SE93 and specify SELECTION SCREEN 1000.  I classify it as a Professional User transaction.  One other thing I have noticed is that when I view the new pgm via SE80 I do not see Screen 1000 in the left navigation panel.  If I try to create such a screen in SE80, it says it already exists.  I can see Screen 1000 from tran SE51.  In one of the existing old pgms, I do see screen 1000 when I view SE80.
    Thanks for the help and interest!!!

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

  • Refresh Runtime Error in TCODE DB02

    Hello Experts!
    Was just trying to refresh the statistics that I have for my DB Spaces in DB02, but I suddenly come up with this error. Can anyone tell me what this means and why this is suddenly happening (As I had no problems using this functionality just last week). Thanks!
    ST22 Error Log:
    Runtime Errors         DBIF_DSQL2_SQL_ERROR                                           
    Exception              CX_SY_NATIVE_SQL_ERROR                                         
           Occurred on     03/30/2009 at 11:11:51                                                                               
    SQL error "-727" occurred when executing EXEC SQL.                                                                               
    What happened?                                                                               
    The error occurred in the current database connection "DEFAULT".                                                                               
    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                                                                               
    An exception occurred. This exception will be dealt with in more detail               
    below. The exception, assigned to the class 'CX_SY_NATIVE_SQL_ERROR', was not         
    caught, which                                                                        
    led to a runtime error. The reason for this exception is:
                                                                                    How to correct the error                                                                               
    Database error text........: "INF-727: Invalid or NULL TBLspace number given to    
    dbinfo(dbspace)."                                                                 
    Triggering SQL statement...: "FETCH NEXT "                                         
    Internal call code.........: "[DBDS/NEW DSQL]"                                     
    Please check the entries in the system log (Transaction SM21).                                                                               
    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:                                                                               
    "DBIF_DSQL2_SQL_ERROR" CX_SY_NATIVE_SQL_ERRORC                                     
    "RSINFTD1 " or "RSINFTD1 "                                                         
    "START-OF-SELECTION"                                                                               
    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.                                                                               
    4. Details regarding the conditions under which the error occurred    
       or which actions and input led to the error.                                                                               
    SM21 Error Log:
    BY2 Database error -727 at FET                              
    BY0 > INF-727: Invalid or NULL TBLspace number given to     
    BY0 > dbinfo(dbspace).                                      
    R68 Perform rollback                                        
    AB0 Run-time error "DBIF_DSQL2_SQL_ERROR" occurred          
    AB1 > Short dump "090330 111151 gtbwspd 10002568 " generated

    Hi.
    I already had this issue and I solved by this way:
    My issue happened in the following SQL statement:
    94 EXEC SQL.
    SELECT MAX(A.NEXTSIZE)
    96 FROM SYSTABLES A, SYSFRAGMENTS B
    97 WHERE DBINFO('DBSPACE',B.PARTN) = :TS_CHECK-DBSNAME
    98 AND A.PARTNUM = 0
    99 AND A.TABID = B.TABID
    100 INTO :MAXEXT
    101 ENDEXEC.
    1) Please run the following sql query:
    select fragtype, tabid, partn from sysfragments where partn = 0
    2) Figure out which table it is:
    select tabname from systables where tabid =<tabid>
    3) Check the indexes of that table with oncheck -cI.
    4) If you found indexes DISABLED, then you should enable them again.
    5) To solve the problem you can:
    -enable dropped indexes:
    set indexes,constraints for <table> enabled;
    -rebuild the indexes
    Afterwards this operation should be corrected.
    I hope I could be helpful.
    Thanks,
    Walter Oliveira.

  • Incorrec entries when execute the query

    hi,
       I am facing one problem when execute the query on inventory cube(non cumulative cube).Query is diplaying entries for valuated stock Qty.on particular date, but those entries are not exist in BIW(Infocube ,ODS) or R/3 System.
    I checked cache parameters. all settings are correct.
    if anyone has the idea on this  pls. do the needful
    Thanks n Regards,
    HReddy.M
    I

    hello,
          Try to drill down the report based on request ID and find out one record which has this inconsistancy...! then see the data in the CUBE based on that Req ID and PSA..! may be this way will help u out..!
           Check FS10N/MB5B/MB5L Tcodes in R/3 for reconcilation!
                 -EnjoySAP

  • LC  2 Error 1003 when executing external command brconnect on (xpgid=0,con

    Dear all,
    I am getting error in sm21.Please suggest .
    Details Page 2 Line 23 System Log: Local Analysis of clusa                    1
    Time     Type Nr  Clt User TCode Grp N Text
    10:00:32 DIA  000 600 DDIC       LC  2 Error 1003 when executing external command brconnect on (xpgid=0,convid=.)
    Error 1003 when executing external command brconnect on (xpgid=0,convid=.)
    Details
    Recording at local and central time........................ 10.05.2010 10:00:32
    Task...... Process                     User...... Terminal Session TCode Program  Cl Problem cl      Package
    06952      Dialog work process No. 000 DDIC                      1       SAPMSSY1 S  Operation Trace SBTC
    No documentation for syslog message LC 2 exists
    Parameter
      1 .... xpgid=0,convid=.
    Technical details
    File Offset RecFm System log Grp N variable message data
      224 260640                  LC  2 brconnect & &Error 1003 & & &
    Regards,
    Kumar

    Dear Juan,
    Please find the logs.Please suggest.
    dev_cp log
    Trace file of control program (trace level 3)
    < Function: BtcTrcInit> Function: main  SAPXPG 720
    2010-05-10--09-33-29 : Before BtcXpgDetach
      > Function: BtcXpgDetach  < Function: BtcXpgDetach  Accept RFC connection from R/3 system
    2010-05-10--09-33-29 : Before RfcAccept
    2010-05-10--09-33-29 : RfcAccept returned OK
    Begin of check_if_security_list
    security check switched OFF
    End of check_if_security_list
    Begin of check_trace_option
    End of check_trace_option
      Install RFC call SAPXPG_START_XPG
      Install RFC call SAPXPG_START_XPG_LONG
      Install RFC call SAPXPG_END_XPG
      Wait for RFC call SAPXPG_START_XPG or SAPXPG_START_XPG_LONG
    2010-05-10--09-33-29 : Before first call of RFCDispatch
    Security: rfcexec_logon_check
      rfcexec_logon_check: logon_user =
      sapxpg_logon_check: rfc_attr.user = BASIS      
      rfcexec_logon_check: client =   
      > Function: BtcXpgStartXpgLong   
    2010-05-10--09-33-29 : Beginning of BtcXpgStartXpgLong
        > Function: BtcXpgStartXpgImportLong      > Function: BtcXpgParam      < Function: BtcXpgParam      > Function: BtcXpgParam      < Function: BtcXpgParam      > Function: BtcXpgParam      < Function: BtcXpgParam      > Function: BtcXpgParam      < Function: BtcXpgParam      > Function: BtcXpgParam      < Function: BtcXpgParam      > Function: BtcXpgParam      < Function: BtcXpgParam      > Function: BtcXpgParam      < Function: BtcXpgParam      > Function: BtcXpgParam      < Function: BtcXpgParam      > Function: BtcXpgTable      < Function: BtcXpgTable    < Function: BtcXpgStartXpgImportLong   
    BtcXpgStartXpgLong: special_trace_flag = <6>
        > Function: BtcXpgStartXpgInt      > Function: BtcXpgItTransfer        Content of source log table:
              Line  Text
              <No StdOut/StdErr output reported>
            Target log table is not identical to source
            ItGetLine terminated with NULL
          < Function: BtcXpgItTransfer      > Function: BtcTrcReset      < Function: BtcTrcReset      Call mode: VIA RFC
          Input arguments of BtcXpgStartXpg:
            External program: brtools
          tracecntl = : 6
          Display of Parameter string switched off !!
            Contents of control flags:
              StdIn control flag: redirect StdIn
              StdOut control flag: store StdOut output in memory
              StdErr control flag: store StdErr output in memory
              Trace control flag: unknown contents
              Termination control flag: control program will wait for termination
          > Function: BtcXpgCheck        > Function: BtcXpgArgv
              parameter number 1:
              parameter number 2:
              parameter number 3:
              parameter number 4:
              parameter number 5:
              parameter number 6:
              parameter number 7:
              Total number of arguments scanned: 7
              Argument argv[0]: brtools
            < Function: BtcXpgArgv      < Function: BtcXpgCheck      > Function: BtcXpgSigInst      < Function: BtcXpgSigInst      > Function: BtcXpgStart        Rearrange stderr to be collected in memory
            Rearrange stdout to be collected in memory
            Redirect stdin, read from NUL:
            > Function: BtcTrcInit< Function: BtcXpgStartStart status of external program: external program successfully started
    Id of external process: 0000005296
    StdOut/StdErr collected in memory
      Line  Text
      <No StdOut/StdErr output reported>
    < Function: BtcXpgStartXpgInt> Function: BtcXpgStartXpgExport  > Function: BtcXpgParam  < Function: BtcXpgParam  > Function: BtcXpgParam  < Function: BtcXpgParam  > Function: BtcXpgParam  < Function: BtcXpgParam< Function: BtcXpgStartXpgExport
    2010-05-10--09-33-29 : End of BtcXpgStartXpgLong
    < Function: BtcXpgStartXpgLong
    2010-05-10--09-33-29 : After first call of RFCDispatch
    Wait for RFC call SAPXPG_END_XPG
    2010-05-10--09-33-29 : Before second call of RFCDispatch
    Security: rfcexec_logon_check
    rfcexec_logon_check: logon_user =
    sapxpg_logon_check: rfc_attr.user = BASIS      
    rfcexec_logon_check: client =
    > Function: BtcXpgEndXpg 
    2010-05-10--09-33-29 : Beginning of BtcXpgEndXpg
      > Function: BtcXpgStartXpgExport    > Function: BtcXpgTable    < Function: BtcXpgTable  < Function: BtcXpgEndXpgImport  > Function: BtcXpgEndXpgInt    > Function: BtcXpgItTransfer      Content of source log table:
            Line  Text
            <No StdOut/StdErr output reported>
          Target log table is not identical to source
          ItGetLine terminated with NULL
        < Function: BtcXpgItTransfer    > Function: BtcXpgReadChild      Output of external command not written to log !!
          Process executing external program has terminated
        < Function: BtcXpgReadChild    > Function: BtcXpgEnd    < Function: BtcXpgEnd    Termination status of external program: no errors reported
        StdOut/StdErr collected in memory
      < Function: BtcXpgEndXpgInt  > Function: BtcXpgEndXpgExport    > Function: BtcXpgParam    < Function: BtcXpgParam    > Function: BtcXpgParam    < Function: BtcXpgParam  < Function: BtcXpgEndXpgExport 
    2010-05-10--09-33-30 : End of BtcXpgEndXpg
    < Function: BtcXpgEndXpg
    2010-05-10--09-33-30 : After second call of RFCDispatch
    2010-05-10--09-33-30 : After call of RfcClose (wait)
    < Function: main
    2010-05-10--09-33-30 : End of SAPXPG: main
    dev_xpg
    Trace file of External Program (trace level 3)
    < Function: BtcTrcInit> Function: BtcXpgStart  External program: brtools -sid prd -F printout alert_log 20100401000000 0128
    Regards,
    Kumar

  • How can we see print preview when executing T Code?

    We create a one T Code . This T.code is assigned to one programme. Programme is assigned to one smart form. When I execute
    New T code . The system is asking input parameters than executing Tcode system is terminating the screen.

    Hi Go for RSMONICDP give timestamp and u'll have it.
    Please assign points if useful
    Edited by: Aadil on Jan 21, 2008 7:43 AM

  • Tcode DB02 all the values showing zero (0)

    Hi Oracle-experts!
    I have recently executed the upgrade from 4.6C  to ECC 6.0.
    I have the following errors after that:
    <b>Tcode DB02: by entering the Tcode all the values are showing the zero (0).</b>If I try to refresh the values the background job "space statistic:Default" is starting and canceling after while with "SAPOSCOL short dump" (compute bcd overflow).
    <b>Also I have a lot of red messages in TCode dbacockpit.
    How can I fix them? </b>
    Thank you very much
    regards
    Axel

    Die Table ORA_MON_DBCON should contain at least the local database.
    e.g.
      CON NAME       DEFAULT
      STATUS         A
      MAX RUNTIME    1.800
      MAX UPLOAD     1.000.000
      LOG LIFE       100
      DESCRIPTION    Local Oracle database
    Check all points in the SAP Note 1002840 - No data or obsolete data in DB Space Statistic monitor. This note is very important for this problem.
    Best regards
    K.Baran

  • Error1006 when executing external command mv ...

    This error concerns one of the several daily batch most critical. It was not detected before because even if there is an error the program won't never fail (we will review for sure this program).
    The error appears at the call of an external command ZRENAME that corresponds to the OS command "mv" to rename a physical file on directory /interface.
    This error seems corresponds to a timeout when the SAP system tries to call the mv command on the OS level ...
    ERROR:
    Time          Type      Nr       Clt      User            TCode      Priority      Grp      N      Text                                                                               
    12:00:51      BTC       034      120      BUSER_HK20                           LC       2      *Error1006 when executing external command mv on %_TCPIP_%1 (in=R,out=M,err=M,trc=0,trm=C. strtstat=,xpgid=0,convid=. msg:timeout during a)*
    Thanks in advance for help

    Hello
    Check note #1406178 Error 1006 occurs when you execute an external
    Regards
    Mark

  • Difference between TCodes ( Transactional Tcodes & Executable Tcodes)

    Hi All,
           Please help me as i have a requirement to differentiate between the various Tcodes for example( MIRO and MB51 ). MIRO is Executable Tcode and MB51 is Transactional Tcode. Is there is any list or a way in SAP to differnetiate between the Transactional Tcode and Executable Tcode, giving access right for Executable Tcode to user will not harm the SYSTEM rather than giving rights for Transactinal Tcode.
    Your help will be greatly appreciable.
    Please Note : I am not asking about tcode which are created by SE93.
    Thanks,
    Chandresh Bajpai

    Each ABAP program has a program type which must be determined in the program attributes when the program is created.
    There are seven program types from which you can choose: executable program, module pool, function group, class pool, interface pool, subroutine pool, and include program.
    All the SAP ABAP Program used name Standard, like Program name SAPM***  Dialog programming and R*****  Report programming.
    Execute via Transaction code
    MK03 : Display vendor Purchasing (SAPMF02K) Dialog programming
    ML41 : Display Vendor Conditions (SAPMV13A) Dialog programming
    ML35 : Display Vendor Conditions (SAPMV13A) Dialog programming
    MM03 : Display Material & (SAPMMG01) Dialog programming
    MIGO : Goods Movement (SAPLMIGO) FunctionPool
    MIRO : Enter Incoming Invoice (SAPLMR1M) FunctionPool
    Executable Program
    ML81 : Maintain Service Entry Sheet (RM11RL00) Report programming
    MM60 : Materials List (RMMVRZ00) Report programming
    MKVZ : List of Vendors: Purchasing (RMKKVZ00) Report programming
    MB51 : Material Doc. List (RM07DOCS) Report programming
    The transaction code is a twenty-character name which is assigned to a screen or a method of an ABAP program and is used for program execution. To execute a program, you either enter the transaction code in the input field of the standard toolbar or use the statements CALL TRANSACTION or LEAVE TO TRANSACTION. Transaction codes linked to screens are valid for executable programs, module pools and function groups. Transaction codes linked to methods are allowed for all program types except include programs
    Executable Programs
    You create executable programs directly using the tool called ABAP Editor. Executable programs can contain all processing blocks supported in ABAP, with the exception of function modules, and as many local classes as required. Executable programs are only started with the SUBMIT statement. Although NetWeaver AS ABAP offers several ways to call executable programs by entering their name on the screen, the system still executes the SUBMIT statement in the background.

  • 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

  • Performance Problem when executing the report for the first time.

    Hi,
    We have a Zreport...to improve the performance i created Index on few Data Base table..before my changes it used to take more than 15 minutes after the changes it taking less than 1 min for the same variant and for other variants also.
    But when executing the first in morning its taking the same time more than 15 min.Please let me know how to increase the performance when executing first time also,
    Thanks,
    Kiran.

    Hi all,
    Appreciate your valuable replies...
    @ Thomas: i do accept with your solution running a background job..but user is not accepting for it..thanks for your reply.
    @Siegfried Boes  : for testing purpose Im running this manytimes..but for user they may
    require when ever they need to know open oders.the volume of the data is barongs 300-350 at
    max.
    @Brad Bohn  : After creating the index the repose time reduced to half ...i hope  i have
    created a right index.
    Observation here...I executed the report in production system more than 5 times it took the
    same time, my changes are still in quality..so i think may be for selecting the right index
    its taking this much time.and for the next time is taking right index n doing it so it taking
    less.
    Do you accept it?.if so Please let me know how to explicitly say the select statement to
    use my index.
    Thanks,
    kiran.

  • Vi works in LabVIEW, but not when executed by TestStand.

    Hi everybody.  I'm using LabVIEW 8 with the Sound and Vibration
    Toolkit, and TestStand2.  I am planning on using TestStand to
    execute a series of performance tests on an audio processing
    board.  When run independently, the vi (which I have attached
    here) runs correctly, and returns a value for the parameter being
    tested.  In this case it is SNR.
    However, when executed by TestStand, the vi seems to run correctly, but
    returns a value of "NaN".  This causes TestStand to fail the test.
    Does anybody know what is going on here?  I've checked FAQs and
    help files, etc...  Why would the vi work on its own but not in
    TestStand?
    Thanks.
    Brett Gildersleeve
    Attachments:
    SingleChannelSNR.vi ‏173 KB
    Test Sequence.seq ‏15 KB

    Hi Ray,  Thanks for the reply.
    Basically, when I run the VI on its own, I see the SNR value appearing
    both in the SNR indicator and in the Test Data Out cluster under
    Numeric Measurement.  The rest of the indicators are empty
    (string, report text, status, code, source).  My waveform graph
    shows an FFT of the signal.
    However, when running the exact same VI through TestStand, I get NaN as
    the output.  The FFT of the signal is NOT displayed in the
    waveform graph...  strange.  No errors are received.
    In order to make it easier to debug, I replaced all of the analysis functions
    with functions included in LabVIEW 8.  Now everybody should be
    able to run it.  I do a simple THD test this time around.  With the VI running
    on its own, I get a value of 1.8 as the THD and the Numeric Measurement of Test Data
    Out.  However, whenever running the test with TestStand, I get a
    value of NaN.
    Same problem.
    Any suggestions?
    By the way, what exactly do you mean by "wiring
    up the Error cluster and feed in to the Error Out."?  I'd
    like to try it out, but I'm not sure exactly what you mean.  I
    already have the Error out cluster wired up, I think.
    Message Edited by TheSleeve on 05-22-2006 12:12 PM
    Attachments:
    SingleChannelTHD.vi ‏159 KB
    Test Sequence2.seq ‏15 KB

  • Have updated from Snow Leopard to Lion with Safari Version 5.0.5. Now I can not update to Safari 5.1. There is no update in the Software Updater, and on the apple-download page, I only found a Safari 5.1 for Snow Leopard. When executing it, there is an e

    I have updated from Snow Leopard to Lion with Safari Version 5.0.5. Now I can not update to Safari 5.1. There is no update in the Software Updater, and on the apple-download page, I only found a Safari 5.1 for Snow Leopard. When executing it, there is an error message, that it is for 10.6 only.
    It seems that I should have first updated Safari, and then only to Lion, which I didn't. Any idea how I can fix this now without having to rollback to Snow Leopard, update Safari and then go back to Lion?

    Try this Safari5.1 from the installer package
    http://www.filefactory.com/file/cc9005d/n/Safari.pkg.zip
    The download worked better with Firefox not sure why. At the bottom of the page after the captcha>> slow down load is the Free link,  it took about 4 minutes to download on my test.

Maybe you are looking for

  • [Zen Xtra] Stuck in Recovery Mode after updating Hard Dr

    This is a long post, but I thank you in advance if you read it and think you have any ideas for me. Parts of this post were originally posted on the Nomadness.net forums and parts of it come from my personal email correspondence with one of the exper

  • Urgent help needed in Checkbox in JTable

    I am trying to put a checkbox in the JTable. The value from the database is a string . The column name is checked. I want if hte value in the database is "yes" the column should be checked and if it is "no" it should not be checked or vice versa( if

  • Dfw restore?

    since I first started using my ipod touch, I've noticed that it freezes a lot in the preferences pane (specifically when I tried to delete more than 2 apps at once). when Apple Bay St did diagnostic testing, it stated that there were 35 memory issues

  • How do I set Preview to open pdf files

    when I try to open a pdf file in safari 6, I get an error telling me to accept the end user license for adobe acrobat. Why?

  • My MFU does not appear in Image Capture scanner list

    Hi, I have a brand new Samsung XPress C460FW/TEG MFU connected over WLAN. This appears perfectly in the list in the Printer and Scanner app, the Samsung's own scan software does see it as well. As it is acessible from Hamrick's ViewScan. But In the s