LSO Follow Up (WBT) - Runtime error due to ceased employees

We have just created a custom program which confirms participation for learners (web-based training). In Production we will create a nightly job that confirms participation if the learner forgets to click on this link.
This is done by using ABAP program SAPLLSO_FOLLOWUP.
It's working fine, however we've come across one issue. We are getting runtime errors when executing the program. After some investigation we found out this is because we have Ceased employees enrolled in the courses.
As as example, in our Test Environment we have a WBT course which has three people enrolled. One of those people is now ceased. When you right click on the course (via the dynamic menu) and click on Follow Up, you get the runtime error.
We can't cancel the ceased employee since he/she has already completed the course. So as a work around, we changed the Course Type "Completion Specifications" infotype so learners can be "canceled at any time". We then cancelled the ceased employee from the course. We then right clicked on the course>follow up, this time it worked.
Obviously this work around won't be suitable for Produciton. We don't want to cancel ceased employees from a course as we still want to keep a record of their training. So is there a way around this???
Any help would be greatly appreciated!!!!
Cheers
Shaun

Figured it out - data issue

Similar Messages

Runtime Error due To ABAP Dump LOAD_TYPE_VERSION_MISMATCH

Hi,
We had a requirement were were asked to add some customer specific fields to Material Master Table MARA.
We did that by appending a z structure to Material master Table. After some while we had made a change in the Data type of a fields in the structure, while activating it was giving a warning message that other dependent structure of Mara table would be affected & activation needs to be done for that dependent structures also. the activation was done but still with warning message.
When this transport request was moved to Production, all those users which were using T-codes related to Material master MM01/02/03 & other T-codes were receiving ABAP dump LOAD_TYPE_VERSION_MISMATCH.
What could be the reason for such ABAP dump ?
Again it is observed that after running it 2-3 times, it is not throwingany runtime errors. We have also tried to regenerate objects related to transport request.
Edited by: priyeshosi on Jul 2, 2011 2:42 PM

Hi priyeshosi,
thats normal.
If a user starts a transaction, the system knows that something has changed and will automatically trigger compilation of the object.
If a user starts a transaction and does not close it - just not to have to start it again too many times -, and then you import the transport, you will probably get the load type mismatch dump as soon as the users uses the already loaded transaction.
The best way to avoid this is importing significant changes in the night when nobody or only few users are working. If this is not possible, the administrator can insert a warning message that pops up when the users takes any action.
You can also start report for mass generation after importing the transport, this will avoid the re-generation triggering but it will not help transactions already loaded into memory.
Regards,
Clemens

Portal Runtime Error due to use of string buffer

Hi All,
Whenever I run a portal component in which i have used srting buffer i am getting portal runtime error like
java.lang.StringBuffer.append(Ljava/lang/String;)Ljava/lang/AbstractStringBuilder;.
but same code run fine from my colleague's system/ NWDS .I reinstalled my NWDS but still same problem .What could be reson for this strange behaviour?
Provide your inputs to solve this problem.
Regards,
Madhvika

Hi,
Check the JDK version for compiling, it should be 1.4.
To check this in NWDS goto menu: windows --> preference --> Java --> Compiler.
Here check tab Compliance and Classfiles.
If this does not solve, check if you installed JDK 1.5, if so uninstall it.
Also check this, may be a NWDS upgrade can help:
Re: Modify or field-symbol statement
Regards,
Praveen Gudapati

Runtime Error due to activating Fund Management

Hi,
I had activated Funds Management in SAP. I started getting Run Time Errors. I deactivated the Fund Management. But still the Run Time Error is there. I am attaching the file for your reference.
I enquired with the Basis consultant who is telling this is a Functional problem, hence I need to solve this. I checked all the configurations, but could not find the exact problem.
Can anybody tell me how this can be resolved.
Note: This error is showing in Quality Server. There was a copying from Production to Quality.

In the error I see the statement before the dump comes is PERFORM exit--entry_from_table | | 1039| IN PROGRAM (-callback_report)
That sounds like an user exit from a table that is not there.
You say you had a copy from production. It could be that a user exit which was not implemented yet in production and therefore not in the exit table. is now also not present anymore in your Q system after the copy. Were there any changes about to go to production ?
Also in the dump I read the comment:
| 1063|* version and guid are used by strategy -> further params for generated | | 1064|* routines. guid is only used for reference purposes and not returned at | | 1065|* the moment
That could possibly mean that this is a generated program. Maybe you need to regenerate it.
I also see: STEP--METHOD_DRULE
That could mean that these have something to do with rules that have not been maintained.
You could ask a programmer to debug the program and see where SAP tries to get the rules and exit information from (which table) .
Maybe that give you a clue what is going wrong.
If you have a table name start SM30 and click customizing. If it opens a customizing transaction then that is where you need to maintain entries.

