SAP Script Translation

Hi All,
Need help in SAP Script translation.
I have to change some hardcoded text from one language to another language.
I went to SE63 and changed the text, but the changes are not added into transport request.
Is there anyway to include the changes into the transport request? Please reply back...

Hi,
Other way would be to create a new request all together for the form. SE03----->Include object in tran req..Write click... execute. Click radiobutton Selected Objects. Add a new line at the bottim. FORM give form name in front of it. Tick the sequare box. F8. Click on Save in req.
Transport this request.
Reagards
Raju Chitale

Similar Messages

Transaction SE76 - SAP Script Translations

Hi All!
I'm working with Smart Forms (similar to SAP Script) and I have to make somne translations. Does somebody know how to use transaction SE76?
Thanks!
Ale.

this is for translate script to existing language to required language...
this u can also do in se71
se71-> enter form name & existing language name -> change
->utilities -> conver language...
i think...
Regards,
Ramesh

Text translation in sap-script

Hi
I am using sapscript for PO printing . I need to translate some texts in the PO depending upon the language . I have the translated text in all languages . How to go about it . putting condition on language would be a tedious job . Is there some better way to perform these translations .
Awaiting response . Would reward any sort of help .
Thanks

Instead Create A TExt Element and euate the text element to the corresponding field which u r transferring to the S. Script.
Suppose ur displaying : &VA_DESCRIPTION& in the SAP Script...
Then Do like this:
VA_DESCRIPTION = TEXT-001.
Now using TRANSLATION TOOL LOAD THE TEXT-001 for all useful languages with the description u already have...
Hope this is clear... For any query write back to me....
Lastly: Don't forget to give POINTS.. as we are putting extra efforts by seating late in office and trying to help u...
Darshan Patel

Translating for SAP Script in ECC 6.0

Hi All ,
How we can do the transalations for SAP Script in ECC6.0? . I was not able to do as we do in 4.7 version where we follow the following path
Translations -> Long texts -> forms .
Can any ody help me inthis regard ?
Thanks ,
Dharma .

Hi Anirban,
I tried that way . When I entered Scripti name in the filed " Object Name" , it is giving warning message "Object not found"( actaully it is existing ) . Even i tried to select by F4, No thing I Could find .Transactional area defaultred to 999999( tried wiht blank also) .
Can any body help for any alternative ?
Thanks ,
Dharma .

How can we make language translation in sap script?

Hi expert,
Based on language i have to display text in sap script form.
please i like to know how to maintain language translation in sap script.
manually i am handling the language text in print program.
like below.
if language = 'EN'
text in english.
endif.
if language = 'DE'
text in German.
endif.
good points will be given for proper answer.
Thanks and regards,
Pavan.

Hello there!
If those texts are static, you can use the following procedure (to translate your text elements):
Go to SE63, then in the menu follow this path:
Translation->ABAP Objects->Other Long Texts->FS (forms and styles)->FORM (Forms)
This will transport you for a screen where you can choose the script (Object -> field Object Name). Press Enter. If says object not found, it's because the source language is wrong (box below named translation -> field source language --- press F4 to change it)
After this, you'll navigate (after pressing Enter with correct language in source and choosing a correct one in target) to the transaltion screen. You'll have you text elements, original on top, your transalation below.
If those texts are dynamic, I believe you have to do the way you are doing.
Hope this helps.

Translations of SAP Script from English to Spanish

Hi All,
I need to do translate one of the SAP script from English to Spanish. Could anyone please help me how to achieve this?
Thank you in anticipation.

Hi Nikhil,
You can use transaction SE63 to do this: Translation->long Texts->SAPscript->Forms.
Regards,
John.

Translation in sap script

In my sap script, i am using a standard text. Now I need to maintain this standard text for 2 languages.
I have created two standard text with name name ZCPQM_INSPECTION_RESULT and maintained differerent values for language EN and FR in SO10.
In script, i have to write it as
INCLUDE ZCPQM_INSPECTION_RESULT OBJECT TEXT ID ST LANGUAGE &lv_langu&.
Now I am not sure wher eto declare the variable lv_langu. Please help

Hi Niti,
Do this way,
/: INCLUDE TESTTEXT OBJECT TEXT ID ST LANGUAGE &NAST-SPRAS&
this will include a SO10 Standard text "TESTTEXT" in the corresponding lagnuage in your form.
in SAP-Script you can not use statements like call funtion: edit_text, read_text, save_text, commit_text, delete_text.
to do so you need to jump off to an external perform like following:
/: Perform edit_text in program YSD_PERFORM
/: USING &NAST-SPRAS&
/: CHANGING &VARIABLE&
/: ENDPERFORM
Regards
Abhii...

