After patching Portal 7.31 SP9 - SP13, CM BW reports fail

Our links to the BI credit reports (like Early Warning Risk) stopped working after patching the NW Portal 7.31 from SP9 to SP13. No other changes were made, and the reports worked prior to the patching.
The child window for the report opens, but then comes back with error:
com.sap.portal.appintegrator.sap.BWReport::BWReport/AskForReport
And then it asks for a BEx Web Application Query String.
I would put this in the portal/netweaver forum, but this error seems strictly related to the CM delivered content (we are on the most current 1.41 BP). We've validated that that the SSO tickets from portal to back end ERP and BI are working properly. Has anyone had this kind of issue after a patch (while staying on same portal release)? We didn't make any changes/patches to the back end ERP and BI systems either.

Yes we have experienced the same thing. We upgraded from 30 to 353 and now we are getting the BW logon prompt. It is very frustrating. I have been searching these message boards for help.
Brien

Similar Messages

Error while running isupplier portal from jdev after patches

latest POS rollup patch was applied and since then i get an error on local machine while running portal pages, need not mention that my substitution has also broken after patches.
On server :
login as isupplier > click on any PO either on home page or any order via Orders> ponumber
On local machine : I get below error when I click on any po.
I have deleted all teh old classes and ftped the whole apps directory on my local machine, but i still get this error.
Also noted that the functionality of changing PO, etc works fine, but this error gets printed in jdev console.
can someone give me some clue ?
thanks
java.lang.ClassCastException
     at oracle.apps.pos.isp.server.PosServerUtil.checkSecurePO(PosServerUtil.java:85)
     at oracle.apps.pos.changeorder.webui.ViewOrderPGCO.processRequest(ViewOrderPGCO.java:1012)
     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequest(OAWebBeanHelper.java:587)
     at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.processRequest(OAWebBeanContainerHelper.java:247)
     at oracle.apps.fnd.framework.webui.beans.layout.OAStackLayoutBean.processRequest(OAStackLayoutBean.java:350)
     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequestChildren(OAWebBeanHelper.java:959)
     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequestChildren(OAWebBeanHelper.java:926)
     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequest(OAWebBeanHelper.java:646)
     at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.processRequest(OAWebBeanContainerHelper.java:247)
     at oracle.apps.fnd.framework.webui.beans.layout.OAStackLayoutBean.processRequest(OAStackLayoutBean.java:350)
     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequestChildren(OAWebBeanHelper.java:959)
     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequestChildren(OAWebBeanHelper.java:926)
     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequest(OAWebBeanHelper.java:646)
     at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.processRequest(OAWebBeanContainerHelper.java:247)
     at oracle.apps.fnd.framework.webui.OAPageLayoutHelper.processRequest(OAPageLayoutHelper.java:1136)
     at oracle.apps.fnd.framework.webui.beans.layout.OAPageLayoutBean.processRequest(OAPageLayoutBean.java:1569)
     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequestChildren(OAWebBeanHelper.java:959)
     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequestChildren(OAWebBeanHelper.java:926)
     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequest(OAWebBeanHelper.java:646)
     at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.processRequest(OAWebBeanContainerHelper.java:247)
     at oracle.apps.fnd.framework.webui.beans.form.OAFormBean.processRequest(OAFormBean.java:385)
     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequestChildren(OAWebBeanHelper.java:959)
     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequestChildren(OAWebBeanHelper.java:926)
     at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequest(OAWebBeanHelper.java:646)
     at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.processRequest(OAWebBeanContainerHelper.java:247)
     at oracle.apps.fnd.framework.webui.beans.OABodyBean.processRequest(OABodyBean.java:353)
     at oracle.apps.fnd.framework.webui.OAPageBean.processRequest(OAPageBean.java:2335)
     at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:1734)
     at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:508)
     at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(OAPageBean.java:429)
     at OA.jspService(OA.jsp:34)
     at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:56)
     at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:317)
     at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:465)
     at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:379)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:727)
     at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:306)
     at com.evermind.server.http.ServletRequestDispatcher.forward(ServletRequestDispatcher.java:209)
     at com.evermind.server.http.GetParametersRequestDispatcher.forward(GetParametersRequestDispatcher.java:189)
     at com.evermind.server.http.EvermindPageContext.forward(EvermindPageContext.java:199)
     at OA.jspService(OA.jsp:39)
     at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:56)
     at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:317)
     at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:465)
     at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:379)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:727)
     at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:306)
     at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:767)
     at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:259)
     at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:106)
     at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:803)
     at java.lang.Thread.run(Thread.java:534)
