SAP ISU Print Workbench

Hi,
Can any one provide me the basics of the SAP ISU Print workbench?
Regards,
Chandan
Moderator message: please search for available information/documentation.
Edited by: Thomas Zloch on Sep 23, 2011 11:39 PM

Hello,
You need to attach application form for each and every Correspondence Type.
Few of the Corr types are
BL44 Outgoing Payment Confirmation
BL45 Account Statement
BL46 Capital Transfer Offer
BL47 Payment Plan
BL48 Rollover Offer
BL49 Repayment
BL50 Borrower Change Without Capital Transfe
BL51 Deferral of Customer Loan
BL52 Capitalization of Overdue Items CL
BL53 Installment Plan Change CL
BL54 Consumer Loan Confirmation
BL55 Notice Given by Bank
BL56 Rescind Credit Life Insurance
BL57 Confirmation of Change
BL58 Interest on Arrears Statement
You can define them in IMG\FICA\Basic Functions\Correspondence\Define Correspondence types.
<SAP provides lot of correspondence types. You have to copy them from client 000>
After that you have to define application form for correspondence types in
IMG\FICA\Basic Functions\Correspondence\Define Application Forms for Correspondence.
You have to attach SAP defined correspondence forms.
To trigger correspondence, you have to run FPCOPARA run mentioning relevant correspondence type.
The data gets updated in table DFKKCOH.
Do remember that apart from above config, there are various areas of correspondence config you need to do for different categories like Payments, Returns, Refunds , Dunning & Collection agency.
For ex, for Returns, you attach  application form in Return reason codes, similarly for Dunning, you attach the application form in Dunning activites ...
To view the list of Application forms, use T-Code EFRM
Hope this helps
Rgds
Rajendra

