Syntax error dump.

Hi Champs,
We are loading data from ODS data source to the two targets Cube and ODS thru Process Chain.But we are getting SYNTAX ERROR DUMP in the update rule step and because of this our targets are not getting updated.Any idea Why it is so??
It is delta Update thru PSA..
10zin

Hi Tenzin,
I suggest you to debug the code within update rules.
I'm afraid perhaps there is some computation within there causing the error. But to prove it, you need to debug it first.
Here is i deliver you some usefull path regarding debugging:
/people/pavan.bayyapu/blog/2006/09/06/debugging-data-upload-in-bw
Hopefully it can help you a lot.
Regards,
Niel.
thanks for the points you choose to assign.

Similar Messages

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

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

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

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

How to resolve the dump Syntax error in program /1BCWDY/824VCAJI0ED4WMLLJ7N

I have created 4 components and I have linked them to a single web dynpro application component through an interface.
This is working fine in development.
When we moved all these objects to quality and when i run the application it is opening the default component. However when i try to call any other component it is giving the following dump.
Syntax error in program /1BCWDY/824VCAJI0ED4WMLLJ7NV==CP.
When we debugged we found that this dump is arising in the CREATE COMPONENT method.
Please suggest how to resolve this issue.

Hi,
Using the method prepare_dynamic_navigation i am calling all the components.
After this method i have written the following code for deleting the active and create the new component.
Delete the active componet if any before bind the called component
IF wa_cmp_usage-component_usage->has_active_component( ) IS NOT INITIAL.
    wa_cmp_usage-component_usage->delete_component( ).
ENDIF.
Bind the compont called to this main component
wa_cmp_usage-component_usage->create_component( lv_target_comp ).     -
> when i debug, inside this am getting dump.
In ST22 the error is occuring in the following place.
call method (l_gen_class_name)=>if_wdr_classloader~create_instance
    receiving
      component_instance = me->component_factory.
I am actually 5 components. The default and the fifth components are only having tab and a text view. There are no other UI elements. These two components are working.
The remaining components are having many UI elements and these components are giving the above said dumps.
Edited by: Mohamed Aslam on May 13, 2010 12:11 PM

Abap Dump Syntax error in program "/SSF/SLIB " occuring in SOLMAN 7.1???

Hello Friends,
   After upgradation Solman 7.01 to 7.1, During EWA Alert management configuration in step 3 --> Check Software component level phase, we receiving below error.
   Also Syntax error in program "/SSF/SLIB " Dump is occurring inST22. Please find the Abap dump details attachment.
Please help me to resolve this issue.
Regards,
Farkath C

/SSF/SLIB comes from SP A/PI, if there were issues in old version then they should have been reported.
Upgrading may be a solution.
However, there references of ADD_CCDB_ABAP_EXTRACTOR
Execute RFC                                                                            |
|>>>>>| CASE LS_OPT-RFC_CALLTYPE.                                                                 |
| 1640|    WHEN 'SYNC'.                                                                            |
| 1641|      CALL FUNCTION '/SSF/CALL_SUBROUTINE_RFC'                                              |
| 1642|                                   DESTINATION LS_OPT-DESTINATION
That's why I am asking for the latest dump after the run of RTCCTOOL.
Regards

ABAP Query ... syntax error ...... short dump

Hi,
I am getting dump when executing ABAP Query..
Error in the ABAP Application Program
The current ABAP program "AQL4LA==========ZTST_DATA=====" had to be terminated
because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program "/1BCDWB/SAPLIQ000000000486 " in
include "/1BCDWB/LIQ000000000486$04 " in
line 5:
"A FUNCTION already exists with the name "/1BCDWB/IQ000000000486SSCR"."
Any help ?
Giri

Hello,
Please refer to SAP note 723577 and implement the recommendations within and regenerate the query.
Hope this helps.
Regards,
David

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

IW31 Dump - Syntax error in program "SAPLCNTX ".

Dear All,
I am facing a strange problem, while creating a maitnenance order.
Core modules had been implemented earlier and now SAP PM is getting implemented.
Whenever i try to create a maintenance order, system gives below dump.
I have checked with my ABAP team, but we are not able to find out any specific reason for this.
I searched the threads also, but haven't found any thing.
Would request you to please help.
ShrtText
    Syntax error in program "SAPLCNTX ".
