No Form Exists error in ESS salary statement

Hi,
The Salary statement in our ESS portal is with standard functinality. This problem started recently.
All the employees are assigned to the sayme payroll area. However, for some employees the "Salary Satement" in ESS is working fine and for a few employees it is throwing the dump "No Form Exists" in portal.
"com.sap.pcuigp.xssfpm.java.FPMrUNTIMException: No form exists"
We have checked the configuration for the Payslip in r/3 and they are fine.
We have executed the tcode PC00_M20_CEDT successfully to view the salaryslips for the individual employees in R/3.
We are currently on EP7.0 SP19 and ECC.0
I have found some similar threads on this issue, which did not cater to our need.
Any help on this would be appreciated.
Regards,
Venu

Hello,
We've run into the same issue as described above. We've been able to narrow down the issue but still can't find a solution, even after applying what was suggested.
The PDF pay advice works fine when we log on with a user assigned to an employee role. When we log on with a user id assigned to both a manager and employee role, we get the following error when viewing the PDF pay advice "error " Form ZFHR_PAYSLIP does not exist ".
However, If we switch configuration to use the PE51 form, everything seems to work fine. The issue arises when we try and use the PDF pay advice logged and logged in as a manager.
Thanks in advance,
-joel

Similar Messages

How to configure ESS Salary Statement

Hello,
I am trying to configure the ESS Salary Statement in ECC->spro where I have specified the Z.....Form name in the various features.....but when I view it on the portal....I get the following errors:
com.sap.pcuigp.xssfpm.java.FPMRuntimeException: Form Z.......does not exist
for 1 user
and No payroll results found for personnel number <personnel number> for the other user...
Please let me know if I am missing something.

Hi Anil,
Please go to TCODE: PTARQ
Employee Self-Service -> Service-Specific Settings -> Benefits and Payment -> Salary Statement -> Form Using HR Forms Editor (PE51)
-> Edit Feature HRFOR: insert the constant $CEDT$ - this is how you tell to the program that you want to select the remuneration statement from the portal
-> Edit Variant and Feature EDTIN: need to insert the variant you create to call the remuneration statement
-> Provide Salary Statement as PDF File in Internet:
- Edit Feature EDPDF: insert the name of the remuneration statement
If you want to make some customizing on the form, use transaction SMARTFORMS.
To the employees which have acess to the remuneration statement on ESS, please make a check on IT0655.
And thats it!
Hope this help.
Sónia

Configure ESS Salary Statement and Quota Overview

Hello,
I am having problems in displaying ESS salary statement on portal (EP 7.0) .....this is the error :
Form SAP_PAYSLIP_US does not exist
I feel there is some configuration to be done for this....also how do I configure Time accounts in ESS....is creation of Rule groupd a necessity...?
Any help would be appreciated.

Hi Anil,
just a small check, the z smartform name, have you created this through HRFORMS.
For example in HRFORMS, u have maintiend HRFORM name say, ZHR_TIME_IN. Now this shoud be activeted and check the details. Here it would be showing the zsmartform name and report name.
Also, in backend config spro, have u maintained this ZHR_TIME_IN for TESD, TESP,TMW etc..u can select the relevant class. please go thru the node config help on HRFOR feature. u will get sufficient information here
also,

Error when creating the form Pay ESS "Salary Statement"-Benefits and Payments

Dear All.
I have a issue when genere the PayError when creating the form Pay ("Salary Statement"-Benefits and Payments)
Thanks in advance
Regards

Hi Juan,
This is a very common problem.
refer the following thread ESS EHP5 Payslip form error
Thanks,
Aashima

ESS Salary Statement 'No result exist'

Hi All,
We are setting-up our salary statements on ESS and I am getting this error. I can see results in the overview section, but no form. We are using the HR Forms (PE51) method. I think I have the features setup correctly.
EDTIN: CUS&BEHR_MXESS
HRFOR: ESS = $CEDT$
EDPDF: Y_MX_ESS_PAYSLIP_TO_PDF
The error doesnt say there is an issue with the form, so maybe its something else .. authorization?
Any help is appreciated.
Brandyn