Similar Messages

  • ISU Print workbench

    Can someone pls tell how to create a selection screen for providing inputs to a print workbench application form?

    Hi,
    In the start or end exit of the application form write the following code to get the user input.
    FORM f1000_get_user_input.
      DATA: wa_scrfields TYPE sval.
      CONSTANTS : lc_but050(10) TYPE c VALUE 'BUT050',
                  lc_but000(10) TYPE c VALUE 'BUT000',
                  lc_dfkkcoh(7) TYPE c VALUE 'DFKKCOH',
                  lc_servcont(10) TYPE c VALUE 'SOBJECTFVD',
                  lc_service(20) TYPE c VALUE 'Service Contract No',
                  lc_ztcorr_sign(15) TYPE c VALUE 'ZTCORR_SIGN',
                  lc_ztcorr_code(15) TYPE c VALUE 'ZTCORR_CODE',
                  lc_ztcrm_addrtyp(15) TYPE c VALUE 'ZTCRM_ADDRTYP',
                  lc_5                        VALUE '5',
                  lc_title_welcome(20) TYPE c VALUE 'WELCOME LETTER',
                  lc_contact(20)  TYPE c VALUE 'Contact Partner',
                  lc_department(20) TYPE c VALUE 'Department',
                  lc_address_type(20) TYPE c VALUE 'Address Type',
                  lc_partner2(10) TYPE c VALUE 'PARTNER2',
                  lc_partner(10) TYPE c VALUE 'PARTNER',
                  lc_signcode(10) TYPE c VALUE 'SIGNCODE',
                  lc_addr_typ(10) TYPE c VALUE 'ADDR_TYP',
                  lc_letrvar(10) TYPE c VALUE 'LETRVAR',
                  lc_cm33 TYPE dfkkcoh-cotyp VALUE 'CM33'.
    * Add Contact partner field
      CLEAR wa_scrfields.
      wa_scrfields-tabname = lc_but050.
      wa_scrfields-fieldname = lc_partner2.
      wa_scrfields-fieldtext = lc_contact.
      APPEND wa_scrfields TO git_scrfields.
    * Add Service Contract field
      CLEAR wa_scrfields.
      wa_scrfields-tabname = lc_dfkkcoh.
      wa_scrfields-fieldname = lc_servcont.
      wa_scrfields-fieldtext = lc_service.
      APPEND wa_scrfields TO git_scrfields.
    *Add Address Type field
      CLEAR wa_scrfields.
      wa_scrfields-tabname = lc_ztcrm_addrtyp.
      wa_scrfields-fieldname = lc_addr_typ.
      wa_scrfields-fieldtext = lc_address_type.
      APPEND wa_scrfields TO git_scrfields.
    * Add Letter Variant field
      CLEAR wa_scrfields.
      wa_scrfields-tabname = lc_ztcorr_code.
      wa_scrfields-fieldname = lc_letrvar.
      APPEND wa_scrfields TO git_scrfields.
      CALL FUNCTION 'POPUP_GET_VALUES'
        EXPORTING
          popup_title     = lc_title_welcome
          start_column    = lc_5
          start_row       = lc_5
        TABLES
          fields          = git_scrfields
        EXCEPTIONS
          error_in_fields = 0
          OTHERS          = 0.
      IF sy-subrc NE 0.
        EXIT.
      ENDIF.
    <b>Reward points if it helps.</b>

  • SAP -ISU PrintWorkBench

    Can some one help me with the procedure to use SAP-ISU Print WorkBench

    Hello,
    You need to attach application form for each and every Correspondence Type.
    Few of the Corr types are
    BL44 Outgoing Payment Confirmation
    BL45 Account Statement
    BL46 Capital Transfer Offer
    BL47 Payment Plan
    BL48 Rollover Offer
    BL49 Repayment
    BL50 Borrower Change Without Capital Transfe
    BL51 Deferral of Customer Loan
    BL52 Capitalization of Overdue Items CL
    BL53 Installment Plan Change CL
    BL54 Consumer Loan Confirmation
    BL55 Notice Given by Bank
    BL56 Rescind Credit Life Insurance
    BL57 Confirmation of Change
    BL58 Interest on Arrears Statement
    You can define them in IMG\FICA\Basic Functions\Correspondence\Define Correspondence types.
    <SAP provides lot of correspondence types. You have to copy them from client 000>
    After that you have to define application form for correspondence types in
    IMG\FICA\Basic Functions\Correspondence\Define Application Forms for Correspondence.
    You have to attach SAP defined correspondence forms.
    To trigger correspondence, you have to run FPCOPARA run mentioning relevant correspondence type.
    The data gets updated in table DFKKCOH.
    Do remember that apart from above config, there are various areas of correspondence config you need to do for different categories like Payments, Returns, Refunds , Dunning & Collection agency.
    For ex, for Returns, you attach  application form in Return reason codes, similarly for Dunning, you attach the application form in Dunning activites ...
    To view the list of Application forms, use T-Code EFRM
    Hope this helps
    Rgds
    Rajendra

  • Print WorkBench in ISU

    Can anyone send me the documents on print work bench.
    T.Code: EFRM.
    [email protected]
    Thanks

    Hi,
    The Print Workbench is the central development environment for creating standardized outgoing correspondence. To configure the correspondence forms, the Print Workbench uses the SAP standard components for configuring forms – SAPscript or Smart Forms.
    The Print Workbench is subdivided into the following subobjects:
    ·        Form classes
    Form classes are defined by SAP applications and contain a modeling as well as access instructions for all of the data that belongs to an application or an application process. You can use form classes to create application forms where you access the data defined in the form classes. Invoices, dunning notices, and account statements are examples of form classes. The form classes are delivered with each application component that use the Print Workbench. Changes to form classes delivered have modification status.
    ·        Application forms
    You create application forms based on the form classes delivered. You can define several application forms for each form class, for example, different invoices for different business partner groups. SAP delivers example forms that you can use as a reference for your own application forms. You can use user exits to adjust the application forms to your requirements. Numerous help functions simplify form creation.
    You can call up the Print Workbench via the area menu PWB.
    Integration
    The Print Workbench (CA-GTF-PWB) is a component of the Web Application Server (Release 6.20) and it can be used with no further prerequisites by every other SAP application. In the Print Workbench you can use Smart Forms (BC-SRV-SSF) and SAPscript (BC-SRV-SCR) alternatively.
    with regards,
    Sowjanya.Gosala.

  • SAP-ISU consultant details

    Hi friends, can any halp me to know SAP-ISU consultant details,
    what are all things i have in that SAP-ISU, whether it's having any programming part like ABAP,

    Hi ARUNKUMAR´,
    gas, water, elelctricity:
    All a mass business: Big numbers of customers, much bigger numbers of document items.
    Main focus is on (sub-module) FI-CA AKA RMCA, means contract acounting. Here you have an interesting kind of userexits: There are hundreds of pre-defined (and well documented) events. You can assign own FUNCTIONS to the events to enrich, change or check data.
    Billing, dunning and payment procedures processed in parralel; quite complex organization of the parrallel processing transactions.
    Alvaro is talking of the PRINT WORKBENCH which integrates the (SAPSCRIPT) forms handling and programming, but you can do a lot more with it.
    Also important/interesting is the customer master data organized using the SAP BUSINESS PARTNER model.
    This is ISU in short.
    Note: The main functions of IS-U are also used in Telecommunications (IS-T) and Media (IS-M).
    Regards,
    Clemens

  • Installation lock error while uploading meter readings in sap isu

    Hi,
    Following is the process followed:-
    Execute EL35 transaction to generate MRO Print in SAP ISU.
    at back end a process is triggered where Meter readings are fetched from a data server and uploaded in the sap isu using BAPI BAPI_MTRREADDOC_UPLOAD as a background process after a propogation delay of a minute after executing EL35.
    If the el35 requesting is closed the meter readings get uploaded.
    However if the transaction is kept open then we get an error that installation is locked.
    Please advice if there is a way to dequeue this lock while trigerring the EL35 transaction in first place..
    Regards,
    Sarvesh
    9920722958

    Hi,
    Message - 'Format of MR 17737 not valid (MR document number 105677 ) signifies that number of pre-decimal places and number of post decimal places do not match with your register group configuration.
    Since, you are suggesting that your logic works in most of the cases, I think when meter overflow happens and while you are converting it to actual read - this reading do not match with pre-decimal and post decimal places.
    You need to double click on register group for a device, where you are facing this issue and then compare your calculated read in your code.
    Hope this helps.
    Regards,
    Avinash

  • Creating Flat file in Print workbench.

    Hi,
       I have a query in Print workbench.
       I have to diable spooling and printing and I've to create a 'Flat file' instead.
       If anyone worked on this area or if anyone could suggest me some idea, it would be of great help to me.
    Thanks before-hand and Greetings,
    Sasi.

    Hi,
    Take a look at https://www.sdn.sap.com/sdn/weblogs.sdn?blog=/pub/wlg/1523. [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] It gives information on how to setup printer for file output. See if it helps.
    Regards

  • How to assign SmartForms to Application Forms for SAP ISU

    Hi Experts,
    We are going to use PWB for bill printing in SAP ISU.
    I have worked with ECC6.0 for PWB and seen that there is an option available to assign Smart Forms to the Application form in EFRM with selecting SmartForm option available in a dropddown. And for transaction EFCS creating FormClass the checkbox is available to make it usable for SmartForms.
    But we are using SAP R/3 4.6C. But these option i am not able to see in 4.6C.
    Can anyone guide how we can use and assign SmartForms for Release 4.6C.
    Thanks in advance.
    Ankur

    Thanks for the reply, but what about doing DML on other tables in other schemas. The DBA has created roles and granted permission to the user and they can do DML thru SQL plus without problem but when same operation is attempted thru Oracle forms ORA-40508 and object does not exist errors come up.
    How does a forms knows which tables in the database (under their own schema or on others to which they have been granted rights to) are availabel. Is there a property setting in the pallate or something in forms runtime which would recognize varoius users and then let them do DML on various tables under their or others's schema.
    Thanks in advance

  • About Print Workbench

    Hi guru's,
    I am implementing SAP LSO recently. I want to use the Print Workbench(Collections) to create an email with a Attachment(NOT PDF Format). How can I do that?
    for example:
    When learner book a course, system will send a email(with attachment in outlook appointment format) to him/her.
    I add two smartforms in the Collections, one is email content, the other is outlook appointment file content, I set the Attachment indicator in the outlook appointment file content smartform in the Collections, but when I received the email, the attachment is PDF format. How can I change the format of the attachment or is there any way to do so?(BADI?)
    Thank you!
    Tommy

    Hi
    in ecc6 the procedure adopted in efrm is as follows
    1.efrm t code
    type the application form name u wish 2 activate
    click enter
    in the next screen click activate button
    2.for creating a new form
    gv ur form name ex ZIS_U_WA_ORDER_DOWNLOAD
    and click in menu bar copy from client
    copy from 000 to ur client id
    and u can see in the next screen all forms and application forms created in new name starting with z...
    and save in english
    thats it in the ecc6 version
    differnece between sapcripts and smartforms are based on client depenedecies
    smartforms areclient dependent and sap scriots are clienct independent
    coloured logos can be made in smart forms not in sap scripts
    smart forms is always easier since it s the advanced of sapscript concept..
    foor more clear differnce contacta technical consultant near u
    in case if u  dnt  want the pdf format  try  for either sapscripts and smartforms for the same format u  want or prepare ur own in  them
    thanks ans regards
    raj

  • Print Workbench

    Hi guru's,
    I am implementing SAP LSO recently. I want to use the Print Workbench(Collections) to create an email with a Attachment(NOT PDF Format). How can I do that?
    for example:
    When learner book a course, system will send a email(with attachment in outlook appointment format) to him/her.
    I add two smartforms in the Collections, one is email content, the other is outlook appointment file content, I set the Attachment indicator in the outlook appointment file content smartform in the Collections, but when I received the email, the attachment is PDF format. How can I change the format of the attachment or is there any way to do so?(BADI?)
    Thank you!
    Tommy

    Hai,
    The Print Workbench is the central development environment for creating standardized outgoing correspondence. To configure the correspondence forms, the Print Workbench uses the SAP standard components for configuring forms – SAPscript or Smart Forms.
    These links also help you...
    http://help.sap.com/saphelp_nw04/helpdata/en/e4/a45a36998cf732e10000009b38f839/frameset.htm
    How I can use Print Workbench
    Regards,
    Srikanth.
    Reward points if helpful.

  • Sap ISU and CRM

    We are implementing SAP ISU with Billing and Invoicing, next step would be the implementation of CRM for Utilities.  In a part we are using the installation guide of Best Practices for Water Utilities, which presuppose the implementation of CRM. My question is the following: is it possible to do the implementation of billing and invoicing in ERP and afterwards move the billing and invoicing to CRM, without any big efforts?
    Thanks in advance
    Maja

    Maja,
    The IS-U billing engine sits in the SAP for Utilities system. Today, there is not such a thing in the CRM system you can use to do the same. Same it is for invoicing, bill print etc. not to speak of FI-CA. You can't even replicate these objects to CRM.
    The Water Template is not referring to such a thing. It is only levelling he way to a replication the standard objects, such as, business partner, from the ERP system to the CRM system.
    I hope this answers your question.
    Kind regards,
    Fritz

  • 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

  • Docs for Print workbench

    Hi,
    Can anyone provide me good docs for Print Workbench.
    Good docs will be rewarded with points.
    regards ,
    Vijay

    Hi
    Go thru this Link.
    http://www.sap.com/industries/media/pdf/FICAPWB_EN.pdf#search=%22Print%20Workbench%20in%20SAP%22
    Thanks
    Sunil

  • How to start Print Workbench

    Hi Group,
    I am new to print workbench,any body can provide some links or material to start learning print workbench.

    Hi,
    check online SAP help ..
    here it explained very well..
    http://help.sap.com/saphelp_nw04/helpdata/en/e4/a45a36998cf732e10000009b38f839/frameset.htm
    regards
    vijay

  • LSO RBC with Print Workbench

    Dear Expert,
    Can anyone share on any How-to-guide or blog which highlights step by step on how to create RBC correspondence for LSO, especially how the form and application classes are related and used in an Adobe Print Form / Smartform with the Print Workbench ? Thank you.
    Regards
    Kir Chern

    As always it is recommended that you search the SAP Help first then when you have specific questions you can post that.  Your question is so broad it is difficult to know where to start to answer it.
    Print Workbench is divided into the following subobjects:
    Form Classes
    Application Forms
    You can call up the Print Workbench via the area menu PWB.
    Form Class- containes the underlying data hierarchy for the application.  The attributes of a form class contain controlling information that is relevant for further processing in the Application Form.  (see example PWB_FLIGHT_NOTIFICATION).  Generally you use one of the standard SAP Form Classes but you can create your own. (Transaction EFCS).  Refer to SAP Help on creating Form Classes and Form Levels.
    Application Form -  Consists of properties/attributes, hierarchy, SAPscript/Smart Form, SAPscript text, User Exit Includes, Generated print program.  The hierarchy is determined by the assigned Form Class.  (Transaction EFRM)
    You create your SAPScript (or Smart Form) with the necessary windows.
    You may enter text directly in the SAPScript (if there are no variables) or you add the text to the appropriate form levels in the Application Form. 
    At each form level you are able to add user exits - before, during and after looping through the level.
    You can also add text exits for the text added.
    When you activate the Application Form a print program is generated.
    you create a print request which adds the record to the correspondence container (the transaction used depends on what correspondence you are creating) then you go to transaction FPCOPARA to print the correspondence.
    This is a high-level overview.  No quick answer to your question other than to once again refer you to the SAP Help.  Hopefully it gives you a place to start.

