Need to print a text of 255 char from a Ztable into sap script printing.

Hi All,
I Have a requirement where I have to fetch an incoterm description maintained in Z table according to incoterm key and print it via SAP script.
I am getting the complete 255 char data in the variable which I am passing to the script from the driver program, However in the output I can see only 80 characters getting printed.
My code
Subroutine created in se71
DEFINE &L_VTEXT& = SPACE
PERFORM GET_INCOTERMS IN PROGRAM ZMM_MEDRUCK
USING &EKKO-INCO1&
CHANGING &L_VTEXT&
ENDPERFORM
Form created in Driver program:
FORM get_incoterms TABLES pt_input STRUCTURE itcsy
                                             pt_output STRUCTURE itcsy.
   DATA: l_vtext TYPE zincoterms-vtext.
   READ TABLE pt_input WITH KEY name = 'EKKO-INCO1'.
   SELECT SINGLE vtext FROM zincoterms INTO l_vtext
       WHERE inco1 = pt_input-value.
   CLEAR pt_output.
   pt_output-value = l_vtext.
   MODIFY pt_output TRANSPORTING value WHERE name = 'L_VTEXT'.
ENDFORM.                 
Note: Here pt_output-value is having a complete 255 char data
I have tried printing it using offset as well, However complete text is not getting printed.
Please help me in solving this issue as it is urgent requirement.
Thanks and Regards,
Ankit

Hi Ankit,
   pt_output-value = l_vtext.
   MODIFY pt_output TRANSPORTING value WHERE name = 'L_VTEXT1'.
   pt_output-value = l_vtext+80.
   MODIFY pt_output TRANSPORTING value WHERE name = 'L_VTEXT2'.
   pt_output-value = l_vtext+160.
   MODIFY pt_output TRANSPORTING value WHERE name = 'L_VTEXT3'.
   pt_output-value = l_vtext+240.
   MODIFY pt_output TRANSPORTING value WHERE name = 'L_VTEXT4'.
I guess it's a workaround if it's really urgent. Present variables next to one another.
regards,
Edgar

