Enabling ESS in HRMS

Hi Gurus,
I am new to the Employee Self Service (ESS). I have worked in Form based HRMS but never worked in ESS. When I am trying to access the ESS responsibility, it says I do not have privileges to use this responsibility. I checked with our administrator, we have all required licenses but still I do not see any ESS related screens. Am I missing any profile option change or any other thing?
Any clue will be highly appreciated.
Thanks,
CAH

Hey Sharath,
Thanks for your response.
I checked the profile option and it was set to "No". I set it to "Yes" but still I am getting following error :
You have encountered an unexpected error. Please contact the System Administrator for assistance. Click here for exception details.
When i click on the exception details link, it shows me lots of Java Null pointer exceptions. Any help??
Thanks,
CAH

Similar Messages

How to enable security in HRMS

Hello
I want to know is there any way we can enable security in HRMS such a way that we can hide/mask National Identification Number/Salary etc from application and also from back end.
Thanks!

Security could be enable in HRMS in various ways . Using Security profile in Oracle HRMS controls the list of Employees that are visible to a given user from “Employee/Person Screen”.
For hide/mask National Identification Number/Salary information you can go with Form personlization.
Thanks

Enabling ESS/webdynpro

To enable ess for a basic poc, are there a list of essential web dynpro's to enable so we can get a url to call this web dynpro? for example (personal information).
Thanks in advance for your time.
Edited by: Dhana Vajja on Oct 6, 2010 5:08 PM

>
Dhana Vajja wrote:
> To enable ess for a basic poc, are there a list of essential web dynpro's to enable so we can get a url to call this web dynpro? for example (personal information).
>
> Thanks in advance for your time.
>
> Edited by: Dhana Vajja on Oct 6, 2010 5:08 PM
hi Dhana,
not really, to test ess you basically need install the entire SAP Business package, which would include installation components at both the ABAP / r3 system and the netweaver Portal stack. the wiki below describes how basis can implement the package. at the bottom includes some information on more recent business package version. basically you need to download and install 1.4 ESS business package from service markertplace........
http://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=31476

How to enable ESS link in portal

I need the enable ESS link or provide access permission of ESS in my portal.what can i do for that.can anyone help me?
Thanks in advance.
S.Ramesh

Hi RK,
I will try to sum up as much as I can and limit to repeat whats already mentioned above (as they are whats needed in certain steps of implementing ESS).
1) Go to the SAP MarketPlace and via there, you can proceed to SAP PC (or use this https://www.sdn.sap.com/irj/sdn/contentportfolio).
There are 3 BP for ESS, choose the BP with suit your EP and backend system. Click on the text and you can see the below:
a) Primary Backend System
b) Portal Release
c) iView Runtime Technology
To see your EP version, goto http://<host>:<port>/sap/monitoring/SystemInfo. There you'll find something like sap.com/SAP-JEE 7.00 SPxx, this means, you're on Netweaver 7.00 (formerly 2004s), otherwise you'll see 6.40 (that's Netweaver 2004).
2) Deploy the selected BP
http://help.sap.com/saphelp_nw70/helpdata/EN/44/fa068634000c4be10000000a11466f/frameset.htm
3) After deploying the BP, you have to maintain the JCo's for ESS to access your backend system which host your HR.
http://help.sap.com/erp2005_ehp_03/helpdata/EN/8c/cb3042366c0521e10000000a155106/frameset.htm
4) In the backend system which host your HR, you have to setup the necessary ESS authorizations. ESS backend are normally to assign SAP_EMPLOYEE_ERP role to employee which is composite role, which contain following roles:
SAP_BC_EMPLOYEE
SAP_BC_ENDUSER
SAP_ESSUSER_ERP
SAP_HR_EMPLOYEE_DE_ERP
SAP_HR_EMPLOYEE_US_ERP
SAP_HR_PA_XF_EXPERT
You can duplicate or maintain the authorization objects for the above mentioned roles (base on what you want them to execute) using PFCG, generate the profiles and complete the user compare.
In summary, your setup Portal for your ESS users to display what they can see via the ESS BP and you can customise what you want them to see (ESS BP provide standard ESS iviews, pages, workset and role but you can create your own page, workset or role and delta link the provided ESS iviews). From the backend system (HR), you set what your ESS users can do via authorisation roles mentioned above. Once you have setup the above, your ESS users can start with their ESS activities.
P.S: As also mentioned above SSO is also a plus point for your users as then they will not have to login when they try to access ESS (backend system) via the Portal.
Hope that helps.
Ray

Enable ESS over the internet but not the MSS

Hello gurus!!!
I have a few questions that I need to get clarified. We have a Portal server and we installed ESS and MSS business packages on it. Now, our requirement is that we just need to expose ESS applications over the internet and not the MSS applications. When a user gets logged into the portal, the user might be assigned a MSS role and also an ESS role. But when this user tries to login to the portal away from work (ie over the internet), the user should be denied access to the MSS applications but should be allowed to access only the ESS applications.
How can we enable this on one portal server?
Thanks a lot!!
~~~LB

I know its not my Network or ISP because I have RealVNC Enterprise connecting with no issues internally nor outside of my network and it uses the same VNC port 5900 so it can't be that.
ARD only uses port 5900 for observation and control. For other functions ARD uses port 3283. So you may need to open and forward that port as well, or verify that your ISP and other locations aren't blocking.
Regards.

