RPTARQEMAIL not working in ESS

Hi,
In ESS RPTARQEMAIL is not working for leave request.
The entries is shown when i send leave request but when i run it the email doesnt get sent.
Regards
Priya

Hi Prakash
This is the end of the dev_jrfc.trc from the abap/j2ee webdynpro server:
Error file opened at 20050608 101523 British Summer Time Rel 6.40
Error> occured >Wed Jun 08 10:15:23,406< >RfcGetException rc (7) message: The system is unable to interpret the SSO ticket received
<RfcGetException
Error> occured >Wed Jun 08 10:17:28,544< >RfcGetException rc (7) message: The system is unable to interpret the SSO ticket received
<RfcGetException
The portal dev_jrfc.trc does not report any errors.
Other information I should have mentioned: EP uses LDAP for user directory, the ABAP system uses its own user management, the J2EE on the ABAP server uses its own user management. The user I am testing with is the same name in all 3 systems and has full admin permissions in each.
Thanks, Fergus

Similar Messages

UserExit not working on ESS

Hi,
I have added a Check on Infotype 0006 and its working on R/3, but not working on ESS. We are on ECC 6.0. Any ideas?

Hi,
Instead of finding the user exit why dont you try to use the BADI.
Just use below 2 methods to find the appropriate BADI and you will get hte solution by your own.
Method 1:
Go to Tranaction: SE24.
open class CL_EXITHANDLER
Open the method " GetInstance"
Put Break point in the statement
call method cl_exithandler=>get_class_name_by_interface
Now execute the Transaction which you need teh BDC it will automatically stops at the the method. In debugging mode double click on the variable: " exit_name" It will return the BADI Name.
Method 2:
find the Package name and go to the tranaction SE84.
Enter the package name
inside the left navaigaiton panel there is one option " Enhancements" click on this enhancement and then enter the package name and execute it. you will get hte number of enhancement.
Thanks,
Chidanand

F4 help key does not work in ESS on ITS in Portal

Hello All,
F4 help key is not working in all iviews in ESS in Portal.When i try to press it nothing happens and no pop up appears,kindly please suggest wt might be the cause of this error? Iam tired struggling with this issue and not able to trace out reason for the same.My Email Id is [email protected] .Plz revert at earliest.
regards,
Saumya

Hi,
This kind of problem is known when webgui is being started from an IAC, e.g. HRWPC_FC_EXEC
You have to set parameter ~webgui_popups 1 in the service file of this IAC.
BR,
Disha.
Pls reward points for helpful answers.

BADI HRPAD00INFTY is not working in ESS

Hi Gurus,
I have a requirement for Infotype 0006 at the time of saving or updating or deleting the infotype record. I used BADI HRPAD00INFTY for this. It is working fine if we go through PA30 T-code.
If I enter the records into infotype 0006 through ESS then this BADI is not triggering. Tried in SDN and found that for ESS we need to use BADI HRPAD00INFTYBL. In this my problem is how can we get whether it is updation or deletion or creation mode?
Otherwise can any one provide me another BADI is available for this scenario which will work through ESS.
Thanks,
SC

If you are trying to use this BADI and you don't have access to the current operation being executed (INS, MOD, DEL etc), you can always have access by using the PSYST structure used on the main program of the infotype you are working with.
You just have to use a field-symbol to get access.
FIELD-SYMBOLS: <FS> TYPE PSYST.
ASSIGN('(MP000100)PSYST') TO <FS>.
CASE <FS>-IOPER.
WHEN 'MOD'.
ENDCASE.

Exit Button not working in ESS

Hi All,
We have configured ESS in our landscape. When I go to any Overview/Edit/Review Page (in W-4 Tax, Add/Change dependents etc..), the Exit button which is present is not working. When I click the Exit button, it doesn't exit the current view, but instead stays at the current location.
Can anyone tell me the reason for this strange behaviour? Also, where should I make the code level changes for the Exit button work.
Any kind of help would be greatly appreciated.
Regards,
Adren

Hi Apparo,
In onAction method of the Exit button, a call is made to the TargetExitApplication as follows:
fpm.navigate(wdThis
.wdGetFcNavigationInterface()
.getNavigationTargetExitApplication());
Also, the Exit button does work in the Address Overview/Edit/Review Page, but not in W-4 Tax and Benefits Enrollment.
Any help on this problem !!!
Regards,
Adren

