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.WSH_RU_ACTIONS dependencies on WSH_CUSTOMIZED_ACTIVITY_MSGS

Line 593: * Table Handler to insert records into wsh_customized_activity_msgs table

589:
590:
591:
592: /**************************************************************************************
593: * Table Handler to insert records into wsh_customized_activity_msgs table
594: * This API is designed to be called from ROLE_DEFINITIONS form only.
595: ****************************************************************************************/
596: Procedure insert_customized_msgs (
597: p_custom_message_rec IN OUT NOCOPY custom_message_rec

Line 631: insert into wsh_customized_activity_msgs

627: END IF;
628:
629: x_return_status := wsh_util_core.g_ret_sts_success;
630:
631: insert into wsh_customized_activity_msgs
632: (customized_activity_mesg_id
633: ,role_id
634: ,activity_code
635: ,validation_code

Line 643: (wsh_customized_activity_msgs_s.nextval

639: ,last_update_date
640: ,last_updated_by
641: ,last_update_login)
642: values
643: (wsh_customized_activity_msgs_s.nextval
644: ,p_custom_message_rec.role_id
645: ,p_custom_message_rec.activity_code
646: ,p_custom_message_rec.validation_code
647: ,p_custom_message_rec.return_status

Line 676: * Table Handler to update records into wsh_customized_activity_msgs table

672: End insert_customized_msgs ;
673:
674:
675: /**************************************************************************************
676: * Table Handler to update records into wsh_customized_activity_msgs table
677: * This API is designed to be called from ROLE_DEFINITIONS form only.
678: * ***************************************************************************************/
679: Procedure update_customized_msgs (
680: p_custom_message_rec IN OUT NOCOPY custom_message_rec

Line 711: update wsh_customized_activity_msgs msg

707: END IF;
708:
709: x_return_status := wsh_util_core.g_ret_sts_success;
710:
711: update wsh_customized_activity_msgs msg
712: set return_status = nvl(p_custom_message_rec.return_status,'W')
713: ,creation_date = l_sysdate
714: ,created_by = l_user_id
715: ,last_update_date = l_sysdate

Line 743: * Table Handler to delete records into wsh_customized_activity_msgs table

739: End update_customized_msgs ;
740:
741:
742: /**************************************************************************************
743: * Table Handler to delete records into wsh_customized_activity_msgs table
744: * This API is designed to be called from ROLE_DEFINITIONS form only.
745: ****************************************************************************************/
746: Procedure delete_customized_msgs (
747: p_custom_message_rec IN OUT NOCOPY custom_message_rec

Line 772: delete from wsh_customized_activity_msgs

768: END IF;
769:
770: x_return_status := wsh_util_core.g_ret_sts_success;
771:
772: delete from wsh_customized_activity_msgs
773: where customized_activity_mesg_id = p_custom_message_rec.customized_activity_mesg_id;
774:
775: IF l_debug_on THEN
776: wsh_debug_sv.log(l_module_name,'l_return_status',x_return_status);

Line 800: from wsh_customized_activity_msgs msgs

796: ,p_activity_code in VARCHAR2
797: ,p_validation_code in VARCHAR2
798: ,p_lookup_type in VARCHAR2) is
799: select msgs.activity_code , msgs.validation_code , msgs.return_status
800: from wsh_customized_activity_msgs msgs
801: ,wsh_grants grants
802: ,wsh_lookups activity
803: ,wsh_lookups message
804: where grants.user_id = p_user_id