FB03 transaction gives runtime error due to time out!

Hi All,
In the transaction FB03, I entered a reference number that has not yet been created and then a company code of 2130 and fiscal year 2010 and hit enter. It takes a lot of time to show the error message that "No documents exists which fulfills the selection criteria".
I debugged and found that a FETCH NEW CURSOR statement takes time and hence the delay in showing the o/p.
The exact ABAP statement is :- FETCH NEW CURSOR dbcursor INTO CORRESPONDING FIELDS OF ex_result.
Please suggest me if there is some note to be implemented or any other solution for the same!
Thanks,
Safeer.

I entered a reference number that has not yet been created and then a company code of 2130 and fiscal year 2010 and hit enter. It takes a lot of time to show the error message that "No documents exists which fulfills the selection criteria".
Trace the process to determine if there is a bad index being used. Is the search using BKPF~1 or another index? Are your DB stats up to date? As for notes, you're unlikely to find one but don't ask for them here, search for them on OSS.

Runtime error in distribution FM 'CVV5_EVENT_START_DISTRIBUTION'

Dear All,
I am facing an issue in document distribution. Business scenario: PR is created with a doument. PR goes through a release strategy which is designed through a Workflow. When PR is finally approved, Documnet distribution happens. Business object DRAW is called with event CHANGED and hence this FM CVV5_EVENT_START_DISTRIBUTION is called. However this results in a runtime error due to exception 'NO_RELATION_EXIST'. I am not able to debug and find if any necessary parameter is getting missed and i do not have too much information on DMS.
Can somebody guide me in resolving this issue. If any other information is needed then please post it.
Thanking you in advance.
Regards,
Saud

Thnaks a lot. That note is explicitly for this problem. I will take it forward now. Will revert back in case of any issue. Thanks again.
Regards,
Saud

Runtime Error : CALL_DIALOG_CONTAINER_MISSING

Please Help, I am getting the following Dump:
Regards,
Runtime Errors         CALL_DIALOG_CONTAINER_MISSING
Date and Time          04.12.2008 10:29:33
Short tex
     Format error during parameter transfer: No further container available.
What happened?
Error in the SAP kernel.
The current ABAP "SAPMS380" program had to be terminated because the
ABAP processor detected an internal system error.
What can you do?
Note which actions and input led to the error.
For further help in handling the problem, contact your SAP administrator
You can use the ABAP dump analysis transaction ST22 to view and manage
termination messages, in particular for long term reference.
Error analysis
     For a precise analysis of the error, you should supply
     documents with as many details as possible.
