DAC-104/JBO-110 Runtime Error.

What does the following runtime error mean (how can I fix the
problem?)?
DAC-104: ImmediateAccess setAttribute failed. ColumnView:
LNAME
JBO-110: Cannot update Read only attribute.
I get this error when trying to update a row using
Infoswing-based components.
NOTE: The code worked a moment ago, but I must have messed
something up! Any ideas?
Thanks,
Matt
null

Matt,
I'm not sure what went wrong. Is this repeatable? Were you the
only one accessing the database at that time?
FYI: You can assign different levels of locking for the
SessionInfo control (via the Inspector). You can have optimistic,
pessimistic or no locking at all.
Regards,
Matt Larson (guest) wrote:
: What does the following runtime error mean (how can I fix the
: problem?)?
: DAC-104: ImmediateAccess setAttribute failed. ColumnView:
: LNAME
: JBO-110: Cannot update Read only attribute.
: I get this error when trying to update a row using
: Infoswing-based components.
: NOTE: The code worked a moment ago, but I must have messed
: something up! Any ideas?
: Thanks,
: Matt
null

Similar Messages

New runtime error JBO-27014 appears by upgrating JDv 9.0.2.289 to 9.0.3.1035

Without changing the application source, after the upgrade from Upgrade from JDeveloper 9.0.2.289 to 9.0.3.1035 we are receiving the runtime error code:
oracle.jbo.AttrValException: JBO-27014: Attribute AtyId in Appointmenttypes is required
at oracle.jbo.server.JboMandatoryAttributesValidator.validateMandatoryAttributes(JboMandatoryAttributesValidator.java:115)
at oracle.jbo.server.JboMandatoryAttributesValidator.vetoableChange(JboMandatoryAttributesValidator.java:163)at oracle.jbo.server.EntityDefImpl.validate(EntityDefImpl.java:1719)
at oracle.jbo.server.EntityImpl.validateEntity(EntityImpl.java:1115)
at oracle.jbo.server.EntityImpl.validate(EntityImpl.java:1297)
at oracle.jbo.server.DBTransactionImpl.validate(DBTransactionImpl.java:3261)
at oracle.jbo.server.DBTransactionImpl.commitInternal(DBTransactionImpl.java:1516)
at oracle.jbo.server.DBTransactionImpl.commit(DBTransactionImpl.java:1693)
at oracle.jbo.html.jsp.datatags.CommitTag.doStartTag(CommitTag.java:45)
at jsp_servlet.__appointment_add_proc._jspService(__appointment_add_proc.java:498)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:304)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2456)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2039)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
The AtyId is defined as surrogate key. sequence number
It is strange. This field is a defined DBSequence number and should be automaticaly incremented each new record.
At the "old" version it was working and with the upgrade, not more.
Should one new parameter be defined to have it running again?
Thanks

A bug 2535331 was reported for this issue:
The bug was in 902 that BC4J did not enforce null checks for domains properly. In 903 it does and that leads to validation failure in DBSequence case as in this case, the DB value for the domain is null as database generates the right value for new entities. To fix that when you open/close the Entity-editor it re-establishes the domain settings on the attribute leading it to be non-mandatory.
In JDev 903, Entity editor should not allow DBSequence domains to be "checked" as "Mandatory"
A known workaround is to visit all such entities that have DBSequence attribute marked as mandatory and open/finish editor so that attribute properties for the DBsequence attribute is regenerated and the wizard takes off the mandatory setting.
You may say that the migration/upgrade process should have 'fixed' this and we missed that boat on this issue.

Runtime error 104

My former manager created a helpfile using Adobe Robohelp for
HTML 7. The helpfile is now off being tested on XP and Vista, and
on a handful of pages (out of hundreds), runtime error message 104
is displayed.
Line: 104
Error: Expected ')'
Yes/No.
If you click No then the help page is displayed successfully,
however I'd like to get rid of this bug. Looking in Robohelp, I get
the same error, so am assuming it is a bug generated by Robohelp...
I'm a bit new to all this, so apologies if I'm appearing stupid -
any ideas how I go about resolving it?
Many thanks, Mike

Thanks guys!
I've had a look at the pages and didn't see anything that
separated these pages from any others - but it would be fair to say
I don't really know what I am looking for.
It definitely isnt due to double clicking, so I think we can
eliminate that.
I'm going to try and regenerate the primary layout on my
machine to see if the problem was caused by something on my former
manager's machine. If it doesn't, I found a utility on the web
called regcure which I can download and it claims to fix runtime
errors. I'd need the IT guys to run it in Administrator mode tho.
Worth a try? Any other suggestions?
Mike

Panic Error Like ;- DAC-502 ; JBO-27120 ; ORA-00942

Hi,
I am developing wizard through simple database connection application and save it and try run it run first time ok and I also inserted 2 record in it. But next day I strat OJD 3.1.1.2 and try to insert record in same project I found bellow error.
DAC-502: ResultSetInfo: ResultSet ItemMast could not be opened because of problems opening one or more attributes.
JBO-27120: SQL error during query execution. Statement: SELECT REF AS "REF$",SYS_NC_OID$,ITEM_CD AS "ItemCd",ITEM_DATE AS "ItemDate",OLD_ST_CD AS "OldStCd",ITEM_NM AS "ItemNm",REMARK,COMP_NM AS "CompNm",PROD_GP AS "ProdGp",PROD_IT_GP AS "ProdItGp",ST_ON_HAND AS "StOnHand",RATE,DISC_PER AS "DiscPer",DISC_RS AS "DiscRs",MESU_TYPE AS "MesuType",MRP,MESURE FROM ITEM_MAST
ORA-00942: table or view does not exist
null

