ORACLE APPLICATIONS ARCHIVES
Topicwise collection of
Postings on Mail Lists
ON
HRMS - SETUP
What Elements to link
Subject: [orahrms-l] What elements should we link?
From: "Lyng, Janice E" jlyng@kpmg.com
Date: Mon, 26 Jul 1999 10:08:53 -0400
Folks,
While attending a Oracle HRMS implementation class the instructor indicated
that for earnings elements it was only necessary to link the element you
created and the shadow element, special inputs. She said it was not
necessary to link the special features element. I subsequently attended a
more advanced elements class and many individuals in the class said ALL
elements should be linked. They indicated that if you do not link all
elements you will run into trouble later on.
I'm interested in hearing people's thought's on this. Does anyone have any
life experiences to support either method?
Also, does the same hold true for deductions?
Thanks. Janice
Janice Lyng
Consultant
KPMG LLP
Phone - 518-427-4717
Subject: Re: [orahrms-l] What elements should we link?
From: "Ken Conway" ken.conway@bosscorporation.com
Date: Mon, 26 Jul 1999 09:28:39 -0500
Janice:
Linking of Special Features elements is really not necessary except for
extreme circumstances. In general, Oracle uses Special Features for
internal purposes, and it is rare that you would want to get involved with
this process.
We do not link Special Features elements on our projects. It would not hurt
you to link these but has not served any practical purpose in the past.
Hope this helps,
Ken
Ken Conway
BOSS Corporation
Better Organization Service Solutions
(214) 495-7654 voice
(214) 495-7543 fax
(770) 622-5500 Headquarters
Flexible Benefits
Subject: [orahrms-l] Flexible Benefits in 10.7SC
From: Brenda Finley bfinley@standard.com
Date: Tue, 27 Jul 1999 14:40:24 -0700
Hi...
We're currently running HR only, 10.7SC 16.1, and are in the process of
changing our benefit plans from a traditional set of benefits to a cafeteria
style plan where employees will be given a certain amount of credits to use
to "buy" their benefits, or something along these lines.
I realize that to administer a flexible benefits package, we will need the
Oracle Advanced Benefits module with Oracle 11i. However, we will probably
outsource the administration for a while until we upgrade to Oracle 11i. My
question is: Is anyone running 10.7sc 16.1 (or any version of 10.7,
possibly even 11.0x) and have flex/cafeteria style benefits? I'd like to
find out information on what your company handles in the HR app vs what the
TPA does (which I assume you must have), etc. Just looking for contacts
right now that I can communicate with as we move through this process.
Thanks much!
Brenda
Brenda Finley [Mailto:bfinley@standard.com]
Data Analyst IV, Business Technical Services
Standard Insurance Company
1100 SW Sixth Avenue, P3B
Portland, OR 97204
Subject: RE: [orahrms-l] Flex Benefits in 10.7SC
From: "Jarnutowski, George J." JarnGJ@jea.com
Date: Tue, 27 Jul 1999 18:12:57 -0400
We are also on 10.7sc and our company is going to open enrollment this year
and like to see how someone is doing this.
Subject: Re: [orahrms-l] Flex Benefits in 10.7SC
From: "Lewis Cunningham" lcunning@mediaone.net
Date: Tue, 27 Jul 1999 15:27:03 -0700
Brenda,
Since you're HR only, it's really an admin thing as opposed to a real-time
connection to payroll. I've done a fairly simple modification to the
element entry screen that allows flex dollars for benefits and ee/er
calculations for specific benefits.
How are you feeding data to your payroll system? I developed a simple
interface to send to ADP payroll. ADP doesn't do any of the calculations
for benefits, we pass the amounts to be taken out and it lists them on the
stub. The exception to this is benefits based on actuals, like 401k.
Write me off line if this is an interest to you and I'll describe in more
detail.
Lewis
Employee with two active, identical elements
Subject: [orahrms-l] Employee with two active, identical elements?
From: "Kevin Jarrett" kejarr@copelco.com
Date: Thu, 12 Aug 1999 08:11:58 -0400
Hi folks,
I stumbled across this when running a query this morning. I have a feeling
this has an easy answer.
The query is for a specific element (Quarterly Bonus Plan). SQL to follow.
LAST_NAME
FIRST_NAMEVALUE EFFECTIVE
EFFECTIVE
------------------------------ -------------------- ----- --------- -------
--
XXXXXGary2412-JAN-98
31-DEC-12
XXXXXGary3012-JAN-98
31-DEC-12
In the application, he shows as having a 24% input value. The 30% entry
appears to have been end-dated 11-JAN-99, per my review of the element
entries via date track.
Here's the SQL:
SELECT DISTINCT
ppf.LAST_NAME, ppf.FIRST_NAME, peevf.screen_entry_value VALUE,
peef.effective_start_date,
peef.effective_end_date
FROM
hr.per_people_f ppf,
hr.per_assignments_f paf,
hr.pay_element_entries_f peef,
hr.pay_element_links_f pelf,
hr.pay_element_types_f petf,
hr.pay_element_entry_values_f peevf
WHERE
ppf.person_id = paf.person_id ANDv
paf.assignment_id = peef.assignment_id AND
peef.element_link_id = pelf.element_link_id AND
pelf.element_type_id = petf.element_type_id AND
peef.element_entry_id = peevf.element_entry_id AND
sysdate BETWEEN ppf.effective_start_date AND ppf.effective_end_date AND
sysdate BETWEEN peef.effective_start_date AND peef.effective_end_date AND
peevf.input_value_id = '149' and
peevf.screen_entry_value > 18
ORDER BY 1
/
What am I missing? Why would this guy have more than two current rows?
Thanks!
-kj-
Kevin Jarrett Copelco Capital, Inc.
E-Commerce Project Manager Mount Laurel, NJ USA
kejarr@copelco.com http://www.copelco.com
"Brobeck, Jason" brobeck@ppg.com
on 08/12/99 08:37:02 AM
To: Kevin Jarrett/INTSERV/COPELCO
Subject: RE: [orahrms-l] Employee with two active, identical elements?
You have to datetrack the pay_element_entry_values_f table also. While you
are picking up only the current pay_element_entries_f row, you are getting
both the current and the old entry_values_f row. Actually, all 6 of those
tables should be datetracked to guarantee only 1 row is returned (or else
assignment changes, link changes, etc would also cause multiple rows to
come
back). If you are just interested in the current data, you can use the _x
view instead of the _f table ('_x' is a view that datetracks each table to
the sysdate).
Jason Brobeck
PPG Industries, Inc.
Subject: RE: [orahrms-l] Employee with two active, identical elements?
From: "Kevin Jarrett" kejarr@copelco.com
Date: Thu, 12 Aug 1999 08:48:46 -0400
BINGO!
(slapping forehead)
Thanks! I knew it was something easy.
-kj-
Subject: RE: [orahrms-l] Employee with two active, identical elements?
From: PA DAVID SELVARAJ DSELVARAJ@FAMILYDOLLAR.com
Date: Thu, 12 Aug 1999 09:02:26 -0400
I guess you are missing assignment effective date comparison.
sysdate between paf.effective_start_date and paf.effective_end_date
One person can have more than one assingment record with the different
effective_dates.
Hope this helps.
-- David Selvaraj.
Subject: Re: [orahrms-l] Employee with two active, identical elements?
From: "Bob Cody" Bob_Cody@norstanconsult.com
Date: Thu, 12 Aug 1999 09:07:40 -0400
Hi Kevin,
You should qualify your query for all of your date tracked tables (those ending
in '_f ')
with an effective date. One of these tables (per_assignments_f,
pay_element_links_f,
or pay_element_types_f ) probabably has 2 rows causing you to get two results.
You can use SYSDATE to qualify or use the '_x' view of these tables. The '_x'
views (i.e. per_assignments_x ) have the SYSDATE built in to always give you
the the data for todays date.
Bob Cody
Norstan Consulting
bob_cody@norstanconsult.com
Y2K problem with Benefits screen
Date: Wed, 18 Aug 1999 13:29:46 -0400
From: "Bartoletti, Mike" BartolMi@rf.suny.edu
To: "'Multiple recipients of list'" oraapps-l@cpa.qc.ca
Subject: HR:Benefits Y2K Issue
Has anyone run into a problem with Release 11.02 in the benefits screens
that entering '1950' will actually return '2050' after the record is saved?
Michael Bartoletti
Applications Development
Research Foundation of SUNY
ph:(518)434-7204
fx:(518)434-7211
mailto:bartolmi@rfsuny.org
Date: Wed, 18 Aug 1999 18:43:10 -0400
From: Sudershan virdi virdi@interlog.com
To: oraapps-l@cpa.qc.ca
Subject: Re: HR:Benefits Y2K Issue
As i understand , the application database uses the NLS_DATE_FORMAT of
'DD-MON-RR' and if you enter 50 now(in 1999) it will interpret as 2050,which
is
what you want. It is not expected that you will have personnel data for
1950(?).
Sudershan Virdi
Fast Formula - How to Debug - Query 1
From:"Lewis Cunningham" LCunningham@gwmail.valencia.cc.fl.us
Date : 18th August 1999
Subject: FF: Debug in fast formula R11
Has anyone used the DEBUG function in FastFormula in R11. I think it
was added with the PTO Accrual patch. It seems to be defined correctly
but when I try to Verify, I get an error. The syntax for debug is
debug(). The error I get points to the line where debug is and to
the column where the ' starting the expression is, i.e.:
DEBUG( 'fubar' )
The error points to column 6. "The error is Unexpected Text which
cannot be verified".
I've tried using ", and I've tried assigning the string to a variable
first but no luck.
Does anyone know of any other way to debug a fast formula?
Thanks,
Lewis
Fast Formula - How to Debug - Query 2
From:
"manu kkk" manu1357@hotmail.com
28 Aug 1999 2:10 AM
Subject:
[orahrms-l] debugging the fast formula: URGENT??
Hi All,
We are having a problem in a fast formula. Can someone suggest me how
to debug the fast formula and after finding the problem in the code how to
fix that up..Is it something like compiling and recomipling the pl/sql code
like we do in Stored procedures etc..
I have a DBA backgroud so sql and pl/sql will bot be a problem. Will
really appreciate an early answer..
thanks
From:
Hankins Parichabutr Hankins@spinsoftware.com
28 Aug 1999 3:49 AM
Subject:
Re: [orahrms-l] debugging the fast formula: URGENT??
To:
manu kkk manu1357@hotmail.com
I've not seen the 'debug' that Oracle have provided w/FF in Rel 11, but it's
useful enough to simply return messages out of the formula.
I don't know if R11 debug lets you somehow check out a formula
without running a payroll run - that would be interesting.
Any plsql functions you call from the formula should also be spot tested
via sqlplus or a plsql block.
In general, a design goal for writing formulae should be to do as much as
possible - all of the calculation if you can - via a plsql function called from
Formula. This way you're able to do most of your coding/testing/debugging
and enhancing via plsql...
Good luck,
"HPARICHA"
Hankins Parichabutr
Spin Software
Practice Director
228 Queen Street, Level 3
Auckland, New Zealand
(+64) 25.771.275 (mobile) or 9.366.0348 ext. 804
http://www.spinips.com/
From:
OraHRMS-L List Owner gaclark@ibm.net
28 Aug 1999 8:51 AM
Subject:
Re: [orahrms-l] debugging the fast formula: URGENT??
To:
manu1357@hotmail.com
I tend to agree with Hankins' philosophy...to do as much as possible via a
plsql function called from the formula because:
1. Not only do you gain the advantage of doing your
coding/testing/debugging and enhancing via pl/sql, but also reduce the
occurrence and maintenance of redundant code in your formulas
2. Because Hankins says so...just about every generated formula and pl/sql
function has his id "HPARICHA" tattooed in it...sorry, just a weak attempt
at some humor.
Actually, I recently taught an FastFormula class internally at Oracle and
I'll pass on some of my own general thoughts regarding errors and
debugging. Recognize that there are really two types of Oracle FastFormula
errors that can occur. These are verify-time errors and run-time errors.
Verify-errors are those errors which occur when click the verify button
while editing or creating a formula via the Formula window. Usually these
errors are the result of typographical errors or failure to adhere to some
of the coding rules outlined in the documentation. Usually there is an
error message which offers "some" explanation of the problem...but not
necessarily, THE explanation! Be careful, the problem may not always be
what the message says. An example would be the using an operand of the
wrong data type in the text function GET_TABLE_VALUE. The message returned
in this scenario states something to the effect of that the function is not
defined or found.
Run-time errors occur while the formula is running and can be a little
trickier to debug. It usually is the result of some type a data problem
within:
1. the formula code
2. the code for a pl/sql function called by the formula
3. the application database
Examples of run-time errors are Divide by Zero, Null Data Found, or Too
Many Rows. SO what can you do to reduce the occurrence of run time errors?
1. follow the coding guidelines in the FastFormula documentation
2. test pl/sql functions which are registered as FastFormula function via
sql*plus
3. enter data through support APIs or through the application.
One thing that you can do is create local variables or formula results in
your formula to hold messages which return the value of variables at
different logic points with in the formula logic. Remember to put this
variable in your RETURN statement and also to reference it in the Formula
Result Rules windows.
A bit more about FastFormula functions...a FastFormula Function is actually
a function call to PL/SQL packaged functions. A user-defined function may
only return one value. IN OUT and OUT type parameters are not supported. A
user-fined function should not have ant commit, rollback, or savepoint
statements because they may lead to data integrity problems with the
payroll run.
The function registration process actually consists of three parts:
1. Naming and defining the new function.
This step consists of inserting a row into table FF_FUNCTIONS. In Release
11.0.x the Define Function window takes care of this process for you.
2. Creating the new function contexts.
Contexts are environmental values that do not get passed to the function,
but are available to you. This step consists of inserting a row(s) into
table FF_FUNCTION_CONTEXT_USAGES. In Release 11.0.x the Context Usage
window takes care of this process for you.
3. Creating the new function parameters.
This step consists of inserting a row(s) into table FF_FUNCTION_PARAMETERS.
In Release 11.0.x the Parameter window takes care of this process for you.
Please note that when a function requires a mixture of contexts and
parameters, the context should be listed first in the function header
followed by the function parameters.
Finally...I believe that 85% of FastFormula is design and requires the
skills of a functional resource. What are the inputs? What data is
available to you? What are you trying to calculate? What are the business
rules of the enterprise? Are the run results in compliance with legislative
requirements?
I hope this helps...
Regards,
Greg
Gregory A. Clark
Senior Principal Consultant Oracle Corporation
HR/Payroll Practice 6505 Blue Lagoon Drive
Voice Mail: 305.260.7221 Suite 400
Email: gaclark@us.oracle.com Miami, FL 33126
Alternate: gaclark@PayrollWorld.com
From:
"Lewis Cunningham" LCunningham@gwmail.valencia.cc.fl.us
28 Aug 1999 6:46 PM
Subject:
Re: [orahrms-l] debugging the fast formula: URGENT??
To:
manu1357@hotmail.com, gaclark@ibm.net
I agree with most of that but the game changes when you're trying to
debug a seeded accrual or accual sub-formula. When I say seeded, I mean
a formula provided specifically to be customized. You can only RETURN
certain things and you're not running them in a payroll run; they run
from the employee accrual screen.
Like triggers, I prefer to always package my processing. It makes
maintenance and debugging easier. I think Oracle chose not to package
everything so that people who don't know pl/sql or even what a stored
procedure is can modify the formulas.
Lewis
From:
OraHRMS-L List Owner gaclark@ibm.net
28 Aug 1999 6:59 PM
Subject:
Re: [orahrms-l] debugging the fast formula: URGENT??
To:
"Lewis Cunningham" LCunningham@gwmail.valencia.cc.fl.us
Lewis,
You bring up a very good point, particularly for clients on older releases
of HRMS. However, an additional functionality patch 865749 for Absences and
PTO Accrual Plans provides a solution for this concern going forward with
R11.0X.
The documentation update is in MetaLink for clients to retrieve. Basically,
much of the PTO functionality is now FastFormula based. There is a section
in the documentation which addresses how to write or edit accrual formulas.
Regards,
Greg
From:
"Lewis Cunningham" LCunningham@gwmail.valencia.cc.fl.us
28 Aug 1999 6:49 PM
Subject:
Re: [orahrms-l] debugging the fast formula: URGENT??
To:
manu1357@hotmail.com, OraHRMS-L@mail-list.com
I created a simple table, 2 columns, msg varchar2(2000) and order_by
number. Create and register a procedure that writes to the table and
commits. Call that from inside your formula and you can trace and
display execution. I wouldn't take this approach for a payroll formula
unless you're in an instance you can just refresh anytime. Don't do
this in prod.
Lewis
From:
Hankins Parichabutr Hankins@spinsoftware.com
29 Aug 1999 3:00 AM
Subject:
Re: [orahrms-l] debugging the fast formula: URGENT??
Yep, if Oracle could do it again...all formulae would be done using plsql !
Fast Formula was developed before plsql existed, and the US template
and seeded formulae (for earnings/deductions) were built before plsql was
mature enough to be useful. The capability to call a plsql function from
formula
was introduced (as in, was absolutely necessary :) as the US business
requirements
fleshed themselves out. A good thing that plsql, else US functionality would
have
been too unwieldy.
As Lewis says, Fast Formula has always been pitched at functional payroll
staff -
ie. a simple language which a functional person could use to define any and
all payroll
calculations - a major selling point as baan, psft, jde, sap didn't and still
don't(?) have
anything like it.
As it turns out, implementing anything other than the simplest business
requirements
means you need something w/more power than a one pass formula - ie.
plsql/iteration
to do any kind of reasonably complex calculation...
Hankins Parichabutr
Spin Software
Practice Director
228 Queen Street, Level 3
Auckland, New Zealand
(+64) 25.771.275 (mobile) or 9.366.0348 ext. 804
http://www.spinips.com/
From:
"John Turner" jturner@SpinSoftware.com
29 Aug 1999 6:31 AM
Subject:
Re: [orahrms-l] debugging the fast formula: URGENT??
All
I'd like to add a word of caution when using PL/SQL functions in
formulas. The payroll run has a fair amount of optimization for
database items. I suggest that you retrieve the database items in
your formula and then pass them to PL/SQL functions as
parameters. This way you take advantage of the database item
optimization and the power of PL/SQL.
JT
___
John Turner
jturner@SpinSoftware.com
http://www.spinsoftware.com
Cost Allocation KFF - setup
Date: Thu, 2 Sep 1999 17:21:42 -0400
From: Palazzola_Paul@tmac.com
To: oraapps-l@cpa.qc.ca
Subject: Oracle Payroll Setup for the Cost Allocation Key Flexfield
Good Afternoon,
We are in the processing of implementing Oracle HRMS internally for a
January
1st start date. Since we are already using a web based system to transfer
time
sheets to Oracle Projects, all of the costed labor is transferred to Oracle
General Ledger. We only want payroll related items (non-labor) transferred
to
Oracle General Ledger from Oracle Payroll.
What cost allocation key flexfield should be setup to collect only those
items
which are non- project related such as: state tax w/h, FIT and loans etc ?
We
have a six segment general ledger accounting field. However, it will only be
necessary to capture costs in only two segments in most cases since these
are
only balance sheet accounts.
Any ideas on the subject would be terrific.
Thank you in advance for your help on this subject!!
Date: Fri, 3 Sep 1999 01:19:52 EDT
From: GWRR@aol.com
To: oraapps-l@cpa.qc.ca
Subject: Re: Oracle Payroll Setup for the Cost Allocation Key Flexfield
Hi Paul,
You need to set up the costing at either the element link level (for fixed
cost) or input level for individual costing. You also need to mapped your
cost allocation key FF to your GL FF.
Gwen
Security by Org Heirarchy
From:
"Buscher, Nancy" nbuscher@usa.capgemini.com
9/1/99 1:40 AM
Subject:
[orahrms-l] Orgs & Security
Hi...
HELP!!! I am trying to setup Security by Organization Hierarchy. It's not
working. I think it's because of the hierarchy. When I setup a hierarchy,
all the subordinates show 0 where I would expect to see 1 or 2 depending on
how many subordinates I set up.
Has anyone run into this?
Thanks for any help...
Nancy Buscher@usa.capgemini.com