How to correct the error
     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.
          If the error occures in a non-modified SAP program, you may be able to
          find an interim solution in an SAP Note.
          If you have access to SAP Notes, carry out a search with the following
          keywords:
          "CALL_DIALOG_CONTAINER_MISSING" " "
          "SAPMS380" or " "
          "SYSTEM-EXIT"
     System environment
          SAP-Release 700
          Application server... "DMATE"
          Network address...... "140.1.1.141"
          Operating system..... "Windows NT"
          Release.............. "5.2"
          Hardware type........ "4x AMD64 Level"
          Character length.... 16 Bits
          Pointer length....... 64 Bits
          Work process number.. 1
          Shortdump setting.... "full"
          Database server... "dmate"
          Database type..... "ADABAS D"
          Database name..... "AD0"
          Database user ID.. "SAPAD0"
          Char.set.... "C"
          SAP kernel....... 700
          created (date)... "Jun 23 2008 00:09:46"
          create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
          Database version. "SQLDBC 7.6.0.018 CL 119055 "
          Patch level. 166
          Patch text.. " "
          Database............. "MaxDB 7.6, MaxDB 7.7"
          SAP database version. 700
          Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
           NT 6.0"
          Memory consumption
          Roll.... 16192
          EM...... 456692560
          Heap.... 0
          Page.... 267976704
          MM Used. 833296
          MM Free. 3353920
     User and Transaction
          Client.............. 040
          User................ "CONSULTANT"
          Language key........ "E"
          Transaction......... "FB1S "
          Transactions ID..... "A5CCC1DDC388F1439FA4001143E563CA"
          Program............. "SAPMS380"
          Screen.............. "SAPMS380 0100"
          Screen line......... 0
     Information on where terminated
          Termination occurred in the ABAP program "SAPMS380" - in "SYSTEM-EXIT".
          The main program was "SAPMS380 ".
          In the source code you have the termination point in line 0
          of the (Include) program " ".
     Contents of system fields
     Name     Val.
     SY-SUBRC     0
     SY-INDEX     0
     SY-TABIX     0
     SY-DBCNT     0
     SY-FDPOS     0
     SY-LSIND     0
     SY-PAGNO     0
     SY-LINNO     1
     SY-COLNO     1
     SY-PFKEY
     SY-UCOMM
     SY-TITLE     ABAP Runtime Error
     SY-MSGTY
     SY-MSGID
     SY-MSGNO     000
     SY-MSGV1
     SY-MSGV2
     SY-MSGV3
     SY-MSGV4
     SY-MODNO     0
     SY-DATUM     20081204
     SY-UZEIT     102932
     SY-XPROG
     SY-XFORM
     Active Calls/Events
     No.   Ty.          Program                             Include                             Line
           Name
         1 EVENT        SAPMS380                            ???                                     0
           SYSTEM-EXIT
     Chosen variables
     Name
         Val.
     No.          1     Ty.      EVENT
     Name      SYSTEM-EXIT
     Internal notes
          The termination was triggered in function "imp_ldial_segment"
          of the SAP kernel, in line 1915 of the module
           "//bas/700_REL/src/krn/runt/abxdat.c#4".
          The internal operation just processed is " ".
          Internal mode was started at 20081204102932.
          Requested paging area: 32706.
     Active Calls in SAP Kernel
     Lines of C Stack in Kernel (Structure Differs on Each Platform)
     SAP (R) - R/3(TM) Callstack, Version 1.0
     Copyright (C) SAP AG. All rights reserved.
     Callstack without Exception:
     App       : disp+work.EXE (pid=5540)
     When      : 12/4/2008 10:29:32.703
     Threads   : 2
     Computer Name       : DMATE
     User Name           : SAPServiceAD0
     Number of Processors: 4
     Processor Type: EM64T Family 15 Model 4 Stepping 1
     Windows Version     : 5.2 Current Build: 3790
     State Dump for Thread Id 704
     FramePtr         ReturnAd         Param#1          Function Name
     0000000007ead400 0000000077d7047f 0000000000343e90 ntdll!NtWaitForSingleObject
     0000000007ead4a0 000000000173b1d1 0000000000000014 kernel32!WaitForSingleObjectEx
     0000000007ead6f0 00000000006179c5 0000000000000001 disp+work!NTDebugProcess [ntstcdbg.c (501)]
     0000000007ead720 0000000000b05d9c 0000000000000001 disp+work!CTrcStack [dptstack.c (182)]
     0000000007ead770 0000000000b0afc0 0000000000000001 disp+work!rabax_CStackSave [abrabax.c (7093)]
     0000000007eae150 00000000009736d2 0000000001c859b0 disp+work!ab_rabax [abrabax.c (1231)]
     0000000007eae190 00000000009aee62 0000000007eaf4d0 disp+work!imp_ldial_segment [abxdat.c (1915)]
     0000000007eae1f0 0000000000a2b2a6 0000000007eae330 disp+work!ab_ReadData [abconcnv.c (1397)]
     0000000007eae230 0000000000a2b13a 0000000007eae330 disp+work!ReadSkipValue [abconne.c (7339)]
     0000000007eae270 0000000000a3500f 00000000000000ae disp+work!ReadSkipValue [abconne.c (7369)]
     0000000007eaf710 0000000000977317 0000000003698300 disp+work!ab_connread [abconne.c (4924)]
     0000000007eaf750 0000000000b68126 0000000007eb6050 disp+work!ab_ldiaimport [abxdat.c (2052)]
     0000000007eaf780 000000000064bc9c 0000000000000000 disp+work!ab_nmode [abtcod.c (939)]
     0000000007eb6020 0000000000b6633f 0000000007eb6078 disp+work!dy_cdiag [dynpabsv.c (1830)]
     0000000007eb9640 0000000000b0a0f0 0000000001d0b870 disp+work!ab_sdialog [abtcod.c (300)]
     0000000007eb9f30 0000000000b0c3c0 0000000000000001 disp+work!rabax_do [abrabax.c (5338)]
     0000000007eba910 0000000000a35c78 0000000001d0b8a0 disp+work!ab_rabax [abrabax.c (1497)]
     0000000007eba960 0000000000a36730 0000000800007fff disp+work!ab_mnew [abmarea.c (228)]
     0000000007eba9d0 00000000009726b8 000000000000096a disp+work!ab_mnnext [abmarea.c (297)]
     0000000007ebaa20 00000000009b07bb 000000000000000c disp+work!exp_ldial_segment [abxdat.c (1391)]
     0000000007ebaa70 0000000000a26d88 000007fe7257a190 disp+work!ab_WriteData [abconcnv.c (1590)]
     0000000007ebaaf0 0000000000a33d8b 000007fe8c76c7d8 disp+work!export_itab [abconne.c (3877)]
     0000000007ebbc60 000000000097620d 0000000000000000 disp+work!ab_connwrite [abconne.c (1992)]
     0000000007ebbca0 0000000000b69431 000007ffe7be1f88 disp+work!ab_locex [abxdat.c (1008)]
     0000000007ebbd30 0000000000b69e17 000007ffe7be1f88 disp+work!dial_local [abtcod.c (213)]
     0000000007ebbea0 0000000000ad3390 0000000000000000 disp+work!ab_cdialog [abtcod.c (203)]
     0000000007ebc740 0000000000ad50b3 0000000000000129 disp+work!ab_retdynp [abdynpro.c (671)]
     0000000007ebc7d0 0000000000679328 0000000000000129 disp+work!ab_dstep [abdynpro.c (492)]
     0000000007ebc950 000000000067d76d 000007fe725e08ae disp+work!dynpmcal [dymainstp.c (2396)]
     0000000007ebc9f0 000000000067ca2a 0000000000000000 disp+work!dynppai0 [dymainstp.c (1106)]
     0000000007ebcaa0 00000000006395c5 0000000000000000 disp+work!dynprctl [dymainstp.c (360)]
     0000000007ebfc30 00000000004dbc4c 0000000000000002 disp+work!dynpen00 [dymain.c (1646)]
     0000000007ebfeb0 000000000042f096 0000000007f62ff0 disp+work!TskhLoop [thxxhead.c (4538)]
     0000000007ebfee0 000000000040108d ffffffff00000003 disp+work!DpMain [dpxxdisp.c (1136)]
     0000000007ebff10 00000000019e84b1 0000000000000000 disp+work!nlsui_main [thxxanf.c (84)]
     0000000007ebff70 0000000077d5966c 0000000000000000 disp+work!wmainCRTStartup [crtexe.c (498)]
     0000000007ebffa0 0000000000000000 00000000019e8340 kernel32!BaseProcessStart
     State Dump for Thread Id 11a0
     FramePtr         ReturnAd         Param#1          Function Name
     000000000c9dfe40 0000000077d5f651 0000000007f1cc60 ntdll!NtFsControlFile
     000000000c9dfeb0 00000000018ce23f 0000000000000000 kernel32!ConnectNamedPipe
     000000000c9dff40 000007ff7fc411c4 0000000000000000 disp+work!SigIMsgFunc [signt.c (679)]
     000000000c9dff70 0000000077d6b69a 0000000077d6b660 msvcrt!endthreadex
     000000000c9dffa0 0000000000000000 0000000000000000 kernel32!BaseThreadStart
     List of ABAP programs affected
     Index     Typ     Program     Group     Date     Time     Size     Lang.
          0     Prg     SAPMS380          0     09.03.2008     19:40:55        182272     E
          1     Typ     SYST          0     09.09.2004     14:18:12         34816
     Directory of Application Tables
     Name                                     Date       Time       Lngth
         Val.
     Program      SAPMS380
     SYST            . .            : :          00004612
          \0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\x0001\0\0

