eTRM uses javascript that opens and focuses a separate window to display reports. Your browser does not appear to support javascript. This should not prevent you from using eTRM but it does mean the window focus feature will not work. Please check the contents of other windows on your desktop if you click on a link that does not appear to do anything.

APPS.HR_SPP_EXCEPTION_DATA dependencies on PER_SPINAL_POINT_PLACEMENTS_F

Line 165: from per_spinal_point_placements_f spp1,

161: -- done.
162: --
163: cursor csr_sequence_number is
164: select sps.sequence,spp1.parent_spine_id
165: from per_spinal_point_placements_f spp1,
166: per_spinal_point_placements_f spp2,
167: per_spinal_point_steps_f sps
168: where spp1.step_id = sps.step_id
169: and p_effective_date = spp1.effective_start_date

Line 166: per_spinal_point_placements_f spp2,

162: --
163: cursor csr_sequence_number is
164: select sps.sequence,spp1.parent_spine_id
165: from per_spinal_point_placements_f spp1,
166: per_spinal_point_placements_f spp2,
167: per_spinal_point_steps_f sps
168: where spp1.step_id = sps.step_id
169: and p_effective_date = spp1.effective_start_date
170: and spp2.effective_start_date = spp1.effective_end_date +1

Line 180: from per_spinal_point_placements_f

176: -- with same parent spine
177: --
178: cursor csr_future_record is
179: select parent_spine_id
180: from per_spinal_point_placements_f
181: where placement_id = p_placement_id
182: and parent_spine_id = p_parent_spine_id
183: and p_effective_date between effective_start_date
184: and effective_end_date;

Line 272: per_spinal_point_placements_f spp,

268: nvl(paa.special_ceiling_step_id,pgs.ceiling_step_id)
269: into l_ceiling_step_id, l_special_ceiling_step_id
270: from per_grade_spines_f pgs,
271: per_spinal_point_steps_f sps,
272: per_spinal_point_placements_f spp,
273: per_all_assignments_f paa
274: where pgs.grade_spine_id = sps.grade_spine_id
275: and paa.assignment_id = spp.assignment_id
276: and spp.assignment_id = p_assignment_id