What happened?
    Error in ABAP application program.
    The current ABAP program "SAPLCOZV" 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 "SAPLCNTX ", the following syntax error occurred
    in the Include "LCNTXF19 " in line 195:
    ""LV_SUBJECT" is not type-compatible with formal parameter "I_SUBJECT"."
    Author and last person to change the Include are:
    Author "SAP "
    Last changed by "SAP "
Error analysis
    In program "SAPLCNTX ", the following syntax error occurred:
    ""LV_SUBJECT" is not type-compatible with formal parameter "I_SUBJECT"."
Trigger Location of Runtime Error
    Program                                 SAPLCOZV
    Include                                 LCOZVU01
    Row                                     2,549
    Module type                             (FUNCTION)
    Module Name                             CO_ZV_ORDER_POST
Thanks & Regards,
Mihir

Hi,
Please check (or paste here) "What you can do" section of dump. Search OSS notes.
Regards
Shrikant

Dump in transction FD02 - Syntax error.

In transction FD02 i got a dump Syntax error.
I tried to apply this note " 1571237", that corresponds to my problem note but sap says is not applicable.
1 FUNCTION cmd_enqueue_exkna1.
2 *"-----------------------------------------------------------------
3 *"*"Lokale Schnittstelle:
4 *" IMPORTING
5 *"     VALUE(MODE_KNA1) TYPE ENQMODE DEFAULT 'E'
6 *"     VALUE(MANDT) TYPE KNA1-MANDT DEFAULT SY-MANDT
7 *"     VALUE(KUNNR) TYPE KNA1-KUNNR OPTIONAL
8 *"     VALUE(X_KUNNR) DEFAULT SPACE
9 *"     VALUE(_SCOPE) DEFAULT '2'
10 *"     VALUE(_WAIT) DEFAULT SPACE
11 *"     VALUE(_COLLECT) TYPE DDENQCOLL DEFAULT ' '
12 *" EXCEPTIONS
13 *"      FOREIGN_LOCK
14 *"      SYSTEM_FAILURE
15 *"-----------------------------------------------------------------
16
17   DATA: lv_msgtext(72),
18          ls_bapiret2      TYPE bapiret2,
19          lv_user          TYPE symsgv,
20          ls_syst          TYPE syst,
21          ls_error         TYPE cvis_message,
22          lv_in_lock_table TYPE boolean,
23          lb_badi_lock     TYPE REF TO cmd_additional_locks.
24
25
26 * Initialize exporting parameter
27   CLEAR:
28     ls_error.
29
30 * Check internal table gt_lock_kunnr whether KUNNR is locked
>>>>>   CALL METHOD cmd_ei_api=>get_lock
32     EXPORTING
33       iv_kunnr         = kunnr
34     IMPORTING
35       ev_in_lock_table = lv_in_lock_table.
36
37 * KUNNR is locked already, back to caller
38   IF lv_in_lock_table = 'X'.
39     RETURN.
40   ENDIF.
41
   42 * KUNNR is not locked, try to lock......
   43   CALL FUNCTION 'ENQUEUE_EXKNA1'
   44     EXPORTING
   45       mode_kna1      = mode_kna1
   46       mandt          = mandt
   47       kunnr          = kunnr
   48       x_kunnr        = x_kunnr
   49       _scope         = _scope
   50       _wait          = _wait
My system is a ECC 6.0 kernel 720 patch90.
Component SAP_APPL is 605 patch 5.
Anyone have seen this issue or know how to fix ?
Thank you in advance
Edited by: telmodom on Oct 26, 2011 2:41 PM

Hello,
You couldn't apply this note because the corrections delivered via this note have already been delivered by SAP_APPL 605 patch 05 and your system already has 605 patch 05.
BTW, kernel 100 is available for download, if you are not able to find out any other reason for this syntax error then kernel update can also be tried.
Thanks

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

Basis SP 18 to 20, can not logon through SAPGUI - Syntax Error