Buttons/Links not working in ESS standard application

Hi Experts,
We have implemented ESS module in the portal. Here we have created a view via delta link tracer that contains less number of overview content. In this new view we just have links for "leave", Payment and Personal information links only. This was the requirment of the client. Now a few links inside the above mentioned links are not working. For example if i click on "Leave" and then "Quota overview" there comes a screen where an Exit button is there. This exit button is not working at all. The screen remains the same on pressing the button. Similarly inside "paymen", the link payment summary is not responding. The screen remains the same when we click on payment summary. Is it related to configuration of these buttons. We are using the standard ESS application and have not at all modified the same.
Best Regards,
KM

Note that
While creating an iView instance there are two option
-paste
-paste as delta link
You should choose paste as delta link option.
Please check the link for more information-
http://help.sap.com/saphelp_NW04s/helpdata/en/f5/eb515d0e6a11d7b84900047
582c9f7/frameset.htm
'Exit' button feature comes into picture when you consider that
application should use home page customizing feature.

Approve link not working in ESS/MSS UWL portal

Hi experts,
we are using portal 7.3 with ess/mss.
in mss when user is approving a leave request, he is not ale to proceed
after few steps as one link "pprove another request" is not working.
this i a standrd portal scren in UWL. please suggest.
Thanks a lot in advance.

Hello,
This should be possible with some UWL configuration. Please check the following forum post: http://forums.sdn.sap.com/thread.jspa?threadID=1677777
Kr,
Julien

SSO not working in ESS/MSS in ERP 2004

I have installed the Business Packages ESS 60.2 and MSS 60.1.2 on EP6 SP9. Another server has the Web AS ABAP 6.40 system and J2EE running the ESS and MSS Web Dynpro apps. It all works fine without SSO. When I change the JCO Destinations for the application data to ticket instead of username/password I get the following error on testing:
com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: The system is unable to interpret the SSO ticket received
This error also occurs when accessing the webdynpro app directly or through the portal. NB. The portal SSO does work in the case of calling an R/3 transaction or calling webdynpro app iview that does not in turn make an RFC call to the ABAP system. I have followed the SAP help on "Scenario: SSO Between Portal, Web Dynpro, and ABAP Systems".
Any ideas appreciated
Fergus

Hi Prakash
This is the end of the dev_jrfc.trc from the abap/j2ee webdynpro server:
Error file opened at 20050608 101523 British Summer Time Rel 6.40
Error> occured >Wed Jun 08 10:15:23,406< >RfcGetException rc (7) message: The system is unable to interpret the SSO ticket received
<RfcGetException
Error> occured >Wed Jun 08 10:17:28,544< >RfcGetException rc (7) message: The system is unable to interpret the SSO ticket received
<RfcGetException
The portal dev_jrfc.trc does not report any errors.
Other information I should have mentioned: EP uses LDAP for user directory, the ABAP system uses its own user management, the J2EE on the ABAP server uses its own user management. The user I am testing with is the same name in all 3 systems and has full admin permissions in each.
Thanks, Fergus

Used dc and public part concept not working in ess