What skills needed to enable ESS and MSS in ECC6.0?

We are upgrading to ECC6.0 from 5.0. We have been using MSS and ESS (old ITS version of ESS) for 5 to ten years. What skillsets does my HCM IT team need in order to enable this functionality? I have been trying to find classes on BSP pages and Webdynrpo without success.

Jim
On ECC 6.0 with EHP 4, you would need Business Package 1.41 for ESS/MSS.
Lets call it right, its not EP 7, its called NW 7.0. Yes, upgrading to NW 7.0 is required for EHP 4.
Once again, EHP 4 is too fresh to implement. Recommended solution is ECC 6 with EHP 3, Business Package 1.3 and NW 7.0.
Apply the latest service patches for a smoother ride.
For functional activities, refer to http://help.sap.com/erp2005_ehp_04/helpdata/en/42/fbded750e61febe10000000a422035/frameset.htm to know whats new in EHP 4.
Regards
Yash

Enabling ESS user to enter Bank information

Hi All,
I am new to SAP portal 7.3 version. My requirement is to make the ess user to enter his/her bank details for the first time and after that this should not be editable. But in the portal there is no option to add the bank details as like in others( ie. ADD option in ADDRESSES).
How to make it available?
Thanks in Advance
Vengadesh R

Hi,
You will have to enhance the infotype. Refer the links below. It might help.
http://scn.sap.com/community/erp/hcm/employee-self-service/blog/2014/06/30/enhancement-of-standard-infotype-in-ess-personal-profile-ehp-5-and-above
http://scn.sap.com/community/erp/hcm/employee-self-service/blog/2012/10/10/enhancing-infotype-0009-using-de-coupled-frame-work-in-ess
Regards,
Navya

Can I use SAP HR to drive ESS Portal user creation?

Hello
We are implementing a new instance of SAP HR and Portal for ESS and MSS and I am not sure of all the steps that need to be completed so any guidance / tips would be greatly appreciated.
Company currently has an LDAP - but not used extensively. Not all employees currently in LDAP as not all have network ids. All employees will have a SAP account to enable ESS (via Kiosks etc). ESS iViews in Portal will call SAP HR and possibly SAP BW. We have an instance of SAP already and user admin maintained via CUA - this will continue.
Scenario:
My initial thoughts are that we try to use SAP HR as the leading system to drive the ESS Portal users and access. Basically I want to create the user in SAP and assign them an ESS SAP role... then through syncronization have the user created in the Portal and have the correct ESS Portal assigned (in the Portal)
My thinking so far is to go the following way;
1) Create User Master Record in SAP (SU01)
2) Hire employee into the org structure (via HR processes)
3) Populate Infotype 0105 with SAP username
4) Populate Infortype 1016 - with SAP role to be assigned to allow ESS access (not sure about this aspect) or role could be assigned in 1) above
I am not sure of the next steps - I think there must be a way in an SAP table to map the ESS SAP role to the ESS Portal Role (is this via WP3R?)
then I am hoping that a standard job can be run (is this RSLDAPSYNC_USER) that will create the user in the Portal (UME?) and assign the correct Portal role ?
(obviously configuration needed)
For MSS and HR Power users - we would continue to assign SAP roles via SU01.
Can anyone assist with;
- Is my thinking correct in terms of how this should / could work?
- in SAP how can I map SAP Roles to Portal Roles ?
- will syncronization in SAP create the user in Portal and assign the role ? what do I need to configure?
Thanks in advance

Dear Michale,
I just dont know if this can throw some light on your prob.'
In our Orgn we had around 250 ess users and 200 sapr/3 users. Some of the r/3 users also logon to ess via their r/3 uname and password.
What we have done is like follows:
1. Created a role for only the ess users ZHRESS. For this i asked the HR functional people with sap_all profile to do all the job which the ESS users are supposed to do and tracer the authorization via tcode st01. We created the role on the basis of this trace report.
2. For the purely ESS users we created the users via tcode HRUSER and assigned then with the above role.
3. For the R/3 users who are supposed to avail the ess facility we assigned them with the role ZHRESS role in addition to the other roles assigned to them to carry out their normal R/3 transactions. Then we mapped their R/3 uname to their employee no via PA30 infotype 105.
4. Tcode HRUSER saved time which would have consumed had we done it via su01 and moreover it picked Name etc data from the HR master table. In HRUSER tcode , setting the user attributes helps to define what roles the users are to be assigned, what should be their initial password etc.
Pl let me know if it satisfies you querry.
Regards

ESS Maintain own data only

Hi Expert,
Any switch to enable ESS user to display his/her own data?
My requirment is that user should be able to view his/her own data but not data of other.
We have defined communication 105 with a corresponding id.
If we grant permission on infotype 8 to that user id
That user would be able to not only view his/her own data but also everyone's data (of course we have grant access to PA20).
Is there any way to control he/she can only acces own data.

Lewis,
Although the structural authorization example will work, there's a simpler way. For the ESS users, you must assign the authorization object P_PERNR for the infotypes (and subtypes) and that you want them to see only their own data for, and make sure you do not assign them P_ORGIN for those infotypes.
Before P_PERNR is effective, though, you must activate the authorization check for this object. You do this with transaction OOAC, changing the value for AUTSW PERNR to 1.
P_PERNR comes into play when a user tries to access infotype data against their own personnel number. For other personnel numbers, P_ORGIN is used.
--Matt