Edited by: OAF-dev on Apr 19, 2010 1:39 PM

I cross checked all the versions and I have the correct one installed....
it was working before the patch . Patch is only the upgrade of POS. I got all teh class files again on my local machine , but this error comees up in jdev console. and rest all works fine. I have no clue why.

"ORA-12222 TNS no such protocol adapter" When running Forms after installing Portal

We have a Forms 6i (web) application running on 9iAS. This worked fine. But after installing Portal on the same 9iAS, we got the following error when starting the WebForms application:
ORA-12222 TNS no such protocol adapter
Who knows a solution?
Configuration
9IAS v1.0.2.2
8.1.7
Form 6i Patch 10
Windows NT
Best regards,
Harm van Zoest

This is s SQLNET error.
You can search for it on OTN using the search button.
IT usually means that the tnsnames.ora file was changed. Or that you are now using another tnsnames.ora.

AS Java applications not starting after patching from 2004s SPS10 to SPS11

Hi folks,
after patching our NetWeaver 2004s from SPS10 to SPS11 and the Kernel from 7.00.83.0 to 7.00.95.0, the applications on the AS Java do not start up automatically any more.
Under the following URLs, the same error is shown:
http://<fully qualified host name>:51000/
http://<fully qualified host name>:51000/nwa
http://<fully qualified host name>:51000/sap/monitoring/SystemInfo
http://<fully qualified host name>:51000/useradmin/
http://<fully qualified host name>:51000/wsnavigator
http://<fully qualified host name>:51000/uddiclient
503 Service Unavailable
SAP J2EE Engine/7.00
Application stopped.
Details: You have requested an application that is currently stopped
http://<fully qualified host name>:51000/webdynpro/welcome/Welcome.jsp
itself works, the two links Content Administrator and Web Dynpro Console both lead to the same 503 error described above
On http://<fully qualified host name>:51000/irj, the error message is different:
com.sap.engine.services.deploy.container.ApplicationInManualStartUpException:
Application sap.com/com.sap.portal.fpn.accessservice cannot be started because is in MANUAL start-up mode..
Exception id: 09:33_09/05/07_0003_102709250
See the details for the exception ID in the log file
In std_server0.out we have the following entries, right after the list of all services that were started:
ServiceManager started for 39904 ms.
Framework started for 46720 ms.
SAP J2EE Engine Version 7.00 PatchLevel is running!
PatchLevel January 31, 2007 18:37 GMT
May 9, 2007 9:40:19 AM com.sap.portal.prt.sapj2ee.error [SAPEngine_Application_Thread[impl:3]_3] Fatal:
The last line with com.sap.portal.prt.sapj2ee.error is listed another 131 times, and there is also the following message:
### Excluding compile: com.sapportals.portal.prt.jndisupport.util.AbstractHierarchicalContext::lookup
We can connect to the system using Visual Administrator. Under Server->Services->Deploy, most applications are not running. It is possible to start a few applications manually, others however do not start showing different exceptions.
We have AS ABAP and AS Java installed, as well as BI, DI, EP and EPC. AS ABAP seems to be running fine.
We have also noticed the following deviations in JSPM:
BC_FES_IGS is Release 7.00 SP Level 7.0
EP_BUILDT is Release 7.00 SP Level 10.0
SAP_BUILDT is Release 7.00 SP Level 0.0
All other components except for the Kernel are Release 7.00 SP Level 11.0 or 11.2
What could be wrong, and what can we do to solve it?
Best regards,
Robert Schulte