Hi,
I tried using the ess address dc(of US country) as used dc in w4 dc(US country) and did all steps of making address dc as public part and added it as used DC in W4, when i tried to get the address dc context in to w4 by calling the read method( of Fc CC) of address DC using the (Fc IC of address DC) which is added in w4 VcW4Overview CC as used component and defined it as usagecomponent and called the readmethod.But i am getting the below error.
Country/Structure do not match application Country .
com.sap.pcuigp.xssfpm.java.FPMRuntimeException: Country/Structure do not match application country
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.per.helpers.MessageHelper.raiseException(MessageHelper.java:43)
com.sap.xss.hr.per.us.address.fc.wdp.InternalFcPerAddressUS.readRecord(InternalFcPerAddressUS.java:615)
     at com.sap.xss.hr.per.us.address.fc.FcPerAddressUSInterface.readRecord(FcPerAddressUSInterface.java:150)
     at com.sap.xss.hr.per.us.address.fc.wdp.InternalFcPerAddressUSInterface.readRecord(InternalFcPerAddressUSInterface.java:229)
     at com.sap.xss.hr.per.us.address.fc.wdp.InternalFcPerAddressUSInterface$External.readRecord(InternalFcPerAddressUSInterface.java:305)
     at com.sap.xss.hr.per.us.address.overview.VcPerAddressUSOverview.onBeforeOutput(VcPerAddressUSOverview.java:267)
     at com.sap.xss.hr.per.us.address.overview.wdp.InternalVcPerAddressUSOverview.onBeforeOutput(InternalVcPerAddressUSOverview.java:275)
     at com.sap.xss.hr.per.us.address.overview.VcPerAddressUSOverviewInterface.onBeforeOutput(VcPerAddressUSOverviewInterface.java:158)
     at com.sap.xss.hr.per.us.address.overview.wdp.InternalVcPerAddressUSOverviewInterface.onBeforeOutput(InternalVcPerAddressUSOverviewInterface.java:140)
     at com.sap.xss.hr.per.us.address.overview.wdp.InternalVcPerAddressUSOverviewInterface$External.onBeforeOutput(InternalVcPerAddressUSOverviewInterface.java:224)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.callOnBeforeOutput(FPMComponent.java:603)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:569)
     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
I am using US country application so all backend configuration should be set, the address and w4 are working fine as out of box.
The read method sends the infty infotype 0006 as input paramenter to RFC Hrxss_Per_Read_P0006_Us_Input, i tried executing this rfc from se37 by giving infotype 0006 but its throwing the exception , but from portal from address iview its working fine.Please send your comments on this.
thanks,
yogi

Hi Yogi ..
How did u resolved this error !! I am getting the same error ..
Pls suggest !!
POints for sure !

Transporting to QA is not working for ESS application.

Hi ,
I have modified the DC ESSUSfam. and activated the code , its working fine in Dev server, But while transporting to QA , it's went successfully but changes does not effect, checked SDM and found that old ear file is still running.
Please tell me If i direclty deploye the EAR file thru SDM, will it work. Also tell me if there is any other solution.
we have EP6.0 SP 21.
Thanks & Regards
Manoj Sahoo

Yes, you can deploy the ear file directly using SDM in QA portal.

Appraisal template standard buttons not working via ESS/MSS

Hi experts,
The error which I am facing in appraisal template is as follows
When I click on any button on appraisal template no action takes place.
Kindly let me know how can I resolve this error.
we are using BSP application HAP_DOCUMENT.
according to me page fragment 'document_buttons.htm' (Method CONVERT_BUTTON_TO_UI) contains the code for button creation and button handling
the page fragment 'document_buttons.htm' is getting triggered when page is initialized but it is not triggering when button is clicked.
Additional info that might be useful to resolve the issue:
1) While viewing appraisal template's web layout in t-code PHAP_CATALOG_PA.
I am facing following script error.
This error reappears when I click on any standard button For eg SAVE
2) We are currently using IE 8
3) We recently upgraded ECC system from ECC 6.0 to ECC 6.0 / EHP 6 (ECC 6.6)
4) I checked SICF and corresponding services are active
Thanks in advance

Hi Adrian,
Design2008 service is inactive in my system.when activated temporarily I was not able to see previous page (Blank page was displayed) in my appraisal application.
For BSP application HAP_document, i checked SICF->default host->SAP->BC->BSP->SAP->HAP_document.This service is active.
The image which I have attached with my question is appraisal template's web layout in t-code PHAP_CATALOG_PA.
regards
Ninad

ESS is not working properly after upgrade from 4.7 to ECC6.0