HELP NEEDED: ESS Sick Leave Workflow

Hi ESS/MSS Gurus,
Good day!
I am a newbie workflow consultant currently working on enabling ESS-MSS for a client. In summary, here are their requirements:
1. Leave Requests and Clock In/Out Corrections - Upon initiation of employee request, the work item is sent to the manager for approval. Regardless of the decision (either approve or reject), the employee will be notified via an email notification
2. Sick Leave Requests - upon initiation of employee request, the work item is sent to the company doctor for approval. Regardless of the decision (either approve or reject), both the employee and his/her immediate manager will be notified via an email notification
Here are some details regarding how I went about it:
1. Leave Requests and Clock In/Out Corrections - Created a copy of workflow WS12300111 and included send mail steps after TS12300097 (Approval Process) to notify the work item initiators.
2. Sick Leave Request - Created a copy of workflow WS12300111 and included send mail steps after TS12300097 (Approval Process). The approval process is pointed to the Position Company Doctor. After which a step was inserted after the approval process which uses a customized method (using FM SWX_GET_MANAGER) to determine the employee's manager. Then send mail steps are executed for the employee and the manager
3. Clock Corrections and Sick Leave/Leave Requests belong to the same Rule Group
During testing in our sandbox client I was able to successfully test all of the workflows. However, when I migrated the changes into our pseudo-QA system, I cannot launch the Sick Leave workflow from ESS. I encountered the following errors in PTARQ (standard leave request and clock in/out correction are ok):
1. Scenario 1: applied leave coincides with the working time of the employee
   "Document created with information: P2 848: Absence encompasses planned work time
2. Scenario 2: when only the total nmber of hours is entered for the applied sick leave date
   "No document created: HRTIM_ABS_REQ 094 Indentical clock times were adjusted, Check the entries"
3. Scenario 3: applied leavedoues not coincide with the working time
   "Document created with warning" HRTIM00BLPRETRO 001 Time entry triggers retroactive accounting in payroll"
For all cases, no work item was created in the back end.
I would like to tap unto your wealth of knowledge and experience on how to address such errors. I need to determine if this is a misstep in the workflow, HCM, or ESS/MSS configuration to better isolate the errors.
Your immediate response is highly appreciated.
Regards,

you dont need a custom WF first of all, You can directly use standard one cause we have a standard mail program
called rptarqemail
ie
The mails will be directly triggered to the mail address once you run rptarqemail.
Please check if you are running the report using the option since last
run. The procedure is usually this :
1. Create a Leave Request
2. Execute the report RPTARQEMAIL.
3. Approve the Leave Request.
4. Execute the report RPTARQPOST.
5. Execute the report RPTARQEMAIL.
Now to determine different approvers for different types of leave you can use the option of badi PT_GEN_REQ
IF_EX_PT_GEN_REQ~FIND_RESP_AND_DEFAULT_NEXT_PRC.
Method FIND_RESP_AND_DEFAULT_NEXT_PRC of badi
PT_GET_REQ might be utilised here.
Please have a look at the method
CL_PT_REQ_SEARCH_NEXT_P~SEARCH_NEXT_PROCESSOR.
If you are implementing the badi then make sure you copy all the methods
and implement the one, as mentioned.
also note that
Standard Leave request application offers the following options to
determine the Next agent. This specifies whether and how the next agent
of a leave request is to be determined.
Last Agent: The system reads from the database the last agent to have
had requests from this employee.
Line Manager: The system uses the organizational model to determine the
agent.
Last Agent, Then Line Manager: If no agent is entered in the database,
the system then uses the organizational model to determine the agent.
No Calculation/Manual Entry: The system does not determine a next agent.
Employees can enter an agent manually.
However if the customer has a different requirement, the BADI PT_GET_REQ
method FIND_RESP_AND_DEFAULT_NEXT_PRC is provided for this purpose.
the message you get is correct and its a information message which will not stop leave request, they depend upon customisation which can be hidden too
check here
http://wiki.sdn.sap.com/wiki/display/ERPHCM/LeaveRequestCustom+Messages

Multiple records for infotype with TC1

Hi all,
We have maintained use case A4 for mailing address in ESS.
Strangely, one of our end users, has two overlapping mailing address records! The user had a mailing address record which he edited in ESS. This edited record appears in the backend as a new record. So now the user sees two records in the backend - both with a different start date, but the same end date of 12/31/9999, instead of seeing the first record as delimited. And now when he tries to edit his mailing address in ESS, he gets an RFC error.
Ideally for TC1, a user cannot have two overlapping records and the first record gets delimited to accomodate the updated record as the current record.
Any idea, why this could be happening? We are unable to replicate this issue at our end as this scenario seems impossible for an infotype with TC1.
TIA!
Regards,
Diana

