ORACLE APPLICATIONS ARCHIVES

Topicwise collection of
Postings on Mail Lists
ON
HRMS - PERSONAL INFORMATION



Capturing Info about employee's relations

From: Bijus@mashreqbank.com
To: orahrms-l@mail-list.com
Subject: [orahrms-l]
Date: Mon, 21 Jun 1999 00:28:42 +0400
I have a case where a particular benefit depends on the number of spouse+children and their age. Spouse/Child information is entered through contacts window. Can someone suggest me a method for getting the information of spouse/children and their date of birth, from within the fast formula. I have achieved this using a user defined function, which makes use of the tables HRV_CONTACT_RELATIONSHIPS and PER_ALL_PEOPLE_F. Can someone suggest a way to avoid this function.

Thanks & Regards, Biju Sebastian


Convert Applicants to Employees

From: Bui, Loann [mailto:lBui@wssc.dst.md.us]
Sent: Thursday, June 17, 1999 1:26 PM
To: OraHRMS-L@mail-list.com
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: Greg.Hoover@IFLYATA.COM
To: lBui@wssc.dst.md.us, OraHRMS-L@mail-list.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


From: Sandy Honigsberg Sandy.Honigsberg@orange.co.il
To: "'Bui, Loann'" lBui@wssc.dst.md.us, OraHRMS-L@mail-list.com
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



What API to use to delete Contacts

Date: Mon, 19 Jul 1999 11:23:23 -0700
From: Peter P Lin plin@mail1.jpl.nasa.gov
Subject: HRMS -- What API to Use for Delete Contacts

All,

We have a need of deleting contacts (non-Dependent, non-Beneficiary or non-Payments Recipient). What APIs should we use for deleting those contacts? We are currently running 10.7SC.

Does Oracle support hr_person.delete_a_person API which is used by Oracle's Delete Personal Records Form? Also, what are the things we need to watch out for if we use this API?

Thanks Peter


Multiple cities sharing same ZIP code

Subject: [orahrms-l] HR: Vertex Validation when >1 City Exists for a Given ZIP
From: "Kevin Jarrett" kejarr@copelco.com
Date: Wed, 10 Mar 1999 17:30:44 -0500

Season's Greetings from sunny Mahwah, NJ...

We've got Vertex installed and working in our HR-only instance (10.7SC/16.1) ... but there's a catch. We're having problems with city names where the zip code is 'shared'.

Example: hapless John Q. Employee lives in Weston, FL 33332.

According to our friends at the US Postal Service, http://www.usps.com/ncsc/lookups/lookup_ctystzip.html;

33332 is associated with the following:

Please click here for the table

Note the (DEFAULT) moniker is for Fort Lauderdale, FL.

So....Oracle HR (more correctly, Vertex) will not let me save this person's address record with "Weston" as the city.

We've got the latest Vertex patch from Oracle Support, and I've got a TAR logged...but surely some of you have already dealt with this...anyone...anyone...?

Do I just enter the address as Fort Lauderdale, FL?

Thanks, kj


Subject: RE: [orahrms-l] HR: Vertex Validation when >1 City Exists for a Given ZIP
From: Ken Schwartz kens@dbn.net
Date: Wed, 10 Mar 1999 16:52:08 -0600

KJ:

You need to add the city using the facility in HR that was designed for that purpose. Once you get to the city definition screen, the window asks you for the state, then the county. Once you have entered both of those pieces of data you enter the high and low zip code for that city.

That's all you need.
Regards from snowy St. Louis,
Ken Schwartz


Subject: RE: [orahrms-l] HR: Vertex Validation when >1 City Exists for a G iven ZIP
From: "Kevin Jarrett" kejarr@copelco.com
Date: Wed, 10 Mar 1999 18:24:08 -0500
cc: OraApps-L@cpa.qc.ca, OraHRMS-L@mail-list.com

Hey Ken!

I'm here with Henry Kryszpin (who thanks you for those great cigars at the Q1 kickoff)...and we already tried that. It won't allow us to save the record, because a record for Weston already exists.

Any other thoughts? Remember, we are HR-only with Vertex installed as a precursor to the Oracle/Ceridian interface.

OWWS is already on this, maybe I ought to bump it to a P1...

Thanks, kj


Subject: [orahrms-l] Re: Vertex Validation when >1 City Exists for a Given ZIP
From: "Ken Conway" k_conway@sprynet.com
Date: Wed, 10 Mar 1999 20:20:48 -0600

Kevin:

