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.AME_ACF_INS dependencies on AME_ACTION_TYPE_USAGES

Line 316: from ame_action_type_usages

312: begin
313: if(p_order_number IS null) then
314: select rule_type
315: into l_rule_type
316: from ame_action_type_usages
317: where action_type_id = p_action_type_id
318: and sysdate between start_date and
319: nvl(end_date - (1/86400) , sysdate)
320: and rownum < 2;

Line 334: ame_action_type_usages

330: else
331: select (nvl(max(order_number), 0) + 1)
332: into p_order_number
333: from ame_action_type_config,
334: ame_action_type_usages
335: where
336: ame_action_type_config.action_type_id = ame_action_type_usages.action_type_id and
337: ame_action_type_config.application_id = p_application_id and
338: ame_action_type_usages.rule_type = l_rule_type and

Line 336: ame_action_type_config.action_type_id = ame_action_type_usages.action_type_id and

332: into p_order_number
333: from ame_action_type_config,
334: ame_action_type_usages
335: where
336: ame_action_type_config.action_type_id = ame_action_type_usages.action_type_id and
337: ame_action_type_config.application_id = p_application_id and
338: ame_action_type_usages.rule_type = l_rule_type and
339: p_effective_date between ame_action_type_config.start_date and
340: nvl(ame_action_type_config.end_date - ame_util.oneSecond, p_effective_date) and

Line 338: ame_action_type_usages.rule_type = l_rule_type and

334: ame_action_type_usages
335: where
336: ame_action_type_config.action_type_id = ame_action_type_usages.action_type_id and
337: ame_action_type_config.application_id = p_application_id and
338: ame_action_type_usages.rule_type = l_rule_type and
339: p_effective_date between ame_action_type_config.start_date and
340: nvl(ame_action_type_config.end_date - ame_util.oneSecond, p_effective_date) and
341: p_effective_date between ame_action_type_usages.start_date and
342: nvl(ame_action_type_usages.end_date - ame_util.oneSecond, p_effective_date);

Line 341: p_effective_date between ame_action_type_usages.start_date and

337: ame_action_type_config.application_id = p_application_id and
338: ame_action_type_usages.rule_type = l_rule_type and
339: p_effective_date between ame_action_type_config.start_date and
340: nvl(ame_action_type_config.end_date - ame_util.oneSecond, p_effective_date) and
341: p_effective_date between ame_action_type_usages.start_date and
342: nvl(ame_action_type_usages.end_date - ame_util.oneSecond, p_effective_date);
343: end if;
344: else
345: hr_api.mandatory_arg_error

Line 342: nvl(ame_action_type_usages.end_date - ame_util.oneSecond, p_effective_date);

338: ame_action_type_usages.rule_type = l_rule_type and
339: p_effective_date between ame_action_type_config.start_date and
340: nvl(ame_action_type_config.end_date - ame_util.oneSecond, p_effective_date) and
341: p_effective_date between ame_action_type_usages.start_date and
342: nvl(ame_action_type_usages.end_date - ame_util.oneSecond, p_effective_date);
343: end if;
344: else
345: hr_api.mandatory_arg_error
346: (p_api_name => l_proc