cancel
Showing results for 
Search instead for 
Did you mean: 

Loan application issue in EHP7

former_member182426
Active Contributor
0 Kudos

We are trying to use the WDABAP Loan Request application in EHP7.

When we run from SE80 it's working fine no issue.

When we click on New Loan Request button application opens fine.

But when we run from ESS role from portal it's giving error.

In Launchpad application configured as below.

To cross check i just configured, only Create Loan Request application and checked. It's opening fine.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

From portal error:

System Alias:  'LOGL300',

User:          'SHANKAR',

Reason:        System Alias is not defined or permission denied for this user

  at com.sapportals.portal.appintegrator.accessor.system.LocalSystemAccessor.<init>(LocalSystemAccessor.java:60)

It says

1. System Alias:  'LOGL300' not defined

or

2. Permission denied for this user

I would suggest to add the system alias(LOGL300) in portal just to check if its works fine after adding it or not.

Apart from it make sure your user id or the respective portal role or group has the permissions.

Login to portal as Administrator, in content admin, open the permissions for Portal Content and give the Everyone group the read access. Also click on the "Reset Child Permissions" button so that all the children will get same read access. This should resolve your permission problem.

Try these two and see.

For the backend see why the iv_classname is empty, may be some config is not there or getting lost some where in code.

former_member182426
Active Contributor
0 Kudos

I already checked it by adding the LOGL300 as system alias in system object portal side. And it's opening fine.

still my question is , why it's looking for SAP ECC logical system name as system alias for this loan application when we run from portal instead of SAP_ECC_HumanResources like Leave Request or Leave Overview applications.

And 2nd thing i observed, by running this application form SE80, sucessfully created the loan request and workflow is triggered for approval. And task is pending with manager id in workflow log.

But when i check from manager application i.e HRESS_LOAN_AP_OVP_TREE_IN loan approval application this loan requests are not showing for approval.

I check in debug mode of this application feeder class CL_HRESS_LOAN_APPR_TREE_OVP_IN

What I observed in this method IF_FPM_GUIBB_TREE~GET_DATA

The flow happening like this when i open the loan approval application as manager.

-> In GET_DATA method,  It's calling FM  HRXSS_IN_LOANS_TRANS_DATA with below export parameters.

Mode = 0

approver = gv_app_pernr

workitem_id = wi_id

->  Inside FM, Statement  CASE 0 level.

there is statement checking the WORKITEM_ID value and clearing the PERNR field if there is no WORKITEM ID passed

-> After that it's calling PERFORM GET_APPR_TRANS as shown in above screen shot.

In side this perform it's trying to read the records from table T7INTRNS_META_DT

But here there is no PERNR value passed since before calling this perform PERNR field got clear and it's not returning the values of pending requests.

In debug mode i tried to pass the value of approver no. and check it, but it's not getting the loan requests for approval.

Then i check in table T7INTRNS_META_DT, it's having employee no (Loan Request created by)  and pending with user id and it will not contain the approver employee number.

Is there any bug in WDABAP based loan request / approval applications ? Any body faced this issues ?


Struck with is anything missed or application issue etc.


- Plz provide your views on this issue.

former_member182426
Active Contributor
0 Kudos

Finally issue got solved with below OSS Note implementation.

2062247 - Loans - Webdynpro ABAP Revamp functionality

This new WDABAP Loan application is not like leave request approval application,

You have to add the ECC Logical system name as system alias name in portal side to

avoid the create new loan request from Loan Overview application in portal.

Former Member
0 Kudos

Hi Shankar,

Glad that your issue got resolved.

Can we use this application for country grouping other than India ??

Regards,

Namsheed.

former_member182426
Active Contributor
0 Kudos

This application is released only for India not for other countries.

For other countries you can use HCM Processes and Forms.

Former Member
0 Kudos

Thanks for the info. Can we update IT45 , IT0015 and all using F&P..? Do u have any steps for doing that..?

Regards,

Namsheed.

former_member182426
Active Contributor
0 Kudos

You can check below standard SAP processes for some loan request processes.

S_LOAN_A500_QA

S_LOAN_A400_QA

HR_PA_XX_COMPANY_LOANS

Answers (3)

Answers (3)

pankaj001
Participant
0 Kudos

Hi Shankar,

We are also facing a similar kind of issue where when we click on "New Loan Request" Button from Loan Overview in ESS we are getting "Page not found error", and when i check the logs URL is pointing to some Business Package folder.

We are at EHP7 and have imported PFCG role for ESS in Portal.

Please help!

Regards,

Pankaj

Former Member
0 Kudos

Hi Shankar,

Nice to see the Solutions on loans which you have posted . We are on EHP7 . Our requirement is loans . Can you please let me know the standard package of loans for India in EHP 7 . We have been checking for standard things under LPD_CUST ----> ESS and i have the loan application mentioned as below

Now as i read through the Thread which you have posted,  i feel first the SAP note to be implemented

i e 2062247 in the present environment .isnt it ?

After this please let me know the process to follow to get the loan service on the portal ?

Thanks and regards

Lokesh

Former Member
0 Kudos

Issue resolved .

former_member182426
Active Contributor
0 Kudos

And I cross checked with only New Loan Request application form portal. This also is having some issue.

From portal application opens fine.

After filling the values clicking on Review button it's shows dump.

I check in ST22, it show dump in standard class method.

In debug mode, 2nd time it's getting emtpy for field iv_classname and returning 500 internal error.

This issue is happening from portal only. If i run from SE80 and create new request from overview screen it's working fine.

Former Member
0 Kudos