Thanks for your response, usha rani
1. We already tried that, unfortunately, it does not help
2. We checked the kernel version thoroughly after you suggested it, everything seems to be fine. We had a Unicode kernel before, and we still have one.
3. safemode is already set to NO
4. J2EE's default.trace is full of exceptions, but none of them is pointing me into a helpful direction.
Perhaps the exceptions mean more to someone else:
java.lang.Exception: Exception loading and instanciating sub-manager:
com.sap.caf.km.repositorymanager.CAFSecurityManager
(java.lang.ClassNotFoundException: com.sap.caf.km.repositorymanager.CAFSecurityManager)
com.sapportals.wcm.repository.runtime.CmConfigurationProvider#
sap.com/irj#com.sapportals.wcm.repository.runtime.CmConfigurationProvider.Component
<SetRoomIdForDiscussionObjects> will not be available.
Failed to load class
<com.sap.netweaver.coll.room.impl.filter.DiscussionSetRoomIdPropertyFilterManager>
#J2EE_GUEST#0####1e820b50fe4111db8e780013724175b4#SAPEngine_Application_Thread[impl:3]_22
##0#0#Error##Plain###
java.lang.ClassNotFoundException:
com.sap.netweaver.coll.room.impl.filter.DiscussionSetRoomIdPropertyFilterManager
com.sap.portal.prt.runtime.broker#sap.com/irj#
com.sap.portal.prt.runtime.broker#J2EE_GUEST#0####
1e820b50fe4111db8e780013724175b4#SAPEngine_Application_Thread[impl:3]_22##0#0#
Error#1#/System/Server#Java###
[PortalServiceItem.startServices] service initialisation failed:
tc.eu.odi.conn.uwl|OdiBridgeService
[EXCEPTION]
{0}#1#com.sapportals.portal.prt.core.broker.PortalServiceInstantiationException:
Could not instantiate implementation class com.sap.tc.eu.odi.conn.uwl.OdiBridgeService
of Portal Service tc.eu.odi.conn.uwl|OdiBridgeService because: could not load the service
com.sap.engine.services.deploy.container.ApplicationInManualStartUpException:
Application sap.com/com.sap.portal.fpn.accessservice cannot be started
because is in MANUAL start-up mode.
There are many more entries in default.trace.

Error after patch EP6.0 SP3- EP6.0 SP4(patch4)- WAS6.40SP6

