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_WIP_TXNS dependencies on HR_API

Line 75: default hr_api.g_varchar2

71: ,p_current_user_id IN fnd_user.user_id%TYPE
72: ,p_vo_xml IN VARCHAR2
73: ,p_sub_state IN hr_wip_transactions.sub_state%TYPE
74: ,p_dml_mode IN hr_wip_transactions.dml_mode%TYPE
75: default hr_api.g_varchar2
76: ,p_context_display_text IN hr_wip_transactions.context_display_text%TYPE
77: default hr_api.g_varchar2
78: ,p_transaction_id OUT NOCOPY hr_wip_transactions.transaction_id%TYPE
79: );

Line 77: default hr_api.g_varchar2

73: ,p_sub_state IN hr_wip_transactions.sub_state%TYPE
74: ,p_dml_mode IN hr_wip_transactions.dml_mode%TYPE
75: default hr_api.g_varchar2
76: ,p_context_display_text IN hr_wip_transactions.context_display_text%TYPE
77: default hr_api.g_varchar2
78: ,p_transaction_id OUT NOCOPY hr_wip_transactions.transaction_id%TYPE
79: );
80: --
81: -- ----------------------------------------------------------------------------

Line 90: default hr_api.g_varchar2

86: ,p_current_user_id IN fnd_user.user_id%TYPE
87: ,p_vo_xml IN VARCHAR2
88: ,p_sub_state IN hr_wip_transactions.sub_state%TYPE
89: ,p_dml_mode IN hr_wip_transactions.dml_mode%TYPE
90: default hr_api.g_varchar2
91: ,p_context_display_text IN hr_wip_transactions.context_display_text%TYPE
92: default hr_api.g_varchar2
93: );
94: --

Line 92: default hr_api.g_varchar2

88: ,p_sub_state IN hr_wip_transactions.sub_state%TYPE
89: ,p_dml_mode IN hr_wip_transactions.dml_mode%TYPE
90: default hr_api.g_varchar2
91: ,p_context_display_text IN hr_wip_transactions.context_display_text%TYPE
92: default hr_api.g_varchar2
93: );
94: --
95: -- ----------------------------------------------------------------------------
96: -- |-----------------------< save_for_later_append >-----------------------|

Line 112: default hr_api.g_varchar2

108: ,p_item_key IN wf_items.item_key%TYPE
109: ,p_current_user_id IN fnd_user.user_id%TYPE
110: ,p_vo_xml IN VARCHAR2
111: ,p_dml_mode IN hr_wip_transactions.dml_mode%TYPE
112: default hr_api.g_varchar2
113: ,p_context_display_text IN hr_wip_transactions.context_display_text%TYPE
114: default hr_api.g_varchar2
115: );
116: -- ----------------------------------------------------------------------------

Line 114: default hr_api.g_varchar2

110: ,p_vo_xml IN VARCHAR2
111: ,p_dml_mode IN hr_wip_transactions.dml_mode%TYPE
112: default hr_api.g_varchar2
113: ,p_context_display_text IN hr_wip_transactions.context_display_text%TYPE
114: default hr_api.g_varchar2
115: );
116: -- ----------------------------------------------------------------------------
117: -- |-----------------------< pending_approval >-----------------------|
118: -- ----------------------------------------------------------------------------

Line 124: default hr_api.g_varchar2

120: (p_transaction_id IN hr_wip_transactions.transaction_id%TYPE
121: ,p_current_user_id IN fnd_user.user_id%TYPE
122: ,p_vo_xml IN VARCHAR2
123: ,p_dml_mode IN hr_wip_transactions.dml_mode%TYPE
124: default hr_api.g_varchar2
125: ,p_context_display_text IN hr_wip_transactions.context_display_text%TYPE
126: default hr_api.g_varchar2
127: );
128: --

Line 126: default hr_api.g_varchar2

122: ,p_vo_xml IN VARCHAR2
123: ,p_dml_mode IN hr_wip_transactions.dml_mode%TYPE
124: default hr_api.g_varchar2
125: ,p_context_display_text IN hr_wip_transactions.context_display_text%TYPE
126: default hr_api.g_varchar2
127: );
128: --
129: -- ----------------------------------------------------------------------------
130: -- |-----------------------< reject_for_correction >-----------------------|

Line 168: default hr_api.g_varchar2

164: ,p_item_key IN wf_items.item_key%TYPE
165: ,p_state IN hr_wip_transactions.state%TYPE
166: ,p_sub_state IN hr_wip_transactions.sub_state%TYPE
167: ,p_dml_mode IN hr_wip_transactions.dml_mode%TYPE
168: default hr_api.g_varchar2
169: ,p_vo_xml IN VARCHAR2
170: ,p_context_display_text IN hr_wip_transactions.context_display_text%TYPE
171: default hr_api.g_varchar2
172: );

Line 171: default hr_api.g_varchar2

167: ,p_dml_mode IN hr_wip_transactions.dml_mode%TYPE
168: default hr_api.g_varchar2
169: ,p_vo_xml IN VARCHAR2
170: ,p_context_display_text IN hr_wip_transactions.context_display_text%TYPE
171: default hr_api.g_varchar2
172: );
173: --
174: -- ----------------------------------------------------------------------------
175: -- |-----------------------< update_transaction >-----------------------|

Line 182: default hr_api.g_varchar2

178: (p_transaction_id IN hr_wip_transactions.transaction_id%TYPE
179: ,p_state IN hr_wip_transactions.state%TYPE
180: ,p_sub_state IN hr_wip_transactions.sub_state%TYPE
181: ,p_dml_mode IN hr_wip_transactions.dml_mode%TYPE
182: default hr_api.g_varchar2
183: ,p_vo_xml IN VARCHAR2
184: ,p_context_display_text IN hr_wip_transactions.context_display_text%TYPE
185: default hr_api.g_varchar2
186: );

Line 185: default hr_api.g_varchar2

181: ,p_dml_mode IN hr_wip_transactions.dml_mode%TYPE
182: default hr_api.g_varchar2
183: ,p_vo_xml IN VARCHAR2
184: ,p_context_display_text IN hr_wip_transactions.context_display_text%TYPE
185: default hr_api.g_varchar2
186: );
187: --
188: END hr_wip_txns;