<ROOT>
 <APPS_INITIALIZE_DATA>
  <USER_NAME>ENGINATICS</USER_NAME>
  <RESPONSIBILITY_KEY>SYSTEM_ADMINISTRATOR</RESPONSIBILITY_KEY>
  <APPLICATION_SHORT_NAME>SYSADMIN</APPLICATION_SHORT_NAME>
 </APPS_INITIALIZE_DATA>
<LOVS>
<!-- loader xml for Enginatics Blitz Report lov: INV Organization Code (including master) -->
 <LOVS_ROW>
  <GUID>0B22DF18E239D64AE0630100007FBD85</GUID>
  <LOV_NAME>INV Organization Code (including master)</LOV_NAME>
  <VALIDATE_FROM_LIST>Y</VALIDATE_FROM_LIST>
  <LOV_QUERY>select
ood.organization_code value,
ood.organization_name description
from
org_organization_definitions ood
where
ood.organization_id in (select oav.organization_id from org_access_view oav where oav.resp_application_id=fnd_global.resp_appl_id and oav.responsibility_id=fnd_global.resp_id) and
(:$flex$.operating_unit is null or ood.operating_unit in (select haouv.organization_id from hr_all_organization_units_vl haouv where xxen_util.contains(:$flex$.operating_unit,haouv.name)=&apos;Y&apos;)) and
(:$flex$.ledger is null or ood.set_of_books_id in (select gl.ledger_id from gl_ledgers gl where xxen_util.contains(:$flex$.ledger,gl.name)=&apos;Y&apos;)) and
nvl(ood.disable_date,sysdate)&gt;=sysdate
order by
ood.organization_code</LOV_QUERY>
  <LOV_TRANSLATIONS>
   <LOV_TRANSLATIONS_ROW>
    <LANGUAGE>US</LANGUAGE>
    <DESCRIPTION>All active inventory organization codes, restricted to the current user&apos;s org access view</DESCRIPTION>
   </LOV_TRANSLATIONS_ROW>
  </LOV_TRANSLATIONS>
 </LOVS_ROW>
<!-- loader xml for Enginatics Blitz Report lov: QA Collection Plan -->
 <LOVS_ROW>
  <GUID>52162B9B8C221F1DE0630100007FADC0</GUID>
  <LOV_NAME>QA Collection Plan</LOV_NAME>
  <VALIDATE_FROM_LIST>Y</VALIDATE_FROM_LIST>
  <LOV_QUERY>select
qp.name value,
qp.description
from
qa_plans qp,
mtl_parameters mp
where
qp.organization_id=mp.organization_id(+) and
(:$flex$.Organization is null or xxen_util.contains(:$flex$.Organization,mp.organization_code)=&apos;Y&apos;) and
(qp.organization_id=0 or qp.organization_id in (select oav.organization_id from org_access_view oav where oav.resp_application_id=fnd_global.resp_appl_id and oav.responsibility_id=fnd_global.resp_id))
order by
qp.name</LOV_QUERY>
  <LOV_TRANSLATIONS>
   <LOV_TRANSLATIONS_ROW>
    <LANGUAGE>US</LANGUAGE>
   </LOV_TRANSLATIONS_ROW>
  </LOV_TRANSLATIONS>
 </LOVS_ROW>
<!-- loader xml for Enginatics Blitz Report lov: Yes -->
 <LOVS_ROW>
  <GUID>8E2FF36EDEA679D2E0530100007F1FF2</GUID>
  <LOV_NAME>Yes</LOV_NAME>
  <VALIDATE_FROM_LIST>Y</VALIDATE_FROM_LIST>
  <LOV_QUERY>select &apos;Y&apos; id, xxen_util.meaning(&apos;Y&apos;,&apos;YES_NO&apos;,0) value, null description from dual</LOV_QUERY>
  <LOV_TRANSLATIONS>
   <LOV_TRANSLATIONS_ROW>
    <LANGUAGE>US</LANGUAGE>
   </LOV_TRANSLATIONS_ROW>
  </LOV_TRANSLATIONS>
 </LOVS_ROW>
