ESS / MSS Calendar

Hi ,
In ECC 5.0, what is needed for Setup and/or Dynpro for a employee in ESS, to maintain a calendar ( which will feed the team calendar of the Manager ) ? Is Working Time needed and a lot of IMG ? or else, ...
Also, what is needed for the Manager to See the calendar ?
Thank's.

Team calender is based on the Org structure of the manager. IE he can view the org unit and persons under his supervision.
EE personal calendar reflects his own team members in the same org unit.
Both calender indicates the absences taken/applied or course attendance etc for better management and macro view of absences and attendances.
Once the ESS and MSS webdynpro is configured then you need to assign the employee to the relevant org unit.
The ESS/MSS basic configurations will enable to view the calendars. If you want to 'restrict' what sort of attendnance and absence to be reflected, then you have to configure in IMG.

Similar Messages

ESS & MSS Team Calendar Customization

Hi Team,
We are implemented ESS & MSS & configured Team Calendar but in that we are facing bellow issues
Can we do customization Team calendar? If it is possible how?
Reporting structure showing wrongly displaying.
    please help me
Regards,
Ajay

Hi Mithun & Jwala,
Thanks for reply, here i am sharing my screen shots please check
We required direct report employees list only should display MSS Team workset
    Emp: Direct report employees only 44 to that manager but in MSS team workset nearly 90 employees
            are displying
I am client side functional consultant, my ESS & MSS project done by other company
Now they left the company I had no much knowledge on the ESS& MSS Team calendar just I had knowledge functional side so please guide me to close my issue
Thanks,
Ajay

Modifying Team Calendar - ESS/MSS

Hi All,
We are in midst of a major implementation and would like to go ahead with very critical requirement.
" We have to modify the team calendar in ESS/MSS application so that they reflect the holidays for oragnization as well in grayed out fashion."
Any ideas as how to go about modifying the team calendar.
TIA,
Vivek

Hi Pradnya,
I am not aware as how this will be carried out.
Any help in this regard will be highly appreciated.
TIA,
Vivek

ESS MSS multiple entry table is not showing up

Hi All,
I have a issue in ESS when user applies leave and cancels the leave. When the user clicks on that day again in the calendar
then unable to see the history of the cancelled leave in ESS Leave application.
multiple entries are there for that day and in the team calender its not showing light blue color.
We are using ESS MSS latest package HR Package and US Payroll.
Swathy

Hello,
Is the posting program being run correctly?
Please check 1104839 - ESS LEA:Wrong Behavior in Change/Delete of Leave
Rgs,
Bentow.

Time management configuration/ ESS MSS configuration documents

hello Xperts,
do any one have Configuration documents for time management and ESS/MSS Pls forward to me
shanker366atgmail.com

