[Home] [Help]
193: and effective_end_date;
194: --
195: Cursor csr_grade_ceiling is
196: select pgs.ceiling_step_id
197: from per_grade_spines_f pgs
198: where pgs.parent_spine_id = p_parent_spine_id
199: and pgs.grade_id = l_grade_id
200: and p_effective_date between pgs.effective_start_date
201: and pgs.effective_end_date;
264: -- --------------------------------------------------------------------------
265: select sps.sequence
266: into max_ceiling_number
267: from per_spinal_point_steps_f sps,
268: per_grade_spines_f pgs
269: where sps.step_id = l_ceiling_to_use
270: and sps.grade_spine_id = pgs.grade_spine_id
271: and pgs.parent_spine_id = p_parent_spine_id
272: and p_effective_date between sps.effective_start_date
676: -- Description:
677: -- - Validates that a parent_spine_id exists in the table per_parent_spines
678: -- and that the step_id exists in table per_spinal_point_steps_f.
679: -- (When checking the parent_spine_id, it is also copared to the table
680: -- per_grade_spines_f. This is so that grade_spine_id can be extracted
681: -- so that when checking the step_id you can use the grade spine id to
682: -- check that the step_id is a valid step id for the parent spine.)
683: -- - Checks that the effective dates for the parent_spine_id being passed is
684: -- between the effective dates for the parent_spine_id in the table
681: -- so that when checking the step_id you can use the grade spine id to
682: -- check that the step_id is a valid step id for the parent spine.)
683: -- - Checks that the effective dates for the parent_spine_id being passed is
684: -- between the effective dates for the parent_spine_id in the table
685: -- per_grade_spines_f.
686: -- - Checks that the effective dates for the step_id being passed is between
687: -- the effective dates for the step_id in the table
688: -- per_spinal_point_steps_f.
689: --
698: -- p_effective_end_date
699: --
700: --
701: -- Post Success:
702: -- If a row does exist in per_spinal_point_steps_f or per_grade_spines_f for
703: -- the given parent spine id or the step id then processing continues.
704: --
705: -- Post Failure:
706: -- If a row does not exist in per_spinal_point_steps_f or per_grade_spines_f
702: -- If a row does exist in per_spinal_point_steps_f or per_grade_spines_f for
703: -- the given parent spine id or the step id then processing continues.
704: --
705: -- Post Failure:
706: -- If a row does not exist in per_spinal_point_steps_f or per_grade_spines_f
707: -- for the given parent spine id or the step id then an application error
708: -- will be raised and processing is terminated.
709: --
710: -- Access Status:
737: -- Validate if the parent spine alone is invalid
738: --
739: cursor csr_valid_parent_spine is
740: select gs.parent_spine_id
741: from per_grade_spines_f gs
742: where gs.parent_spine_id = p_parent_spine_id
743: and p_effective_start_date between gs.effective_start_date
744: and gs.effective_end_date;
745: --
747: --
748: cursor csr_valid_parent_spine_step_id is
749: select gs.parent_spine_id,
750: gs.grade_spine_id
751: from per_grade_spines_f gs,
752: per_spinal_point_steps_f sps
753: where gs.parent_spine_id = p_parent_spine_id
754: and gs.grade_spine_id = sps.grade_spine_id
755: and sps.step_id = p_step_id
813: hr_utility.set_location(l_proc, 30);
814: --
815: -- Check that the Parent Spine ID is linked to a
816: -- valid parent_spine_id on per_parent_spines table
817: -- and get the grade_spine_id from the per_grade_spines_f table
818: -- based on the parent_spine_id
819: --
820: open csr_valid_parent_spine_step_id;
821: fetch csr_valid_parent_spine_step_id into l_parent_spine_id,l_grade_spine_id;