<?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 Regarding CALL_BACK parameter in subroutine in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/regarding-call-back-parameter-in-subroutine/m-p/4102327#M980983</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;I have an upgrade error  ( version 4.7) saying ' FORM DOES NOT EXIST OR  NUMBER OF PARAMETERS ARE DIFFERENT'     .&lt;/P&gt;&lt;P&gt;I dont know why i am getting this error can u please check out my code and help me.&lt;/P&gt;&lt;P&gt;Here is my code:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;SUB ROUTINE BODY&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;form api_label_segment using lb like zlblparms call_back.&lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;This interface allows the calling app to create labels in rows, for&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;example program ZMBCTMP1 prints 4 stg types on a single label. In&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;the definition of the JOB, a header and trailer may be specified as&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;normal. However, for 'Segmented' labels the MID section has a special&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;structure as follows:&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;    posns:  12345678901234567890&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;            STG_TYPE_HDR        (This is the TOP of the label)&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;            STG_TYPE_SEG 0004   (0004 is the max segments/label)&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;            STG_TYPE_FTR        (Bottom of label eg TRM:\  )&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;This routines accesses MID by index so it can get the formats it&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;needs depending on the number of segments printed. This is very&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;convenient for the calling program since it does not need to know&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;anything about no fo segments or format names, this code calls the&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;header/footer etc. at the appropriate times in the run. All the&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;calling code needs to do is keep calling this form repeatedly (for&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;each 'item' (or segment) it wants to print.&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;Global variable seg_ctr keeps track of how many segments within the&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;label have been printed (and so when the 'footer' is needed etc).&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;See notes above on label_api_hdr for more details of this function.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;  data: label_name like zbcf-fname.&lt;/P&gt;&lt;P&gt;  data: t(80) occurs 0 with header line.&lt;/P&gt;&lt;P&gt;*--Is header required at this point?&lt;/P&gt;&lt;P&gt;  if seg_ctr eq 0.            " causes the header to print ...&lt;/P&gt;&lt;P&gt;    perform get_mid_entry tables t using 1.&lt;/P&gt;&lt;P&gt;    &lt;U&gt;debug&lt;/U&gt;if sy-subrc ne 0&lt;/P&gt;&lt;P&gt;             'Cannot find FIRST Entry in MID table (115)' '' ''.&lt;/P&gt;&lt;P&gt;    read table t into label_name index 1.&lt;/P&gt;&lt;P&gt;    lb-labelname = label_name.&lt;/P&gt;&lt;P&gt;    perform print_a_label using 1 lb.&lt;/P&gt;&lt;P&gt;    seg_ctr = 1.&lt;/P&gt;&lt;P&gt;  endif.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;*--Print the segment...&lt;/P&gt;&lt;P&gt;  perform get_mid_entry tables t using 2.&lt;/P&gt;&lt;P&gt;  &lt;U&gt;debug&lt;/U&gt;if sy-subrc ne 0&lt;/P&gt;&lt;P&gt;                 'Cannot Find 2nd Entry in MID table (121)' '' ''.&lt;/P&gt;&lt;P&gt;  read table t into label_name index 1.&lt;/P&gt;&lt;P&gt;  read table t into max_segs index 2.&lt;/P&gt;&lt;P&gt;  perform (call_back) in program (sy-cprog)&lt;/P&gt;&lt;P&gt;                         tables t using seg_ctr if found.&lt;/P&gt;&lt;P&gt;  lb-labelname = label_name.&lt;/P&gt;&lt;P&gt;  perform print_a_label using 1 lb.&lt;/P&gt;&lt;P&gt;  add 1 to seg_ctr.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;*--Print the footer if needed now...&lt;/P&gt;&lt;P&gt;  if seg_ctr gt max_segs.           " causes the trailer to print ...&lt;/P&gt;&lt;P&gt;    perform get_mid_entry tables t using 3.&lt;/P&gt;&lt;P&gt;    &lt;U&gt;debug&lt;/U&gt;if sy-subrc ne 0&lt;/P&gt;&lt;P&gt;                  'Cannot Find 3rd Entry in MID table (127)' '' ''.&lt;/P&gt;&lt;P&gt;    read table t into label_name index 1.&lt;/P&gt;&lt;P&gt;    lb-labelname = label_name.&lt;/P&gt;&lt;P&gt;    perform print_a_label using 1 lb.&lt;/P&gt;&lt;P&gt;    seg_ctr = 0.&lt;/P&gt;&lt;P&gt;  endif.&lt;/P&gt;&lt;P&gt;endform.                    "API_LABEL_SEGMENT&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PERFORM STATEMENT&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PERFORM API_LABEL_SEGMENT(SAPLZBCD) USING LB.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Radhika&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 10 Jul 2008 13:54:26 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-07-10T13:54:26Z</dc:date>
    <item>
      <title>Regarding CALL_BACK parameter in subroutine</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/regarding-call-back-parameter-in-subroutine/m-p/4102327#M980983</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;I have an upgrade error  ( version 4.7) saying ' FORM DOES NOT EXIST OR  NUMBER OF PARAMETERS ARE DIFFERENT'     .&lt;/P&gt;&lt;P&gt;I dont know why i am getting this error can u please check out my code and help me.&lt;/P&gt;&lt;P&gt;Here is my code:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;SUB ROUTINE BODY&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;form api_label_segment using lb like zlblparms call_back.&lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;This interface allows the calling app to create labels in rows, for&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;example program ZMBCTMP1 prints 4 stg types on a single label. In&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;the definition of the JOB, a header and trailer may be specified as&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;normal. However, for 'Segmented' labels the MID section has a special&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;structure as follows:&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;    posns:  12345678901234567890&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;            STG_TYPE_HDR        (This is the TOP of the label)&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;            STG_TYPE_SEG 0004   (0004 is the max segments/label)&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;            STG_TYPE_FTR        (Bottom of label eg TRM:\  )&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;This routines accesses MID by index so it can get the formats it&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;needs depending on the number of segments printed. This is very&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;convenient for the calling program since it does not need to know&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;anything about no fo segments or format names, this code calls the&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;header/footer etc. at the appropriate times in the run. All the&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;calling code needs to do is keep calling this form repeatedly (for&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;each 'item' (or segment) it wants to print.&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;Global variable seg_ctr keeps track of how many segments within the&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;label have been printed (and so when the 'footer' is needed etc).&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;See notes above on label_api_hdr for more details of this function.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;  data: label_name like zbcf-fname.&lt;/P&gt;&lt;P&gt;  data: t(80) occurs 0 with header line.&lt;/P&gt;&lt;P&gt;*--Is header required at this point?&lt;/P&gt;&lt;P&gt;  if seg_ctr eq 0.            " causes the header to print ...&lt;/P&gt;&lt;P&gt;    perform get_mid_entry tables t using 1.&lt;/P&gt;&lt;P&gt;    &lt;U&gt;debug&lt;/U&gt;if sy-subrc ne 0&lt;/P&gt;&lt;P&gt;             'Cannot find FIRST Entry in MID table (115)' '' ''.&lt;/P&gt;&lt;P&gt;    read table t into label_name index 1.&lt;/P&gt;&lt;P&gt;    lb-labelname = label_name.&lt;/P&gt;&lt;P&gt;    perform print_a_label using 1 lb.&lt;/P&gt;&lt;P&gt;    seg_ctr = 1.&lt;/P&gt;&lt;P&gt;  endif.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;*--Print the segment...&lt;/P&gt;&lt;P&gt;  perform get_mid_entry tables t using 2.&lt;/P&gt;&lt;P&gt;  &lt;U&gt;debug&lt;/U&gt;if sy-subrc ne 0&lt;/P&gt;&lt;P&gt;                 'Cannot Find 2nd Entry in MID table (121)' '' ''.&lt;/P&gt;&lt;P&gt;  read table t into label_name index 1.&lt;/P&gt;&lt;P&gt;  read table t into max_segs index 2.&lt;/P&gt;&lt;P&gt;  perform (call_back) in program (sy-cprog)&lt;/P&gt;&lt;P&gt;                         tables t using seg_ctr if found.&lt;/P&gt;&lt;P&gt;  lb-labelname = label_name.&lt;/P&gt;&lt;P&gt;  perform print_a_label using 1 lb.&lt;/P&gt;&lt;P&gt;  add 1 to seg_ctr.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;*--Print the footer if needed now...&lt;/P&gt;&lt;P&gt;  if seg_ctr gt max_segs.           " causes the trailer to print ...&lt;/P&gt;&lt;P&gt;    perform get_mid_entry tables t using 3.&lt;/P&gt;&lt;P&gt;    &lt;U&gt;debug&lt;/U&gt;if sy-subrc ne 0&lt;/P&gt;&lt;P&gt;                  'Cannot Find 3rd Entry in MID table (127)' '' ''.&lt;/P&gt;&lt;P&gt;    read table t into label_name index 1.&lt;/P&gt;&lt;P&gt;    lb-labelname = label_name.&lt;/P&gt;&lt;P&gt;    perform print_a_label using 1 lb.&lt;/P&gt;&lt;P&gt;    seg_ctr = 0.&lt;/P&gt;&lt;P&gt;  endif.&lt;/P&gt;&lt;P&gt;endform.                    "API_LABEL_SEGMENT&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PERFORM STATEMENT&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PERFORM API_LABEL_SEGMENT(SAPLZBCD) USING LB.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Radhika&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 10 Jul 2008 13:54:26 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/regarding-call-back-parameter-in-subroutine/m-p/4102327#M980983</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-07-10T13:54:26Z</dc:date>
    </item>
    <item>
      <title>Re: Regarding CALL_BACK parameter in subroutine</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/regarding-call-back-parameter-in-subroutine/m-p/4102328#M980984</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;remove call_back from the form ..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;form api_label_segment using lb like zlblparms.&lt;/STRONG&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 10 Jul 2008 13:57:49 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/regarding-call-back-parameter-in-subroutine/m-p/4102328#M980984</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-07-10T13:57:49Z</dc:date>
    </item>
    <item>
      <title>Re: Regarding CALL_BACK parameter in subroutine</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/regarding-call-back-parameter-in-subroutine/m-p/4102329#M980985</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;use like this...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;form api_label_segment using lb like zlblparms .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;or check like this..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;form api_label_segment using lb like zlblparms zlblparmscall_back .( no gap  at the end) .&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 10 Jul 2008 13:58:03 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/regarding-call-back-parameter-in-subroutine/m-p/4102329#M980985</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-07-10T13:58:03Z</dc:date>
    </item>
    <item>
      <title>Re: Regarding CALL_BACK parameter in subroutine</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/regarding-call-back-parameter-in-subroutine/m-p/4102330#M980986</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We need to make changes only in the perform statement.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 10 Jul 2008 14:26:23 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/regarding-call-back-parameter-in-subroutine/m-p/4102330#M980986</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-07-10T14:26:23Z</dc:date>
    </item>
  </channel>
</rss>