We have WAS 6.40 SP 6.0 and EP 6.0 SP3 on HP-Unix 11i 64-bit.
I have tried to patch the portal twice to SP4 and after patching I got
twice the same problem.
The patch application - the exact patch is EP 6.0 SP4 Patch4 is
successful. There are no errors in the installation logs, etc.
But when I try to login to the portal url I get this error message:
Portal Runtime Error
An exception occurred while processing a request for :
iView : N/A
Component Name : N/A
Could not find portal application com.sap.portal.ivs.api_iview.
Exception id: 02:21_05/08/04_0001_1516650
See the details for the exception ID in the log file
The error part of the portal log file is attached. The WAS is running
perfectly, no other errors or issues. The heap memory is set as per the
OSS 723909. I wonder if I have to add the 32-bit compatible UNIX shared
memory parameter settings as per OSS 497427, but I do not think it is
related the issue.
Please, advise.
Vladimir
Portal Log:
Aug 5, 2004 2:18:19 PM # SAPEngine_Applica... Info Loading
application com.sap.portal.yahoo #
Aug 5, 2004 2:18:19 PM # SAPEngine_Applica... Fatal Operation
failed - application: com.sap.portal.ivs.iviewservice
com.sapportals.portal.prt.runtime.PortalRuntimeException:
[PortalApplicationItem.__prepareClassLoaderAndDependencies]:
com.sap.portal.ivs.iviewservice
at
com.sapportals.portal.prt.core.broker.PortalApplicationItem.__prepareCla
ssLoaderAndDependencies(PortalApplicationItem.java:361)
at
com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare
(PortalApplicationItem.java:207)
at
com.sapportals.portal.prt.core.broker.PortalApplicationItem.getCoreLoade
r(PortalApplicationItem.java:276)
at
com.sapportals.portal.prt.core.broker.PortalApplicationItem.__initJNDISu
pport(PortalApplicationItem.java:1780)
at
com.sapportals.portal.prt.core.broker.PortalApplicationItem.__initJNDISu
pport(PortalApplicationItem.java:1746)
at
com.sapportals.portal.prt.core.broker.PortalApplicationItem.initJNDISupp
ort(PortalApplicationItem.java:1730)
at
com.sapportals.portal.prt.core.broker.PortalAppBroker.preparePortalAppli
cations(PortalAppBroker.java:1306)
at com.sapportals.portal.prt.core.broker.PortalAppBroker.start
(PortalAppBroker.java:1429)
at
com.sapportals.portal.prt.core.broker.PortalAppBroker.startNonCoreApplic
ations(PortalAppBroker.java:1389)
at com.sapportals.portal.prt.runtime.Portal.init
(Portal.java:359)
at
com.sapportals.portal.prt.core.PortalCoreInitializer.coreInit
(PortalCoreInitializer.java:54)
at
com.sapportals.portal.prt.dispatcher.PortalInitializer.<init>
(PortalInitializer.java:129)
at
com.sapportals.portal.prt.dispatcher.Dispatcher$doSetupPortalInitializer
.run(Dispatcher.java:156)
at java.security.AccessController.doPrivileged(Native Method)
at
com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher
(Dispatcher.java:354)
at com.sapportals.portal.prt.dispatcher.Dispatcher.access$000
(Dispatcher.java:40)
at
com.sapportals.portal.prt.dispatcher.Dispatcher$InitRunner.run
(Dispatcher.java:109)
at com.sapportals.portal.prt.dispatcher.Dispatcher.init
(Dispatcher.java:387)
at
com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponent
s.addServlet(WebComponents.java:130)
at
com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadI
nitializer.loadServlets(ApplicationThreadInitializer.java:376)
at
com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadI
nitializer.run(ApplicationThreadInitializer.java:110)
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:94)
at com.sap.engine.core.thread.impl3.SingleThread.run
(SingleThread.java:144)
Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException:
[PortalApplicationItem.__prepareClassLoaderAndDependencies]:
com.sap.portal.ivs.api_iview
at
com.sapportals.portal.prt.core.broker.PortalApplicationItem.__prepareCla
ssLoaderAndDependencies(PortalApplicationItem.java:361)
at
com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare
(PortalApplicationItem.java:207)
at
com.sapportals.portal.prt.core.broker.PortalApplicationItem.__prepareCla
ssLoaderAndDependencies(PortalApplicationItem.java:352)
... 24 more
Caused by:
com.sapportals.portal.prt.core.broker.PortalApplicationNotFoundException
: Could not find portal application com.sap.portal.ivs.api_iview
at
com.sapportals.portal.prt.core.broker.PortalApplicationItem.refresh
(PortalApplicationItem.java:1093)
at
com.sapportals.portal.prt.core.broker.PortalApplicationItem.__prepareCla
ssLoaderAndDependencies(PortalApplicationItem.java:326)
... 26 more
Follow errors of other applications like
com.sap.portal.ivs.systemlandscapeservice, which are probably dependent
on the com.sap.portal.ivs.iviewservice.

We needed exactly the SP Stack 3 specification - WAS 6.40 SP6 and EP 6.0 SP4, so I could not go to higher SP on both WAS and EP.
I resolved the issue by applying all EP6.0 SP4 patches sequentially. SAP claims that these patches are cumulative and you can directly install the latest available patch, but it did not work in our case.
I was suspicious at the beginning, because the files size of the first patch is much bigger that patch 4, but the installation did not complained:
08/03/2004 06:13p 32,672,495 EP6PORTAL04P_4-20000394.SAR
08/03/2004 06:03p 50,455,982 EP6PORTAL04_0-20000394.SAR
Regards,
Vladimir