Hi,
Time management Config.
The following is the config. document of TM. check the threads u will get some more good responses and close the thread if u find the response is good enough
I think its helpful to u.
IMG  Personnel Time Management  Work Schedules  Define Public Holiday Classes
IMG  Personnel Time Management  Work Schedules  Personnel Subarea Groupings  Group Personnel Subareas for the Work Schedule
IMG  Personnel Time Management  Work Schedules  Personnel Subarea Groupings  Group Personnel Subareas for theDaily Work Schedule
IMG  Personnel Time Management  Work Schedules  Daily Work Schedules  Define Daily Work Schedules
IMG  Personnel Time Management  Work Schedules  Period Work Schedules  Define Period Work Schedules.
IMG  Personnel Time Management  Work Schedules  Day Types  Define Day Types.
IMG  Personnel Time Management  Work Schedules  Day Types  Define Day Types.
IMG  Personnel Time Management  Work Schedules  Day Types  Define Special Days.
IMG  Personnel Time Management  Work Schedules  Work Schedule Rules and Work Schedules  Define Employee Subgroup Groupings
IMG  Personnel Time Management  Work Schedules  Work Schedule Rules and Work Schedules  Define Groupings for the Public Holiday Calendar.
IMG  Personnel Time Management  Work Schedules  Work Schedule Rules and Work Schedules  Set Work Schedule Rules and Work Schedules.
IMG  Personnel Time Management  Work Schedules  Work Schedule Rules and Work Schedules  Generate Work Schedules Manually
IMG  Personnel Time Management  Work Schedules  Planned Working Time  Set Default Value for the Work Schedule.
IMG  Personnel Time Management  Work Schedules  Planned Working Time  Set Default Value for Time Management Status.
IMG  Personnel Time Management  Time Data Recording and Administration  Substitutions  Define Personnel Subareas for Substitution Types.
IMG  Personnel Time Management  Time Data Recording and Administration  Substitutions  Set Defaults for Substitution Types.
IMG  Personnel Time Management  Time Data Recording and Administration  Absences  Absence Catalog  Group Personnel Subareas for Attendances and Absences.
IMG  Personnel Time Management  Time Data Recording and Administration  Absences  Absence Catalog  Define Absence Types.
IMG  Personnel Time Management  Time Data Recording and Administration  Absences  Absence Catalog  Absence Counting  Define Counting Classes for the Period Work Schedule.
IMG  Personnel Time Management  Time Data Recording and Administration  Absences  Absence Catalog  Absence Counting  Rules for Absence Counting (New)  Group Employee Subgroups for Time Quotas.
IMG  Personnel Time Management  Time Data Recording and Administration  Absences  Absence Catalog  Absence Counting  Rules for Absence Counting (New)  Group Personnel Subareas for Time Quotas
IMG  Personnel Time Management  Time Data Recording and Administration  Absences  Absence Catalog  Absence Counting  Rules for Absence Counting (New)  Define Rules for Rounding Counted Absences
IMG  Personnel Time Management  Time Data Recording and Administration  Absences  Absence Catalog  Absence Counting  Rules for Absence Counting (New)  Define Counting Rules
IMG  Personnel Time Management  Time Data Recording and Administration  Absences  Absence Catalog  Absence Counting  Rules for Absence Counting (New)  Define Counting Rules  Deduction rules for Absence quotas
IMG  Personnel Time Management  Time Data Recording and Administration  Absences  Absence Catalog  Absence Counting  Assign Counting Rules to Absence Types.
IMG  Personnel Time Management  Time Data Recording and Administration  Attendances/Actual Working Times  Define Attendance Types.
IMG  Personnel Time Management  Time Data Recording and Administration  Attendances/Actual Working Times  Attendance counting  Rules for Attendance counting (New)  Assign Counting Rules to Attendance Types.
IMG  Personnel Time Management  Time Data Recording and Administration  Managing Time Accounts Using Attendance/Absence Quotas  Time Quota Types  Define Absence Quota Types.
IMG  Personnel Time Management  Time Data Recording and Administration  Managing Time Accounts Using Attendance/Absence Quotas  Calculating Absence Entitlements  Automatic Accrual of Absence Quotas  Permit Quota Generation Without Time Evaluation.
IMG  Personnel Time Management  Time Evaluation  Time Evaluation Settings  Set Personnel Subarea Groupings for Time Recording.
IMG  Personnel Time Management  Time Data Recording and Administration  Managing Time Accounts Using Attendance/Absence Quotas  Calculating Absence Entitlements  Rules for Generating Absence Quotas  Set Base Entitlements  Base Entitlement for Absence Quota Generation.
IMG  Personnel Time Management  Time Data Recording and Administration  Managing Time Accounts Using Attendance/Absence Quotas  Calculating Absence Entitlements  Rules for Generating Absence Quotas  Determine Validity and Deduction Periods.
IMG  Personnel Time Management  Time Data Recording and Administration  Managing Time Accounts Using Attendance/Absence Quotas  Calculating Absence Entitlements  Rules for Generating Absence Quotas  Set Base Entitlements  Define Generation Rules for Quota Selection.
Thanks and Regards,
Revathi.

ESS/MSS Customizations

HI ESS/MSS Gurus,
During our discussions with the client regarding the inherent features of the standard ESS/MSS functionalities, several points were raised, namely:
1. The cumbersome nature of data/request entry - basically they just want all the request filing to occur in one screen. No need to skip screens to review and validate the request
2. No record id to document the request -> they want a means for the user and manager to monitor and track requests using a standardized request numbering system. I believe that the standard solution for ESS/MSS does not have this one in place
3. Ability to extract reports of histories of requests raised (for the employee) and requests reviewed (for the manager)
In our opinion, these items will require heavy customization on both the portal and back end side. We are basically considering a custom table which will store these information and depending on the status of the requests, a request column will be updated with the corresponding values. The request approvals, notifications, and postings are also to be done via ABAP
In designing this solution, we came across some stumbling blocks, specifically on updating the personal and team calendars for leave requests and the employee's schedule for the clock in/out corrections. Hence, we want to check if any of you guys have had experience with customizing the ESS/MSS interfaces (specifically the leave and clock in/out application and approval), and if so, can you help us identify which tables are being updated/read when a leave or clock in/out is created and approved. We already checked the FMs attached to the portal application and the they call several methods and functions; i.e. is there a table/set of tables that you can point us to instead?
Your immediate response is highly appreciated.
Regards,