Hi Brandyn,
Are you able to see form Y_MX_ESS_PAYSLIP_TO_PDF under SMARTFORMS transaction and see if it is active status.
This could be anothe rreason for form not showing on ESS.
Also, check if you are logging into ESS for correct system and login system. Possibly url may be incorrect.
Also, ensure new transaction pz11_pdf (old one was pz11) is assigned to ESS user role and pz11_pdf service is published under ITS/Portal in order to recognize the transaction.
Thanks,
Ameet

ESS salary statement view problem

Hi All ,
I created a custom form from using PE51 and configured IMG setting Personnel Management >Employee Self-Service > Service-Specific Settings > Benefits and Payment > Salary Statement
The form is visible fine when i am giving authorization to the user SAP_ALL and SAP_NEW but when i am removing the authorization SAP_ALL and SAP_NEW its giving following me the error.
Can anybody help me on this.
com.sap.pcuigp.xssfpm.java.FPMRuntimeException: Form ZAP_PAYSLIP does not exist
     at com.sap.pcuigp.xssfpm.java.MessageManager.raiseException(MessageManager.java:111)
     at com.sap.pcuigp.xssfpm.java.MessageManager.raiseException(MessageManager.java:121)
     at com.sap.xss.hr.rep.fcrfw.FcRepFramework.reportBapiRet2Error(FcRepFramework.java:495)
     at com.sap.xss.hr.rep.fcrfw.FcRepFramework.callRfcGetForm(FcRepFramework.java:366)
     at com.sap.xss.hr.rep.fcrfw.FcRepFramework.processFollowingActions(FcRepFramework.java:454)
     at com.sap.xss.hr.rep.fcrfw.FcRepFramework.callRfcExecAction(FcRepFramework.java:350)
     at com.sap.xss.hr.rep.fcrfw.FcRepFramework.initModel(FcRepFramework.java:264)
     at com.sap.xss.hr.rep.fcrfw.wdp.InternalFcRepFramework.initModel(InternalFcRepFramework.java:243)
     at com.sap.xss.hr.rep.fcrfw.FcRepFrameworkInterface.initModel(FcRepFrameworkInterface.java:136)
     at com.sap.xss.hr.rep.fcrfw.wdp.InternalFcRepFrameworkInterface.initModel(InternalFcRepFrameworkInterface.java:196)
     at com.sap.xss.hr.rep.fcrfw.wdp.InternalFcRepFrameworkInterface$External.initModel(InternalFcRepFrameworkInterface.java:256)
     at com.sap.xss.hr.rem2.selection.VcRem2Selection.onInit(VcRem2Selection.java:217)
     at com.sap.xss.hr.rem2.selection.wdp.InternalVcRem2Selection.onInit(InternalVcRem2Selection.java:238)
     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:466)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:354)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:179)
     at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:95)
     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:347)
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:382)
     at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:618)
     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
     at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:251)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:48)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
     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:102)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Thanks in Advance.
Edited by: BI Consultant BI Consultant on May 10, 2009 12:20 PM

Hi,
Request you to debug the object associated with payslip with SAP_ALL. Basis folks can help you to debug and find the objects for proper authorization.
Regards,
Sanjeev mourya

ESS - Salary statement

We have a salary statement designed in PE51. This has been desgined to be mass printed as a pay stub. When this same form is plugged in ESS , the form alignment is not correct - which is obvious becuase this was created keeping in mind that it will be printed on paper that has a different size window frame as opposed to ESS window. Now the question : Inorder to fit this form in ESS also,
Do I have re align the form using PE51 or are there settings in ESS itself that can be used to achieve this?
- Mark

Hi,
You have to redesign in PE51.
Good Luck
Om

Overview Link of ESS Salary Stat application

Hello,
We are using few ESS applications in our environment. We were using the ESS applications without any customization so far. Now, we have some requirements for customizing a few things. I would really appreciate your help in the following requirement.
(We have the NWDI setup and track created I have imported the configuration into NWDS and created the appropriate project for ess/rem and ess/rep).
(We are on EP 7.0 using Webdynpro Java XSS 600 components)
Our requirement is:
In the ESS pay (Remuneration) statement application:
1. Display the Overview screen by default (This is hidden now and will only be displayed if you click on the link "Show Overview")
I really have very limited idea about this webdynpro application and am having difficulty finding the exact piece of code to be modified.
I will appreciate your help.
Thank You,
Kalyan B

