<?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: hi   sap script in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/hi-sap-script/m-p/1909250#M378652</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;PERFORM form IN PROGRAM prog. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Additions: &lt;/P&gt;&lt;P&gt;1. ... USING    p1 p2 p3 ... &lt;/P&gt;&lt;P&gt;2. ... CHANGING p1 p2 p3 ... &lt;/P&gt;&lt;P&gt;3. ... TABLES   itab1 itab2 ... &lt;/P&gt;&lt;P&gt;4. ... IF FOUND &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In an ABAP Objects context, a more severe syntax check is performed that in other ABAP areas. See Passsing SY-REPID not allowed and Receiving SY-SUBRC not allowed. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, here you can specify the names of both the subroutine and the program in which it occurs dynamically at runtime. If you do this, you should place the variables form and prog in parentheses. The names in form and prog must be entered in uppercase, otherwise a runtime error occurs. If you do not specify any additions (such as USING) you do not need to specify the program after IN PROGRAM. In this case, the system looks for the subroutine in the current program. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Example&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DATA: RNAME(30) VALUE 'WRITE_STATISTIC',                                                                                PNAME(8)  VALUE 'ZYX_STAT'.     &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;     &lt;/P&gt;&lt;P&gt;Here Form and Program name must be written in upper case.   &lt;/P&gt;&lt;P&gt;                                      &lt;/P&gt;&lt;P&gt;PERFORM (RNAME)         IN PROGRAM ZYX_STAT.&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;PERFORM WRITE_STATISTIC IN PROGRAM (PNAME). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PERFORM (RNAME)         IN PROGRAM (PNAME). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;All three PERFORM statements have the same effect, that is, they call the subroutine 'WRITE_STATISTIC', which is defined in the program 'ZYX_STAT'. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Sruthi&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 20 Feb 2007 09:54:05 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-02-20T09:54:05Z</dc:date>
    <item>
      <title>hi   sap script</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/hi-sap-script/m-p/1909245#M378647</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;one example pl.  to show   how to use   PERFORM   in   form.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanx&lt;/P&gt;&lt;P&gt;rocky&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 20 Feb 2007 06:16:26 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/hi-sap-script/m-p/1909245#M378647</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-02-20T06:16:26Z</dc:date>
    </item>
    <item>
      <title>Re: hi   sap script</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/hi-sap-script/m-p/1909246#M378648</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;IN SAPSCRIPT FORM DO THIS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;/:   PERFORM DATA_COLLECTION IN PROGRAM Z_PROGRAM         
/:   USING &amp;amp;REGUH-VBLNR&amp;amp;                                                    
/:   USING &amp;amp;REGUH-LIFNR&amp;amp;                                                    
/:   CHANGING &amp;amp;BAREA&amp;amp;                                                       
/:   CHANGING &amp;amp;NAME&amp;amp;                                                        
/:   CHANGING &amp;amp;NAME2&amp;amp;                                                       
/:   CHANGING &amp;amp;NAME3&amp;amp;   &lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;                                                    &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;IN Z_PROGRAM DO THIS.&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;FORM DATA_COLLECTION TABLES  IN_TAB STRUCTURE itcsy
                            OUT_TAB STRUCTURE itcsy.

*your logic

