APPS.QA_MQA_PLAN_ELEMENTS dependencies on QA_CHARS

Line 33: -- info. Previously the where clause used to have 3 outer joins qa_chars,

29: BEGIN
30: -- When user doesnt enter any spec, a -1 is passed in..........not a null.
31:
32: -- rkaza bugs 2753703, 2767550. 01/27/2003. Refer to bug texts for more
33: -- info. Previously the where clause used to have 3 outer joins qa_chars,
34: -- qa_spec_chars, qa_specs and the user entered spec value. It gave
35: -- incorrect results. For Eg: 1) Either the char is removed if no spec matches. 2) More
36: -- than one row results for the same char if the char is present in some
37: -- other spec other than the one specified by user. 3) The char is retained

Line 170: qa_chars qc,

166: qp.decimal_precision,
167: qc.lower_user_defined_limit,
168: qscqs.lower_user_defined_limit) lower_user_defined_limit
169: FROM
170: qa_chars qc,
171: qa_plan_chars qp,
172: (SELECT
173: qsc.CHAR_ID,
174: qsc.ENABLED_FLAG,

Line 459: l_spec_limit qa_chars.target_value%TYPE;

455: p_qpc_dec_prec NUMBER,
456: p_qc_spec_limit VARCHAR2,
457: p_qsc_spec_limit VARCHAR2) RETURN VARCHAR2 IS
458:
459: l_spec_limit qa_chars.target_value%TYPE;
460:
461: BEGIN
462: IF p_spec_char_id IS NULL THEN
463: l_spec_limit := p_qc_spec_limit;