DBA Data[Home] [Help]

APPS.PAY_GRR_BUS dependencies on PER_GRADES

Line 24: -- relevant grade exists and is date effective on per_grades

20: -- Description:
21: -- Validates that a value for grade_or_spinal_point_id must be entered
22: --
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: --

Line 56: -- and is date effective on per_grades then processing continues

52: -- p_rate_id
53: --
54: -- Post Success:
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: --

Line 74: -- not exist or is not date effective on per_grades then an application

70: --
71: --
72: -- Post Failure:
73: -- If the grade_or_spinal_point_id refers to a grade and the grade does
74: -- not exist or is not date effective on per_grades then an application
75: -- error is raised and processing is terminated
76: --
77: -- If the business group of the grade rule is not the same as the
78: -- business group of the spinal point.

Line 106: from per_grades pg

102: l_business_group_id pay_grade_rules_f.business_group_id%type;
103: --
104: cursor csr_valid_grade_id is
105: select business_group_id
106: from per_grades pg
107: where pg.grade_id = p_grade_or_spinal_point_id
108: and p_effective_start_date between pg.date_from
109: and nvl(pg.date_to, hr_api.g_eot)
110: and p_effective_end_date <= nvl(pg.date_to, hr_api.g_eot);

Line 165: -- is a valid grade on per_grades, otherwise the rule

161: --
162: hr_utility.set_location(l_proc, 20);
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

Line 428: -- The grade (grade_or_spinal_point_id) must be valid on per_grades

424: -- for Minimum (if not null) and greater than or equal to the value for
425: -- Value (if not null)
426: --
427: -- Pre-conditions:
428: -- The grade (grade_or_spinal_point_id) must be valid on per_grades
429: --
430: -- In Arguments:
431: -- p_grade_rule_id
432: -- p_rate_type

Line 603: -- The grade (grade_or_spinal_point_id) must be valid on per_grades

599: -- for Minimum (if not null) and less than or equal to the value for
600: -- Maximum (if not null).
601: --
602: -- Pre-conditions:
603: -- The grade (grade_or_spinal_point_id) must be valid on per_grades
604: --
605: -- In Arguments:
606: -- p_grade_rule_id
607: -- p_rate_type

Line 767: -- The grade (grade_or_spinal_point_id) must be valid on per_grades

763: -- for Maximum (if not null) and less than or equal to the value for
764: -- Value (if not null)
765: --
766: -- Pre-conditions:
767: -- The grade (grade_or_spinal_point_id) must be valid on per_grades
768: --
769: -- In Arguments:
770: -- p_grade_rule_id
771: -- p_rate_type

Line 951: -- Grade or Spinal Point sequence on the table per_grades or

947: -- p_effective_end_date
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

Line 956: -- for Sequence for the Grade or Spinal Point defined on 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
957: -- per_spinal_points then an application error is raised and
958: -- processing is terminated
959: --
960: -- Access Status:

Line 980: from per_grades pg

976: l_proc varchar2(72) := g_package||'chk_sequence';
977: --
978: cursor csr_valid_grade_seq is
979: select null
980: from per_grades pg
981: where pg.grade_id = p_grade_or_spinal_point_id
982: and pg.sequence = p_sequence
983: and p_effective_start_date between pg.date_from
984: and nvl(pg.date_to, hr_api.g_eot)

Line 1036: -- on per_grades

1032: --
1033: if p_sequence is not null then
1034: --
1035: -- Check that value for Sequence is valid for the grade
1036: -- on per_grades
1037: --
1038: if p_rate_type = 'G' then
1039: open csr_valid_grade_seq;
1040: fetch csr_valid_grade_seq into l_exists;

Line 1073: -- The grade (grade_or_spinal_point_id) must be valid on per_grades

1069: -- for Minimum (if not null) and less than or equal to the value for
1070: -- Maximum (if not null)
1071: --
1072: -- Pre-conditions:
1073: -- The grade (grade_or_spinal_point_id) must be valid on per_grades
1074: --
1075: -- In Arguments:
1076: -- p_grade_rule_id
1077: -- p_rate_type