Thanks Brain,
It is working well....
How to pass status message in Status Bar.
I created new(open) button and write bellow line in it.
void itemFileOpen_actionPerformed(ActionEvent e) {
statusBar .setText(" Need Help " )
OJD 3.1.1.2 gave me this error = >
D:\jdev3112\myprojects\ShareDM\DataModule.java
Error: (456) method setText(java.lang.String) not found in class oracle.dacf.control.swing.StatusBarControl.
Warning: Deprecated APIs are used. Please recompile with the 'deprecation' option for details.
null

Portal runtime error while trying to run a MSS report

Hello gurus!!
 I setup the MSS reports launchpad and now I am seeing all the list of reports on the reports launchpad. I am able to click on all the links and each link opens up the relevant page and the selection criteria also comes up. However, on the last screen, I get a portal runtime error after I click on the report result button.
The trace file shows the following errors:
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7185 - 630]/>
<!NAME[./log/defaultTrace.trc]/>
<!PATTERN[defaultTrace.trc]/>
<!FORMATTER[com.sap.tc.logging.ListFormatter]/>
<!ENCODING[UTF8]/>
<!FILESET[17, 20, 10485760]/>
<!PREVIOUSFILE[defaultTrace.16.trc]/>
<!NEXTFILE[defaultTrace.18.trc]/>
<!LOGHEADER[END]/>
#1.5 #0050568444360067000005D2000005D400049F27DC8DD843#1300893459438#com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent#sap.com/tcwddispwda#com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent#SSUBBARAO#113523##n/a##ae3b7a53556011e0cd95000000191d7e#SAPEngine_Application_Thread[impl:3]_23##0#0#Fatal#1#/Applications/Xss#Java###null
[EXCEPTION]
#1#com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: Exception condition "PROFILE_NOT_INITIALIZED" raised., error key: RFC_ERROR_SYSTEM_FAILURE
 at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:101)
 at com.sap.xss.hr.cat.record.blc.RfcManager.rfcExecute(RfcManager.java:453)
 at com.sap.xss.hr.cat.record.blc.RfcManager.init(RfcManager.java:820)
 at com.sap.xss.hr.cat.record.blc.wdp.InternalRfcManager.init(InternalRfcManager.java:280)
 at com.sap.xss.hr.cat.record.blc.FcCatRecordInterface.onInit(FcCatRecordInterface.java:353)
 at com.sap.xss.hr.cat.record.blc.wdp.InternalFcCatRecordInterface.onInit(InternalFcCatRecordInterface.java:268)
 at com.sap.xss.hr.cat.record.blc.wdp.InternalFcCatRecordInterface$External.onInit(InternalFcCatRecordInterface.java:542)
 at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:922)
 at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:891)
 at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1084)
 at com.sap.xss.hr.cat.record.vac.calendar.VcCatCalendar.onInit(VcCatCalendar.java:251)
 at com.sap.xss.hr.cat.record.vac.calendar.wdp.InternalVcCatCalendar.onInit(InternalVcCatCalendar.java:194)
 at com.sap.xss.hr.cat.record.vac.calendar.VcCatCalendarInterface.onInit(VcCatCalendarInterface.java:162)
 at com.sap.xss.hr.cat.record.vac.calendar.wdp.InternalVcCatCalendarInterface.onInit(InternalVcCatCalendarInterface.java:146)
 at com.sap.xss.hr.cat.record.vac.calendar.wdp.InternalVcCatCalendarInterface$External.onInit(InternalVcCatCalendarInterface.java:222)
 at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:564)
 at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:438)
 at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:196)
 at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)
 at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
 at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
 at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
 at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
 at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
 at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:783)
 at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:303)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:761)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:696)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
 at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
 at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
 at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:869)
 at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:229)
 at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1346)
 at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:356)
 at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:549)
 at com.sap.portal.pb.PageBuilder.wdDoRefresh(PageBuilder.java:595)
 at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:867)
 at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:755)
 at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPortalDispatch(WindowPhaseModel.java:717)
 at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:136)
 at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
 at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
 at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:333)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:712)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
 at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
 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(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Caused by: com.sap.aii.proxy.framework.core.BaseProxyException: Exception condition "PROFILE_NOT_INITIALIZED" raised., error key: RFC_ERROR_SYSTEM_FAILURE
 at com.sap.aii.proxy.framework.core.AbstractProxy.send$(AbstractProxy.java:150)
 at com.sap.xss.hr.cat.general.model.slim.CatsModelSlim.hrxss_Cat_Wd_Record(CatsModelSlim.java:245)
 at com.sap.xss.hr.cat.general.model.slim.Hrxss_Cat_Wd_Record_Input.doExecute(Hrxss_Cat_Wd_Record_Input.java:137)
 at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:92)
 ... 64 more
Could anybody please guide me how to fix this error and get the reports working properly?
Any help with this is much appreciated.
Thank you!
~Maria Kutty~

Hi,
Please refer to note 878440.
Thanks
Prashant

Help me debug DAC-104, BC4J

DAC-104: ImmediateAccess: setAttribute failed. ColumnView: Hct row: 1
JBO-26080: Error while selecting entity for Cbc
[ODBC S1C00] driver not capable of this operation
This is an Oracle Lite source. I'm confused by the ODBC statement - as I thought I'm running a JDBC connection.
How can I debug this????