Hello. Yes, I've run into this before. After you log these TARs with Oracle WWS, be diligent in finding out when these will be incorporated in a patch. Depending on how long you have before going live, you may be able to wait for the patch. Secondly, talk to Support about supplying you a SQL patch that will INSERT or UPDATE the appropriate tables depending on exactly what data you need to insert or modify.

While I do not advocate using SQL directly against the tables without working with Oracle WWS, I have investigated these tables at one of our past clients. Our issues at that client involved several cities that existed in more than one county. However, Oracle did not recognize all of the city/county combinations.

There are several Oracle Payroll tables involved and it is tricky. I know your installation is HR-only so we may need to confirm that these same tables are being used. If you don't get sufficient progress from WWS, please don't hesitate to give me a call and I will be happy to step you through the process.

Hope this helps,
Ken
Ken Conway
BOSS Corporation


Subject: [orahrms-l] RE: HR: Vertex Validation when >1 City Exists for a Given ZIP
From: "Kevin Jarrett" kejarr@copelco.com
Date: Thu, 11 Mar 1999 08:40:50 -0500

Thanks, everyone, for your responses. It appears we have the following options:

Update the requisite tables via patch from Oracle
Update the requisite tables via SQL
Kludge the address (change something) to make it match the data we DO have

Since #1 will take God-knows-how-long, #2 is just a wee bit risky and not upgrade-safe, we are going with #3. Where we can simply change the person's zip code (as in the Weston, FL example) we will do so. If necessary we will change the city name. I'm sure the person's mail will still arrive. It's just a damn shame the HR-only clients get short shrift on deals like this. Without a valid address, the employee will not have a valid tax record.

Also, FYI, our crack on-site Oracle consultant (Henry Kryszpin...discriminating clients ask for him by name) discovered a handy bit of SQL that Oracle provides to validate addresses (City/State/Zip combinations) for employees and work locations. It's called

pyvaladr.sql

and our DBA pulled it off our 10.7 server. We ran it and it works great. You need to have Vertex installed, 'cuz it looks to those tables for info, but it definitely shows you the problem children. Thanks Henry!

Have a brilliant day, -kj-



Duplicate employees

Subject: [orahrms-l] HR/Payroll Duplicate People
From: "Mavis O'Connor" moconnor@IR.ColoState.EDU
Date: Thu, 18 Mar 1999 11:48:13 -0700 (MST)

I'm hoping that those of you who have been on large implementation projects can advise us on how large companies or universities are preventing their users from entering the same person into Oracle HR more than once.

At Colorado State the input of employees is decentralized and it's possible (common) for a student hourly employee to apply for jobs and get multiple concurrent assignments working for more than one organization. Obviously if 2 different organizations enter the same person and these "duplicates" get paid there will be a big mess to unravel and some type of adjustment will need to be made to balances, etc. This can also happen fairly easily if a person is in HR as a "contact" and later becomes employed by the University and subsequently gets entered again because the employing department is unaware that the person already exists as a contact.

I realize that Oracle provides some warning messages for duplicate names, however with a student body of 25,000 and 10,000+ employees we do have several people with the same name.

Specifically, my questions are:

1. How are you detecting, preventing, and identifying duplicate people--preferably before they are paid?

2. If a duplicate person is paid on both person/assignment records under 2 different employee id #s what steps must you follow to adjust all balances (post payroll) and delete one of the duplicate person records?

Mavis O'Connor
Colorado State University
moconnor@ir.colostate.edu


Subject: RE: [orahrms-l] HR/Payroll Duplicate People
From: pkandra@civicdevelopment.com
Date: Thu, 18 Mar 1999 14:18:37 -0500

I'd use the social security # as the employee # if possible. That will go a long way towards preventing duplicate employees. If that's not possible, I'd look into using alerts to periodically (maybe before your payroll process is kicked off) query the PER_PEOPLE_F and PER_ASSIGNMENTS_F tables. If people still slipped through, you can probably reverse their payroll process depending upon when you caught the mistake. That will keep an audit trail by creating negative entries to cancel out the payroll process results. You can then terminate the duplicate assignment.

Hope this helps.


Subject: [orahrms-l] Re: Duplicate people in HRMS
From: "Ken Conway" k_conway@sprynet.com
Date: Thu, 18 Mar 1999 14:41:17 -0600

Mavis:

The Social Security number should be unique for each employee. Oracle HR will allow you to save more than one employee with the same SSN but it should give you a warning. At the time of receiving this warning, this would be the time that I recommend correcting the data. Either the currently entered SSN is incorrect or you must search the other employee records to find who has this same SSN.