</LOVS>
<REPORTS>
<!-- loader xml for Enginatics Blitz Report: QA Collection Plan Transactions -->
 <REPORTS_ROW>
  <GUID>58FCD72D1E4C5FB8E0630100007FF786</GUID><ENABLED>Y</ENABLED>
  <SQL_TEXT>select
mp.organization_code,
qp.name plan_name,
qp.description plan_description,
xxen_util.meaning(qp.plan_type_code,&apos;COLLECTION_PLAN_TYPE&apos;,3) plan_type,
xxen_util.meaning(to_char(qpt.transaction_number),&apos;QA_TXN_NAME&apos;,700) transaction_name,
xxen_util.description(to_char(qpt.transaction_number),&apos;QA_TXN_NAME&apos;,700) transaction_description,
xxen_util.yes(case when qpt.mandatory_collection_flag=1 then &apos;Y&apos; end) mandatory_collection,
xxen_util.yes(case when qpt.background_collection_flag=1 then &apos;Y&apos; end) background_collection,
xxen_util.yes(case when qpt.enabled_flag=1 then &apos;Y&apos; end) enabled,
(select count(*) from qa_plan_transactions qpt2 where qpt.plan_id=qpt2.plan_id and qpt.transaction_number=qpt2.transaction_number) transaction_attachments,
qc.name collection_trigger,
(select qtct.form_description from qa_txn_collection_triggers qtct where qpt.transaction_number=qtct.transaction_number and qpct.collection_trigger_id=qtct.collection_trigger_id) trigger_field,
(select qtct.database_field from qa_txn_collection_triggers qtct where qpt.transaction_number=qtct.transaction_number and qpct.collection_trigger_id=qtct.collection_trigger_id) trigger_database_field,
xxen_util.meaning(qc.datatype,&apos;QA_CHAR_DATATYPE&apos;,700) trigger_datatype,
xxen_util.meaning(qpct.operator,&apos;QA_OPERATOR&apos;,700) trigger_operator,
qpct.low_value trigger_low_value,
qpct.high_value trigger_high_value,
xxen_util.user_name(nvl(qpct.created_by,qpt.created_by)) created_by,
xxen_util.client_time(nvl(qpct.creation_date,qpt.creation_date)) creation_date,
xxen_util.user_name(nvl(qpct.last_updated_by,qpt.last_updated_by)) last_updated_by,
xxen_util.client_time(nvl(qpct.last_update_date,qpt.last_update_date)) last_update_date
from
qa_plans qp,
mtl_parameters mp,
qa_plan_transactions qpt,
qa_plan_collection_triggers qpct,
qa_chars qc
where
qp.organization_id=mp.organization_id(+) and
qp.plan_id=qpt.plan_id and
qpt.plan_transaction_id=qpct.plan_transaction_id(+) and
qpct.collection_trigger_id=qc.char_id(+) and
(qp.organization_id=0 or qp.organization_id in (select oav.organization_id from org_access_view oav where oav.resp_application_id=fnd_global.resp_appl_id and oav.responsibility_id=fnd_global.resp_id)) and
1=1
order by
mp.organization_code,
qp.name,
transaction_name,
qpt.plan_transaction_id,
qc.name</SQL_TEXT>
  <VERSION_COMMENTS>Review corrections, neither altering the row set or any column value. The justification below for excluding qa_plan_transactions.eqr_layout_mode asserted that the lookup QA_PC_LAYOUT_MODE does not exist on 11i. That was wrong and is removed: the lookup does exist there at view application 250 with the same two codes as R12, and both the sibling QA Collection Plan Relationships report and the shipped QA Plan Relationship Upload render it, so a reader trusting the sentence would have judged a working column broken. The exclusion stands on its true ground, restated below: the column, not the lookup, is R12 only. The Collection Plan picker also widens, the shared QA Collection Plan list of values having excluded the seeded template plans this report returns; it now admits organization 0 and outer joins mtl_parameters, mirroring the sibling QA Collection Element list of values.