1. The cumbersome nature of data/request entry - basically they just want all the request filing to occur in one screen. No need to skip screens to review and validate the request
-- Depending on your version less than or equal to ehp5,.. this is true in versions less then ehp5. then ahain until ehp4 any forms that need implementation will need some element of development work so in your particular case the element of develpment could be a little higher to make them all use a single entry screen that gets submitted.
2. No record id to document the request -> they want a means for the user and manager to monitor and track requests using a standardized request numbering system. I believe that the standard solution for ESS/MSS does not have this one in place
-- for any form or process that has workflow attached there is an automatic workflow-id assigned by the system and I believe you can report on these inthe back end... standard workflow fuctionality... why dont you explore this option with your workflo consultant?
3. Ability to extract reports of histories of requests raised (for the employee) and requests reviewed (for the manager)
-- refer to point 2 answer above...
In our opinion, these items will require heavy customization on both the portal and back end side. We are basically considering a custom table which will store these information and depending on the status of the requests, a request column will be updated with the corresponding values. The request approvals, notifications, and postings are also to be done via ABAP
-- I have seen this done previously,... it is not very cumbersome or difficult,. it is just replacing std sap workflow function of assigning identifiers with user specified number ranges... the only advantage here is you get to define specific number ranges for process to get ids from...
In designing this solution, we came across some stumbling blocks, specifically on updating the personal and team calendars for leave requests and the employee's schedule for the clock in/out corrections. Hence, we want to check if any of you guys have had experience with customizing the ESS/MSS interfaces (specifically the leave and clock in/out application and approval), and if so, can you help us identify which tables are being updated/read when a leave or clock in/out is created and approved. We already checked the FMs attached to the portal application and the they call several methods and functions; i.e. is there a table/set of tables that you can point us to instead?
-- I dont see any problems in the assignment of workflow ids to any requests related to leave requests or clockin-out scenarios,.. so unless you are more specific about the nature of errors am not sure anyone can help much...
cheers

NetWeaver Portal and ERP 6.0: BI, ESS/MSS and full Portal on one machine

Hello,
with ERP 6.0 you need a EP Core Portal for BI Java. An other EP Core Portal for HCM ECC/MSS. The iViews from this portal you integrate in the main portal via federated portal. But in this scenario i need to much portals and have a lot of maintenance costs (administration overhead for evry portal). For a small Customer i will build one Portal for all. It is possible e.g. to use the BI Portal with ESS/MSS and as full portal?
Best regards,
Patrick

Hi,
So you would like one BI installation with both the ABAP and the Java-stack with the full BI-functionallity and additionally the XSS-component and set it up to work against the ECC ABAP-only system ?
I think the scenario would actually work, but:
1) You might get future problems if you want to upgrade your BI-system and not the ECC-system.
Is it possible to run the old XSS-components in the new java-stack ?
2) You might get future problems if you want to upgrade your ECC-system and not the BI-system.
What if the new version of the XSS-component demands certain java-components which the BI-system do not have.
So my recommendation is still to run the java-stack on both systems.
ECC with the XSS-java-components and BI with the Bi-java-components.
This way you do not lock yourself into a corner and each system can be upgrade independent of the other.

Backend R/3 connectivity for ESS MSS from portal

Hi,
We are currently in development cycle for ESS/MSS based on portal EP 6.0 SP16 and ERP 2004 in backend. We are trying to find out how the ESS/MSS business package on portal works with backend ESS functionality in ERP 2004. It is more of a connectivity question. We want to know if we expose our portal to internet so that users can login to ESS/MSS from internet, do we need to put backend ERP (ECC 5.0) system also in DMZ? Do we need to open ports between portal and R/3 so that ESS/MSS can work? Or the communication happens using JCO connections and we need not to expose R/3 system.
Also one more specific question? If someone knows how ESS/MSS talks to backend system. At SAP application layer level or database level? I am asking this question to check if I need to open a port to talk to database or I can very well keep 2-3 SAP application server in DMZ and work.
PK

