Syntax error in SAPLSCSM_BI_DATALOAD program

Hi
Even after applying snote 1610374 we got syntax error in Solution manager 7.1.
Does it require to correct program with an abaper?  Please help..
Regards,
Cinu

Below note may help
:  2004350 - Syntax error in program SAPLSCSM_BI_DATALOAD
Resolution
Check include LSCSM_BI_DATALOADTOP in SE38 or perform the following step:
- Tcode SE37
- CCMSBI_AGGR_DSO2CUBE
- Line 412, iv_object_name = ods_curr2
- Double click the name "ods_curr2"
Check if this report is in active status. If not, please activate it.
If it is already active, please check version management to see if there is the latest modified version and retrieve the new version.
Hope this will help you .

Similar Messages

  • Syntax Error occured in Program  in include " CNTN01

    Hi,
    We are working on SAP 4.6C to ECC 6.0 Migration. While testing One Transaction, I am getting following error:
    The current ABAP program "CL_GOS_TOOLBOX_MODEL==========CP" had to be
    terminated because it has come across a statement that unfortunately cannot be executed.
    The following syntax error occurred in program
    "Z3I_CL_BASCULER_SCS_GOS=======CP " in include "<CNTN01> " in
    line 13:
    "Within classes and interfaces, you can only use "TYPE" to refer to ABA"
    "P Dictionary types, not "LIKE" or "STRUCTURE"."
    The include has been created and last changed by:
    Created by: "SAP "
    Last changed by: "SAP "
    Error in the ABAP Application Program
    This Error is coming while executing transaction in ECC 6.0 however in R/3 4.6C it is working fine.
    Pls Advice what should be done to resolve this issue. This issue is coing in alot of transactions.
    I will appreciate if anyone of you can guide me regarding same.
    regards
    Sandeep

    Hi,
    I was trying hand on one of my Z class which contain  include <CNTN01>. in its Local Types.
    I commented the existing include statement and added new statement as
    INCLUDE CNTN01_OO.
    After saving now when i try to activate the Z Class, it is giving me following error:
    INCLUDE CNTN01_OO
    You can only define classes and interfaces at the highest level of CLASS-POOL.
    CLASS Z5C_CL_MESSAGE, Internal classes in a class include "CNTN01_OO" does not start with the prefix (Z5C_CL_MESSAGE=======)of the current class pool.
    pls advice what i should do correct this issue.
    Sandeep

  • Hierarchy load - Error RSAR 683 Syntax error in generated program, row 0

    Hi guys,
    When I load the hierarchy on ZMATERIAL (load from 0MATERIAL hierarchy - source system BW), I have this error message : RSAR 683 Syntax error in generated program, row 0.
    I have found several SAP notes, especially [Sap Note 944842|https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bw_whm/~form/handler], but the implementation on our system does not change anything.
    We are working on BW3.5 SP12.
    Can anyone could tell me what to do ?
    Will this issue be solved once we upgrade until SP18 as it is mentionned in the SAPNote ?
    Thanks,
    Alexandra
    Edited by: Alexandra Guillaux on Apr 1, 2009 4:36 PM

    Hello Alex,
    after implementing the corrrection part of note 944842 via SNOTE, plaese also:
    1. replicate datasource
    2. activate transfer structure (report RS_TRANSTRU_ACTIVATE_ALL)
    3. activate infoobject   (make dummy change to description
    of infoobject etc, save and activate it, remove change and save and
    activate it again).
    Hope it could resolve the incident.
    Thank you & Best regards,
    Vince

  • Syntax Error in generated program.

    Hi Experts -
    I saw a similar thread regarding the issue I'm having but I thought I'd open another thread.
    0CMMT_ITEM_FMCI_PU_HIER Syntax Error for Generated Program
    I'm doing an extraction for 0CRM_ORGUNIT_HR01_HIER in RSA3 of CRM.
    I get an error message:
    Message RJ028 : Error 6 in function module RSS_PROGRAM_GENERATE
    There is a syntax error in the code.
    How do you solve this issue?
    We applied OSS note 822323 but still get the same error. The code still has the syntax error.
    Any one saw this or have any solutions? Please let me know. Thanks a lot in advance!

    Hi,
    Use the program RSA1HCAT in SE38 to check your hierarchy.
    Transaction RSA3 was not developed for checking hierarchy DataSources.
    Rather, it is only for transaction and attribute/text datasources.  If
    you want to check the extraction of hierarchy datasources in the R/3
    system, you should use the report RSA1HCAT.  In this report, enter the
    name of the hierarchy datasource in the "DataSource with HierarchyType"
    field.
    For this problem look at the note: 632920.
    Regards,
    Srikanth.

  • Syntax error in standard program after upgrade

    Hi,
    After upgrade from 7.0 to 7.3, we are facing a syntax error in standard program that is used in one of our process
    The error says:
    The field "G_REQUIDPARENT" is unknown, but there is a field with the s"
    imilar name "G_REQUID_LAST". "G_REQUID_LAST"."
    The system cannot find this object inside include LRSBM_REQUEST_GUIP04, that belongs to program SAPLRSBM_REQUEST_GUI
    We assume that this is associated with the upgrade but we cannot find any solution in the web. Besides, this is a standard program so we cannot perform any change directly. We look for SAP Notes to apply but we didn't find nothing worthwhile
    Basically, we are receiving a dump with the error message posted above and we found the syntax error, but the thing is that we don't know how to fix it, due to the fact that is a standard program and we cannot change it
    I know that SAP could remove some object reference during the upgrade, but there should be an anticipated plan to fix this kind of errors, right?
    Can you shed some light on this, please ?
    Thanks a lot
    Ale

    Hi Ale,
    If you make sure there are no customization around the object and SGEN already run, I think you can just open a OSS message to SAP to looking for a fix.
    Regards
    Bill

  • Syntax error in the program SAPLSYMB

    Hi
    I have installed ECC6 on windows 2003 server  sqlserver 2005 as database. We are getting error at the time applying basis patch. The patch process is stopped at import_proper stage.
    When i try to execute any transaction , the error is "syntax error in the program SAPLSYMB". I have cleard the transaction log, still  the errro is same.
    When I try to relogin the error is same, I am unable to execute any transaction.
    Please do the needful
    Regards
    Prasanna.B.S

    Hellow,
    I have the same error, and I executed this command for 12 hours
    tp r3i SAPKB70017 ITP pf=/usr/sap/trans/bin/TP_DOMAIN_ITP.PFL tag=spam -Dclientcascade=yes -Drepeatonerror=8
    the message in cmd is
    earth\sapmnt\trans\tmp\SLOG0914.ITP.LOC is already in use (14474), I'm waiting
    2 sec (20090401065221). My name: pid 4188 on earth (dministrator)
    But this file (SLOG0914.ITP.LOC ) is in 0 kb, is this normally ?
    Please Help me
    Regards
    Graciela

  • SYNTAX ERROR IN SAPMSSYD PROGRAM

    HI ,
               We included the code in Program 'SAPMSSYD' for our internal
    validation. This validation requires to fetch the data from the ztables.
    we created ZTABLE and included custom code in SAPMSSYD in DEV server
    and tested sucessfully.
    We tried to move the Transport request from DEV to QAS. We had separate
    transport request for Ztable Creation and for our custom code
    validation. Instead of moving the Ztable request first, we have moved
    the customer code request and Due to this System throws an syntax error
    when we get into login screen of QAS server. Now we are not able to
    login to QAS and our testing process was completely stopped in QAS
    server. Pls advice us how to revoke transport or to solve this issue.
    Best Regards
    Thiru

    First, if you change such a kernel-like program, I advise you to request SAP consulting, that's really too much dangerous!
    Secondly, if you want to revert back, you have to do it on the DEV system (version management), then transport again.

  • Syntax error in the program in the "SAP LZTEST"

    When executing Transaction Code VF01/VF02/VF03, it is not possible to create a billing document. it is showing the error like the above.
    "The data object "ZASD_MAINT" does not have a component called "TIME_Z0" "NE".
    Can you please help me in this issue ASAP.

    Hello Eechaneri,
    May some user exit or custom code is involved in here. Please get it checked by you developers. They would be able to help you out using debugging. ABAP dump analysis also wont be very helpful in this case unless you involve your developers here.
    Regards.
    Ruchit.

  • SYNTAX_ERROR unable to log in to SAP system Syntax error in program "SAPMSE

    hi SAP Experts,
    I have applied Basis patch 12 and I scheduled the background.  Backgroud job was terminated. System became slow. Then I stopped the server and restarted.  Now, I am unable to log in to SAP GUI by entering Username and Password and getting syntax error.
    Syntax error in program "SAPMSEM1".
    What happened?
    Error in the ABAP Application Program
    The current ABAP program '????????????????????????????"
    terminated because it has
    come across a statement that unfortunately cannot be executed.
    The following syntax error occured in program "SAPMSEM1" in include
    "CL_SALV_FORM_ELEMET==========CU" in
    line 13:
    "the type "IF_SALV_FORM_CONFIG" is unknown."
    The include has been created and last changed by:
    Created by: "SAP "
    Last Changed by: "SAP "
    I am unable to access any transction code.
    Please help me..
    Thanks in advance...
    Raju

    hi,
    Thanks for your response.
    i haven't take any back up.  can u pls tell me step by step procedure to implement the SP with TP.
    your answer will be helpful..
    Regards
    Raju

  • InfoSet Query: Syntax Error while generating the program.

    Dear All,
    I have a Query in CRM system which contains an Infoset based on LDB.
    The InfoSet Query throws up a Syntax error while generating the program.
    So, we are not able to change the Infoset using the Infoset Query through SQ01.
    The error is as follows:-
    Syntax error in program "AQZZ==/SAPQUERY/CRM_ACTMON1 ".
    Error in the ABAP Application Program
    The current ABAP program "CL_QUERY_OUTPUT_DEFINITION====CP" had to be
    terminated because it has
    come across a statement that unfortunately cannot be executed.
    The following syntax error occurred in program "AQZZ==/SAPQUERY/CRM_ACTMON1 "
    in include "AQZZ==/SAPQUERY/CRM_ACTMON1 " in
    line 28:
    ""CRMT_REPORT_LOCATORLIST" must be a flat structure. You cannot use int"
    "ernal tables, strings, references, or structures as components. -"
    Please help me arrive at an solution, so that we are able to change the Infoset through the InfoSet Query.
    Awaiting your reply as soon as possible.
    Thanks and Regards,
    Pankaj.

    There is an error in your query, specifically in the definition of CRMT_REPORT_LOCATORLIST. In the short dump (transaction ST22) you will see more details and the exact location of an error if you just scroll down.
    I can't tell more because this problem is specific to your system, to which I have no access. Read the whole dump and look at all the objects mentioned there.

  • Syntax Error while running "RFBILA00" program

    Hello,
    I am encountering some issues while trying to run reports that use table "FAGLFREESEL". The below error is for report "RFBILA00":
    Short Text
        Syntax error in program "RFBILA00 ".
    What happened?
        Error in the ABAP Application Program
        The current ABAP program "SAPLALDB" had to be terminated because it has
        come across a statement that unfortunately cannot be executed.
        The following syntax error occurred in program "RFBILA00 " in include "RFBILA00
         " in
        line 46:
        ""FAGLFREESEL" muß eine flache Struktur sein. Interne Tabellen, Referen"
        "zen, Strings und Strukturen sind als Komponenten verboten."
        The include has been created and last changed by:
        Created by: "SAP "
        Last changed by: "SAP "
        Error in the ABAP Application Program
        The current ABAP program "SAPLALDB" had to be terminated because it has
        come across a statement that unfortunately cannot be executed.
    Any sugestions on how to fix this would be greatly appreaciated.
    Thank you!

    Hello Constantin,
    As the message suggests, FAGLFREESEL should be a Structure. CHeck in your system whether it has been created as a sturcture.
    Have you checked SAP Service marketplace for the SAP Note. There are couple of SAP notes available for 2013 for few countries. Check whether anything applicable to your country.
    If not, raise a OSS note with SAP.
    BR
    Amitash

  • 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

  • Syntax error in program "CL_HTTP_SERVER=CP " after EHP4 Upgrade

    Hi All,
    Iam getting ABAP dumps after upgrading my system to EHP4  Windows ABAP+JAVA stack,
    Syntax error in program "CL_HTTP_SERVER================CP ".
    Error in the ABAP Application Program
    The current ABAP program "SAPLHTTP_RUNTIME" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
    The following syntax error occurred in program
    "CL_HTTP_SERVER================CP " in include
    "CL_HTTP_SERVER================CM00F " in
    line 15:
    "Field "C_IS_SHOW_SERVER_HEADER" is unknown. It is neither in one of th"
    "e specified tables nor defined by a "DATA" statement. ."
    The include has been created and last changed by:
    Created by: "SAP "
    Last changed by: "SAP "
    Error in the ABAP Application Program
    The current ABAP program "SAPLHTTP_RUNTIME" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
    What can you do?
        Please eliminate the error by performing a syntax check
        (or an extended program check) on the program "CL_HTTP_SERVER================CP
        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
         CL_HTTP_SERVER================CP :
        "Field "C_IS_SHOW_SERVER_HEADER" is unknown. It is neither in one of th"
        "e specified tables nor defined by a "DATA" statement. ."
    Regards
    Uday

    Hi,
    SPDD should be performed before ACT_UPG phase when system prompts you for SPDD. But now you cannot do SPDD phase. All the objects that came during SPDD phase has been resetted to new objects which SAP has delivered with EHP4.
    SPAU you can perform after upgrade and that too with in 14 days when upgrade finished without object key.
    I should suggest you to read upgrade guide on http://service.sap.com/erp-ehp.
    Thanks
    Sunny

  • Short Dump-Syntax error program"CL_RSD_MULTIPROV==CP" after EHP1SP5 upgrade

    Hi,
         MultiProvider Activation/Display data is resulting into short dump with following text
    Error in the ABAP Application Program
    The current ABAP program "CL_RSD_MULTIPROV_CHECK========CP" had to be
    terminated because it has
    come across a statement that unfortunately cannot be executed.
    The following syntax error occurred in program
    "CL_RSD_MULTIPROV==============CP " in include
    "CL_RSD_MULTIPROV==============CM010 " in
    line 1:
    "Method "CHECK_LINITFL" is not declared or inherited in class "CL_RSD_M"
    "ULTIPROV". -"
    The include has been created and last changed by:
    Created by: "SAP "
    Last changed by: "SAP "
    Error in the ABAP Application Program
    The current ABAP program "CL_RSD_MULTIPROV_CHECK========CP" had to be
    terminated because it has
    come across a statement that unfortunately cannot be executed.
              We have recently upgraded to EHP1SP5. We noticed this issue just after that.
    Regards,
    PD

    Hi,
    Please check the note 1461401.
    1461401 - System error in the program CL_RSD_MULTIPROV_CHECK
    This note should help you.
    Regards,
    Rafael

  • IW32/ IW33 - Syntax error in program "SAPLIWO_UI_DL "

    Dear All,
    I am facing a strange problem, while displaying a service order (IW33).
    Our system component systems are SAP ERP 6.0 ( EHP 5) and NetWeaver 7.0 (EHP 2).
    Whenever I try to display a service order, system gives below dump error.
    I have checked the source cord,
    and I found  the function, "iwo_ui_dl_operation_def_create", that does not define the field, "GV_DEF_CUST."
    I have searched the threads, but I haven't found any extensions or solutions.
    Would request you to please help.
    What happened?
        Error in the ABAP Application Program
        The current ABAP program "CL_IM_IWO_UI_FLEXIBLEORDER====CP" had to
         terminated because it has
        come across a statement that unfortunately cannot be executed.
        The following syntax error occurred in program "SAPLIWO_UI_DL " in
         "LIWO_UI_DLU22 " in
        line 155:
        "Field "GV_DEF_CUST" is unknown. It is neither in one of the specif
        "tables nor defined by a "DATA" statement. ."
        The include has been created and last changed by:
        Created by: "SAP "
        Last changed by: "SAP "
        Error in the ABAP Application Program
        The current ABAP program "CL_IM_IWO_UI_FLEXIBLEORDER====CP" had to
         terminated because it has
        come across a statement that unfortunately cannot be executed.
    Error analysis
        The following syntax error was found in the program SAP
        "Field "GV_DEF_CUST" is unknown. It is neither in one o
        "tables nor defined by a "DATA" statement. ."   
    Trigger Location of Runtime Error
        Program                                 CL_IM_IWO_UI_FLEXIBLEORDER====CP
        Include                                 CL_IM_IWO_UI_FLEXIBLEORDER====CM001
        Row                                     3
        Module type                             (METHOD)
        Module Name                             IF_EX_IWO_UI_USEFLEX~EXEC_NEW
    Thanks & Regards,
    Jinno

    FYI.
    Solved by importing component EA-APPL (Version: SAPK-60501INEAAPPL).
    Regards,
    Jinno

Maybe you are looking for