Lists every collection transaction an Oracle Quality collection plan is attached to (qa_plan_transactions), outer joined to its trigger conditions (qa_plan_collection_triggers) so that attachments which collect unconditionally are not dropped, as an inner join would drop them. The trigger&apos;s form prompt and database field are read from qa_txn_collection_triggers through scalar subqueries rather than a join, because joining that table outer to both the transaction number and the collection trigger id is a two table outer join and raises ORA-01417 on a pre 12c database. A Transaction Attachments count column exposes the fact that plan id and transaction number are deliberately not unique, so one attachment carrying several triggers can be told apart from several separate attachments of the same transaction. Audit columns fall back from the trigger to the transaction so each row&apos;s audit data belongs to the row actually shown. mtl_parameters is outer joined and organization 0 is admitted explicitly so the seeded template plans are not dropped; org_access_view inventory organization security otherwise applies. Optional Organization, Collection Plan, Plan Type, Transaction, Collection Trigger, Mandatory Collection Only and Enabled Transactions Only parameters, all injected at the single 1=1 anchor.

Deliberate decisions. qa_plan_transactions.eqr_layout_mode is not exposed. It is the only R12 only column on any table this report touches, verified absent from qa_plan_transactions on 11i by dictionary diff and by a control statement that raises ORA-00904 there while parsing on R12, and it is null on the large majority of rows, so under the standing preference for one dual use definition it is omitted and the report ships with no 11i variant and no translate rule; every other column, lookup type and construct referenced was verified to exist on 11i, the lookup QA_PC_LAYOUT_MODE that would translate the omitted column included. The Transaction parameter uses a hand written LOV rather than the Oracle standard value set QA_IMPORT_TXN_TYPE, which is table validated over a different, import only lookup type and not QA_TXN_NAME. That LOV returns the lookup code as its id rather than the translated meaning, so the bind reaches qa_plan_transactions.transaction_number as a number and the transaction number index stays usable; every QA_TXN_NAME lookup code was verified numeric on both releases. Both hand written LOVs offer only transactions and triggers actually attached to a plan the responsibility can see, and every reference to a multi value parent uses xxen_util.contains rather than equality, so a multi select parent cannot return an empty child list. The form assignment maps Collection Plan only, matching the sibling reports, because the Transaction parameter validates against the translated QA_TXN_NAME meaning and it was not established that the transactions block item carries that same string.</VERSION_COMMENTS>
  <REPORT_TRANSLATIONS>
   <REPORT_TRANSLATIONS_ROW>
    <LANGUAGE>AR</LANGUAGE>
    <REPORT_NAME>QA تقرير حركات خطة التجميع</REPORT_NAME>
    <DESCRIPTION>Application: الجودة
Source: تقرير حركات خطة التجميع (XML)
Short Name: QLTPLTXR_XML
DB package: QA_QLTPLTXR_XMLP_PKG</DESCRIPTION>
   </REPORT_TRANSLATIONS_ROW>
   <REPORT_TRANSLATIONS_ROW>
    <LANGUAGE>D</LANGUAGE>
    <REPORT_NAME>QA Prüfpläne - Transaktionen</REPORT_NAME>
    <DESCRIPTION>Application: Qualität
Source: Prüfpläne - Transaktionen (XML)
Short Name: QLTPLTXR_XML
DB package: QA_QLTPLTXR_XMLP_PKG</DESCRIPTION>
   </REPORT_TRANSLATIONS_ROW>
   <REPORT_TRANSLATIONS_ROW>
    <LANGUAGE>F</LANGUAGE>
    <REPORT_NAME>QA Etat Mouvements de procédure de collecte</REPORT_NAME>
    <DESCRIPTION>Application: Quality
Source: Etat Mouvements de procédure de collecte (XML)
Short Name: QLTPLTXR_XML
DB package: QA_QLTPLTXR_XMLP_PKG</DESCRIPTION>
   </REPORT_TRANSLATIONS_ROW>
   <REPORT_TRANSLATIONS_ROW>
    <LANGUAGE>US</LANGUAGE>
    <REPORT_NAME>QA Collection Plan Transactions</REPORT_NAME>
    <DESCRIPTION>Every collection transaction an Oracle Quality collection plan is attached to, with the trigger conditions that decide whether collection actually fires, the Mandatory Collection, Background Collection and Enabled flags, and each trigger&apos;s field, database field, datatype, operator and low and high values. Attachments that collect unconditionally are listed too, with a blank Collection Trigger.