Similar Messages

  • List of standard sap scripts/print programs in SAP MM and SD modules ??

    Hi,
    I have worked in medruck only. Can anyone give me a list of other standard sap scripts/print program names in SAP MM, FI/CO and SD modules, which often needs to be  modified by the client ?
    thanks

    press f4 in SE71
    then press application heirarchy, expand the modules which ever u want.
    regards.
    santhosh reddy
    Reward if useful

  • SAP Script Printing

    Hi,
    Can we have 'Collate' functionality as in Word document in SAP script printing.

    Hi Rathakrishnan,
    It's not a functionality of SAP script, but you have to set an attribute of the output device. Use transaction SPAD, select your printer and hit button Output Device. Then go to Tab 'Output attributes' and set 'Copies as separate output requests (in SAP System)'. This is similar to the collate functionality.
    Does this solve your problem?
    Regards,
    John.

  • HOW TO PRINT LONG TEXT OF 255 CHARACTER IN ALV GRID instead of132 Char's

    Hi sir/mam
    i'm sreekar can any one help me on this please
    "As I took a variable 'STR' with 255 length, But still ALV GRID DISPLAYS the same 132 characters, and
    When I download the report into excel it is showing the 250 charactered text"
    how can i print it in alv grid
    FORM BUID_CATALOG .
      DATA : COL_POS TYPE I.
      COL_POS = COL_POS + 1.
    *--DECLARING FIELDCATALOG FOR HEADER
      LT_FCAT-COL_POS = COL_POS.
      LT_FCAT-FIELDNAME = 'EBELN'.
      LT_FCAT-TABNAME = 'LT_FINAL'.
      LT_FCAT-SELTEXT_L = 'Purch.doc.no.'(002).
      LT_FCAT-REF_FIELDNAME = 'EBELN'.
      LT_FCAT-REF_TABNAME = 'EKKO'.
      APPEND LT_FCAT.
      CLEAR LT_FCAT.
      LT_FCAT-COL_POS = COL_POS.
      LT_FCAT-FIELDNAME = 'BEDAT'.
      LT_FCAT-TABNAME = 'LT_FINAL'.
      LT_FCAT-SELTEXT_L = 'Po Date'(003).
      LT_FCAT-REF_FIELDNAME = 'EBDAT'.
      LT_FCAT-EDIT_MASK = '__.__.____'.
      APPEND LT_FCAT.
      CLEAR LT_FCAT.
      LT_FCAT-COL_POS = COL_POS.
      LT_FCAT-FIELDNAME = 'EKGRP'.
      LT_FCAT-TABNAME = 'LT_FINAL'.
      LT_FCAT-SELTEXT_L = 'Purch.Grp'(004).
      LT_FCAT-REF_FIELDNAME = 'BKGRP'.
      APPEND LT_FCAT.
      CLEAR LT_FCAT.
      LT_FCAT-COL_POS = COL_POS.
      LT_FCAT-FIELDNAME = 'EKNAM'.
      LT_FCAT-TABNAME = 'LT_FINAL'.
      LT_FCAT-SELTEXT_L = 'Purch.Grp. Name'(005).
      LT_FCAT-REF_FIELDNAME = 'EKNAM'.
      APPEND LT_FCAT.
      CLEAR LT_FCAT.
      LT_FCAT-COL_POS = COL_POS.
      LT_FCAT-FIELDNAME = 'LIFNR'.
      LT_FCAT-TABNAME = 'LT_FINAL'.
      LT_FCAT-SELTEXT_L = 'Vendor No.'(006).
      LT_FCAT-REF_FIELDNAME = 'ELIFN'.
      APPEND LT_FCAT.
      CLEAR LT_FCAT.
      LT_FCAT-COL_POS = COL_POS.
      LT_FCAT-FIELDNAME = 'NAME1'.
      LT_FCAT-TABNAME = 'LT_FINAL'.
      LT_FCAT-SELTEXT_L = 'Vendor Name'(007).
      LT_FCAT-REF_FIELDNAME = 'NAME1_GP'.
      APPEND LT_FCAT.
      CLEAR LT_FCAT.
      LT_FCAT-COL_POS = COL_POS.
      LT_FCAT-FIELDNAME = 'ZTERM'.
      LT_FCAT-TABNAME = 'LT_FINAL'.
      LT_FCAT-SELTEXT_L = 'Pay.Code'(008).
      LT_FCAT-REF_FIELDNAME = 'ZTERM'.
      APPEND LT_FCAT.
      CLEAR LT_FCAT.
      LT_FCAT-COL_POS = COL_POS.
      LT_FCAT-FIELDNAME = 'TEXT1'.
      LT_FCAT-TABNAME = 'LT_FINAL'.
      LT_FCAT-SELTEXT_L = 'Own explanation'(009).
      LT_FCAT-REF_FIELDNAME = 'DZTERM'.
      LT_FCAT-OUTPUTLEN = '30'.
      LT_FCAT-DDICTXT = 'L'.
      APPEND LT_FCAT.
      CLEAR LT_FCAT.
      LT_FCAT-COL_POS = COL_POS.
      LT_FCAT-FIELDNAME = 'WAERS'.
      LT_FCAT-TABNAME = 'LT_FINAL'.
      LT_FCAT-SELTEXT_L = 'Curr'(010).
      LT_FCAT-REF_FIELDNAME = 'WAERS'.
      APPEND LT_FCAT.
      CLEAR LT_FCAT.
      LT_FCAT-COL_POS = COL_POS.
      LT_FCAT-FIELDNAME = 'NETWR'.
      LT_FCAT-TABNAME = 'LT_FINAL'.
      LT_FCAT-SELTEXT_L = 'Net Value'(011).
      LT_FCAT-REF_FIELDNAME = 'BWERT'.
      APPEND LT_FCAT.
      CLEAR LT_FCAT.
    ENDFORM.                    " BUID_CATALOG
    CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
        EXPORTING
          I_BUFFER_ACTIVE         = 'X'
          I_BACKGROUND_ID         = 'ALV_BACKGROUND'
          IS_LAYOUT               = GS_LAYOUT
          IT_FIELDCAT             = LT_FCAT[]
          I_SAVE                  = G_SAVE
          IS_VARIANT              = GS_VARIANT
        IMPORTING
          E_EXIT_CAUSED_BY_CALLER = G_EXIT_CAUSED_BY_CALLER
          ES_EXIT_CAUSED_BY_USER  = GS_EXIT_CAUSED_BY_USER
        TABLES
          T_OUTTAB                = LT_FINAL[]
        EXCEPTIONS
          PROGRAM_ERROR           = 1
          OTHERS                  = 2.
      IF SY-SUBRC = 0.
        IF G_EXIT_CAUSED_BY_CALLER = 'X'.
        ELSE.
          IF GS_EXIT_CAUSED_BY_USER-BACK = 'X'.       "F3
            EXIT.
          ELSE.
            IF GS_EXIT_CAUSED_BY_USER-EXIT = 'X'.     "F15
              LEAVE TO SCREEN 1000.
            ELSE.
              IF GS_EXIT_CAUSED_BY_USER-CANCEL = 'X'. "F12
                LEAVE TO SCREEN 1000.
              ELSE.
                EXIT.
              ENDIF.
            ENDIF.
          ENDIF.
        ENDIF.
      ELSE.
      ENDIF.
    ENDFORM.                    " DISPLAY_DATA
    CALL FUNCTION 'READ_TEXT'
    EXPORTING
    CLIENT = SY-MANDT
    ID = 'F15' "ls_thead-tdid PAYMENT TERMS
    LANGUAGE = SY-LANGU "ls_thead-tdspras "CURRENT LANGUAGE 'E'
    NAME = NAME "ls_thead-tdname PO NUMBER LW_EKKO-EBELN
    OBJECT = 'EKKO' "ls_thead-tdobject TABLE NAME EKKO
    IMPORTING
    HEADER = HTEXT
    TABLES
    LINES = LTEXT
    EXCEPTIONS
    ID = 1
    LANGUAGE = 2
    NAME = 3
    NOT_FOUND = 4
    OBJECT = 5
    REFERENCE_CHECK = 6
    WRONG_ACCESS_TO_ARCHIVE = 7
    OTHERS = 8.
    IF SY-SUBRC = 0.
    LOOP AT LTEXT.
    IF LTEXT-TDLINE NE ''.
    MOVE LTEXT-TDLINE TO WA_WORD-TEXT.
    APPEND WA_WORD TO LT_SENTENCE.
    ENDIF.
    ENDLOOP.
    ENDIF.
    LOOP AT LT_SENTENCE INTO WA_WORD.
    COUNT = COUNT + 1.
    IF COUNT = 1.
    STR = WA_WORD-TEXT.
    LW_FINAL-TEXT1 = STR.
    ELSEIF COUNT = 2 OR COUNT = 3 OR COUNT = 4 OR COUNT = 5 OR COUNT = 6 OR COUNT = 7 OR COUNT = 8.
    CONCATENATE STR WA_WORD-TEXT INTO STR SEPARATED BY SPACE.
    LW_FINAL-TEXT1 = STR.
    ENDIF.
    ENDLOOP.

    can you provide an example of how to wrap the text i have like this please see the below code and correct if any errors
    FORM GET_TEXT_LINES .
      DATA :NAME TYPE THEAD-TDNAME.
      NAME = LW_EKKO-EBELN.
      V_TABIX = SY-TABIX.
    CALLING FUNCTION READ_TEXT FOR PAYMENT TEXTS
      CALL FUNCTION 'READ_TEXT'
        EXPORTING
          CLIENT                  = SY-MANDT          "CLIENT ID 200/600/400
          ID                      = 'F15' "ls_thead-tdid "PAYMENT TERMS TEXT ID 'F15'
          LANGUAGE                = SY-LANGU "ls_thead-tdspras "CURRENT LANGUAGE 'E'
          NAME                    = NAME "ls_thead-tdname "PO NUMBER LW_EKKO-EBELN
          OBJECT                  = 'EKKO' "ls_thead-tdobject "TABLE NAME EKKO
        IMPORTING
          HEADER                  = HTEXT "LS_THEAD
        TABLES
          LINES                   = LTEXT "LT_LINES[]
        EXCEPTIONS
          ID                      = 1
          LANGUAGE                = 2
          NAME                    = 3
          NOT_FOUND               = 4
          OBJECT                  = 5
          REFERENCE_CHECK         = 6
          WRONG_ACCESS_TO_ARCHIVE = 7
          OTHERS                  = 8.
      IF SY-SUBRC = 0.
        LOOP AT LTEXT.
          IF LTEXT-TDLINE NE ''.
            MOVE LTEXT-TDLINE TO WA_WORD-TEXT.
            APPEND WA_WORD TO LT_SENTENCE.
          ENDIF.
        ENDLOOP.
      ENDIF.
    Word Wrap the text in multiple lines
      LOOP AT LT_SENTENCE INTO WA_WORD.
        CALL FUNCTION 'RKD_WORD_WRAP'
          EXPORTING
            TEXTLINE            = WA_WORD-TEXT
             OUTPUTLEN           = 100
          TABLES
            OUT_LINES           = LT_SENTENCE
          EXCEPTIONS
            OUTPUTLEN_TOO_LARGE = 1
            OTHERS              = 2.
        IF SY-SUBRC EQ 0.
             IF not LT_SENTENCE IS INITIAL.
          READ TABLE LT_SENTENCE INTO WA_WORD INDEX v_tabix.
          LW_FINAL-TEXT1 = WA_WORD_TEXT.
          MODIFY LT_FINAL FROM LW_FINAL INDEX V_TABIX.
      ENDLOOP.
      CLEAR: LT_SENTENCE.
    ENDFORM.                    " GET_TEXT_LINES
    *&      Form  LAYOUT_INIT
          text
         -->P_GS_LAYOUT  text
    FORM LAYOUT_INIT  USING RS_LAYOUT TYPE SLIS_LAYOUT_ALV.
    *"Build layout for list display
      RS_LAYOUT-DETAIL_POPUP      = 'X'.
    ENDFORM.                    " LAYOUT_INIT
    *&      Form  EVENTTAB_BUILD
          text
         -->P_GT_EVENTS[]  text
    FORM EVENTTAB_BUILD  USING RT_EVENTS TYPE SLIS_T_EVENT.
    *"Registration of events to happen during list display
      DATA: LS_EVENT TYPE SLIS_ALV_EVENT.
      CALL FUNCTION 'REUSE_ALV_EVENTS_GET'
        EXPORTING
          I_LIST_TYPE = 0
        IMPORTING
          ET_EVENTS   = RT_EVENTS.
      READ TABLE RT_EVENTS WITH KEY NAME = SLIS_EV_AFTER_LINE_OUTPUT
                               INTO LS_EVENT.
      IF SY-SUBRC = 0.
        APPEND LS_EVENT TO RT_EVENTS.
      ENDIF.
    ENDFORM.                    " EVENTTAB_BUILD
    *&      Form  AFTER_LINE_OUTPUT
          text
    -->  p1        text
    <--  p2        text
    FORM AFTER_LINE_OUTPUT.
    CLEAR :COUNT,LT_SENTENCE.
    LOOP AT LT_SENTENCE INTO WA_WORD.
      READ TABLE LT_SENTENCE INTO WA_WORD INDEX V_TABIX.
      CHECK SY-SUBRC = 0.
    CALL FUNCTION 'RKD_WORD_WRAP'
        EXPORTING
          TEXTLINE  = WA_WORD-TEXT
          OUTPUTLEN = 20
        TABLES
          OUT_LINES = LT_SENTENCE.
      DESCRIBE TABLE LT_SENTENCE LINES V_TABIX.
      CHECK V_TABIX > 1.
        COUNT = COUNT + 1.                                                   
        IF COUNT = 1.                                                      
          STR = WA_WORD-TEXT.                                                         
          LW_FINAL-TEXT1 = STR.                                          
        ELSEIF COUNT = 2 OR COUNT = 3 OR COUNT = 4 OR COUNT = 5 OR COUNT = 6 OR COUNT = 7 OR COUNT = 8.
          CONCATENATE STR WA_WORD-TEXT INTO STR SEPARATED BY SPACE.
          LW_FINAL-TEXT1 = STR.
        ENDIF.
      ENDLOOP.
    ENDFORM.                    " AFTER_LINE_OUTPUT

  • How to transfer data more than 255 char from excel sheet to internal table.

    Hello Experts,
    I have a requirement where i have a text field in the excel sheet of more than 255 char and need to be updated in the text element. To do that i need to transfer the excel sheet data to an internal table where one of the field is more than 255 char.
    in the standard function module it works only upto 255 char. Can you help me if we have some other way to get more than 255 char in the internal table from excel sheet.
    Thanks in Advance.
    BR,
    RaJ.

    Using .xls, it is not possible transfer data more than 255 characters from excel sheet. However if the excel sheet is saved as Comma Delimited format or Tab Delimited format, then using GUI_DOWNLOAD function module data more than 255 characters can be transferred.
    File name should be : .csv (Comma Delimited format)  or .txt (Tab Delimited format)
    File Type would still remain 'ASC' while calling function module GUI_DOWNLOAD
    Also In the internal table declare the field type as String or LCHAR.
    Eg:
    TYPES: begin of ty_file,
            col_a TYPE string,
          end of ty_file.
    DATA: i_file type standard table
                   of ty_file
                 with header line
    CALL FUNCTION 'GUI_UPLOAD'
      EXPORTING
        FILENAME                      =  'C:\test.csv'
      TABLES
        DATA_TAB                      = i_file

  • Firefox prints garbled text no matter what, from my XP-SP3 HT-P4 to my HP LJ 1200 PCL

    I am using FF 3.6.13 on a HT-P4, 3 GHz, with XP-SP3, 4Gig RAM lots of HD space. Every other application on my machine prints fine to my HP LaserJet 1200 PCL (even MS Explorer and G-Chrome) but no matter what I do in terms of changing settings or fonts, no matter what webpage or HTML file I pull up in it, FF prints garbled text. Some times not all of the text is garbled but usually the parts I really need are the ones garbled.

    I wonder whether anyone can give me advice on the above problem, thanks. Have upgraded to Firefox 9.

  • Print text on back side of last page in sap script

    Hi All,
    In Script PO i have to print 'Terms and Conditions' text only on the back side of last page of the PO.
    Presently script contains two pages ( FIRST, NEXT).
    FIRST  with attributes :
       next page as  NEXT , Print mode T.
    NEXT  with attributes :
       next page as NEXT and print mode T
    Please help us in solving issue.
    Thanks and Regards
    Venkata Swamy

    Hi ,
    In Script PO i have to print 'Terms and Conditions' text only on the back side of last page of the PO.
    Presently script contains THREE pages ( FIRST, NEXT, TERMS).
    FIRST with attributes :
    next page as NEXT , Print mode T.
    NEXT with attributes :
    next page as NEXT and print mode T
    TERMS with attributes :
    next page as ' '.
    I Created 'TERMS AND CONDITION' window.For TERMS page i selected 'TERMS AND CONDITION' window only.
    So page window of 'TERMS'  is 'TERMS AND CONDITION'  and i included standard text in 'TERMS AND CONDITION' window.
    If PO contains 9 pages( that means MAIN WINDOW data flows up to 9th page with footer also ).
    So i have to print standard text(Terms and conditions) back side of 9th page only not on all pages.
    So total PO contians 9 pages with 10 prints.
    Please help to solve the issue
    Thanks and Regards
    Venkata swamy

  • Sap Scripts-printing the text in a single line

    In Sap Scripts I would like to have my text in a single line. For that I have used the extended line (=) tag. But It is not working.
    Can anyone help me how can I achieve this.
    Actually how many characters I can put in a single line. I think it is 72. But my text is less than 72 characters.
    Can anyone Please help me.
    Regards
    Meshack Appikatla.

    A Text Symbol in Script or Smartform can take lenght of Maximum 80 characters. Any thing more than that will be truncated even if the window is long enoguh to hold more than 80 characters. Si your character formated need to be have the PROTECTED option checked.
    At Topic:
    Try increasing the window size in lenght or width, If that is not possible pratically, you can try by decreasing the font size.

  • Sap Script - Printing text

    Hi Experts,
    In a classical ABAP report we make use of
    write:/20 'Text'.
    to print text from the 20th column. Can we do something similar in a SAP Script Page Window. I have a box and lines drawn. Now I want the text to start exactly after the vertical line(column). Is there a way to do in SAP Script.
    Regards
    Abdullah.

    Hi
    You can do one thing. you can straight away write the field
    &BSEG-SGTXT&
    in two lines straight with offset.
    in the first line T1 &BSEG-SGTXT+0(25)&
    In second line T1 &BSEG-SGTXT+25(25)&
    first write like this and see, is it printing or not.
    Reward all helpfull answers
    Regards
    Pavan

  • Sap scripts print modes

    What are the print modes available in the sap scripts?

    Hi
    Parent Topic: SAPScript
    HOWTO:Sap script
    Edit this entry - Discuss - Rename - Watch - History - 
    Major contributors: gopang, cmurphy262 | All Contributors
    Your votes have been tallied! See which wiki entry took top honors and find out who is this year's Wiki Ironman.  View the winners. 
    White Papers
    Do You Need a Fax Server? A Special Guide on Fax Servers and SAP Electronic Document Delivery
    Achieving Real-Time Supply Chain Integration
    E-Invoicing for Business Process Efficiency with SAP(R) Systems
    Jobs
    SAP Consultants (Any City) - SD, MM, PP, FI/CO, CS, ABAP (Dice) 
    SAP ABAP LEAD (Dice) 
    SAP ABAP Workflow Developer -Contract (Dice) 
    Community Content
    3 days until GO-LIVE!!! (Blogs)
    RE: RE: RE: RE: RE: Lost connection when using tcode FS00 (Groups)
    SAP SCRIPT
    Table of contents Show TOCHide TOC 
    1. 1 Concepts
    1.1. 1.1 Modifying SAP Forms
    1.2. 1.2 Forms: Concepts
    1.3. 1.3 Client and Language Versioning: Concepts
    2. 2 Componentes
    2.1. 2.1 Header Data
    2.2. 2.2 Paragraph Formats and Attributes
    2.2.1. 2.2.1 Standard Paragraph Attributes
    2.2.2. 2.2.2 Font Attributes for Paragraphs
    2.2.3. 2.2.3 Tabs in Paragraph Formats
    2.2.4. 2.2.4 Paragraph and Heading Numbering
    2.3. 2.3 Character Formats and Attributes
    2.3.1. 2.3.1 Standard Attributes for Character Formats
    2.3.2. 2.3.2 Font Attributes for Character Formats
    2.4. 2.4 Windows
    2.4.1. 2.4.1 Default Paragraph
    2.5. 2.5 Pages
    2.5.1. 2.5.1 Defining Follow-On Pages in Duplex Print Modes
    2.5.2. 2.5.2 Testing Tray Selection and Print Mode Selection
    2.6. 2.6 Page Windows
    2.7. 2.7 Text Elements
    2.7.1. 2.7.1 Default Text Element
    2.8. 2.8 Main Window
    3. 3 Técnicas
    3.1. 3.1 Displaying Versions of Forms
    3.2. 3.2 Including Graphics
    3.2.1. 3.2.1 Using Boxes, Lines, and Shading
    3.2.2. 3.2.2 Supported Printers
    3.2.3. 3.2.3 Boxes, Lines, Shading: BOX, POSITION, SIZE
    3.2.3.1. 3.2.3.1 BOX Command
    3.2.3.2. 3.2.3.2 POSITION Command
    3.2.3.3. 3.2.3.3 SIZE Command
    3.2.4. 3.2.4 Pre-Setting BOX Position Arguments
    3.2.5. 3.2.5 Using the Commands in Texts and Forms
    3.2.6. 3.2.6 Tips and Guidelines
    4. 4 Design Tools
    4.1. 4.1 Form Components
    4.2. 4.2 Processing in Overview
    4.2.1. 4.2.1 Defining Header Data
    4.2.1.1. 4.2.1.1 Completing the Header Data After Defining the Attributes
    4.2.1.2. 4.2.1.2 Passing Data to an External Program
    4.2.2. 4.2.2 Defining Paragraph Formats
    4.2.3. 4.2.3 Defining Character Formats
    4.2.4. 4.2.4 Defining Pages
    4.2.5. 4.2.5 Defining Windows
    4.2.6. 4.2.6 Using Text Elements in Page Windows
    4.2.7. 4.2.7 Defining Page Windows
    4.2.7.1. 4.2.7.1 Filling Page Windows with Text
    4.2.8. 4.2.8 Using Text Elements in Page Windows
    4.2.9. 4.2.9 Defining Main Windows in Page Windows
    4.3. 4.3 Test-Printing a Form
    5. 5 Releasing Forms
    6. 6 SAPscript Control Commands
    6.1. 6.1 Syntax of Control Commands
    6.2. 6.2 Explicit Page Break: NEW-PAGE
    6.3. 6.3 Preventing Page Breaks: PROTECT
    6.4. 6.4 Next Main Window: NEW-WINDOW
    6.5. 6.5 Assigning a Value to a Text Symbol: DEFINE
    6.6. 6.6 Formatting Date Fields: SET DATE MASK
    6.7. 6.7 Formatting Time Fields: SET TIME MASK
    6.8. 6.8 Country-Dependent Formatting: SET COUNTRY
    6.9. 6.9 Position of the Leading Sign: SET SIGN
    6.10. 6.10 Initializing Numbered Paragraphs: RESET
    6.11. 6.11 Including Other Texts: INCLUDE
    6.12. 6.12 Changing the Style: STYLE
    6.13. 6.13 Formatting Addresses: ADDRESS
    6.13.1. 6.13.1 Parameters
    6.14. 6.14 Setting a Footer Text in the Main Window: BOTTOM
    6.15. 6.15 Conditional Text: IF
    6.16. 6.16 Finding a Match: CASE
    6.17. 6.17 Calling ABAP Subroutines: PERFORM
    6.18. 6.18 Inserting Print Controls: PRINT-CONTROL
    6.19. 6.19 Boxes, Lines, Shading: BOX, POSITION, SIZE
    6.20. 6.20 Hexadecimal Data: HEX, ENDHEX
    6.21. 6.21 Summing a Program Symbol: SUMMING
    6.21.1. 6.21.1 Summing and Carrying Forward is Incorrect
    7. 7 SAPscript Symbols
    7.1. 7.1 Syntax of Symbols
    7.2. 7.2 System Symbols
    7.2.1. 7.2.1 Current Date
    7.2.2. 7.2.2 Current Day Number
    7.2.3. 7.2.3 Current Month Number
    7.2.4. 7.2.4 Current Year Number
    7.2.5. 7.2.5 Current Day Name (Long Form)
    7.2.6. 7.2.6 Current Month Name (Long Form)
    7.2.7. 7.2.7 Current Time
    7.2.8. 7.2.8 Hours Component of Current Time
    7.2.9. 7.2.9 Minutes Component of Current Time
    7.2.10. 7.2.10 Seconds Component of Current Time
    7.2.11. 7.2.11 Current Page Number
    7.2.12. 7.2.12 Page Number of the Next Page
    7.2.13. 7.2.13 Selected Device Type
    7.2.14. 7.2.14 Spaces
    7.2.15. 7.2.15 Underline
    7.2.16. 7.2.16 Vertical Line
    7.3. 7.3 Program Symbols
    7.3.1. 7.3.1 SYST: System Fields in the ABAP Programming Environment
    7.3.2. 7.3.2 USR03: User Address Data
    7.3.3. 7.3.3 SAPSCRIPT: General SAPscript Fields
    7.4. 7.4 Standard Symbols
    7.5. 7.5 Text Symbols
    7.6. 7.6 Formatting Options
    7.6.1. 7.6.1 Offset
    7.6.2. 7.6.2 Output Length
    7.6.3. 7.6.3 Omitting the Leading Sign
    7.6.4. 7.6.4 Leading Sign to the Left
    7.6.5. 7.6.5 Leading Sign to the Right
    7.6.6. 7.6.6 Omitting Leading Zeros
    7.6.7. 7.6.7 Space Compression
    7.6.8. 7.6.8 Number of Decimal Places
    7.6.9. 7.6.9 Omitting the Separator for ‘Thousands’
    7.6.10. 7.6.10 Specifying an Exponent for Floating Point Numbers
    7.6.11. 7.6.11 Right-Justified Output
    7.6.12. 7.6.12 Fill Characters
    7.6.13. 7.6.13 Suppressing Output of Initial Values
    7.6.14. 7.6.14 Ignoring Conversion Routines
    7.6.15. 7.6.15 Changing the Value of a Counter
    7.6.16. 7.6.16 Preceding and Subsequent Texts (Pre-Text / Post-Text)
    7.7. 7.7 Country-Dependent Formatting
    7.7.1. 7.7.1 Date Mask
    7.7.2. 7.7.2 Time Mask
    7.8. 7.8 Formatting Conventions
    7.8.1. 7.8.1 Primary Formatting of System Symbols
    7.8.2. 7.8.2 Primary Formatting of Standard Symbols
    7.8.3. 7.8.3 Primary Formatting of Program Symbols
    7.8.4. 7.8.4 Primary Formatting of Text Symbols
    7.8.5. 7.8.5 End Formatting
    1 Concepts Edit section
    1.1 Modifying SAP Forms Edit section
    If you want to modify SAP forms, set up your development environment as follows:
    1. Make sure that no SAP-standard forms are stored as client-specific copies in your development client. Such forms should be held only in client 000, the SAP development and installation client. If you access an SAP-standard form from another client, then the central copy in client 000 is used.
    If you need to remove SAP-standard objects from your development client, see Notes 10388 and 3355 in the SAP Online Service System (OSS). These notes explain the procedure for saving modified forms and then deleting all forms.
    2. To modify SAP standard forms,
    Copy the forms you need from client 000 to your development client.
    Rename the forms using a name from the customer name reserve (names starting with Y or Z).
    Copy the forms to one of your own Y or Z development classes.
    Renaming the SAP standard object makes it possible to manage and transport your changes with the SAP workbench organizer. The organizer is not activated for SAP-standard objects that are modified in clients other than 000.
    3. To put your modifications into effect, you must also modify the ABAP print program used to print documents that use this form. You should rename such print programs and store them in your own Y or Z development classes.
    You can use the SAP Customizing System to replace the SAP print program with your modified print program in the affected applications
    1.2 Forms: Concepts Edit section
    Forms are used to control the page layout and also the text formatting in your documents. Before formatting a document for output to the screen or to a printer, you must assign a form to it. If you do not specify a form for a document, then the SYSTEM form is assigned to the document by default.
    Application-specific forms are used in SAP applications to specify the page layout for such special documents as invoice or checks. These forms specify the structure of the information on the page(s) of such a document. They define, for example, the address header, item lines, the footer, and so on. There are two ways to format texts with forms:
    In the standard SAPscript text processing (Tools &#61614; Word processing &#61614; Standard text), you can select a form for a document. You can then type text into the main window of the form and output the document in the format defined in the form.
    For example, you can select a form for a letter. You can then type the body text of the letter in the main window. When you print the letter, the default text elements in the other windows of the form (heading, footer, and so on) are printed with the body text.
    A document can be generated by a print program in one of the SAP applications. The print program uses a form to generate the document. Most correspondence and document generation in the SAP System are handled by way of print programs.
    A print program selects the text elements that are to be printed in the windows of a form. It may also collect information from the user or ask the user to input text directly, as in some correspondence functions. The print program may also provide data for variables defined in the form.
    Finally, the print program uses the form to format the document for display or printing.
    1.3 Client and Language Versioning: Concepts Edit section
    Forms and styles are client-specific. That is, a form or style other than the SAP standard in client 000 is available only in the client in which it was created.
    Forms and styles are also language-specific. That is, the definitions and texts in a form or style are defined for a particular language. Forms and styles can be translated using the standard SAP translation tools.
    Client 000 Defaulting: SAPscript accords forms and styles in client 000 a special status.
    If a form or style that is used in a document is not available in the client in which the document is being printed, then SAPscript checks for the form or style in client 000. If it is found there, then the client 000 version is used to print the document.
    SAP standard forms and styles are always held in client 000. You can take advantage of the client 000 defaulting as well by storing your Yxxx and Zxxx forms and styles there. That way, if a local version of a form or style is not present in a client, the client 000 version is used instead.
    Language rules: SAPscript uses the following rules to manage versions of forms and styles in different languages:
    The language in which a form or style is created is its "original language." You can translate a form or style into other languages using SAP’s translation tools.
    If a form or style is needed only in its original language and need not be translated, then you can indicate this in the language attributes in the header data. The form or style then does not appear in work lists in the translation tools.
    In versions other than the original language version, changes to a form or style are limited only to translation of texts. No changes to definitions and attributes are permitted.
    2 Componentes Edit section
    2.1 Header Data Edit section
    You can find header data in both form and style maintenance. In style maintenance, it is used primarily to present important information – information designed to make it easier for the end user to select a style. The header data in form maintenance, on the other hand, is used for information and control purposes. For this reason, the header data of a form will be described in more detail.
    Below, the header data is described as it appears in the alphanumeric Form Painter.
    Like the header data of a style, the header data of a form comprises two parts: the data set by the system and the data you are expected to enter. The latter is dealt with separately.
    Device-independent entries.
    Description
    A short explanatory description of the form (also applies to the style), designed to make selection easier for the end user.
    Form class
    You can assign a form to a class to help you organize and search for forms. The default set of classes is the set of program classes in your system.
    Start page
    Tells the print program which page format in a form to use first for printing.
    Default paragraph
    Paragraph set to * in standard text maintenance.
    Tab stop
    A grid set at specified intervals in all windows defined in the form. However, you should note that the tab stops are only valid in paragraphs where you have not defined your own tabs.
    Language, Original language, Translation applic
    Use these fields to record the master language and language of the current version of a form. Marking Translation applic makes the form accessible for translation from the SAP System’s translation tools (transaction SE63).
    Device-dependent entries.
    You can only enter values here that are supported in the R/3 printer definition. If you make other entries, this leads to errors in the check routine.
    Page format
    Determined from the spool administration table with transaction SPAD. Make sure there is a printer assignment – there must be an additional spool format for the printer with the same page format.
    Orientation
    Depends on the page format selected. This can also be determined from the spool administration table. Please note that the formats landscape and portrait are not supported by all printers.
    Lines per inch (LPI)
    Basis for converting the unit of measurement LN in style and form maintenance. The value 6.00 is set by the system, as this value is supported by all printers.
    Characters per inch (CPI)
    Basis for converting the unit of measurement CH in style and form maintenance. The value 10.00 is set by the system, as this value is supported by all printers.
    Font attributes
    With these fields, you can set the default font for a form. The default font applies if other objects do not specify a font. SAPscript suggests a default font, which you can change.
    2.2 Paragraph Formats and Attributes Edit section
    In SAPscript, paragraphs are formatted using formats and their corresponding attributes. Text processing is simplified by the use of different paragraph attribute groups:
    Standard
    Font
    Tabs
    Outline
    There are naming conventions for paragraph tags:
    The paragraph tag can have one or two characters.
    The first character in the paragraph tag must be a letter, the second a letter, number, or blank; special characters are not valid.
    The paragraph format must be identified in the Description field.
    2.2.1 Standard Paragraph Attributes Edit section
    In the Standard attribute group, you find the general attributes that can be defined in paragraph formats:
    Description
    Precise explanation of your paragraph tag, so that the user can immediately identify it.
    Left or right margin
    Amount of space between the paragraph and the left or right border of the form window.
    Indent first line
    Indent of the first line of a paragraph. If the value is positive, it is indented to the right, if it is negative, it is indented to the left.
    If you specify a negative value, then you must place the minus sign after the number: 1- .
    Space before and space after
    Space before and space after control the amount of space between paragraphs. The actual space between paragraphs results from the space after the preceding paragraph and the space before the following paragraph.
    Alignment
    Alignment of a paragraph.
    Left-aligned
    LEFT
    Right-aligned RIGHT
    Centered CENTER
    Justified BLOCK
    Line spacing
    Spacing between the lines. The default value is 1 line; the LPI value (lines per inch) in the header data is used to calculate the line spacing.
    No blank lines
    Suppression of blank lines. You can control whether the blank lines of a paragraph should be suppressed in the printout or not:
    No entry
    blank lines not suppressed
    X blank lines suppressed
    Page protection
    Cohesion of a paragraph. It is possible to determine whether or not a paragraph can be divided by a page break.
    No entry
    no page protection (default)
    X all lines of the paragraph are on one page
    Next paragraph same page
    Cohesion of two adjacent paragraphs. Here you can define whether the subsequent paragraph should begin on the same page (that is, at least the first line of the subsequent paragraph must be on the same page).
    No entry
    subsequent paragraph is output on the same page or the next page, depending on the amount of space (default)
    X subsequent paragraph begins on the same page
    2.2.2 Font Attributes for Paragraphs Edit section
    You can specify font attributes for paragraph formats. They control the font used in the text. You can specify these attributes both for the default font in the header and for particular paragraph formats:
    Font family
    Enter a font supported in the SAPscript font maintenance.
    Font size
    Enter the size of a character font. It is measured in 1/10 point.
    Bold/Italic
    Specify whether to use bold-face printing or italics.
    Underlined
    Mark this attribute to underline entire blocks of text.
    When defining a paragraph format, use More to specify these underline attributes:
    Spacing between the base line and the underline
    Thickness
    Intensity
    Intensity is expressed in percent: 0 % is a black underline; 100 % is no underline.
    If you defined default underlining in the header, then the fields for underline attributes are already displayed on the screen.
    The following selection criteria apply to the font attributes bold, italics, and underlined:
    Off attribute is not set
    Retain inherited
    On attribute is set
    The combination of font family, font size, bold type attribute and italics attribute is referred to as a system font or SAP font. To use the SAPscript font maintenance, choose Tools &#61614; Word processing &#61614; Font.
    2.2.3 Tabs in Paragraph Formats Edit section
    You can define as many tab positions as you require for each paragraph format. The text can be aligned in different ways:
    Left-aligned with LEFT
    Right-aligned with RIGHT
    Centered with CENTER
    At the sign with SIGN
    At the comma or decimal point with DECIMAL
    You can control the tab feed in a paragraph with tab positions. The tab stops you define in the paragraph format replace the tab spacing you defined in the header data of the form. However, this depends on the extent to which you have defined tab stops in the paragraph format. If there are fewer tabs in the paragraph formats than in the header data, the tab stops of the header data are used for the rest of the line. The tab stops are represented as, , in the text editor.
    You can use different units of measurement to define a tab position:
    CH Characters
    CM Centimeters
    MM Millimeters
    PT Points
    TW Twips (1/20 point)
    The unit of measurement CH is converted to an absolute unit of measurement using the CPI value (characters per inch) from the header data of the form.
    2.2.4 Paragraph and Heading Numbering Edit section
    The paragraph numbering and marking attributes are used to structure texts into chapters, subchapters, and sections. Numbering is carried out automatically by SAPscript.
    You can create an outline with the entry options available:
    Outline
    Enter the name of the highest-level paragraph in an outline hierarchy here. The outline hierarchy is created by assigning this paragraph to all outline paragraphs.
    Outline level
    Enter the level in the outline hierarchy. The outline levels of the paragraphs are numbered upwards from 1; the highest outline level therefore has the outline number 1.
    Number margin
    Specify the space between numbering and window border. Note that your numbering may extend into the text area of the paragraph if the difference between the left margin and the number margin is not great enough to hold the numbering characters.
    Left/right delimiter
    Specify the character that precedes or follows the numbering.
    Number chaining
    Specify whether you want the paragraph numbering of the paragraph to be preceded by the numbering of all higher paragraphs in the hierarchy.
    Example for number chaining
    with   without
    3.     3.
    3.1     1.
    3.2     2.
    3.2.1     1.
    Character string
    Specify the numbering format. The numbering can be assigned a different font or character format to the rest of the paragraph.
    Numbering type
    ARABIC
    Arabic numerals: 1, 2, 3.
    CHAR Fixed character: letter or numeral, entered in the field
    LETTER Letters: A-Z
    ROMAN Roman numerals: I, II, III, IV
    Depending upon the numbering type that you select, the following attributes may also apply:
    Fixed character
    Define the fixed character to be used for numbering. You should only make an entry in the field Fixed character if you have specified CHAR as the numbering type. Fixed characters include + - and o .
    Output length
    Enter the number of characters for Arabic numerals.
    Upper case
    Specify for letters or Roman numerals.
    2.3 Character Formats and Attributes Edit section
    Character formats, as opposed to paragraph attributes, allow you to format entire blocks of text within a paragraph.
    Character attribute groups can be:
    Standard
    Font
    When you define character formats, observe the following naming conventions:
    The character format can have one or two characters.
    The first character must be a letter, the second a letter, number, or blank; special characters are not valid.
    Enter a simple explanation in the field Description. It is intended to help the user make a selection.
    2.3.1 Standard Attributes for Character Formats Edit section
    Marker
    Links a search key to the selected character string when the end user uses this character format. Examples include glossary, hypertext, and data element links. Here, selected character strings are assigned the appropriate key.
    Bar code
    Bar code that is required for certain variables and is known to the printer, for example EAN8. The character string is printed as a bar code if the character string concerned is selected.
    Bar code names, such as EAN8, refer to system bar codes. These are defined in the SAPscript font maintenance (Tools &#61614; Word processing &#61614; Font).
    Protected
    The character string is not split by a line break, but printed together on the next line.
    Hidden
    The character string is not printed. The text is only visible in the text editor.
    Superscript/subscript
    The character string is printed half a line higher or lower.
    The following options are available for defining these attribute types:
    Off
    Attribute is not set
    Retain Attribute is inherited
    On Attribute is set
    2.3.2 Font Attributes for Character Formats Edit section
    Font attributes can be specified for character formats as well as for paragraph formats. You have the same options as for defining font attributes for paragraph formats.
    2.4 Windows Edit section
    Windows are defined in form maintenance. They represent areas that are positioned on pages – as page windows – and in which at a later time text is printed. You must define at least one window for each form. Otherwise, SAPscript cannot format the text.
    You can assign window names and window types. However, note that you can define only one main window per form.
    Use one of these window types:
    MAIN
    Main window in which continuous text is printed. This is the window used by dialog users of a print program and form. For example, the body text of a letter would be entered in MAIN.
    The text in the main window can extend over several pages. If the text fills one page, output continues in the window of the next and subsequent pages, as long as MAIN has been defined for these pages.
    VAR
    Window with variable contents. The text can vary on each page in which the window is positioned. Variable windows are formatted for each page.
    To every window you can assign text, which is printed in the corresponding window when the form is formatted. To assign text, use text elements, which are stored with the form.
    To create and maintain text elements with the SAPscript Editor, choose Text elements. Should the text selected for the window exceed the window size, then the text is cut off.
    CONST
    Window with constant contents that is formatted only once.
    Currently, CONST windows are processed in the same way as VAR windows. You should only use windows of type VAR.
    2.4.1 Default Paragraph Edit section
    For a particular window, you can override the default paragraph format that is set in the form header. Enter the default format that should apply in the window in the Default paragraph field in the window definition screen.
    2.5 Pages Edit section
    You must define at least one page for every form. And you must designate a "first" page in the form header. Otherwise text formatting is not possible. In addition, you should inform the system which page is to be used after reaching the end of the first page. If you do not specify a next page, the output of your text ends at the end of the current page.
    To define a page, give it a name and specify attributes for it:
    Name of the next page
    Page counter mode
    INC Increases the counter by 1
    HOLD Counter remains unchanged
    START Sets the counter to 1
    You can display the contents of the page counter with the system symbol&PAGE&.
    Numbering type of the page counter
    ARABIC Arabic numerals
    LETTER Letters
    ROMAN Roman numerals
    Although CHAR is displayed as an entry option for the numbering type of the page counter, internally CHAR is converted to ARABIC.
    Output length for page numbering with numerals
    Upper or lower case for numbering with Roman numerals or letters
    Resource name
    With Resource name, you specify that the paper for this page should be taken from a particular paper tray at the printer.
    In Resource name, enter the print control that has been defined for switching to the paper tray you want to use. In printer types pre-defined by SAP, these print controls are generally as follows:
    TRY01 Select first paper tray
    TRY02 Select second paper tray (if available at the printer)
    TRY03 Select third paper tray (if available at the printer)
    TRYEN Print envelopes (if available at the printer)
    TRYMN Switch the printer to manual paper feed (if available at the printer). The printer pauses until you feed a sheet of paper into it.
    TRYME Switch the printer to manual envelope feed (if available at the printer). The printer pauses until you feed an envelope into it.
    You can use all tray selection print controls except TRY03 with suitably equipped printers that are defined with the following SAP device types: HPLJSTND, HPLJ_II, HPLJIIID, HPLJ4, LX4039, and SNI20XX8.
    You can use TRY01, TRY02, TRY03, and TRYMN on suitably equipped printers that are defined with these device types: KYOF1000, KYOF1200, KYOFS1500.
    See the spool system (transaction SPAD) to check on how your printers are defined.
    Print mode
    With Print mode, you can specify single- or double-sided printing for a page. You can choose from the following values:
    ' ' Currently active printing mode continues unchanged.
    S The page is printed in simplex mode. That is, the printer should print on only one side of the paper. If another mode was previously active, then the printer is switched to simplex mode with the start of the page.
    D The page is printed on the first side of a sheet in duplex mode. If another mode was previously active, then the printer is switched to duplex mode with the start of the pageand continues in this mode.
    T The page is printed on the first side of a sheet in tumble duplex mode. That is, the printer prints on both sides. The page on the second side is always inverted, so that the footer of the second page is printed opposite the header of the first page.
    If another mode was previously active, then the printer is switched to tumble duplex mode with the start of the page and continues printing in this mode.
    Print modes are currently supported for printers that use the PCL-5 language. These are printers that are defined with the following SAP device types: HPLJ_II, HPLJIIID, HPLJ4, LX4039, SNI20XX8.
    See the spool system (transaction SPAD) to check on how your printers are defined.
    The print controls for these functions are SPMSI (begin simplex printing); SPMDU (begin duplex printing); SPMTU (begin tumble duplex printing); SPMFS (print on first side of sheet in duplex or tumble duplex mode); and SPMBS (print on second side of sheet in duplex or tumble duplex mode).
    2.5.1 Defining Follow-On Pages in Duplex Print Modes Edit section
    You switch to duplex or tumble duplex mode with a form page for which one of these modes is specified. To continue printing in the current mode, for follow-on pages you must define another page in which the Print mode field is empty. Otherwise, the following pages after the mode switch will continue to be printed only on the front sides of new sheets of paper.
    The reason: When SAPscript sends a page with Print mode D or T to the printer, it not only sets the print mode accordingly. To ensure that the first page in the new mode is correctly output, SAPscript also instructs the printer to output the page on the front side of a sheet. If SAPscript sends a sequence of D or T pages to the printer, the output is printed only on the front side of each sheet.
    You define a first page named FIRST for a form to be printed in duplex mode. You therefore set the Print mode in FIRST to D.
    To make the duplex printing work correctly, you must define a second page FOLLOWER in which Print mode is left empty. In the form definition, you specify FOLLOWER as the follow-on page for FIRST and for itself as well.
    Your text is then printed in duplex mode. FIRST switches the printer to duplex mode and forces printing of the first page on the front side of a new sheet. FOLLOWER accepts the duplex mode and sends no further mode print controls to the printer. The printer therefore alternately prints FOLLOWER pages on the fronts and backs of sheets.
    2.5.2 Testing Tray Selection and Print Mode Selection Edit section
    SAP provides predefined SAPscript documents with which you can test whether tray selection and print mode selection are working properly on your printers.
    For tray selection, print the SAPscript document SAPSCRIPT-TRAYTEST, ID ST, Language D or E.
    For print mode selection, print the SAPscript document SAPSCRIPT-PRINTMODETEST, ID ST, Language D or E.
    2.6 Page Windows Edit section
    When you define page windows, the window names are linked to page names. You must specify the position and size of the window on the assigned page.
    Define the position of a window by specifying the left margin and upper margin and the size of a window by specifying its width and height.
    Left margin
    Space between the window and left margin of the page
    Upper margin Space between the window and upper margin of the page
    Window width Width of the window depending on the page format selected
    Window height Height of the window depending on the page format selected
    Note that the width of the main window must be the same on all pages. All other window types can have different sizes and positions on different pages.
    To print multiple columns, define several main windows on a page. As text entry is continuous, once the first main window has been filled, output continues in the second main window.
    Rewards if helpfull
    Regards
    Pavan

  • Prob with putting text after the Schedule line item in PO Sap script

    Hi Guys,
    I need to include a Text afetr the first schedule line item and that shouldn't print after next onwards, can anyone help me out.
    Thanks,
    Ramesh

    two things
    in this
    activate debugger and check whether the field
    &EKET-J_3ASIZE& is eq ' ' or not
    only then it will come in to else condition
    if its coming into else case check whether &T166P-TXNAM& is getting populated or not
    if it doesnt u need to go to item_text
    define a variable and move the value of &T166P-TXNAM&
    define &TEXT& = &T166P-TXNAM&
    and then
    in item_schedule
    iNCLUDE <b>&TEXT &</b> OBJECT &T166P-TDOBJECT& ID &T166P-TDID& LANGUAGE &EKKO-SPRAS& PARAGRAPH IX
    i think this will resolve the issue.
    Harish
    reward if its useful

  • How to print line item 2times in two different main window in Sap Script

    Hi,
    I am designing check printing form using Sap script. I need to print line items 2times in different 2main window.can yu pls explain  how print like this.
    JK

    i cud not get ur query..pls elaborate

  • Problem passing texts into sap-script

    Dear Experts,
    I have a requirement, where I have to pass some text-lines from my selection-screen of the driver-program to the sap-script,i.e. whatever I write in those text fields that should be displayed(printed) on the specified place of my script. Another specification is  that,
    those lines will get printed only if the checkbox on my selection-screen is checked.
    What should be the procedure,please help me.

    The text lines on the selection screen will be in a variable. Pass the variable to the SAPScript. I don't see the problem.
    Rob

  • Sap Script printing issue

    Hi Gurus,
    I am working on a SAP script... when I am printing the SAP script the last few lines of my text is missing... I got to know that there might be a problem in the page setting... i.e. the page may be set as a A4 and i am printing on letter... so can you please tell me how can I check what the page setting that my sap script is using.
    Thanks,
    Rajaeev Gupta

    Hi,
    Issue of 'part of the Text missing' is happening during Print Preview or when taking a print out?
    I guess, the problem is due to height of the window, the height of the window where u printing this text is not able to accomodate the entire text. just increase the height of the window & try. 
    To know the page format that ur script is using, just follow the below steps:
    Txn SE71--> give the Script form name > click on change/Display button> click on Header button (red hat symbol) in app tool bar or press F5 button --> now click on Basic Settings button. Here u see the Page Format in 'Set up Page' block...
    Hope it helps!!
    Rgds,
    Pavan

  • SAP Script: Printing the signature on main window at the end

    Hi,
    I am working on a SAP Script (Benefits enrollment form HR_BEN_ENRO).  I copied the HR_BEN_ENRO into ZHR_BEN_ENRO and making the necessary changes without modifying the driver program.
    The problem I am facing is as follows:
    In the main window there are so many Text elements.  At the end of the main window, after the last text element, I have put some text using Include statement.  The last text element is getting triggered for some employees and hence the text underneeth that is printing, but for some employees the last element is not triggering and hence nothing is printing underneeth that.
    Is there any solution to print the this text at the end of main window after printing all the remaining information.
    I also tried using BOTTOM & ENDBOTTOM. But in this case I don't know how to check that I am in last page of the main window.  I tried the following way:
    /: BOTTOM
    /: IF &PAGE& = SAPSCRIPT-FORMPAGES&
    SIGNATURE:__________   Date:__________
    /: ENDIF
    /: ENDBOTTOM
    In this case the value I am getting for &SAPSCRIPT-FORMPAGES& is 0 (zero).
    Any solution..please.
    Appreciate.

    How to link the ZHR_BEN_ENROL instead of HR_BEN_ENRO?
    I mean when I execute the TCODE: HRBEN0001 and select particular employee and click on Print form under Offer Selection area. Then standard program calls HR_BEN_ENRO. How to replace it with Zform?
    Thanks in advance.
    Regards,
    Krishna

Maybe you are looking for

  • HP Utility and Scanning issues with Officejet Pro 6830

    I purchased a 6830 several weeks ago and have been using it for general wireless printing from my Mac for serveral weeks with no problems.   Today I wanted to try scanning, and for the first time brought up the "HP Utility" and noticed that it connec

  • Optimal iTunes network configuration

    Please advise if there is a better place to post this. I am trying to optimize my iTunes set up. We have three computers, all with iTunes, and two iPhones. I sync my iphone with my laptop (lenovo/windows 7) and my wife syncs er iPhone with her laptop

  • Creating html sig with embedded gif

    Hi all, I'm trying to create an html sig for mail, with an embedded gif but am having no success. I do the whole save as archive from safari and give the name of existing temp sig created from mail; and it appears in my mail app correctly except for

  • When is the new fix for ios 8 coming after 8.0.1 failed?

    Wi-Fi is slow, my battery is draining very fast, and my photos on the Cloud are not on my device anymore. Ive also experienced some freezing and non responses to touch at various times. When will you resend the fix after the fix?

  • Pavilion dv6 headphones stop working when certain programs launched

    My pavilion dv6 (product number: A5F76AV; OS: Windows 7 Ultimate 64-bit) is brand new, just arrived yesterday. On startup, the headphones work fine when watching videos online and for any other system audio, but when I launch a game (through steam) I