Null Exception in Family Iview after Patch Upgrade

Hello
We have SAP XSS installed on our production portal.
following was the composition.
SAP_ESS 603 SP3
SAP_MSS 600 SP16
SAPPCUI_GP 603 SP3
recently we upgraded patch level to
SAP_ESS 603 SP7 (1000.603.0.7.4.20110124060804)
SAP_MSS 600 SP18 (1000.600.0.18.0.20100830054638)
SAPPCUI_GP 603 SP7 (1000.603.0.7.0.20100914080506)
as per the link [https://wiki.sdn.sap.com/wiki/display/ERPHCM/HOWTOGETRIDOFSPSTACKMISMATCHISSUES] and SAP note 1521297
Backend patches remain the same viz
EA-HR Release: 604 ,level : 011
Now when we try to test the Personal Information Iview it gives us the following error
com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: Access via NULL object reference not possible., error key: RFC_ERROR_SYSTEM_FAILURE
Note: We have already implemented note no 1018036 which reports the above issue.Jcos are working fine , SSo is properly established and User remains valid.
Thanks
Surender Dahiya

Hi,
The logs from ST22 as as follows:
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_REF_IS_INITIAL', was not
caught in
procedure "HRXSS_PER_CLEANUP" "(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:
You attempted to use a 'NULL' object reference (points to 'nothing')
access a component.
An object reference must point to an object (an instance of a class)
before it can be used to access components.
Either the reference was never set or it was set to 'NULL' using the
CLEAR statement.
Other ESS applications are working fine.Issue is in Family application.Server is also restarted after patch upgradation.
Please suggest.
Thanks,
Surendra

Problems with AIF after upgrading Portal

Hi,
After updating Portal from NW04 SPS14 to NW04SPS21, AIF Projects stopped working with the following message:
com.adobe.ProcessingError: Invalid working PDF filename detected during creation of a PDF Manipulation Module.
Please ensure that <Render><Output><IsPDF>1</IsPDF></Output></Render> is set if post processing a rendered PDF file.
I already tried to reload and rebuild projects with NWDS SPS21, without success.
Any hints?
Thanks & Regards,
John

Hi,
I think u have to apply some patch for the AIF to work.
Regards
Mustafa

Big Button become Small Button after patching system

Hello experts,
we have a produktiv running WD ABAP application, which runs on computers with touchscreens.
Because of that we developed the applicatin with big buttons (standard Ui element button with a big image) so that our user can hit it with their finger. now after patching our systems the buttons are small again and the big image in the button is cut.
Does anybody know how we can increase the size of the buttons?
Regards

Hi,
I presume you have upgraded your system from SP<=13 to SP>=14. We have a same problem after we have patched our system.
There was a problem with the alignment of the images when large images were used. Therefore SAP rectified the same in rendering corrections from SP13 which were available in SP14. As a result of which button size remains small even if you use large image.
You can not use theme editor to change the button sizes or image sizes. The only option is to raise an SAP ticket. SAP is already working on the issue as I had raised a ticket for the same. Hope to have a fix very soon. But I suggest you also raise an OSS ticket.
Regards
Rohit Chowdhary

JCo missing after patching the system

Hi
We have gone for pataching the Portal and ESS. We see that after patching there is only Selfservicgenerics and HumanResources Jco appearing. All other JCo,s are missing from the system. Is this normal behavior ??
How do we get other JCo appear asthey were already configured before.

Hi Purav,
I think yuu need me create manually as per your required JCO for ESS/MSS applciation.
Try to check in the SLD if all earlier JCO's available
Thanks
Arun

Function module "GM_DOCUMENT_REVERSE" not found. after Patch Update

Hi Abapers/Basis
After patch update i am not able to do FBCJ reversal entry getting below error message.
Runtime Errors         CALL_FUNCTION_NOT_FOUND
Exception              CX_SY_DYN_CALL_ILLEGAL_FUNC
Date and Time          25.05.2011 14:43:26
Short text
     Function module "GM_DOCUMENT_REVERSE" not found.
What happened?
     The function module "GM_DOCUMENT_REVERSE" is called,
     but cannot be found in the library.
     Error in the ABAP Application Program
     The current ABAP program "SAPLRWCL" 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
Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_DYN_CALL_ILLEGAL_FUNC', was
     not caught in
    procedure "CALL_DISPATCHER_STORNO_R" "(FORM)", 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:
    The program "SAPLRWCL" contains the CALL FUNCTION statement.
    The name of the function module to be called is "GM_DOCUMENT_REVERSE".
    No function module exists with the name "GM_DOCUMENT_REVERSE".
    All function modules are listed in the Function Library (SE37).
    Possible reasons:
    a) Wrong name specified. Pay particular attention to
       upper/lower case and underscores ("_").
       or
    b) Transport error
    c) In the case of an enqueue/dequeue module,
       the lock object may not have been activated
       (ABAP/4 Dictionary).
