ERROR in program SAPLV14A (ECC 6.0)

Hello experts,
We just upgraded to ECC 6.0
and the functional team is not able to create any sales order because of an error in program SAPLV14A
Here is the short text:
Short text
Syntax error in program "SAPLV14A ".
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLV69A" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program "SAPLV14A " in include "LV14AU48
     " in
line 114:
""NO-" expected, not "NO_"."
The include has been created and last changed by:
    Created by: "46CUPGSPAU "
    Last changed by: "PATEL "
    Error in the ABAP Application Program
The current ABAP program "SAPLV69A" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
The code is like this
IF NO_ERROR_IF_NEW_REBATE IS INITIAL.
Check auf KSPAE
    IF CREATE_CREDIT_NOTE = YES OR
       SAVE_CREDIT_NOTE   = YES OR
       DO_PRE_SETTLEMENT_CHECKS   = YES.
Neues Verfahren ?
      IF I_NEW_REBATE_PROCESSING = YES.
        LOOP AT CONDITION
             WHERE KSPAE = YES.
          MESSAGE E780 WITH BONUS_AGREEMENT-KNUMA RAISING ERROR_MESSAGE.
        ENDLOOP.
      ENDIF.
    ENDIF.
ENDIF.
Can anybody please tell me what is wrong?

Hello everyone,
I just found out that we had a wrong version of the FM (beta 1 apparently).
So we are trying to get the correct one.
What is the version beta 1?

Similar Messages

Error in installation of ECC 6 Import ABAP