ESS Scenario in 4.7
4.7 Scenario:
The IMG configuration u201CWork and Life Eventsu201D is done to map them with the PZM3 service (Home Page) to get them as different folders/links on the home page as given below:
List of Services used to set up ESS:
Sl.No     Functionality     Service/EWT/URL Name     Standard/ Customized     Type
1     Home Page     PZM3                                          Standard                 Service
2     Inbox                     BWSP                                          Standard                 Service
3     Calendar                     BWCA                                          Standard                 Service
4     Whou2019s Who     PZ01                                          Standard                 Service
5     CPF Display     http://192.168.0.2:7070/omcpf             NA                                  URL
6     Payslip Display     ZPAYSLIP_USER                          Customized                Service
7     Section 80C     PZ88                                          Standard                EWT
8     Section 80                     PZ80                                          Standard                EWT
9     Form 16                     HRESSIN_F16                          Standard                EWT
10     Address                     PZ02                                             Standard                EWT
11     Bank Information     PZ03                                          Standard                Service
12     Open Appraisals     Not Available                           NA                                 Service
13     Emergency Address     PZ05                                           Standard                 EWT
14     Family/Dependents     PZ12                                           Standard                 EWT
15     Personal Data     PZ13                                               Standard                  EWT
16     Previous Employers     PZ28                                           Standard                 EWT
17     Apply Leave     WS20000081                           Standard               Service
18     Leave Overview     WS01000109                           Standard              Service
19     Leave Balance     PZ09                                             Standard              Service
20     Loan Application     ZLOAN                                          Customized              Service
ECC6.0 Scenario:
In ECC6.0, flow based services are no more supported by ECC6.0 and Dynpro based services are supported.PZM3 (Home Page) is a flow based service.
There is no replacement provided for PZM3 service, so the IMG configuration is not possible for u201CWork and Life Eventsu201D.
OSS ticket raised, but no solution for IMG u201CWork and Lifeu201D events.
List of Services would be used to set up ESS:
Sl.No     Functionality     Service/EWT/URL Name     Standard/ Customized    Type
1     Home Page     PZM3                                       Standard                           service
1)this service is not available
2)SAP does not provide any replacement.
3)PZM3 is not supported in Integrated ITS. No direct solution proposed.
4)Given reference of few notes.
5) A dynpro (module pool screen) based IAC needs to be created and links need to be provided on that screen. Generated HTML page is modified to access the services via URL or by OKCODE.
Screenshot attached below.
2           Whou2019s Who                 PZ01                                      Standard                             Service
1)this service Available
2)Not Working properly.
3) The problem may be because of the dependency with SAP Query. Either Query is missing in the new system or not having the proper authorization. Needs to be debugged and finalized.
7     Section 80C     PZ88      Standard     EWT     Available
8     Section 80      PZ80     Standard     EWT     Available
9     Form 16                HRESSIN_F16     Standard     EWT     Available
10     Address                PZ02     Standard     EWT     Available     Only EWT Available.          Service needs to be created to access the EWT.
11     Bank Information     PZ03     Standard     Service     Available     EWT Available.           Service needs to be created to access the EWT.
12     Open Appraisals     Not Available     NA     Service          EWT Available.           Service needs to be created to access the EWT.
13     Emergency Address     PZ05     Standard     EWT     Available     EWT Available.           Service needs to be created to access the EWT.
14     Family/Dependents     PZ12     Standard     EWT          EWT Available.           Service needs to be created to access the EWT.
15     Personal Data     PZ13     Standard     EWT          EWT Available.           Service needs to be created to access the EWT.
16     Previous Employers     PZ28     Standard     EWT          Service Available
17     Apply Leave     WS20000081     Standard     Service     Available, but not working                                                                               No solution is proposed yet.
18     Leave Overview     WS01000109     Standard     Service     Available, but not working               No solution is proposed yet.
19     Leave Balance     PZ09     Standard     Service     Available, but not working               No solution is proposed yet.

Ya ramakrishna,
Even easier is for you to send us the mail ID of your client. We will do the work, then send them an idoc of message type INVOICE and for you a post card of course.
Please do the needfull,
Julius