How to correct the error
    Check the last transports to the SAP System.
    Is the program "SAPLRWCL" currently being changed?
    If an enqueue/dequeue module is involved, is the activation
    of the lock object missing in the ABAP/4 Dictionary?
    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_FUNCTION_NOT_FOUND" "CX_SY_DYN_CALL_ILLEGAL_FUNC"
    "SAPLRWCL" or "LRWCLF10"
    "CALL_DISPATCHER_STORNO_R"
    Function modules with names similar to "GM_DOCUMENT_REVERSE":
    GM_DOCUMENT_CLOSE
    GM_DOCUMENT_RECORD
    GM_DOCUMENT_DELETE
    GM_DOCUMENT_POST
    GM_DOCUMENT_CHECK
    G_DOCUMENT_RECORD
    GJ_DOCUMENT_RECORD
    GM_DOCUMENT_PROJECT
    GET_DOCUMENTS
    GM_DOCUMENT_DISPLAY
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
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".
Moderator message: please don't just dump your dumps, search for SAP notes or open a call with SAP instead.
Edited by: Thomas Zloch on May 25, 2011 2:16 PM

Hi Karthik,
Thank you for ur reply.
I did not implement any user exit/ badi. Dump is saying that my smarform function module does not exist in the se37 library.
I have excuted my form through se38, that time is working fine. When i tried through output type it is going to dump.
Regards,
Kusuma.

Authorization problems after patch 6 upgrade and re-install

Hello everybody.
I had a perfect working Visual Composer installation.
After patching it, I got an 401 message, stating that I do not have authorization to view this page:
HTTP Error 401.1 - Unauthorized: Access is denied due to invalid credentials.
Uninstalling and reinstalling didn't bring me much further. It seems to be an Internet Explorer and/or IIS 6.0 related problem.
Of course I followed the very valuable note 804996, but the problem remains...
Can anyone help me out?
Thanx.

Hi all.
I resolved my own problem.
Additional to the permission settings as they are explained in note 804996, you must add the Directory Security - Authentication & Access Control, set to Integrated Windows Authentication.
Otherwise Windows NTFS security will block you.
Gr.,
Marc.

Sales office data missing after patching in CRM

Hi,
We have CRM 4.0 for internet sales.
Recently, we patched our Development and QA CRM systems from SAPKU40009 to
SAPKU40016.
Immediately after the patching, we see that the Sales office information in the BP (Sales area- organization tab) is missing. We have only one Sales org and Dist channel with division not active. All the sales office belong to the same sales org. Nothing has changed w.r.t org model before and after patching and all the org units are checked for determintation.
Everything was working before the patching. Just after patching, we find the sales office information blanked out in the BP and as well as the drop down list is empty.
I can see the sales office table entries for all the BPs in CRMM_BUT_SET0140. But when ichange the BP data (for some other field) and save, the table entries get deleted as i am not able to assign the sales office any more.
We have not buffered the attributes. I tried that also and ran the report HRBCI_ATTRIBUTES_BUFFER_UPDATE, but it is of no use.
Can somebody help?
Thanks
Shankar

