<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Not allow to write on a matchcode in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/not-allow-to-write-on-a-matchcode/m-p/9450271#M1741358</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I've created a matchcode and I'm using it on an abap program.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="L0S52"&gt;parameters&lt;SPAN class="L0S55"&gt;: myparameter&lt;/SPAN&gt; &lt;SPAN class="L0S52"&gt;like zmytable&lt;/SPAN&gt;&lt;SPAN class="L0S70"&gt;-myfield&lt;/SPAN&gt; &lt;SPAN class="L0S52"&gt;matchcode &lt;/SPAN&gt;object zmymatchcode &lt;SPAN class="L0S52"&gt;default 'myparam&lt;/SPAN&gt;&lt;SPAN class="L0S33"&gt;'&lt;/SPAN&gt;&lt;SPAN class="L0S55"&gt;.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My question is, how can I get that my matchcode can't be written?&amp;nbsp; I mean, the user only must select the available values of the matchcode.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;&lt;P&gt;Regards.&lt;/P&gt;&lt;P&gt;&lt;SPAN class="L0S52"&gt;&lt;SPAN class="L0S55"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 27 May 2013 13:46:37 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2013-05-27T13:46:37Z</dc:date>
    <item>
      <title>Not allow to write on a matchcode</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/not-allow-to-write-on-a-matchcode/m-p/9450271#M1741358</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I've created a matchcode and I'm using it on an abap program.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="L0S52"&gt;parameters&lt;SPAN class="L0S55"&gt;: myparameter&lt;/SPAN&gt; &lt;SPAN class="L0S52"&gt;like zmytable&lt;/SPAN&gt;&lt;SPAN class="L0S70"&gt;-myfield&lt;/SPAN&gt; &lt;SPAN class="L0S52"&gt;matchcode &lt;/SPAN&gt;object zmymatchcode &lt;SPAN class="L0S52"&gt;default 'myparam&lt;/SPAN&gt;&lt;SPAN class="L0S33"&gt;'&lt;/SPAN&gt;&lt;SPAN class="L0S55"&gt;.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My question is, how can I get that my matchcode can't be written?&amp;nbsp; I mean, the user only must select the available values of the matchcode.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;&lt;P&gt;Regards.&lt;/P&gt;&lt;P&gt;&lt;SPAN class="L0S52"&gt;&lt;SPAN class="L0S55"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 27 May 2013 13:46:37 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/not-allow-to-write-on-a-matchcode/m-p/9450271#M1741358</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2013-05-27T13:46:37Z</dc:date>
    </item>
    <item>
      <title>Re: Not allow to write on a matchcode</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/not-allow-to-write-on-a-matchcode/m-p/9450272#M1741359</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If there are not too many values, you could define the PARAMETERS myparameter &lt;SPAN class="qtext"&gt;AS LISTBOX VISIBLE LENGTH 30.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Else disable the input-ability of the parameter in the PBO (AT SELECTION-SCREEN OUTPUT) using a &lt;SPAN class="qtext"&gt;MODIF ID value to identify field. Manage the F4 in POV (AT SELECTION-SCREEN ON VALUE-REQUEST) and store the selected value in a global variable or no-display parameter (to be stored in variant) that you will copy in PBO back to the parameter, also trigger a PAI/PBO cycle after the F4 execution using a tool like FM &lt;/SPAN&gt;SAPGUI_SET_FUNCTIONCODE or static method CL_GUI_CFW=&amp;gt;SET_NEW_OK_CODE.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="qtext"&gt;Regards,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="qtext"&gt;Raymond&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 27 May 2013 14:17:15 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/not-allow-to-write-on-a-matchcode/m-p/9450272#M1741359</guid>
      <dc:creator>RaymondGiuseppi</dc:creator>
      <dc:date>2013-05-27T14:17:15Z</dc:date>
    </item>
    <item>
      <title>Re: Not allow to write on a matchcode</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/not-allow-to-write-on-a-matchcode/m-p/9450273#M1741360</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Raymond,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please, could you give an example in abap? My list has only two values and I want to avoid that the field could be changed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks again.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 28 May 2013 06:54:07 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/not-allow-to-write-on-a-matchcode/m-p/9450273#M1741360</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2013-05-28T06:54:07Z</dc:date>
    </item>
    <item>
      <title>Re: Not allow to write on a matchcode</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/not-allow-to-write-on-a-matchcode/m-p/9450274#M1741361</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;H6&gt;No coding with ddic&lt;/H6&gt;&lt;P&gt;Create a domain via SE11 and give the two allowed values, use this domain in one data element affected to the dynpro field and define the &lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;&lt;P&gt;PARAMETERS: parametername TYPE datalementname &lt;SPAN class="qtext"&gt;AS LISTBOX VISIBLE LENGTH 60.&lt;/SPAN&gt;&lt;/P&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;H6&gt;&lt;SPAN class="qtext"&gt;Coding &lt;/SPAN&gt;&lt;/H6&gt;&lt;P&gt;&lt;SPAN class="qtext"&gt;Use of FM likeVRM_SET_VALUES. &lt;/SPAN&gt;&lt;SPAN class="qtext"&gt;Use same syntax for the parameter, but fill "manullay" the value list and attach it to field with this FM.&lt;/SPAN&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;&lt;P&gt;INITIALIZATION.&lt;/P&gt;&lt;P&gt;* LISTBOX values&lt;/P&gt;&lt;P&gt;&amp;nbsp; DATA: vrm_id TYPE vrm_id,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; vrm_values TYPE vrm_values,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; vrm_value LIKE LINE OF vrm_values.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; CLEAR vrm_value.&lt;/P&gt;&lt;P&gt;&amp;nbsp; vrm_value-key = 'V01'.&lt;/P&gt;&lt;P&gt;&amp;nbsp; vrm_value-text = text-v01.&lt;/P&gt;&lt;P&gt;&amp;nbsp; APPEND vrm_value TO vrm_values.&lt;/P&gt;&lt;P&gt;&amp;nbsp; vrm_value-key = 'V02'.&lt;/P&gt;&lt;P&gt;&amp;nbsp; vrm_value-text = text-v02.&lt;/P&gt;&lt;P&gt;&amp;nbsp; APPEND vrm_value TO vrm_values.&lt;/P&gt;&lt;P&gt;&amp;nbsp; vrm_id = 'PARAMETERNAME'.&lt;/P&gt;&lt;P&gt;&amp;nbsp; CALL FUNCTION 'VRM_SET_VALUES'&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; EXPORTING&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; id&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; = vrm_id&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; values&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; = vrm_values&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; EXCEPTIONS&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; id_illegal_name = 1&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; OTHERS&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; = 2.&lt;/P&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;H6&gt;Radiobuttons&lt;/H6&gt;&lt;P&gt;Define your prameter as NO-DISPLAY. Create a radiobutton group with one button for each value. put the radiobutton in a group without frame, and fill the hidden parameter in a AT SELECTION-SCREEN ON GROUP, you could also insure coherence, set/unset radiobutton depending on value of parameter (e.g. when your report is called via SUBMIT)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And many, many other solutions, just try.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Raymond&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 28 May 2013 07:13:49 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/not-allow-to-write-on-a-matchcode/m-p/9450274#M1741361</guid>
      <dc:creator>RaymondGiuseppi</dc:creator>
      <dc:date>2013-05-28T07:13:49Z</dc:date>
    </item>
    <item>
      <title>Re: Not allow to write on a matchcode</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/not-allow-to-write-on-a-matchcode/m-p/9450275#M1741362</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ok,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks a lot.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 28 May 2013 07:21:50 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/not-allow-to-write-on-a-matchcode/m-p/9450275#M1741362</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2013-05-28T07:21:50Z</dc:date>
    </item>
  </channel>
</rss>