Dear Kalyan,
 I have not done anything, try to check the table properties and redeploy it again.
 Please find my coding
// This file has been generated partially by the Web Dynpro Code Generator.
// MODIFY CODE ONLY IN SECTIONS ENCLOSED BY @@begin AND @@end.
// ALL OTHER CHANGES WILL BE LOST IF THE FILE IS REGENERATED.
package com.sap.xss.hr.rem2.selection;
// IMPORTANT NOTE:
// ALL IMPORT STATEMENTS MUST BE PLACED IN THE FOLLOWING SECTION ENCLOSED
// BY @@begin imports AND @@end. FURTHERMORE, THIS SECTION MUST ALWAYS CONTAIN
// AT LEAST ONE IMPORT STATEMENT (E.G. THAT FOR IPrivateSelectionView).
// OTHERWISE, USING THE ECLIPSE FUNCTION "Organize Imports" FOLLOWED BY
// A WEB DYNPRO CODE GENERATION (E.G. PROJECT BUILD) WILL RESULT IN THE LOSS
// OF IMPORT STATEMENTS.
//@@begin imports
import com.sap.tc.webdynpro.clientserver.uielib.standard.api.IWDTable;
import com.sap.tc.webdynpro.progmodel.api.WDVisibility;
import com.sap.xss.hr.rem2.selection.wdp.IPrivateSelectionView;
//@@end
//@@begin documentation
//@@end
public class SelectionView
Logging location.
private static final com.sap.tc.logging.Location logger =
 com.sap.tc.logging.Location.getLocation(SelectionView.class);
static
 //@@begin id
 String id = "$Id$";
 //@@end
 com.sap.tc.logging.Location.getLocation("ID.com.sap.tc.webdynpro").infoT(id);
Private access to the generated Web Dynpro counterpart
for this controller class. 
Use <code>wdThis</code> to gain typed access to the context,
to trigger navigation via outbound plugs, to get and enable/disable
actions, fire declared events, and access used controllers and/or
component usages.
@see com.sap.xss.hr.rem2.selection.wdp.IPrivateSelectionView for more details
private final IPrivateSelectionView wdThis;
Root node of this controller's context. 
Provides typed access not only to the elements of the root node
but also to all nodes in the context (methods nodeXYZ())
and their currently selected element (methods currentXYZElement()).
It also facilitates the creation of new elements for all nodes
(methods createXYZElement()). 
@see com.sap.xss.hr.rem2.selection.wdp.IPrivateSelectionView.IContextNode for more details.
private final IPrivateSelectionView.IContextNode wdContext;
A shortcut for <code>wdThis.wdGetAPI()</code>. 
Represents the generic API of the generic Web Dynpro counterpart
for this controller. 
private final com.sap.tc.webdynpro.progmodel.api.IWDViewController wdControllerAPI;
A shortcut for <code>wdThis.wdGetAPI().getComponent()</code>. 
Represents the generic API of the Web Dynpro component this controller
belongs to. Can be used to access the message manager, the window manager,
to add/remove event handlers and so on. 
private final com.sap.tc.webdynpro.progmodel.api.IWDComponent wdComponentAPI;
public SelectionView(IPrivateSelectionView wdThis)
 this.wdThis = wdThis;
 this.wdContext = wdThis.wdGetContext();
 this.wdControllerAPI = wdThis.wdGetAPI();
 this.wdComponentAPI = wdThis.wdGetAPI().getComponent();