I'm a bit further - with debug output on I find:
[267] Executing LOCK...SELECT DAY, HORSE_ID, WBC, HGB, HCT, PLT, MCHC, PMN, STAB, BASO, LYMPH, MONO, EOS, FECAL, MY, ALBUMIN, BL FROM CBC WHERE DAY=? AND HORSE_ID=? FOR UPDATE NOWAIT
I doubt that Oracle LITE supports "Select for update nowait", which is why I then get:
[268] {{+++ id=10059 type: 'JDBC_CREATE_STATEMENT' createPreparedStatement - prefetch size: 1
[269] }}+++ End Event10060 null
[270] SQL Failure in select for lock: [ODBC S1C00] driver not capable of this operation
This is a detail entity of a master detail. It fails like this if you bring up an existing row, then change any field, and tab/navigate to the next field. Apparently at this point DAC/BC4J are trying to lock the row for update for me. I have no idea how this got turned on - how do I turn it back off? [Assuming Oracle Lite does not support "Select for update".
Thanks,
Bryan

ABAP Runtime Error : STRING_LENGTH_TOO_LARGE In Solution Manager 7.0

Hi All,
In SolMan 7.0 when i am using T-code Solution_Manager->Business process Monitoring tab System is give as give below ABAP DUMP . Please Share your idea to resolve this issue.
Runtime Errors                                                       STRING_LENGTH_TOO_LARGE
Except.                                                       CX_SY_RANGE_OUT_OF_BOUNDS
Date and Time                                                       24.11.2009                    12:16:08
     Short text
               Illegal access to a string (length too large)
     What happened?
               Error in the ABAP Application Program
               The current ABAP program "CL_CRM_CCKPT_CFS_SERVICE_HTTP=CP" had to be
                terminated because it has
               come across a statement that unfortunately cannot be executed.
     What can you do?
               Note down which actions and inputs caused the error.
               To process the problem further, contact you SAP system
               administrator.
               Using Transaction ST22 for ABAP Dump Analysis, you can look
               at and manage termination messages, and you can also
               keep them for a long time.
     Error analysis
               An exception occurred that is explained in detail below.
               The exception, which is assigned to class 'CX_SY_RANGE_OUT_OF_BOUNDS', was not
                caught in
               procedure "IF_HTTP_EXTENSION~HANDLE_REQUEST" "(METHOD)", 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:
               In the running program "CL_CRM_CCKPT_CFS_SERVICE_HTTP=CP", part of a string was
                about to be accessed
               with an explicitly specified length.
               However, this length (8) exceeded the current length of the string
               (5).
               This kind of access is illegal.
     How to correct the error
               Reduce the length with which to access the string.
               If the error occurred in your own ABAP program or in an SAP
               program you modified, try to remove 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:
               "STRING_LENGTH_TOO_LARGE" "CX_SY_RANGE_OUT_OF_BOUNDS"
               "CL_CRM_CCKPT_CFS_SERVICE_HTTP=CP" or "CL_CRM_CCKPT_CFS_SERVICE_HTTP=CM004"
               "IF_HTTP_EXTENSION~HANDLE_REQUEST"
               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.
               The exception must either be prevented, caught within proedure
               "IF_HTTP_EXTENSION~HANDLE_REQUEST" "(METHOD)", or its possible occurrence must
                be declared in the
               RAISING clause of the procedure.
               To prevent the exception, note the following:
     System environment
               SAP-Release 701
               Application server... ".........."
               Network address...... ""
               Operating system..... "Windows NT"
               Release.............. "5.2"
               Hardware type........ "8x AMD64 Level"
               Character length.... 16 Bits
               Pointer length....... 64 Bits
               Work process number.. 0
               Shortdump setting.... "full"
               Database server... "................."
               Database type..... "ORACLE"
               Database name..... "SM7"
               Database user ID.. "SAPSR3"
               Terminal.......... ".............."
               Char.set.... "C"
               SAP kernel....... 701
               created (date)... "Oct 12 2008 23:34:32"
               create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
               Database version. "OCI_10201_SHARE (10.2.0.2.0) "
               Patch level. 15
               Patch text.. " "
               Database............. "ORACLE 9.2.0.*.*, ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*"
               SAP database version. 701
               Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
                NT 6.0"
               Memory consumption
               Roll.... 16192
               EM...... 4189840
               Heap.... 0
               Page.... 0
               MM Used. 1513920
               MM Free. 2673296
     User and Transaction
               Client.............. 100
               User................ 182836
               Language Key........ "E"
               Transaction......... " "
               Transactions ID..... "09C5D8DE506DF14DB42D001E682F27BB"
               Program............. "CL_CRM_CCKPT_CFS_SERVICE_HTTP=CP"
               Screen.............. "SAPMHTTP 0010"
               Screen Line......... 2
               Information on Caller ofr "HTTP" Connection:
               Plug-in Type.......... "HTTP"
               Caller IP............. "10.226.33.101"
               Caller Port........... 8080
               Universal Resource Id. "/sap/bc/solman/defaultUser/graphic/solmangraphic.htm"
     Information on where terminated
               Termination occurred in the ABAP program "CL_CRM_CCKPT_CFS_SERVICE_HTTP=CP" -
                in "IF_HTTP_EXTENSION~HANDLE_REQUEST".
               The main program was "SAPMHTTP ".
               In the source code you have the termination point in line 130
               of the (Include) program "CL_CRM_CCKPT_CFS_SERVICE_HTTP=CM004".
               The termination is caused because exception "CX_SY_RANGE_OUT_OF_BOUNDS"
                occurred in
               procedure "IF_HTTP_EXTENSION~HANDLE_REQUEST" "(METHOD)", but it was neither
                handled locally nor declared
               in the RAISING clause of its signature.
               The procedure is in program "CL_CRM_CCKPT_CFS_SERVICE_HTTP=CP "; its source
                code begins in line
               6 of the (Include program "CL_CRM_CCKPT_CFS_SERVICE_HTTP=CM004 ".
     Source Code Extract
     Line               SourceCde
       100               *     url of its for WebGUI links (extension for portal cfs)
       101                     WHEN 'its'.
       102                       lv_its = ls_param_fields-value.
       103               *     name of transaction for WebGUI links (extension for portal cfs)
       104                     WHEN 'trans'.
       105                       lv_trans = ls_param_fields-value.
       106               *     name of transaction parameter for WebGUI links
       107               *     (extension for portal cfs)
       108                     WHEN 'trans_keyname'.
       109                       lv_trans_keyname = ls_param_fields-value.
       110               *     info block
       111                     WHEN gc_parameter_name-io.
       112                       lv_io = ls_param_fields-value.
       113               *     portal base url
       114                     WHEN gc_parameter_name-base_url.
       115                       lv_base_url = ls_param_fields-value.
       116
       117               * Note 834787-- Headers of Infoblocks are not translated in Fact sheet
       118               * display set the language
       119                     WHEN 'sap-language'.
       120                       try.
       121                           set locale language ls_param_fields-value.
       122                         catch CX_SY_LOCALIZATION_ERROR.
       123               * No language with this code is installed.
       124               * use the default one
       125                           SET LOCALE LANGUAGE SPACE.
       126                       endtry.
       127
       128                     WHEN OTHERS.
       129               *       additional types for selection
     >>>>>                       IF ls_param_fields-name(8) EQ 'sel-type'.
       131                         CLEAR ls_sel_param.
       132                         MOVE ls_param_fields-value TO ls_sel_param-name.
       133                         lv_num = ls_param_fields-name+8(*).
       134                         CLEAR lv_key.
       135                         CONCATENATE 'sel-value'
       136                                     lv_num
       137                                INTO lv_key.
       138                         READ TABLE lt_param_fields WITH KEY name = lv_key
       139                              INTO ls_param_fields.
       140                         IF sy-subrc = 0.
       141                           MOVE ls_param_fields-value TO ls_sel_param-value.
       142                         ENDIF.
       143                         APPEND ls_sel_param TO lt_sel_param.
       144                       ENDIF.
       145                   ENDCASE.
       146                 ENDLOOP.
       147
       148               * HTML error message if no business partner
       149                 IF bp IS INITIAL.
     Contents of system fields
     Name                         Val.
     SY-SUBRC                         0
     SY-INDEX                         1
     SY-TABIX                         3
     SY-DBCNT                         1
     SY-FDPOS                         17
     SY-LSIND                         0
     SY-PAGNO                         0
     SY-LINNO                         1
     SY-COLNO                         1
     SY-PFKEY
     SY-UCOMM
     SY-TITLE                         HTTP Control
     SY-MSGTY
     SY-MSGID
     SY-MSGNO                         000
     SY-MSGV1
     SY-MSGV2
     SY-MSGV3
     SY-MSGV4
     SY-MODNO                         0
     SY-DATUM                         20091124
     SY-UZEIT                         121608
     SY-XPROG
     SY-XFORM
     Active Calls/Events
     No.               Ty.                              Program                                                            Include                                   Line
                    Name
         4               METHOD                              CL_CRM_CCKPT_CFS_SERVICE_HTTP=CP                                                            CL_CRM_CCKPT_CFS_SERVICE_HTTP=CM004                                     130
                    CL_CRM_CCKPT_CFS_SERVICE_HTTP=>IF_HTTP_EXTENSION~HANDLE_REQUEST
         3               METHOD                              CL_HTTP_SERVER================CP                                                            CL_HTTP_SERVER================CM00G                                     574
                    CL_HTTP_SERVER=>EXECUTE_REQUEST
         2               FUNCTION                              SAPLHTTP_RUNTIME                                                            LHTTP_RUNTIMEU02                                     942
                    HTTP_DISPATCH_REQUEST
         1               MODULE (PBO)                              SAPMHTTP                                                            SAPMHTTP                                      13
                    %_HTTP_START
     Chosen variables
     Name
               Val.
     No.                   4                    Ty.                         METHOD
     Name               CL_CRM_CCKPT_CFS_SERVICE_HTTP=>IF_HTTP_EXTENSION~HANDLE_REQUEST
     SERVER
               {O:2*\CLASS=CL_HTTP_SERVER_NET}
             F0000000
             D0002000
     LS_PARAM_FIELDS-NAME
               _appl
             56776
             F100C
             00000
             00000
     SY-REPID
               CL_CRM_CCKPT_CFS_SERVICE_HTTP=CP
             4454545444555445554554445455534522222222
             3CF32DF33B04F363F3526935F8440D3000000000
             0000000000000000000000000000000000000000
             0000000000000000000000000000000000000000
     SPACE
             2
             0
             0
             0
     GC_PARAMETER_NAME-BASE_URL
               ep_base_url
             67566765776
             50F2135F52C
             00000000000
             00000000000
Regards
Suresh
Edited by: Suresh Kumar on Nov 24, 2009 3:21 PM

Hi Naveen,
Please find given below BBPCRM & SAP_BW version..
BBPCRM     500     0013     SAPKU50013     BBPCRM     BBP/CRM Supp. Pack.
SAP_BW     701     0003     SAPKW70103     SAP Business Warehouse     Component Supp. Pkg.
This problem is not only with Bussiness process tab (T-Code: Solution_manage) also System monitoring Still i searching solution for this But once we are restarting System that time this problem is not occuring but after some time system is giving this DUMP
Regards,
Suresh

Runtime Error - DBIF_RSQL_INVALID_RSQL - Too many OPEN CURSOR

When I try to train a Decision Tree Model via an APD process in RSANWB, I get a runtime error when my model is configured with too many parameter fields or too many leaves (with 2 leaves it works, with more it fails).
By searching SAP Notes I see that there are many references to this kind of runtime errors. But no note on occurences of it in RSANWB / RSDMWB .
Any information on this anyone?
Claudio Ciardelli
Runtime Errors DBIF_RSQL_INVALID_RSQL
Date and Time 29.07.2005 16:19:21
|ShrtText |
| Error in RSQL module of database interface. |
|What happened? |
| Error in ABAP application program. |
| |
| The current ABAP program "SAPLRS_DME_DECISION_TREE_PRED" had to be terminated |
| because one of the |
| statements could not be executed. |
| |
| This is probably due to an error in the ABAP program. |
| |
|Error analysis |
| The system attempted to open a cursor for a SELECT or OPEN CURSOR |
| statement but all 16 cursors were already in use. |
| The statement that failed accesses table "/BIC/0CDT000030 ". |
| The erroneous statement accesses table "/BIC/0CDT000030 ". |
|Trigger Location of Runtime Error |
| Program SAPLRS_DME_DECISION_TREE_PRED |
| Include LRS_DME_DECISION_TREE_PREDU06 |
| Row 103 |
| Module type (FUNCTION) |
| Module Name RS_DME_DTP_EVALUATE |
|Source Code Extract |
|Line |SourceCde |
| 73|* Prepare for Data evaluation |
| 74| CATCH SYSTEM-EXCEPTIONS OTHERS = 15. |
| 75| CREATE DATA ref TYPE (i_enum_dbtab). |
| 76| ASSIGN ref->* TO <fs_wkarea>. |
| 77| ASSIGN COMPONENT gv_class_dbposit OF STRUCTURE |
| 78| <fs_wkarea> TO <fs_class>. |
| 79| CREATE DATA ref TYPE TABLE OF (i_enum_dbtab). |
| 80| ASSIGN ref->* TO <ft_data>. |
| 81| |
| 82| ENDCATCH. |
| 83| IF sy-subrc = 15. |
| 84|* Error on Assignment. |
| 85| CALL FUNCTION 'RS_DME_COM_ADDMSG_NOLOG' |
| 86| EXPORTING |
| 87| i_type = 'E' |
| 88| i_msgno = 301 |
| 89| i_msgv1 = 'EVALUATION_PHASE' |
| 90| IMPORTING |
| 91| es_return = ls_return. |
| 92| APPEND ls_return TO e_t_return. |
| 93| EXIT. |
| 94| ENDIF. |
| 95| |
| 96|* For the un-trained Rec-Ids, evaluate..... |
| 97| REFRESH lt_recinp. |
| 98| APPEND LINES OF i_t_records TO lt_recinp. |
| 99| SORT lt_recinp . |
| 100|* Open Cursor.. |
| 101| DATA: l_curs TYPE cursor. |
| 102| DATA: l_psize TYPE i VALUE 10000. |
|>>>>>| OPEN CURSOR WITH HOLD l_curs FOR |
| 104| SELECT * FROM (i_enum_dbtab) |
| 105| WHERE rsdmdt_recid NOT IN |
| 106| ( SELECT rsdmdt_recid FROM |
| 107| (i_learn_tab) ). |
| 108| |
| 109|* Start Fetch... |
| 110| DO. |
| 111| FETCH NEXT CURSOR l_curs |
| 112| INTO CORRESPONDING FIELDS OF TABLE <ft_data> |
| 113| PACKAGE SIZE l_psize. |
| 114| IF sy-subrc NE space. |
| 115| EXIT. |
| 116| ENDIF. |
| 117| |
| 118|* Process records... |
| 119| LOOP AT <ft_data> ASSIGNING <fs_wkarea>. |
| 120| |
| 121|* Call Prediction Function. |
| 122| CALL FUNCTION 'RS_DME_DTP_PREDICT_STRUCTURE' |

Hi Claudio,
well the message is very clear and I think in your case you need to split your model into a few somehow equal models, each not having more than 2 leaves.
Another option might be to do more things serially instead of parallel.
Hope it helps
regards
Siggi

Runtime error Dynpro_not_found

Hi experts,
I get the following runtime error when trying to open a Z table under SM30.
Short text
 Dynpro does not exist
Error analysis
 The system attempted to use dynpro 0100 in program "SAPLZGET_ORG".
 This dynpro does not exist.
User and Transaction
Client.............. 100
 User................ "ARUN"
 Language key........ "E"
 Transaction......... "SM30 "
 Transactions ID..... "4976D21BC7F841F0E1000000C0A80046"
Program............. "SAPLZGET_ORG"
 Screen.............. " "
 Screen line......... 0
Line SourceCde
97 i_messnbr = '288'.
 98 ELSE. "customer system
 99 i_messnbr = '289'.
100 ENDIF.
101 ENDIF.
102 MESSAGE ID 'AM' TYPE 'I' NUMBER i_messnbr
103 WITH vim_addr_basetable
104 vim_addr_bastab_field
105 vim_tsadrv-tablename
106 vim_tsadrv-fieldname.
107 CLEAR x_header-adrnbrflag. MODIFY x_header INDEX 1.
108 ELSE. "entry in TSADRV is complete
109 vim_addr_group = vim_tsadrv-addr_group.
110 IF x_header-adrnbrflag EQ 'O'.
111 CALL FUNCTION 'ADDR_GET_STATUS_INFO'
112 TABLES
113 status_table = i_statetab.
114 READ TABLE i_statetab WITH KEY
115 constant = vim_tsadrv-addr_group.
116 IF sy-subrc NE 0. CLEAR i_statetab-value. ENDIF.
117 TRANSLATE i_statetab-value USING ' OXN'.
118 x_header-adrnbrflag = i_statetab-value.
119 MODIFY x_header INDEX 1.
120 ENDIF.
121 ENDIF.
122 ENDIF.
123 ENDIF.
124 PERFORM vim_process_assigns.
125 IF <status>-initializd EQ space. "not processed yet
126 * reset dropdown lists
>>> CALL FUNCTION 'VRM_REFRESH_VALUES'.
128 IF x_header-frm_af_ini NE space. "user exit exists AND
129 * set environment for user exit.
130 ASSIGN dba_sellist-sys TO <vim_sellist>.
131 vim_enqueue_range = x_header-subsetflag. assigned = 'X'.
132 * perform user exit -> 3.0B processed in JUSTIFY_ACTION_MODE
133 PERFORM (x_header-frm_af_ini) IN PROGRAM (sy-repid).
134 ENDIF.
135 * backup DBA_SELLIST
136 * REFRESH vim_dba_sel_kept. "UF210200b
137 * APPEND LINES OF dba_sellist TO vim_dba_sel_kept.
138 * remove multiple values for subsets
139 DELETE dba_sellist WHERE ddic = 'M'.
140 DESCRIBE TABLE dba_sellist.
141 IF sy-tfill GT 0.
142 READ TABLE dba_sellist INDEX sy-tfill.
143 CLEAR dba_sellist-and_or.
144 MODIFY dba_sellist INDEX sy-tabix.
145 ENDIF. "UF210200e
146 ENDIF.
Please kindly help me out with the issue.
Thank You.

Hi,
What is the screen number given when you created the maitenence generator? Over here it seems it is trying to open the table in sm30 using screen 0100.
Try to recreate the table maintenence generator. Delete the existing maintenence generator and when screen number is there select propose screen number so the system suggests the screen number.
Then try to maintain entries via sm30.
Hope this helps.
Regards,
Sachin

Portal Runtime Error occurred when trying to create iView using template.

Hi,
When I tried to create an iView by Content Management through "Existing iView Templates", the Portal runtime error occurred.
(However, when I tried to create an iView through "Deployed Portal Archive" or "Web Dynpro Java Application", it was successful)
If you know the same error and the way to solve, please help me.
Best Regards,
Daisuke Ikari
It occurred below system environment.
Version: NetWeaver 7.0 SPstack18
OS: Windows 2003 Server SP2
RDBMS: Oracle 10.2.0.2
And the error log is below.
08:29_26/03/09_0002_6759950
[EXCEPTION]
java.lang.NoSuchMethodError: com.sapportals.portal.pcd.gl.PcdSearchControls.addExplicitAttributeCheck(Lcom/sapportals/portal/pcd/gl/IPcdAttribute;)V
 at com.sap.portal.pcm.iviewserver.cache.TemplatesCacheSrv.getPCDCatalog(TemplatesCacheSrv.java:184)
 at com.sap.portal.pcm.iviewserver.cache.TemplatesCacheSrv.refresh(TemplatesCacheSrv.java:589)
 at com.sap.portal.pcm.iviewserver.cache.TemplatesCacheSrv.getTemplates(TemplatesCacheSrv.java:646)
 at com.sapportals.admin.templateselection.panes.InitPane.getCatalogList(InitPane.java:206)
 at com.sapportals.admin.templateselection.panes.InitPane.initTemplateList(InitPane.java:122)
 at com.sapportals.admin.templateselection.panes.InitPane.processInput(InitPane.java:59)
 at com.sapportals.admin.wizardframework.core.WizardInstance.doPost(WizardInstance.java:350)
 at com.sapportals.admin.wizardframework.core.WizardInstance.doWizard(WizardInstance.java:174)
 at com.sapportals.admin.wizardframework.core.WizardInstance.doWizard(WizardInstance.java:99)
 at com.sapportals.admin.wizardframework.AbstractDynamicWizard.doContent(AbstractDynamicWizard.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:524)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
 at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
 at com.sapportals.appdesigner.appdesignerfw.TabContentComponent.doOnNodeReady(TabContentComponent.java:110)
 at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:388)
 at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
 at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:368)
 at com.sapportals.portal.prt.pom.AbstractNode.addChildNode(AbstractNode.java:340)
 at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:642)
 at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
 at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:524)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
 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(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)