Hello Experts,
We had started ECC6.0 SP18 to SP20 patches and now we are getting Syntax error in program "CL_WB_CROSSREFERENCE==========CP ". for most of the transactions executed.
1. Job RDDIMPDP is also failing with message
Program RDDIMPDP is running in client 000
Context TERNAL_INFOS does not contain any fields
Context TERNAL_INFOS contains errors and could therefore not be generated
Context BANK_CTX_JC_REPORT modified
Internal session terminated with a runtime error (refer to ST22)
Job cancelled
2. Here are the details of this short dump, as soon as we get the short dump we get message in the status bar saying "Context BANK_CTX_JC_REPORT modified".
Error in the ABAP Application Program
The current ABAP program "SAPLSEWB" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program
     "CL_WB_CROSSREFERENCE==========CP " in include
     "CL_WB_CROSSREFERENCE==========CM005 " in
    line 7:
""PROGRAM-" expected, not "PROGNAME_""
The include has been created and last changed by:
    Created by: "SAP "
Last changed by: "PEARSONA "
    Error in the ABAP Application Program
The current ABAP program "SAPLSEWB" 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
     CL_WB_CROSSREFERENCE==========CP :
    ""PROGRAM-" expected, not "PROGNAME_""
Trigger Location of Runtime Error
    Program                                 SAPLSEWB
    Include                                 LSEWBU07
    Row                                     837
    Module type                             (FORM)
    Module Name                             PROGRAM_ACTUALIZE
Source Code Extract
Line SourceCde
807 * PROGRAM_ACTUALIZE, ADD_CHILDS und PG_COMPONENT verwendet
808
809   previous_id = '1'.
810   xtype = 'C'.
811   IF xprogram(4) = 'SAPL' OR xprogram+1 CS '/SAPL'.
812 *   Funktionsgruppennamen bestimmen
813     l_program = xprogram.
814     CALL FUNCTION 'FUNCTION_INCLUDE_SPLIT'
815       EXPORTING
816         program   = l_program
817       IMPORTING
818         namespace = l_namespace
819         group     = l_area
820       EXCEPTIONS
821         OTHERS    = 6.
822     IF sy-subrc = 0.
823       xtype+1(1) = 'F'.
824     ELSE.
825       xtype+1(1) = 'P'.
826     ENDIF.
827   ELSEIF current_treename(3) = 'CP_'.
828     xtype+1(1) = 'O'.
829   ELSE.
830     xtype+1(1) = 'P'.
831   ENDIF.
832
833   IF without_crossreference IS INITIAL.
834     IF scros_new_where_used_list = 'X' AND index_parallel EQ space.
835 *     neuer Index Verwendungsnachweis
836       lprogram = xprogram.
>>>>>       CALL METHOD cl_wb_crossreference=>program_index(
838         EXPORTING
839           p_name             = lprogram    " Programmname
840         IMPORTING
841           p_error            = l_error    " Fehler Index wurde nicht aufgebaut
842         EXCEPTIONS
843           program_name_empty = 1
844           OTHERS             = 2
845             ).
846       IF sy-subrc <> 0.
847 *        MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
848 *                   WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
849       ENDIF.
850     ENDIF.
851   ENDIF.
852
3. Tried to generate the program manually through SE38 -> CL_WB_CROSSREFERENCE==========CP --> but it dumps with same message line 7:
""PROGRAM-" expected, not "PROGNAME_""
Appreciate your inputs in resolving this issue.
Raised message with SAP support but didn't hear anything till now - so seeking your experise.
Best Regards
Davinder

Hello Experts,
Further investigation on system showed that we had implemented SNOTE 1374978 - which seems to be causing the problem.
Now as Support packages (SPAM) has locked SNOTE transactions also - is there any way that we can deimplement the above sap note from our system.
Thanks
Davinder

Syntax error when executing a process chain.