I have got error during installation of ECC 6 on win 2003 and oracle.
"Not all objects are succefully processed. DIAGNOSIS: For detail see output file with invalid objects invalid_objects.txt and log file object_checker.log SOLUTION: Normally it indicates the data load error but in some special case (for example if some objects were created or loaded externally) you can press OK to continue.
Here is invalid_objects.txt
checkObjects=
dbType=ORA
strDirs=E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_1\EXP1\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_2\EXP2\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_3\EXP3\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_4\EXP4\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_5\EXP5\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP6\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP7\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP8\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP9\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP10\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP11\DATA
trace=all
tskDir=C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS
package   object type action status
SAPDFACT ?N      pkey create
and object_checker.log
INFO: 2020-12-31 10:12:55
Object Checker is started.
CONFIG: 2020-12-31 10:12:55
Application options:
checkObjects=
dbType=ORA
strDirs=E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_1\EXP1\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_2\EXP2\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_3\EXP3\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_4\EXP4\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_5\EXP5\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP6\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP7\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP8\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP9\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP10\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP11\DATA
trace=all
tskDir=C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS
CONFIG: 2020-12-31 10:12:55
List of packages with table structure: 'SAP0000'.
INFO: 2020-12-31 10:12:55
19 packages found in 'E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_1\EXP1\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_2\EXP2\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_3\EXP3\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_4\EXP4\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_5\EXP5\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP6\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP7\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP8\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP9\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP10\DATA;E:\51032413_IDES SAP ERP 2005 SR2 Inst. Export 1 of 35\51032413_6\EXP11\DATA' directories.
TRACE: 2020-12-31 10:12:56 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (ADA) index 'MAPR~ADQ' found in STR file for 'SAPAPPL0' package.
TRACE: 2020-12-31 10:12:56 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (!MSS) index 'MLST~1' found in STR file for 'SAPAPPL0' package.
TRACE: 2020-12-31 10:12:56 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (MSS) index 'MLST~1AD' found in STR file for 'SAPAPPL0' package.
TRACE: 2020-12-31 10:12:56 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (!MSS) index 'MLST~2' found in STR file for 'SAPAPPL0' package.
TRACE: 2020-12-31 10:12:56 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (MSS) index 'MLST~2AD' found in STR file for 'SAPAPPL0' package.
TRACE: 2020-12-31 10:12:56 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (!MSS) index 'MLST~4' found in STR file for 'SAPAPPL0' package.
TRACE: 2020-12-31 10:12:56 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (MSS) index 'MLST~4AD' found in STR file for 'SAPAPPL0' package.
TRACE: 2020-12-31 10:12:56 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (ADA) index 'PLMK~ADQ' found in STR file for 'SAPAPPL0' package.
TRACE: 2020-12-31 10:12:57 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (MSS) index 'SEMPLOYES~ARE' found in STR file for 'SAPAPPL0' package.
TRACE: 2020-12-31 10:12:57 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (MSS) index 'SEMPLOYES_APP~ARE' found in STR file for 'SAPAPPL0' package.
TRACE: 2020-12-31 10:12:57 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (MSS) index 'SEMPLOYES_RB~ARE' found in STR file for 'SAPAPPL0' package.
TRACE: 2020-12-31 10:12:57 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (MSS) index 'SEMPLOYES_TI~ARE' found in STR file for 'SAPAPPL0' package.
TRACE: 2020-12-31 10:12:57 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (MSS) index 'SEMPLOY_CSH~ARE' found in STR file for 'SAPAPPL0' package.
TRACE: 2020-12-31 10:12:57 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (MSS) index 'SEMPLOY_SEARCH~ARE' found in STR file for 'SAPAPPL0' package.
TRACE: 2020-12-31 10:12:57 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (MSS) index 'STXH~TDN' found in STR file for 'SAPAPPL0' package.
TRACE: 2020-12-31 10:12:58 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (ADA) index 'BBSID~ADQ' found in STR file for 'SAPAPPL1' package.
TRACE: 2020-12-31 10:12:58 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (ADA) index 'BSID~ADQ' found in STR file for 'SAPAPPL1' package.
TRACE: 2020-12-31 10:12:58 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (DB6) index 'DB6CSTRACE~1' found in STR file for 'SAPAPPL1' package.
TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (ADA) index 'KBED~3' found in STR file for 'SAPAPPL1' package.
TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (ADA) index 'KBED~4' found in STR file for 'SAPAPPL1' package.
TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (ADA) index 'NAST~ADQ' found in STR file for 'SAPAPPL1' package.
TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (ADA) index 'S003~ADQ' found in STR file for 'SAPAPPL1' package.
TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (ADA) index 'S003BIW1~ADQ' found in STR file for 'SAPAPPL1' package.
TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (ADA) index 'S003BIW2~ADQ' found in STR file for 'SAPAPPL1' package.
TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (ADA) index 'S004~ADQ' found in STR file for 'SAPAPPL1' package.
TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (ADA) index 'S004BIW1~ADQ' found in STR file for 'SAPAPPL1' package.
TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (ADA) index 'S004BIW2~ADQ' found in STR file for 'SAPAPPL1' package.
TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (ADA) index 'S006~ADQ' found in STR file for 'SAPAPPL1' package.
TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (ADA) index 'S006BIW1~ADQ' found in STR file for 'SAPAPPL1' package.
TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (ADA) index 'S006BIW2~ADQ' found in STR file for 'SAPAPPL1' package.
TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (ADA) index 'S011~ADQ' found in STR file for 'SAPAPPL1' package.
TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (ADA) index 'S011BIW1~ADQ' found in STR file for 'SAPAPPL1' package.
TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (ADA) index 'S011BIW2~ADQ' found in STR file for 'SAPAPPL1' package.
TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (ADA) index 'S012~ADQ' found in STR file for 'SAPAPPL1' package.
TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (ADA) index 'S012BIW1~ADQ' found in STR file for 'SAPAPPL1' package.
TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (ADA) index 'S012BIW2~ADQ' found in STR file for 'SAPAPPL1' package.
TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (ADA) index 'S013~ADQ' found in STR file for 'SAPAPPL1' package.
TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (ADA) index 'S013BIW1~ADQ' found in STR file for 'SAPAPPL1' package.
TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (ADA) index 'S013BIW2~ADQ' found in STR file for 'SAPAPPL1' package.
TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (ADA) index 'S031~ADQ' found in STR file for 'SAPAPPL1' package.
TRACE: 2020-12-31 10:12:59 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (ADA) index 'S032~ADQ' found in STR file for 'SAPAPPL1' package.
TRACE: 2020-12-31 10:13:02 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Database specific (DB6) index 'VARIS~DB6' found in STR file for 'SAPAPPL2' package.
TRACE: 2020-12-31 10:13:04 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Data load must be skipped for table 'DBPROPERTIES' from STR file for 'SAPSDIC' package.
TRACE: 2020-12-31 10:13:04 com.sap.inst.migcheck.object.ObjectCheckTask collectPackageObjects
Data load must be skipped for table 'DDLOG' from STR file for 'SAPSPROT' package.
ERROR: 2020-12-31 10:13:05
1 objects have error/ignore/execute or unknown status in the task lines.
Invalid objects are saved in 'invalid_objects.txt' file.
INFO: 2020-12-31 10:13:05
Object Checker is stopped.
I have not installed any object manually. Also not sure which object did not installed properly? Any idea or suggestion for this?
Thanks
Edited by: Prinesh Patel on Jan 7, 2008 7:35 PM