Also, if you were to change a SSN for someone who had previously been paid, I would think you could do this. We need to test this and see. Basically, within the database, the payroll run results for an employee ultimately map back to an assignment_id which in turn allows you to map back to the employee through person_id. The good news is that the payroll run results do not map to the SSN.

Having said this, on the People Form, confirm that you do not receive a form error or "Field is protected against update" message. If you get one of these messages, then please call me at one of the numbers below and I will help you diagnose a corrective plan of action.

One more note... You mention that entry of employees is decentralized. I am assuming that the decentralized data entry is still accessing a central Oracle database. If this is not the case, then there will be other issues that we should discuss.

Hope this helps,
Ken
Ken Conway
BOSS Corporation


Subject: RE: [orahrms-l] HR/Payroll Duplicate People
From: sdunnell@usmarine.com
Date: Thu, 18 Mar 1999 17:40:22 -0800
cc: moconnor@IR.ColoState.EDU, OraHRMS-L@mail-list.com

A word of caution about using the SSN as the employee number. If you are going to implement more that just the HR module - you may find that the SSN shows up in places that you don't want it to - whereever the employee # displays. That was a confidentiality/liability problem that caused us to change the employee number to another number that was unique.


Subject: RE: [orahrms-l] HR/Payroll Duplicate People
From: sredrova@es.com
Date: Thu, 18 Mar 1999 19:28:26 -0700
Cc: moconnor@IR.ColoState.EDU, OraHRMS-L@mail-list.com

I want also to add that, specially in a university, a lot of foreign students have temporary SSN that can change with their status. I really don't recommend to use SSN as employee number.



Keeping Contract Employees' Data

Subject: [orahrms-l] Keeping Contract Employee Data in HRMS
From: Cindy Rockwell cindy.rockwell@infocus.com
Date: Tue, 20 Apr 1999 09:05:22 -0700

We are considering maintaining contract employees (paid by a temporary agency) in HRMS and would like to know if anyone has had experience pro or con in doing this.

thanks
cindy rockwell
InFocus Systems


Subject: Re: [orahrms-l] Keeping Contract Employee Data in HRMS
From: Lewis R Cunningham lcunning@lmumail.lmu.edu
Date: Tue, 20 Apr 1999 10:07:56 -0700

It makes sense especially if you are tracking things like equipment and email ids in the HR system. You can even track where they work and what they do by giving them a job of Contractor, in the right org and just don't give them a payroll or salary.

Lewis


Subject: Re: [orahrms-l] Keeping Contract Employee Data in HRMS
From: Julie Simnick eipop@iquest.net
Date: Tue, 20 Apr 1999 16:49:37 -0500

We track both non-agency contract employees and employees paid through temporary agencies in Oracle HR. For Temporary employees we use a Special Information field to track the agency information -- vendor name, bill rate, etc. (if that is important to you). Other than that, we use basically the same screens we use for employees (Address, People, Assignment) but we don't track Salary or Tax information. The only problem I can think of that you may encounter in doing this is with some of your interfaces (if you have any, we have several and for the most part this information does not interface, but only because we do not want it to). Please let me know if I can provide additional information.


Subject: RE: [orahrms-l] Keeping Contract Employee Data in HRMS
From: "Wynne, Matthew" Matthew.Wynne@fmr.com
Date: Tue, 20 Apr 1999 18:25:54 -0400

We have started setting this up in an instance. We need to track time for them. In our situation, the approach we took was to set up separate person status types and user assignment types, but set up as person-type Employee. We did not set up locations for them, so that they couldn't be later added to a payroll by mistake.

MJW



Invalid Special Ceiling on updating assignment

Subject: [orahrms-l] invalid ceiling
From: Steve Silveri ssilver@dpc.com
Date: Thu, 22 Apr 1999 14:22:48 -0700

I am trying to load employees and update assignment criteria using the following paramters:

hr_assignment_api.update_emp_asg_criteria (
p_effective_date => v_hr.hire_date,
p_datetrack_update_mode => 'CORRECTION',
p_assignment_id => v_assign_id,
p_object_version_number =>
v_asg_object_version_number,
p_position_id => v_position_id,
p_job_id => v_job_id,
p_payroll_id => v_payroll_id,
p_location_id => v_location_id,
p_organization_id => v_org_id,
p_pay_basis_id => v_hour_sal_id,
p_special_ceiling_step_id => v_step_id,
p_employment_category => v_emp_cat,
p_effective_start_date => v_eff_start_date,
p_effective_end_date => v_eff_end_date,
p_people_group_id => v_group_id,
p_group_name => v_group_name,
p_org_now_no_manager_warning => v_no_manager_warning,
p_other_manager_warning =>
v_other_manager_warning,
p_spp_delete_warning => v_spp_delete_warning,
p_entries_changed_warning =>
v_entries_changed_warning,
p_tax_district_changed_warning =>
v_tax_district_changed_warning);