//@@begin javadoc:wdDoInit()
/** Hook method called to initialize controller. */
//@@end
public void wdDoInit()
 //@@begin wdDoInit()
 // Added here to Call methods When the Application is loaded.
 if(wdContext.currentVCDATAElement().getLINK_ENABLED()){
 try{
 wdContext.currentContextElement().setTable_visible(WDVisibility.VISIBLE);
 wdContext.currentVCDATAElement().setOVERVIEW_SEL("99");
 wdThis.wdGetVcRem2SelectionController().execAction(wdContext.currentVCDATAElement().getACTIONID_LINK());
 wdThis.wdGetVcRem2SelectionController().execAction(wdContext.currentVCDATAElement().getACTIONID_DDSEL());
 }catch(NullPointerException e){
 wdComponentAPI.getMessageManager().reportWarning("Salary Statement does not Exists in database for You : " + e.getMessage());
 }else{
 wdContext.currentContextElement().setTable_visible(WDVisibility.NONE);
 wdComponentAPI.getMessageManager().reportWarning("Payroll data does not Exists, Check with HR Team");
 //@@end
//@@begin javadoc:wdDoExit()
/** Hook method called to clean up controller. */
//@@end
public void wdDoExit()
 //@@begin wdDoExit()
 //@@end
//@@begin javadoc:wdDoModifyView
Hook method called to modify a view just before rendering.
This method conceptually belongs to the view itself, not to the
controller (cf. MVC pattern).
It is made static in order to discourage a way of programming that
routinely stores references to UI elements in instance fields
for access by the view controller's event handlers etc.
The Web Dynpro programming model recommends to restrict access to
UI elements to code executed within the call to this hook method!
@param wdThis generated private interface of the view's controller as
 provided by Web Dynpro; provides access to the view controller's
 outgoing controller usages etc.
@param wdContext generated interface of the view's context as provided
 by Web Dynpro; provides access to the view's data
@param view the view's generic API as provided by Web Dynpro;
 provides access to UI elements
@param firstTime indicates whether the hook is called for the first time
 during the lifetime of the view
//@@end
public static void wdDoModifyView(IPrivateSelectionView wdThis, IPrivateSelectionView.IContextNode wdContext, com.sap.tc.webdynpro.progmodel.api.IWDView view, boolean firstTime)
 //@@begin wdDoModifyView
 //wdContext.nodeVCTABLE().getNodeInfo().addAttributesFromDataNode();
 //wdComponentAPI.getMessageManager().reportWarning("Check Status : " + wdContext.currentVCDATAElement().getOVERVIEW_VISIBLE());
 IWDTable viewTab = (IWDTable) view.getElement("OverViewTab");
 wdThis.wdGetVcRem2SelectionController().assignTable(view, viewTab, wdContext.nodeTABLE0(), firstTime);
 if (wdContext.currentVCDATAElement().getOVERVIEW_VISIBLE() == WDVisibility.VISIBLE) {
 // overview is already shown - enable close
 wdContext.nodeCONTENT_TABLE0().setLeadSelection(wdContext.currentVCDATAElement().getSELECTED_TABROW());
 wdContext.currentRemLocalElement().setLinkOverviewLabel(wdThis.wdGetAPI().getComponent().getTextAccessor().getText("CloseOverviewLabel"));
 wdContext.currentRemLocalElement().setLinkOverviewTooltip(wdThis.wdGetAPI().getComponent().getTextAccessor().getText("CloseOverviewLabel"));
 } else {
 wdContext.nodeCONTENT_TABLE0().setLeadSelection(-1);
 wdContext.currentRemLocalElement().setLinkOverviewLabel(wdThis.wdGetAPI().getComponent().getTextAccessor().getText("OpenOverviewLabel"));
 wdContext.currentRemLocalElement().setLinkOverviewTooltip(wdThis.wdGetAPI().getComponent().getTextAccessor().getText("OpenOverviewLabel"));
 //@@end
//@@begin javadoc:onActionOverViewRowSelection(ServerEvent)
/** declared validating event handler */
//@@end
public void onActionOverViewRowSelection(com.sap.tc.webdynpro.progmodel.api.IWDCustomEvent wdEvent )
 //@@begin onActionOverViewRowSelection(ServerEvent)
 wdContext.currentVCDATAElement().setSELECTED_TABROW(wdContext.nodeCONTENT_TABLE0().getLeadSelection());
 wdThis.wdGetVcRem2SelectionController().execAction(wdContext.currentVCDATAElement().getACTIONID_TABSEL());
 //@@end
//@@begin javadoc:onActionToggleVisibility(ServerEvent)
/** declared validating event handler */
//@@end
public void onActionToggleVisibility(com.sap.tc.webdynpro.progmodel.api.IWDCustomEvent wdEvent )
 //@@begin onActionToggleVisibility(ServerEvent)
 wdThis.wdGetVcRem2SelectionController().execAction(wdContext.currentVCDATAElement().getACTIONID_LINK());
 //@@end
//@@begin javadoc:onActionSel_ListSelection(ServerEvent)
/** declared validating event handler */
//@@end
public void onActionSel_ListSelection(com.sap.tc.webdynpro.progmodel.api.IWDCustomEvent wdEvent )
 //@@begin onActionSel_ListSelection(ServerEvent)
 wdThis.wdGetVcRem2SelectionController().execAction(wdContext.currentVCDATAElement().getACTIONID_DDSEL());
 //@@end
The following code section can be used for any Java code that is
not to be visible to other controllers/views or that contains constructs
currently not supported directly by Web Dynpro (such as inner classes or
member variables etc.). 
Note: The content of this section is in no way managed/controlled
by the Web Dynpro Designtime or the Web Dynpro Runtime.
//@@begin others
//@@end
Regards
Ponnusamy

Form 16 error in ESS

Hi Portal Experts ,
While trying to view the Form 16 link in Benefits and pay section we are getting the below error . W ehave integrated ESS /MSS 1.41 with EP and in backend able to preview the form 16 .   System connection is working fine and jco also fine.
error :
Critical Error
A critical error has occured. Processing of the service was terminated. Unsaved data has been lost.
Contact your system administrator.
     Screen output without connection to user.                           , error key: RFC_ERROR_SYSTEM_FAILURE
com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException:      Screen output without connection to user.                           , error key: RFC_ERROR_SYSTEM_FAILURE
     at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:101)
     at com.sap.xss.hr.rep.fcrfw.FcRepFramework.callRfcExecAction(FcRepFramework.java:373)
     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.in.f16.vc.vcf16selection.VcF16Selection.onInit(VcF16Selection.java:237)
     at com.sap.xss.hr.in.f16.vc.vcf16selection.wdp.InternalVcF16Selection.onInit(InternalVcF16Selection.java:235)
     at com.sap.xss.hr.in.f16.vc.vcf16selection.VcF16SelectionInterface.onInit(VcF16SelectionInterface.java:161)
     at com.sap.xss.hr.in.f16.vc.vcf16selection.wdp.InternalVcF16SelectionInterface.onInit(InternalVcF16SelectionInterface.java:144)
     at com.sap.xss.hr.in.f16.vc.vcf16selection.wdp.InternalVcF16SelectionInterface$External.onInit(InternalVcF16SelectionInterface.java:220)
     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:864)
     at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:220)
     at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1362)
     at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:355)
     at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:549)
     at com.sap.portal.pb.PageBuilder.wdDoInit(PageBuilder.java:192)
     at com.sap.portal.pb.wdp.InternalPageBuilder.wdDoInit(InternalPageBuilder.java:150)
     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.doApplicationProcessingStandalone(ClientSession.java:741)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694)
     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: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(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:      Screen output without connection to user.                           , error key: RFC_ERROR_SYSTEM_FAILURE
     at com.sap.aii.proxy.framework.core.AbstractProxy.send$(AbstractProxy.java:150)
     at com.sap.xss.hr.rep.model.rfwmodel.RfwModel.hrxss_Ser_Rfw_Rfc_Exec_Action(RfwModel.java:184)
     at com.sap.xss.hr.rep.model.rfwmodel.Hrxss_Ser_Rfw_Rfc_Exec_Action_Input.doExecute(Hrxss_Ser_Rfw_Rfc_Exec_Action_Input.java:137)
     at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:92)
     ... 63 more