Hi Patel,
                     Thanks for your update.
Regards,
Hari.

Error in Transferred from ECC to GTS

Hi experts
We are getting the following errors in our Development and Staging system
When running transaction /SAPSLL/PRODUCT_TLSH
Red Light on
Log: MATERIAL TRANSFER 09/19/2011 12:03:42
Green light on
Transfer Log for Product IM001FERT1-NY01 Transferred from Feeder System DEVCLNT020
Red light on
Object /SAPSLL/EPR is blocked by user ERUKULLA
Red light on
Internal error in program object /SAPSLL/API_6850_SYNCH (RC = 2) - processing terminated
Our ECC 6.0 Development system is on
PI_BASIS
Release - 701
Level - 0006
Highest Supp Pack - SAPK-70106INPBASIS
Software Component Description - Basis Plug In
Our GTS Development system is on
PI_BASIS
Release - 2006_1_700
Level - 0015
Highest Supp Pack - SAPKIPYM15
Software Component Description - Basis Plug In ( PI_BASIS) 2006_1_700
Can anyone tell me if those of the correct versions for each system?

Hi Teresa,
I'm not completely familiar with the technicalities, but one of the things that will cause Product Transfer to fail with the exception "Processing Error" (RC = 2) is a missing or full Number Range. So check the Number Range SLL_PROD, and make sure that Interval '01' exists with available numbers.
As far as I know, the Product Transfer works ok with more-or-less any versions of ECC and GTS.
Regards,
Dave

Need to Trigger a Program in ECC after the DSO load has completed

HI Experts,
I have scenario where i need to trigger a Program in ECC after the load to DSO has been completed successfully. Basically opposite of the everyday scenario.
Can i still use the the RSSM_EVENT_RAISE FM in the program to call the event in ECC.
If the above is true.Do i need to have code in the program to confirm the DSO has been loaded or can i just have the program (which basically calls the FM RSSM_EVENT_RAISE) appended to the process chain after the DSO Activation?
Appreciate your advice

Hi,
To help future proof your solution, lean towards using the process chain as much as possible.
A "Green/Success" only link from the DataStore Activation process variant to an ABAP Program process variant will work nicely. It will also still allow your program to be executed by other scenarios (like manually because you want the event raised now without any dependency on the DataStore status).
SAP now recommends you use the CL_BATCH_EVENT class and it's methods to interact with the system events. Use transaction SE24 to review the methods and parameters available and then use the sample code below to test your solution.
Here is a starting point for coding that is used within an ABAP Program process variant in a process chain.
Use transaction SE38 to store this code to be called by the ABAP Program process variant.
constants:
c_interrupt_eventid   type btceventid value '[Event]',
c_interrupt_eventparm type btcevtparm value '[Parameter]'.
data:
l_interrupt_eventid   type btceventid value c_interrupt_eventid,
l_interrupt_eventparm type btcevtparm value c_interrupt_eventparm.
call method cl_batch_event=>raise
EXPORTING
    i_eventid                      = l_interrupt_eventid
    i_eventparm                    = l_interrupt_eventparm
EXCEPTIONS
    excpt_raise_failed             = 2
    excpt_server_accepts_no_events = 3
    excpt_raise_forbidden          = 4
    excpt_unknown_event            = 5
    excpt_no_authority             = 6
    others                         = 1.
if sy-subrc <> 0.
message e051(rsar) with 'Failed to raise background event.' c_interrupt_eventid c_interrupt_eventparm.
endif.
Note: The error message is process chain friendly and will appear in the RSPC transaction GUI and system logs.
Hope this helps,
John.

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

Unable to login in the system ---- Syntex Error is Program SAPLSFES