Maybe you are looking for

  • Is it possible that my update stats used only correct tables?

    Whenever there is a schedule maintenance run I receive a error: Executing the query "UPDATE STATISTICS [Perf].[PerfHourly_F65954CD35A54..." failed with the following error: "Table 'PerfHourly_F65954CD35A549E886A48E53F148F277' does not exist.". Possib

  • New Flash Player and GPU acceleration...

    Hy. I played this "example video" at 1080p (FF 3.6 and IE8): http://youtu.be/Ou6_MkIvKOo with flash build 10.2 I got => CPU load: 3%-11% for the whole video. ok. I was happy, because I have seen that GPU acceleration worked fine! now...with flash 10.

  • Corrupted catalog

    The last few times I've down loaded photos directly from my camera to LR I got a notice that said my catalog had been corrupted. I had backup catalog files but using these meant that all photo modifications and folders i had were lost and i had to do

  • I did not sign up for this account

    I have been charged for something I did not want. Please stop this account and and reverse the charges immediately.  Thank you 

  • Best 2015 AirPrint-capable monochrome laser printer(name brand, model) for flawless install and Wi-Fi connectivity?

    I currently use an HP LaserJet P1102w monochrome printer purchased in October, 2012. Cannot print from mobile devices because HP no longer supports the drivers needed for this. Instead, I must use their "HP app" to print from my iPhone 6. I can, howe