Discoverer payroll report questions

Question

Hi all,
I know this may not be the correct board for this but here goes.
I have to create a disco report for payroll and it involves salary history and is mainly based on customer sql folders in the business area.
I am trying to get the salary history for an employee but I am picking up more rows that expected.
I have the code below. I know that an employee has had 6 salary amounts since they started. The code below brings me back 6 rows including start and end date for each salary.
However, when I comment in a join to pay_grade_rules_f and add in pgrf.value field in the select and attempt to get back the actual salary amount associated with each band, I am getting 12 rows back instead of 6. I think it is because my join is not unique enough. I am joining to pay_grade_rules_f from per_spinal_point_steps_f on an id field but it seems the id exists more than once in the pay_grade_rules_f table.
Would anyone know how I can fine tune this so that I only get back the correct salary for each band?
thanks
dw
select
psppf.assignment_id
,psppf.effective_start_date
,psppf.effective_end_date
--,pgrf.value
FROM
per_spinal_point_placements_f psppf
join
per_all_assignments_f paaf on psppf.assignment_id = paaf.assignment_id
join
per_grades pg on paaf.grade_id = pg.grade_id
join
per_spinal_point_steps_f pspsf on psppf.step_id = pspsf.step_id
join
per_grade_spines_f pgsf on pg.grade_id = pgsf.grade_id
-- join
-- pay_grade_rules_f pgrf on pspsf.spinal_point_id = pgrf.grade_or_spinal_point_id
where
psppf.assignment_id = someid
and
sysdate between paaf.effective_start_date and paaf.effective_end_date
order by 2

Answer 1

Every customer implementation is unique. My experience has been, in working to create workbooks in Discoverer, is that I have to study my data carefully to understand it and resolve the kind of issue that you are having here. For example, one issue we have here that you apparently do not have in your data is that we can have more than one assignment active at a time for an employee. So we cannot just select on assignment effective date, as you are doing, otherwise we end up with duplicate records. If you cannot figure out what is causing the duplication, then I suggest opening a service request with Oracle support. Oracle support has diagnostic tools that can be used to send them data in your database. Since we on this forum cannot see your data, we can only speculate as to a possible cause. That speculation may be wrong, and cause you to waste time trying to chase down something that does not exist.
John Dickey