ideally it should have delimited the records, but can check how the enduser created the record?
TC1 can use A1,A4,B1,B4
TC2 can use A1,A2,A3,A4,A5,B1,B2,B4,B5
TC3 can use A6,B3
Note this
A: A record can be created specifying the valid start and/or end date Multiple records can exist.. By default the ESS scenario's will allow you specify the start date as today or future date. If you wish to enable ESS scenario's to accept a start date in the past, Business Add-in "HRXSS_PER_BEGDA" can be implemented.
For more information, please refer to IMG activity "Change Default Start Date".
B: A record can be created without specifying the valid start and/or end date. Multiple records are not possible.
A4: Variant of A1, Difference to A1 being, "New <infotype/subtype>" button will always be available on the overview screen of the concerned scenario. E.g., suitable in Permanent address.
A6: Multiple infotype records of the same type (e.g. other bank) may exist for an employee at the same time. "New <infotype/subtype>" button will always be available on the overview screen of the concerned scenario. E.g., suitable in Other bank.

OIM Reconciliation with eBusiness Suite

Im seeing the following error on enabling the (eBusiness HRMS Trusted Reconciliation) task. I havent configured SSL between OIM and eBusiness suite. Will that be a problem ?
What are the exact steps to be followed for the reconciliation task?
Thanks
ERROR,30 Jul 2009 14:55:50,437,[OIMCP.EBSER],================= End Stack Trace =
======================
ERROR,30 Jul 2009 14:55:50,437,[OIMCP.EBSER],================= Start Stack Trace
=======================
ERROR,30 Jul 2009 14:55:50,437,[OIMCP.EBSER],oracle.iam.connectors.ebs.hrms.task
s.EmployeeReconciliationTask : init
ERROR,30 Jul 2009 14:55:50,437,[OIMCP.EBSER],
ERROR,30 Jul 2009 14:55:50,437,[OIMCP.EBSER],Description :
ERROR,30 Jul 2009 14:55:50,437,[OIMCP.EBSER],oracle.iam.connectors.common.Connec
torException:
at oracle.iam.connectors.common.vo.ITResource.<init>(Unknown Source)
at oracle.iam.connectors.ebs.hrms.tasks.EmployeeReconciliationTask.init(
Unknown Source)
at com.thortech.xl.scheduler.tasks.SchedulerBaseTask.run(Unknown Source)
at com.thortech.xl.scheduler.core.quartz.QuartzWrapper$TaskExecutionActi
on.run(Unknown Source)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
dSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.security.Security.runAs(Security.java:41)
at Thor.API.Security.LoginHandler.weblogicLoginSession.runAs(Unknown Sou
rce)
at com.thortech.xl.scheduler.core.quartz.QuartzWrapper.execute(Unknown S
ource)
at org.quartz.core.JobRunShell.run(JobRunShell.java:178)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.j
ava:477)
Caused by: oracle.iam.connectors.common.ConnectorException:
... 11 more
Caused by: Thor.API.Exceptions.tcColumnNotFoundException
at Thor.API.tcMetaDataSet.getStringValue(Unknown Source)
... 11 more

