Error in program SAPLCKDI screen 4610

Hi everyone.
I've have trouble with screen 4610 in program SAPLCKDI, during costing sales order.
In sometimes we have a runtime error in the same program and same screen.
That's the runtime error: Overwriting a protected field
In other cases, the mentioned screen appears with a lot of special characters like #.
The costin lot size field appears with a weird value over than 1 bilion.
Kind regards.

Hi Alex,
I have moved this thread to CO forum since this program belongs to CO rather than SD.
Best regards,
Smile

Similar Messages

  • SPAM - SAPKB70016 error during phase Generation of Programs and Screens

    Hi experts,
    I am trying import package SAP BASIS 700 level 16, but i have still errors in phase Generation of Programs and Screens:
    Program /OSP/SAPLR3_REPORT, Include /OSP/LR3_REPORTU38: Syntax error in line 000014
    Type '/OSP/REP_BADI' is unknown
    Program CL_HRBAS_INFTY_BL_COMPUTATION=CP, Include CL_HRBAS_INFTY_BL_COMPUTATION=CI: Syntax error in line 000005
    Type 'HRBAS00INFTYBL' is unknown
    Program CL_HRBAS_OBJECT_OPERATIONS====CP, Include IF_HRBAS_BUF_INTEGRATION_TO_PAIU: Syntax error in line 000007
    Type 'HRBAS_PD_PA_INTEGRATION' is unknown
    Program CL_HRBAS_RHOMBUFFER===========CP, Include IF_HRBAS_BUF_INTEGRATION_TO_PAIU: Syntax error in line 000007
    Type 'HRBAS_PD_PA_INTEGRATION' is unknown
    Program CL_PROXY_WSDL2ABAP============CP, Include CL_PROXY_WSDL2ABAP============CM03G: Syntax error in line 000004
    Type 'SPRX_PROXY_NAMEPROPOSAL' is unknown
    Program CL_WDR_CFG_PERSISTENCE_COMP===CP, Include CL_WDR_CFG_PERSISTENCE_COMP===CM005: Syntax error in line 000014
    Transformation 'WDR_CFG_COMP_TRANSL' has no activeversion
    Program CL_WSSE_PROCESSOR=============CP, Include CL_WSSE_PROCESSOR=============CM009: Syntax error in line 000131
    Transformation 'SEC_SAML_ASSERTION' has no activeversion
    Program SAPLPA_PACKAGE_CHECKS, Include LPA_PACKAGE_CHECKSTOP: Syntax error in line 000030
    Type 'WB_PACKAGE_COMPONENT_CHECK' is unknown
    System is: SAP ERP 6.0 IDES EHP3, kernel221, WIN2003, Oracle 10.2.0.4
    Can you help me pls?

    thank you for your help Sunny
    I solved problem:
    1.)
    Program /OSP/SAPLR3_REPORT, Include /OSP/LR3_REPORTU38: Syntax error in
    line 000014
    Type '/OSP/REP_BADI' is unknown 
    (SE18 -> reactivated Enhancement Spot /OSP/REP_ENH_SPOT  )
    2.)
    Program CL_HRBAS_INFTY_BL_COMPUTATION=CP, Include
    CL_HRBAS_INFTY_BL_COMPUTATION=CI: Syntax error in line 000005
    Type 'HRBAS00INFTYBL' is unknown
    Program CL_HRBAS_OBJECT_OPERATIONS====CP, Include
    IF_HRBAS_BUF_INTEGRATION_TO_PAIU: Syntax error in line 000007
    Type 'HRBAS_PD_PA_INTEGRATION' is unknown
    Program CL_HRBAS_RHOMBUFFER===========CP, Include
    IF_HRBAS_BUF_INTEGRATION_TO_PAIU: Syntax error in line 000007
    Type 'HRBAS_PD_PA_INTEGRATION' is unknown
    Program CL_PROXY_WSDL2ABAP============CP, Include
    CL_PROXY_WSDL2ABAP============CM03G: Syntax error in line 000004
    Type 'SPRX_PROXY_NAMEPROPOSAL' is unknown
    Program SAPLPA_PACKAGE_CHECKS, Include LPA_PACKAGE_CHECKSTOP: Syntax
    error in line 000030
    Type 'WB_PACKAGE_COMPONENT_CHECK' is unknown
    (SE18 -> reactivated types)
    3.)
    Program CL_WDR_CFG_PERSISTENCE_COMP===CP, Include
    CL_WDR_CFG_PERSISTENCE_COMP===CM005: Syntax error in line 000014
    Transformation 'WDR_CFG_COMP_TRANSL' has no activeversion
    CL_WDR_CFG_PERSISTENCE_COMP===CP ,
    Program CL_WSSE_PROCESSOR=============CP, Include
    CL_WSSE_PROCESSOR=============CM009: Syntax error in line 000131
    Transformation 'SEC_SAML_ASSERTION' has no activeversion
    (Tcode STRANS -> reactivated Transformations
    Edited by: Miroslav Mihok on Oct 6, 2009 3:37 PM

  • Error while writting a screen in report

    Hello Friends,
                            I am running a report while executing i am getting error Error when writing a screen,
    If anyone have useful answer please replay.
    Thanking
    Shrikant

    Hello ,
    While running program i am getting following dump error.
    Short text                                                                        
        Error when writing a screen.                                                                               
    What happened?                                                                    
        Error in the SAP kernel.                                                                               
    The current ABAP "ZHRM_DEVIATION_ALL" program had to be terminated because the
        ABAP processor detected an internal system error.                             
    Thanks
    Shrikant

  • Syntax error in program "SAPLXRSA " -SENT

    Hi Guys,
    I have done user exit in R/3 datasource when I do the test extraction using RSA3 and geting the data without any error. I've transport the requet to Test Box and tried to do the extraction in TestBox and getting the below SYNTAX Error message. Kindly advise it's very URGET. Thanks in advance.
    ShrtText
    Syntax error in program "SAPLXRSA ".
    What happened?
    Error in ABAP application program.
    The current ABAP program "SAPLRSAP" had to be terminated because one of the
    statements could not be executed.
    This is probably due to an error in the ABAP program.
    In program "SAPLXRSA ", the following syntax error occurred
    in the Include "ZXRSAU01 " in line 21:
    "Field "ZOXPRO0043" is unknown. It is neither in one of the specified t"
    "ables nor defined by a "DATA" statement. "DATA" statement."
    Author and last person to change the Include are:
    Author "SAPCHEOLENG "
    Last changed by "CCEV200 "
    What can you do?
    Please eliminate the error by performing a syntax check
    (or an extended program check) on the program "SAPLXRSA ".
    You can also perform the syntax check from the ABAP/4 Editor.
    If the problem persists, proceed as follows:
    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
    In program "SAPLXRSA ", the following syntax error occurred:
    "Field "ZOXPRO0043" is unknown. It is neither in one of the specified t"
    "ables nor defined by a "DATA" statement. "DATA" statement."
    How to correct the error
    Probably the only way to eliminate the error is to correct the program.
    If you cannot solve the problem yourself and you wish to send
    an error message to SAP, include the following documents:
    1. A printout of the problem description (short dump)
    To obtain this, select in the current display "System->List->
    Save->Local File (unconverted)".
    2. A suitable printout of the system log
    To obtain this, call the system log through transaction SM21.
    Limit the time interval to 10 minutes before and 5 minutes
    after the short dump. In the display, then select the function
    "System->List->Save->Local File (unconverted)".
    3. If the programs are your own programs or modified SAP programs,
    supply the source code.
    To do this, select the Editor function "Further Utilities->
    Upload/Download->Download".
    4. Details regarding the conditions under which the error occurred
    or which actions and input led to the error.
    System environment
    SAP Release.............. "640"
    Application server....... "hawk"
    Network address.......... "137.132.12.22"
    Operating system......... "HP-UX"
    Release.................. "B.11.23"
    Hardware type............ "ia64"
    Character length......... 8 Bits
    Pointer length........... 64 Bits
    Work process number...... 0
    Short dump setting....... "full"
    Database server.......... "hawk"
    Database type............ "ORACLE"
    Database name............ "QAS"
    Database owner........... "SAPR3"
    Character set............ "en_US.iso88591"
    SAP kernel............... "640"
    Created on............... "Oct 16 2006 20:35:55"
    Created in............... "HP-UX B.11.23 U ia64"
    Database version......... "OCI_920 "
    Patch level.............. "153"
    Patch text............... " "
    Supported environment....
    Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE
    10.2.0.."
    SAP database version..... "640"
    Operating system......... "HP-UX B.11"
    Memory usage.............
    Roll..................... 16128
    EM....................... 12569760
    Heap..................... 0
    Page..................... 65536
    MM Used.................. 1716768
    MM Free.................. 2470608
    SAP Release.............. "640"
    User and Transaction
    Client.............. 220
    User................ "CCEENGG"
    Language key........ "E"
    Transaction......... "RSA3 "
    Program............. "SAPLRSAP"
    Screen.............. "SAPMSSY0 1000"
    Screen line......... 6
    Information on where terminated
    The termination occurred in the ABAP program "SAPLRSAP" in
    "CALL_DATA_CUSTOMER_FUNCTION".
    The main program was "RSFHGEN2 ".
    The termination occurred in line 96 of the source code of the (Include)
    program "LRSAPF06"
    of the source code of program "LRSAPF06" (when calling the editor 960).
    Source Code Extract
    Line
    SourceCde
    66
    CALL FUNCTION BW_BTE_CALL_BW204010_E
    67
    EXPORTING
    68
    I_DATASOURCE = L_DATASOURCE
    69
    I_UPDMODE    = P_UPDMODE
    70
    TABLES
    71
    I_T_SELECT   = P_T_SELECT
    72
    I_T_FIELDS   = P_T_FIELDS
    73
    C_T_DATA     = P_T_DATA
    74
    C_T_MESSAGES = L_T_MESSAGES
    75
    EXCEPTIONS
    76
    OTHERS       = 1.
    77
    DESCRIBE TABLE P_T_DATA LINES L_LINES.
    78
    MESSAGE S408 WITH L_LINES.
    79
    Handle BTE-Exit error messages
    80
    IF SY-SUBRC <> 0.
    81
    P_SUBRC = SY-SUBRC.
    82
    IF 1 = 2. MESSAGE E021 WITH ''. ENDIF.
    83
    MESSAGE_WRITE 'E' 'R3' '021' 'BW_BTE_CALL_BW204010_E' '' '' ''.
    84
    ENDIF.
    85
    IF NOT L_T_MESSAGES IS INITIAL.
    86
    PERFORM WRITE_BTE_EXIT_MESSAGES TABLES   L_T_MESSAGES
    87
    CHANGING P_SUBRC.
    88
    ENDIF.
    89
    ENDIF.
    90
    ENDIF.
    91
    92
    Call Customer-Exit
    93
    DESCRIBE TABLE P_T_DATA LINES L_LINES.
    94
    MESSAGE S407 WITH 'EXIT_SAPLRSAP_001' 'CMOD' L_LINES.
    95
    CLEAR SY-SUBRC.
    >>>>>
    CALL CUSTOMER-FUNCTION '001'
    97
    EXPORTING
    98
    I_DATASOURCE             = L_DATASOURCE
    99
    I_ISOURCE                = L_12B_SOURCE
    100
    I_UPDMODE                = P_UPDMODE
    101
    TABLES
    102
    I_T_SELECT               = P_T_SELECT
    103
    I_T_FIELDS               = P_T_FIELDS
    104
    C_T_DATA                 = P_T_DATA
    105
    C_T_MESSAGES             = L_T_MESSAGES
    106
    EXCEPTIONS
    107
    RSAP_CUSTOMER_EXIT_ERROR = 1
    108
    OTHERS                   = 2.
    109
    DESCRIBE TABLE P_T_DATA LINES L_LINES.
    110
    MESSAGE S408 WITH L_LINES.
    111
    112
    Handle Customer-Exit error messages
    113
    IF SY-SUBRC <> 0.
    114
    P_SUBRC = SY-SUBRC.
    115
    IF 1 = 2. MESSAGE E020 WITH ''. ENDIF.
    Contents of system fields
    Name
    Val.
    SY-SUBRC
    0
    SY-INDEX
    1
    SY-TABIX
    1
    SY-DBCNT
    0
    SY-FDPOS
    0
    SY-LSIND
    0
    SY-PAGNO
    0
    SY-LINNO
    1
    SY-COLNO
    1
    SY-PFKEY
    SY-UCOMM
    SY-TITLE
    Report for the extractor call
    SY-MSGTY
    S
    SY-MSGID
    R3
    SY-MSGNO
    407
    SY-MSGV1
    EXIT_SAPLRSAP_001
    SY-MSGV2
    CMOD
    SY-MSGV3
    100
    SY-MSGV4
    Active Calls/Events
    No.   Ty.          Program                             Include                             Line
    Name
    5 FUNCTION     SAPLRSAP                            LRSAPF06                               96
    CALL_DATA_CUSTOMER_FUNCTION
    4 FORM         SAPLRSAP                            LRSAPF06                               96
    CALL_DATA_CUSTOMER_FUNCTION
    3 FORM         GP3PDR0GQDXJ0ZOA35DPGNCU80M         GP3PDR0GQDXJ0ZOA35DPGNCU80M           274
    PROCESS_DATA_PACKAGE
    2 FORM         GP3PDR0GQDXJ0ZOA35DPGNCU80M         GP3PDR0GQDXJ0ZOA35DPGNCU80M           170
    DATA_TRANSFER
    1 EVENT        RSFHGEN2                            RSFHGEN2                               59
    START-OF-SELECTION

    Hello Raja,
    I think some objects should still lying in the dev. server which are yet to be transported, also try to deactivate and reactivate the project for user exit for BW and transport it .
    Also manually request can be created for transporting object "ZOXPRO0043" into quality environment and transport it .
    Let us know the output for the same.
    Hope that helps.
    Regards
    Kapadia
    ***Assigning points is the way to say thanks in SDN.***

  • Itunes wont launch, no error message, no blue screens, just wont open

    itunes wont launch, i get no error message, no blue screen, it just wont open. I've tried to delete and reinstall, but once i close itunes i still have same issue. it wont open again.

    I have same problem  on my XP lap top and Windows 7 PC.    Apple have been investigating this problem for me for a week now without success so far.  Understand it 's ongoing with other customers as well.
      It is caused by an bit of program called APSDaemon supplied by Apple in latest i-Tunes.     Your quick fix to enable you to open i-Tunes again is as follows:-     open Task Manager (right click bottom toolbar), click on Task Manager, select Processes.   Find APSDaemon, highlight and press END PROCESS.      I-tunes will now re-open ok.   You have to repeat this every time you want i-Tunes re-opened until you switchoff or restart.
    A pain I know, but lets you keep going until Apple repair and release an update for i-Tunes

  • Short dump in VF01 - Syntax error in program "RKEAK9RECP3000001"

    Helo all,
    We recently copied our production client to a QA client and when we try to save an SD invoice (VF01), we get a short dump titled - Syntax error in program "RKEAK9RECP3000001".
    The dump long text states:
    "The Dictionary structure or table "K9RECP3000001" is either not active"
    " or does not exist."
    and
    NOTE in case of a SHORT DUMP:
    if the following perform statement should lead to a short dump, then
    the report stated in the short dump is missing (RKEAK9Rsssmmmnnnn)
    Check if table K9Rsssmmmnnn exists. If not it should be transported
    from the original system.
    Regenerate the missing reports by using transaction SE37, entering
    function KEDR_REGENERATE_ALL_REPORTS and pressing button 'Test' and
    'Execute'.
    but I tried to run function KEDR_REGENERATE_ALL_REPORTS in SE37 and the problem persists.
    Maybe I'm not running it correctly - there is no execute option when pressing "Test" so I enter the function and press F8, which takes me to a screen titled "Test function module" and then I execute.
    My suspicion is that table "K9RECP3000001" cannot be created or generated since it it a system specific naming convention K9RSSSCCC0001 in which SSS is system ID (in our case ECP is production and ECQ is QA) ans CCC is client number (300 in prod, and should be 286 in ECQ).
    Has anyone encountered this type of a problem and knows how to fix it?
    Needless to say, I looked at OSS notes, but did not find the solution there.
    Any thought will be appreciated,
    Yoel.

    Shalom Yoel,
    This problem may be caused by the fact that some derivation rules
    that were originally created once in a system have been transported
    into target system without transporting the dependent objects
    as well (the generated tables for the derivation rule entries).
    You can see this by execution of program RKEDRCHECK with only
    parameter 'Check in all clients' marked. You will then get
    inconsistent derivation steps (which refer to a generated table
    table for the rule entries that doesn't exist because it was
    not transported).
    There are two ways to solve the problem:
    1.) If you don't need these steps any more in derivation you can get
        rid of them by executing program RKEDRCHECK with both parameters
        marked ('Check in all clients' and 'Delete inconsistent steps').
    2.) If these steps should remain you have to retransport the missing
        tables from the source system in which these tables have to exist
        (creating transport requests for the customizing of derivation by
        pushing on the 'Transport' icon in the source system in transactions
        KEDR and KEPC).
    For each derivation step,the system generates a program RKEAK9R *
    and a table K9R+ System ID+ Mandant+ a number of five figures
    from the object number in KEDR.
    br, Guido

  • Syntax error in program "SAPLHTTPTREE " during application of SAPKB70012

    Hi everyone,
    I am applying support pack SAPKB70012 when it stopped in the XPRA_EXECUTION phase. Anybody encountered this error "Syntax error in program "SAPLHTTPTREE "? Been looking for any notes on this but haven't found anything. I already created message to SAP but even though its high, nobody's picking it up. We're using Windows NT and database MSSQL.
    Below is part of the import queue log:
    The following details help you to analyze the problem:
        -   Error in phase: XPRA_EXECUTION
        -   Reason for error: TP_STEP_FAILURE
        -   Return code: 0012
        -   Error message: OCS Package SAPKB70012, tp step R, return code
            0012
    Notes on phase XPRA_EXECUTION
    The XPRAs and after-import methods are executed in this phase. This
    phase can terminate due to the following reasons:
    o   TP_INTERFACE_FAILURE: The system was unable to call the tp
        interface.
    o   TP_FAILURE: The system was unable to execute the tp program. For
        more information, see the SLOG or ALOG log file.
    When I check SM37, I found this ABAP runtime error:
    *job: RDDEXEC
    Runtime Errors         SYNTAX_ERROR
    Date and Time          16.01.2008 19:13:09
    Short text
    Syntax error in program "SAPLHTTPTREE ".
    What happened?
    Error in the ABAP Application Program
    The current ABAP program "SAPLSCTS_EXE_EXP" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
    The following syntax error occurred in program "SAPLHTTPTREE " in include
    "LHTTPTREETOP " in
    line 9:
    ""ICFALIAS" must be a flat structure. You cannot use internal tables, s"
    "trings, references, or structures as components ."
    The include has been created and last changed by:
    Created by: "SAP "
    Last changed by: "SAP "
    What can you do?
    Please eliminate the error by performing a syntax check
    (or an extended program check) on the program "SAPLHTTPTREE ".
    You can also perform the syntax check from the ABAP Editor.
    If the problem persists, proceed as follows:
    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
    The following syntax error was found in the program SAPLHTTPTREE :
    ""ICFALIAS" must be a flat structure. You cannot use internal tables, s"
    "trings, references, or structures as components ."
    How to correct the error
    Probably the only way to eliminate the error is to correct the program.
    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.
    User and Transaction
    Client.............. 000
    User................ "DDIC"
    Language key........ "E"
    Transaction......... " "
    Transactions ID..... "0224C4DC1741F1C28D9D001A4BDB2C98"
    Program............. "SAPLSCTS_EXE_EXP"
    Screen.............. "SAPMSSY0 1000"
    Screen line......... 6
    Information on where terminated
    Termination occurred in the ABAP program "SAPLSCTS_EXE_EXP" - in
    "CALL_IMP_METHODS_IN_CLIENT".
    The main program was "RDDEXECU ".
    In the source code you have the termination point in line 351
    of the (Include) program "LSCTS_EXE_EXPF02".
    The program "SAPLSCTS_EXE_EXP" was started as a background job.
    Job Name....... "RDDEXECL"
    Job Initiator.. "DDIC"
    Job Number..... 19130500
    Source Code Extract
    Line
    SourceCde
    321
    CLEAR: sy-msgid, sy-msgty, sy-msgno.
    322
    323
    IF ps_spec_pars-with_data_file EQ 'X'.
    324
    CALL FUNCTION ps_method_call-method_fb
    325
    EXPORTING
    326
    iv_tarclient  = ps_client-client
    327
    iv_is_upgrade = pv_is_upgrade
    328
    iv_datafile   = ps_spec_pars-data_file
    329
    TABLES
    330
    tt_e071       = lt_e071
    331
    tt_e071k      = lt_e071k.
    332
    ELSEIF ps_spec_pars-with_asynch_mode EQ 'X'.
    333
    CALL FUNCTION ps_method_call-method_fb
    334
    EXPORTING
    335
    iv_tarclient    = ps_client-client
    336
    iv_is_upgrade   = pv_is_upgrade
    337
    iv_asynchronous = ps_spec_pars-asynch_mode
    338
    TABLES
    339
    tt_e071         = lt_e071
    340
    tt_e071k        = lt_e071k.
    341
    ELSEIF ps_spec_pars-with_cl_results EQ 'X'.
    342
    CALL FUNCTION ps_method_call-method_fb
    343
    EXPORTING
    344
    iv_trkorr     = pv_trkorr
    345
    iv_is_upgrade = pv_is_upgrade
    346
    it_e071       = lt_e071
    347
    it_e071k      = lt_e071k
    348
    CHANGING
    349
    it_client     = ps_spec_pars-clients.
    350
    ELSE.
    >>>>>
    CALL FUNCTION ps_method_call-method_fb
    352
    EXPORTING
    353
    iv_tarclient  = ps_client-client
    354
    iv_is_upgrade = pv_is_upgrade
    355
    TABLES
    356
    tt_e071       = lt_e071
    357
    tt_e071k      = lt_e071k.
    358
    ENDIF.
    359
    360
    361
    reset info on called method in memory.
    362
    CALL FUNCTION 'TRINT_RESET_STACK_KILLER'.
    363
    check if method call has deleted variables in global memory
    364
    and set those variables again
    365
    CALL FUNCTION 'TRINT_CHECK_VARS_IN_MEMORY'
    366
    IMPORTING
    367
    ev_ok = lv_ok.
    368
    IF lv_ok = ' '.
    369
    memory destroyed: set all clients to errornous for security
    370
    for methods of switch framework
    Contents of system fields
    Name
    Val.
    SY-SUBRC
    0
    SY-INDEX
    0
    SY-TABIX
    1
    SY-DBCNT
    1
    SY-FDPOS
    2
    SY-LSIND
    0
    SY-PAGNO
    0
    SY-LINNO
    1
    SY-COLNO
    1
    SY-PFKEY
    SY-UCOMM
    SY-TITLE
    Execute Post-Import Methods and XPRAs for Transport Request
    SY-MSGTY
    SY-MSGID
    SY-MSGNO
    000
    SY-MSGV1
    ASYNCH_IAC_PUBLISH
    SY-MSGV2
    0011
    SY-MSGV3
    SY-MSGV4
    SY-MODNO
    0
    SY-DATUM
    20080116
    SY-UZEIT
    191309
    SY-XPROG
    SAPLSYST
    SY-XFORM
    SYSTEM_HOOK_OPEN_DATASET
    Active Calls/Events
    No.   Ty.          Program                             Include                             Line
    Name
    5 FUNCTION     SAPLSCTS_EXE_EXP                    LSCTS_EXE_EXPF02                      351
    CALL_IMP_METHODS_IN_CLIENT
    4 FORM         SAPLSCTS_EXE_EXP                    LSCTS_EXE_EXPF02                      351
    CALL_IMP_METHODS_IN_CLIENT
    3 FORM         SAPLSCTS_EXE_EXP                    LSCTS_EXE_EXPF02                       87
    CALL_IMP_METHODS
    2 FUNCTION     SAPLSCTS_EXE_EXP                    LSCTS_EXE_EXPU02                      103
    TRINT_CALL_AFTER_IMP_METHOD
    1 EVENT        RDDEXECU                            RDDEXECU                              171
    START-OF-SELECTION
    Chosen variables
    Name
    Val.
    No.       5 Ty.          FUNCTION
    Name  CALL_IMP_METHODS_IN_CLIENT
    GC_GNS_NO_DIFF
    /0*/
    2322222222
    F0AF000000
    0000000000
    0000000000
    LT_E071
    Table IT_137[21x360]
    FUNCTION-POOL=SCTS_EXE_EXPFORM=CALL_IMP_METHODS_IN_CLIENTDATA=LT_E071
    Table reference: 46
    TABH+  0(20) = B0A6D957FE07000050C8D957FE07000000000000
    TABH+ 20(20) = 2E000000890000001500000068010000FFFFFFFF
    TABH+ 40(16) = 044D0000F00B000015000000C9248001
    store        = 0xB0A6D957FE070000
    ext1         = 0x50C8D957FE070000
    shmId        = 0     (0x00000000)
    id           = 46    (0x2E000000)
    label        = 137   (0x89000000)
    fill         = 21    (0x15000000)
    leng         = 360   (0x68010000)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000049
    occu         = 21    (0x15000000)
    access       = 1     (ItAccessStandard)
    idxKind      = 1     (ItIndexLinear)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 1
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0xF0C0E257FE070000
    pgHook       = 0x0000000000000000
    idxPtr       = 0x10A7D957FE070000
    shmTabhSet   = 0x0000000000000000
    id           = 111   (0x6F000000)
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 21    (0x15000000)
    lineAlloc    = 21    (0x15000000)
    shmVersId    = 0     (0x00000000)
    shmRefCount  = 2     (0x02000000)
    >>>>> 1st level extension part <<<<<
    regHook      = 0x90C4D957FE070000
    collHook     = 0x0000000000000000
    ext2         = 0x0000000000000000
    >>>>> 2nd level extension part <<<<<
    tabhBack     = Not allocated
    delta_head   = Not allocated
    pb_func      = Not allocated
    pb_handle    = Not allocated
    GC_GNS_NO_SPECIFIC
    2222222222
    FAF0000000
    0000000000
    0000000000
    LT_E071K
    Table[initial]
    RELSET
    RNO
    544
    2EF
    000
    000
    PS_SPEC_PARS-WITH_CL_RESULTS
    2
    0
    0
    0
    SY-XPROG
    SAPLSYST
    5454555522222222222222222222222222222222
    310C393400000000000000000000000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    PS_METHOD_CALL-METHOD_FB
    SICF_AFTER_IMPORT
    544454454554454552222222222222
    3936F16452F9D0F240000000000000
    000000000000000000000000000000
    000000000000000000000000000000
    GC_PARTNRPR_BACK_TO_STNDRD
    1A&1B&1H&1I&2I&3R
    34234234234234235
    11612618619629632
    00000000000000000
    00000000000000000
    PV_IS_UPGRADE
    2
    0
    0
    0
    %_ARCHIVE
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    PV_TRKORR
    SAPKB70012
    54544333332222222222
    310B2700120000000000
    00000000000000000000
    00000000000000000000
    SYST-REPID
    SAPLSCTS_EXE_EXP
    5454545554545455222222222222222222222222
    310C3343F585F580000000000000000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    DEVC_PREFIXNS
    N
    4
    E
    0
    0
    PS_SPEC_PARS-CLIENTS
    Table[initial]
    %_PRINT
    000                                                                                0###
    2222333222222222222222222222222222222222222222222222222222222222222222222222222222222222223000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    PS_CLIENT-CLIENT
    222
    000
    000
    000
    %_DUMMY$$
    2222
    0000
    0000
    0000
    No.       4 Ty.          FORM
    Name  CALL_IMP_METHODS_IN_CLIENT
    LT_E071
    Table IT_137[21x360]
    LT_E071K
    Table[initial]
    PS_SPEC_PARS-WITH_CL_RESULTS
    2
    0
    0
    0
    PS_METHOD_CALL-METHOD_FB
    SICF_AFTER_IMPORT
    544454454554454552222222222222
    3936F16452F9D0F240000000000000
    000000000000000000000000000000
    000000000000000000000000000000
    PV_IS_UPGRADE
    2
    0
    0
    0
    PV_TRKORR
    SAPKB70012
    54544333332222222222
    310B2700120000000000
    00000000000000000000
    00000000000000000000
    PS_SPEC_PARS-CLIENTS
    Table[initial]
    PS_CLIENT-CLIENT
    222
    000
    000
    000
    No.       3 Ty.          FORM
    Name  CALL_IMP_METHODS
    PV_TRKORR
    SAPKB70012
    54544333332222222222
    310B2700120000000000
    00000000000000000000
    00000000000000000000
    PV_NO_WORK_FOUND
    2
    0
    0
    0
    PT_CLIENT
    Table IT_21[1x8]
    PROGRAM=RDDEXECUDATA=GT_CLIENT
    Table reference: 16
    TABH+  0(20) = B0311757FE070000000000000000000000000000
    TABH+ 20(20) = 10000000150000000100000008000000FFFFFFFF
    TABH+ 40(16) = 040000009008000010000000C1248001
    store        = 0xB0311757FE070000
    ext1         = 0x0000000000000000
    shmId        = 0     (0x00000000)
    id           = 16    (0x10000000)
    label        = 21    (0x15000000)
    fill         = 1     (0x01000000)
    leng         = 8     (0x08000000)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000031
    occu         = 16    (0x10000000)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 1
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0x10311757FE070000
    pgHook       = 0x0000000000000000
    idxPtr       = 0x0000000000000000
    shmTabhSet   = 0x0000000000000000
    id           = 20    (0x14000000)
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 16    (0x10000000)
    lineAlloc    = 16    (0x10000000)
    shmVersId    = 0     (0x00000000)
    shmRefCount  = 1     (0x01000000)
    >>>>> 1st level extension part <<<<<
    regHook      = Not allocated
    collHook     = Not allocated
    ext2         = Not allocated
    >>>>> 2nd level extension part <<<<<
    tabhBack     = Not allocated
    delta_head   = Not allocated
    pb_func      = Not allocated
    pb_handle    = Not allocated
    LS_CLIENT_H
    2222
    0000
    0000
    0000
    TTRA
    T
    5
    4
    0
    0
    SY
    ######################################f#######################################T#########  ####
    0000000000000000000000000000000000000060000000000000000000000000000000000000105000000080220000
    0000104000000000000010201000100000000060000000000000000000000000000000000000604000000000000300
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000070000000
    000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000C
    PV_UPDATE_LOCKFLAG
    X
    5
    8
    0
    0
    PV_CTC
    2
    0
    0
    0
    PV_STATLOG_FILE
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    PS_METHOD_CALL
    AFTER_IMP SICF_AFTER_IMPORT              ###Á#>#À#?###@#
    44545544525444544545544545522222222222222000C030C0309040
    16452F9D003936F16452F9D0F240000000000000000010E000F0F000
    00000000000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000000000
    PV_IS_UPGRADE
    2
    0
    0
    0
    PV_TOP_LEVEL
    2
    3
    2
    0
    0
    PS_SPEC_PARS
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    PS_METHOD_CALL-CLIDEP
    2
    0
    0
    0
    PS_SPEC_PARS-WITH_CL_RESULTS
    2
    0
    0
    0
    %_VIASELSCR
    0
    4
    No.       2 Ty.          FUNCTION
    Name  TRINT_CALL_AFTER_IMP_METHOD
    IS_E070
    SAPKB70012          DRSAP       SYSTSAPUSER     20080116185743
    5454433333222222222245545222222255555455545222223333333333333322222222222222222222
    310B270012000000000042310000000039343105352000002008011618574300000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000
    IT_E071
    Table IT_15[23207x360]
    PROGRAM=RDDEXECUDATA=E071_TAB[]
    Table reference: 10
    TABH+  0(20) = C0841857FE070000B0611757FE07000000000000
    TABH+ 20(20) = 0A0000000F000000A75A000068010000FFFFFFFF
    TABH+ 40(16) = 04000000C005000010000000C1248001
    store        = 0xC0841857FE070000
    ext1         = 0xB0611757FE070000
    shmId        = 0     (0x00000000)
    id           = 10    (0x0A000000)
    label        = 15    (0x0F000000)
    fill         = 23207 (0xA75A0000)
    leng         = 360   (0x68010000)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000016
    occu         = 16    (0x10000000)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 1
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0x206E1857FE070000
    pgHook       = 0x30047F57FE070000
    idxPtr       = 0x0000000000000000
    shmTabhSet   = 0x0000000000000000
    id           = 14    (0x0E000000)
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 32752 (0xF07F0000)
    lineAlloc    = 23216 (0xB05A0000)
    shmVersId    = 0     (0x00000000)
    shmRefCount  = 1     (0x01000000)
    >>>>> 1st level extension part <<<<<
    regHook      = 0x0000000000000000
    collHook     = 0x0000000000000000
    ext2         = 0x40611757FE070000
    >>>>> 2nd level extension part <<<<<
    tabhBack     = 0xD0C31F57FE070000
    delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
    pb_func      = 0x0000000000000000
    pb_handle    = 0x0000000000000000
    IT_E071K
    Table IT_16[6045x564]
    PROGRAM=RDDEXECUDATA=E071K_TAB[]
    Table reference: 11
    TABH+  0(20) = 20851857FE070000F0611757FE07000000000000
    TABH+ 20(20) = 0B000000100000009D17000034020000FFFFFFFF
    TABH+ 40(16) = 040000005006000010000000C1248001
    store        = 0x20851857FE070000
    ext1         = 0xF0611757FE070000
    shmId        = 0     (0x00000000)
    id           = 11    (0x0B000000)
    label        = 16    (0x10000000)
    fill         = 6045  (0x9D170000)
    leng         = 564   (0x34020000)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000019
    occu         = 16    (0x10000000)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 1
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0x00C49357FE070000
    pgHook       = 0x60E75357FE070000
    idxPtr       = 0x0000000000000000
    shmTabhSet   = 0x0000000000000000
    id           = 15    (0x0F000000)
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 8192  (0x00200000)
    lineAlloc    = 6048  (0xA0170000)
    shmVersId    = 0     (0x00000000)
    shmRefCount  = 1     (0x01000000)
    >>>>> 1st level extension part <<<<<
    regHook      = 0x0000000000000000
    collHook     = 0x0000000000000000
    ext2         = 0xE06F1757FE070000
    >>>>> 2nd level extension part <<<<<
    tabhBack     = 0x806F1757FE070000
    delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
    pb_func      = 0x0000000000000000
    pb_handle    = 0x0000000000000000
    IV_CTC
    2
    0
    0
    0
    IV_DATNAME
    :D:T:S:data:F:IB70012.SAP
    3435353667634344333332545222222222222222222222222222222222222222222222222222222222222222222222
    A4A4A3A4141A6A9270012E310000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    IV_SFW_CALL
    2
    0
    0
    0
    IV_STATLOG_FILE
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    IV_TRKORR
    SAPKB70012
    54544333332222222222
    310B2700120000000000
    00000000000000000000
    00000000000000000000
    IV_UPDATE_LOCKFLAG
    X
    5
    8
    0
    0
    IT_CLIENT
    Table IT_21[1x8]
    LS_SPEC_PARS-NOT_DURING_UPGRADE
    2
    0
    0
    0
    ALLSTAT
    RNODL
    54444222222222222222222222
    2EF4C000000000000000000000
    00000000000000000000000000
    00000000000000000000000000
    LV_UPGRADE_IS_RUNNING
    2
    0
    0
    0
    TMVD
    E
    4
    5
    0
    0
    RSJOBINFO
    00000000000000                                  ##
    2222222222222222222222222222222233333333333333222222222222222222222222222222222200
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000
    <LS_METHOD_CALL>
    AFTER_IMP SICF_AFTER_IMPORT              ###Á#>#À#?###@#
    44545544525444544545544545522222222222222000C030C0309040
    16452F9D003936F16452F9D0F240000000000000000010E000F0F000
    00000000000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000000000
    LV_IS_UPGRADE
    2
    0
    0
    0
    LV_TOP_LEVEL
    2
    3
    2
    0
    0
    LV_NO_WORK_FOUND
    2
    0
    0
    0
    LS_SPEC_PARS
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    SPACE
    2
    0
    0
    0
    No.       1 Ty.          EVENT
    Name  START-OF-SELECTION
    SCREEN
    %_17NNS0000691660_%_%_%_%_%_%_
    2533445333333333352525252525252222222222222222222222222222222222222222222222222222222222222222
    5F17EE30000691660F5F5F5F5F5F5F0000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    SYST
    ######################################f#######################################T#########  ####
    0000000000000000000000000000000000000060000000000000000000000000000000000000105000000080220000
    0000104000000000000010201000100000000060000000000000000000000000000000000000604000000000000300
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000070000000
    000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000C
    GT_CLIENT
    Table IT_21[1x8]
    GS_CLIENT
    2222
    0000
    0000
    0000
    DATNAME
    :D:T:S:data:F:IB70012.SAP
    3435353667634344333332545222222222222222222222222222222222222222222222222222222222222222222222
    A4A4A3A4141A6A9270012E310000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    %_DATNAME_%_APP_%
    Data File Name (from TRBAT)
    467624666246662267662554452222
    4141069C50E1D50862FD0422149000
    000000000000000000000000000000
    000000000000000000000000000000
    E071_TAB[]
    Table IT_15[23207x360]
    E071K_TAB[]
    Table IT_16[6045x564]
    SY-SUBRC
    0
    0000
    0000
    GV_CTC
    2
    0
    0
    0
    GV_TRBAT_DATNAME
    :D:T:S:data:F:IB70012.SAP
    3435353667634344333332545222222222222222222222222222222222222222222222222222222222222222222222
    A4A4A3A4141A6A9270012E310000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    <%_TABLE_E071>
    <%_TABLE_E071K>
    GV_STATLOG_FILE
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    COMFILE
    SAPKB70012
    54544333332222222222
    310B2700120000000000
    00000000000000000000
    00000000000000000000
    SY-LANGU
    E
    4
    5
    0
    0
    SY
    ######################################f#######################################T#########  ####
    0000000000000000000000000000000000000060000000000000000000000000000000000000105000000080220000
    0000104000000000000010201000100000000060000000000000000000000000000000000000604000000000000300
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000070000000
    000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000C
    SPACE
    2
    0
    0
    0
    Internal notes
    The termination was triggered in function "ab_genprog"
    of the SAP kernel, in line 1476 of the module
    "//bas/700_REL/src/krn/runt/abgen.c#5".
    The internal operation just processed is "FUNC".

    Good Morning
    Did you ever get this working without restoring ?
    Kind Regards
    Marius

  • Throwing error msg in selection screen

    Hi all,
    I want to throw one error message in selection screen .
    This message is of more than 1000 chars.   and i want to show these 1000 chars in  a pop up window and when i press 'TICK' mark, it should stay only in the selection screen . It should not go to the output screen and it should not leave the transaction either..
    Can anyone help me in this by providing the coding for this..
    Regards,
    Shanthi

    Hi Shanthi,
    Your requirement is fulfilled by standard SAP message processing. Through message maintenance (TCode SE91), you define a message with a long text.
    Let us say the message class is ZSHANTHI and the message number is 025. Besides the message short text you defined say 'Something wrong with &. Refer Long Text', un-check the checkk-box 'Self Explanatory', choose this message number and click on 'Long Text' button on the application toolbar. You will get long text editor and you can compose your 1000 lines or even 1000 pages story there.
    Now let us see what you need to do in the report program. Your requirement is 'Issue the error message. When user hits Tick, display long text in a modal window and later stay in the same selection screen'.
    You just issue this message in AT SELECTION-SCREEN event as:
    MESSAGE e025(ZSHANTHI) WITH 'requirement'.
    The error message will display on the status bar and when user hits the message X button, the long text with your story will appear in a modal box and still selection screen stays.
    If your client is adamant in having only 'Tick' mark (this sucks me), you can add DISPLAY LIKE 'S' addition to the above message statement. But this addition works only 4.7 upwards.
    If you want to  issue this error message in list processing events like START-OF-SELECTION, then, you need to issue the following statements:
    MESSAGE s025(ZSHANTHI) WITH 'still weird requirement'.
    Note the message type 'S' above.
    LEAVE LIST-PROCESSING.
    Hope this helps.
    Regards
    Suresh Radhakrishnan

  • System error in program CL_RSMD_RS_SPECIAL

    I have a query built on a Infoset, and the problem comes with 0FISCPER variable, when we try to do a input help (F4) in Bex. this happens only when I use fiscper on queries bulit on INFOSETS, and it works perfectly alright with all other cubes. We are on SP13. So do anyone know how to fix this issue, or a single OSS that can fix this issue.
    System error in program CL_RSMD_RS_SPECIAL and form
    IF_RSMD_RS~READ_META_DATA-02 (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.
    and in portal, it gets to the point of variable screen and then throws a error msg.
    ABEND RSBOLAP (000): Program error in class SAPMSSY1 method : UNCAUGHT_EXCEPTION
    MSGV1: SAPMSSY1
    MSGV3: UNCAUGHT_EXCEPTION

    I was a lil late on this time
    However;i found a note below which exactly matches your infoset issue and 0fiscper,but i believe that SP-14 did the trick.
    any ways good luck
    Note 1058906 - GET_DIME_VALUES-02 in CL_RSMD_RS_SPECIAL
    Hope it Helps
    Chetan
    @CP..

  • System error in program Constiuent Assembly - internal error

    Hi,
    This is regarding the query execution, we have three variables in the selection screen, We have one variable for hierarchy selection from Constiuent Assembly.
    I am facing an issue while executing the query in BEX analyzer.Once i fill all the selection criteria in variable screen, I am getting an error saying that "System error in program Constiuent Assembly "
    Can anyone please suggest what could be the reason for this error?
    Please find below the error details.
    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.

    Hi,
    May be the selection variable is not correct or corrupt.
    Use any other slection variable for hierarchy object.
    I hope it will help.
    Thanks,
    S

  • System error in program SAPLRRI2 and form BEST_WGR_02-01-

    Hi Friends,
    When I am trying to execute a query i get the error message below.
    System error in program SAPLRRI2 and form BEST_WGR_02-01- (see long text)
    Error when generating dataProvider
    The Same query can be executed after restarting BI server.( Hope No one recommends restarting BI server always).
    I am using SAP BI Patch level 3.
    Internet explorer 7
    Gui 6.4
    At the same time it is unable to disply variable screen in BEx Analyser with IE 7(Variable entry Screen appeares but No Input boxes are seen). Its Working fine with IE 6.
    Any Solution For This.
    Many Thanks,
    Anand

    Hi
    IE 7 is not so compitable with BEx. It always has the Popups problem..
    See the Note :919196 and  Note 1159538 - Issues in Internet Explorer   Note 950975 - SAP GUI for Windows: Support for IE7 (Internet Explorer 7)
    Hope it helps

  • System Error in program CL_RSR executing queries

    Hi,
    We have several queries created from multiprovider X and these queries are included in a workbook. Multiprovider is active and fine (I have used the programs RSCOMPCONS and RSR_MULTIPROV_CHECK return status OK).
    When I open the workbook the followings error messages are showed (before selection screen):
    - System error in class SAPMSSSY1 method: UNCAUGHT_EXCEPTION
    - System error in program CL_RSR and FORM GET_INITIAL_CHAVL_OFF-02-
    We are looking sap notes (we are in the new version 7.30, Support package 5) in order to solve this error but We don't find the solution.
    Please, could you help me?
    Thanks!

    Might require to collect the workbooks, queries along with the MP & perform a transport. Please collect the roles also. This must solve.

  • System Error in program SAPLRRS2 and form GET_SID-1 -(see long text)

    Hello all,
    One of the users is trying to run a report in Production using BEx analyser and gets the following error.
    BI Server error:
    Program error in class SAPMSSY1 method: UNCAUGHT_EXCEPTION
    System Error in program SAPLRRS2 and form GET_SID-1 -(see long text)
    I have already run the SAP Note 1237190 but there is no use as the error comes up again.
    Could any one please help to resolve this issue.
    Thanks
    Phani.

    Hi Dipika
    Thanks for the reply.
    But I dont think that note is applicable for this error as this error pops as soon as the selection screen is past and before the report is displayed.
    This is not happening with all the users though.
    Its a random problem only.
    Thanks
    Phani.

  • System error in program CL_RSR_WWW_PAGE

    Hi BW gurus!
    when i try to export to excel from my report "Logistic dahsboard ", i have this error message :
    "System error in program CL_RSR_WWW_PAGE and form 01EXPORT_DATA:01      "
    SAP doesn't give any notes.
    Can anyone help me?
    Dev

    Solved.
    Go to SE80 (in BW system) :
    --> Click on MIME Repository
    --> path SAP --> BW --> Customer --> Javascript
    one of the javascript file contains all the javascript functions (Export to excel, bookmark...) you have in the web screen of the report used in your reports
    --> Search keyword "goto_url"
    --> normally you reach the javascript function
    --> now check the parameters in case of "(value = 'EXPORT')", especially the name of the dataprovider must map with which one defined in the WAD.
    hope it will be helpful for anyone
    Dev

  • System error in program SAPLRRS2 and form SELOPT_ASSIGN-01- (SAP BW 3.5)

    Hi,
    The following error occured when executed a query :
    "System error in program SAPLRRS2 and form SELOPT_ASSIGN-01-"
    I have read OSS note 907533 but from what I see in this note, I conclude the repair instruction
    only for SAP BI 7.0 so this note not for SAP BW 3.5.
    I have use button "Check query" and everthing is fine.
    Is there someone who can solve my problem?Thank you
    Regards,
    Satria

    This question is interesting. 
    One of my users got the same message today.  Wednesday, she ran some queries that had 3 variables on them.  She had no problems.  Yesterday, she tried to run the same queries, and one of the three variables did not show up on the variable screen.  The characteristic in question is not authorization relevent.  Others had no problems with these queries. 
    Today, I created a new query using the characteristic with no variables.  It ran fine for her.  I added the variable and she got the error message.
    So, I would really appreciate an answer to this thread!
    Ginny

Maybe you are looking for

  • Display issue for xRPM CAPACITY MANAGEMENT  report on EP

    Experts, I am using xRPM 4.2 version. My BW is on release 700 with patch level 15 & EP on 7.0 I am tring to view the various reports uder capacity management on EP. These reports are viewable correctly in BIW system but not able to display the same o

  • IPhone 2.2.1 software on my iPod touch isn't recognized by my car stereo...

    Hey, First ever post in an online discussion. Hope I'm doin' this right... I'm trying to restore the factory software to my first generation 32G ipod touch from my MacBook because my car stereo does not recognize the new software. (my MacBook doesn't

  • Action Script to add a parent node value to the top node

    I need to add a new parent node value to a hierarchy for the top node.  The action script parameters to add a node is "Add|Version|Hierarchy|Node|Parent Node|Leaf property".  I am at a loss on what to do for the top node since there is no Parent Node

  • Explain this to me plz

    Hey guys i was here last night with a problem on my first app...i got it working and have started on another...i am using a book to help me, but i dont understand it and i was wondering if anyone could explain to me exactly what this code does....Ill

  • Adobe CS 3 to 5.5 Upgrade OSX

    Hi, I have a question regarding an upgrade I have performed on OSX Snow Leopard. Situation : An iMac with OSX Tiger and Adobe CS 3 installed.  Needs to be upgraded to Adobe CS 5.5 Design Standard Actions performed: 1) Upgraded OSX to Snow Leopard 2)