Hi,
We have Sol_Man 7(N/W 700) in Win2003 and MSSQL 2005.
During Support pack SAPKB70014 application in our Soloution Manager, I have continued all the step in Dialog but today it shows a message that "Inform SAP system for tp termination".The SP application was running for almost 12-14hrs.
Then I restart my SAP system.Now when I opening SAP GUI
Message is comming
ABAP Runtime Error   Error Code <no erorr name or code was mentioned >
In bottom of the page messege is comming
" Syntex Error is Program SAPLSFES "
Login name & password not asking.
I also found in the Slog that
"WARNING:       Background job RDDIMPDP could not be started or terminated abnormally."
In SAPIB70014
2EETW000 sap_dext called with msgnr "1":
2EETW000 -
db call info -
2EETW000 function:   db_xrtab
2EETW000 fcode:      RT_MI_LOAD
2EETW000 tabname:    SPROXHDR
2EETW000 len (char): 1740
2EETW000 key:        CLASCX_SERVICES_REGISTRY_SIPUBLIS8 CLASCX_SERVICES_REGISTRY_SIPUBLIS82F7E61BA8717B7CD295188A843F6CB8E97F12D39
2EETW000 retcode:    1
2EETW125 SQL error "1105" during "" access: "[1105] Could not allocate space for object 'dbo.SPROXHDR'.'SPROXHDR~HAS' in database 'SM1' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup."
I also checked and found that TRBAT table contains only header information where as TRJOB table is empty.
Also found tp.exe in Task Manager.
I have already created a message with SAP.
Please guide me in this regard.
Regards,
Partha

WARNING: Background job RDDIMPDP could not be started or terminated abnormally."
login into Client 000 and schedule the background job again.
Could not allocate space for object 'dbo.SPROXHDR'.'SPROXHDR~HAS' in database 'SM1' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup."
Check the database space also. i think there is some space problem also, you need to add some space or need to add datafile.
Regards,
Subhash

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

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

Abort system error in program CL_RSDM_READ_MASTER_DATA and form_sidval_dire

HI All,
The following error is thrown when I execute the query.
abort system error in program CL_RSDM_READ_MASTER_DATA and form_sidval_direct_
However, earlier today, I ran this query successfully several times.This Query is on a multiprovider.
Appreciate your help in advance.
Regards,
Harika

Dear Harika,
Try to repair at RSRV and check.
Check: Re: SID error for characteristic
Srini

BW-WebI Report: MDDataSetBW.GetCellData. System error in program

Hi,
I'm trying to run a WebIntelligence Report connected with BW Query but return error before showing the results.
The error is:
Error in MDDataSetBW.GetCellData. System error in program CL_RSDRC_MULTIPROV and form SETRESOLVE-01- (consid.TxtDescrit.). (WIS 10901)
My query in BO contain 8 dimensions and 2 measures.
Someone has been there?
Tks!
Edited by: Peeter Cassiano Antunes Bonomo on Sep 6, 2011 7:33 PM

Ingo,
running the query in RSRT with the same elements works perfectly.The results are displayed.
But tested the MDX query in the transaction MDXTest and entered in the ABAP Debugger, press F8 and the following message appeared:
"The current application triggered a termination with a short dump".
"The current application program detected a situation which really should not occur. Therefore, a termination with a short dump was triggered on purpose by the key word MESSAGE (type x)."
"Short text of error message:
System error in program SAPLRRK0 and form CHECK_KHANDLE (consid.TxtDescrit)."
Does that help?
Tks,
Edited by: Peeter Cassiano Antunes Bonomo on Sep 9, 2011 3:18 PM

When I try to open an embedded PDF file I get an error "The program used to create this object is AcroExch.exe.

When I try to open an embedded PDF file (Word doc) I get an error "The program used to create this object is AcroExch.exe. That program is either not installed on your computer, or is corrupt..." I've tried about everything from unchecking
protected mode at startup to removing & reinstalling Adobe. Nothing seems to fix this issue. Any other ideas?
This is happening on Adobe reader 9, 10 & 11 with MS Word 2010 & 2013. I've uninstalled, cleaned & reinstalled Reader 9, 10 & 11, as well as Acrobat 10 Pro & 11 Standard. Removed "Protected mode at startup, and changed
the default program for viewing from reader to Acrobat. This will not go away. It is affecting production at our company.