Could you please help !!!
regards,
Sai

Hi,
You need to maintain entry in table T7XSS_SER_RFW for XSS_HR_IN_F16.
You should maintain entry as follows:
Applid                      classname
XSS_HR_IN_F16      CL_HRXSS_IN_F16
This table value is delivered in standard delivery. Because the delivery class is E "Control table, SAP and customer have separate key areas" Kindly compare in your client 000.
You need to maintain this entry because all applications based on the Generic Reporting Tool (GRT) require a unique application ID. Every application has a class that implements the IF_HRXSS_SER_RFW interface
and controls the back-end logic.
To maintain the entry you can proceed through IMG as follows-> SPRO-> Personnel Management-> Employee Self Service-> General Settings-> Generic Reporting tool(GRT)-> Assign Application ID to application class->
I hope this information will help in resolving the issue.
Assaf Klieger

Hrxss_Per_Subtype_Allowed does not exist error in ESS

Hi SAP Guru's
I am getting error
com.sap.dictionary.runtime.DdException: Type com.sap.xss.per.model.mac.types.Hrxss_Per_Subtype_Allowed does not exist
under Personal Information tabe in ESS, I have searched this error in the SDN but I am not getting exact solution whether should be applied note 1129210 or is it related to other issue.
Please guru's let me know the solution.
Thaks & Regards
Vinay Patel