Thanks for your help. Here is the xml
<PAREVAHRS>
<P_PROJECT_TYPE>Food Equipment</P_PROJECT_TYPE><P_PRJ_CATEGORY>Qualification</P_PRJ_CATEGORY><P_CPM_ID>658</P_CPM_ID><P_FROM_DATE>2007/03/01 00:00:00</P_FROM_DATE><P_TO_DATE>2007/03/31 00:00:00</P_TO_DATE>
<LIST_G_PROGRAM>
<G_PROGRAM>
<PROGRAM_CODE>0180</PROGRAM_CODE>
<PROGRAM_NAME>Food Equipment</PROGRAM_NAME>
<LIST_G_MGR>
<G_MGR>
<PROJ_MGR>Lamoreaux, Mr. David</PROJ_MGR>
<LIST_G_PRJ>
<G_PRJ>
<PROJECT_NUMBER>249400</PROJECT_NUMBER>
<LONG_NAME>KM-60, 100 & 150 BAH, ICE MAKE 249400</LONG_NAME>
<CUSTOMER_NUMBER>22460</CUSTOMER_NUMBER>
<CUSTOMER_NAME>HOSHIZAKI AMERICA, INC.</CUSTOMER_NAME>
<LIST_G_TSKEXP>
<G_TSKEXP>
<TASK_NUMBER>PO01START</TASK_NUMBER>
<EXP_TYPE>100 Labor - Chargeable</EXP_TYPE>
<EXP_DATE/>
<QTY>9.25</QTY>
<REV>0</REV>
</G_TSKEXP>
</LIST_G_TSKEXP>
<PRJREV>0</PRJREV>
<PRJQTY>9.25</PRJQTY>
</G_PRJ>
The PRJREV and PRJQTY is at the same level and they are either zero or non null values.
- Vasu -