User does not exist in this period / ESS does not work anymore ;-(

Hello experts,
starting any ess application on portal side (leave request), I get the follwoing error code:
com.sap.pcuigp.xssfpm.java.FPMRuntimeException: User TESTUSER does not exist in this period
Starting application personal data I get the message: "There are no services in the area."
I know, that this error has often been discussed in this forum. So I check the hints I found, but I could not solve my problem.
The HR user TESTUSER is assigned to the portal user TESTUSER in IT0105 and the user is not exceeded.
TESTUSER got SAP_ALL on HR side.
The error appears for all users, that worked propably a few days before.
Login on portal side and HR works. ESS overview is shown for TESTUSER. For a user that has not a login to HR system it does not appear. So the single singn on (SSO) between portal and HR system seems to work.
The ESS applications worked fine until two days ago. Portal guys said, they had not done any changes on portal side.
Where could the error occure on HR side? How can I recognize if any changes have been made on HR side?
Thank you for your help.

TX HRUSER seems not working.
Using the function 'Set Up and Maintain ESS User (Overview)' in TX HRUSER with my test-PERNR it is shown under 'Employees with deleted users'.
Clicking on it I got the Information:
PERS.NO: 12345678 (i.e.) NAME: Test User FROM: 01.01.2011 TO: 31.12.9999 USER: Name: FROM: TO: User does not exist.
But in IT0105 the PERNR is assigned to user TESTUSER in that period.
When I try to assign PERNR to TESTUSER with TX HRUSER under 'Assign Employees to Existing Users' I read the follwing information:
USER: TESTUSER Name: FROM: 01.01.2011 TO: 31.12.9999 USER GROUP: IT PERS.NO.: NAME: FROM: TO: no employee assigned.
Trying to 'assign employees' I get the message 'Error occurred when creating relationship for user ESSUSER-B to employee'.
Please create the appropriate assignment manually in HR master data.
But I have assigned it manualy in IT 0105.
Concurrent employment (CCURE PAUIX) is not activated.

ESS - Time Accounts- Exit button not working

We have implemented ESS Business Package, the Time Accounts application's Exit button is not working.
When we click on Exit, it is not doing anything. In Development env it is working fine, but when it comes to quality it is not working.
suggest me if we can solve this problem.

Hi Kiran,
We had a same problem with "Exit" button for "Benefits Enrollment" in both dev and quality systems. As a workaround we redirected to the specific iView using WDPortalNavigation.navigateAbsolute on clicking "Exit button".
Hope this helps.
Regards,
Adren

Standard Leave iView of ESS does not work... What to do?

Hi Experts,
We are implementing ESS / MSS. Most of the iViews of ESS are working fine. However, iView of Leave Request is not working.
1) Is it possible that during the portal installation due to some error, some of the components needed for Leave Request has not got installed properly.
2) If yes, can we take the dump / par / WD file of other SAP EP system and import it in my portal.
3) If no, what is the remedy for the solution.
Please suggest. I am getting following message while running application in web dynpro content administration :
An object with ID portal_content/com.sap.pct/srvconfig/com.sap.pct.erp.srvconfig.ess.employee_self_service/com.sap.pct.erp.srvconfig.lea/com.sap.pct.erp.srvconfig.fpmapplications/com.sap.pct.erp.srvconfig.LeaveRequest does not exist.
Regards,
Gary

Hi Pinki,
Case 1:
From content admin --> portal content > Content Provided by SAp>End User Content > Employee Self-service> Iviews--> working time I am getting following error message:
iView : The initial exception that caused the request to fail, was:
   com.sapportals.portal.prt.runtime.PortalRuntimeException: Failed in WD JNDI lookup. javax.naming.NameNotFoundException: No child found in WebDynproContext with name base
    at com.sap.portal.pcm.iview.admin.AdminBaseiView.createAttrSetLayersList(AdminBaseiView.java:357)
    at com.sap.portal.pcm.iview.admin.AdminBaseiView.getAttrSetLayersList(AdminBaseiView.java:205)
    at com.sap.portal.pcm.iview.admin.AdminBaseiView.getCustomImplementation(AdminBaseiView.java:148)
    at com.sap.portal.pcm.admin.PcmAdminBase.getImplementation(PcmAdminBase.java:530)
    at com.sapportals.portal.ivs.iviews.IviewServiceObjectFactory.getObjectInstance(IviewServiceObjectFactory.java:442)
    ... 40 more