Hi gurus,
This is a weird problem that we have been facing since yesterday. In the transaction RSPC, we had created a process chain in Feb 09. It ran smoothly till yesterday. However when I try to schedule the process chain now, it gives me a dump stating Syntax error in program "CL_RSDMD_IOBJ_U_TPL===========CP ".
This same dump is generated whenever I try to display variant of one of the nodes of Process Chain.
I tried checking the corresponding programs but in vain. I have no Idea why am I receiving the error.
If anyone has faced this problem please post the same.
The following is brief overview of the dump.
Information on where terminated Termination occurred in the ABAP program
"CL_RSBK_DTP_DATABASE==========CP" - in "COPY_FROM_DB". The main program was
"RSPC_MAINTAIN ".
In the source code you have the termination point in line 166
of the (Include) program "CL_RSBK_DTP_DATABASE==========CM003".
Any help would be appreciated.
Regards,
Sree.

Hi Rayapa,
There is no Long text as such, however, there is a short text which I have mentioned in my question itself.
And there is a What Happened
which is as follows
Error in the ABAP Application Program
The current ABAP program "CL_RSBK_DTP_DATABASE==========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_RSDMD_IOBJ_U_TPL===========CP " in include
"CL_RSDMD_IOBJ_U_TPL===========CM00E " in
line 4:
"Field "P_BOOKMODE" is unknown. It is neither in one of the specified t"
"ables nor defined by a "DATA" statement. "DATA" statement."
The include has been created and last changed by:
Created by: "SAP"
Last changed by: "<My SAP user>"
Error in the ABAP Application Program
The current ABAP program "CL_RSBK_DTP_DATABASE==========CP" had to be
terminated because it has
come across a statement that unfortunately cannot be executed.
thnkz n regards,
Sree.
Edited by: Sree Nair on Apr 3, 2009 12:10 PM

Error in SUM: MAIN_NEWBAS/XPRAS_AIMMRG: Syntax Error in SAPLSUU6

Pinging Boris Rubarth on what looks to be a minor bug with SUM 1.0 SP12 patch 12. The symptoms and resolution are pretty much identical to that described in Note 2093666 (Syntax Error in SAPLSUU6), except that according to the Note the error was corrected with SUM sp12 patch 6.
The upgrade stopped with a number of errors in phase MAIN_NEWBAS/XPRAS_AIMMRG, essentially that job RDDEXECL terminated for post-import methods:
/SAPSRM/PDO_MD_L_U_AFTER_IMP_I for /SAPPSSRM/CTRL
/SAPSRM/V_SWITCH_AFTER_IMPORT for /SAPSRM/V_SWITCH
/SAPPSSRM_BASE_AFTER_IMP for /SAPPSSRM/VC_HT
/SAPSRM/PDO_MD_L_U_AFTER_IMP for /SAPSRM/V_ITPRO
Digging into the job logs for RDDEXECL I saw that it was short dumping due to a syntax error in program SAPLSUU6, include LSUU6TOP: Type VSUSR_USBAPILINK is unknown. This is just as described in the Note.
The Note says that in SUM SP12 with a patch level earlier than 6, the fix is to logon to client 000 as DDIC and execute report RSSCD_CHECK_GEN to regenerate change documents, then repeat the phase. With SUM SP12 patch 6 or greater, simply repeating the phase should fix it.
Repeating the phase alone did not fix it, but running RSSCD_CHECK_GEN did. This was on patch 12, currently the latest. So, the workaround/fix from the Note still works, but the bug seems to still exist in SUM for a few of these after-import methods.
This was an upgrade from SRM 5.0 to SRM 7.02 sps14 (i.e., including Basis 731 sp14). I ran SUM in 'Single System' Mode. The platform is Windows 2012 R2, SQL Server 2012 sp2 cu5.
Otherwise, everything ran well. There was another slight hiccup in the same phase (after I resolved the one above) in which 'example' BAdI implementations are activated by the upgrade, but I think this might be more specific to SRM.
Note to everyone else -- the discussion is not marked as a question because I have in fact resolved the issue for my system as described and moved on (the upgrade is complete and successful).
Cheers,
Matt

Oops, there is one other small bug. The feedback form doesn't seem to exist. Clicking the link on the 'summary' page of the tool opens the URL http://<host>:4239/eval/EvalForm.html but results in a "Not Found" error.

Syntax Error while applying support package stack 8

I get the following short dump while I was applying support package stack 8. I'm at the latest saint version 34
Runtime Errors         SYNTAX_ERROR
Date and Time          23.07.2009 14:09:27
Short text
     Syntax error in program "CL_DYNPRO_PROPERTY_BAG========CP ".