How to print u0080 in SAP Script

Hi Experts,
   I have one small issue, i want to print symbol in sap script. If i puts this an hardcode vallue, but its not accepting this symbol.
Plz anyone guide this, how to display and print the above symbel in script.
This symbol is not available in displayable charactor area also.
Point will be sure.
Regards,
Mohana

Form to translate unicode symbol to superscript
you can use this in subroutine i think this may be usefull to you before that you need to select the radio button of super script in charecter format for that perticular format
FORM FORM_NAME TABLES inttab STRUCTURE itcsy
                           outtab STRUCTURE itcsy.
*Data Declaration.
DATA : V_TEXT1(320).
DATA: BEGIN OF ITAB OCCURS 0,
        WORD(40),
        END OF ITAB.
READ TABLE inttab INDEX 1.
V_TEXT1 = inttab-value.
REPLACE ALL OCCURRENCES OF '' IN V_TEXT1 WITH '<SP></>'.
READ TABLE outtab INDEX 1.
IF SY-SUBRC = 0.
    MOVE V_TEXT1 TO outtab-value.
    MODIFY outtab INDEX 1.
ENDIF.
ENDFORM

Not able to Export sap script with RSTXSCRP in different languages IT,ES

Hi all,
I am trying to export sap script to local file using this program RSTXSCRP, but it's working fine for English but not other languages like IT,ES and DA. Even if i specify parameter in selection screen Language vector as IT. It's not exporting code from sap script for IT language. By default it's exporting only EN.
Can you please tell me what I have to do to export sap script from different language.
Thank you.

Hi!
For Translating you can do it by
Going in transaction SE63 -> Translation -> Abap objects -> Other Long Texts -> FS Forms and Styles.
There you have to enter client and form name source lang. and target lang.
Then you export it with the program RSTXSCRP in the language u have translated....
As you have form created in English and you can download and upload it in only English .
Regards.

How can I convert Upper case word in Title case in Sap-Script

Hi All,
I have a text 'AAAAA BBBBB CCCCC' in sap-script.
I want to display it as 'Aaaa Bbbbb Ccccc'.

Hi,
Another way could be to call the FM <b>SWA_STRING_TO_UPPERCASE</b> from your sapscript for every string that you want in the desired format. It translates first character of each alphabetical substring to upper case. Set the input parameter <b>PRESERVE_EXISTING_CAPITALS</b> = SPACE, if your are receiving the values already in uppercase.
Hope this helps.
Regards
Message was edited by: Shehryar Khan

ABAP Subroutines in SAP Script forms

Hi Friends,
Can any give an example on using ABAP Subroutines in SAP Scripts
how to call ABAP subroutine IN FORM and how to define form statement in abap program
thanks in advance
Points for sure
Regards
Vijaya

Hi,
you have to write
perform formname in program zprogram
using &var1&
using &var2&
changing &var3&
endperform
in se38 create program zprogram of subroutine pool ttype
and
write the
form
endform there
egcode for a subroutne for changing the amount into indian words
PROGRAM ZFII_SR_PAYMNT_CHCK.
declaring the variables which are necessary
DATA:
G_AMOUNT       TYPE PC207-BETRG,          " having amount value
G_SPELL_AMOUNT(60) TYPE C, " LIKE     SPELL-WORD, " amount in words
G_SPELL_AMOUNT1(60) TYPE C,        " spell structure
G_WHTAX TYPE BSAK-QBSHB,   "
G_QBSHB TYPE BSAK-QBSHB, " FOR COLLECTING THE WITH HOLDING TAX
G_ZUMSK TYPE BSAK-ZUMSK.
*DECLARING THE INTERNAL TABLES FOR THE OUTPUT TO BE DISPLAYED.
TYPES : BEGIN OF T_INPUT_TABLE.
        INCLUDE STRUCTURE ITCSY.
TYPES : END OF T_INPUT_TABLE.
TYPES : BEGIN OF T_OUTPUT_TABLE.
        INCLUDE STRUCTURE ITCSY.
TYPES: END OF T_OUTPUT_TABLE.
DATA: GWA_INPUT_TABLE TYPE T_INPUT_TABLE.
DATA: GWA_OUTPUT_TABLE TYPE T_OUTPUT_TABLE.
DATA: GIT_INPUT_TABLE TYPE STANDARD TABLE OF T_INPUT_TABLE.
DATA: GIT_OUTPUT_TABLE TYPE STANDARD TABLE OF T_OUTPUT_TABLE.
TYPES : BEGIN OF T_ITEM,
          BUKRS TYPE BUKRS,
          BELNR TYPE BELNR_D,
          GJAHR TYPE GJAHR,
          WT_WITHCD TYPE WT_WITHCD,
          WT_QBSHB TYPE WT_WT1,
         END OF T_ITEM,
       IT_T_ITEM TYPE STANDARD TABLE OF T_ITEM.