Case 2:
From Content Admin> Webdynpro> Deployed content (int he left side panel) >sap.com> sap.com/ess~lea I am getting following error message:
An object with ID portal_content/com.sap.pct/srvconfig/com.sap.pct.erp.srvconfig.ess.employee_self_service/com.sap.pct.erp.srvconfig.lea/com.sap.pct.erp.srvconfig.fpmapplications/com.sap.pct.erp.srvconfig.LeaveRequest does not exist.:
com.sap.xss.config.FPMInconsistentObjectException: An object with ID portal_content/com.sap.pct/srvconfig/com.sap.pct.erp.srvconfig.ess.employee_self_service/com.sap.pct.erp.srvconfig.lea/com.sap.pct.erp.srvconfig.fpmapplications/com.sap.pct.erp.srvconfig.LeaveRequest does not exist.
Thanks
Gary
     at com.sap.xss.config.pcd.PcdObjectBroker.retrieveObjectInternal(PcdObjectBroker.java:90)
     at com.sap.xss.config.pcd.PcdObjectBroker.retrieveObject(PcdObjectBroker.java:47)
     at com.sap.xss.config.domain.PersistentObjectManager.retrieveObjectInternal(PersistentObjectManager.java:106)
     at com.sap.xss.config.domain.PersistentObjectManager.retrieveObject(PersistentObjectManager.java:80)
     at com.sap.xss.config.FPMRepository.retrieveObjectInternal(FPMRepository.java:83)
     at com.sap.xss.config.FPMRepository.retrieveObject(FPMRepository.java:66)
     at com.sap.pcuigp.xssutils.ccpcd.FcXssPcd.initializeConfiguration(FcXssPcd.java:816)
     at com.sap.pcuigp.xssutils.ccpcd.FcXssPcd.loadConfiguration(FcXssPcd.java:250)
     at com.sap.pcuigp.xssutils.ccpcd.wdp.InternalFcXssPcd.loadConfiguration(InternalFcXssPcd.java:178)
     at com.sap.pcuigp.xssutils.ccpcd.FcXssPcdInterface.loadConfiguration(FcXssPcdInterface.java:138)
     at com.sap.pcuigp.xssutils.ccpcd.wdp.InternalFcXssPcdInterface.loadConfiguration(InternalFcXssPcdInterface.java:148)
     at com.sap.pcuigp.xssutils.ccpcd.wdp.InternalFcXssPcdInterface$External.loadConfiguration(InternalFcXssPcdInterface.java:240)
     at com.sap.pcuigp.xssutils.ccpcd.CcXssPcd.loadConfiguration(CcXssPcd.java:282)
     at com.sap.pcuigp.xssutils.ccpcd.wdp.InternalCcXssPcd.loadConfiguration(InternalCcXssPcd.java:184)
     at com.sap.pcuigp.xssutils.ccpcd.CcXssPcdInterface.loadConfiguration(CcXssPcdInterface.java:115)
     at com.sap.pcuigp.xssutils.ccpcd.wdp.InternalCcXssPcdInterface.loadConfiguration(InternalCcXssPcdInterface.java:124)
     at com.sap.pcuigp.xssutils.ccpcd.wdp.InternalCcXssPcdInterface$External.loadConfiguration(InternalCcXssPcdInterface.java:184)
     at com.sap.xss.essservices.cc.ccesspcd.CcEssPcd.loadConfiguration(CcEssPcd.java:268)
     at com.sap.xss.essservices.cc.ccesspcd.wdp.InternalCcEssPcd.loadConfiguration(InternalCcEssPcd.java:169)
     at com.sap.xss.essservices.cc.ccesspcd.CcEssPcdInterface.loadConfiguration(CcEssPcdInterface.java:115)
     at com.sap.xss.essservices.cc.ccesspcd.wdp.InternalCcEssPcdInterface.loadConfiguration(InternalCcEssPcdInterface.java:124)
     at com.sap.xss.essservices.cc.ccesspcd.wdp.InternalCcEssPcdInterface$External.loadConfiguration(InternalCcEssPcdInterface.java:202)
     at com.sap.pcuigp.xssutils.ccxss.CcXss.loadConfiguration(CcXss.java:209)
     at com.sap.pcuigp.xssutils.ccxss.wdp.InternalCcXss.loadConfiguration(InternalCcXss.java:153)
     at com.sap.pcuigp.xssutils.ccxss.CcXssInterface.loadConfiguration(CcXssInterface.java:112)
     at com.sap.pcuigp.xssutils.ccxss.wdp.InternalCcXssInterface.loadConfiguration(InternalCcXssInterface.java:124)
     at com.sap.pcuigp.xssutils.ccxss.wdp.InternalCcXssInterface$External.loadConfiguration(InternalCcXssInterface.java:184)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:187)
     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:756)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:291)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
     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.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
     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)

RPTARQEMAIL not working in ESS

Similar Messages

Maybe you are looking for