DBA Data[Home] [Help]

APPS.PER_VGR_BUS dependencies on HR_POSITIONS_F

Line 107: -- hr_positions_f for the position_id if it is not null.

103: -- Validates that date from must be within the range specified by date_from
104: -- and date_to on per_grades for the grade_id.
105: --
106: -- Validates that date from is equal to or later than the effective_date of
107: -- hr_positions_f for the position_id if it is not null.
108: --
109: -- Validates that date from is equal to or later than the date_from of
110: -- per_jobs_v for the job_id if it is not null.
111: --

Line 165: -- Changes 22-APR-02. replaced hr_positions with hr_positions_f and added effective_date

161: where job.job_id = p_job_id
162: and p_date_from >= job.date_from;
163: --
164: -- Changes 12-Oct-99 SCNair (per_positions to hr_positions) Date tracked position req.
165: -- Changes 22-APR-02. replaced hr_positions with hr_positions_f and added effective_date
166: -- condition
167: cursor csr_chk_pos_dates is
168: select null
169: from hr_positions_f pos

Line 169: from hr_positions_f pos

165: -- Changes 22-APR-02. replaced hr_positions with hr_positions_f and added effective_date
166: -- condition
167: cursor csr_chk_pos_dates is
168: select null
169: from hr_positions_f pos
170: where pos.position_id = p_position_id
171: and p_date_from >= pos.date_effective
172: and p_effective_date between pos.effective_start_date and pos.effective_end_date;
173: --

Line 241: -- hr_positions_f p_position_id

237: end if;
238: hr_utility.set_location(l_proc, 5);
239: --
240: -- Check that date_from is on or later than the effective_date on
241: -- hr_positions_f p_position_id
242: --
243: if p_position_id is not null then
244: open csr_chk_pos_dates;
245: fetch csr_chk_pos_dates into l_exists;

Line 431: -- Validates that a position id exists in the table hr_positions_f

427: -- |---------------------------< chk_position_id >----------------------------|
428: -- ----------------------------------------------------------------------------
429: --
430: -- Description :
431: -- Validates that a position id exists in the table hr_positions_f
432: --
433: -- Validates that the business group id for the position is the same as
434: -- that for the valid grade.
435: --

Line 443: -- If a row does exist in hr_positions_f for the given position id then

439: -- In Arguments :
440: -- p_position_id
441: --
442: -- Post Success :
443: -- If a row does exist in hr_positions_f for the given position id then
444: -- processing continues
445: --
446: -- Post Failure :
447: -- If a row does not exist in hr_positions_f for the given position id then

Line 447: -- If a row does not exist in hr_positions_f for the given position id then

443: -- If a row does exist in hr_positions_f for the given position id then
444: -- processing continues
445: --
446: -- Post Failure :
447: -- If a row does not exist in hr_positions_f for the given position id then
448: -- 0an application error will be raised and processing is terminatet
449: --
450: -- Access Status :
451: -- Internal Table Handler Use only.

Line 470: -- Changed 22-APR-02.hr_positions is replaced with hr_positions_f and added the

466: l_business_group_id number(15);
467: --
468: --
469: -- Changed 12-Oct-99 SCNair (per_positions to hr_positions) Date tracked position req
470: -- Changed 22-APR-02.hr_positions is replaced with hr_positions_f and added the
471: -- effective_date condition. Bug 1760707
472: cursor csr_valid_pos is
473: select pos.business_group_id
474: from hr_positions_f pos

Line 474: from hr_positions_f pos

470: -- Changed 22-APR-02.hr_positions is replaced with hr_positions_f and added the
471: -- effective_date condition. Bug 1760707
472: cursor csr_valid_pos is
473: select pos.business_group_id
474: from hr_positions_f pos
475: where pos.position_id = p_position_id
476: and p_effective_date between pos.effective_start_date and pos.effective_end_date;
477: --
478: cursor csr_chk_pos_grd_comb is

Line 512: -- position on hr_positions_f

508: p_argument_value => p_business_group_iD
509: );
510: --
511: -- Check that the position ID , if it is not null, is linked to a valid
512: -- position on hr_positions_f
513: --
514: if p_position_id is not null then
515: open csr_valid_pos;
516: fetch csr_valid_pos into l_business_group_id;

Line 557: -- hr_positions_f for the position_id if it is not null.

553: -- Validates that date to must be within the range specified by date_from
554: -- and date_to on per_grades for the grade_id.
555: --
556: -- Validates that date to is equal to or earlier than the effective_date of
557: -- hr_positions_f for the position_id if it is not null.
558: --
559: -- Validates that date to is equal to or earlier than the date_to of
560: -- per_jobs_v for the job_id if it is not null.
561: --

Line 618: from hr_positions_f pos

614: -- replaced hr_positions with hr_position_f.Added effective_date condition. Bug 1760707
615: --
616: cursor csr_chk_pos_dates is
617: select null
618: from hr_positions_f pos
619: where pos.position_id = p_position_id
620: and nvl(p_date_to, hr_api.g_eot) <= nvl(hr_general.get_position_date_end(p_position_id), hr_api.g_eot)
621: and p_effective_date between pos.effective_start_date and pos.effective_end_date;
622: --

Line 692: -- hr_positions_f p_position_id

688: end if;
689: hr_utility.set_location(l_proc, 5);
690: --
691: -- Check that date_to is on or later than the end_date on
692: -- hr_positions_f p_position_id
693: --
694: if p_position_id is not null then
695: open csr_chk_pos_dates;
696: fetch csr_chk_pos_dates into l_exists;