ESS Claims Problem
Hi,
I am working on ESS / MSS Claims, the problem i am facing is
when the applicant calim for say 2400 where his eligibility is 2400
he is able to send the claim request to Appover & the request is reaching the approvers inbox,
but when the approver tries to approve the request it is giving the following error...
" Requested amount 24000 is greater than balance eligibilty amount 0.00 "
in appover level it is checking for the balance amount of applicant , which is not correct.
Can any one tell me why the system is checking the balance eligibilty amount of applicant at the approver level ?
Waiting for ur reply ...
Regards,
Srinath
Hi All,
I even checked the UWL XML content for Webflow connector.The particular Task ID for claims is registered there.CHeck the following .Do I have to add anything here?
<ItemType name="uwl.task.webflow.TS18900010.sap_R3%130" connector="WebFlowConnector" defaultView="DefaultView" defaultAction="launchWebDynPro" executionMode="default">
<ItemTypeCriteria systemId="sap_R3%130" externalType="TS18900010" connector="WebFlowConnector"/>
<Actions>
<Action name="launchWebDynPro" groupAction="" handler="SAPWebDynproLauncher" returnToDetailViewAllowed="yes" launchInNewWindow="yes" launchNewWindowFeatures="resizable=yes,scrollbars=yes,status=yes,toolbar=no,menubar=no,location=no,directories=no">
<Properties>
<Property name="WebDynproApplication" value="ClaimAdvanceRequest_IN"/>
<Property name="WebDynproDeployableObject" value="sap.com/essinclaims"/>
<Property name="newWindowFeatures" value="resizable=yes,scrollbars=yes,status=yes,toolbar=no,menubar=no,location=no,directories=no"/>
<Property name="openInNewWindow" value="yes"/>
<Property name="display_order_priority" value="5"/>
</Properties>
<Descriptions default=""/>
</Action>
</Actions>
</ItemType>
Please help.
Similar Messages
-
ESS Claims - Requested value Rs. 20000 is greater than balance eligibility
Dear All,
While Approving the ESS claims request getting a error message Requested value Rs. 20000 is greater than balance eligibility value 0.00.
Help in solving this issue.
Regards,
Potru.Hi,
This is a correct error. Please check the balance amount in infty 45 for the particular loan type. The loan request should not exceed that.
Hope this helps
Regards
Roy -
ESS Claim Advance Approval screen showing incomplete list of requests.
Hi Friends,
In ESS Claim Advance Approval screen we are facing this issue.
When approver opens the screen for approving the request.
The list of requests appear but its not the complete list.
There are also 2 sucess messages that get displayed.
112 records found for the selection
Only 10 of 112 records loaded which meet the selection criteria
Users are able to see the rest of the request at r/3,
also if they approve the first 10 request then they are able to view the next slot of requests.
Any guidance as where the configuration for this could be checked.
Regards.
Edited by: SAP Portal Deve on Sep 20, 2011 2:41 PMyou mean number of requests in UWL?
Please specify
http://help.sap.com/saphelp_afs64/helpdata/en/56/15681955744ec8877931c56607ec35/frameset.htm
Edited by: Siddharth Rajora on Sep 20, 2011 8:08 PM -
Hi ALL ,
we are doin configuration for ESS claims in ECC 6.
Our screen has Reimubersement types then request types and scheme type.
for some employees we are able to see 3 reimbursement types namely LTA, office expences and medical but for some this dropdown box shows only 1 or 2 options.
please telll me from where we configure reimbursement types in claims
if its depends upon ESG then wher we maitain
thanks in advancethanks for the reply.
i have checked that table but still i am unable to understand how it is reflecting in drop down of reimbursemnt types on ESS page -
Error in ESS claims Functionality
Hi all,
We are on track for implementing Standard ESS Claims Functionality.
While taking advance there is no issue but when we go for Claim Against
Advance it is throwing error as
1. LTC Block Start and End Year not maintained in V_T511K
2. There is no eligibility for any of the dependents for LTC scheme (SLTA:CA:LTC:20110326).
While debugging we have come across that while call function to
HRXSS_IN_CL_SLTC_ELIGIBLITY there is no begda maintained in parameter
ifd_edate = pds_reqdt-trnsd-begda but when we see in table V_T511K LCT
Block start and end dates are maintained. PLs guide .
Component details
SAP_HR 604
Portal Version
EHP1 EP 7.01
Regards,
SoniDear soni,
Can you please send config steps for LTC claim via ESS.
Urgent requirement Please help.
send to kseenu019 at the rate gmail dot com
Thanks and Regards
Srinivas -
Problem in processing the ESS Claims work item in UWL
Hi All,
After Employee raises the claim request ,work item is coming to Manager's UWL Inbox but the problem is it is not coming as a Hyperlink , it is not opening the approval window even if we click the item , it is not even coming as a hyperlink.
Please help.Hi All,
I even checked the UWL XML content for Webflow connector.The particular Task ID for claims is registered there.CHeck the following .Do I have to add anything here?
<ItemType name="uwl.task.webflow.TS18900010.sap_R3%130" connector="WebFlowConnector" defaultView="DefaultView" defaultAction="launchWebDynPro" executionMode="default">
<ItemTypeCriteria systemId="sap_R3%130" externalType="TS18900010" connector="WebFlowConnector"/>
<Actions>
<Action name="launchWebDynPro" groupAction="" handler="SAPWebDynproLauncher" returnToDetailViewAllowed="yes" launchInNewWindow="yes" launchNewWindowFeatures="resizable=yes,scrollbars=yes,status=yes,toolbar=no,menubar=no,location=no,directories=no">
<Properties>
<Property name="WebDynproApplication" value="ClaimAdvanceRequest_IN"/>
<Property name="WebDynproDeployableObject" value="sap.com/essinclaims"/>
<Property name="newWindowFeatures" value="resizable=yes,scrollbars=yes,status=yes,toolbar=no,menubar=no,location=no,directories=no"/>
<Property name="openInNewWindow" value="yes"/>
<Property name="display_order_priority" value="5"/>
</Properties>
<Descriptions default=""/>
</Action>
</Actions>
</ItemType>
Please help. -
Error in ESS Claims: Field outlook cahracetrs have not been maintined
Dear Experts,
We are having an error in the ESS qualty ..in the Reimbursement and claims screen. When we click on this link we are getting a warning message "Field outlook cahracetrs have not been maintined".Only default reimbursement types LTA and Medical allowance are appearing in the drop down for reimbursement type. All the paroll allowance groupings and claims configuration have been done. Please let us know the possible cause for the error.
Note: The problem persists in Quality but working fine in SandboxAny inputs??
-
ESS Claim Application Behaviour
Hi ESS Experts,
I have configured Claims Functionality.
Now when I am trying to raise new claim request, system is not displaying Dropdown LOV's. It was properly and i was able to update records in R/3.
We have not done any changes in Configuration .. I am using Java Application for Claims ..
and the strange thing.. when I am checking with same user using Reimbursement Approval Link then system is showing the LOV's..
I don't know why system is not showing LOV in one link but in other its is showing.
Please suggest solutions.
Thanks
PuneetIssue resolved by self. There was some JCO connection error.
-
ESS Claims: Reimbursement types not appearing in portal
Hi ESS Experts,
I have done al the configuration required for Claims functionality and it was working fine also.
Now I am not able to see cliam list in ESS application. I using Java Application.
T7INT9 and A9 tables are cofigured and eligibility is showing in HINCREMS also
Kindly provide the solution.
Thanks
PuneetHi,
Execute the report HINCREMS with out giving any Reimbursement type in the selection screen and let us know the result.
Regards,
Jyothi -
Hi
I am not able to get drop downs for claims and reimbursement type in ESS, has configured R/3.
Pls. guide.
ThanksPlease check in SPRO you have maintained the help for this.
-
Hi,
Situation
We are using ESS/MSS within the Portal 7.0 SP 14. The SAP Backend which we are using is ECC 6.0.
SSO between the Portal and Backend works efficient.
Problem
There are some issues when using the Universal Worklist. All tasks appear in our Universal Worklist from the Backend. Unfortunately, when trying to open any task we are facing the following error:
com.sap.aii.proxy.framework.core.DataAccessException: Type conversion error, field I_TRIPNUMBER, complex type class com.sap.xss.tra.tri.model.tripform.Ptrm_Web_Form_Pdf_Get_Input
at com.sap.aii.proxy.framework.core.JcoBaseTypeData.propagateJcoException(JcoBaseTypeData.java:130)
at com.sap.aii.proxy.framework.core.JcoBaseTypeData.setElementValue(JcoBaseTypeData.java:751)
at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClass.setAttributeValueAsString(DynamicRFCModelClass.java:669)
at com.sap.xss.tra.tri.model.tripform.Ptrm_Web_Form_Pdf_Get_Input.setI_Tripnumber(Ptrm_Web_Form_Pdf_Get_Input.java:282)
at com.sap.xss.tra.tri.fc.tripform.FcTriTripForm.rfcFormPdfGet(FcTriTripForm.java:382)
... 65 more
Following steps have been followed up
The URL parameter of the resource "Employee_travel_tripform_srv05 has the value "sap_xss_tra_UsePdf=true"
The iView "Display Trip Form" has the application parameter "sap.xss.tra.UsePdf=true"
Question
When a task is opened from the Universal Worklist, the Trip Form must appear in PDF Form.At this stage the iview "Display Trip Form" opens but shows the error mentioned above.
Is there anyone who could help us out?
Any help would be appreciated.
Regards,
Gene MadikramaHi Barin Desai,
Again thank you for your response. We have checked the workflow *WS90000013*, and you are right; it is a customized workflow.
As we already mentioned, we are using a &BUS2089&.
In this &BUS2089& there are the elements: &TRIP.EMPLOYEENUMBER& and &TRIP.TRIPNUMBER&
Unfortunately it is not possible to delete &BUS2089&. Deleting the &BUS2089& will cause a lot of problems for this total Workflow.
UWL iView
For the UWL iView we are using the XML file "com.sap.pct.erp.mss.tra.xml" that comes with the ESS/MSS business package.
A piece of the code of "com.sap.pct.erp.mss.tra.xml is:
<Action name="com.sap.pct.erp.mss.tra.action.DisplayExpenseForm" referenceBundle="com.sap.pct.erp.mss.tra.DisplayForm"
handler="SAPAppLauncher" returnToDetailViewAllowed="yes" launchInNewWindow="yes"launchNewWindowFeatures="toolbar=no,menubar=no">
<Properties>
<Property name="SAPIntegrator" value="ROLES://portal_content/com.sap.pct/every_user/com.sap.pct.erp.ess.bp_folder/com.sap.pct.erp.ess.roles/com.sap.pct.erp.ess.employee_self_service/com.sap.pct.erp.ess.employee_self_service/com.sap.pct.erp.ess.area_travel_expenses/com.sap.pct.erp.ess.tripform"/>
<Property name="sap.xss.tra.TripNo" value="${item.TripNumber}"/>
<Property name="sap.xss.tra.PersNo" value="${item.EmployeeNumber}"/>
<Property name="sap.xss.tra.TripComponent" value=" "/><!-- Display Travel Expense Report -->
<Property name="display_order_priority" value="10"/><!-- Shift to left side -->
<!Property name="UserComment" value="$"/>
<!Property name="User" value="$The specified item was not found."/>
</Properties>
</Action>
Question:
Will changing the code of "com.sap.pct.erp.mss.tra.xml" solve our problem? Or do we need to change something else?
Is there anything we need to do from the portal side or any configuration on the ECC backend?
Regards,
Gene Madikrama -
Hi All,
I have configured the Claims service in ESS and i am getting the work item in UWL in approver's tasklist. But when i click on the task item, it redirects to SAPR3 EASY ACCESS MENU and gives the error that WORKITEM CAN ONLY BE EXECUTED USING THE PORTAL AND UWL.
I have maintained the SWFVISU transaction for taskid TS18900010 and given the APPLICATION NAME and PATH. But still no use.
Can anyone plz advise on this
Thanks and Regards
ReshmaHi Reshma,
I think there is an error in the configuration. Could you give a bit more info? Which workflow are you using (standard or custom?). What system are you on ECC?
I also checked for the task you mentioned, but it is not available in ECC 5.0.
Also when you cross post in different forums mention this in your post.
Regards,
Martin -
Hi One & All,
Hope everyone is doing good.
I have one issue when creating Claims request from ESS through Portal.
When I click Create in Reimbursements / claims application, I have selected the Reimbursement type & Request type, then It is giving error message saying: " You Cannot create more than 0 requests in a SLTA: date YYYYMMDD. Creation cancelled.
Please help me how can I solve this?
Regards,
KSanj.Hi,
Does it look like a standard error?
We have made an enhancement for achieving this as we did not find any solution for controlling the creation of open TI if it is more than 10 requests.
Not sure how much will this help. But please check here.
In WD Component : FITE_VC_GENERAL_DATA, Component Controller,
Method : ON_INIT, On the Pre Exit of this we have controlled this by checking table PTRV_PERIO.
Please check and let me know if you found useful.
Cheers,
Raj
Edited by: Rajagopalan Kannan on May 2, 2011 12:04 PM -
ESS Configuration problem - Salary statement
I have configured the ESS as per the documentations.
We have ECC 6.0 with EA-HR SP03 and XSS SP6.
The following JCO connections are all setup to ECC 6.0 back end and are pinging and tested successfully, even though not all are required.
SAP_R3_Financials_MetaData
SAP_R3_HumanResources
SAP_R3_HumanResources_Metadata
SAP_R3_SelfServiceGenerics
SAP_R3_SelfServiceGenerics_MetaData
SAP_R3_SelfServiceGenerics_MetaDataFIN
SAP_R3_SelfServiceGenericsFIN
SAP_R3_Travel
SAP_R3_Travel_MetaData
WD_MODELDATA_DEST
WD_RFC_METADATA_DEST
WD_RSDAS_MODELDATA_DEST
WD_RSDAS_RFC_METADATA_DEST.
The System Aliases SAP_ECC_HumanResources and SAP_WebDynpro_XSS are defined with WAS properties.
There are no authorization issues as the user is SAP_ALL at ECC and superuser at the portal.
Employee search and Maintain own data services are working fine with default settings.
But while trying to view the Salary Statement (Paycheck Inquiry Service) the error below comes up.
The full exception chain is as below.
java.lang.ArrayIndexOutOfBoundsException: -1
at com.sap.mw.jco.JCO$Record.getString(JCO.java:12623)
at com.sap.aii.proxy.framework.core.JcoBaseTypeData.getElementValueAsString(JcoBaseTypeData.java:669)
at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClass.getAttributeValueAsString(DynamicRFCModelClass.java:409)
at com.sap.xss.hr.rep.model.rfwmodel.Hrxss_Ser_Rfw_Rfc_Get_Form_Output.getHeight(Hrxss_Ser_Rfw_Rfc_Get_Form_Output.java:179)
at com.sap.xss.hr.rep.fcrfw.FcRepFramework.callRfcGetForm(FcRepFramework.java:395)
at com.sap.xss.hr.rep.fcrfw.FcRepFramework.processFollowingActions(FcRepFramework.java:484)
at com.sap.xss.hr.rep.fcrfw.FcRepFramework.callRfcExecAction(FcRepFramework.java:378)
at com.sap.xss.hr.rep.fcrfw.FcRepFramework.initModel(FcRepFramework.java:292)
at com.sap.xss.hr.rep.fcrfw.wdp.InternalFcRepFramework.initModel(InternalFcRepFramework.java:256)
at com.sap.xss.hr.rep.fcrfw.FcRepFrameworkInterface.initModel(FcRepFrameworkInterface.java:136)
at com.sap.xss.hr.rep.fcrfw.wdp.InternalFcRepFrameworkInterface.initModel(InternalFcRepFrameworkInterface.java:198)
at com.sap.xss.hr.rep.fcrfw.wdp.InternalFcRepFrameworkInterface$External.initModel(InternalFcRepFrameworkInterface.java:258)
at com.sap.xss.hr.rem2.selection.VcRem2Selection.onInit(VcRem2Selection.java:245)
at com.sap.xss.hr.rem2.selection.wdp.InternalVcRem2Selection.onInit(InternalVcRem2Selection.java:249)
at com.sap.xss.hr.rem2.selection.VcRem2SelectionInterface.onInit(VcRem2SelectionInterface.java:161)
at com.sap.xss.hr.rem2.selection.wdp.InternalVcRem2SelectionInterface.onInit(InternalVcRem2SelectionInterface.java:144)
at com.sap.xss.hr.rem2.selection.wdp.InternalVcRem2SelectionInterface$External.onInit(InternalVcRem2SelectionInterface.java:220)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:563)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:437)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:195)
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:429)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:345)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:668)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:268)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:725)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:661)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:227)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:150)
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:739)
at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:208)
at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1240)
at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:340)
at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:538)
at com.sap.portal.pb.PageBuilder.wdDoRefresh(PageBuilder.java:582)
at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:811)
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:137)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:344)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:298)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:677)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:227)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:150)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:56)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:47)
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:390)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
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:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Could you please help me out.
thanks & regards
K. Muhammed AliMohammed,
Did you ever get an answer to this ESS problem? We are having the same problem now.
Thanks,
Dave -
Standard Workflow Tables for ESS Claims
Hi Experts,
We have configured the ESS / MSS Claims process in R/3, Portal and Workflow. Once I am applying claim in portal and approving the claim. I am running the standard program to update the infotypes. Now my query is, where these datas will be stored in the backend. When the user is required to view the datas how should they might check these datas except through infotype. I have checked the standard tables there is no data available.
Kindly reply me as soon as possible.... So that I have process it further
Regards,
Kannan
Edited by: Kanna83 on Dec 21, 2011 6:35 PMDear Siddharth,
Thanks for your valuable reply.
But in the table T77WWW_CLTRANSD we are not able to see any records getting stored.
How to view the records in the table T77WWW_CLTRANSD?
Can u let us knw that the table T7INCLM_ADV_TRNS ( Claims & Advance Transaction Table ) will get updated or not???
Is there any report to update the table T7INCLM_ADV_TRNS.
Please let us knw.
Thanks,
Nalla B.
Maybe you are looking for
-
Got HTC Incred 2 and is great. Now in Europe for first time and email works but not calling. Any suggestions? Can't find number to contact verizon from Europe either. thanks
-
IPOHONE 4: I have a problem in the touch screen
IPOHONE 4: I have a problem in the touch screen. Sometimes it responds ODD.. it is not working as the way it must be. when i touch an apps to open, insted of the desired apps, another apps opens. this is due to the touch screen issue. How do i Rectif
-
the podcast app is not fixed still wont download,did not find any solutions with anyones comments,they all have the same problem with this app.So how can you say the problem is fixed,get someone who knows how to really do something so it is not a rec
-
Where used list doesn't work for global data
Hi, When i try to do where used list on a constant in an include, it doesn't give the results for classes. The class contains the include in a method that uses the constant, and the where used list for that constant doesn't find the appearance of the
-
I'm trying to synchronize my new Palm Z22 with iCal and Address book. Michael Lafferty solved my original problem of not getting iSync. I have downloaded iSync Palm Conduit and it appears as a "pkg" and was said to be installed successfully. However,