eTRM uses javascript that opens and focuses a separate window to display reports. Your browser does not appear to support javascript. This should not prevent you from using eTRM but it does mean the window focus feature will not work. Please check the contents of other windows on your desktop if you click on a link that does not appear to do anything.

APPS.HR_PERSON_ATT dependencies on HR_UTILITY

Line 751: hr_utility.set_location('Entering:'|| l_proc, 5);

747: ,c_global_person_id in varchar2 default hr_api.g_varchar2 )
748: return boolean is
749: l_proc varchar2(72) := g_package||'process_row';
750: begin
751: hr_utility.set_location('Entering:'|| l_proc, 5);
752: -- get the parameter values to pass to the BP API
753: l_title := hr_dt_attribute_support.get_parameter_char
754: (p_effective_date_row => l_effective_date_row
755: ,p_parameter_name => 'P_TITLE'

Line 1533: hr_utility.set_location(' Leaving:'|| l_proc, 10);

1529: end if;
1530: if l_orig_hire_warning and not l_api_orig_hire_warning then
1531: l_api_orig_hire_warning := l_orig_hire_warning;
1532: end if;
1533: hr_utility.set_location(' Leaving:'|| l_proc, 10);
1534: -- we need to process the next row so return true
1535: return(true);
1536: else
1537: hr_utility.set_location(' Leaving:'|| l_proc, 15);

Line 1537: hr_utility.set_location(' Leaving:'|| l_proc, 15);

1533: hr_utility.set_location(' Leaving:'|| l_proc, 10);
1534: -- we need to process the next row so return true
1535: return(true);
1536: else
1537: hr_utility.set_location(' Leaving:'|| l_proc, 15);
1538: -- processing has finished return false
1539: return(false);
1540: end if;
1541: end process_row;

Line 1543: hr_utility.set_location('Entering:'|| l_proc, 5);

1539: return(false);
1540: end if;
1541: end process_row;
1542: begin
1543: hr_utility.set_location('Entering:'|| l_proc, 5);
1544: --
1545: -- issue a savepoint if operating in validation only mode.
1546: --
1547: if p_validate then

Line 1600: hr_utility.set_message(801, 'HR_6153_ALL_PROCEDURE_FAIL');

1596: -- we can only perform a correction
1597: l_datetrack_update_mode := hr_api.g_correction;
1598: else
1599: -- we cannot perform an update due to a restriction within the APIs
1600: hr_utility.set_message(801, 'HR_6153_ALL_PROCEDURE_FAIL');
1601: hr_utility.set_message_token('PROCEDURE', l_proc);
1602: hr_utility.set_message_token('STEP','10');
1603: hr_utility.raise_error;
1604: end if;

Line 1601: hr_utility.set_message_token('PROCEDURE', l_proc);

1597: l_datetrack_update_mode := hr_api.g_correction;
1598: else
1599: -- we cannot perform an update due to a restriction within the APIs
1600: hr_utility.set_message(801, 'HR_6153_ALL_PROCEDURE_FAIL');
1601: hr_utility.set_message_token('PROCEDURE', l_proc);
1602: hr_utility.set_message_token('STEP','10');
1603: hr_utility.raise_error;
1604: end if;
1605: -- set lock start date to the effective date

Line 1602: hr_utility.set_message_token('STEP','10');

1598: else
1599: -- we cannot perform an update due to a restriction within the APIs
1600: hr_utility.set_message(801, 'HR_6153_ALL_PROCEDURE_FAIL');
1601: hr_utility.set_message_token('PROCEDURE', l_proc);
1602: hr_utility.set_message_token('STEP','10');
1603: hr_utility.raise_error;
1604: end if;
1605: -- set lock start date to the effective date
1606: l_lck_start_date := l_constant_effective_date;

Line 1603: hr_utility.raise_error;

1599: -- we cannot perform an update due to a restriction within the APIs
1600: hr_utility.set_message(801, 'HR_6153_ALL_PROCEDURE_FAIL');
1601: hr_utility.set_message_token('PROCEDURE', l_proc);
1602: hr_utility.set_message_token('STEP','10');
1603: hr_utility.raise_error;
1604: end if;
1605: -- set lock start date to the effective date
1606: l_lck_start_date := l_constant_effective_date;
1607: elsif p_attribute_update_mode = 'ATTRIBUTE_CORRECTION' then

Line 1615: hr_utility.set_message(801, 'HR_7203_DT_UPD_MODE_INVALID');

1611: l_datetrack_update_mode := hr_api.g_correction;
1612: else
1613: -- the datetrack mode is not an ATTRIBUTE_UPDATE or ATTRIBUTE_CORRECTION
1614: -- so raise DT invalid mode error
1615: hr_utility.set_message(801, 'HR_7203_DT_UPD_MODE_INVALID');
1616: hr_utility.raise_error;
1617: end if;
1618: -- lock all person rows to ensure integrity. note: this will never fail.
1619: -- if the person doesn't exist (i.e. the person_id is invalid) then the

Line 1616: hr_utility.raise_error;

1612: else
1613: -- the datetrack mode is not an ATTRIBUTE_UPDATE or ATTRIBUTE_CORRECTION
1614: -- so raise DT invalid mode error
1615: hr_utility.set_message(801, 'HR_7203_DT_UPD_MODE_INVALID');
1616: hr_utility.raise_error;
1617: end if;
1618: -- lock all person rows to ensure integrity. note: this will never fail.
1619: -- if the person doesn't exist (i.e. the person_id is invalid) then the
1620: -- business process will error with the correct error

Line 1903: hr_utility.set_location(' Leaving:'||l_proc, 10);

1899: p_name_combination_warning := l_api_name_combination_warning;
1900: p_assign_payroll_warning := l_api_assign_payroll_warning;
1901: p_orig_hire_warning := l_api_orig_hire_warning;
1902: --
1903: hr_utility.set_location(' Leaving:'||l_proc, 10);
1904: exception
1905: when hr_api.validate_enabled then
1906: --
1907: -- As the Validate_Enabled exception has been raised