You need to look at the specific business package. For example, ESS for mySAP ERP 2004 says that the technology is Java / Web dynpro, which says that the Java engine uses RFCc to get the data from the backend.
Othe businesss packages may use ITS, which then needs another connection from the user to the ITS server.
Cheers

Creating NWDI track for ESS/MSS

Hi,
I am trying to implement ESS/MSS (600 SP7). For customization I need to import the package on the track in CMS. Import of JEE, JTECHS, BUILDT and PCUIG were successful. When i tried importing ESS and MSS, import is failing. Check-In of both the components are successful but while importing the component under Development tab, its failing. Import of MSS in DTR is successful but CMS is failing.
Below is the log for ESS:
Info:Starting Step Repository-import at 2007-04-10 12:46:13.0591 +5:00
Info:Component:sap.com/SAP_ESS
Info:Version :MAIN_ERP05PAT_C.20070314050106
Info:1. PR is of type TCSSoftwareComponent
Info:propagatable is known in repository, it is not necessary to write the workspacecontent to the DTR
Fatal Exception:com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: VcmFailure received: Internal Server Error [(pre||post)-condition failed: Internal Server Error]:communication error: VcmFailure received: Internal Server Error [(pre||post)-condition failed: Internal Server Error]
com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: VcmFailure received: Internal Server Error [(pre||post)-condition failed: Internal Server Error]
     at com.sap.cms.tcs.client.DTRCommunicator.integrateChangelist(DTRCommunicator.java:393)
     at com.sap.cms.tcs.core.RepositoryImportTask.processRepositoryImport(RepositoryImportTask.java:335)
     at com.sap.cms.tcs.core.RepositoryImportTask.process(RepositoryImportTask.java:578)
     at com.sap.cms.tcs.process.ProcessStep.processStep(ProcessStep.java:77)
     at com.sap.cms.tcs.process.ProcessStarter.process(ProcessStarter.java:197)
     at com.sap.cms.tcs.core.TCSManager.importPropagationRequests(TCSManager.java:376)
     at com.sap.cms.pcs.transport.importazione.ImportManager.importazione(ImportManager.java:227)
     at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.execImport(ImportQueueHandler.java:634)
     at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.startImport(ImportQueueHandler.java:103)
     at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:584)
     at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:560)
     at com.sap.cms.pcs.transport.proxy.LocalCmsTransportProxyLocalObjectImpl0_0.startImport(LocalCmsTransportProxyLocalObjectImpl0_0.java:1252)
     at com.sap.cms.ui.wl.Custom1.importQueue(Custom1.java:1198)
     at com.sap.cms.ui.wl.wdp.InternalCustom1.importQueue(InternalCustom1.java:2215)
     at com.sap.cms.ui.wl.Worklist.onActionImportQueue(Worklist.java:881)
     at com.sap.cms.ui.wl.wdp.InternalWorklist.wdInvokeEventHandler(InternalWorklist.java:2390)
     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:299)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:752)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:705)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:261)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:154)
     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:387)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:160)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(AccessController.java:207)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Info:Step Repository-import ended with result 'fatal error' ,stopping execution at 2007-04-10 12:47:49.0198 +5:00
Regards,
Piyush.
ps: points will be awarded to all helpful answers. )

Hi Bharath
How r u? Hope fine.
I have specified the version above. I am using (ESS 600 SP 7 [P11] & MSS 600 SP 7 [P4]).
Is there anything i can do to resolve the issue in JDBC etc? Whats this AFAIK?
Can u suggest something, a work around, to solve this issue?
Regards,
Piyush.
ps: u can directly mail to my ID, will grant u points for helpful answers. )

Function modules or BAPIs for ESS MSS