ENDFORM.&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 20 Feb 2007 06:20:14 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/hi-sap-script/m-p/1909246#M378648</guid>
      <dc:creator>dani_mn</dc:creator>
      <dc:date>2007-02-20T06:20:14Z</dc:date>
    </item>
    <item>
      <title>Re: hi   sap script</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/hi-sap-script/m-p/1909247#M378649</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;Syntax in a form window:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;/: PERFORM &amp;lt;form&amp;gt; IN PROGRAM &amp;lt;prog&amp;gt;&lt;/P&gt;&lt;P&gt;/: USING &amp;amp;INVAR1&amp;amp;&lt;/P&gt;&lt;P&gt;/: USING &amp;amp;INVAR2&amp;amp;&lt;/P&gt;&lt;P&gt;......&lt;/P&gt;&lt;P&gt;/: CHANGING &amp;amp;OUTVAR1&amp;amp;&lt;/P&gt;&lt;P&gt;/: CHANGING &amp;amp;OUTVAR2&amp;amp;&lt;/P&gt;&lt;P&gt;......&lt;/P&gt;&lt;P&gt;/: ENDPERFORM&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;INVAR1 and INVAR2 are variable symbols and may be of any of the four SAPscript symbol types. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;OUTVAR1 and OUTVAR2 are local text symbols and must therefore be character strings. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The ABAP subroutine called via the command line stated above must be defined in the ABAP report prog as follows:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;FORM &amp;lt;form&amp;gt; TABLES IN_TAB STRUCTURE ITCSY&lt;/P&gt;&lt;P&gt;OUT_TAB STRUCTURE ITCSY.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;...&lt;/P&gt;&lt;P&gt;ENDFORM.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 20 Feb 2007 06:21:37 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/hi-sap-script/m-p/1909247#M378649</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-02-20T06:21:37Z</dc:date>
    </item>
    <item>
      <title>Re: hi   sap script</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/hi-sap-script/m-p/1909248#M378650</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;See some example below.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Definition in the SAPscript form:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;/: PERFORM GET_BARCODE IN PROGRAM QCJPERFO&lt;/P&gt;&lt;P&gt;/: USING &amp;amp;PAGE&amp;amp;&lt;/P&gt;&lt;P&gt;/: USING &amp;amp;NEXTPAGE&amp;amp;&lt;/P&gt;&lt;P&gt;/: CHANGING &amp;amp;BARCODE&amp;amp;&lt;/P&gt;&lt;P&gt;/: ENDPERFORM&lt;/P&gt;&lt;P&gt;/&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;/ &amp;amp;BARCODE&amp;amp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Coding of the calling ABAP program:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;REPORT QCJPERFO.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;FORM GET_BARCODE TABLES IN_PAR STUCTURE ITCSY&lt;/P&gt;&lt;P&gt;OUT_PAR STRUCTURE ITCSY.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DATA: PAGNUM LIKE SY-TABIX, "page number &lt;/P&gt;&lt;P&gt;NEXTPAGE LIKE SY-TABIX. "number of next page&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;READ TABLE IN_PAR WITH KEY &amp;#145;PAGE&amp;#146;.&lt;/P&gt;&lt;P&gt;CHECK SY-SUBRC = 0.&lt;/P&gt;&lt;P&gt;PAGNUM = IN_PAR-VALUE.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;READ TABLE IN_PAR WITH KEY &amp;#145;NEXTPAGE&amp;#146;.&lt;/P&gt;&lt;P&gt;CHECK SY-SUBRC = 0.&lt;/P&gt;&lt;P&gt;NEXTPAGE = IN_PAR-VALUE.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;READ TABLE OUT_PAR WITH KEY &amp;#145;BARCODE&amp;#146;.&lt;/P&gt;&lt;P&gt;CHECK SY-SUBRC = 0.&lt;/P&gt;&lt;P&gt;IF PAGNUM = 1.&lt;/P&gt;&lt;P&gt;OUT_PAR-VALUE = &amp;#145;|&amp;#146;. "First page &lt;/P&gt;&lt;P&gt;ELSE.&lt;/P&gt;&lt;P&gt;OUT_PAR-VALUE = &amp;#145;||&amp;#146;. "Next page &lt;/P&gt;&lt;P&gt;ENDIF.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IF NEXTPAGE = 0.&lt;/P&gt;&lt;P&gt;OUT_PAR-VALUE+2 = &amp;#145;L&amp;#146;. "Flag: last page&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ENDIF.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;MODIFY OUT_PAR INDEX SY-TABIX.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ENDFORM.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 20 Feb 2007 06:22:22 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/hi-sap-script/m-p/1909248#M378650</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-02-20T06:22:22Z</dc:date>
    </item>
    <item>
      <title>Re: hi   sap script</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/hi-sap-script/m-p/1909249#M378651</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;here i have 2 questions&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;why STRUCTURE ITCSY is used?? what is its importance??&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;second--- what is the type of in program i.e. whether it is executable or subroutine pool.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanx&lt;/P&gt;&lt;P&gt;rocky&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 20 Feb 2007 07:28:20 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/hi-sap-script/m-p/1909249#M378651</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-02-20T07:28:20Z</dc:date>
    </item>
    <item>
      <title>Re: hi   sap script</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/hi-sap-script/m-p/1909250#M378652</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;PERFORM form IN PROGRAM prog. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Additions: &lt;/P&gt;&lt;P&gt;1. ... USING    p1 p2 p3 ... &lt;/P&gt;&lt;P&gt;2. ... CHANGING p1 p2 p3 ... &lt;/P&gt;&lt;P&gt;3. ... TABLES   itab1 itab2 ... &lt;/P&gt;&lt;P&gt;4. ... IF FOUND &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In an ABAP Objects context, a more severe syntax check is performed that in other ABAP areas. See Passsing SY-REPID not allowed and Receiving SY-SUBRC not allowed. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, here you can specify the names of both the subroutine and the program in which it occurs dynamically at runtime. If you do this, you should place the variables form and prog in parentheses. The names in form and prog must be entered in uppercase, otherwise a runtime error occurs. If you do not specify any additions (such as USING) you do not need to specify the program after IN PROGRAM. In this case, the system looks for the subroutine in the current program. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Example&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DATA: RNAME(30) VALUE 'WRITE_STATISTIC',                                                                                PNAME(8)  VALUE 'ZYX_STAT'.     &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;     &lt;/P&gt;&lt;P&gt;Here Form and Program name must be written in upper case.   &lt;/P&gt;&lt;P&gt;                                      &lt;/P&gt;&lt;P&gt;PERFORM (RNAME)         IN PROGRAM ZYX_STAT.&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;PERFORM WRITE_STATISTIC IN PROGRAM (PNAME). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PERFORM (RNAME)         IN PROGRAM (PNAME). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;All three PERFORM statements have the same effect, that is, they call the subroutine 'WRITE_STATISTIC', which is defined in the program 'ZYX_STAT'. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Sruthi&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 20 Feb 2007 09:54:05 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/hi-sap-script/m-p/1909250#M378652</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-02-20T09:54:05Z</dc:date>
    </item>
    <item>
      <title>Re: hi   sap script</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/hi-sap-script/m-p/1909251#M378653</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 the type of program  'ZYX_STAT'   in   se38,  is it executable or subroutine pool??????????????????????????????&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 20 Feb 2007 11:21:16 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/hi-sap-script/m-p/1909251#M378653</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-02-20T11:21:16Z</dc:date>
    </item>
    <item>
      <title>Re: hi   sap script</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/hi-sap-script/m-p/1909252#M378654</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;   Perform program for sapscript is of type SUBROUTINE POOL.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Br, &lt;/P&gt;&lt;P&gt;Laxmi&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 23 Feb 2007 22:36:54 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/hi-sap-script/m-p/1909252#M378654</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-02-23T22:36:54Z</dc:date>
    </item>
    <item>
      <title>Re: hi   sap script</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/hi-sap-script/m-p/1909253#M378655</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi rocky robo&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Calling ABAP subroutines&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can call an ABAP subroutine from SapScript using the PERFORM statment. You can use this to get data&lt;/P&gt;&lt;P&gt;without havning to cnahge the print program. In the examole below NAME is retreived from table SCUSTOM.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SapScript&lt;/P&gt;&lt;P&gt;/:DEFINE &amp;amp;CUST&amp;amp; = '00000021'.&lt;/P&gt;&lt;P&gt;/:PERFORM GET_NAME IN PROGRAM Z_BC460_EX4_HF&lt;/P&gt;&lt;P&gt;/: USING &amp;amp;CUST&amp;amp;&lt;/P&gt;&lt;P&gt;/: CHANGING &amp;amp;NAME&amp;amp;&lt;/P&gt;&lt;P&gt;/:ENDPERFORM.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Dear &amp;amp;NAME&amp;amp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The ABAP routine&lt;/P&gt;&lt;P&gt;The ABAP routine could be defined as follows:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IMPORTANT: The structure itcsy must be used for the parameters.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;REPORT Z_HENRIKF_SCRIPT_FORM .&lt;/P&gt;&lt;P&gt;TABLES scustom.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;FORM get_name tables in_tab structure itcsy out_tab structure itcsy.&lt;/P&gt;&lt;P&gt;read table in_tab index 1.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;select single * from scustom&lt;/P&gt;&lt;P&gt;where id = in_tab-value.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if sy-subrc = 0.&lt;/P&gt;&lt;P&gt;read table out_tab index 1.&lt;/P&gt;&lt;P&gt;move scustom-name to out_tab-value.&lt;/P&gt;&lt;P&gt;modify out_tab index sy-tabix.&lt;/P&gt;&lt;P&gt;else.&lt;/P&gt;&lt;P&gt;read table out_tab index 1.&lt;/P&gt;&lt;P&gt;move 'No name' to out_tab-value.&lt;/P&gt;&lt;P&gt;modify out_tab index sy-tabix.&lt;/P&gt;&lt;P&gt;endif.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;UL&gt;&lt;LI level="2" type="ul"&gt;&lt;P&gt;You could also fill the ouput parameter table this way&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;READ TABLE out_par WITH KEY 'NAME1'.&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;out_par-value = l_name1.&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;MODIFY out_par INDEX sy-tabix.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ENDFORM.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Note that if you use more than one parameter you must use Using or Changing before every parameter !&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;/: PERFORM &amp;lt;form&amp;gt; IN PROGRAM &amp;lt;prog&amp;gt;&lt;/P&gt;&lt;P&gt;/: USING &amp;amp;INVAR1&amp;amp;&lt;/P&gt;&lt;P&gt;/: USING &amp;amp;INVAR2&amp;amp;&lt;/P&gt;&lt;P&gt;......&lt;/P&gt;&lt;P&gt;/: CHANGING &amp;amp;OUTVAR1&amp;amp;&lt;/P&gt;&lt;P&gt;/: CHANGING &amp;amp;OUTVAR2&amp;amp;&lt;/P&gt;&lt;P&gt;......&lt;/P&gt;&lt;P&gt;/: ENDPERFORM&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 24 Feb 2007 13:15:10 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/hi-sap-script/m-p/1909253#M378655</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-02-24T13:15:10Z</dc:date>
    </item>
    <item>
      <title>Re: hi   sap script</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/hi-sap-script/m-p/1909254#M378656</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;ITCSY STRUCTURE is a subroutine pool which is used in the SAP script form Editor for calling an internal or external program. If the requirement is totally differnt as the print program exits or that piece of requirement of code is not supported by print program or not present in the print program. then you can make use of this structure by writing it separately and call the same in the form editor using Perform as all of our friends suggested. ITCSY STRUCTURE hold two fields which you need to use in the program. they are fieldname and the fieldvalue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;bye&lt;/P&gt;&lt;P&gt;shamim.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 26 Feb 2007 07:18:16 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/hi-sap-script/m-p/1909254#M378656</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-02-26T07:18:16Z</dc:date>
    </item>
  </channel>
</rss>

