DBA Data[Home] [Help]

APPS.QA_ERES_UTIL dependencies on QA_SS_CONST

Line 178: l_char_id := QA_SS_CONST.esignature_status;

174:
175: BEGIN
176:
177: -- Get the Char ID of eSignature Status element
178: l_char_id := QA_SS_CONST.esignature_status;
179:
180: -- Get the Prompt for the eSignature Status element
181: l_prompt := QA_CHARS_API.prompt( l_char_id );
182:

Line 353: p_char_id => qa_ss_const.esignature_status); -- check if this API checks for Eres Profile

349: QA_ERES_UTIL.get_result_esig_status
350: (p_occurrence => p_occurrence,
351: p_coll_id => p_collection_id,
352: p_plan_id => p_plan_id,
353: p_char_id => qa_ss_const.esignature_status); -- check if this API checks for Eres Profile
354:
355: -- check if the eSignature Status is PENDING.
356: -- We can safely compare it with Harcoded PENDING String
357: -- as Description is different in for transalation issues