Attaching a collection plan to a transaction is what makes Oracle Quality collect anything at all: until a plan is attached to a transaction such as Receiving Transactions or Completion Transactions it is only a definition, and nothing is ever collected against it. Trigger conditions narrow that further, so the attachment on its own does not tell you when collection happens - a plan attached to Completion Transactions with a trigger of Item equals a single assembly collects for that assembly and no other. Mandatory Collection means the transaction cannot be saved without quality results, and Background Collection means results are collected without prompting the operator.

A plan can be attached to the same transaction more than once, each attachment carrying its own trigger conditions. Transaction Attachments counts how many attachments the plan has for that transaction, so one attachment with several triggers can be told apart from several separate attachments. Trigger Field is the form prompt the trigger tests and Trigger Database Field is the column behind it, both taken from the transaction&apos;s own trigger list in qa_txn_collection_triggers, so a condition can be traced from the prompt an implementer sees to the column a data load has to supply.

Leave the parameters blank for the full picture, or narrow with Organization, Collection Plan, Plan Type, Transaction and Collection Trigger. Mandatory Collection Only and Enabled Transactions Only restrict to attachments carrying those flags. Leaving Organization blank returns every collection plan the responsibility has inventory organization access to, plus the seeded template plans, which are not owned by an inventory organization and therefore show a blank Organization Code.</DESCRIPTION>
   </REPORT_TRANSLATIONS_ROW>
   <REPORT_TRANSLATIONS_ROW>
    <LANGUAGE>ZHS</LANGUAGE>
    <REPORT_NAME>QA 收集计划事务处理报表</REPORT_NAME>
    <DESCRIPTION>Application: 质量管理系统
Source: 收集计划事务处理报表 (XML)
Short Name: QLTPLTXR_XML
DB package: QA_QLTPLTXR_XMLP_PKG</DESCRIPTION>
   </REPORT_TRANSLATIONS_ROW>
  </REPORT_TRANSLATIONS>
  <CATEGORY_ASSIGNMENTS>
   <CATEGORY_ASSIGNMENTS_ROW>
    <CATEGORY>Enginatics</CATEGORY>
   </CATEGORY_ASSIGNMENTS_ROW>
  </CATEGORY_ASSIGNMENTS>
  <ANCHORS>
   <ANCHORS_ROW>
    <ANCHOR>1=1</ANCHOR>
   </ANCHORS_ROW>
  </ANCHORS>
  <PARAMETERS>
   <PARAMETERS_ROW>
    <SORT_ORDER>1</SORT_ORDER>
    <DISPLAY_SEQUENCE>10</DISPLAY_SEQUENCE>
    <ANCHOR>1=1</ANCHOR>
    <SQL_TEXT>mp.organization_code=:organization</SQL_TEXT>
    <PARAMETER_TYPE_DSP>LOV</PARAMETER_TYPE_DSP>
    <LOV_NAME>INV Organization Code (including master)</LOV_NAME>
    <LOV_GUID>0B22DF18E239D64AE0630100007FBD85</LOV_GUID>
    <VALIDATE_FROM_LIST_DSP>Y</VALIDATE_FROM_LIST_DSP>
    <LOV_QUERY_DSP>select