Hello Juan,
I also received the same error while deleting the Product categories Under Responsibility of a Purchase group in Transaction PPOMA_BBP in SRM.
Once it allows me to delete them but I do the same twice I do get like below
"Runtime error MEMORY_NO_MORE_PAGING has occurred"
If you have any idea on the above issues then please help me to fix this issues.
Thanks & regards
Pratap J

Runtime Error in Acrobat X Pro

After installing Acrobat X Pro on my Windows 7 based PC, when I tried to open the program, received the following message:
An internal error has occurred.
After clicking "OK," the following message appeared:
Runtime Error!
Program C:\.....
This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information.
I have uninstalled and reinstalled Acrobat X Pro 3 times and get the same error.
Please help!

Hi,
Please follow the suggestions provided here : http://helpx.adobe.com/acrobat/kb/runtime-error-roaming-profile-workflows.html

Portal runtime error in MSS

In MSS portal -->Work Overview --> Key Figure Monitor section displays Portal runtime error as follows.
Portal runtime error.
An exception occurred while processing your request. Send the exception ID to your portal administrator.
Exception ID: 03:45_24/10/11_0126_6285950
Refer to the log file for details about this exception.
When I Traced the Log file I got the trace as follows
03:28_24/10/11_0125_6285950
[EXCEPTION]
com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Unable to parse template '<System.Access.WAS.protocol>://<System.Access.WAS.hostname>/sap/bc/webdynpro/<WebDynproNamespace>/<WebDynproApplication>/;sap-ext-sid=<ESID[url_ENCODE]>?sap-ep-iviewhandle=007<ESID[HASH]>&sap-wd-configId=<WebDynproConfiguration>&sap-ep-iviewid=<IView.ShortID>&sap-ep-pcdunit=<IView.PCDUnit.ShortID>&sap-client=<System.client>&sap-language=<Request.Language>&sap-accessibility=<User.Accessibility[SAP_BOOL]>&sap-rtl=<LAF.RightToLeft[SAP_BOOL]>&sap-ep-version=<Portal.Version[url_ENCODE]>&sap-wd-tstamp=<$TimeStamp>&<FPNInfo[IF_false PROCESS_RECURSIVE]>&sap-explanation=<User.Explanation[SAP_BOOL]>&<StylesheetIntegration[IF_true PROCESS_RECURSIVE]>&<Authentication>&<DynamicParameter[PARAMETER_MAPPING PROCESS_RECURSIVE]>&<ForwardParameters[QUERYSTRING]>&<ApplicationParameter[PROCESS_RECURSIVE]>'; the problem occured at position 310. Cannot process expression <System.client> because Invalid System Attribute:
System:    &#39;SAP_LocalSystem&#39;,
Attribute: &#39;client&#39;.
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContentPass(AbstractIntegratorComponent.java:125)
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContent(AbstractIntegratorComponent.java:98)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:545)
at java.security.AccessController.doPrivileged(AccessController.java:246)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:434)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(AccessController.java:219)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
I am new to MSS Portal. Can anyone help me figure out the cause of this error.

