DBA Data[Home] [Help]

APPS.PAY_GRR_BUS dependencies on PER_SPINAL_POINTS

Line 27: -- relevant spinal point exists on per_spinal_points

23: -- Validates that if the grade rule is specific to a given grade, the
24: -- relevant grade exists and is date effective on per_grades
25: --
26: -- Validates that if the grade rule is specific to a given spinal point, the
27: -- relevant spinal point exists on per_spinal_points
28: --
29: -- Validates that the value for grade_or_spinal_point_id is unique for the
30: -- combination of business_group_id, rate_id, rate_type and
31: -- grade_or_spinal_point_id between the start and end effective dates for

Line 59: -- point exists on per_spinal_points then processing continues

55: -- If the grade_or_spinal_point_id refers to a grade and the grade exists
56: -- and is date effective on per_grades then processing continues
57: --
58: -- If the grade_or_spinal_point_id refers to spinal point and the spinal
59: -- point exists on per_spinal_points then processing continues
60: --
61: -- If the combination of grade_or_spinal_point_id, business_group_id,
62: -- rate_id and rate_type is unique on pay_grade_rules_f between the start
63: -- and end effective dates then processing continues

Line 114: from per_spinal_points psp

110: and p_effective_end_date <= nvl(pg.date_to, hr_api.g_eot);
111: --
112: cursor csr_valid_spinal_point is
113: select business_group_id
114: from per_spinal_points psp
115: where psp.spinal_point_id = p_grade_or_spinal_point_id;
116: --
117: cursor csr_unique_rate is
118: select null

Line 167: -- the spinal point id should exist on per_spinal_points

163: --
164: -- Check that if the rule is for a grade, this grade
165: -- is a valid grade on per_grades, otherwise the rule
166: -- must be defined for a spinal point in which case
167: -- the spinal point id should exist on per_spinal_points
168: --
169: if p_rate_type = 'G' then
170: hr_utility.set_location(l_proc, 30);
171: open csr_valid_grade_id;

Line 952: -- per_spinal_points then processing continues

948: --
949: -- Post Success:
950: -- If the value for sequence corresponds to the value defined for the
951: -- Grade or Spinal Point sequence on the table per_grades or
952: -- per_spinal_points then processing continues
953: --
954: -- Post Failure:
955: -- If the value for sequence does not correspond to the associated value
956: -- for Sequence for the Grade or Spinal Point defined on per_grades or

Line 957: -- per_spinal_points then an application error is raised and

953: --
954: -- Post Failure:
955: -- If the value for sequence does not correspond to the associated value
956: -- for Sequence for the Grade or Spinal Point defined on per_grades or
957: -- per_spinal_points then an application error is raised and
958: -- processing is terminated
959: --
960: -- Access Status:
961: -- Internal Table Handler Use Only.

Line 989: from per_spinal_points psp

985: and p_effective_end_date <= nvl(pg.date_to, hr_api.g_eot);
986: --
987: cursor csr_valid_sp_seq is
988: select null
989: from per_spinal_points psp
990: where psp.spinal_point_id = p_grade_or_spinal_point_id
991: and psp.sequence = p_sequence;
992: --
993: begin