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.OTA_CHAT_API dependencies on HR_API

Line 136: ,p_start_date_active in date default hr_api.g_date

132: ,p_effective_date in date
133: ,p_name in varchar2
134: ,p_description in varchar2
135: ,p_business_group_id in number
136: ,p_start_date_active in date default hr_api.g_date
137: ,p_end_date_active in date default hr_api.g_date
138: ,p_start_time_active in varchar2 default hr_api.g_varchar2
139: ,p_end_time_active in varchar2 default hr_api.g_varchar2
140: ,p_timezone_code IN VARCHAR2 DEFAULT hr_api.g_varchar2

Line 137: ,p_end_date_active in date default hr_api.g_date

133: ,p_name in varchar2
134: ,p_description in varchar2
135: ,p_business_group_id in number
136: ,p_start_date_active in date default hr_api.g_date
137: ,p_end_date_active in date default hr_api.g_date
138: ,p_start_time_active in varchar2 default hr_api.g_varchar2
139: ,p_end_time_active in varchar2 default hr_api.g_varchar2
140: ,p_timezone_code IN VARCHAR2 DEFAULT hr_api.g_varchar2
141: ,p_public_flag in varchar2 default hr_api.g_varchar2

Line 138: ,p_start_time_active in varchar2 default hr_api.g_varchar2

134: ,p_description in varchar2
135: ,p_business_group_id in number
136: ,p_start_date_active in date default hr_api.g_date
137: ,p_end_date_active in date default hr_api.g_date
138: ,p_start_time_active in varchar2 default hr_api.g_varchar2
139: ,p_end_time_active in varchar2 default hr_api.g_varchar2
140: ,p_timezone_code IN VARCHAR2 DEFAULT hr_api.g_varchar2
141: ,p_public_flag in varchar2 default hr_api.g_varchar2
142: ,p_chat_id in number

Line 139: ,p_end_time_active in varchar2 default hr_api.g_varchar2

135: ,p_business_group_id in number
136: ,p_start_date_active in date default hr_api.g_date
137: ,p_end_date_active in date default hr_api.g_date
138: ,p_start_time_active in varchar2 default hr_api.g_varchar2
139: ,p_end_time_active in varchar2 default hr_api.g_varchar2
140: ,p_timezone_code IN VARCHAR2 DEFAULT hr_api.g_varchar2
141: ,p_public_flag in varchar2 default hr_api.g_varchar2
142: ,p_chat_id in number
143: ,p_object_version_number in out nocopy number);

Line 140: ,p_timezone_code IN VARCHAR2 DEFAULT hr_api.g_varchar2

136: ,p_start_date_active in date default hr_api.g_date
137: ,p_end_date_active in date default hr_api.g_date
138: ,p_start_time_active in varchar2 default hr_api.g_varchar2
139: ,p_end_time_active in varchar2 default hr_api.g_varchar2
140: ,p_timezone_code IN VARCHAR2 DEFAULT hr_api.g_varchar2
141: ,p_public_flag in varchar2 default hr_api.g_varchar2
142: ,p_chat_id in number
143: ,p_object_version_number in out nocopy number);
144: --

Line 141: ,p_public_flag in varchar2 default hr_api.g_varchar2

137: ,p_end_date_active in date default hr_api.g_date
138: ,p_start_time_active in varchar2 default hr_api.g_varchar2
139: ,p_end_time_active in varchar2 default hr_api.g_varchar2
140: ,p_timezone_code IN VARCHAR2 DEFAULT hr_api.g_varchar2
141: ,p_public_flag in varchar2 default hr_api.g_varchar2
142: ,p_chat_id in number
143: ,p_object_version_number in out nocopy number);
144: --
145: -- ----------------------------------------------------------------------------