<?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 Re: samt transaction in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/samt-transaction/m-p/2126898#M446690</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi abhishek&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;u&amp;gt;&amp;lt;i&amp;gt;&amp;lt;b&amp;gt;ABAP Program Mass Processing&amp;lt;/b&amp;gt;&amp;lt;/i&amp;gt;&amp;lt;/u&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Transaction SAMT allows you to perform tests on sets of associated&lt;/P&gt;&lt;P&gt;programs.&lt;/P&gt;&lt;P&gt;To do this, you specify a subroutine which you call with an external&lt;/P&gt;&lt;P&gt;PERFORM for each individual program.&lt;/P&gt;&lt;P&gt;A program name and the associated TRDIR entry is then passed to a test&lt;/P&gt;&lt;P&gt;subroutine.&lt;/P&gt;&lt;P&gt;If the test detects any problem, it analyzes the information, error or&lt;/P&gt;&lt;P&gt;warning and outputs a note on the program location (external PERFORM&lt;/P&gt;&lt;P&gt;SAMT_HINT(SAPRSAMT)).&lt;/P&gt;&lt;P&gt;One note can have several messages consisting of any amount of text&lt;/P&gt;&lt;P&gt;(external PERFORM SAMT_MESSAGE(SAPRSAMT)).&lt;/P&gt;&lt;P&gt;For documentation about writing these subroutines, refer to the program&lt;/P&gt;&lt;P&gt;documentation for RSAMTFEX.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;u&amp;gt;&amp;lt;i&amp;gt;&amp;lt;b&amp;gt;Special functions&amp;lt;/b&amp;gt;&amp;lt;/i&amp;gt;&amp;lt;/u&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;u&amp;gt;&amp;lt;i&amp;gt;&amp;lt;b&amp;gt;Transporting tests&amp;lt;/b&amp;gt;&amp;lt;/i&amp;gt;&amp;lt;/u&amp;gt;&lt;/P&gt;&lt;P&gt;This function allows you to transport a test to another&lt;/P&gt;&lt;P&gt;system, but the system transports only a table entry, not the&lt;/P&gt;&lt;P&gt;associated test program.&lt;/P&gt;&lt;P&gt;Transported tests are usually displayed in green.&lt;/P&gt;&lt;P&gt;These transports are only deleted irrevocably if the deletion&lt;/P&gt;&lt;P&gt;was also transported.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Creating program sets&lt;/P&gt;&lt;P&gt;With this function, you create a program set belonging to a&lt;/P&gt;&lt;P&gt;particular test. You can describe the set on the next&lt;/P&gt;&lt;P&gt;selection screen.&lt;/P&gt;&lt;P&gt;If you want to enable certain program sets with a complicated&lt;/P&gt;&lt;P&gt;selection to be created several times, you can define a&lt;/P&gt;&lt;P&gt;variant of the program RSAMTSEL (in the usual way).&lt;/P&gt;&lt;P&gt;If you want to determine the program set according to&lt;/P&gt;&lt;P&gt;different criteria, you can use your own subroutine. This must&lt;/P&gt;&lt;P&gt;be part of the main program for the test, have the name&lt;/P&gt;&lt;P&gt;DETERMINE_PROGRAMSET and the following interface:&lt;/P&gt;&lt;P&gt;FORM DETERMINE_PROGRAMSET.&lt;/P&gt;&lt;P&gt;TABLES P_PROGRAMS TYPE PROGRAMS&lt;/P&gt;&lt;P&gt;USING P_FORM TYPE FORM&lt;/P&gt;&lt;P&gt;CHANGING P_SHORTTEXT TYPE SHORTTEXT.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Executing a test&lt;/P&gt;&lt;P&gt;The subroutine belonging to the test is called for each&lt;/P&gt;&lt;P&gt;program in a program set (in alphabetical order).&lt;/P&gt;&lt;P&gt;Since locks are set, several different sessions can perform&lt;/P&gt;&lt;P&gt;tests on the same program set at the same time. This means you&lt;/P&gt;&lt;P&gt;can reduce considerably the total amount of time needed to&lt;/P&gt;&lt;P&gt;process a program set.&lt;/P&gt;&lt;P&gt;There is also a function to execute tests in the background.&lt;/P&gt;&lt;P&gt;The function for performing a test on all machines initiates&lt;/P&gt;&lt;P&gt;the scheduling of a background job that executes a test on all&lt;/P&gt;&lt;P&gt;"suitable" machines (with RFC). Since this function increases&lt;/P&gt;&lt;P&gt;the load on the entire system considerably, this type of&lt;/P&gt;&lt;P&gt;background job should only be run at night.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Copying a program set&lt;/P&gt;&lt;P&gt;This function creates a new version of an existing program&lt;/P&gt;&lt;P&gt;set. You can execute the test for all the programs concerned.&lt;/P&gt;&lt;P&gt;In this way, you can detect any change in the results.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Extracting a program set&lt;/P&gt;&lt;P&gt;With this function, you create a new program set from an&lt;/P&gt;&lt;P&gt;existing program set.&lt;/P&gt;&lt;P&gt;For example, you can extract just the programs that cause&lt;/P&gt;&lt;P&gt;errors.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Copying a program set to another test&lt;/P&gt;&lt;P&gt;This function copies a program set from one test to another&lt;/P&gt;&lt;P&gt;test.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;u&amp;gt;&amp;lt;i&amp;gt;&amp;lt;b&amp;gt;User statistics&amp;lt;/b&amp;gt;&amp;lt;/i&amp;gt;&amp;lt;/u&amp;gt;&lt;/P&gt;&lt;P&gt;If you want to determine the persons responsible for all the&lt;/P&gt;&lt;P&gt;program classes and development classes of the selected&lt;/P&gt;&lt;P&gt;programs, you can generate a list of all the relevant user&lt;/P&gt;&lt;P&gt;names.&lt;/P&gt;&lt;P&gt;This is accompanied by statistics giving the number of&lt;/P&gt;&lt;P&gt;programs, informations, warnings and errors.&lt;/P&gt;&lt;P&gt;&amp;lt;u&amp;gt;&amp;lt;i&amp;gt;&amp;lt;b&amp;gt;&lt;/P&gt;&lt;P&gt;Code statistics&amp;lt;/b&amp;gt;&amp;lt;/i&amp;gt;&amp;lt;/u&amp;gt;&lt;/P&gt;&lt;P&gt;You can also generate a statistic containing all the notes&lt;/P&gt;&lt;P&gt;codes that have occurred.&lt;/P&gt;&lt;P&gt;The text for a code is any first line of a note belonging to&lt;/P&gt;&lt;P&gt;the code.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can branch to the relevant results display from either the&lt;/P&gt;&lt;P&gt;user statistic or the code statistic.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;u&amp;gt;&amp;lt;i&amp;gt;&amp;lt;b&amp;gt;Displaying the results&amp;lt;/b&amp;gt;&amp;lt;/i&amp;gt;&amp;lt;/u&amp;gt;&lt;/P&gt;&lt;P&gt;There are two types of results display - standard display and&lt;/P&gt;&lt;P&gt;private display using your own program.&lt;/P&gt;&lt;P&gt;You can reduce the standard display by specifying certain&lt;/P&gt;&lt;P&gt;criteria.&lt;/P&gt;&lt;P&gt;If you want to perform non-standard results analyses, you can&lt;/P&gt;&lt;P&gt;handle the display and processing of test results yourself. To&lt;/P&gt;&lt;P&gt;do this, you call the program containing the test subroutine&lt;/P&gt;&lt;P&gt;directly (with SUBMIT ... VIA SELECTION-SCREEN). The test,&lt;/P&gt;&lt;P&gt;program set and version IDs are then passed via memory.&lt;/P&gt;&lt;P&gt;Since this involves a lot of programming and assumes some&lt;/P&gt;&lt;P&gt;knowledge of the structure of results tables, you are advised&lt;/P&gt;&lt;P&gt;against such results analysis.&lt;/P&gt;&lt;P&gt;Instead, you should make a development request for this&lt;/P&gt;&lt;P&gt;transaction in order to get any defective function included in&lt;/P&gt;&lt;P&gt;the standard.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Editing&lt;/P&gt;&lt;P&gt;By double-clicking on a message for a note in the standard&lt;/P&gt;&lt;P&gt;display, you can go into the ABAP/4 editor and jump to the&lt;/P&gt;&lt;P&gt;relevant place in the program.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Refreshing&lt;/P&gt;&lt;P&gt;You can refresh display lists at any time. This makes changes&lt;/P&gt;&lt;P&gt;made by other modi visible.&lt;/P&gt;&lt;P&gt;Return -&amp;gt;&lt;/P&gt;&lt;P&gt;SAMT&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I think SAMT is obsolete after SAP introduced Code Inspector /available as of 6.10 as part of the standard delivery, downport is possible for 46C/.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;navjot&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;reward if helpfull&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Message was edited by: &lt;/P&gt;&lt;P&gt;        navjot sharma&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Message was edited by: &lt;/P&gt;&lt;P&gt;        navjot sharma&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 04 Apr 2007 10:14:32 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-04-04T10:14:32Z</dc:date>
    <item>
      <title>samt transaction</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/samt-transaction/m-p/2126896#M446688</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What is SAMT transaction used for?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 Apr 2007 10:09:43 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/samt-transaction/m-p/2126896#M446688</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-04-04T10:09:43Z</dc:date>
    </item>
    <item>
      <title>Re: samt transaction</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/samt-transaction/m-p/2126897#M446689</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi Abhishek,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SAMT   SAPRSAMT       ABAP Program Set Processing&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw04/helpdata/en/79/c55458b3dc11d5993800508b6b8b11/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw04/helpdata/en/79/c55458b3dc11d5993800508b6b8b11/content.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Santosh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 Apr 2007 10:14:02 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/samt-transaction/m-p/2126897#M446689</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-04-04T10:14:02Z</dc:date>
    </item>
    <item>
      <title>Re: samt transaction</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/samt-transaction/m-p/2126898#M446690</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi abhishek&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;u&amp;gt;&amp;lt;i&amp;gt;&amp;lt;b&amp;gt;ABAP Program Mass Processing&amp;lt;/b&amp;gt;&amp;lt;/i&amp;gt;&amp;lt;/u&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Transaction SAMT allows you to perform tests on sets of associated&lt;/P&gt;&lt;P&gt;programs.&lt;/P&gt;&lt;P&gt;To do this, you specify a subroutine which you call with an external&lt;/P&gt;&lt;P&gt;PERFORM for each individual program.&lt;/P&gt;&lt;P&gt;A program name and the associated TRDIR entry is then passed to a test&lt;/P&gt;&lt;P&gt;subroutine.&lt;/P&gt;&lt;P&gt;If the test detects any problem, it analyzes the information, error or&lt;/P&gt;&lt;P&gt;warning and outputs a note on the program location (external PERFORM&lt;/P&gt;&lt;P&gt;SAMT_HINT(SAPRSAMT)).&lt;/P&gt;&lt;P&gt;One note can have several messages consisting of any amount of text&lt;/P&gt;&lt;P&gt;(external PERFORM SAMT_MESSAGE(SAPRSAMT)).&lt;/P&gt;&lt;P&gt;For documentation about writing these subroutines, refer to the program&lt;/P&gt;&lt;P&gt;documentation for RSAMTFEX.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;u&amp;gt;&amp;lt;i&amp;gt;&amp;lt;b&amp;gt;Special functions&amp;lt;/b&amp;gt;&amp;lt;/i&amp;gt;&amp;lt;/u&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;u&amp;gt;&amp;lt;i&amp;gt;&amp;lt;b&amp;gt;Transporting tests&amp;lt;/b&amp;gt;&amp;lt;/i&amp;gt;&amp;lt;/u&amp;gt;&lt;/P&gt;&lt;P&gt;This function allows you to transport a test to another&lt;/P&gt;&lt;P&gt;system, but the system transports only a table entry, not the&lt;/P&gt;&lt;P&gt;associated test program.&lt;/P&gt;&lt;P&gt;Transported tests are usually displayed in green.&lt;/P&gt;&lt;P&gt;These transports are only deleted irrevocably if the deletion&lt;/P&gt;&lt;P&gt;was also transported.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Creating program sets&lt;/P&gt;&lt;P&gt;With this function, you create a program set belonging to a&lt;/P&gt;&lt;P&gt;particular test. You can describe the set on the next&lt;/P&gt;&lt;P&gt;selection screen.&lt;/P&gt;&lt;P&gt;If you want to enable certain program sets with a complicated&lt;/P&gt;&lt;P&gt;selection to be created several times, you can define a&lt;/P&gt;&lt;P&gt;variant of the program RSAMTSEL (in the usual way).&lt;/P&gt;&lt;P&gt;If you want to determine the program set according to&lt;/P&gt;&lt;P&gt;different criteria, you can use your own subroutine. This must&lt;/P&gt;&lt;P&gt;be part of the main program for the test, have the name&lt;/P&gt;&lt;P&gt;DETERMINE_PROGRAMSET and the following interface:&lt;/P&gt;&lt;P&gt;FORM DETERMINE_PROGRAMSET.&lt;/P&gt;&lt;P&gt;TABLES P_PROGRAMS TYPE PROGRAMS&lt;/P&gt;&lt;P&gt;USING P_FORM TYPE FORM&lt;/P&gt;&lt;P&gt;CHANGING P_SHORTTEXT TYPE SHORTTEXT.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Executing a test&lt;/P&gt;&lt;P&gt;The subroutine belonging to the test is called for each&lt;/P&gt;&lt;P&gt;program in a program set (in alphabetical order).&lt;/P&gt;&lt;P&gt;Since locks are set, several different sessions can perform&lt;/P&gt;&lt;P&gt;tests on the same program set at the same time. This means you&lt;/P&gt;&lt;P&gt;can reduce considerably the total amount of time needed to&lt;/P&gt;&lt;P&gt;process a program set.&lt;/P&gt;&lt;P&gt;There is also a function to execute tests in the background.&lt;/P&gt;&lt;P&gt;The function for performing a test on all machines initiates&lt;/P&gt;&lt;P&gt;the scheduling of a background job that executes a test on all&lt;/P&gt;&lt;P&gt;"suitable" machines (with RFC). Since this function increases&lt;/P&gt;&lt;P&gt;the load on the entire system considerably, this type of&lt;/P&gt;&lt;P&gt;background job should only be run at night.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Copying a program set&lt;/P&gt;&lt;P&gt;This function creates a new version of an existing program&lt;/P&gt;&lt;P&gt;set. You can execute the test for all the programs concerned.&lt;/P&gt;&lt;P&gt;In this way, you can detect any change in the results.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Extracting a program set&lt;/P&gt;&lt;P&gt;With this function, you create a new program set from an&lt;/P&gt;&lt;P&gt;existing program set.&lt;/P&gt;&lt;P&gt;For example, you can extract just the programs that cause&lt;/P&gt;&lt;P&gt;errors.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Copying a program set to another test&lt;/P&gt;&lt;P&gt;This function copies a program set from one test to another&lt;/P&gt;&lt;P&gt;test.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;u&amp;gt;&amp;lt;i&amp;gt;&amp;lt;b&amp;gt;User statistics&amp;lt;/b&amp;gt;&amp;lt;/i&amp;gt;&amp;lt;/u&amp;gt;&lt;/P&gt;&lt;P&gt;If you want to determine the persons responsible for all the&lt;/P&gt;&lt;P&gt;program classes and development classes of the selected&lt;/P&gt;&lt;P&gt;programs, you can generate a list of all the relevant user&lt;/P&gt;&lt;P&gt;names.&lt;/P&gt;&lt;P&gt;This is accompanied by statistics giving the number of&lt;/P&gt;&lt;P&gt;programs, informations, warnings and errors.&lt;/P&gt;&lt;P&gt;&amp;lt;u&amp;gt;&amp;lt;i&amp;gt;&amp;lt;b&amp;gt;&lt;/P&gt;&lt;P&gt;Code statistics&amp;lt;/b&amp;gt;&amp;lt;/i&amp;gt;&amp;lt;/u&amp;gt;&lt;/P&gt;&lt;P&gt;You can also generate a statistic containing all the notes&lt;/P&gt;&lt;P&gt;codes that have occurred.&lt;/P&gt;&lt;P&gt;The text for a code is any first line of a note belonging to&lt;/P&gt;&lt;P&gt;the code.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can branch to the relevant results display from either the&lt;/P&gt;&lt;P&gt;user statistic or the code statistic.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;u&amp;gt;&amp;lt;i&amp;gt;&amp;lt;b&amp;gt;Displaying the results&amp;lt;/b&amp;gt;&amp;lt;/i&amp;gt;&amp;lt;/u&amp;gt;&lt;/P&gt;&lt;P&gt;There are two types of results display - standard display and&lt;/P&gt;&lt;P&gt;private display using your own program.&lt;/P&gt;&lt;P&gt;You can reduce the standard display by specifying certain&lt;/P&gt;&lt;P&gt;criteria.&lt;/P&gt;&lt;P&gt;If you want to perform non-standard results analyses, you can&lt;/P&gt;&lt;P&gt;handle the display and processing of test results yourself. To&lt;/P&gt;&lt;P&gt;do this, you call the program containing the test subroutine&lt;/P&gt;&lt;P&gt;directly (with SUBMIT ... VIA SELECTION-SCREEN). The test,&lt;/P&gt;&lt;P&gt;program set and version IDs are then passed via memory.&lt;/P&gt;&lt;P&gt;Since this involves a lot of programming and assumes some&lt;/P&gt;&lt;P&gt;knowledge of the structure of results tables, you are advised&lt;/P&gt;&lt;P&gt;against such results analysis.&lt;/P&gt;&lt;P&gt;Instead, you should make a development request for this&lt;/P&gt;&lt;P&gt;transaction in order to get any defective function included in&lt;/P&gt;&lt;P&gt;the standard.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Editing&lt;/P&gt;&lt;P&gt;By double-clicking on a message for a note in the standard&lt;/P&gt;&lt;P&gt;display, you can go into the ABAP/4 editor and jump to the&lt;/P&gt;&lt;P&gt;relevant place in the program.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Refreshing&lt;/P&gt;&lt;P&gt;You can refresh display lists at any time. This makes changes&lt;/P&gt;&lt;P&gt;made by other modi visible.&lt;/P&gt;&lt;P&gt;Return -&amp;gt;&lt;/P&gt;&lt;P&gt;SAMT&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I think SAMT is obsolete after SAP introduced Code Inspector /available as of 6.10 as part of the standard delivery, downport is possible for 46C/.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;navjot&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;reward if helpfull&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Message was edited by: &lt;/P&gt;&lt;P&gt;        navjot sharma&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Message was edited by: &lt;/P&gt;&lt;P&gt;        navjot sharma&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 Apr 2007 10:14:32 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/samt-transaction/m-p/2126898#M446690</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-04-04T10:14:32Z</dc:date>
    </item>
    <item>
      <title>Re: samt transaction</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/samt-transaction/m-p/2126899#M446691</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;mishra,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;   ABAP Development Under Unicode &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A Unicode-enabled ABAP program (UP) is a program in which all Unicode checks are effective. Such a program returns the same results in a non-Unicode system (NUS) as in a Unicode system (US). In order to perform the relevant syntax checks, you must activate the Unicode flag in the screens of the program and class attributes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In a US, you can only execute programs for which the Unicode flag is set. In future, the Unicode flag must be set for all SAP programs to enable them to run on a US. If the Unicode flag is set for a program, the syntax is checked and the program executed according to the rules described in this document, regardless of whether the system is a US or an NUS. From now on, the Unicode flag must be set for all new programs and classes that are created.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the Unicode flag is not set, a program can only be executed in an NUS. The syntactical and semantic changes described below do not apply to such programs. However, you can use all language extensions that have been introduced in the process of the conversion to Unicode. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As a result of the modifications and restrictions associated with the Unicode flag, programs are executed in both Unicode and non-Unicode systems with the same semantics to a large degree. In rare cases, however, differences may occur. Programs that are designed to run on both systems therefore need to be tested on both platforms.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You are recommended to follow the procedure below to make your programs US-compliant:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The UNICODE task in transaction SAMT performs first an NUS and then a US syntax check for a selected program set. For an overview of the syntax errors by systems, programs and authors, consult the following document in SAPNet: Alternatively, you can start the ABAP program RSUNISCAN_FINAL to determine the Unicode-relevant syntax errors for a single program. &lt;/P&gt;&lt;P&gt;Before you can set the Unicode flag in the NUS in the attributes of the program concerned, all syntax errors must be removed. &lt;/P&gt;&lt;P&gt;Having enabled the Unicode flag in the NUS, you can run the syntax check for this program. To display a maximum of 50 syntax errors simultaneously, choose Utilities -&amp;gt; Settings -&amp;gt; Editor in the ABAP Editor and select the corresponding checkbox. &lt;/P&gt;&lt;P&gt;Once all syntactical requirements are met in the NUS, you must test the program both in the NUS and US. The purpose of this test is to recognize any runtime errors and make sure that the results are correct in both systems. To rule out runtime errors in advance, you should always type field symbols and parameters so that any potential problems can be detected during the syntax check. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Don't forget to reward if useful&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 Apr 2007 10:14:58 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/samt-transaction/m-p/2126899#M446691</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-04-04T10:14:58Z</dc:date>
    </item>
    <item>
      <title>Re: samt transaction</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/samt-transaction/m-p/2126900#M446692</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When you start the SAMT transaction, you can choose the task you want to schedule. Just double-click. From there use 'Create Program Set' (or press F5). Here you can create the selection for which programs you want to check. Fill in the selection and press create program set.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This might take some time...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After the program set is created, start the task: Select Task --&amp;gt; Execute --&amp;gt; in Background. Once it's finished, you can select "display results" (function F2).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;vijay&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;rewards if helpfull.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 Apr 2007 11:13:36 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/samt-transaction/m-p/2126900#M446692</guid>
      <dc:creator>Vijay</dc:creator>
      <dc:date>2007-04-04T11:13:36Z</dc:date>
    </item>
  </channel>
</rss>

