TX BDLS - Syntax error in program SBDLS21020100127145818 line SELECT SINGLE

Hi All,
I am in the process of configuring a QAS system taken from a copy of th production system, I am going into TX BDLS and getting the following error message Syntax error in program SBDLS21020100127145818 line SELECT SINGLE AWSYS FROM DFKKKO has anyone got any ideas about this issue?
Thanks
Jay

Force manual activation in se11 this tables: (SE11 -> display -> menu 'table' -> actívate)
DFKKKO
DFKKCOLFILE_P_W
DFKKMKO
DFKKREP06
DFKKREP06_S
DFKKREP07
DFKKREV06
DFKKREV07
Try again the BDLS.
Regards.

Similar Messages

  • Syntax Error in program "/BDL/SAPLBDL11"

    Hi,
    I have installed ST-PI and ST-A/PI Add-ons with latest Support Patches in our BI7.01 environment. after that i have configured SDCCN successfully in Development environment but when i am trying to configure SDCCN in Quality environment, i am getting Syntax_Error for program /BDL/SAPLBDL11. Due to this error i am not able to create SDCC_OSS RFC also not able to activate batch jobs /BDL/TASK_PROCESSOR.
    Following is the brief detail of error.
    ===================================================================================
                                                                        SYNTAX_ERROR
    Short text
        Syntax error in program "/1BCDWBEN/SAPL/BDL/EN0000 ".
    What happened?
        Error in the ABAP Application Program
        The current ABAP program "/BDL/SAPLBDL11" had to be terminated because it has
        come across a statement that unfortunately cannot be executed.
        The following syntax error occurred in program "/1BCDWBEN/SAPL/BDL/EN0000 " in
         include "/1BCDWBEN/L/BDL/EN0000U01 " in
        line 41:
        "Field "ALL_" is unknown. It is neither in one of the specified tables "
        "nor defined by a "DATA" statement. "DATA" statement."
        The include has been created and last changed by:
        Created by: "DDIC "
        Last changed by: "DDIC "
        Error in the ABAP Application Program
        The current ABAP program "/BDL/SAPLBDL11" had to be terminated because it has
        come across a statement that unfortunately cannot be executed.
    ========================================================================================
    Thanking you
    Regards
    Pranav

    Dear Pranav
    I  think you have done the upgradation to EHP3 ,  In order to Fix this issue would you please try to  activated the lock object /ISDFPS/EALESYS   ,  ENQUEUE_/ISDFPS/EALESYS and DEQUEUE_/ISDFPS/EALESYS   in transaction SE11
    I am sure this will fix that issue.
    Best Regards
    Jai Wardhan

  • Syntax error in program RK2CIDEA, include RK2CIDEA, line 5614

    Dear All
    Good Evening!
    I'm trrying to generate the operating concern in ECC5 Ides, but system is displaying following error.
    <i>"<b>Program RK2CIDEA contains a syntax error in include RK2CIDEA. The error occurred in line                                                5614. Thefollowing message describes the error."</b></i>
    I also implement  the solution of  Note 778704 - Syntax error in generated report RK2CXXXX.
    but still system displaying the same error.
    operating conceren " IDEA" is Red ( No Active)
    Please guide me!
    Thanks

    Good Evening!
    Thanks for reply!
    I implement the solution of "778704" , but function module that is given in this solution giving me return code "8" ( export Prameter subrc = 8)
    also I implement the solution of Note 143557 - Line item list: Integration FI/CO document. but still having the same problem.
    <b>Syntax error in program RK2CIDEA  " Field "CE0S001" is unknown"</b>
    Any advise more......
    Thanks

  • 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

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

  • Syntax error in program "SAPLOCS_LOG ". for SPAM

    Hi  Team ,
    I have updated SPAM from 730 45 to 730 51 after that i am trying to update SPS from spam , it is throwing the  below error .
    Category          
    ABAP Programming Error
    Runtime Errors    
    SYNTAX_ERROR
    ABAP Program      
    SAPLOCS_LOG
    Application Component  BC-UPG-OCS
    Date and Time     
    07.04.2014 18:21:55
    Short text
        Syntax error in program "SAPLOCS_LOG ".
    What happened?
        Error in the ABAP application program.
        The current ABAP program "SAPLOCS_UI" had to be interrupted because it contains
        a statement that cannot be executed.
        In the include "LOCS_LOGU15 " in the line 97 of program "SAPLOCS_LOG " the
         following syntax
        errors occur:
        "The data object "LS_PATHISTQ" does not have a component called "PRE_VR"
        "S"."
        Author and last person to change the include are:
        Author "SAP "
        Last changer "SAP "
    Error analysis
        The following syntax error was found in the program SAPLOCS_LOG :
        "The data object "LS_PATHISTQ" does not have a component called "PRE_VR"
        "S"."
    Help is much appreciated .
    Thanks,
    Pradeep.

    Hi ,
    After full restart of the system also there is no use , even i tried to upgrade to 52 .
    It is throwing dump .
    Category          
    ABAP Programming Error
    Runtime Errors    
    SYNTAX_ERROR
    ABAP Program      
    SAPLOCS_LOG
    Application Component  BC-UPG-OCS
    Date and Time     
    07.04.2014 23:32:43
    Short text
    Syntax error in program "SAPLOCS_LOG ".
    What happened?
    Error in the ABAP application program.
    The current ABAP program "SAPLOCS_UI" had to be interrupted because it contains
    a statement that cannot be executed.
    In the include "LOCS_LOGU15 " in the line 97 of program "SAPLOCS_LOG " the
    following syntax
    errors occur:
    "The data object "LS_PATHISTQ" does not have a component called "PRE_VR"
    "S"."
    Author and last person to change the include are:
    Author "SAP "
    Last changer "SAP "
    Help is really much appreciated ..
    Thanks,
    Pradeep.

  • 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

  • Syntax error in program "SAPLBBP_BAPI_PO " while PO transfer

    Hi:
    I am getting below dump in ECC when I order PO in SRM. PO is created in SRM successfully, but err out.  I am on SRM 701 with PPS and ECC 6.  I am guessing some switch needs to be activated but not sure.  Any help is appreciated.
    Syntax error in program "SAPLBBP_BAPI_PO "
    The current ABAP program "SAPMSSY1" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
    The following syntax error occurred in program "SAPLBBP_BAPI_PO " in include
    "LBBP_BAPI_POU04 " in
    line 1:
    "Function "BBP_GET_SWITCH_STATE_RFC" not found in Function Library."

    Hello Vijay,
    Could you please check:
    - in R/3 if Business Function LOG_MM_MAA_1 is switched on in SWF5 transaction.
    - in SRM if BBP_FUNCTION_MAP table is populated for adaptater BBP_GET_SWITCH_STATE_RFC.
    Regards.
    Laurent.

  • Syntax error in program "SAPDBZMPQ_PGQ "

    Hi All,
    while executing tcode zppwagri its going to dump.I have gone through SDN but there is no solution.As this is related to standard Include issue.Can anyone provide me the SAPNOTE or solution for the issue.
    We are upgrade our system from 4.7 to ECC6 EHP5 the structure qavo_tab not available in old version
    but its there in newer system.how to remove above structure or avoid the syntax error as well as dump.
    Dump details:
    Short text:
    Syntax error in program "SAPDBZMPQ_PGQ ".
    What happened?
    Error in the ABAP Application Program
    The current ABAP program "ZMPQ_RQEEAL10" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
    The following syntax error occurred in program "SAPDBZMPQ_PGQ " in include
    "DBPGQF001 " in line 256:
    "Field "QAVO_TAB" is unknown. It is neither in one of the 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 "ZMPQ_RQEEAL10" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
    Error analysis:
    The following syntax error was found in the program SAPDBZMPQ_PGQ :
    "Field "QAVO_TAB" is unknown. It is neither in one of the specified tab"
    "les nor defined by a "DATA" statement."
    In standard Include program DBPGQTOP i have structure.
    Tabelle der Vorgangsverwendungsentscheide
    DATA:   BEGIN OF qavo_tab OCCURS 5.
            INCLUDE STRUCTURE qavo.
    DATA:   END OF qavo_tab.
    Thanks
    Siri

    Looks like the top include DBPGQTOP is not linked with the main program anymore after upgrade. In fact, we faced a similar 'missing include/syntax error' issue after our EHP5 upgrade. But that was on a function module/function group. We corrected it by running SE37->Utilities->Repair function group.
    In the same way, try running 'Rebuild object list' from SE80 for your program.
    Regards,
    Gokul

  • Syntax error in program "HINCALC0 ".

    Hi,
    After applying the Snote -1474958 along with the Prerequisties (Snote -1455387,1425161,1452218,1456076,1459813,1459875,1475735), when we exec the TC PC00_M40_CALC we are getting the abap dump.
    Runtime Errors         SYNTAX_ERROR
    Date and Time          23.08.2010 13:06:31
    ShrtText
    Syntax error in program "HINCALC0 ".
    What happened?
    Error in ABAP application program.
    The current ABAP program "????????????????????????????????????????" 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 "HINCALC0 ", the following syntax error occurred
    in the Include "PCSECIN0 " in line 155:
    "Field "80CCF_DEDMT" is unknown. It is neither in one of the specified "
    "tables nor defined by a "DATA" statement. "DATA" statement."
    Author and last person to change the Include are:
    Author "SAP "
    Last changed by "BASIS_USER "
    Error analysis
    In program "HINCALC0 ", the following syntax error occurred:
    "Field "80CCF_DEDMT" is unknown. It is neither in one of the specified "
    "tables nor defined by a "DATA" statement. "DATA" statement."
    Trigger Location of Runtime Error
    Program                                 ????????????????????????????????????????

    Hi Ramana,
    While applying the snote we are getting error below
    Yellow light for the status Object PCFDCIN0- Corrections incompletly copied:see change display.
    Green Light for the Status Object PSDECIN0 - Changes Can be copied
    Green Light for the Status Object PSDECIN1 - Changes Can be copied
    Regards,
    KARAN.

  • Syntax error in program "SAPLGLIN "

    Hi,
    After creating new client and made a copy from an existant one, when we try to create an accounting document from any module (SD,Fi,MM)this error occurs :
    Error in the ABAP Application Program
    Syntax error in program "SAPLGLIN "
    The current ABAP program "SAPLRWCL" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
    The following syntax error occurred in program "SAPLGLIN " in include "LGL
      " in
    line 1742:
    "The field "TAB_FBICRC001P" is unknown, but there is a field with the s"
    "imilar name "TAB_FBICRC001A". ."
    thanks in advance

    That note also says below;
    If problems are not still solved after successfully running the program RGZZGLUX, contact SAP development.
    So it looks you need to contact SAP service through marketplace.
    Regards,

  • FRF-00025  Unable to call function. Error message: Syntax error in program

    hi,
    when we try to import the export file,we are getting the following error in the 24th phase
    i.e., check DDIC Password.
    The Error is
    INFO       2007-10-29 15:53:20 [iaxxrfcimp.cpp:1017]
               CAbRfcImpl::callLibraryFunction
    Generating interface for remote function.
    TRACE      [iaxxrfcimp.cpp:1056]
               CAbRfcImpl::performFunctionCall
    Calling function module: INST_RFC_GET_INTERFACE
    WARNING[E] 2007-10-29 15:53:21 [iaxxrfcimp.cpp:1089]
               CAbRfcImpl::performFunctionCall
    FRF-00025  Unable to call function. Error message: Syntax error in program SAPLSUNI                                . .
    TRACE      [iaxxrfcimp.cpp:1090]
               CAbRfcImpl::performFunctionCall
    RFC failure or system exception raised
    TRACE      [iaxxrfcimp.cpp:1091]
               CAbRfcImpl::performFunctionCall
    Syntax error in program SAPLSUNI                                .
    TRACE      [iaxxbjsmod.cpp:657]
               CJSlibModule::showOkCancelBox_impl()
    <html>Test logon to SAP System I50 failed.<p>Make sure that the system is started, that the user DDIC exists and that the password of user DDIC is correct.</html>
    TRACE      [iaxxgenimp.cpp:1093]
               showDialog()
    waiting for an answer from gui
    What Could be the solution for this.
    waiting for ur reply
    SS

    Hi Friend,
    Please check whether or not there is view missing error recorded in dev_w0 trace file.
    if there is , you can try to follow this procedure in order to manually
    import the missing view definitions.
    All steps must be carried out with the <sid>adm user of the target
    system and from the install-directory:
    1. In the install-directory
    <sapinst_instdir>\...COPY\IMPORTT\SYSTEM\ABAP\ORA\UC\DB
    create a file SAPVIEW.cmd with the following content:
    tsk: "<sapinst_instdir>\...\COPY\IMPORT\SYSTEM\ABAP\ORA\UC\DB\SAPVIEW.TSK"
    icf: "
    <YOUR_EXPORT_DIRECTORY>\export\DATA\SAPVIEW.STR"
    dcf: "<sapinst_instdir>\...\COPY\IMPORT\SYSTEM\ABAP\ORA\UC\DB\DDLORA.TPL"
    dat: null
    dir: null
    ext: null
    Please make sure that all paths are written correctly (in one line) and
    the refered files are existant and readable. One exception:
    The SAPVIEW.TSK file is created with step 2.:
    2. Run from the command-line:
    R3load -ctf I
    <YOUR_EXPORT_DIRECTORY>\export\DATA\SAPVIEW.STR <sapinst_instdir>\...\COPY\IMPORT\SYSTEM\ABAP\ORA\UC\DB\DDLORA.TPL SAPVIEW.TSK ORA -l SAPVIEW.log
    If there's a problem reading the 'SAPVIEW.STR' file, copy the
    file to the install directory and adapt the path accordingly.
    3. Run the view import by:
    R3load.exe -i SAPVIEW.cmd -dbcodepage <YOUR_CODE_PAGE> -l SAPVIEW.log
    -stop_on_error
    4. Check both the SAPVIEW.log and the SAPVIEW.TSK file whether all views
    have been created successfully.
    If 4. is okay, restart the central instance and check whether you are
    able to log on now. If yes, continue 'sapinst' by the option 'retry' or
    'continue old installation'.
    I Hope It can be helpful.
    With Best Regards
    Julia

  • St22 dump : Syntax error in program "SAPLCRM_KNOWLEDGE ".

    Hello experts,
    When i click on Define Template for folder in SPRO ( spro -> customer relation relationship management>
    basic function --> content management ---> define template for folder) it goes to dump.
    Runtime Errors         SYNTAX_ERROR
    Short text :Syntax error in program "SAPLCRM_KNOWLEDGE ".
    What happened?
         Error in the ABAP Application Program
         The current ABAP program "SAPLSVIM" had to be terminated because it has
         come across a statement that unfortunately cannot be executed.
         The following syntax error occurred in program "SAPLCRM_KNOWLEDGE " in include
          "LCRM_KNOWLEDGEF03 " in
         line 71:
         ""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 "
         Error in the ABAP Application Program
         The current ABAP program "SAPLSVIM" had to be terminated because it has
         come across a statement that unfortunately cannot be executed.
    Error analysis
        The following syntax error was found in the program SAPLCRM_KNOWLEDGE :
        ""ICFALIAS" must be a flat structure. You cannot use internal tables, s"
        "trings, references, or structures as components. -"
    The version of CRM is crm 2007 with support stack sp02
    Regards
    Ranadhir

    Thanks Venkataramanan, after the implementing the note 1117598 and 1101434 the problem solved.
    Regards
    Ranadhir

  • SE80 Dump - Syntax error in program CL_GUI_ALV_GRID

    Hi,
    We have applied 2 sap notes and after this there were some inactive objects.
    1353846 & 875986.If i go ST22 /SE 80 i am getting thes dumps.. I tried checking inactive object via SE38/Environment Se24/Environment i get the same dump..
    Unkowingly We did it in wrong sequence so de-implemented but still have some inactive objects how do we activate those class files.
    Already logged a ticket with SAP but curious to know if there is anyway to resolve this issue.
    Short text
         Syntax error in program "CL_GUI_ALV_GRID===============CP ".
    What happened?
         Error in the ABAP Application Program
         The current ABAP program "CL_DD_AREA====================CP" had to b
          terminated because it has
         come across a statement that unfortunately cannot be executed.
         The following syntax error occurred in program
          "CL_GUI_ALV_GRID===============CP " in include
          "CL_SALV_BS_DATA===============CU " in
         line 10:
         "Type "IF_SALV_BS_DATA" is unknown"
         The include has been created and last changed by:
         Created by: "SAP "
          Error in the ABAP Application Program
         The current ABAP program "CL_DD_AREA====================CP" had to b
          terminated because it has
         come across a statement that unfortunately cannot be executed.
    Rgds
    Vara

    Hi Vara,
    it depends on what notes you applied, what release you are on. Frequently notes have preconditions (i.e. applying other notes) or some manual work must be done like modifying function interfaces.
    Go through the notes again, tell us the numbers.
    Regards,
    Clemens

Maybe you are looking for