Runtime Errors DYNPRO_SYNTAX_ERROR

Hi,
Can any one tell me the solution for this. Runtime Errors DYNPRO_SYNTAX_ERROR.
System environment
    SAP-Release 700
    Application server... "erpd00"
    Network address...... "10.1.25.55"
    Operating system..... "Linux"
    Release.............. "2.6.18-194.
    Hardware type........ "x86_64"
    Character length.... 16 Bits
Information on where terminated
    Termination occurred in the ABAP program "SAPLCPDA" - in "DYNP_CALL".
    The main program was "SAPLCPDI ".
    In the source code you have the termination point in line 111
    of the (Include) program "LCPDAU01".
   81
   82 * Daten aus Dynpro-Workareas auf Exportparameter schieben
   83 *=======================================================================
   84   MOVE:
   85         PLKOD         TO PLKOD_EXP,
   86         RC27S-FLG_ESC TO FLG_ESC,
   87         OK-CODE       TO OK_CODE.
   88
   89 ENDFUNCTION.
   90
   91 *----
   92 *       FORM DYNP_CALL                                                 *
   93 *----
   94 *       Dynpronummer über TCA36 ermitteln und aufrufen                 *
   95 *----
   96 * --> BLDGR_IMP Bildgruppe                                           *
   97 * --> PANEL_IMP Panel
   98 * --> PLNAW_imp Plananwendung
   99 * --> PlNTY_IMP Plantyp