" Help > Troubleshooting Information > Profile Directory: Open Containing Folder" . i can't find open containing folder in profile directory. it does give me the option to open the places.sqlite file using graphic converter. when i try that, graphic converter gives me a window saying that it can't be opened because it is corrupted or is not a file type supported by graphic converter.
i appreciate your help with a workaround to get the old bookmarks. that works. however, the problem has morphed from that concern to why adobe reader [the default app.] won't open firefox .sqlite files. is the problem in adobe reader or firefox? also, how can i tell if the places.sqlite file is corrupt?
i'm getting in over my head here and do appreciate your help.

!!System error in program SAPLRS_EXCEPTION and form RS_EXCEPTION_TO_MESSAGE

Hi Gurus,
Mater data text loading from a DSO to a InfoObject has failed in the process Chain at DTP step while trying to extract Data packet 2 from the DSO.
In the log i am getting following error message:
"System error in program SAPLRS_EXCEPTION and form RS_EXCEPTION_TO_MESSAGE (see long text)
Message no. BRAIN299".
Please help urgent.
FYI.....
we have recently done upgrade from BI/ABAP SP11 to SP15 and the latest Java SP || 14 (both included in SPS 14).
Points will surely be awarded.
Thanks,
Anurag

Hello Anurag,
Could you solve this problem? If so, please share the solution with me. I'm getting the same error while loading data using DTPs.
Regards,
Neha

Abort System Error in Program SAPLRRV and for RRSV_CHAVL_TO_VALUE_CONVERT

Hello SDN
While refreshing a query in a Workbook, I have received this error message and getting disconnecting form the BW server.
"Abort System Error in Program SAPLRRV and for RRSV_CHAVL_TO_VALUE_CONVERT"
Does anyone has any idea? It is happening in Production and need to fix it as soon as possible.
Appreciate any help and points will be assigned for useful information.
Thanks
kumar

Hi Dinesh
It is stopping at the BREAK-POINT in Function LRRMSU13(RRMS_X_MESSAGE)
variable_screen=X&template_id=0QUERY_TEMPLATE
In the messages , For generation, it display:
&CAUSE&
The query contains selection elements with "Constant Selection". Such a
query cannot be run in the read mode 'Read Everything at Once'.
&SYSTEM_RESPONSE&
The read mode is automatically converted.
&SYS_ADMIN&
In the Variables, I see
&CAUSE&
Variable <(>&<)>V1& is used in the query in such a way, that an
optional entry is not possible.
For example, you might be using an "Exclude", or the variable might be
connected using OR to additional selections for <(>&<)>V2& in the
global filter, but is still displayed in the columns selections.
It is also not possible to use an optional parameter variable to fill
an interval selection in either the from-field or the to-field.
&SYSTEM_RESPONSE&
&WHAT_TO_DO&
If you are able to accept the mandatory entry, you need not do
anything. Otherwise you must work with several variables in the query.
You can use an optional interval variable to do this.
&SYS_ADMIN&
For Key Figs :
&CAUSE&
Quantities are multiplied with values for the key figure &V2& (&V1&).
This is not sensible.
A basic key figure was probably defined that contain a price. Only
addable amounts should be written on the database. Ratios and prices
are calculated as key figures. Therefore, the system maintains the
correct sequence, meaning summing takes place on every place and then
the quotient is formed.
If a 'price amount' is saved as a basic key figure after all then the
'non-aggregated indicator' can be undone using 'Change key figure'.
Therefore, the system carries out the multiplication (or division)
before the summing. The key figure is then assigned to the group 'Other
columns'.
&WHAT_TO_DO&
Please check the definition of the key figure &V2& (&V1&).
<DS:TRAN.KDNN>Check or change key figure &V1&</>
Can you please let me know how to fix this issue?
Thanks
Kuamr

Error Specify a value for variable-Abort System error in program SAPLRRK0 a

Dear Experts,
Could anyone help me to fix this issue?
I have an Customer exit variable in my query to calulate the first week of the prior year value as per the system calendar. when i execute the query, I am receiving the following error messaged and i am throwing out from the BW server.
The error message is
Error Specify a value for variable ZR00**
Abort System error in program SAPLRRK0 and form APPEND_KHANDLE_1-01-
Many thanks in advance.
Regards.
Krishna.

Hi Kishor,
try runnig the same query in RSRT, with execute and debug option.
Also check in query designer for its correctness.
Hope this helps...
Regards,
umesh

ERROR in program SAPLV14A (ECC 6.0)

Similar Messages

Maybe you are looking for