What happened?
     Error in the ABAP application program.
     The current ABAP program "SAPLSCR2" had to be interrupted because it con
     a statement that cannot be executed.
     In the include "CL_DYNPRO_PROPERTY_BAG========CM009 " in the line 176 of
      program "CL_DYNPRO_PROPERTY_BAG========CP " the following syntax
     errors occur:
     "The field "SPROP_C_TAG_CUSTOMPROPERTY" is unknown, but there is a fiel"
     "d with the similar name "SPROP_C_TAG_TOOLTIPTEXT". "SPROP_C_TAG_TOOLTI"
     "PTEXT"."
     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
      CL_DYNPRO_PROPERTY_BAG========CP :
     "The field "SPROP_C_TAG_CUSTOMPROPERTY" is unknown, but there is a fiel"
     "d with the similar name "SPROP_C_TAG_TOOLTIPTEXT". "SPROP_C_TAG_TOOLTI"
     "PTEXT"."
Trigger Location of Runtime Error
     Program                                 SAPLSCR2
     Include                                 LSCR2U47
     Row                                     31
     Module type                             (FUNCTION)
     Module Name                             RS_SCRP_PROP_ADD_TO_PROP_LIST
1 FUNCTION RS_SCRP_PROP_ADD_TO_PROP_LIST.
2 *"----
3 ""Lokale Schnittstelle:
4 *" IMPORTING
5 *"     REFERENCE(P_TEXTFIELD) TYPE D021S-FNAM OPTIONAL
6 *"     REFERENCE(P_TOOLTIPTEXT_TEXTELEM) TYPE CHAR3 OPTIONAL
7 *"     REFERENCE(P_TOOLTIPTEXT_VARIABLE) TYPE D021S-FNAM OPTIONAL
8 *"     REFERENCE(P_KEEPTAB) TYPE SEU_BOOL OPTIONAL
9 *"     REFERENCE(P_DISABLEIMPLICITLABELS) TYPE SEU_BOOL OPTIONAL
10 *"     REFERENCE(P_BARCODEINPUT) TYPE SEU_BOOL OPTIONAL
11 *" CHANGING
12 *"     REFERENCE(P_PROP_LIST) TYPE PROP_LIST
13 *"----
14
15 data: l_prop type prop_line,
16       l_prop_list type prop_list,
17       l_string type prop_str.
18
19 * Property TextField
20 * -
21
22 if p_textfield is supplied.
23   clear l_prop_list.
24   clear l_prop.
25   l_prop-name   = sprop_c_tag_textfield_name.
26   l_prop-syntax = sprop_c_syntax_content .
27   l_prop-value = p_textfield.
28   append l_prop to l_prop_list.
29 * Zusammensetzen eines Strings der Form
30 * <Name>value_1</Name> ... <Name>value_n</Name>
>>   call method cl_dynpro_property_bag=>fill_prop_list_into_properties
32     exporting
33       prop_list = l_prop_list
34     importing
35       properties = l_string.
36 * Property-Eintrag zusammensetzen
37   clear l_prop.
38   l_prop-name   = sprop_c_tag_textfield.
39   l_prop-type   = sprop_c_type_string.
40   l_prop-syntax = sprop_c_syntax_content .
41   l_prop-value = l_string.
42 * Property-Eintrag in PROP_LIST aufnehmen/ersetzen
43   read table p_prop_list transporting no fields
44       with key name = l_prop-name.
45   if sy-subrc = 0.
46     modify p_prop_list index sy-tabix
47         from l_prop.
48   else.
49     append l_prop to p_prop_list.
50 endif.
Can anyone help me? I now get the same error with executing other transactions as well.

Hi,
Please let us know the component which you are trying to apply. Is it BASIS or ABAP or BW and also let us know the version?
I hope you are applying the BW patch 8, as per SAP's recommendation we need to apply both 8 an 9 patch of BW at the same time. If not we need to apply some notes which you could find in the service market place. Once you apply the notes, you can proceed with the SP application.
Regards,
Varadhu

Syntax error dump.

Similar Messages

Maybe you are looking for