ood.organization_code value,
ood.organization_name description
from
org_organization_definitions ood
where
ood.organization_id in (select oav.organization_id from org_access_view oav where oav.resp_application_id=fnd_global.resp_appl_id and oav.responsibility_id=fnd_global.resp_id) and
(:$flex$.operating_unit is null or ood.operating_unit in (select haouv.organization_id from hr_all_organization_units_vl haouv where xxen_util.contains(:$flex$.operating_unit,haouv.name)=&apos;Y&apos;)) and
(:$flex$.ledger is null or ood.set_of_books_id in (select gl.ledger_id from gl_ledgers gl where xxen_util.contains(:$flex$.ledger,gl.name)=&apos;Y&apos;)) and
nvl(ood.disable_date,sysdate)&gt;=sysdate
order by
ood.organization_code</LOV_QUERY_DSP>
    <DEFAULT_VALUE>xxen_util.previous_parameter_value(:parameter_id)</DEFAULT_VALUE>
    <PARAMETER_TRANSLATIONS>
     <PARAMETER_TRANSLATIONS_ROW>
      <LANGUAGE>AR</LANGUAGE>
      <PARAMETER_NAME>اسم الخطة</PARAMETER_NAME>
     </PARAMETER_TRANSLATIONS_ROW>
     <PARAMETER_TRANSLATIONS_ROW>
      <LANGUAGE>D</LANGUAGE>
      <PARAMETER_NAME>Planbezeichnung</PARAMETER_NAME>
     </PARAMETER_TRANSLATIONS_ROW>
     <PARAMETER_TRANSLATIONS_ROW>
      <LANGUAGE>F</LANGUAGE>
      <PARAMETER_NAME>Nom de la procédure</PARAMETER_NAME>
     </PARAMETER_TRANSLATIONS_ROW>
     <PARAMETER_TRANSLATIONS_ROW>
      <LANGUAGE>US</LANGUAGE>
      <PARAMETER_NAME>Organization</PARAMETER_NAME>
     </PARAMETER_TRANSLATIONS_ROW>
     <PARAMETER_TRANSLATIONS_ROW>
      <LANGUAGE>ZHS</LANGUAGE>
      <PARAMETER_NAME>计划名称</PARAMETER_NAME>
     </PARAMETER_TRANSLATIONS_ROW>
    </PARAMETER_TRANSLATIONS>
   </PARAMETERS_ROW>
   <PARAMETERS_ROW>
    <SORT_ORDER>2</SORT_ORDER>
    <DISPLAY_SEQUENCE>20</DISPLAY_SEQUENCE>
    <ANCHOR>1=1</ANCHOR>
    <SQL_TEXT>qp.name=:collection_plan</SQL_TEXT>
    <PARAMETER_TYPE_DSP>LOV</PARAMETER_TYPE_DSP>
    <LOV_NAME>QA Collection Plan</LOV_NAME>
    <LOV_GUID>52162B9B8C221F1DE0630100007FADC0</LOV_GUID>
    <VALIDATE_FROM_LIST_DSP>Y</VALIDATE_FROM_LIST_DSP>
    <LOV_QUERY_DSP>select
qp.name value,
qp.description
from
qa_plans qp,
mtl_parameters mp
where
qp.organization_id=mp.organization_id(+) and
(:$flex$.Organization is null or xxen_util.contains(:$flex$.Organization,mp.organization_code)=&apos;Y&apos;) and
(qp.organization_id=0 or qp.organization_id in (select oav.organization_id from org_access_view oav where oav.resp_application_id=fnd_global.resp_appl_id and oav.responsibility_id=fnd_global.resp_id))
order by
qp.name</LOV_QUERY_DSP>
    <PARAMETER_TRANSLATIONS>
     <PARAMETER_TRANSLATIONS_ROW>
      <LANGUAGE>US</LANGUAGE>
      <PARAMETER_NAME>Collection Plan</PARAMETER_NAME>
     </PARAMETER_TRANSLATIONS_ROW>
    </PARAMETER_TRANSLATIONS>
   </PARAMETERS_ROW>
   <PARAMETERS_ROW>
    <SORT_ORDER>3</SORT_ORDER>
    <DISPLAY_SEQUENCE>30</DISPLAY_SEQUENCE>
    <ANCHOR>1=1</ANCHOR>
    <SQL_TEXT>qp.plan_type_code=:plan_type</SQL_TEXT>
    <PARAMETER_TYPE_DSP>LOV Oracle</PARAMETER_TYPE_DSP>
    <LOV_NAME>QA_SRS_PLAN_TYPE_CODE</LOV_NAME>
    <VALIDATE_FROM_LIST_DSP>Y</VALIDATE_FROM_LIST_DSP>
    <LOV_QUERY_DSP>select