DATA : GIT_ITEM TYPE IT_T_ITEM,
        GWA_ITEM TYPE T_ITEM.
GET_SPELL_AMOUNT
FORM GET_SPELL_AMOUNT TABLES INPUT STRUCTURE ITCSY
                               OUTPUT STRUCTURE ITCSY.      "#EC CALLED
CLEARING OFF THE VARIABLE USED IN PROGRAM.
CLEAR: G_AMOUNT,
           G_SPELL_AMOUNT.
*clearing the internal tables which we have used.
CLEAR:
   GIT_INPUT_TABLE,
   GIT_OUTPUT_TABLE.
*REFRESHING THE INTERNAL TABLES.
REFRESH:
   GIT_INPUT_TABLE,
   GIT_OUTPUT_TABLE.
*initially assigning the memory vaules to our internal tables.
GIT_INPUT_TABLE[] = INPUT[].
GIT_OUTPUT_TABLE[] = OUTPUT[].
*reading the table input to get the amount value.
READ TABLE GIT_INPUT_TABLE INTO GWA_INPUT_TABLE   INDEX 1.
IF GWA_INPUT_TABLE-VALUE CA 'X'.
    REPLACE ALL OCCURRENCES OF 'X' IN GWA_INPUT_TABLE-VALUE WITH '0'.
ENDIF.
*THIS IS IMPORTANT PART AS IT IS CONVERTING THE
*CHARACTER FIELD INTO CURRENCY FIELD.
SHIFT GWA_INPUT_TABLE-VALUE LEFT DELETING LEADING SPACE.
TRANSLATE GWA_INPUT_TABLE-VALUE USING ', '.
CONDENSE GWA_INPUT_TABLE-VALUE NO-GAPS.
G_AMOUNT = GWA_INPUT_TABLE-VALUE.
*calling the function moudle which will
*covert amount into words (indian format ).
*i.e in crores, lakhs, thousands
DATA: L_SPELLAMOUNT(255) TYPE C,
        L_ONLY(255) TYPE C.
CLEAR: L_SPELLAMOUNT, L_ONLY.
*here the amount should not be more than
99,99,99,999.99 . if it is greater than
*this amount this function module will not work
*so give the amount which is lessthan or equal to
*above said amount.
IF G_AMOUNT LT '1000000000'.
    CALL FUNCTION 'HR_IN_CHG_INR_WRDS'
      EXPORTING
        AMT_IN_NUM         = G_AMOUNT
      IMPORTING
        AMT_IN_WORDS       = L_SPELLAMOUNT
      EXCEPTIONS
        DATA_TYPE_MISMATCH = 1
        OTHERS             = 2.
    IF SY-SUBRC <> 0.
      MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
              WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
ENDIF.
CONDENSE L_SPELLAMOUNT.
TRANSLATE L_SPELLAMOUNT TO UPPER CASE.
CONCATENATE L_SPELLAMOUNT 'ONLY' INTO L_ONLY SEPARATED BY SPACE.
*moivng the field name into table field.
GWA_OUTPUT_TABLE-NAME = 'G_SPELL_AMOUNT'.
*assigning the amount in words to the variable.
*the reason behind splitting the word into two parts
*is--- in the scripts the whole string is not getting
*printed. So we are splitting it into two parts so that
*it will print the whole string.
G_SPELL_AMOUNT = L_ONLY+0(60).
G_SPELL_AMOUNT1 = L_ONLY+60(60).
G_SPELL_AMOUNT = L_SPELLAMOUNT.
*MOVING THE AMOUNT IN WORDS TO FINAL WORK AREA.
MOVE G_SPELL_AMOUNT TO GWA_OUTPUT_TABLE-VALUE.
*MODIFYING THE INTERNAL TABLE FORM THE WORK AREA.
MODIFY GIT_OUTPUT_TABLE FROM GWA_OUTPUT_TABLE INDEX 1.
*FOR THE SECOND RECORD I.E FOR THE NEXT 60characters
GWA_OUTPUT_TABLE-NAME = 'G_SPELL_AMOUNT1'.
MOVE G_SPELL_AMOUNT1 TO GWA_OUTPUT_TABLE-VALUE.
MODIFY GIT_OUTPUT_TABLE FROM GWA_OUTPUT_TABLE INDEX 2.
*assigning the total output table to the memory .
OUTPUT[] = GIT_OUTPUT_TABLE[].
ENDFORM.                    "GET_COMPADDR
thanks & regards,
Venkatesh