Hi Nivedita
Thanks a lot
I have applied sp12 only in the Backand system and my problem has been resolved .
My ESS Business Package level is 10
BP_ERP5ESS 1.0 SP10
I am giving 10/10 points.
But I am getting only one error when I am going Personal Information ->Bank information
and editing the Bank Details I am getting below mentained RFC Error
com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: An exception occurred that was not caught., error key: RFC_ERROR_SYSTEM_FAILURE
     at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:101)
     at com.sap.xss.hr.per.xx.bank.fc.FcPerBankXX.modifyRecord(FcPerBankXX.java:232)
     at com.sap.xss.hr.per.xx.bank.fc.wdp.InternalFcPerBankXX.modifyRecord(InternalFcPerBankXX.java:706)
     at com.sap.xss.hr.per.xx.bank.fc.FcPerBankXXInterface.modifyRecord(FcPerBankXXInterface.java:116)
     at com.sap.xss.hr.per.xx.bank.fc.wdp.InternalFcPerBankXXInterface.modifyRecord(InternalFcPerBankXXInterface.java:237)
     at com.sap.xss.hr.per.xx.bank.fc.wdp.InternalFcPerBankXXInterface$External.modifyRecord(InternalFcPerBankXXInterface.java:313)
     at com.sap.xss.hr.per.us.bank.detail.VcPerBankUSDetail.onFlush(VcPerBankUSDetail.java:212)
     at com.sap.xss.hr.per.us.bank.detail.wdp.InternalVcPerBankUSDetail.onFlush(InternalVcPerBankUSDetail.java:245)
     at com.sap.xss.hr.per.us.bank.detail.VcPerBankUSDetailInterface.onFlush(VcPerBankUSDetailInterface.java:144)
     at com.sap.xss.hr.per.us.bank.detail.wdp.InternalVcPerBankUSDetailInterface.onFlush(InternalVcPerBankUSDetailInterface.java:136)
     at com.sap.xss.hr.per.us.bank.detail.wdp.InternalVcPerBankUSDetailInterface$External.onFlush(InternalVcPerBankUSDetailInterface.java:212)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:492)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:438)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.access$600(FPMComponent.java:78)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.raiseReviewAndSaveEvent(FPMComponent.java:948)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.raiseReviewAndSaveEvent(FPMComponent.java:1111)
     at com.sap.xss.per.vc.detailnavi.VcPersInfoDetailNavi.next(VcPersInfoDetailNavi.java:226)
     at com.sap.xss.per.vc.detailnavi.wdp.InternalVcPersInfoDetailNavi.next(InternalVcPersInfoDetailNavi.java:163)
     at com.sap.xss.per.vc.detailnavi.DetailNaviView.onActionNext(DetailNaviView.java:153)
     at com.sap.xss.per.vc.detailnavi.wdp.InternalDetailNaviView.wdInvokeEventHandler(InternalDetailNaviView.java:161)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
     at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)
     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:319)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:733)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:668)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
     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:860)
     at com.sap.tc.webdynpro.portal.pb.impl.localwd.LocalApplicationProxy.sendDataAndProcessAction(LocalApplicationProxy.java:77)
     at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1299)
     at com.sap.portal.pb.PageBuilder.SendDataAndProcessAction(PageBuilder.java:326)
     at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:868)

Table or view does not exists error while executing select statement

Hi,
I am new to Oracle. I am getting a error while executing the select statement if i give table name without double quotes.
Ex: Select * from Customer;
But working fine when the table name is enclosed within a double quotes.
Ex: Select * from "Customer";
Is there any way to execute the select statement without the double quotes?
Actually I am using NHibernate objects for data access.
Thanks,
Sai

Actually I am using NHibernate objects for data access.And probably that's the problem:
SQL> select * from mytab;
         A
         1
SQL> select * from mYtAb;
         A
         1
SQL> select * from MYTAB;
         A
         1