lookup_code id,
meaning value,
null description
from
fnd_common_lookups
where lookup_type=&apos;COLLECTION_PLAN_TYPE&apos; order by meaning</LOV_QUERY_DSP>
    <PARAMETER_TRANSLATIONS>
     <PARAMETER_TRANSLATIONS_ROW>
      <LANGUAGE>US</LANGUAGE>
      <PARAMETER_NAME>Plan Type</PARAMETER_NAME>
     </PARAMETER_TRANSLATIONS_ROW>
    </PARAMETER_TRANSLATIONS>
   </PARAMETERS_ROW>
   <PARAMETERS_ROW>
    <SORT_ORDER>4</SORT_ORDER>
    <DISPLAY_SEQUENCE>40</DISPLAY_SEQUENCE>
    <ANCHOR>1=1</ANCHOR>
    <SQL_TEXT>qpt.transaction_number=:transaction</SQL_TEXT>
    <PARAMETER_TYPE_DSP>LOV custom</PARAMETER_TYPE_DSP>
    <VALIDATE_FROM_LIST_DSP>Y</VALIDATE_FROM_LIST_DSP>
    <LOV_QUERY_DSP>select distinct
to_char(qpt.transaction_number) id,
xxen_util.meaning(to_char(qpt.transaction_number),&apos;QA_TXN_NAME&apos;,700) value,
xxen_util.description(to_char(qpt.transaction_number),&apos;QA_TXN_NAME&apos;,700) description
from
qa_plans qp,
mtl_parameters mp,
qa_plan_transactions qpt
where
qp.organization_id=mp.organization_id(+) and
qp.plan_id=qpt.plan_id and
(:$flex$.Organization is null or xxen_util.contains(:$flex$.Organization,mp.organization_code)=&apos;Y&apos;) and
(:$flex$.Collection_Plan is null or xxen_util.contains(:$flex$.Collection_Plan,qp.name)=&apos;Y&apos;) and
(qp.organization_id=0 or qp.organization_id in (select oav.organization_id from org_access_view oav where oav.resp_application_id=fnd_global.resp_appl_id and oav.responsibility_id=fnd_global.resp_id))
order by
value</LOV_QUERY_DSP>
    <PARAMETER_TRANSLATIONS>
     <PARAMETER_TRANSLATIONS_ROW>
      <LANGUAGE>US</LANGUAGE>
      <PARAMETER_NAME>Transaction</PARAMETER_NAME>
     </PARAMETER_TRANSLATIONS_ROW>
    </PARAMETER_TRANSLATIONS>
   </PARAMETERS_ROW>
   <PARAMETERS_ROW>
    <SORT_ORDER>5</SORT_ORDER>
    <DISPLAY_SEQUENCE>50</DISPLAY_SEQUENCE>
    <ANCHOR>1=1</ANCHOR>
    <SQL_TEXT>qc.name=:collection_trigger</SQL_TEXT>
    <PARAMETER_TYPE_DSP>LOV custom</PARAMETER_TYPE_DSP>
    <VALIDATE_FROM_LIST_DSP>Y</VALIDATE_FROM_LIST_DSP>
    <LOV_QUERY_DSP>select distinct