SAP Script : Can"t create / Display / Copy Elements in EN language... Urgen

Dear All,
I am working in a Script, I copied a standard Script and tried to Create a new Window but it is not allowing me.
I realised that, I can"t create a new window in English Version, I can do that only in German version.
I feel it is cubersome that every time I have to log into German to do any editing. So Can you guys kidly let me know how can I do editing in English version.
I have tried to Change Original Language into English from utilities -> Convert original language but that Field is Grey (Blanked out. So could not do that.
I even tried to create new window in DE language, but when I tried to logon to English, it say form in English Language is Locked.
Plese advice me .. this is urgent, without this information, I cann"t even start ... Should I contact with my Basis Consultant.
Thanking you.
Regards
Venkat
Thanking you.
Regards
Venkat.

Hi there,
the alst answer you got in your previous thread
SAP Script : Editing in EN Version / DE version : Urgent pls
was correct. But you really have to login in language DE first. If you do that, the translation option is enabled. After that follow the instructions again.
try...it wil work
chrs
Hayo

SAP script printout

Hi,
I have got the output from my sap script.
I want to send the output as a mail to the concerned person.
In menu there is a send mail options but it is disabled.
How to send this SAP script output in a mail (either PDF or the same as output format.

step1:
use the FM CONVERT_OTF to convert otf to pdf.
step 2:
use the folowing code to convert the PDF to a required format and to move the exact content in g_objbin and g_objpack
LOOP AT t_line.
    TRANSLATE t_line USING ' ~'.
   CONCATENATE g_buffer t_line INTO g_buffer.
ENDLOOP.
TRANSLATE g_buffer USING '~ '.
DO.
   g_message1 = g_buffer.
   APPEND g_message1.
SHIFT g_buffer LEFT BY 255 PLACES.
   IF g_buffer IS INITIAL.
    EXIT.
ENDIF.
ENDDO.
g_objbin [] = g_message1 [] .
DESCRIBE TABLE g_objbin LINES g_lines_bin.
READ TABLE g_objbin INDEX g_lines_bin.
g_objpack-transf_bin = 'X'.
g_objpack-head_start = 1.
g_objpack-head_num = 0.
g_objpack-body_start = 1.
g_objpack-doc_size = ( g_lines_bin - 1 ) * 255 + STRLEN( g_objbin ).
g_objpack-body_num = g_lines_bin.
g_objpack-doc_type ='PDF'.
g_objpack-obj_name = text-009.
APPEND g_objpack.
step 3:
use teh following code to attach the content in mail and send it to a recevier
g_reclist-rec_type = 'F'.
g_reclist-fax = l_faxno.
g_reclist-country = 'USA'.
APPEND g_reclist.
CALL FUNCTION 'SO_DOCUMENT_SEND_API1'
    EXPORTING
      document_data           = wa_doc_chng
      put_in_outbox           = 'X'
      commit_work             = 'X'
    TABLES
      packing_list            = g_objpack
      contents_bin            = g_objbin
      contents_txt            = g_objtxt
      receivers               = g_reclist
    EXCEPTIONS
      too_many_receivers      = 1
      document_not_sent       = 2
      document_type_not_exist = 3.
let me know if you need any more help
Edited by: jeevitha krishnaraj on Jul 7, 2009 9:35 AM

How to transport the sap script

Hi gurus,
I am new to the SAP scripts. I finished the development of my form by usiing SAP Scripts. How can I transport it? Any help is appreciated!
Thx in advance!
Kun Bao

check these links it will be very useful...
How to transport SAPSCRIPT??
SMARTFORMS translate and transport
SAP Scripts are client-dependent objects. Hence, they may often require to be downloaded from or uploaded to SAP system
Following programs can be used to download from/upload to SAP System
RSTXR3TR To EXPORT/IMPORT layout set (FORM) using a Transport Request (CTS)
RSTXSCRP To EXPORT/IMPORT layout set (FORM), Style, Standard Text or Device Type without using a Transport Request
execute the Program 'RSTXSCRP' give the Script name and Export it to u'r system and then log on in different client and Import the script using the same Program.
reward all help full answers.

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  Word processing  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 SAPs 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 Systems 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  Word processing  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  Word processing  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

SAP Script Translation

Similar Messages

Maybe you are looking for