[Home] [Help]
263: -- the current step id, in which case it needs to through an error
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
278: -- Select the sequence number for the passed step id
279: -- --------------------------------------------------------------------------
280: select sps.sequence
281: into l_step_number
282: from per_spinal_point_steps_f sps
283: where sps.step_id = p_step_id
284: and p_effective_date between sps.effective_start_date
285: and sps.effective_end_date;
286: -- --------------------------------------------------------------------------
674: -- ---------------------------------------------------------------------------
675: --
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.)
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: --
690: --
691: -- Pre-conditions:
692: -- None.
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:
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
756: and p_effective_start_date between gs.effective_start_date
1273: --
1274: /* -- bug 7457065. As we allow end dated Steps to be used now, this check is removed.
1275: If ((nvl(p_step_id, hr_api.g_number) <> hr_api.g_number) and
1276: NOT (dt_api.check_min_max_dates
1277: (p_base_table_name => 'per_spinal_point_steps_f'
1278: ,p_base_key_column => 'STEP_ID'
1279: ,p_base_key_value => p_step_id
1280: ,p_from_date => p_validation_start_date
1281: ,p_to_date => p_validation_end_date))) Then