qc.name value,
qc.prompt description
from
qa_plans qp,
mtl_parameters mp,
qa_plan_transactions qpt,
qa_plan_collection_triggers qpct,
qa_chars qc
where
qp.organization_id=mp.organization_id(+) and
qp.plan_id=qpt.plan_id and
qpt.plan_transaction_id=qpct.plan_transaction_id and
qpct.collection_trigger_id=qc.char_id and
(:$flex$.Organization is null or xxen_util.contains(:$flex$.Organization,mp.organization_code)=&apos;Y&apos;) and
(:$flex$.Collection_Plan is null or xxen_util.contains(:$flex$.Collection_Plan,qp.name)=&apos;Y&apos;) and
(:$flex$.Transaction is null or xxen_util.contains(:$flex$.Transaction,to_char(qpt.transaction_number))=&apos;Y&apos;) and
(qp.organization_id=0 or qp.organization_id in (select oav.organization_id from org_access_view oav where oav.resp_application_id=fnd_global.resp_appl_id and oav.responsibility_id=fnd_global.resp_id))
order by
qc.name</LOV_QUERY_DSP>
    <PARAMETER_TRANSLATIONS>
     <PARAMETER_TRANSLATIONS_ROW>
      <LANGUAGE>US</LANGUAGE>
      <PARAMETER_NAME>Collection Trigger</PARAMETER_NAME>
     </PARAMETER_TRANSLATIONS_ROW>
    </PARAMETER_TRANSLATIONS>
   </PARAMETERS_ROW>
   <PARAMETERS_ROW>
    <SORT_ORDER>6</SORT_ORDER>
    <DISPLAY_SEQUENCE>60</DISPLAY_SEQUENCE>
    <ANCHOR>1=1</ANCHOR>
    <SQL_TEXT>qpt.mandatory_collection_flag=1</SQL_TEXT>
    <PARAMETER_TYPE_DSP>LOV</PARAMETER_TYPE_DSP>
    <LOV_NAME>Yes</LOV_NAME>
    <LOV_GUID>8E2FF36EDEA679D2E0530100007F1FF2</LOV_GUID>
    <VALIDATE_FROM_LIST_DSP>Y</VALIDATE_FROM_LIST_DSP>
    <LOV_QUERY_DSP>select &apos;Y&apos; id, xxen_util.meaning(&apos;Y&apos;,&apos;YES_NO&apos;,0) value, null description from dual</LOV_QUERY_DSP>
    <MATCHING_VALUE>Y</MATCHING_VALUE>
    <PARAMETER_TRANSLATIONS>
     <PARAMETER_TRANSLATIONS_ROW>
      <LANGUAGE>US</LANGUAGE>
      <PARAMETER_NAME>Mandatory Collection Only</PARAMETER_NAME>
     </PARAMETER_TRANSLATIONS_ROW>
    </PARAMETER_TRANSLATIONS>
   </PARAMETERS_ROW>
   <PARAMETERS_ROW>
    <SORT_ORDER>7</SORT_ORDER>
    <DISPLAY_SEQUENCE>70</DISPLAY_SEQUENCE>
    <ANCHOR>1=1</ANCHOR>
    <SQL_TEXT>qpt.enabled_flag=1</SQL_TEXT>
    <PARAMETER_TYPE_DSP>LOV</PARAMETER_TYPE_DSP>
    <LOV_NAME>Yes</LOV_NAME>
    <LOV_GUID>8E2FF36EDEA679D2E0530100007F1FF2</LOV_GUID>
    <VALIDATE_FROM_LIST_DSP>Y</VALIDATE_FROM_LIST_DSP>
    <LOV_QUERY_DSP>select &apos;Y&apos; id, xxen_util.meaning(&apos;Y&apos;,&apos;YES_NO&apos;,0) value, null description from dual</LOV_QUERY_DSP>
    <MATCHING_VALUE>Y</MATCHING_VALUE>
    <PARAMETER_TRANSLATIONS>
     <PARAMETER_TRANSLATIONS_ROW>
      <LANGUAGE>US</LANGUAGE>
      <PARAMETER_NAME>Enabled Transactions Only</PARAMETER_NAME>
     </PARAMETER_TRANSLATIONS_ROW>
    </PARAMETER_TRANSLATIONS>
   </PARAMETERS_ROW>
  </PARAMETERS>
  <TEMPLATES>
  </TEMPLATES>
  <DEFAULT_TEMPLATES>
  </DEFAULT_TEMPLATES>
  <UPLOAD_COLUMNS>
  </UPLOAD_COLUMNS>
  <UPLOAD_PARAMETERS>
  </UPLOAD_PARAMETERS>
  <UPLOAD_SQLS>
  </UPLOAD_SQLS>
 </REPORTS_ROW>
</REPORTS>
</ROOT>