Hi Experts,
I am new to HR (ESS/MSS & who's who). I am looking for standard BAPI's and Function Modules that would give me information about an employee's upper level's and lower levels (reporting).
My requirement is to build an Webdynpro Application with taking employee id as user input and display his uplevel's and downlevel's. Also, hyperlink on employee should help me to further navigate to the corresponding employee's information.
Note: I tried to search this forum, but unable to narrow down the required business functions that i require.
Thanks,
Gaurav.

https://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=190743879
RH_GET_MANAGER_ASSIGNMENT

Issue while accessing two web-dynpro application, ESS/MSS and Payroll

Hi All,
We are facing one Critical Server Issue in our systems. Following is the scenerio:-
Our Portal system was having one Application known as German Payroll application. Before last two week one more application of ESS/MSS i.e. Time Management has been deployed to our system.
Now the user has two application with two different roles in the portal.
When user try to navigate from Time Management Application to German Payroll application or German Payroll Application to Time Management Application then they are facing Critical Server Error issue.
But once the user try to refresh using CTRL+F5 then the problem got resolved.
========================================================================
German Payroll applications back end server details:P95.
Time Management Application back end server details: P23
Steps to reproduce the issue:
1-login to portalgot to Employee self service tab-wait for 3-5mins
& than navigate to german payroll applications----& faced crtical
server errors:
Log from deafult trace:-
=======================================================
1.#0021280FECEE0028000000A400005A4B0004A2FA644F345C#1305096215265#com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent#sap.com/tcwddispwda#com.sap.tc.webdyn
pro.progmodel.generation.DelegatingComponent#km048893#2758##n/a##fa2a61757b9911e08e660021280fecee#SAPEngine_Application_Thread[impl:3]
_9##0#0#Fatal#1#/Applications/Xss#
Java###null
[EXCEPTION]
#1#com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException
at
com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:107)
at com.sap.xss.ser.xssmenu.fc.ModelHandler.onInit
(ModelHandler.java:205)
at com.sap.xss.ser.xssmenu.fc.wdp.InternalModelHandler.onInit
(InternalModelHandler.java:428)
at com.sap.xss.ser.xssmenu.fc.FcXssMenu.setPersonnelNumber
(FcXssMenu.java:570)
at com.sap.xss.ser.xssmenu.fc.FcXssMenu.onInit
(FcXssMenu.java:292)
at com.sap.xss.ser.xssmenu.fc.wdp.InternalFcXssMenu.onInit
(InternalFcXssMenu.java:455)
at com.sap.xss.ser.xssmenu.fc.FcXssMenuInterface.onInit
(FcXssMenuInterface.java:165)
System 'P95' is not possible because RFC Metadata was retrieved using
System 'P23'. Please assure you have configured the RFC Connections
properly. A Server restart may
be necessary!#
==============================================================
here is the catch....When user is trying to navigate from ESS tab(using
custom jcos for Backend system P23) to German payroll(backend system
P95) after 3 mins ---getting crtical error...Still its using the
data/metadat jcos connection information of ESS applications from
cache...that you can see in default trace.
PS: Standards Jcos are configured for P23 systems:
====================================================
SAP_R3_HumanResources----created with P23
SAP_R3_HumanResources_MetaData----been created with P23
SAP_R3_SelfServiceGenerics----been created with P23
SAP_R3_SelfServiceGenerics_MetaData----been created with P23
=====================================================
P95----Germman payroll
P23---ESS/MSS
Name of Cutsomn Jcos created for bakcend P95 i.e. german payroll
A-P95
=======================================================
SAP_R3_HumanResources:D95
SAP_R3_HumanResources_MetaData:D95
SAP_R3_SelfServiceGenerics:D95
SAP_R3_SelfServiceGenerics_MetaData:D95 configured with sap-wd-arfc-
useSys.
Name of cutom jcos created for backend ESS/MSS P23
B-P23
=========================================================
SAP_R3_HumanResources_MetaData:X23
SAP_R3_HumanResources:X23
SAP_R3_SelfServiceGenerics:X23
SAP_R3_SelfServiceGenerics_MetaData:X23 configured with sap-wd-arfc-
useSys.
========================================================
Jcos parameter of P23 backend:
JCo Pool Configuration
Maximum Pool Size: 50
Maximum Connections: 100
Connection Timeout (msec.): 10000
Maximum Waiting Time (msec.): 30000
Jcos parameter of P95 backend:
JCo Pool Configuration :
Maximum Pool Size: 5
Maximum Connections: 10
Connection Timeout (msec.): 10000
Maximum Waiting Time (msec.): 30000
===================================================================
After more analyzing the situation we found that one web dynrpo component i.e. pcui_gp~xssutils is common to both the application and it is configured to standard JCO i.e.
SAP_R3_HumanResources
SAP_R3_HumanResources_MetaData
SAP_R3_SelfServiceGenerics
SAP_R3_SelfServiceGenerics_MetaData
My thinking is that this component is giving us the problem.
Please provide your comments and solution to rectify this issue.
Also, let me know in case you need more information.
Thanks in Advance
Kuldeep Verma