100 *----
101 FORM DYNP_CALL USING BLDGR_IMP
102                      PANEL_IMP
103                      PLNAW_IMP
104                      PLNTY_IMP.
105   DATA BEGIN OF TCA36_TMP.
106           INCLUDE STRUCTURE TCA36.
107   DATA END OF TCA36_TMP.
108   DATA: MPOOL LIKE SY-REPID.
109
110   MPOOL = SY-REPID.
>>>>>   CALL FUNCTION 'TCA36_READ'
112        EXPORTING
113             BLDGR_IMP = BLDGR_IMP
114             PANEL_IMP = PANEL_IMP
115             MPOOL_IMP = MPOOL
116             PLNAW_IMP = PLNAW_IMP
117             PLNTY_IMP = PLNTY_IMP
118        IMPORTING
119             TCA36_EXP = TCA36_TMP.
120   IF TCA36_TMP-WINX1 IS INITIAL AND
121      TCA36_TMP-WINX2 IS INITIAL AND
122      TCA36_TMP-WINY1 IS INITIAL AND
123      TCA36_TMP-WINY2 IS INITIAL.
124     CALL SCREEN TCA36_TMP-DYNPRO.
125   ELSE.
126     CALL SCREEN TCA36_TMP-DYNPRO
127                 STARTING AT TCA36_TMP-WINX1 TCA36_TMP-WINY1
128                 ENDING AT   TCA36_TMP-WINX2 TCA36_TMP-WINY2.
129   ENDIF.
130 ENDFORM.

If this is unmodified SAP code, search for SAP notes. If you cannot find any, raise a message with their support.
It looks like note 1549364 fits the bill.
Rob
Edited by: Rob Burbank on Sep 14, 2011 3:26 PM

Runtime error while creating pdf page

Hi,
I am using FOP0.15 jar ,I am getting runtime error(it was going loop if fo file length is more).Please any one suggest me how to avoid this.
Thanks in advance
Error was
formatting FOs into areas
[1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17] [18] [19] [20] [21] [22] [23] [24] [25] [26] [27
] [28] [29] [30] [31] [32] [33] [34] [35] [36] [37] [38] [39] [40] [41] [42] [43] [44] [45] [46] [47] [48] [49] [50] [51] [52
] [53] [54] [55] [56] [57] [58] [59] [60] [61] [62] [63] [64] [65] [66] [67] [68] [69] [70] [71] [72] [73] [74] [75] [76] [77
] [78] [79] [80] [81] [82] [83] [84] [85] [86] [87] [88] [89] [90] [91] [92] [93] [94] [95] [96] [97] [98] [99] [100] [101] [
102] [103] [104] [105] [106] [107] [108] [109] [110] [111] [112] [113] [114] [115] [116] [117] [118] [119] [120] [121] [122]
[123] [124] [125] [126] [127] [128] [129] [130] [131] [132] [133] [134] [135] [136] [137] [138] [139] [140] [141] [142] [143]..........
regards,s
suneel

how about first upgrading to the latest version of FOP? 0.15? you're far behind...

Runtime Error in Portal Application

Can any body help me in resolving the following runtime error in portal application, (Netweaver Version : 7.0)
Full Message Text
03:21_21/09/11_0002_6275851
[EXCEPTION]
java.lang.NoClassDefFoundError: org.apache.commons.httpclient.methods.RequestEntity
at java.lang.J9VMInternals.verifyImpl(Native Method)
at java.lang.J9VMInternals.verify(J9VMInternals.java:69)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:131)
at java.lang.Class.forNameImpl(Native Method)
at java.lang.Class.forName(Class.java:152)
at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:228)
at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getComponentInstance(PortalComponentItemFacade.java:160)
at com.sapportals.portal.prt.core.broker.PortalComponentItem.getComponentInstance(PortalComponentItem.java:732)
at com.sapportals.portal.prt.component.PortalComponentContext.getComponent(PortalComponentContext.java:103)
at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:242)
at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.refresh(PortalComponentContextItem.java:271)
at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.getContext(PortalComponentContextItem.java:316)
at com.sapportals.portal.prt.component.PortalComponentRequest.getComponentContext(PortalComponentRequest.java:387)
at com.sapportals.portal.prt.connection.PortalRequest.getRootContext(PortalRequest.java:488)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:607)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:540)
at java.security.AccessController.doPrivileged(AccessController.java:246)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:423)
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)
Caused by: java.lang.ClassNotFoundException: org.apache.commons.httpclient.methods.RequestEntity
Found in negative cache

Hi,
this exception seems caused by a missing interface org.apache.commons.httpclient.methods.RequestEntity. Please the following ones:
http://www.jarfinder.com/index.php/java/info/org.apache.commons.httpclient.methods.RequestEntity
Br,
Javier

