Blocks in SAP Script

Hi Experts,
Please help me out with this....I need to have boxes for all the records..Like if I have 10 records then i need to have the boxes which have been printed fr the first record should get printed for the other 10 records...
But this is nt happening...I am getting all the records on the basis of the range I enter in the selection criteria but not the boxes which i am getting only for the first record.
Also I need to have chechboxes in the headr of the report which will be checked by the user. Please let me know how to create checkboxes in the SAP Script.

hi!
create a variable window and write this code there
/: POSITION XORIGIN '2' CM YORIGIN '10' CM
/: SIZE WIDTH '18.05' CM HEIGHT '18' CM
/: BOX FRAME 10 TW
/: POSITION XORIGIN '2.05' CM YORIGIN '10.05' CM
/: BOX WIDTH '18' CM HEIGHT '1' CM INTENSITY 15
/: POSITION XORIGIN '3.5' CM YORIGIN '10' CM
/: BOX FRAME 10 TW  WIDTH '0' TW HEIGHT '18' CM
/: POSITION XORIGIN '9.2' CM YORIGIN '10' CM
/: BOX FRAME  10 TW  WIDTH '0' TW HEIGHT '18' CM
/: POSITION XORIGIN '11.5' CM YORIGIN '10' CM
/: BOX FRAME  10 TW  WIDTH '0' TW HEIGHT '18' CM
then create a main window with same height and width as that of the varaible window (overlapping the variable window on to it).
now on looping in the main table and displaying the data 10 records in the one page and then 10 records on the other page the boxes will come it self....
here the main window dimensions are
MAIN    00 Main Window                    2,00 CM  10,00 CM  18,00 CM  18,00 CM
[then with the help of data element call the box
/: BOX WIDTH '18' CM HEIGHT '1' CM FRAME 10 TW
in loop where write_form is called....]
u will get the box with the data printed in the form......
keeping same for the variable window....
and try it....
this will be done....
Edited by: Richa Tripathi on Feb 18, 2009 8:11 AM