Hi
First try a very simple application with nothing in it just one text saying Hello World
Run it and see what happens.
Also check if your url uses FQDN name. something like https:
company.name.co:50000\.......
If you do not use the FQDN it will always show a script error on the bottom and some functions will not work e.g
dropdowns.
regards
Yuval.

ESS/MSS Installation to R/3 4.7 Enterprise

Goodday Guru's,
I've just received a requirement to install and configure ESS/MSS. Backend system is on R/3 4.7 and Portal is on EP 6.0. I have downloaded ESS 50.4 and MSS 60.1_19 for this requirement. There would not be any development work, only out of the box standard ESS/MSS configuration. I believe that most of you out htere have succesfully implemented such a requirement. Would you mind sharing your experience with me? Any step-by-step guide would be very appreciated.
P.S:- Just a quick check. For this requirement, do i need to download ESS/MSS/PCUI for WebDynpro component? I know that it is needed for ERP2004 (ECC 5.0).
Regards,
Johan

Hi Johan
the following is procedure that u need.
if u have all DVD/CD for installation than go by following.
if ur os is win2000 -- SP4 needed or use WIN2003 server
install J2SDK 1.4.2_08 or _09 don't use above.
set JAVA_HOME variable in win2000 enviorenment variable.
set path c:\j2sdk1.4.2_08\bin;
install oracle with no database (do not create any databse during oracle installation, look oracle installation documentation)
apply oracle patch.
set ORACLE_HOME under win2000 enviorenment variable.
set ORACLE_SID under win2000 enviorenment variable.
where sid is ur sap system id i.e EPD
install j2ee server.
install portal.
install CM if u want.
install ITS 6.20 on same system or Other win2000/2003 system (IIS required. look installation document)
create system i.e R3,ITS in portal according to document that i send,
import Buisness package for ESS/MSS into portal,
assign the ESS/MSS role to user in portal.
By default ther is no role for ESS with standard BP's create ur own role and Add tha workset using delta link,
u can find the import content under migrated content-> EP 5.0
regards,
kaushal

SAP IDES ECC 6.0 configuration for ess/mss

Hi,
Iam new to sap . i want to practice various scenarios in ess/mss in my own pc which is installed with ecc 6.0 . what are the configuration to be made in ecc 6.0 for maintaining about 10-20 users for using ess/mss scenarios. i have a knowledge on webdynpro java and little knowledge on ep and using r/3 server. The 10-20 users created should be able to use ess/mss through portal .
So, list the steps configuring for 10-20 users for using ess/mss in ecc ides 6.0 server.
Thanks & regard
prasad

<< Do not post the same question across a number of forums >>

ESS / MSS - is there a way to view Histories of FORMs submitted and processed?

Hi,
We're implementing the ESS / MSS RDS EP 6 (version 3.606 SAP Enterprise Portal scenario).
The project also includes the custom development of a number of Forms that will be integrated into ESS / MSS via iViews.
The customer requires a "HISTORY View" of FORMs for the ESS and MSS users.
It is the historic FORMs themselves that they want to be able to display - or as much of the Key information from the Forms that they can identify specific Form submissions (and not the related Workflows for these forms).
I'm told that there is no HISTORY view for Forms. The history functions for Workflows (in the UWL) is not really suitable for users but only for more technical analysis of workflows.
Does anyone know of a way of getting these history views of Forms without resorting to a custom development? e.g. is there a standard Report or a way of enabling Histories to be maintained and accessible?
Kind Regards
Alan

Hi Alan,
I think the best we could get is Process Browser application.
Can you refer this link and see if this helps.
Also try the WD Application - ASR_PROCESSES_DISPLAY.
Thanks
Raja Sekhar

Error while accessing services of ESS/MSS tabs - URGENT