Hi,
I am also facing the same issue .Getting runtime Erorr (Whilce Click on MSS--Budget/Projects/recruitment/team..etc...
Is this related to backend Configuraiton issue or Portal installtion error
Portal runtime error
An exception occurred while processing your request. Send the exception ID to your portal administrator.
Exception ID 05:48_09/06/12_0165_22331150
See log file for details about this exception
we have installed the below BP's on (Netweaver 7.3 and backend EHP5)
BP_ERP5COM    1.51
BP_ERP5ESS    1.41
BP_ERP5MSS    1.51
BPERPESSWDA   1.50
SAP_ESS       633
SAP_MSS       630
SAPPCUI_GP    633
Please adivce..
thanks
Matt

Runtime Errors         "READ_REPORT_LINE_TOO_LONG"

i am using a include program to alv list display.
and when i execute the main program.. it gives the following dump.
Runtime Errors         READ_REPORT_LINE_TOO_LONG
Exception              CX_SY_READ_SRC_LINE_TOO_LONG
analysis..
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_READ_SRC_LINE_TOO_LONG', was
not caught in
procedure "K_KKB_FIELDCAT_MERGE" "(FUNCTION)", nor was it propagated by a
RAISING clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
There was an attempt to read program "ZSM_INVFNL" from the database.
The READ REPORT statement allows you to copy a program text into an
internal table. The occupied line length in the program text must not
exceed the width of the internal table.
The internal table "\FUNCTION=K_KKB_FIELDCAT_MERGE\DATA=L_ABAP_SOURCE[]" is 72
characters wide. The program line is
88 characters wide..
can some one tell me how to resolve this...??

In first screen of transaction SE38, go to menubar Utilities->Settings. In the ABAP Editor tab of the popup dialog box look under subtab Editor. At the bottom of the dialog box there should be a checkbox named Downwards-Comp.Line Lngth(72). Uncheck that, press Enter and leave the transaction. Now run your report again, it should be fine this time.
Cheers,
Sougata.

Pro*C compile/runtime errors w/ XMLTYPE

On an Oracle 9iR2 NT machine (Pro*C/C++: Release 9.2.0.1.0)...
1. The following SQL works without error from SQL*Plus:
     DECLARE
     xml_clob CLOB;
     file_name VARCHAR2(200);
     BEGIN
     file_name := 'rsand.xml';
     xml_clob := f_get_xml_document(file_name);
     insert into RCTXMLD values(file_name, XMLTYPE(xml_clob));
     END;
     select extractValue(RCTXMLD_XMLDOC, '/CommonRecord/ReportingSchl[1]/@EntityId')
     from rctxmld
     where rctxmld_docname = 'rsand.xml'
     SELECT existsNode (RCTXMLD_XMLDOC, '/CommonRecord/ReportingSchl[1]')
     FROM RCTXMLD
     WHERE RCTXMLD_DOCNAME = 'rsand.xml'
     SELECT existsNode (RCTXMLD_XMLDOC,'/CommonRecord/ReportingSchl[1]/AttendingSchl[1]')
     FROM RCTXMLD
     WHERE RCTXMLD_DOCNAME = 'rsand.xml'
     SELECT XMLTYPE.existsNode (RCTXMLD_XMLDOC, '/CommonRecord/ReportingSchl[1]')
     FROM RCTXMLD
     WHERE RCTXMLD_DOCNAME = 'rsand.xml'
2. The following SQL compiles and works without error from Pro*C:
EXEC SQL DECLARE REPORTING_SCHOOL CURSOR FOR
SELECT XMLTYPE.existsNode (RCTXMLD_XMLDOC, '/CommonRecord/ReportingSchl[1]')
FROM RCTXMLD
WHERE RCTXMLD_DOCNAME = :file_name_parm;
Note: This only compiles when existsNode is prefixed by "XMLTYPE."
3. The following SQL generates runtime errors from Pro*C:
static void ins_xml_doc(void)
#ifdef SCT_DEBUG
printf("Executing ins_xml_doc\n");
fflush(stdout);
#endif
EXEC SQL EXECUTE
DECLARE
xml_clob CLOB;
BEGIN
xml_clob := f_get_xml_document(:file_name_parm);
INSERT into RCTXMLD VALUES (:file_name_parm, XMLTYPE(xml_clob));
END;
END-EXEC;
POSTORA;
Run Sequence Number....................................:
Processing C:\TEMP\jobsub\finaid\rsand.xml...
Connected.
ORA-22288: file or LOB operation FILEOPEN failed
The process cannot access the file because
it is being used by another process
ORA-06512: at "SYS.DBMS_LOB", line 672
ORA-06512: at "FAISMGR.F_GETÃ±
WRN-ORACERR: Error occurred in file "d:\banner\finaid\c\rerim04.pc" at line 1318
WRN-ERRSTMT: Following statement was last statement parsed:
declare xml_clob CLOB ; BEGIN xml_clob := f_get_xml_document ( :file_n
Unable to initialize device default
4. The following SQL generates compile errors from Pro*C:
EXEC SQL SELECT XMLTYPE.extractValue(RCTXMLD_XMLDOC, '/CommonRecord/ReportingSchl[1]/@EntityId')
INTO :ReportingSchlEntityId
FROM RCTXMLD
WHERE RCTXMLD_DOCNAME = :file_name_parm;
POSTORA;
Processing rerim04, type pc...
Pro*C/C++: Release 9.2.0.1.0 - Production on Thu Feb 6 08:59:46 2003
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
System default option values taken from: D:\oracle\ora92\precomp\admin\pcscfg.cfg
Error at line 1887, column 5 in file d:\banner\finaid\c\rerim04.pc
EXEC SQL SELECT XMLTYPE.extractValue(RCTXMLD_XMLDOC,
....1
PLS-S-00302, component 'EXTRACTVALUE' must be declared
Error at line 1887, column 5 in file d:\banner\finaid\c\rerim04.pc
EXEC SQL SELECT XMLTYPE.extractValue(RCTXMLD_XMLDOC,
....1
PLS-S-00000, SQL Statement ignored
Semantic error at line 1887, column 5, file d:\banner\finaid\c\rerim04.pc:
EXEC SQL SELECT XMLTYPE.extractValue(RCTXMLD_XMLDOC,
....1
PCC-S-02346, PL/SQL found semantic errors
Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 12.00.8168 for 80x86
Copyright (C) Microsoft Corp 1984-1998. All rights reserved.
rerim04.c
fatal error C1083: Cannot open source file: 'C:\TEMP\rerim04.c': No such file or directory

On an Oracle 9iR2 NT machine (Pro*C/C++: Release 9.2.0.1.0)...
1. The following SQL works without error from SQL*Plus:
     DECLARE
     xml_clob CLOB;
     file_name VARCHAR2(200);
     BEGIN
     file_name := 'rsand.xml';
     xml_clob := f_get_xml_document(file_name);
     insert into RCTXMLD values(file_name, XMLTYPE(xml_clob));
     END;
     select extractValue(RCTXMLD_XMLDOC, '/CommonRecord/ReportingSchl[1]/@EntityId')
     from rctxmld
     where rctxmld_docname = 'rsand.xml'
     SELECT existsNode (RCTXMLD_XMLDOC, '/CommonRecord/ReportingSchl[1]')
     FROM RCTXMLD
     WHERE RCTXMLD_DOCNAME = 'rsand.xml'
     SELECT existsNode (RCTXMLD_XMLDOC,'/CommonRecord/ReportingSchl[1]/AttendingSchl[1]')
     FROM RCTXMLD
     WHERE RCTXMLD_DOCNAME = 'rsand.xml'
     SELECT XMLTYPE.existsNode (RCTXMLD_XMLDOC, '/CommonRecord/ReportingSchl[1]')
     FROM RCTXMLD
     WHERE RCTXMLD_DOCNAME = 'rsand.xml'
2. The following SQL compiles and works without error from Pro*C:
EXEC SQL DECLARE REPORTING_SCHOOL CURSOR FOR
SELECT XMLTYPE.existsNode (RCTXMLD_XMLDOC, '/CommonRecord/ReportingSchl[1]')
FROM RCTXMLD
WHERE RCTXMLD_DOCNAME = :file_name_parm;
Note: This only compiles when existsNode is prefixed by "XMLTYPE."
3. The following SQL generates runtime errors from Pro*C:
static void ins_xml_doc(void)
#ifdef SCT_DEBUG
printf("Executing ins_xml_doc\n");
fflush(stdout);
#endif
EXEC SQL EXECUTE
DECLARE
xml_clob CLOB;
BEGIN
xml_clob := f_get_xml_document(:file_name_parm);
INSERT into RCTXMLD VALUES (:file_name_parm, XMLTYPE(xml_clob));
END;
END-EXEC;
POSTORA;
Run Sequence Number....................................:
Processing C:\TEMP\jobsub\finaid\rsand.xml...
Connected.
ORA-22288: file or LOB operation FILEOPEN failed
The process cannot access the file because
it is being used by another process
ORA-06512: at "SYS.DBMS_LOB", line 672
ORA-06512: at "FAISMGR.F_GETÃ±
WRN-ORACERR: Error occurred in file "d:\banner\finaid\c\rerim04.pc" at line 1318
WRN-ERRSTMT: Following statement was last statement parsed:
declare xml_clob CLOB ; BEGIN xml_clob := f_get_xml_document ( :file_n
Unable to initialize device default
4. The following SQL generates compile errors from Pro*C:
EXEC SQL SELECT XMLTYPE.extractValue(RCTXMLD_XMLDOC, '/CommonRecord/ReportingSchl[1]/@EntityId')
INTO :ReportingSchlEntityId
FROM RCTXMLD
WHERE RCTXMLD_DOCNAME = :file_name_parm;
POSTORA;
Processing rerim04, type pc...
Pro*C/C++: Release 9.2.0.1.0 - Production on Thu Feb 6 08:59:46 2003
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
System default option values taken from: D:\oracle\ora92\precomp\admin\pcscfg.cfg
Error at line 1887, column 5 in file d:\banner\finaid\c\rerim04.pc
EXEC SQL SELECT XMLTYPE.extractValue(RCTXMLD_XMLDOC,
....1
PLS-S-00302, component 'EXTRACTVALUE' must be declared
Error at line 1887, column 5 in file d:\banner\finaid\c\rerim04.pc
EXEC SQL SELECT XMLTYPE.extractValue(RCTXMLD_XMLDOC,
....1
PLS-S-00000, SQL Statement ignored
Semantic error at line 1887, column 5, file d:\banner\finaid\c\rerim04.pc:
EXEC SQL SELECT XMLTYPE.extractValue(RCTXMLD_XMLDOC,
....1
PCC-S-02346, PL/SQL found semantic errors
Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 12.00.8168 for 80x86
Copyright (C) Microsoft Corp 1984-1998. All rights reserved.
rerim04.c
fatal error C1083: Cannot open source file: 'C:\TEMP\rerim04.c': No such file or directory

Runtime Error: CONVT_NO_NUMBER with MM01 BDC

Hi All,
I am creating Material Master using Call transaction Method for MM01 Tcode.
I am passing the value called Standard Price (MBEW-STPRS) in the BDC.
Standard price will be like 100.00 (Hundred Rupees)
While passing this value, I am getting Runtime Error with the following details.
Runtime Error: CONVT_NO_NUMBER
Unable to interpret "/" as a number.
258 ----
259 *        Insert field                                                  *
260 ----
261 FORM BDC_FIELD USING FNAM FVAL.
>>>   IF FVAL <> NODATA.
263     CLEAR BDCDATA.
264     BDCDATA-FNAM = FNAM.
265     BDCDATA-FVAL = FVAL.
266     APPEND BDCDATA.
267   ENDIF.
268 ENDFORM.
How to resolve this type of error???
Regards
Pavan

I have defined field STPRS as char(13 length) in the internal table as char.
The field NODATA is having value ' \ ' in the debugging mode.
The code mentioned in my above post is from the standard perform statement.
Even if i provide value as "100" in the flat file, while reaching the statment
perform bdc_field       using 'MBEW-STPRS'
it_mm01-stprs.
it shows as "100.00" in the debugger.
Any idea....????
Regards
Pavan

How to i fix runtime error r6034?

I have an HP 625 laptop with windows 7 installed. I have just ran the latest itunes update and now I am unable to open itunes. The following message shows:
Runtime Error!
Program C:\Program Files (x86)\iTunes\iTunes.exe
R6034
An application has made an attempt to load the C runtime library incorrectly
Please contact the applications support team for more information
Can somebody help please?
Thanks

See Troubleshooting issues with iTunes for Windows updates.
tt2

Fi posting error due to fiscal period error 1

HI SAP GURUS,
I am trying to post TR6 Challan in todays date & getting following message-
Fi posting error due to fiscal period error 1
Message no. 8I216
Diagnosis
Attempt to post the document in a period outside the current Fiscal
period setup.
Procedure
Change the posting date or Change the fiscal period prior to posting
the transaction under consideration.
please help me to resolve the issue.
CHEERS

HI
This error is due to Posting period is not open in FI check the posting period is opened for all the accounts in OB52 then post the entries
hope it will be usefull

VBScript runtime error '800a0006'

I have a site that is ASP and VBScript with MySQL db and it
has been running brilliantly for a number of years, but it has just
started to have errors of the following:
Microsoft VBScript runtime error '800a0006'
Overflow
/admin/grantaccess.asp, line 275
Line 275 is this:
rssubsall_first = MM_offset + 1
rssubsall is the name of my recordset.
It is also intermitent, sometimes the error happens and
others it doesn't. If I get a page to display correctly, I can
click refresh and the exact same page errors - I don't get it!
Any ideas on what is causing this to happen and how I can fix
it?
TIA
Mat

Not sure if this will help but googling the error brought up
this answer
Overflow means you ended up with a number too large for the
variable type.
The easiest way to determine is output the value prior to
attempting to
calculate. You may just need to increase the size of the
variable type (like
int to long).
Paul Whitham
Certified Dreamweaver MX2004 Professional
Adobe Community Expert - Dreamweaver
Valleybiz Internet Design
www.valleybiz.net
"matthew stuart" <[email protected]> wrote
in message
news:eeu03g$r4a$[email protected]..
>I have a site that is ASP and VBScript with MySQL db and
it has been
>running
> brilliantly for a number of years, but it has just
started to have errors
> of
> the following:
>
> Microsoft VBScript runtime error '800a0006'
> Overflow
> /admin/grantaccess.asp, line 275
>
> Line 275 is this:
>
> rssubsall_first = MM_offset + 1
>
> rssubsall is the name of my recordset.
>
> Any ideas on what is causing this to happen and how I
can fix it?
>
> TIA
>
> Mat
>

LSO Follow Up (WBT) - Runtime error due to ceased employees

Similar Messages

Maybe you are looking for