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_ENGINE dependencies on AME_ACTION_TYPE_USAGES

Line 4789: ame_action_type_usages.rule_type

4785: ame_action_type_config.order_number,
4786: ame_action_type_config.chain_ordering_mode,
4787: ame_action_types.name,
4788: ame_action_types.procedure_name,
4789: ame_action_type_usages.rule_type
4790: from
4791: ame_action_type_config,
4792: ame_action_types,
4793: ame_action_type_usages

Line 4793: ame_action_type_usages

4789: ame_action_type_usages.rule_type
4790: from
4791: ame_action_type_config,
4792: ame_action_types,
4793: ame_action_type_usages
4794: where
4795: ame_action_type_config.application_id = engAmeApplicationId and
4796: ame_action_types.action_type_id = ame_action_type_config.action_type_id and
4797: ame_action_type_usages.action_type_id = ame_action_types.action_type_id and

Line 4797: ame_action_type_usages.action_type_id = ame_action_types.action_type_id and

4793: ame_action_type_usages
4794: where
4795: ame_action_type_config.application_id = engAmeApplicationId and
4796: ame_action_types.action_type_id = ame_action_type_config.action_type_id and
4797: ame_action_type_usages.action_type_id = ame_action_types.action_type_id and
4798: /*
4799: Only action types for list-creation and exception rules have two action-type usages;
4800: all other action types have exactly one (current) action-type usage each.
4801: */

Line 4802: ame_action_type_usages.rule_type <> ame_util.exceptionRuleType and

4798: /*
4799: Only action types for list-creation and exception rules have two action-type usages;
4800: all other action types have exactly one (current) action-type usage each.
4801: */
4802: ame_action_type_usages.rule_type <> ame_util.exceptionRuleType and
4803: engEffectiveRuleDate between
4804: ame_action_type_config.start_date and
4805: nvl(ame_action_type_config.end_date - ame_util.oneSecond, engEffectiveRuleDate) and
4806: engEffectiveRuleDate between

Line 4810: ame_action_type_usages.start_date and

4806: engEffectiveRuleDate between
4807: ame_action_types.start_date and
4808: nvl(ame_action_types.end_date - ame_util.oneSecond, engEffectiveRuleDate) and
4809: engEffectiveRuleDate between
4810: ame_action_type_usages.start_date and
4811: nvl(ame_action_type_usages.end_date - ame_util.oneSecond, engEffectiveRuleDate)
4812: order by ame_action_types.action_type_id;
4813: cursor configVarCursor is
4814: select

Line 4811: nvl(ame_action_type_usages.end_date - ame_util.oneSecond, engEffectiveRuleDate)

4807: ame_action_types.start_date and
4808: nvl(ame_action_types.end_date - ame_util.oneSecond, engEffectiveRuleDate) and
4809: engEffectiveRuleDate between
4810: ame_action_type_usages.start_date and
4811: nvl(ame_action_type_usages.end_date - ame_util.oneSecond, engEffectiveRuleDate)
4812: order by ame_action_types.action_type_id;
4813: cursor configVarCursor is
4814: select
4815: decode(nvl(application_id,0),0,0,-1) application_id,