SQL> select * from MYTAb;
         A
         1Oracle statements are case insensitive and doesn't require double quotes unless the object names are reserved words.
As wrote by others if table is created using double quotes it's name bacomes case-sensitive... and this could be the problem...
Max
[My Italian Oracle blog|http://oracleitalia.wordpress.com/2010/02/05/gestione-degli-errori-in-sql-con-log-errors/]
Edited by: Massimo Ruocchio on Feb 5, 2010 7:08 PM
Added last comment..

ESS Salary Statement PDF Format

Hello,
We are implementing ESS 600 SP11 on EP 7.0 ECC 6.0 and for the Pay Statement when try to send email through the Tools option and select option 'Send as a copy' it opens up the Microsoft Outlook setup but does not show up the document in the Subject as PDF ...then the receiver has to open the document using the Adobe Document option and open it ....has anybody encountered this situation....so that the users do not have to do this extra step...
Any help would be highly appreciated.
Edited by: Shikhil Arora on Oct 17, 2008 5:16 PM
Edited by: Shikhil Arora on Oct 17, 2008 5:17 PM

I have a similar problem with Adobe Reader 7, but if I try it on a different PC with Adobe Reader 8 (including the updated browser plug-in) it correctly opens the Outlook message with a file called "unknown.pdf" attached.
You might want to try upgrading to the later version.......

Salary Statement doesnot work

Dear all:
we met a very urgent issue about our sap portal configuration.
i installed a sap portal 7.00 SP11 and the backend system is ECC6.0.
others functions are working now , but "salary statement" doesnot work.
i got this following error after pressed salary statement , so pls help me !
The initial exception that caused the request to fail, was:
 java.lang.ArrayIndexOutOfBoundsException: -1
 at com.sap.mw.jco.JCO$Record.getString(JCO.java:12761)
 at com.sap.aii.proxy.framework.core.JcoBaseTypeData.getElementValueAsString(JcoBaseTypeData.java:669)
 at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClass.getAttributeValueAsString(DynamicRFCModelClass.java:427)
 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)
 ... 45 more
best Regards
scott

Dear James:
thank you very much for your feedback !
i reconfigured the ESS in the backend system , now the error info disappeared.
but i got the other error info:
Error when calling method INIT of class CL_HRXSS_REM 
i have no idea for this error info now .
can you give me some instruction?
thanks again!
best Regards
scott

"SAP_PAYSLIP_US does not exist" error in Salary statement iView of ESS

Hi all,
We have SAP EP7.0 (NW 2004s) with the ESS business package for MySAPERP 2005.Most of our iViews of the business package are working fine,but some are givig problems.
When we try to launch the Salary Statement iView under BEnefits and Payments Workset we get the "SAP_PAYSLIP_US does not exist" error.
The form name SAP_PAYSLIP_US is active and also we have specified the form name in the SPRO settings.
If we change the form name (for e.g.UF01) then the error displayed is "UF01 does not exist".
Can anyone point out as to what the problem is.
Is there any settings we are missing?
Thanks,
Pradeep Shetty

Hi To all!
The Form SAP_TIMESLIP doesn't exist. The correct form to use in the feature HRFOR is SAP_TIM_99_0001 or SAP_TIM_99_0002.
Activate the form in transaction HRFORMS.
SAP didn't release the form SAP_TIMESLIP.
Hope this information is usefull.
Sónia

ESS Salary statemenr: Form Does not exist error

Hi Experts,
As mentioned in may threads, I have changed the form name for salary statement to the custom form name in SPRO- --> HRFOR
But the portal displays "Form does not exist" error. Could not find a solution in any existing post on sdn.
Urgent help needed.
Thanks,
Shobhit

Hi,
If your payslip form is desinged in PE51, then follow these steps.
Employee Self-Service-> Service-Specific Settings-> Benefits and Payment-> Salary Statement-> Form Using HR Forms Editor (PE51)
a. Edit Feature HRFOR: Maintain the constant $CEDT$ for MOLGA 40 RCLAS +01(03).
b. Enter Payslip variant in EDTIN feature
c. Maintain smartform name in EDPDF
If your payslip form is designed in HRFORMS, then enter the form name in HRFOR feature and enter the variant in EDTIN.
Cheers!!
Ashutosh

No Form Exists error in ESS salary statement

Similar Messages

Maybe you are looking for