Find check print script program in nace

Hi experts,
check printing script program ( TCODE  IS  FCH7 ).
how to find in the NACE  this check print script program.
please help me in this

Hi,
Hi,
FI documents are not maintained in NACE. In Nace if you can see there are several applications but nothing is for FI or CO.
Print program RFFOUS* to print cheque.
Thanks,
Abhijit

Similar Messages

  • Check printing script debuggin problem

    Hi
    i am working on a check printing script. i need to adjust the layout of few things in this layout.
    in the debuggin mode i am getting the short dump stating vendor number = xxxxxxxxxxxx (invalid).
    can anyone tel me the windows for date,account payee,amount in words and amount in figures or atleast the fields related to them r tell me where i have to correct my script to proceed in debuggin mode.
    thanks in advance

    Hi,
    CHECKSPL  -> for amount in words,
    CHECK -> other fields ( date, amount )
    CHECKADD -> Payee
    other open form se71 -> display -> go to UTILITIES menu -> select FORM INFO. option
    There you find with general Find( CTRl + F ).
    Reward if helpful.
    Bye

  • How to include script program in nace

    Hi experts,
    I developed one script program now i want to transport this program to production.How to include this program in the NACE tcode
    and this program belongs which application type (how to decide).This program belongs to MM module.(creating a material issue slip).I am basic abaper and i am handilng first time the script task  and also i am seraching sdn forums.Please gine me the steps.

    Hi,
    1. Goto in NACE
    2. You need to ask your functional buddy to let you know about Application area, I suppose u need to take EF.
    3. Select EF from the list and than click on Output Types, select any output type (Which you wud like to give to your script)
    4. Else if you like to create a new one for your script, then on same screen click on change button, then click on New Entries
        And give all the detailed info.
    5. To use existing output types, select a output type like "ZEDI", at the left hand side double click on Processing Routines.
    6. In the Processing Routines block , Give the Program name as print program and here you need to give your SAP scrip name in Form option.
    save it.
    I Hopr I have covered everything, that you need.
    Regards,
    Lokesh

  • Check Print - Script form designing

    Dear experts,
    We are using script form to print cheque as per client requirement... his angle/ layout is as follows
    Header data contains:
    Venodr A/c no: xxxxx   //                                                                        Paymt doc. no. xxxxxxxxx//
    Title, name  of the vendor: xxxxxxxx  //                                                       Date: xxxxxxxxx//
    Adress of the payee: xxxxxxx//
    Advice data contain:
    Doc no.//          Doc Date//      Vendor Bill No//   Bill amount//   Passed Amt//   TDS  Paying (net) amt//
    123//                 xx xx xxxx//       xxxxxxx//           50,000//        30,000//         500//           29,500//
    124//                 xx xx xxxx //       xxxxxxx//          40,000//         25,000//        100//           24,900//
    Total//                  -
              90,000//          55,000//             600//    54,400//
    Other deductions:
    Debit memo raises//      (2,000)//
    Penalty levied//             (2,400)//
    Total//                        50,000//
    And this Rs50,000 is to be paid now through the cheque....
    Please guid me to get all the figures in Script form.. i need tables, feilds and table relations in this regard..
    U may advice me any other way in order to satisy all the above needs..
    Reagards:
    Dasu
    Edited by: Bejugama Sri Dasharathi on Apr 1, 2009 1:50 PM
    Edited by: Bejugama Sri Dasharathi on Apr 1, 2009 1:52 PM
    Edited by: Bejugama Sri Dasharathi on Apr 1, 2009 1:58 PM

    Hi Dasu,
    So ur preparing a FS for the check print output.
    Pls find the FS that i had prepared, it would be helpful to u:
    Header details of chq:
    1) Vendor code : PAYR-LIFNR
    2) Vendor Name and address:
    PAYR-ZSTRA,
    PAYR-ZORT1, PAYR-ZPSTL
    3) Vendor Pan no: J_1IMOVEND-J_1IPANNO , where J_1IMOVEND-LIFNR= PAYR-LIFNR
    4) Date: PAYR-ZALDT
    5) Amount: PAYR-RWBTR (remove u2013ve sign)
    6) Payment doc no : PAYR-VBLNR
    7) Cheque no : PAYR- CHECF
    Advice layout
    1) Doc no: put the payment doc (PAYR-VBLNR) in BSEG-AUGBL, take BSEG-BELNR of line where BSEG-AUGBL is not equal to BSEG-BELNR
    2) Doc date: BKPF- BLDAT of 1)
    3) Vendor Bill no: BKPF- XBLNR of 1)
    4) Bill amount: 5+6
    5) TDS amount: WITH_ITEM- WT_QBSHH of 1)
    6) Net amount: WITH_ITEM- WT_QSSHH of 1)
    Cheque Layout
    1) Pay to: PAYR-ZNME1
    2) Amount in words : amt in words of PAYR-RWBTR
    3) Date: PAYR-ZALDT
    4) Amount in figures: PAYR-RWBTR (remove u2013ve sign)
    If the lines in the page overflow (line items in advice layout), print the additional lines in 2nd page, but cheque layout should be blank (rest all layout should come)
    I think i have replyed this only to ur similar query earlier.
    Regards,
    Kiran

  • Check print using f110

    Hi all
    i copied the check print script F110_PRENUM_CHCK....and made changes as per required...
    i did no change in the driver program ie RFFOUS_C....
    now i m using two tcodes F110 & FBZ5...for printing...check....
    its printing properly from FBZ5 ....but while printing thru F110 it is printing two checks.....
    i removed( commented the text in scripts and deleted the next page ) the advice note ,summary ,i m printing only the check....
    F110 is printing two check e.g.000320,000321.........
    is it a problem of configuration...plz let me knw....
    i also changed the script name from FBZP....
    so plz let me knw...
    Thnx
    Rohit

    When the SAPscript form is called, it uses the formname which is setup in configuration.  The following is the path in configuration (t-code SPRO) where the formname is entered:
    SAP Customizing Implementation Guide>Financial Accounting>Accounts Receivable and Accounts Payable>Business Transactions>Outgoing Payments>Payment Media>Make Settings for Classic Payment Medium Programs-->Assign Payment Forms for Payment Method in Company Code
    This path (in SPRO) will allow you to setup payment methods and the corresponding form names for a particular company code.  Once you select a specific company code and click on the "Allocate forms to payment method in company code" folder in the left-hand window area, it looks like you have the option to specify a SAPscript formname or a "PDF-based Payment Medium Form"
    I am unsure of the actual logic used to call the Adobe form.

  • Check print thru F110

    Hi all
    i copied the check print script F110_PRENUM_CHCK....and made changes as per required...
    i did no change in the driver program ie RFFOUS_C....
    now i m using  two tcodes F110 & FBZ5...for printing...check....
    its printing properly from FBZ5 ....but while printing thru F110 it is printing two checks.....
    i removed( commented the text in scripts and deleted the next page )  the advice note ,summary ,i  m printing only the check....
    F110 is printing two check e.g.000320,000321.........
    is it a problem of configuration...plz let me knw....
    i also changed the script name from FBZP....
    so plz let me knw...
    Thnx
    Rohit

    HI
    You have to deactivate sample print out from the variant that is being used in F110.
    You can get into the variant from F110.
    Good Luck
    Hari

  • How to find Driver program for an Particular Script Excluding TNAPR, NACE

    Hi Friends,
    I had an problem now, that I need to find the driver program for Dunning 'F150' which I already checked in TNAPR table and NACE transaction code, but I couldn't find any desired results on this search. Kindly can anybody suggest me for getting out of it as I need to make some changes over the driver program. Your help is mostly appreciated.
    Thanks in Advance,
    Murali.

    hi,
    try this.
    goto se71 transaction.give your form name click display.in menu goto form - check -texts and press enter.
    you will get all the print programs used for that script.

  • How to find the print program for a sap script

    Hey Experts,
    How to find the print program for a sap script (espicially when it is a custom script(Z*))?
    Thanks a ton,

    Thanx Vijay,
    Actually when I searched for the program in both the tables it didnt show up ther.
    But when I did check in the texts of script, I found it.
    Good job.
    Thanks all.
    Vijay, a small doubt.
    But why didn't it show up in those 2 tables when all the print programs for standard scripts show up usually?
    thnx once again.
    Message was edited by: dev a

  • How to find out the script name used in driver program

    Hi Folks ,
                 I want to find out the Scripts(print program) used in my driver pogram .
    How is it possible any Tcode availble for this ?
    Thanks ,
    Jaga.D

    Hi Jagadish,
    Go to transaction SE38 and open the program RSNAST00. There search for the subroutine TNAPR_LESEN.
    Set a break point at that subroutine and leave. When printing the data from a transaction to a script or form (Like VA01 or VL02N), debugger is started when the processing reaches the subroutine in RSNAST00. There double click on the field TNAPR-FONAM. continue step-by-step execution. The field will display the name of the script or form that is currently being used.
    Another way to do this is to go to transaction NACE and check the transaction for which you want to find out the script. There you will find the script and print program that have been set for a particular transaction.

  • How can i find the printing program?

    hi
    i have sap script how can i find the printing program ?
    ami

    ami bardogo wrote:
    hi
    what is the different between the commands 'break' and 'break-point'
    thanks,
    ami
      h2 Breakpoints  h2
    Apart from being able to execute an ABAP program in the Debugger, you can also start the Debugger call by the choosing a breakpoint. This is achieved by setting one or more of these breakpoints in the program. A breakpoint is a signal at a particular point in the program that tells the ABAP runtime processor to interrupt processing and start the Debugger. The Debugger is activated when the program reaches this point.
    There is also a special kind of breakpoint called a watchpoint. When you use watchpoints, the Debugger is not activated until the contents of a particular field change. For more information, refer to the chapter Watchpoints.
    Breakpoint Variants
    The Debugger contains different breakpoint variants:
    Static
    A user-specific breakpoint is inserted in the source code as an ABAP statement using the keyword BREAK-POINT. A non user-specific breakpoint is set in the ABAP Editor using the BREAK user name statement.
    Directly set
    dynamic breakpoints
    Can be set in the ABAP Editor or the Debugger by double-clicking a line, for example. Dynamic breakpoints are always user-specific, and are deleted when you log off from the R/3 System.
    Breakpoints
    at statements
    The Debugger stops the program immediately before the specified statement is executed.
    Breakpoints
    at subroutines
    The Debugger stops the program immediately before the specified subroutine is called.
    Breakpoints at function modules
    The Debugger stops the program immediately before the specified function module is called.
    Breakpoints at methods
    The Debugger stops the program immediately before the specified method is called.
    Breakpoints at exceptions and system exceptions
    The Debugger stops the program immediately after a system exception, that is, after a runtime error has been intercepted.
    Static Breakpoints
    Static breakpoints are always user-independent if there is no specification of a user name. Once a user has inserted the statement BREAK-POINT or BREAK name in an ABAP program, the system always interrupts the program at that point for that user or only for the user name. This procedure is only useful in the development phase of an application when program execution is always to be interrupted at the same place. For more information, refer to the chapter Static Breakpoints.
    In HTTP sessions, a static breakpoint is skipped if you did not set additional dynamic HTTP breakpoints in the editor of a BSP page. Instead, a corresponding system log entry is written, which can be checked using transaction SM21.
    Dynamic Breakpoints
    Dynamic breakpoints are user-specific. Therefore, you should use them if you only want the program to be interrupted when you run it yourself, not when it is being executed by other users. All dynamic breakpoints are deleted when you log off from the R/3 System.
    Dynamic breakpoints are more flexible than static breakpoints because you can deactivate or delete them at runtime. They have the following advantages:
    ·        You do not have to change the program code.
    ·        You can set them even when the program is locked by another programmer.
    ·        You can define a counter that only activates the breakpoint after it has been reached.
    Special dynamic breakpoints are useful when you want to interrupt a program directly before a particular ABAP statement, a subroutine, or an event, but do not know exactly where to find it in the source code. Event here is used to refer to the occurrence of a particular statement, for example, or calling up a method. Special dynamic breakpoints are user-specific. You can only set them in the Debugger. For more information, refer to the chapter Dynamic Breakpoints.
    In HTTP sessions, the system stops both at static and dynamic breakpoints if a dynamic breakpoint was set in the editor of a BSP page before program execution.
    Lifetime and Transfer of Breakpoints
    A static breakpoint remains intact as long as the BREAK-POINT or BREAK-POINT name statement is not removed from the source code. Without saving, dynamic breakpoints only remain intact in the relevant internal session. However, they remain in effect during the entire user session if they are saved by choosing the menu path Breakpoints ® Save in the ABAP Debugger. For more details on the subject of user sessions and modes, refer to Modularization Techniques in the ABAP keyword documentation.
    If you call an HTTP session during a user session, only the HTTP breakpoints are loaded when the HTTP session is started. You activate HTTP debugging in the ABAP Editor by choosing Utilities ® Settings ® HTTP Debugging. Depending on the setting, the system then displays either the HTTP or standard breakpoints in the Editor.
    If you call an update session during a user session, breakpoints that were defined beforehand in the calling processing unit are copied to the new update session, where they can be displayed under Breakpoints. If, in the ABAP Debugger, you check Update Debugging  under Settings and then, for example, call the update module func using CALL FUNCTION func IN UPDATE TASK, a new window is opened in which you can debug this function module in the update session. All the breakpoints that were set in the calling processing unit can also be processed here.
    For further information on special breakpoints, refer to:
    Breakpoints at Statements
    Breakpoints at Subroutines
    Breakpoints at Function Module Calls
    Breakpoints at Methods
    Breakpoints at System Exceptions
    h2 page  break h2
    WINDOW TYPES
    When defining a layout set window, you must select a window type for the window. You can choose between three types:
    • Constant windows (CONST)
    • Variable windows (VAR)
    • Main windows (MAIN)
    CONSTANT WINDOW
    A window of type CONST has the same contents and size on all layout set pages, on which a corresponding page window is defined. This allows the processing of the window contents to be optimized internally.
    Page windows whose allocated window is of type CONST must have the same size throughout the layout set. If a window of type CONST is full, all remaining text the application program wants to output in this window, is lost. Constant windows do not trigger a page break. In other words: all text exceeding the window size is simply truncated.
    VARIABLE WINDOW
    The contents of variable windows is processed again for each page, on which the window appears. The system outputs only as much text as fits into the window. Text exceeding the window size is truncated; the system does not trigger a page break. Unlike constant windows, the page windows declared as variable windows may have different sizes on different layout set pages.
    As far as the processing of the window contents is concerned, the system currently treats constant and variable windows alike. The only difference is that constant windows have the same size throughout the layout set.
    MAIN WINDOW
    Each layout set must have one window of type MAIN. Such a window is called the main window of the layout set. For SAPscript layout sets, the main window has a central meaning:
    • It controls the page break.
    • It contains the text body that may cover several pages.
    • It allows to fix text elements at the upper and lower margins of the allocated page window (for example, for column headings).
    As soon as a window of type MAIN is full, SAPscript automatically triggers a page break and continues to output the remaining text in the main window of the subsequent page. Page windows of type MAIN have the same width throughout the layout set. The SAPscript composer thus avoids reformatting of the text after each page break.
    If a page does not have a main window, the system implicitly processes all other windows of the page and continues with the subsequent page. This page must not call itself as subsequent page (recursive call), since this would produce an endless loop. In such a case, SAPscript terminates the output after three subsequent pages.
    HOW THE COMPOSER WORKS
    The composer or layout set processor is the central formatting module for the print output. It prepares the texts for the different output devices by using the allocated styles or layout sets.
    Processing a layout set happens in a certain order. You must know some facts concerning the different window types, the setting of subsequent pages, or the dynamic control from within the print program.
    Page control in layout sets
    Define subsequent page statically
    Define subsequent page dynamically
    Format a layout set page
    PAGE CONTROL IN LAYOUT SETS
    SAPscript automatically triggers a page break as soon as the main window of one page is full. To be able to execute the page break, the system must know on which subsequent page to continue outputting the text. You can specify the subsequent page either statically when defining the layout set, or you can set the subsequent page dynamically during layout set output.
    If the subsequent page is not specified, SAPscript automatically terminates printing, thereby ignoring any other output statements of the application program.
    DEFINE SUBSEQUENT PAGE STATICALLY
    You define the subsequent page statically with the layout set maintenance transaction. First, specify the start page in the layout set header. The system automatically calls this page whenever the layout set is started. With this page, or, more correctly, with the page window of this page, the text output starts. For each page, specify the subsequent page in the page definition. After a page break, the system continues text output on the subsequent page defined for the last page. By specifying start page and subsequent pages, you can define a page sequence.
    DEFINE SUBSEQUENT PAGE DYNAMICALLY
    The page sequence set in the layout set definition can be changed by the application program dynamically at runtime. If you want the layout set to start with a page other than the one defined in the layout set header, specify the desired start page using the parameter STARTPAGE when you call the function module START_FORM. However, this new start page is valid only for the current call of the function module.
    If you want to break to a subsequent page other than the one specified in the page definition, use the control statement NEW-PAGE to set the name of the new page.
    NEW-PAGE .
    NEW-PAGE ends the output on the current page. The new subsequent page is only valid for the current call of the control statement. You can either include the control statement explicitly into the text of a text element or pass it to the layout set output using the function module CONTROL_FORM.
    FORMAT LAYOUT SET PAGE
    The process of formatting the output is controlled by the text contents in the BODY area of the main window. If the main window is completely filled, or if the control statement NEW-PAGE appears in the main window, the system executes a page break. Only at this point in time the system formats the contents of the windows of the other types and replaces the variables with the current values.
    For each other window, the system first outputs the default text element, if it exists. Then it processes and formats the list of the active text elements of this window, which you set using the function module WRITE_FORM with the parameter FUNCTION (SET, APPEND, DELETE). Any text that does not fit into the page window is truncated.
    As a consequence to this processing order of the composer, the reservation of space for the TOP and BOTTOM areas must be made beforehand. If the BODY area of the main window already contains text, a new text output to the TOP area does not appear on the current page but on the subsequent page in the TOP area. The same applies for the BOTTOM area. If the BODY area is filled to such an extend that the new BOTTOM text no longer fits into the current main window, this text appears on the subsequent page in the BOTTOM area.
    A frequent error in application programs is that for the subsequent page (for example, NEXT) of a layout set no main window is defined. If the formatted text of the previous page did not fit into the corresponding main window , the composer searches the subsequent pages for a main window to output the text remainder. However, if the subsequent page of NEXT is NEXT again, the composer encounters an endless loop.
    To be able to create correct page breaks in longer text, you should define a main window on each layout set page.
    LAYOUT SET CONTROL
    To output SAPscript layout sets, in the print program you must always start the output with OPEN_FORM and end it with CLOSE_FORM. The function module OPEN_FORM initializes the SAPscript composer and opens the specified layout set for subsequent output. The system combines all output for this layout set up to the CLOSE_FORM to one print request. If CLOSE_FORM is missing, nothing will be printed.
    To output data in a layout set, you must use the SAPscript function modules WRITE_FORM, WRITE_FORM_LINES, and CONTROL_FORM. You can use these function modules any number of times in any order between opening and closing a layout set.
    You cannot use the ABAP/4 statement WRITE to write output to a SAPscript layout set.
    Several print requests
    Start a layout set again
    Switch layout sets
    Find layout sets
    SEVERAL PRINT REQUESTS
    Within one transaction, you can open and close several layout sets using OPEN_FORM and CLOSE_FORM, however not simultaneously. You can use parameters in the OPEN_FORM to control whether the output is stored in the same print request. But also the SAP spool decides, depending on several plausibility checks, whether new output is appended to an existing print request or whether to create a new print request anyway.
    CALL FUNCTION 'OPEN_FORM'
    CALL FUNCTION 'CLOSE_FORM'
    CALL FUNCTION 'OPEN_FORM'
    CALL FUNCTION 'CLOSE_FORM'
    You cannot combine ABAP/4 list output and SAPscript output in one print request.
    START A LAYOUT SET AGAIN
    Usually a print program does not print only one urging letter or one account statement, but several layout sets for different customers. To have the output for each customer begin with the start page of the layout set, you must start the current layout set again and again.
    To start a layout set again, you must first end the current layout set and then open the layout set again. Within one print request, first call the function module END_FORM. It executes the final processing for the current layout set. Then start the layout set again using START_FORM. Output then begins again on the start page of the desired layout set.
    CALL FUNCTION 'OPEN_FORM'
    CALL FUNCTION 'START_FORM'
    CALL FUNCTION 'END_FORM'
    CALL FUNCTION 'START_FORM'
    CALL FUNCTION 'END_FORM'
    CALL FUNCTION CLOSE_FORM
    If you use START_FORM and END_FORM, you must not specify a layout set for OPEN_FORM. However, in this case you can use the SAPscript output functions only after opening a layout set with START_FORM.

  • SAP Script Check printing Layout, Line Items to display twice in First Page

    Hi All,
    This requirement is for US check printing Layout.
    My Requirement is to display Items twice on the first page.
    Eg : Main Window has 10 Items, I need to display all the Items at the bottom in another window at the bottom.
    I can't create 2 Main windows in the first page, as the data from the Main window 1 overflows to Main window 2 in the first page.
    I copied print program RFFOUS_C into a Z-version and try to implement the logic, however unable to print the line items in the bottom window.
    Kindly give your valuable Inputs.
    Thanks
    Vinayak

    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

  • F-58 Print Program for Check Printing

    Hi Guys,
    Have some questions here:
    1) How to locate the print program for F-58 on the Check? We can configure the form by payment method but can't seem to find the print program like other FI correspondences.
    2) Can i ignore the check printing and just print payment advice (if any) after posting via F-58?
    Anyone has done this before?
    Please advice.
    Thanks and Regards,
    Andrew

    Hi
    I think I could understand your requirement. There is no special PRINT PROGRAM FOR Payment Advice.
    There is Print program for check printing : RFFOUS_C
    along with above print program Payment Advice and Payment summary will be printed.
    check tcode: OBVCU, here we assign the print program.
    and Form will be assigned in tcode: OBVU
    or in last case do payment with out any print and create payment advice manually in tcode: FBE1
    any questions revert back please
    Regards
    Hari P
    Edited by: Hari Peddi on Nov 25, 2008 9:51 AM

  • How to change font size in check printing program in AP Invoice

    I would like to know how to change font size in check printing program in Oracle Payables Module for Invoice printing. We are using Oracle standard
    report to print check.
    Concurrent program short name : APXPBFEL
    Prt file : APLASP.prt
    I modified prt file for code 199 like below
    code "199" esc "(8U" esc "(s0p12.00h10.00v0s0b3T" esc "&k11.75H"
    Font size changed for last page only which prints checks, for Void pages its printed with default font. For Page 1 printed with default font and page 2 has reduced font. This change is not intiallized for all pages.
    Please let me know if you any of you know how to change fonts.
    Thanks,
    Anand

    *Default FullZoom Level: https://addons.mozilla.org/firefox/addon/default-fullzoom-level/

  • Format Payments check printing program completes in warning APP-FND-00500:

    Hi All,
    I'm in process of converting Oracle Payables check printing from reports 6i to XML publisher.
    I created template, data definition and changed the output for concurrent program to XML.
    I tried printing check and 'Format Payments (Evergreen)' concurrent program completed with warning.
    Log file has following error.
    APP-FND-00500: AFPPRN received a return code of failure from routine FDUPRN. An error occurred while AOL tried to spawn the print process
    Cause: AFPPRN received a return code of failure from the OSD routine FDUPRN. An error occurred while AOL tried to spawn the print process.
    Any one there has any idea what this error is for.
    Thanks
    pallavi

    This could have something to do with the fact that your printer is not set up correctly. Can you run a plain text (OReports) file output to the same printer? If not, then the printer is not set up in FND correctly. If you can ...
    Remeber that unless you have a more modern printer that can handle PDF documents natively then XMLPs PDF is going to need to be converted to PS or PCL. I would suggest you investigate the PASTA printer driver and get that set up. It provides the ability to call a program pdf2ps for instance, to convert the PDF to PS. There is a bunch of info on metalink
    Tim

  • Configuration of Check printing in Automatic Payment Program

    Hi
    I am able to run the automatic payment program. But I am not sure how to configure check lots and check printing.  Could any one please help me with step by step instruction regarding the configuration required after running the program.
    Thanks
    Hariharan G

    Hi
    For the program RFFOUS_C give Variant(X).
    select maintain Variants button and select continue button.
    give program run date , Identification feature , paying company code , sending company code , payment method , House Bank , Account ID , Check Lot NO..
    Under Print Control
    select Print checks checkbox , give printer name and select print immediately checkbox.
    select Print Payment Advice Notes checkbox , give printer name and select print immediately checkbox.
    select Print Payment Summary checkbox , give printer name and select print immediately checkbox.
    No. of sample printouts (0) and select do not Void any checks checkbox.
    select Attributes button and give description and save.select back arrow.
    select Printout button and select Start Immediately checkbox.
    In the job name for the ? give variant name(X) and enter.
    To see the printed checks from the menu select System -
    >Services -
    >Jobs -
    >Job Overview(SM37) and execute.
    Also go to SP01 and execute.
    we will get the list of spool requests.
    Regards
    Venkat
    Edited by: Venkat Dara on Feb 4, 2009 12:55 PM

Maybe you are looking for