Complete Log:_
DEBUG QuartzWorkerThread-4 OIMCP.EBSER - oracle.iam.connectors.ebs.hrms.tasks.EmployeeReconciliationTask : init:: STARTED
DEBUG QuartzWorkerThread-4 OIMCP.EBSER - oracle.iam.connectors.common.dao.OIMUtil : OIMUtil():: STARTED
DEBUG QuartzWorkerThread-4 OIMCP.EBSER - oracle.iam.connectors.common.dao.OIMUtil : OIMUtil():: FINISHED
INFO QuartzWorkerThread-4 OIMCP.EBSER - oracle.iam.connectors.ebs.hrms.tasks.EmployeeReconciliationTask : init : Task Name: eBusiness HRMS Trusted Reconciliation
DEBUG QuartzWorkerThread-4 OIMCP.EBSER - oracle.iam.connectors.common.vo.ScheduledTask : getScheduledTaskDetails():: STARTED
DEBUG QuartzWorkerThread-4 OIMCP.EBSER - oracle.iam.connectors.common.vo.ScheduledTask : getScheduledTaskDetails():: FINISHED
INFO QuartzWorkerThread-4 OIMCP.EBSER - oracle.iam.connectors.ebs.hrms.tasks.EmployeeReconciliationTask : init : Task Scheduler attributes :: {Resource Object=eBusiness Person, Target Date Format=MM/dd/yyyy hh:mm:ss, User Type=End-User, Query Name=ReconcileCurrentPersons, Batch Size=1000, Person Type Look Up Definition=Lookup.EBS.HRMS.PersonTypes, Query Properties File=C:\OIM\xellerate\XLIntegrations\EBSER\config\ebsERQuery.properties, Query Filter Lookup Definition=Lookup.EBS.HRMS.QueryFilters, IT Resource Name=EBS-HRMS-APPS12, Task Name=eBusiness HRMS Trusted Reconciliation, Organization=Xellerate Users, Last Execution Time=0, Recon Lookup Definition=Lookup.EBS.HRMS.Recon}
DEBUG QuartzWorkerThread-4 OIMCP.EBSER - oracle.iam.connectors.ebs.hrms.tasks.EmployeeReconciliationTask : initializeAndValidateScheduledTaskParams:: STARTED
DEBUG QuartzWorkerThread-4 OIMCP.EBSER - oracle.iam.connectors.ebs.hrms.tasks.EmployeeReconciliationTask : initializeAndValidateScheduledTaskParams : Number of schedule task parameters: 13
DEBUG QuartzWorkerThread-4 OIMCP.EBSER - oracle.iam.connectors.ebs.hrms.tasks.EmployeeReconciliationTask : initializeAndValidateScheduledTaskParams : Scheduled Task Key [0] : Resource Object
DEBUG QuartzWorkerThread-4 OIMCP.EBSER - oracle.iam.connectors.ebs.hrms.tasks.EmployeeReconciliationTask : initializeAndValidateScheduledTaskParams : Scheduled Task Key [1] : Target Date Format
DEBUG QuartzWorkerThread-4 OIMCP.EBSER - oracle.iam.connectors.ebs.hrms.tasks.EmployeeReconciliationTask : initializeAndValidateScheduledTaskParams : Scheduled Task Key [2] : User Type
DEBUG QuartzWorkerThread-4 OIMCP.EBSER - oracle.iam.connectors.ebs.hrms.tasks.EmployeeReconciliationTask : initializeAndValidateScheduledTaskParams : Scheduled Task Key [3] : Query Name
DEBUG QuartzWorkerThread-4 OIMCP.EBSER - oracle.iam.connectors.ebs.hrms.tasks.EmployeeReconciliationTask : initializeAndValidateScheduledTaskParams : Scheduled Task Key [4] : Batch Size
DEBUG QuartzWorkerThread-4 OIMCP.EBSER - oracle.iam.connectors.ebs.hrms.tasks.EmployeeReconciliationTask : initializeAndValidateScheduledTaskParams : Scheduled Task Key [5] : Person Type Look Up Definition
DEBUG QuartzWorkerThread-4 OIMCP.EBSER - oracle.iam.connectors.ebs.hrms.tasks.EmployeeReconciliationTask : initializeAndValidateScheduledTaskParams : Scheduled Task Key [6] : Query Properties File
DEBUG QuartzWorkerThread-4 OIMCP.EBSER - oracle.iam.connectors.ebs.hrms.tasks.EmployeeReconciliationTask : initializeAndValidateScheduledTaskParams : Scheduled Task Key [7] : Query Filter Lookup Definition
DEBUG QuartzWorkerThread-4 OIMCP.EBSER - oracle.iam.connectors.ebs.hrms.tasks.EmployeeReconciliationTask : initializeAndValidateScheduledTaskParams : Scheduled Task Key [8] : IT Resource Name
DEBUG QuartzWorkerThread-4 OIMCP.EBSER - oracle.iam.connectors.ebs.hrms.tasks.EmployeeReconciliationTask : initializeAndValidateScheduledTaskParams : Scheduled Task Key [9] : Task Name
DEBUG QuartzWorkerThread-4 OIMCP.EBSER - oracle.iam.connectors.ebs.hrms.tasks.EmployeeReconciliationTask : initializeAndValidateScheduledTaskParams : Scheduled Task Key [10] : Organization
DEBUG QuartzWorkerThread-4 OIMCP.EBSER - oracle.iam.connectors.ebs.hrms.tasks.EmployeeReconciliationTask : initializeAndValidateScheduledTaskParams : Scheduled Task Key [11] : Last Execution Time
DEBUG QuartzWorkerThread-4 OIMCP.EBSER - oracle.iam.connectors.ebs.hrms.tasks.EmployeeReconciliationTask : initializeAndValidateScheduledTaskParams : Scheduled Task Key [12] : Recon Lookup Definition
DEBUG QuartzWorkerThread-4 OIMCP.EBSER - oracle.iam.connectors.ebs.hrms.tasks.EmployeeReconciliationTask : initializeAndValidateScheduledTaskParams : Scheduled Task Array for Validation: [Ljava.lang.String;@bae7b0
DEBUG QuartzWorkerThread-4 OIMCP.EBSER - oracle.iam.connectors.common.vo.ScheduledTask : validateMandatoryTaskAttrs():: STARTED
DEBUG QuartzWorkerThread-4 OIMCP.EBSER - oracle.iam.connectors.common.vo.ScheduledTask : validateMandatoryTaskAttrs():: FINISHED
INFO QuartzWorkerThread-4 OIMCP.EBSER - oracle.iam.connectors.ebs.hrms.tasks.EmployeeReconciliationTask : initializeAndValidateScheduledTaskParams : Scheduled task Validation : true
INFO QuartzWorkerThread-4 OIMCP.EBSER - oracle.iam.connectors.ebs.hrms.tasks.EmployeeReconciliationTask : initializeAndValidateScheduledTaskParams : Batch Size :: 1000
INFO QuartzWorkerThread-4 OIMCP.EBSER - oracle.iam.connectors.ebs.hrms.tasks.EmployeeReconciliationTask : initializeAndValidateScheduledTaskParams : Last Reconciliation Time: 0
INFO QuartzWorkerThread-4 OIMCP.EBSER - oracle.iam.connectors.ebs.hrms.tasks.EmployeeReconciliationTask : initializeAndValidateScheduledTaskParams : Target Date Format =MM/dd/yyyy hh:mm:ss
INFO QuartzWorkerThread-4 OIMCP.EBSER - oracle.iam.connectors.ebs.hrms.tasks.EmployeeReconciliationTask : initializeAndValidateScheduledTaskParams : Resource Object =eBusiness Person
INFO QuartzWorkerThread-4 OIMCP.EBSER - oracle.iam.connectors.ebs.hrms.tasks.EmployeeReconciliationTask : initializeAndValidateScheduledTaskParams : User Type =End-User
INFO QuartzWorkerThread-4 OIMCP.EBSER - oracle.iam.connectors.ebs.hrms.tasks.EmployeeReconciliationTask : initializeAndValidateScheduledTaskParams : Organization =Xellerate Users
DEBUG QuartzWorkerThread-4 OIMCP.EBSER - oracle.iam.connectors.ebs.hrms.tasks.EmployeeReconciliationTask : initializeAndValidateScheduledTaskParams : Checking existence of Organization Name Xellerate Users in OIM
DEBUG QuartzWorkerThread-4 OIMCP.EBSER - oracle.iam.connectors.ebs.hrms.tasks.EmployeeReconciliationTask : initializeAndValidateScheduledTaskParams : Row count for Organization: 1
INFO QuartzWorkerThread-4 OIMCP.EBSER - oracle.iam.connectors.ebs.hrms.tasks.EmployeeReconciliationTask : initializeAndValidateScheduledTaskParams : Person Type Look Up Definition =Lookup.EBS.HRMS.PersonTypes
DEBUG QuartzWorkerThread-4 OIMCP.EBSER - oracle.iam.connectors.common.dao.OIMUtil : getLookUpMap():: STARTED
DEBUG QuartzWorkerThread-4 OIMCP.EBSER - oracle.iam.connectors.common.dao.OIMUtil : getLookUpMap() : LookUpName : Lookup.EBS.HRMS.PersonTypes
DEBUG QuartzWorkerThread-4 OIMCP.EBSER - oracle.iam.connectors.common.dao.OIMUtil : getLookUpMap():: FINISHED
DEBUG QuartzWorkerThread-4 OIMCP.EBSER - oracle.iam.connectors.ebs.hrms.tasks.EmployeeReconciliationTask : initializeAndValidateScheduledTaskParams : personTypeMap ={Contractor=Consultant, Participant=Full-Time, Contingent Employee=Part-Time, Employee=Full-Time}
INFO QuartzWorkerThread-4 OIMCP.EBSER - oracle.iam.connectors.ebs.hrms.tasks.EmployeeReconciliationTask : initializeAndValidateScheduledTaskParams : Recon Lookup Definition =Lookup.EBS.HRMS.Recon
INFO QuartzWorkerThread-4 OIMCP.EBSER - oracle.iam.connectors.ebs.hrms.tasks.EmployeeReconciliationTask : initializeAndValidateScheduledTaskParams : Query Filter Lookup Definition =Lookup.EBS.HRMS.QueryFilters
INFO QuartzWorkerThread-4 OIMCP.EBSER - oracle.iam.connectors.ebs.hrms.tasks.EmployeeReconciliationTask : initializeAndValidateScheduledTaskParams : Query Name: ReconcileCurrentPersons
INFO QuartzWorkerThread-4 OIMCP.EBSER - oracle.iam.connectors.ebs.hrms.tasks.EmployeeReconciliationTask : initializeAndValidateScheduledTaskParams : Query File Path/Name: C:\OIM\xellerate\XLIntegrations\EBSER\config\ebsERQuery.properties
DEBUG QuartzWorkerThread-4 OIMCP.EBSER - oracle.iam.connectors.ebs.hrms.tasks.EmployeeReconciliationTask : initializeAndValidateScheduledTaskParams : Scheduled Task Attribute Set : [Resource Object, Target Date Format, User Type, Query Name, Batch Size, Person Type Look Up Definition, Query Properties File, Query Filter Lookup Definition, Organization, Last Execution Time, Recon Lookup Definition]
DEBUG QuartzWorkerThread-4 OIMCP.EBSER - oracle.iam.connectors.ebs.hrms.tasks.EmployeeReconciliationTask : initializeAndValidateScheduledTaskParams : Iterator value : java.util.Hashtable$Enumerator@1293e3f
DEBUG QuartzWorkerThread-4 OIMCP.EBSER - oracle.iam.connectors.ebs.hrms.tasks.EmployeeReconciliationTask : initializeAndValidateScheduledTaskParams : Value of Resource Object :eBusiness Person
DEBUG QuartzWorkerThread-4 OIMCP.EBSER - oracle.iam.connectors.ebs.hrms.tasks.EmployeeReconciliationTask : initializeAndValidateScheduledTaskParams : Value of Target Date Format :MM/dd/yyyy hh:mm:ss
DEBUG QuartzWorkerThread-4 OIMCP.EBSER - oracle.iam.connectors.ebs.hrms.tasks.EmployeeReconciliationTask : initializeAndValidateScheduledTaskParams : Value of User Type :End-User
DEBUG QuartzWorkerThread-4 OIMCP.EBSER - oracle.iam.connectors.ebs.hrms.tasks.EmployeeReconciliationTask : initializeAndValidateScheduledTaskParams : Value of Query Name :ReconcileCurrentPersons
DEBUG QuartzWorkerThread-4 OIMCP.EBSER - oracle.iam.connectors.ebs.hrms.tasks.EmployeeReconciliationTask : initializeAndValidateScheduledTaskParams : Value of Batch Size :1000
DEBUG QuartzWorkerThread-4 OIMCP.EBSER - oracle.iam.connectors.ebs.hrms.tasks.EmployeeReconciliationTask : initializeAndValidateScheduledTaskParams : Value of Person Type Look Up Definition :Lookup.EBS.HRMS.PersonTypes
DEBUG QuartzWorkerThread-4 OIMCP.EBSER - oracle.iam.connectors.ebs.hrms.tasks.EmployeeReconciliationTask : initializeAndValidateScheduledTaskParams : Value of Query Properties File :C:\OIM\xellerate\XLIntegrations\EBSER\config\ebsERQuery.properties
DEBUG QuartzWorkerThread-4 OIMCP.EBSER - oracle.iam.connectors.ebs.hrms.tasks.EmployeeReconciliationTask : initializeAndValidateScheduledTaskParams : Value of Query Filter Lookup Definition :Lookup.EBS.HRMS.QueryFilters
DEBUG QuartzWorkerThread-4 OIMCP.EBSER - oracle.iam.connectors.ebs.hrms.tasks.EmployeeReconciliationTask : initializeAndValidateScheduledTaskParams : Value of Organization :Xellerate Users
DEBUG QuartzWorkerThread-4 OIMCP.EBSER - oracle.iam.connectors.ebs.hrms.tasks.EmployeeReconciliationTask : initializeAndValidateScheduledTaskParams : Value of Last Execution Time :0
DEBUG QuartzWorkerThread-4 OIMCP.EBSER - oracle.iam.connectors.ebs.hrms.tasks.EmployeeReconciliationTask : initializeAndValidateScheduledTaskParams : Value of Recon Lookup Definition :Lookup.EBS.HRMS.Recon
DEBUG QuartzWorkerThread-4 OIMCP.EBSER - oracle.iam.connectors.ebs.hrms.tasks.EmployeeReconciliationTask : initializeAndValidateScheduledTaskParams:: FINISHED
DEBUG QuartzWorkerThread-4 OIMCP.EBSER - oracle.iam.connectors.ebs.hrms.tasks.EmployeeReconciliationTask : init : Schedule Task Validation: true
DEBUG QuartzWorkerThread-4 OIMCP.EBSER - oracle.iam.connectors.common.vo.ITResource : ITResource:: STARTED
DEBUG QuartzWorkerThread-4 OIMCP.EBSER - oracle.iam.connectors.common.vo.ITResource : ITResource : IT Resource Key :81
DEBUG QuartzWorkerThread-4 OIMCP.EBSER - oracle.iam.connectors.common.vo.ITResource : ITResource : Inside the exception block,spd_field_name is not found
DEBUG QuartzWorkerThread-4 OIMCP.EBSER - oracle.iam.connectors.common.vo.ITResource : ITResource : itResourceAttrName = Connection Retries
ERROR QuartzWorkerThread-4 OIMCP.EBSER - ====================================================
ERROR QuartzWorkerThread-4 OIMCP.EBSER - oracle.iam.connectors.common.vo.ITResource : ITResource : column svp_field_value not found
ERROR QuartzWorkerThread-4 OIMCP.EBSER - ====================================================
ERROR QuartzWorkerThread-4 OIMCP.EBSER - ====================================================
ERROR QuartzWorkerThread-4 OIMCP.EBSER - oracle.iam.connectors.common.vo.ITResource : ITResource : null
ERROR QuartzWorkerThread-4 OIMCP.EBSER - ====================================================
ERROR QuartzWorkerThread-4 OIMCP.EBSER - ================= Start Stack Trace =======================
ERROR QuartzWorkerThread-4 OIMCP.EBSER - oracle.iam.connectors.common.vo.ITResource : ITResource
ERROR QuartzWorkerThread-4 OIMCP.EBSER - ITResource initialization failed
ERROR QuartzWorkerThread-4 OIMCP.EBSER - Description :
ERROR QuartzWorkerThread-4 OIMCP.EBSER - oracle.iam.connectors.common.ConnectorException:
at oracle.iam.connectors.common.vo.ITResource.<init>(Unknown Source)
at oracle.iam.connectors.ebs.hrms.tasks.EmployeeReconciliationTask.init(Unknown Source)
at com.thortech.xl.scheduler.tasks.SchedulerBaseTask.run(Unknown Source)
at com.thortech.xl.scheduler.core.quartz.QuartzWrapper$TaskExecutionAction.run(Unknown Source)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.security.Security.runAs(Security.java:41)
at Thor.API.Security.LoginHandler.weblogicLoginSession.runAs(Unknown Source)
at com.thortech.xl.scheduler.core.quartz.QuartzWrapper.execute(Unknown Source)
at org.quartz.core.JobRunShell.run(JobRunShell.java:178)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:477)
Caused by: Thor.API.Exceptions.tcColumnNotFoundException
at Thor.API.tcMetaDataSet.getStringValue(Unknown Source)
... 11 more
ERROR QuartzWorkerThread-4 OIMCP.EBSER - ================= End Stack Trace =======================
ERROR QuartzWorkerThread-4 OIMCP.EBSER - ================= Start Stack Trace =======================
ERROR QuartzWorkerThread-4 OIMCP.EBSER - oracle.iam.connectors.ebs.hrms.tasks.EmployeeReconciliationTask : init
ERROR QuartzWorkerThread-4 OIMCP.EBSER -
ERROR QuartzWorkerThread-4 OIMCP.EBSER - Description :
ERROR QuartzWorkerThread-4 OIMCP.EBSER - oracle.iam.connectors.common.ConnectorException:
at oracle.iam.connectors.common.vo.ITResource.<init>(Unknown Source)
at oracle.iam.connectors.ebs.hrms.tasks.EmployeeReconciliationTask.init(Unknown Source)
at com.thortech.xl.scheduler.tasks.SchedulerBaseTask.run(Unknown Source)
at com.thortech.xl.scheduler.core.quartz.QuartzWrapper$TaskExecutionAction.run(Unknown Source)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.security.Security.runAs(Security.java:41)
at Thor.API.Security.LoginHandler.weblogicLoginSession.runAs(Unknown Source)
at com.thortech.xl.scheduler.core.quartz.QuartzWrapper.execute(Unknown Source)
at org.quartz.core.JobRunShell.run(JobRunShell.java:178)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:477)
Caused by: oracle.iam.connectors.common.ConnectorException:
... 11 more
Caused by: Thor.API.Exceptions.tcColumnNotFoundException
at Thor.API.tcMetaDataSet.getStringValue(Unknown Source)
... 11 more
ERROR QuartzWorkerThread-4 OIMCP.EBSER - ================= End Stack Trace =======================
ERROR QuartzWorkerThread-4 XELLERATE.SCHEDULER.TASK - Class/Method: SchedulerBaseTask/run encounter some problems:
oracle.iam.connectors.common.ConnectorException:
at oracle.iam.connectors.ebs.hrms.tasks.EmployeeReconciliationTask.init(Unknown Source)
at com.thortech.xl.scheduler.tasks.SchedulerBaseTask.run(Unknown Source)
at com.thortech.xl.scheduler.core.quartz.QuartzWrapper$TaskExecutionAction.run(Unknown Source)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.security.Security.runAs(Security.java:41)
at Thor.API.Security.LoginHandler.weblogicLoginSession.runAs(Unknown Source)
at com.thortech.xl.scheduler.core.quartz.QuartzWrapper.execute(Unknown Source)
at org.quartz.core.JobRunShell.run(JobRunShell.java:178)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:477)
Caused by: oracle.iam.connectors.common.ConnectorException:
at oracle.iam.connectors.common.vo.ITResource.<init>(Unknown Source)
... 10 more
Caused by: oracle.iam.connectors.common.ConnectorException:
... 11 more
Caused by: Thor.API.Exceptions.tcColumnNotFoundException
at Thor.API.tcMetaDataSet.getStringValue(Unknown Source)
... 11 more

