DBA Data[Home] [Help]

APPS.QA_ERES_UTIL dependencies on QA_SS_CONST

Line 193: l_char_id := QA_SS_CONST.esignature_status;

189:
190: BEGIN
191:
192: -- Get the Char ID of eSignature Status element
193: l_char_id := QA_SS_CONST.esignature_status;
194:
195: -- Get the Prompt for the eSignature Status element
196: l_prompt := QA_CHARS_API.prompt( l_char_id );
197:

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

364: QA_ERES_UTIL.get_result_esig_status
365: (p_occurrence => p_occurrence,
366: p_coll_id => p_collection_id,
367: p_plan_id => p_plan_id,
368: p_char_id => qa_ss_const.esignature_status); -- check if this API checks for Eres Profile
369:
370: -- check if the eSignature Status is PENDING.
371: -- We can safely compare it with Harcoded PENDING String
372: -- as Description is different in for transalation issues