Hi ,
What you can do is,
Create a request for a material whose Sales Area data is missing in
CRM , and perform the request load in transaction:R3AR4.
And please check whether sales area data flows to CRM.
Put a filter in txn:R3AC1, to download single material or material
range.And before performing an initial load in txn:R3AS,please make
sure that sales area data is missing in CRM.Now, perform the initial
load in txn:R3AS.And please check whether sales area data flows to
CRM.
Check the filter settings in transaction R3AC1 for
object MATERIAL and please make sure that it would bring down all
the expected materials from R/3 along with the sales area data. I guess there is some
filter setting which is blocking it.
Please check the entries you have maintained in table MVKE - the entries
for the sales data maintained here must match with the ones maintained in the
filters.
thanks & regards,
Krishnen
Edited by: Krishnen Subramanian on Aug 9, 2011 8:47 AM

Startup after patching (9654983) ORA-32004

I patched a nearly identical system before this one with no issues however after patching this one
on attempting to startup I get :
ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance.
ORA-24324: service handle not initialized
ORA-24323: value not allowed
ORA-01092: ORACLE instance terminated. Disconnection forced.
What gives?
Thanks for any and all help in advance,
Brian

ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance.
ORA-24324: service handle not initialized
ORA-24323: value not allowed
ORA-01092: ORACLE instance terminated. Disconnection forced.
What gives? Check the alert.log to identify the obsolete parameter and remove it.
OR
Check V$OBSOLETE_PARAMETER to see the matching on and remove it.
Then,startup the database.
-Anantha

Behaviour change of synchronous reply after patching to 10.1.3.4

Hi people ,
i have a process like this:
[http://www.jettmedia.com/images/630_syncReply10134Test.jpg]
Normally in 10.1.3.1 , 10.1.3.3.x ; the process will continue after a partial reply, and any fault uncatched in the process would terminate the flow. And any changes to the outputvariable wont change the process response.
But after patching to 10.1.3.4 im having a different behaviour on synchronous process replys ,
The process continues and any uncatched fault AFTER A REPLY its raised to the client, and any change to the outputvariable AFTER A REPLY its changed to the process response .
The worst thing its that is not clear when the response its really sent to the client , ( if i put a wait activity , after the reply, with 1 minute , works as was expected, like in 10.1.3.3 ... )
I read this new features list from oracle
http://www.oracle.com/technology/tech/soa/cab/oraclesoacab-webinar-04-22-08bpel_10_1_3_4_update.pdf
It says that "Faults in a transient process go to the client" , correcting an old problem of lost instances..
I cant find any other documentation explaining this new beahaviour but for my organization its a huge problem afecting , many production processes, on the patched servers. Because i raised faults to leave the instances marked as faulted on the console as a normal procedure on the flows , but now , if that throw its close enough after a reply(with a unknow criteria or number of activities) its raised to the client :S
Thanks for any help , by now the workaround to keep the same behaviour its: WAIT after every reply :S :S !!
Greetings
Dam

Yes its a fire and forget pattern, thanks for the suggestion, il. try it ...
but its difficult to refactor several flows just for patching , you have any idea if this change after upgrade to 10.1.3.4 its normal ? this is an expected beahaviour ?
Thank you very much again

Problem with national language after patching

I have BEx Analyser based on Excel 2007. After patching with 801 (SAP NetWeaver 7.0 Support Package BI Frontend Add-on 7.x SP's for SAP GUI 7.10) got problem with national symbols input.
Please any ideas...
Thanks,
Olga

It's best to post this in a SQL Server forum. ConfigMgr is simply a delivery mechanism for the patch and really has nothing to do with what the patch actually does.
Jason | http://blog.configmgrftw.com | @jasonsandys

After patching Portal 7.31 SP9 - SP13, CM BW reports fail

Similar Messages

Maybe you are looking for