Link Between Oacle Payroll and Oracle Payables

Hi,
We have installed Oracle Payroll and OraclePayable.
I would like to know the link between Oracle Payroll and Oracle Payable i.e. If i run a Payroll process, does the same affect a Cheque Payment that i can see in Oracle Payable?
Can the same Payment format be used by Payroll and Payable?
If i use International HRMS, can i reconcile Payroll with Cash Management, as the GL Cash account field is not enabled for International HRMS on the Organisation Payment method screen?
Thanks in Advance.
Regards,
Anish Daniel

Hi,
We have installed Oracle Payroll and OraclePayable.
I would like to know the link between Oracle Payroll and Oracle Payable i.e. If i run a Payroll process, does the same affect a Cheque Payment that i can see in Oracle Payable?
Can the same Payment format be used by Payroll and Payable?
If i use International HRMS, can i reconcile Payroll with Cash Management, as the GL Cash account field is not enabled for International HRMS on the Organisation Payment method screen?
Thanks in Advance.
Regards,
Anish Daniel

EP Versions and SAP HR

My company is currently running a 4.6C R/3 (HR) release with an EP5.0. We are in the process of replacing our EP5.0, but are unsure if we are able to utilize the NetWeaver 04/EP SP 13 due to our 4.6C backend.
I have read numerous documents, but have not found anything that truly says what version of EP is compatible with our 4.6C HR system.
Does anyone know what is the maximum release of EP that I can run with a 4.6C backend? Can I use the newest Netweaver 04 releases?
Thanks!
Brad