Similar Messages

  • Sap script block positioning.

    hi,
    i have 2 pages in my sap script.
    both the pages have the same "main" window.
    i have given box command in the begining of this main window:
    /:BOX XPOS '.5' CM YPOS '0' CM WIDTH '25' CM HEIGHT '1'  CM FRAME 0 TW  INTENSITY 15
    /:BOX XPOS '.5' CM YPOS '0' CM WIDTH '25' CM HEIGHT 0 TW FRAME 10 TW
    /:BOX XPOS '.5' CM YPOS '1' CM WIDTH '25' CM HEIGHT 0 TW FRAME 10 TW
    The problem i am facing is :the box is coming at the right place for 1st page, but at the top of the page for the next window. i think it must be taking y coord. from the top of the page for the next window.
    Please give a suitable solution for this,
    thanks in advance,
    Ravindra

    hii Ravindra,
    try this out
    /: POSITION XORIGIN '11.21' YORIGIN '5.31' MM
    /: SIZE HEIGHT '2' MM WIDTH '76' MM
    /: BOX  FRAME 10 TW INTENSITY 10
    This can be usefull if you gave several boxes that share the same parameters.
    If you want to set the position realtively to the window use POSITION WINDOW
    to set the position to the top/left start of the window. Then use POSITION
    to set the current position relatively to the start of the Window.
    Note that you uses "+" or "-" in the ORIGIN position to the set the position relatively.
    /: POSITION WINDOW
    /: POSITION XORIGIN '5' MM  YORIGIN '10' MM
    the position is now 5 MM from the left and 10 MM from the top of the window
    NOTE: After using the position command you can move the current position
    realtively to the last used position
    /: POSITION XORIGIN '10' MM  YORIGIN '20' MM
    Now the position will be X = 15 and Y = 30
    Drawing a line. You can draw a line by setting the Height or Weidth to 0
    and add a frane. E.g. a horizontal line:
    /: SIZE HEIGHT '0' MM WIDTH '200' MM
    /: BOX FRAME 10 TW XPOS '11.21' MM YPOS '14.81' MM INTENSITY 100
    i guess this will help
    revert  back for more help
    Regards
    Naresh

  • Problem in SAP-Script Conditional Block

    Hi All,
    I am creating one report form using SAP Script, which uses standard driver program. There is a control statement like,
    { Consider W=1, X=0 , Y=0 & Z=0 }
    /: IF ((X==0 AND Y==0) OR (Z==0 OR W==0)  OR ...) { lot of OR & AND stament used in this conditional statment }
    /: ELSE
    /: ENDIF
    Here is a mistery, it executes both if and else statement. Please give me some idea on this, and why such a weird output is displaying?
    <<removed by moderator>>
    Edited by: kishan P on Sep 13, 2010 4:17 PM

    Hi..
    The syntax of the command could be incorrect. Check for full stops, variables etc.
    http://help.sap.com/saphelp_40b/helpdata/en/d1/80325f454211d189710000e8322d00/content.htm
    Please check the above link's last paragraph which says :
    "If a syntax error occurs in the interpretation of this command, then the command is not executed. This may have an unexpected effect on the subsequent text output. For example, if the IF statement is incorrect, then all following ELSEIF and ELSE commands will be ignored, since the opening IF command is u2018missingu2019. This will cause all the text lines attached to the ELSEIF and ELSE commands to be printed."
    Regards,
    Karthik

  • Regarding Adding multiple SAP Scripts in one Transaction

    Hi All,
    I have a requirement where i will have to develop one custom transaction which will have multiple SAP Script Forms to it.
    The scenario is as below:
    First i will have to create a Program with Selection-Screen with 10 Radio buttons in one Block - Here Each Radio Button indicated Diffrent FORM[SAP SCRIPT].
    Down to it i will create another Block with some selection-screen fields. Like Order Type, Order No, Customer PO number, SOLD TO, BILL TO, SHIP TO etc.
    And based on Radio button selected allowed order types will vary!
    So after selecting one Form[Radio button] and enetring other selection fields once i press execute button.
    i need to display list of Orders in ALV List output with check boxes for each record in the List Output.
    Here all the radio button Forms are related to <b>Sales Order document and Delivery document</b>
    So do we need to create new ALV List Report (or) We can use submit <b>VF31</b> transaction's program <b>[sd70av3a]</b>.
    After we are displayed with orders in the output.
    Then we should provide a functionality as such if user selects mutiple Orders/Check boxes he should be able to view multiple Orders one after other, and simultaneously generate PDF Files for Each Order Selected and attach them in Mail send them to Block of users.
    Can anybody give there sujjestions.
    Without generating spool request no's is it possible to generate PDF files for SAP SCript output!
    Is it possible to Generate & attach one/multiple PDF files to mail ID and send them to list of users!
    Can anybody give inputs.
    Thanks in advance.
    Thanks & Regards,
    Prasad.

    hi prasad,
    There is one concept called Print Work Bench(PWB) to print the multiple scripts or smartforms which r assigned to a same transaction.
    If u need the info related to PWB shoot me a test mail to [email protected]
    i will send u the same
    fot the same u can check the below link also
    http://help.sap.com/saphelp_nw04/helpdata/en/64/bf2f12ed1711d4b655006094192fe3/content.htm
    <b>Prasad i didn't get the mail from you plz check it once again</b>
    If u find it useful plz mark the points
    Regards,
    Naveen
    Message was edited by: NAVEENKUMAR GUDURI

  • ABAP QUERY PROGRAM OUTPUT SHOULD DISPLAY FROM SAP SCRIPT.

    THIS IS MY URGENT REQUIREMENT ...
    I DONT KNOW ABAP QUERY PROGRAM ..
    PLEASE SUGGEST ME A WAY ON THIS ....
    Functional requirements
    Introduction
    The wish of the customer is a printable customer overview. All desired fields will be shown in a new query called ZZADDRSS_CO. Double entries are taken for granted because of the data taken from the sales area and because of multiple contact persons. The customer accepts this. It should be made possible that the user creates and saves its own variant.
    A second overview is needed, another ABAP will be developed for this requirement. This ABAP will show all the customer data and this list will have the possibility to be printed.
    Solution
    New Query ZZADDRESS_CO
    The desired fields of attachment 1 need to be shown in the query.
    The selection criteria are shown in attachment 2.
    The column names of the additional data have to changed in the query.
    Customer Overview.
    Functional specification.
    On behalf of this customer overview a standard SAP transaction will be used (transaction VC/2).This transaction will be extended.
    The fields are shown on screen with the described headers. Printing of the overview will be done via SAP script. The script makes use of a fixed layout of the data.
    The selection criteria are specified in attachment 2.
    The layout of the customer overview and the SAP Script are specified in attachment 3.
    Specification.
    The next steps need to be performed.
    1.     A routine per infoblock need to be created in Include RV77UNNN. In this routine the data is retrieved and written down to the screen and script,
    Example LST1_901 . In include RV77SNNN you can find the standard infoblocks.
    2.     Adapt via transaction SE16 table TFRM.
    3.     Create a new view in the customizing (sales and distribution- Sales support-sales summary-Assign Reporting Views).Assign the new view to the infoblocks.(Example view 001 is assigned to block 901).
    4.     In customizing it is not possible to assign the correct window and element to the infoblock .so this is done via SE16 in table T182A.
    5.     Adapt script. Copy script SD-SALES-SUMMARY to a Z-SALES_SUMM.
    Assign this new version to the new view in customizing. Create in the main window the element who writes the data on behalf of the print.
    Attachment 1 Desired fields
    Header: Address
    ~ Customer number                          KNA1-KUNNR
    ~ Title                                               KAN1-ANRED
    ~ Name1                                           ADRC-NAME1
    ~ Name2                        ADRC-NAME2
    ~ Name3                                           ADRC-NAME3
    ~ Name4                                           ADRC-NAME4
    ~ PO Box                                         ADRC-PO_BOX
    ~ PO Box POSTAL CODE             ADRC-POST_CODE2
    ~ PO Box city                                  ADRC-PO_BOX_LOC
    ~ Telephone no1                              ADR2-TEL_NUMBER   1ST RECORD
    ~ Telephone no2                              ADR2-TEL_NUMBER   2ND RECORD
    ~ Fax number1                                 ADR3-FAX_NUMBER 1ST RECORD
    ~ Fax number2                                ADR3-FAX_NUMBER 2ND RECORD
    ~ E-mail                                            ADR6-SMTP_ADDR
    ~ Search item                                   ADRC-SORT1
    ~ Notes                                            ADRT-REMARK
    Header: control data
    ~ VAT registration number              KAN1-STCEG
    Header: Payment transactions
    ~Bank country key                         KNBK-BANKS
    ~Bank key                                      KNBK-BANKL
    ~Bank Account number                 KNBK-BANKN
    Header: Marketing
    ~ Industry key                                   KNA1-BRSCH
    ~ Industry code 1                              KNA1-BRAN1
    ~ Industry code 2                              KNA1-BRAN2
    ~ Industry code 3                                KNA1-BRAN3
    ~ Industry code 4                                KNA1-BRAN4
    ~ Industry code 5                               KNA1-BRAN5
    ~Annual sales, currency, year           KNA1-UMSA1, KNA1-UWAER, KNA1-UMAH
    ~ Yearly no of employees, year      KAN1-JMZAH, KNA1-JMJAH       
    ~ Fiscal year variant                          KNA1-PERIV
    ~Legal status                                      KNA1-GFORM
    Header: Correspondence
    ~ Our account number at customer            KNB1-EIKTO
    Header: sales
    ~ Sales office                                              KNVV-VKBUR
    ~ Customer group                                       KNVV-KDGRP
    ~ ABC-classification                                  KNVV-KLABC
    Header: Invoice
    ~Tax classification                          KNVI-TAXKD
    ~Terms of payment key                    KNVV-ZTERM
    ~
    Header: Contact Persons
    ~Title                                   KNVK-ANRED
    ~Name                                   KNVK-NAME1
    ~Advertising material                         KNVK-NMAIL
    ~Martial Status                         KNVK-FAMST
    ~Notes                                   KNVK-PARAU
    ~Function                              KNVK-PAFKT
    ~Department                              KNVK-ABTNR
    Header: Partnerroles
    ~Personnel Number                         KNVP-PERNR
    ~Name of employee                         PA0001-ENAME
    Header: Additional Data
    ~Attribute 1                              KNA1-KATR1
    ~Creation date                              KNA1-ERDAT
    ~Attribute 2                              KNA1-KATR2
    ~Change date of field KNA1-KATR2          CDHDR-UDATE
    ~Attribute 3                              KNA1-KATR3
    ~Attribute 4                              KNA1-KATR4          
    ~Attribute 5                              KNA1-KATR5
    ~Attribute 6                              KNA1-KATR6
    Attachment 2 Selection fields
    ~Customer number
    ~Sales office
    ~Personnel Number
    ~Sales Organization (default NL01)
    ~Industry key
    ~Industry codes (1 till 5)
    ~ABC- classification
    ~Creation date
    ~Attribute 1
    ~Attribute 2
    ~Attribute 3
    ~Attribute 4
    ~Attribute 5
    Attachment 3 Customer overview + SAP Script
    Customer master data sheet: 11490                 Page1
    Requested by karen Dunnewold                Date: 25.08.2004
    Address
    (Default SAP script ADDRESS statement)
    Title
    Name1
    Street + number
    PO Box city
    Country
    Search term: ADRC-SORT1
    Telephone 1:      ADR2-TEL_NUMBER     2: ADR2-TEL_NUMBER
    Fax 1:          ADR3-FAX_NUMBER     2: ADR3-FAX_NUMBER
    E-mail:          ADR6-SMTP_ADDR     
    Notes:           ADRT-REMARK
    PO BOX
    ADRC-PO_BOX
    ADRC-POST_CODE2 ADRC-PO_BOX_LOC
    T005T-LANDX (T005T-LAND1 = ADRC-COUNTRY)
    Control data
    VAT registration number:     KNA1-STCEG
    Payment transactions
    Country: KNBK-BANKS Bank-key: KNBK u2013 BANKL Bank account: KNBK-BANKN
    Marketing
    Industry           KNA1-BRSCH     Industry Description
    Industry code1          KNA1-BRAN1     Industry Description
    Industry code2          KNA1-BRAN2     Industry Description
    Industry code3          KNA1-BRAN3     Industry Description
    Industry code4          KNA1-BRAN4     Industry Description
    Industry code5          KNA1-BRAN5     Industry Description
    Figures
    Annual Sales          KNA1-UMSA1, KNA1-UWAER in KNA1-UMAH
    Employees          KNA1-JMZAH                         in KNA1-JMJAH
    Legal status            KNA1-GFORM description
    Customer master data sheet 11490                         Page 2
    Requested by karen Dunnewold                         Date: 25.08.2004
    Contact Persons
    KNVK-ANRED
    Mailings: KNVK-NMAIL           Notes: KNVK-PARAU
    KNVK-ANRED
    Mailings: KNVK-NMAIL           Notes: KNVK-PARAU
    Correspondence
    Our account number at customer      KNB1-EIKTO
    Sales
    Sales office          KNVV-VKBUR     Description
    Customer group     KNVV-KDGRP     Description
    ABC-classify          KNVV-KLABC
    Currency          KNVV-WAERS
    Invoice
    Terms of payment key KNVV-ZTERM      Tax classification KNV1-TAXKD
                                  Description     
    Partner (Leave SAP default)
    Partnerrole               Number          Name
    KNVP-PARVW          KNVP-KUNNR     NAME1
    KNVP-PARVW          KNVP-KUNNR     NAME1
    Additional data
    Attribute1          kna1-katr1     Description
    Attribute2          kna1-katr2     Description
    Attribute3          kna1-katr3     Description
    Attribute4          kna1-katr4     Description
    Attribute5          kna1-katr5     Description
    Attribute6          kna1-katr6     Description

    hi narayana
    i think u need to write a driving program and a provided with a smatform u sit along with the SD consultant.
    ur further views can be shared.
    Rgs,
    Venkat.

  • Need help in sap script

    Hi,
    I have just now started to learn sap script.I want to know good book to learn sap script.If possible send some sample programs.
    thanks in advance.

    Simple SAP script code:
    Driver program:
    *& Report  ZMADHU_PROGRAM                                              *
    REPORT  ZMADHU_PROGRAM.
    DATA: I_EKPO TYPE STANDARD TABLE OF EKPO WITH HEADER LINE.
    SELECTION-SCREEN BEGIN OF BLOCK B1 WITH FRAME TITLE TEXT-001..
    PARAMETERS: P_EBELN LIKE EKPO-EBELN.
    SELECTION-SCREEN END OF BLOCK B1.
    SELECT * FROM EKPO
    INTO CORRESPONDING FIELDS OF TABLE I_EKPO
    WHERE EBELN = P_EBELN.
    CALL FUNCTION 'OPEN_FORM'
    EXPORTING
      APPLICATION                       = 'TX'
      ARCHIVE_INDEX                     =
      ARCHIVE_PARAMS                    =
      DEVICE                            = 'PRINTER'
      DIALOG                            = 'X'
       FORM                              = 'ZMADHU'
       LANGUAGE                          = SY-LANGU
      OPTIONS                           =
      MAIL_SENDER                       =
      MAIL_RECIPIENT                    =
      MAIL_APPL_OBJECT                  =
      RAW_DATA_INTERFACE                = '*'
    IMPORTING
      LANGUAGE                          =
      NEW_ARCHIVE_PARAMS                =
      RESULT                            =
    EXCEPTIONS
      CANCELED                          = 1
      DEVICE                            = 2
      FORM                              = 3
      OPTIONS                           = 4
      UNCLOSED                          = 5
      MAIL_OPTIONS                      = 6
      ARCHIVE_ERROR                     = 7
      INVALID_FAX_NUMBER                = 8
      MORE_PARAMS_NEEDED_IN_BATCH       = 9
      SPOOL_ERROR                       = 10
      CODEPAGE                          = 11
      OTHERS                            = 12
    IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    CALL FUNCTION 'WRITE_FORM'
    EXPORTING
       ELEMENT                        = 'HEADING'
       FUNCTION                       = 'SET'
       TYPE                           = 'BODY'
       WINDOW                         = 'MAIN'
    IMPORTING
      PENDING_LINES                  =
    EXCEPTIONS
      ELEMENT                        = 1
      FUNCTION                       = 2
      TYPE                           = 3
      UNOPENED                       = 4
      UNSTARTED                      = 5
      WINDOW                         = 6
      BAD_PAGEFORMAT_FOR_PRINT       = 7
      SPOOL_ERROR                    = 8
      CODEPAGE                       = 9
      OTHERS                         = 10
    IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    LOOP AT i_ekpo.
    *v_count1 = v_count1 +
    CALL FUNCTION 'WRITE_FORM'
    EXPORTING
       ELEMENT                        = 'ITEMS'
       FUNCTION                       = 'SET'
       TYPE                           = 'BODY'
       WINDOW                         = 'MAIN'
    IMPORTING
      PENDING_LINES                  =
    EXCEPTIONS
      ELEMENT                        = 1
      FUNCTION                       = 2
      TYPE                           = 3
      UNOPENED                       = 4
      UNSTARTED                      = 5
      WINDOW                         = 6
      BAD_PAGEFORMAT_FOR_PRINT       = 7
      SPOOL_ERROR                    = 8
      CODEPAGE                       = 9
      OTHERS                         = 10
    IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    ENDLOOP.
    CALL FUNCTION 'CLOSE_FORM'
    IMPORTING
      RESULT                         =
      RDI_RESULT                     =
    TABLES
      OTFDATA                        =
    EXCEPTIONS
      UNOPENED                       = 1
      BAD_PAGEFORMAT_FOR_PRINT       = 2
      SEND_ERROR                     = 3
      SPOOL_ERROR                    = 4
      CODEPAGE                       = 5
      OTHERS                         = 6
    IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    SAP Script:
    create the window main with two with appropriate size.
    in the text include following lines.
    /E HEADING
       Items     Item Description     Net Price
    /E ITEM
      &i_ekpo-ebelp&,,&i_ekpo-txz01&,,&i_ekpo-NETPR&
    AND activate both driver prg and script.
    execute the driver program

  • Problem in SAP-Script

    Hi All,
    I am creating one report form using SAP Script, it is a replacement of standard SAP Script and which uses standard driver program. I am getting one dump while running SAP Script, it shows like "variable with name 'XXX' has not been used in so and so window".
    In that window there is a code block like,
    /: IF XXX == 'yes'
    /: ENDIF
    As I dont want this block I have commented this like,
    /* IF XXX == 'yes'
    /* ENDIF
    Please let me know how to overcome this short-dump and provide solution why such dump is comming?
    <<removed by moderator>>
    Edited by: kishan P on Sep 13, 2010 4:19 PM

    Hi,
    This is one of the problem of Standard SAP Script driver program, we can over come easily, we no need to comment anything rather do follow the code you can easily solve your issue, I also face the same issue previously.
    your code is,
    /: IF XXX = 'Yes'
    /: ENDIF
    like this means, then change the code like this,
    /: IF 1 = 2
    /: IF XXX = 'Yes'
    /: ENDIF
    /: ENDIF
    here, you didnt write any comment, also the code will never execute.
    Why we are doing this means, driver program expects particular variable has to be used in particular window, but it never expects that variable has to be executed. By using this code you can use the variable also it will never be executed.
    Hope it will be helpful. If you find any other solution please let me know, Thank you:)

  • Migration of SAP Script to SmartFrom

    Hi Experts,
    I migrated an SAP Script to a Smartform. The SAP Script have a lot of PERFORM <...> IN PROGRAM <....> and these are written in a report porgram. I want to know, how to convert those calls and subroutines so that I can use them in Smartforms. your help is appreciated.
    Thank you,
    Surya.

    You can copy the code into CODE BLOCKs in Smartform.
    In SAPscripts, these performs are used to calculate some value or processing some data.
    You can do the same in the CODE blocks in Smartform. Identify what exactly that perform is doing and identify where exactly you can write that in Smartform so that it fits with overall flow of the Smartform.

  • Same set of data should print twice on same page in SAP SCRIPT

    Hi Experts,
    I come across a requirement where I need same set of data in sap script should print twice as it is on same page.
    and if first page overflow, then same scenario should continue till complete data is printed. Basically main window data should print twice in two blocks on same page.
    E.g.
    If I have 10 line item which is to be printed on top window on  first page. Now I want that same 10 lines should be printed in a block below the first block. Data should flow similarly across multiple pages.
    Hope my question is pretty clear. I am expecting suitable answers from experts.
    Thanks in advance.
    Regards,
    Vijay

    Hi
    I had the same request for a check form in Canada. I solved it by writing the line item output into variables and print these variables in a second window. It was ~10 hours of effort, not a real nice technical solution but it worked.
    If you require I can send you a PDF of the sap script form definition. You can contact me at [email protected] Answers can take 1 week or more. 
    Best regards
    JD

  • 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

  • Printing sap script to spool by skipping print parameter window

    Hi all,
    I am trying to print an output (derived from sap script) directly from program to spool and then fetch the spool request and download it to PDF. This should happen automatically when the end user executes the program by giving required inputs. Can any one guide me on this ?
    Rgds,
    Praveen

    Hi all,
    I got the problem solved. Thanks for all who replied and supported me. This is how i solved it. This is not the full code. I am not giving declaration part here. But this is the main blocks which is going to work.
    Data: purdocno TYPE string,
                        v_len_in TYPE i.
    PERFORM open_from.
        LOOP AT it_itab.
          ON CHANGE OF it_itab-ebeln.  
              PERFORM start_form.
              PERFORM write_form.
              PERFORM end_form.
          END ON.
        ENDLOOP.
    PERFORM close_form.
    PERFORM convpdf.
    FORM convpdf.
        CALL FUNCTION 'CONVERT_OTF'
         EXPORTING
           format                      = 'PDF'
    *       MAX_LINEWIDTH               = 132
    *       ARCHIVE_INDEX               = ' '
    *       COPYNUMBER                  = 0
    *       ASCII_BIDI_VIS2LOG          = ' '
           PDF_DELETE_OTFTAB           = 'X'
         IMPORTING
           BIN_FILESIZE                = v_len_in
    *       BIN_FILE                    =
          TABLES
            otf                         = i_otf
            lines                       = i_pdf
         EXCEPTIONS
           ERR_MAX_LINEWIDTH           = 1
           ERR_FORMAT                  = 2
           ERR_CONV_NOT_POSSIBLE       = 3
           ERR_BAD_OTF                 = 4
           OTHERS                      = 5.
        purdocno = s_ebeln+3(10).
        concatenate 'c:\' purdocno '.pdf' INTO purdocno.
        CALL FUNCTION 'GUI_DOWNLOAD'
         EXPORTING
    *      BIN_FILESIZE                    =
          filename                        = purdocno
          FILETYPE                        = 'BIN' " important
    *    IMPORTING
    *      FILELENGTH                      =
         tables
           data_tab                        = i_pdf
         EXCEPTIONS
           FILE_WRITE_ERROR                = 1
           NO_BATCH                        = 2
           GUI_REFUSE_FILETRANSFER         = 3
           INVALID_TYPE                    = 4
           NO_AUTHORITY                    = 5
           UNKNOWN_ERROR                   = 6
           HEADER_NOT_ALLOWED              = 7
           SEPARATOR_NOT_ALLOWED           = 8
           FILESIZE_NOT_ALLOWED            = 9
           HEADER_TOO_LONG                 = 10
           DP_ERROR_CREATE                 = 11
           DP_ERROR_SEND                   = 12
           DP_ERROR_WRITE                  = 13
           UNKNOWN_DP_ERROR                = 14
           ACCESS_DENIED                   = 15
           DP_OUT_OF_MEMORY                = 16
           DISK_FULL                       = 17
           DP_TIMEOUT                      = 18
           FILE_NOT_FOUND                  = 19
           DATAPROVIDER_EXCEPTION          = 20
           CONTROL_FLUSH_ERROR             = 21
         OTHERS                            = 22.
        IF sy-subrc <> 0.
    *     MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *             WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
        ENDIF.
    ENDFORM.

  • 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

  • Zebra background - sap script

    Hi Everyone,
    Can anybody say how to create zebra background in sap script. Eg:- line number one the background is blank and line number 2 is shaded with grey background and line number 3 is blank and so forth.....
    The numbers of lines are dynamic data (repeating) and the numbers are unknown.

    Hi Arun,
    Yes, it is possible to make a bank ground picture in SAPscript also. For this you have to do is create a new window and see the dimensions fit the entire page. Now creat vertical frames in that window at equal gap and fill the alternative blocks of it.
    This will give you zebra background in SAP Script.
    Note: all other windows that contains data/ text will not be effected. it will be displayed on the image.
    Hope this will help.
    Regards,
    Nitin.

  • Sap script window

    Hi All
    Is it possible to print the outer line of the window in SAP script like address window, I want to print the whole address in a block. IF any body can guide me that would be great.
    thanks
    C

    Hi
    This will help you.
    /: BOX XPOS YPOS WIDTH HEIGHT FRAME INTENSITY
    /: POSITION XORIGIN YORIGIN WINDOW PAGE
    /: SIZE WIDTH HEIGHT WINDOW PAGE
    BOX:
    WIDTH
    Width of the box. Default: WIDTH value of the SIZE command.
    HEIGHT
    Height of the box. Default: HEIGHT value of the SIZE command.
    FRAME
    Thickness of frame. Default: 0 (no frame).
    INTENSITY
    Grayscale of box contents as %.
    Example:
    /: BOX WIDTH '17.5' CM HEIGHT 1 CM FRAME 10 TW INTENSITY 15
    /: BOX WIDTH '17.5' CM HEIGHT '13.5' CM FRAME 10 TW
    /: BOX XPOS '10.0' CM WIDTH 0 TW HEIGHT '13.5' CM FRAME 10 TW
    /: BOX XPOS '13.5' CM WIDTH 0 TW HEIGHT '13.5' CM FRAME 10 TW
    Regards
    Anshul

  • Create new window in SAP Script

    Dear All
       how to create new window in sap script
    Regards
    Suresh
    Edited by: Alvaro Tejada Galindo on Apr 9, 2008 11:58 AM

    Hi,
    To create a new window in scripts.
    1.  After opening the form in SE71   Click on Windows push button.
        it will gives a screen  list of windows in a page
    2. Click on Edit option in menu bar  in Edit-->Create Element click it will gives a popup window in the window give Name of the window and short description press enter  like that you can create windows in  a page
    3.  Click on Page windows it will gives a screen where that window you want to place in that page.    Click on Edit option on menu bar Edit-->Create Element
    it will gives a list of windows which your created in a page   here you have to select which window you want to place.  Double click on that window it will adds on the page and give the bottom of the screen you can find  standard attributes block
    there you have to give the position of the window in a page. 
    or
    Click on setting option on menu bar  settings-->form painter
    it will gives a GUI editor here you can drag the window position it is easy to use.
    then you can see the layout.
    Thanks
    Ganesh

Maybe you are looking for

  • Sender mail adapter error

    hi all, I am working on mail-mail scenario where in when i monitor my sender CC it is displaying following error: "exception caught during processing mail message; java.io.IOException: unexpected login response; read 001F BAD Protocol Error: "Invalid

  • Out of the box porlets for Content Management with BEA Portal

    I am looking at BEA Portal for a simple Intranet site with some basic content management system capabilities. I would like to implement this without the use of a third party tool and wanted to know if there are any open source or out of the box BEA p

  • Creating PDF from Publisher files - failure

    my first attempt at converting a publisher file to PDF format failed - no reason given. Too much security on my computer? How can I resolve this probem?

  • How to bind local variables in complex query in PL/SQL

    Hi I have long complex query with local varibales; when I run in Dynamic SQL I get an error. Not sure which is the easiest way to bind local variables. L_QUERY := q'[select m.segment1 col1,       '1' col2,       '13' col3,       l.operand col4,      

  • Advance on asset

    Hello All, I want to confirm whether is it good practic to load advance amount on Asset via downpayment  with respect to asset po. Suggest.