can u try with another pernr by giving sap_all AUTHORISATIONS ONCE and check it in portal

Error in loans ESS | SCN  

the above is i did it in EHP 6 ..once chk by giving SAP_ALL and check in portal

Error while accessing ESS Loan Request. | SCN

former_member182426
Active Contributor
0 Kudos

User is having SAP_ALL, SAP_NEW profiles.. no authorization issue.. i check in su53 and all.. And as i mentioned in above post, we are trying to use WDABAP FPM applications for this loan service, not WDJAVA based application.

former_member182426
Active Contributor
0 Kudos

For more details of the issue, i got the log from basis and check the log trace. I think it's looking for some system alias. But SAP_ECC_HumanResources alias is created and working fine.

Plz check below log and suggest.


#2.0 #2015 09 22 17:46:59:346#+0530#Error#com.sap.portal.prt.runtime#

#EP-PIN-PRT#tc~epbc~prtc~api#C000C0A800DF082B00000002000032E4#5374450000000004#sap.com/com.sap.portal.runtime.system.hooks#com.sap.portal.prt.runtime#SHANKAR#319##CBFE3EB5612311E5877E0000005201F2#cc811dbe612311e5c9f60000005201f2##0#Thread[HTTP Worker [@983450148],5,Dedicated_Application_Thread]#Plain##

05:46_22/09/15_0024_5374450

[EXCEPTION]

com.sapportals.portal.appintegrator.ApplicationIntegratorException: Unknown system alias.

System Alias:  'LOGL300',

User:          'SHANKAR',

Reason:        System Alias is not defined or permission denied for this user

  at com.sapportals.portal.appintegrator.accessor.system.LocalSystemAccessor.<init>(LocalSystemAccessor.java:60)

  at com.sapportals.portal.appintegrator.accessor.system.SystemAccessorFactory$Decider.getAccessor(SystemAccessorFactory.java:178)

  at com.sapportals.portal.appintegrator.accessor.system.SystemAccessorFactory$Decider.getSystemAccessor(SystemAccessorFactory.java:123)

  at com.sapportals.portal.appintegrator.accessor.system.SystemAccessorFactory.getSystemAccessor(SystemAccessorFactory.java:52)

  at com.sapportals.portal.appintegrator.layer.AbstractIntegrationLayer.getLocalOrRemote(AbstractIntegrationLayer.java:642)

  at com.sapportals.portal.appintegrator.layer.TopLayerSwitch.mustRedirectToProducer(TopLayerSwitch.java:105)

  at com.sapportals.portal.appintegrator.layer.TopLayerSwitch.getNextLayer(TopLayerSwitch.java:75)

  at com.sapportals.portal.appintegrator.LayerProcessor.getNextLayer(LayerProcessor.java:293)

  at com.sapportals.portal.appintegrator.LayerProcessor.processActionPass(LayerProcessor.java:183)

  at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doActionPass(AbstractIntegratorComponent.java:155)

  at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doOnPOMReady(AbstractIntegratorComponent.java:73)

  at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:398)

  at com.sap.portal.prt.core.RequestDispatcherFactory$PortalComponentRequestDispatcher$1.service(RequestDispatcherFactory.java:168)

  at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:292)

  at com.sap.portal.prt.core.RequestDispatcherFactory$PortalComponentRequestDispatcher.handleEvent(RequestDispatcherFactory.java:158)

  at com.sap.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:242)

  at com.sap.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:341)

  at com.sap.portal.prt.pom.PortalNode.processEventQueue(PortalNode.java:734)

  at com.sap.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:473)

  at com.sapportals.portal.prt.connection.ServletConnection._handleRequest(ServletConnection.java:224)

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

  at com.sap.portal.prt.dispatcher.DispatcherServlet.service(DispatcherServlet.java:132)

  at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)

  at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:202)

  at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:103)

  at com.sap.portal.http.EnrichNavRequestFilter.doFilter(EnrichNavRequestFilter.java:49)

  at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:79)

  at com.sap.portal.prt.dispatcher.CustomHeaderFilter.doFilter(CustomHeaderFilter.java:58)

  at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:79)

  at com.sap.portal.http.EnrichNavRequestFilter.doFilter(EnrichNavRequestFilter.java:49)

  at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:79)

  at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:441)

  at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)

  at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)

  at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)

  at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)

  at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

  at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)

  at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

  at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:278)

  at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

  at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)

  at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)

  at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

  at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)

  at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)

  at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

  at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)

  at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

  at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

  at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)

  at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

  at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

  at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26)

  at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

  at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

  at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)

  at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

  at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

  at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)

  at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

  at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

  at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:475)

  at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269)

  at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)

  at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)

  at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)

  at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)

Former Member
0 Kudos

in ur log it is pointing to System Alias:  'LOGL300'  but in ur launchpad it is SAP_ECC_HumanResources for this application ...in ur UWL check all the system aliases are defined and about LOGL300 this system alias from ware it is pointing check from ur basis end when starting this application

former_member182426
Active Contributor
0 Kudos

This system alias LOGL300 is SAP ECC Logical system name. It's not System alias and which we will not define as system alias in portal side.

As i mentioned in previous post, from ESS also application opens fine, when we click on New Loan request it's giving this error.

If it's system alias issue, that overview application itself it should not open right.

In LPd_CUST, ESS menu this application is not configured in standard. So we are adding it with that system alias of SAP_ECC_HumanResources like for other applications ITDeclarations, Claims,  salary statement etc.

Former Member
0 Kudos

wait for experts reply or else raise OSS