When I run this, I get

APP 7379 Invalid Special Ceiling Step.

We have salary grades set up, but not Grade Scales. I don't understand the use of the paramter p_special_ceiling_step_id. Can anyone shed some light on this.


Subject: Re: [orahrms-l] invalid ceiling
From: Lewis R Cunningham lcunning@lmumail.lmu.edu
Date: Thu, 22 Apr 1999 14:28:10 -0700

Is your v_step_id null. If not try explicitly sending it null. If that doesn't work write back and I'll take a better look at it.

Lewis



HR_ASSIGNMENT_API Error APP-6153

Subject: [orahrms-l] HR_ASSIGNMENT_API Error APP-6153
From: Phil Riker pmr2073@ritvax.isc.rit.edu
Date: Fri, 23 Apr 1999 15:36:50 -0400

Has anyone any experience the following error message:

HR_6153_ALL_PROCEDURE_FAIL (PROCEDURE=
pay_us_tax_internal.maintain_wc) (STEP=8)

The "book" says tell your system administrator, which I did, to wit she said "&#%&*^ Oracle!! Can't they give up some real helpful info".


Tracking Assignment Changes

Subject: [orahrms-l] Tracking Assigment Changes
From: "Toni Olivier" Toni_Olivier@i2.com
Date: Mon, 26 Apr 1999 23:33:32 -0500

We are needing to track changes to an Employee's Assignment (i.e. Organization, Job, Supervisor, etc). Specifically, we need to see the old value, the new value, effective date of change, update date, and user name. Can anyone recommend a seeded report or other process for tracking these changes? (we originally thought that Audit Trail would do this, but we have not been successful in getting it to work)

Thanks.


Subject: RE: [orahrms-l] Tracking Assigment Changes
From: "Driver, Paul" p.driver@ic.ac.uk
Date: Tue, 27 Apr 1999 08:03:36 +0100

Toni

Audit trail will do what you want it to do. When i last worked on 10.6 i was sent a patch to get the HR audit trail to work. The patch created synonyms etc. Have you spoken to support about your problem?

Cheers
Paul Driver



On updating Assignment through API, People Group KFF errors

Subject: [orahrms-l] INSERTING People group Keyflex segments in ASSIGNMENT API - ERROR
From: "Gul, Metin" MGul@sigeco.com
Date: Tue, 27 Apr 1999 14:33:27 -0500

Hello,

Sometime ago I heard that when you use API 's to insert Descriptive keyflex fields you have to customize the API validaiton procedures/functions to enable the insertion.

However in my case I am using the hr_assignment_api.update_emp_asg_criteria API to update assignment information.

the thing is if the people group flexfield combination (we have 5 segments) exists in the pay_people_groups table then I am able to use the API without any problem. whenever I am trying to insert segments that do not already exist in the system (in the table as well) it errors out.

I have checked the people group flexfield to make sure that dynamic insertion was allowed even then I am still not able to run the API.

Has anybody experienced a situation like this ??
thanks Metin


Subject: Re: [orahrms-l] INSERTING People group Keyflex segments in ASSIGNMENT API - ERROR !!!
From: Rajesh Babu nrajeshbabu@yahoo.com
Date: Sat, 12 Jun 1999 10:17:45 -0700 (PDT)

Hi All,

I am converting the assignment information & facing the same problem below with People Group flexfield.

I tried giving existing segments of people group for assignment API. But still it says we cant enter the key flex segments.

How should I go about for loading the group field of assignment screen.

Thanks in advance, Rajesh Babu


Subject: RE: [orahrms-l] INSERTING People group Keyflex segments in ASSIGNMENT API - ERROR !!!
From: "Gul, Metin" MGul@sigeco.com
Date: Mon, 14 Jun 1999 09:00:54 -0500

Rajesh,

I just made sure that my combinations for people group existed before I loaded them. Some how the API does NOT load the People group segments if they don't pre-exist in the 'pay_people_groups' table. I know you are saying the segments exist , but check it again, even one blank segment makes a different. For example if you have a segment for Union membership as Yes/NO there could be 3 possible rows for this segment.

Let me know if you still have problems.
Metin