Portal runtime error while creating users in portal content administrator

I am getting this error while creating new users in portal.
Portal Runtime Error
An exception occurred while processing a request for :
iView : pcd:portal_content/administrator/super_admin/super_admin_role/com.sap.portal.user_administration/com.sap.portal.user_admin_ws/com.sap.portal.user_management/com.sap.portal.createNewUser/com.sap.portal.createNewUser
Component Name : com.sap.portal.usermanagement.admin.CreateNewUser
com/sap/security/core/util/imp/Util.patternMatch(Ljava/lang/String;Ljava/lang/String;Z)Z.
Exception id: 03:51_27/08/08_0028_7431850
See the details for the exception ID in the log file
any help is appreciated...

log file look something like
this
2,5,PRT-Async]##0#0#Error#1#/System/Server#Java###Exception in PortalRequestManager.dispatchRequest without timeout
[EXCEPTION]
#1#java.lang.NoSuchMethodError: com/sap/security/core/util/imp/Util.patternMatch(Ljava/lang/String;Ljava/lang/String;Z)Z
     at com.sap.security.core.admin.util.checkEmail(util.java:110)
     at com.sap.security.core.admin.UserBean.checkFieldValidity(UserBean.java:695)
     at com.sap.security.core.admin.UserBean.checkUser(UserBean.java:591)
     at com.sap.security.core.admin.UserAdminLogic.performUserModify(UserAdminLogic.java:3226)
     at com.sap.security.core.admin.UserAdminLogic.executeRequest(UserAdminLogic.java:552)
     at com.sapportals.portal.prt.component.usermanagement.admin.UserAdminComponent.doContent(UserAdminComponent.java:71)
     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.async.AsyncIncludeRunnable$1$DoDispatchRequest.run(AsyncIncludeRunnable.java:377)
     at java.security.AccessController.doPrivileged(AccessController.java:241)
     at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable.run(AsyncIncludeRunnable.java:390)
     at com.sapportals.portal.prt.core.async.ThreadContextRunnable.run(ThreadContextRunnable.java:164)
     at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:729)
     at java.lang.Thread.run(Thread.java:758)
#1.5#001125A6576A008C00000015000550E2000455943BAE9D63#1219995051656#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#Administrator#197794##irconepd_EPD_7431850#Administrator#f4d062d0759411ddb89b001125a6576a#Thread[PRT-Async 2,5,PRT-Async]##0#0#Error#1#/System/Server#Java###Exception ID:01:00_29/08/08_0043_7431850
[EXCEPTION]
#1#com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component
Component : pcd:portal_content/administrator/super_admin/super_admin_role/com.sap.portal.user_administration/com.sap.portal.user_admin_ws/com.sap.portal.user_management/com.sap.portal.userSearch/com.sap.portal.userSearch
Component class : com.sapportals.portal.prt.component.usermanagement.admin.UserAdminComponent
User : Administrator
     at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:969)
     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:343)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
     at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable$1$DoDispatchRequest.run(AsyncIncludeRunnable.java:377)
     at java.security.AccessController.doPrivileged(AccessController.java:241)
     at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable.run(AsyncIncludeRunnable.java:390)
     at com.sapportals.portal.prt.core.async.ThreadContextRunnable.run(ThreadContextRunnable.java:164)
     at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:729)
     at java.lang.Thread.run(Thread.java:758)
Caused by: java.lang.NoSuchMethodError: com/sap/security/core/util/imp/Util.patternMatch(Ljava/lang/String;Ljava/lang/String;Z)Z
     at com.sap.security.core.admin.util.checkEmail(util.java:110)
     at com.sap.security.core.admin.UserBean.checkFieldValidity(UserBean.java:695)
     at com.sap.security.core.admin.UserBean.checkUser(UserBean.java:591)
     at com.sap.security.core.admin.UserAdminLogic.performUserModify(UserAdminLogic.java:3226)
     at com.sap.security.core.admin.UserAdminLogic.executeRequest(UserAdminLogic.java:552)
     at com.sapportals.portal.prt.component.usermanagement.admin.UserAdminComponent.doContent(UserAdminComponent.java:71)
     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)
     ... 7 more

Runtime error - DBIF_RSQL_INVALID_RSQL, Exception - CX_SY_OPEN_SQL_DB

Hi,
Following code is working fine in Development system and in Production system I am getting a runtime error. Only difference I am finding is in r_lifnr value. In development system I have few lifnr and in Production system it's not so... am I getting error because of it? Is there any restriction to no. of items populated in a range? Or Basis person need to change any parameter? Enclosed the detail dump below the code...
Advance thanks.
Regards,
Balaji Viswanath.
Code:
SELECT bukrs
 lifnr
 augdt
 augbl
 zuonr
 gjahr
 belnr
 buzei
 waers
 dmbtr
 wrbtr
 zlsch
 shkzg
 blart
 gsber
 sgtxt
INTO TABLE t_bsak_tmp
FROM bsak CLIENT SPECIFIED
WHERE mandt = sy-mandt AND
 lifnr IN r_lifnr AND
 bukrs IN s_bukrs AND
 augdt IN s_augdt AND
 blart IN s_blart.
IF sy-subrc <> 0.
No data found for selection criteria
 MESSAGE i018.
 LEAVE LIST-PROCESSING.
ENDIF.
Dump:
Runtime Errors DBIF_RSQL_INVALID_RSQL
Exception CX_SY_OPEN_SQL_DB
 Occurred on 14.11.2005 at 14:35:22
Error in the module RSQL accessing the database interface.
What happened?
Error in ABAP application program.
The current ABAP program "/DS1/FI_CR_REPT_PGSR802_VEND_P" had to be terminated
because one of the
statements could not be executed.
This is probably due to an error in the ABAP program.
What can you do?
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.
Error analysis
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was
neither
caught nor passed along using a RAISING clause, in the procedure
"GET_CLRD_VEN_DATA" "(FORM)"
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
The SQL statement generated from the SAP Open SQL Statement violates a
restriction imposed by the database system used in R/3.
Possible errors:
o The maximum size of an SQL statement has been exceeded.
o The statement contains too many input variables.
o The space needed for the input data exceeds the available memory.
o ...
You can usually find details in the system log (SM21) and in the
developer trace of the work process (ST11).
If an error occurs the developer trace often informs you about the
current restrictions.
How to correct the error
The exception must either be prevented, caught within the procedure
"GET_CLRD_VEN_DATA"
"(FORM)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
The SAP Open SQL statement must be divided into several smaller units.
If the problem occurred due to the use of an excessively large table
in an IN itab construct, you can use the addition FOR ALL ENTRIES
instead.
When you use this addition, the statement is split into smaller units
according to the restrictions of the database system used.
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:
"DBIF_RSQL_INVALID_RSQL" CX_SY_OPEN_SQL_DBC
"/DS1/FI_CR_REPT_PGSR802_VEND_P" or "/DS1/FI_CR_REPT_PGSR802_VEND_P"
"GET_CLRD_VEN_DATA"
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem.
 To obtain this, select the "Print" function on the current screen.
