Portal Exception

[Former Member]

Hello,

We are implementing MSS on EP7.0 and when a manager is trying to Approve a Travel Request in the UWL , he gets the following :

Portal runtime error.

An exception occurred while processing your request. Send the exception ID to your portal administrator.

Exception ID: 02:19_14/03/11_0022_4406950

Refer to the log file for details about this exception.

When I looked at the NWA Logs , saw the following error:

02:15_14/03/11_0021_4406950

[EXCEPTION]

com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Unable to parse template '<System.Access.WAS.protocol>://<System.Access.WAS.hostname>/sap/bc/webdynpro/<WebDynproNamespace>/<WebDynproApplication>/;sap-ext-sid=<ESID[url_ENCODE]>?sap-ep-iviewhandle=007<ESID[HASH]>&sap-wd-configId=<WebDynproConfiguration>&sap-ep-iviewid=<IView.ShortID>&sap-ep-pcdunit=<IView.PCDUnit.ShortID>&sap-client=<System.client>&sap-language=<Request.Language>&sap-accessibility=<User.Accessibility[SAP_BOOL]>&sap-rtl=<LAF.RightToLeft[SAP_BOOL]>&sap-ep-version=<Portal.Version[url_ENCODE]>&sap-wd-tstamp=<$TimeStamp>&<FPNInfo[IF_false PROCESS_RECURSIVE]>&sap-explanation=<User.Explanation[SAP_BOOL]>&<StylesheetIntegration[IF_true PROCESS_RECURSIVE]>&<Authentication>&<DynamicParameter[PARAMETER_MAPPING PROCESS_RECURSIVE]>&<ForwardParameters[QUERYSTRING]>&<ApplicationParameter[PROCESS_RECURSIVE]>'; the problem occured at position 310. Cannot process expression <System.client> because Invalid System Attribute:

System: 'SAP_LocalSystem',

Attribute: 'client'.

at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContentPass(AbstractIntegratorComponent.java:125)

at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContent(AbstractIntegratorComponent.java:98)

at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)

at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)

at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)

at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)

at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)

at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)

at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)

at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)

at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)

at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)

at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)

at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:235)

at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:541)

at java.security.AccessController.doPrivileged(AccessController.java:246)

at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:430)

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:1060)

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)

Please help.

Any help would be highly appreciated.

[Former Member · Accepted solution]

Can you enable the UWL trace information and check what object is called on click of this workitem. Is it wdp java /abap/ or a portal iview/page. If you know the workflow task id of travel approval w/f then same information can retrieved from transaction swfvisu.

Looks like approval application/iview is looking for a system defined in portal with alias SAP_LocalSystem whose attribute client is missing. Depending on what is getting called from uwl, this may be a misconfiguration issue or an error in standard application or even a permission issue.

cheers~

avadh

[Former Member · Accepted solution]

Avadh,

How can I enable the UWL Trace? I checked in the XML File of the UWL that it's a Webdynpro ABAP Application being called as there is an Action Tag as below:

<Action name="com.sap.pct.erp.mss.tra.action.DisplayExpenseForm" groupAction="" handler="SAPWebDynproABAPLauncher" referenceBundle="com.sap.pct.erp.mss.tra.DisplayForm" returnToDetailViewAllowed="yes" launchInNewWindow="yes" launchNewWindowFeatures="toolbar=no,menubar=no">

<Properties>

<Property name="WebDynproApplication" value="FITV_TRIP_FORM"/>

<Property name="SAP_FITV_TRIPCMP" value=""/>

<Property name="SAP_FITV_TRIPNO" value="${item.TripNumber}"/>

<Property name="WebDynproNamespace" value="sap"/>

<Property name="display_order_priority" value="10"/>

<Property name="SAP_FITV_PERSNO" value="${item.EmployeeNumber}"/>

</Properties>

</Action>

And there is no corresponding entry in the Transaction SWFVISU and no Task associated.

Pls help.

[Former Member · Accepted solution]

To enable uwl trace, go to UWL administration screen in System Administration, open the tray 'Optional universal worklist configuration' and set the option 'Display support information' to true. Alongwith action types, didn't you get property like 'Itemtypes'?

Since its wdp-abap app, check the system settings again. First go to UWL-Administration in system admin and select the 'system alias' you are using and click 'edit'. There you'll see a property name 'Webdynpro Launch System'. This is the system alias which application will use. You need to recheck settings of this system.

You can also overwrite this alias by providing correct alias in property fields of xml. Probably a property like

<Property name="SYSTEM_ALIAS" value="YOUR_ECC_SYSTEM_ALIAS_NAME"/>

added to this action will make sure your wdp-abap connect to correct system.

cheers~

avadh

[Former Member · Accepted solution]

Thanks again.

I enabled the UWL Trace at the place you mentioned and then clicked on the Workitem in the Inbox, now where do I check the actual Trace.?

Also I changed the Property tag as:

<Property name="System" value="MY_ECC_SYSTEM_ALIAS_NAME"/>

Now I get the following dump on clicking the workitem:

The following error text was processed in system R3Q : Value null of URL parameter SAP_FITV_PERSNO has the wrong type