Hi,
When i am accessing the services under ESS, MSS tabs ie, Leave request, My expenses etc.... i am getting the following error.
A critical error has occured. Processing of the service had to be terminated. Unsaved data has been lost.
Please contact your system administrator.
User XYZ does not exist in this period:
com.sap.pcuigp.xssfpm.java.FPMRuntimeException: User XYZ does not exist in this period
     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.pcuigp.xssutils.pernr.FcEmployeeServices.initPernr(FcEmployeeServices.java:257)
     at com.sap.pcuigp.xssutils.pernr.FcEmployeeServices.onInit(FcEmployeeServices.java:220)
     at com.sap.pcuigp.xssutils.pernr.wdp.InternalFcEmployeeServices.onInit(InternalFcEmployeeServices.java:249)
     at com.sap.pcuigp.xssutils.pernr.FcEmployeeServicesInterface.onInit(FcEmployeeServicesInterface.java:135)
     at com.sap.pcuigp.xssutils.pernr.wdp.InternalFcEmployeeServicesInterface.onInit(InternalFcEmployeeServicesInterface.java:183)
     at com.sap.pcuigp.xssutils.pernr.wdp.InternalFcEmployeeServicesInterface$External.onInit(InternalFcEmployeeServicesInterface.java:243)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:920)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:889)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1082)
     at com.sap.xss.tra.fc.utils.FcTraUtils.onInit(FcTraUtils.java:264)
     at com.sap.xss.tra.fc.utils.wdp.InternalFcTraUtils.onInit(InternalFcTraUtils.java:297)
     at com.sap.xss.tra.fc.utils.FcTraUtilsInterface.onInit(FcTraUtilsInterface.java:122)
     at com.sap.xss.tra.fc.utils.wdp.InternalFcTraUtilsInterface.onInit(InternalFcTraUtilsInterface.java:212)
     at com.sap.xss.tra.fc.utils.wdp.InternalFcTraUtilsInterface$External.onInit(InternalFcTraUtilsInterface.java:428)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:920)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:889)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1082)
     at com.sap.xss.tra.fc.allmytrips.FcTraAllMyTrips.onInit(FcTraAllMyTrips.java:247)
     at com.sap.xss.tra.fc.allmytrips.wdp.InternalFcTraAllMyTrips.onInit(InternalFcTraAllMyTrips.java:543)
     at com.sap.xss.tra.fc.allmytrips.FcTraAllMyTripsInterface.onInit(FcTraAllMyTripsInterface.java:115)
     at com.sap.xss.tra.fc.allmytrips.wdp.InternalFcTraAllMyTripsInterface.onInit(InternalFcTraAllMyTripsInterface.java:348)
     at com.sap.xss.tra.fc.allmytrips.wdp.InternalFcTraAllMyTripsInterface$External.onInit(InternalFcTraAllMyTripsInterface.java:420)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:920)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:889)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1082)
     at com.sap.xss.tra.vc.allmytrips.VcTraAllMyTripsInterface.onInit(VcTraAllMyTripsInterface.java:164)
     at com.sap.xss.tra.vc.allmytrips.wdp.InternalVcTraAllMyTripsInterface.onInit(InternalVcTraAllMyTripsInterface.java:205)
     at com.sap.xss.tra.vc.allmytrips.wdp.InternalVcTraAllMyTripsInterface$External.onInit(InternalVcTraAllMyTripsInterface.java:399)
     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:362)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:700)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:269)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:772)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:707)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:261)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:154)
     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.AbstractApplicationProxy.create(AbstractApplicationProxy.java:220)
     at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1248)
     at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:353)
     at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:551)
     at com.sap.portal.pb.PageBuilder.wdDoRefresh(PageBuilder.java:595)
     at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:826)
     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:136)
     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:299)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:723)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:261)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:154)
     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:387)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:160)
     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)
I am able to access in QAS but not in DEV or Prod.

VV,
This could be case when the payroll for the user XYZ has not be updated till the current period, in which you are trying to access the ESS or MSS tabs.
You can try this.
1. Go to the transaction - PC00_mxy_CLSTR
where xy refers to the MOLGA or the country coding for which the payroll is run.
Observe there till which period for the user XYZ the payroll has been run.
2. If the payroll has not been run for the current period.
Go to transaction PC00_mxy_CALC and by entering the parameters, run the payroll and try doing the same.
Hope this helps!
Regards.
Sandeep Tudumu

ESS / MSS Calendar

Similar Messages

Maybe you are looking for