2. A suitable hardcopy prinout of the system log.
 To obtain this, call the system log with Transaction SM21
 and select the "Print" function to print out the relevant
 part.
3. If the programs are your own programs or modified SAP programs,
 supply the source code.
 To do this, you can either use the "PRINT" command in the editor or
 print the programs using the report RSINCL00.
4. Details regarding the conditions under which the error occurred
 or which actions and input led to the error.
System environment
SAP Release.............. "620"
Application server....... "ztm1003"
Network address.......... "145.26.160.103"
Operating system......... "AIX"
Release.................. "5.3"
Hardware type............ "00C004DC4C00"
Character length......... 16 Bits
Pointer length........... 64 Bits
Work process number...... 6
Short dump setting....... "full"
Database server.......... "ztm1003"
Database type............ "ORACLE"
Database name............ "A94"
Database owner........... "SAPR3K"
Character set............ "C"
SAP kernel............... "640"
Created on............... "Aug 7 2005 20:44:35"
Created in............... "AIX 1 5 00538A4A4C00"
Database version......... "OCI_920 "
Patch level.............. "85"
Patch text............... " "
Supported environment....
Database................. "ORACLE 8.1.7.., ORACLE 9.2.0.., ORACLE
10.1.0.."
SAP database version..... "640"
Operating system......... "AIX 1 5, AIX 2 5, AIX 3 5"
User, transaction...
Client.............. 110
User................ "INBVI0"
Language key........ "E"
Transaction......... "SE38 "
Program............. "/DS1/FI_CR_REPT_PGSR802_VEND_P"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
The termination occurred in the ABAP program "/DS1/FI_CR_REPT_PGSR802_VEND_P"
in "GET_CLRD_VEN_DATA".
The main program was "/DS1/FI_CR_REPT_PGSR802_VEND_P ".
The termination occurred in line 503 of the source code of the (Include)
program "/DS1/FI_CR_REPT_PGSR802_VEND_P"
of the source code of program "/DS1/FI_CR_REPT_PGSR802_VEND_P" (when calling
the editor 5030).
Processing was terminated because the exception "CX_SY_OPEN_SQL_DB" occurred in
the
procedure "GET_CLRD_VEN_DATA" "(FORM)" but was not handled locally, not
declared in the
RAISING clause of the procedure.
The procedure is in the program "/DS1/FI_CR_REPT_PGSR802_VEND_P ". Its source
code starts in line 501
of the (Include) program "/DS1/FI_CR_REPT_PGSR802_VEND_P ".
Source code extract
004730 &----
004740 * get country names from t005t
004750 ----
004760 FORM get_country_names.
004770
004780 t_lfa1_land[] = t_lfa1[].
004790 SORT t_lfa1_land BY land1.
004800 DELETE ADJACENT DUPLICATES FROM t_lfa1_land COMPARING land1.
004810
004820 IF NOT t_lfa1_land[] IS INITIAL.
004830 SELECT land1
004840 landx
004850 INTO TABLE t_t005t
004860 FROM t005t
004870 FOR ALL ENTRIES IN t_lfa1_land
004880 WHERE spras = sy-langu AND
004890 land1 = t_lfa1_land-land1.
004900 REFRESH t_lfa1_land.
004910 SORT t_t005t BY land1.
004920 ELSE.
004930 MESSAGE i014 WITH 'No vendor data fetched'(001).
004940 ENDIF.
004950 ENDFORM. " get_country_names
004960 &----
004970 *& Form get_clrd_ven_data
004980 &----
004990 * Cleared vendor data
005000 ----
005010 FORM get_clrd_ven_data .
005020
> SELECT bukrs
005040 lifnr
005050 augdt
005060 augbl
005070 zuonr
005080 gjahr
005090 belnr
005100 buzei
005110 waers
005120 dmbtr
005130 wrbtr
005140 zlsch
005150 shkzg
005160 blart
005170 gsber
005180 sgtxt
005190 INTO TABLE t_bsak_tmp
005200 FROM bsak CLIENT SPECIFIED
005210 * the order of the fields are as in the secondary Index.
005220 WHERE mandt = sy-mandt AND
Contents of system fields
SY field contents..................... SY field contents.....................
SY-SUBRC 0 SY-INDEX 0
SY-TABIX 1 SY-DBCNT 59
SY-FDPOS 0 SY-LSIND 0
SY-PAGNO 0 SY-LINNO 1
SY-COLNO 1 SY-PFKEY
SY-UCOMM
SY-TITLE Vendor Payment Details for IRD
SY-MSGTY I SY-MSGID SF
SY-MSGNO 616 SY-MSGV1 /DS1/FI_CR_REPT_PGSR802_VEND_P
SY-MSGV2 RE SY-MSGV3 EN
SY-MSGV4
Active calls / events
No.... Type........ Name..........................
 Program
 Include Line
 Class
 2 FORM GET_CLRD_VEN_DATA
 /DS1/FI_CR_REPT_PGSR802_VEND_P
 /DS1/FI_CR_REPT_PGSR802_VEND_P 503
 1 EVENT START-OF-SELECTION
 /DS1/FI_CR_REPT_PGSR802_VEND_P
 /DS1/FI_CR_REPT_PGSR802_VEND_P 135

Hi Balaji,
Here is what the dump said and my answers are right below them.
Possible errors:
o The maximum size of an SQL statement has been exceeded.
This may not be the reason in your case. This usually happens when you use the option FOR ALL ENTRIES
o The statement contains too many input variables.
Most likely this is your issue. I think your r_lifnr is filled with all the vendors in your system and filled as single values. In that case you may be exceeding a limit set on the system. Instead of trying to remove this setting, what I would suggest is to do the following.
Define a select-option for LIFNR on your selection screen. This way users can have the flexibility of specifying certain vendors. If they don't enter anything, it is still ok. Don't fill it with single values.
Use this select-option in your select statement. After the select statement, do a delete from itab where the vendors are not in your r_lifnr as below.
DELETE t_bsak_tmp WHERE NOT lifnr IN r_lifnr.
Also, avoid using client. You don't need that unless you really want to select from a different client other than your logon client. Your select statement is using logon client anyway, so you don't need to specify that.
o The space needed for the input data exceeds the available memory.
If the above changes are made and the problem is still there, then this is the next thing to look at.
Srinivas

DAC-104/JBO-110 Runtime Error.

Similar Messages

Maybe you are looking for