The error occurred on application server <Host Name>_R3Q_00 and in work process 1 .

The termination type was: RABAX_STATE

The ABAP call hierarchy was:

Method: GET_REQUEST_INPLUG_PARAMETERS of program CL_WDR_CLIENT_APPLICATION=====CP

Method: INIT of program CL_WDR_CLIENT_APPLICATION=====CP

Method: IF_WDR_RUNTIME~CREATE of program CL_WDR_MAIN_TASK==============CP

Method: HANDLE_REQUEST of program CL_WDR_CLIENT_ABSTRACT_HTTP===CP

Method: IF_HTTP_EXTENSION~HANDLE_REQUEST of program CL_WDR_MAIN_TASK==============CP

Method: EXECUTE_REQUEST_FROM_MEMORY of program CL_HTTP_SERVER================CP

Function: HTTP_DISPATCH_REQUEST of program SAPLHTTP_RUNTIME

Module: %_HTTP_START of program SAPMHTTP

Pls help.

Edited by: SAPEPDeveloper on Mar 15, 2011 8:33 PM

[Former Member · Accepted solution]

After enabling support info, go back to uwl iview as an end user. Select the particular workflow item(no need of click, just select the row) scroll below the uwl table, you should get detailed info for the workitem i.e. workflow task id, action type associated etc. Paste the info you get from there.

Error you are getting is because abap app is reading this parameter from url which is null. Is uwl configuration default in your landscape or some custom settings applied for trip approval workitem?

cheers~

avadh

[Former Member · Accepted solution]

Thanks , I was to check the info.

Yes, there are custom attributes in the XML File as below:

<CustomAttributes>

<CustomAttributeSource id="WEBFLOW_CONTAINER" objectIdHolder="externalId" objectType="WebflowContainer" cacheValidity="final">

<Attribute name="TripNumber" type="string" displayName="Trip Number"/>

<Attribute name="EmployeeNumber" type="string" displayName="Employee Number"/>

</CustomAttributeSource>

</CustomAttributes>

Is that what you mean by Custom Settings?

[Former Member · Accepted solution]

I meant are the attributes related to this workitem all standard and untouched or some changes done by developer/administrator.

Paste the info you get in uwl support info.

cheers~

avadh

[Former Member · Accepted solution]

Here's the Support Info.:

Item May Be Outdated:

Item Type Configuration Name: com.sap.pct.erp.mss.tra123

Item Type: uwl.task.webflow.decision.TS20000118

External Item Type: TS20000118

Item Type: Associated View: com.sap.pct.erp.mss.tra.view.RequestApprovalView

Internal Item ID: 62

External Item ID: 000000387116

Application Context:

System ID: SAP_ECC_Financials

Connector: WebFlowConnector

Execution URL:

Supported Attributes for this Item

Attribute ID Display Text

subject Subject

isEscalated Escalated

creatorId From

createdDate Sent

priority Priority

Rowof 15

Supported Actions for this Item

Action ID Display Text Handler

GroupAction Please approve travel request<Userid> created by UserDecisionHandler

addMemo Add Memo SAPWebDynproLauncher

cancelSubprocess Cancel Sub-Processes UWLActionHandler

com.sap.pct.erp.mss.tra.action.DisplayRequestForm Display Form SAPWebDynproABAPLauncher

com.sap.pct.erp.mss.tra.action.approver.ApproveRequest Approve UserDecisionHandler

Thanks

[Former Member · Accepted solution]

can you check sapnote 890314 fix for "Generic iViews throws exceptions". Is it applicable to your landscape.

cheers~

avadh

[Former Member · Accepted solution]

Hi,

Did you solve your problem? Could you share how? Could you use the display form button?

Thanks

[Former Member · Accepted solution]

Hi,

What happens when you use:

<Property name="System" value="SAP_LocalSystem"/>

if the abap webdynpro resides on the same system? Please ensure you are also modifying the xml file in the correct place.

Beth Maben

EP - Senior Support Consultant

AGS Primary Support, Business Suite & Technology

• Please see the UWL Wiki @

http://www.sdn.sap.com/irj/scn/wiki?path=/display/bpx/uwl+faq ***

[former_member201257]

It looks like there is a problem in the connection between your portal and back end system.

Test the connectivity between your portal and the back end system - using the connection tests on the system object created on your portal via System Administration - System Landscape.

If it is a webdynpro java application that you are trying to launch, make sure that your JCo destinations are configured correctly. Check the system definition for your backend system in the SLD.

Also, make sure that the system alias you are using in your UWL configuration for the back end system is correctly maintained in the System Aliases list for your back end system (from System Administration - System Landscape).

- Shanti

[Former Member]

Shanti,

Thanks for the reply. I checked all the things you mentioned . Connection tests are fine, jco,sld config. is fine. All the ESS/MSS Applications are working.

The Leave Request Approval is working in MSS Inbox.

Only The Travel Request Approval is giving such a issue.

Please reply.

[Former Member]

Make sure the system name/alias is mentioned in the iview is correct. Try to preview the iview itself.

Regards

Puneet

[Former Member]

Which iview I should be looking in for.?

Thanks