You will have all of the functionality you have in the old portal. The business packages that enable ESS and MSS through the portal have changed. I haven't done HR in a while but if you look at the content catalogue here in SDN you should be able to find screen shots and documentation for the packages.

ESS - Benefits - Open enrollment (Concurrent employment is enabled)

We are trying to set up ESS open enrollment. After adding/editing/changing plans --> review enrollment --> Save.
On saving, getting an error "rfc_error_system_failure" on the ESS screen.
Checked with ST22 for the error details. The name of runtime error is "uncaught exception" and the exception is "CX_HRPA_VIOLATED_PRECONDITION".
Based on a Similar thread on the forums --> Link : [Re: CX_HRPA_VIOLATED_PRECONDITION using HR_INFOTYPE_OPERATION to insert rec; and Sap note # 493984 , the error seems to be related with concurrent empoyment.
Analysis:
1. If CE is disabled, there is no error - open enrollment works fine both in R/3 (HRBEN0001) and via ESS
2. If CE is enabled," open enrollment" in R/3 using HRBEN0001 - there is no error.
3. Error occurs only when "open enrollment" is accessed through ESS, when CE is enabled.
Would like to know if some one can share their experience on using ESS open enrollment when CE is switched on?
Version details: ECC 6.0 (support pack level 22 for SAP-HR and EA-HR), EP 7.0 , ESS BP 1.0
Thanks,
Javed.

Problem solved after deploying note # 1020389

Enabling ESS in HRMS

Similar Messages

Maybe you are looking for