360 degrees appraisal system
From: "Schwartz, Ken"
kschwar@rwjf.org
To: "'OraHRMS-L@mail-list.com'" OraHRMS-L@mail-list.com
Date: Tue, 29 Jun 1999 15:29:50 -0400
Subject: [orahrms-l] 360 Degree Feedback Appraisal System
Has anyone implemented a 360 degree appraisal system with Oracle HR?
If so, please contact me ASAP!
Thanks and regards,
Ken Schwartz
Site: 609-720-7529
Cell: 404-226-6334
Seniority - computing of
Subject: [orahrms-l] Computing Seniority
From: "BERNARD (ERP)" BAILBL@bcps.k12.md.us
Date: Wed, 2 Jun 1999 15:36:44 -0400
I have a client who wants seniority information calculated on the fly by the
Oracle HRMS/Payroll application. I am considering mauling around several
different ways to approach this task, however, I wanted to find out if
anyone else had addressed such and issue?
Bernard
Bernard L.Bailey
ERP Implementation Team
(410)545-1903/4/5
From: Charles Neal [SMTP:CGNeal@ci.las-vegas.nv.us]
Sent: Thursday, June 03, 1999 7:33 PM
To: 'BERNARD (ERP)'
Subject: RE: [orahrms-l] RE: Computing Seniority
Could you be more specific on what you mean by "on the fly".
This could mean different things.
From: BERNARD (ERP)
Sent: Friday, June 04, 1999 8:47 AM
To: 'Charles Neal'
Subject: RE: [orahrms-l] RE: Computing Seniority
Yes! The customers organization is made up of employees from several
different unions. Therefore, they would like the initial value i.e. the
start date placed in the DB, and then the seniority calucualtions to take
place and be updated on a regular basis. This would also include defining
rules that would enable a person to change unions and, and quite possibly
restart seniority calculations over again.
Bernard
Internal Promoting gives errors
From: "Bui, Loann" lBui@wssc.dst.md.us
Date: Thu, 17 Jun 1999 14:26:17 -0400
Hello out there,
HELP...
We have the following error when we try to promote an employee internally.
This happens when the type is change from Employee and Applicant back to
Employee.
Error: 1. unprocessed non recurring entries will be validated
2. on-update trigger raised unhandled exception
Does anyone encounter the same problem? Any feedback would be greatly
appreciated.
Thanks,
Loann Bui
lBui@wssc.dst.md.us
301/206-8711
From: "Schwartz, Ken" kschwar@rwjf.org
Date: Thu, 17 Jun 1999 14:38:24 -0400
You just cannot change the person type because you want to. There is
processing behind the scenes that prohibits you from doing what I think you
are attempting.
If the current person type is 'Employee and Applicant' and you terminate the
application, then the system will generate a person type of 'Employee and
Ex-Applicant'. If you terminate the employee, you will get a person type of
'Ex-employee and Applicant' unless you terminate the application as well.
In other wordsw, there are system processes that must be adhered to. Please
contact me directly if you have additional questions.
Regards,
Ken Schwartz
HR Consultant
Site: 609-720-7529
Cell: 404-226-6334
From: Sandy Honigsberg Sandy.Honigsberg@orange.co.il
Date: Sun, 20 Jun 1999 09:08:44 +0200
It's possible that you may have skipped a procedural requirement.
If you want to change the current active assignment to the Application's
assignment,
you must first change the Application's status to accepted. Then (after at
least one day has
elapsed for Datetrack purposes) you may change the person type. When you try
to commit, the system
will ask you whether to update the current assignment. Answering no to this
question will lead to the creation
of a second active assignment.
Sandy
From: Greg.Hoover@IFLYATA.COM
Date: Mon, 21 Jun 1999 08:35:46 -0500
There was an excellent paper presented at this year's Spring OAUG Conference
titled "In the Beginning, There Were Applicants: Oracle HR's Applicant
Tracking". This presentation included a step by step explanation of what
needs to be done to convert Applicants to Employees.
Greg Hoover
Systems Engineer
American Trans Air