# appearing in standard text.

Hello,
I have created a standard text and using the text in a smartform. There are many words with apostrope in them. For eg consumer's. But when it is printed in the smartform , the text is printed as consumer#s. Other standard texts which contains words with apostrope are printing correctly in the smartform. I have compared properties of both the standard texts and they are same. No styles have been used in either case. But , only in one case the "#" symbol is being printed instead of the apostrophe.
Can you please suggest what might be the issue?
Thanks and Regards,
Laxman Pai.

Hi laxman,
MODIFY <dbtab> FROM TABLE <itab>.
Regards,
Clemens
Ooops, sorry, wrong thread! (related to [Modify ztable from internal table|Modify ztable from internal table])
Edited by: Clemens Li on Jan 17, 2011 1:23 PM

Similar Messages

How can I have a standard text block appear on the last page of my documents?

How can I have a standard text block appear on the last page of my documents without having to type it in all the time? I have a terms statement with a line for a customer’s signature which I want on the last page of my invoices and right now I have to type it in each time or cut and paste it from a previous invoice. I already have a Master Page that includes the customer information and my company information at the top of each page and I am using data merge to fill each page with the items ordered and their pictures etc. I would just like to have this standard terms block automatically show up on the last page after the last item in the data merge.
Thank you all in advance for your help.

Thank you Peter. This works. I have the text block now at the bottom of a second master page which I apply to the last page. For aesthetics I can modify the position of the text block in the new master page to bring it up from the bottom under the last item ordered when there is less than 4 items on the page. (my data merge fits up to 4 items with their images on a page). If the last page is full I’ll insert a final page using the second master and also bring it up to the top of the page.

Translation of standard texts that appear in applications

Hi Experts,
I am building my webdynpro applications in a Language in which translations are not provided by SAP but it supports the language in Unicode.
My issue is that when I am running the application, the standard texts like 'Please Wait' while loading the page and 'Messages' in message area are all coming in German. So if you have an idea from where these texts are maintained so that I can maintain the translations.
Thanks in advance,
Saurabh

Hi Saurav,
My problem is that suppose I am running the application in a language for which translations are provided by SAP like German & English then these standard texts appear as desired in those languages.
But if i run my application for languages like Hindi suppose for which SAP do not provide any translations then these std texts appear in German.
Thanks,
Saurabh

Sapscript and Standard Text - Polish Characters not printing

Hi,
I have created an English Sapscript and translated it to Polish via transaction SE76.
Changing my PC Region and Language settings to Polish allowed me to enter Polish Characters into Hardcoded text in the Sapscript and Standard Text via s010.
I have two problems:
1) With my PC Region and Language settings set to Polish, when I create my sapscript output some of the polish characters that I have entered via SE76 and SO10 do not appear and are replaced by others e.g.
ę is dispalyed as ê
ć is displayed as æ
ń is displazed as #
2) I have a business requirement to be in England Logged with PC Region and Language set to English but to print a sapscript output in Polish. Is this possible.
We are currently on non unicode SAP system.
Please can anyone advise.
Regards

Hello,
SAP discourages mixed code page or MDMP systems and with good reason. If there is any possibility of you upgrading to a Unicode system in the near future you should try to wait for it. Supporting multiple languages in Unicode is easy, in MDMP it can be quite tricky. And MDMP makes the move to Unicode more difficult.
That said, your BASIS team can enable Polish and you can print in Polish while your PC is set for English. The SAPScript/Form must be in Polish or using an INCLUDE that is LANGUAGE 'PL' to let SAP know which code page to use when printing.
Seriously, look at moving to Unicode, you need to do it eventually anyways.
Michael

Standard text in SO defined as bold doesn't come out bold in smartform

Hi Gurus,
I have created a standard text in SO10 transaction and I have given to it the characteristic highlighted (bold) the test effectively appears as bold while in SO10.
However when I call this standard text in a smartform (which is treated to be edited as a spool in a subsequent step), my so-called text does not show up with the highlited chatacteristic specified on the spool printout.
Can anyone tell me how I could solve this ?
helpful hints will be rewarded,
Many thanks;
Cedric

Hi,
In case of smartform,
create a style with bold and then use it in smartform.
revertback if queries
regards
jansi

Difference jb/w text symblosin script and standard text in scripts

hi to all
can u pols explain about the
difference b/w text symblos in script and standard text in scripts

hi
Default paragraph Paragraph set to * in standard text maintenance
If no form has been assigned to a text, the system automatically assigns the form SYSTEM, which contains minimal definitions for text formatting. There are two ways of formatting texts using forms: Use the standard text maintenance to enter and print the text.
Any kind of text can be included in a form. If no object is specified, then TEXT will be used (standard texts).

Text Symbols
Text symbols acquire their values as a result of explicit assignment. To interactively assign text symbols, in the text editor choose Include  Symbols  Text. This method is available for all text symbols belonging to a text module as well as those of the associated form. Values defined in this way are lost when the transaction is left. If you want to print the text module again, then you must enter the symbol values again. The purpose of the DEFINE command is to provide a means of making this value assignment a permanent part of the text, so that the values are available again when the text module is called again. This command can also be used to re-assign a new value to a text symbol half-way through the text. Syntax: /: DEFINE &symbol_name& = 'value'
/: DEFINE &subject& = 'Your letter of 7/3/95' The value assigned can have a maximal length of 60 characters. It may itself contain other symbols. A symbol contained within the value assigned to another symbol is not replaced with its own value at the point at which the DEFINE command is executed. Rather, this replacement is made when the symbol defined in the DEFINE command is called in the text.
/: DEFINE &symbol1& = 'mail' /: DEFINE &symbol2& = 'SAP&symbol1&' /: DEFINE &symbol1& = 'script' &symbol2& -> SAPscript If, however, the DEFINE command is written using the ':=' character rather than the '=' character, then any symbol contained within the value being assigned is replaced immediately with its current value. The assignment to the target symbol is made only after all symbols in the value string are replaced with their values. The total length of the value string may not exceed 80 characters. The target symbol must be a text symbol, as before.
/: DEFINE &symbol1& = 'mail' /: DEFINE &symbol2& := 'SAP&symbol1&' /: DEFINE &symbol1& = 'script' &symbol2& -> SAPmail
Inserting Text Symbols
Procedure
Inserting a Text Symbol
1. Choose Insert → Symbols → Text.
2. Place the cursor on the desired text symbol.
3. Choose Choose.
4. The system inserts the text symbol.
Editing the Value of a Text Symbol
1. Choose Insert → Symbols → Text.
2. Choose Edit value bearbeiten. The dialog window Value definition for symbol <text symbol> appears.
3. Enter the appropriate value definition.
4. Choose Continue. In the dialog window Text symbols the specified value appears after the name of the text symbol.
5. Choose Continue.
Deleting all Text Symbol Values
1. Choose Insert → Symbols → Text.
2. Choose Delete all values. The system deletes all defined values.
3. Choose Continue.
Using Formatting Options for Text Symbols
1. Choose Insert → Symbols → Text.
2. Choose Options. The dialog window Formatting options for <text symbol> appears.
3. Fill in the fields.
4. Choose Continue.
5. Choose Continue. The system executes the selected formatting option.
regards
ravish
plz reward points if helpful

Standard Text in 2 adjacent windows of a Script

Hi,
I am Calling 2 separate standard texts in 2 adjacent windows in LAST page.
2 standard texts comprises 3 pages of text.
I am calling the LAST page in MAIN WINDOW using the command
/: NEW-PAGE LAST
When i execute the program, only page of the text is appear at the LAST page.
Rest 2 page texts are not appearing.
What could be the problem? Please help me out.
Thanks,
DhanaLakshmi M S

hi,
try this.
In the driver program ,
CALL FUNCTION 'CONTROL_FORM'
EXPORTING
 COMMAND = 'NEW-PAGE LAST'
EXCEPTIONS
UNOPENED = 1
UNSTARTED = 2
OTHERS = 3
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.

How to Change behavior of standard text object&text ID (SE75)?

Hello there!!
I'm struggling with this:
For standard text object C_SHES_ACH & ID 0001 (EHS: IHS Safety Measures) wichs is used as a description for safety measures (CBIH82/CBIH02..) need that when the user create or edit the text, already appears a "Fill in the blanks" form.
For example, in CBIH82, editing an accident log, I go to Safety measures Button, then create a safety meassure, and when i click for long text description something like this should appear:
TEXT 1 (1st Title)
user line
user line
user line
user line
(free amount of user lines)
TEXT 2 (2nd Title)
user line
user line
user line
user line
(free amount of user lines)
Thanks a lot for your feedback!
Rgds!!

Hii,
I am unable to understand exactly wat you want.
But for free amount of lines : Keep that text under LOOP. Right click on template or window and create a loop and under that loop keep the text ,you can get many lines. or the given below point plzz follow.
1,Use SO10 Tcode to write standard text in Smartform.
2.For long text
method1
Create TEXT node- general attributes change text type to include text
then you can input text name/text object/text id/language
method2
create PROGRAM LINE node - use FM READ_TEXT to read it to a internal table
then use LOOP or TABLE node to display it
For TEXT module(For foreign language)
Tr-code:smartforms -- choose Text module(not choose form)--create a text module object
then enter smartform Create TEXT node- general attributes change text type to text module
input the text module name which created by above
3.
1. take function module name of the smartform.
2. goto se37 and type that fm name.
3. goto attributes tab
4. double click on either program or include .
5. There u can find all the subroutines used inside smartform.
6. search for "perform %move using %textkey-name".
4.Standard Texts are created in SO10 Tcode and stored in STXH table with OBject ,ID and NAME parameters. We can use Read_Text FM to read the text.
check the tables STXH & STXL.
5.
How to CAll Standard Text in Smart Forms
In SFs you can insert the standard tests using the TEXT node. Create a TEXT NODE. Then in the GENERAL ATTRIBUTES of this TEXT node select INCLUDE TEXT in the TYPE option. Then you have to enter the text name, object , ID and language in the provided fields. Then if you dont want any error if there is no text in the corresponding text then CHECK the check box "No errors if no text available.

How can I initiate a transport of Standard Text over to another client

HI,
I need to re-create all the customized standard text in our new ECC6.0 box. Afte creation, I want to transport it to the QA for testing and eventually to the new ECC 6.0 production.
While creating the text, it does not trigger any transport request.
How can I initiate the Transport request?
I had explored and found that it is also possible to upload to the destination. I would prefer the Transport method.
Can someone advice?
Thanks
Thanks

The program name is RSTXTRAN. run from SE38
detailed documentation is here.
Symptom
This is a brief guide to RSTXTRAN
More Terms
RSTXTRAN, Transport of SAPscript Texts, Standard Texts
Cause and Prerequisites
Solution
Basic Background
You want to transport SAPscript Texts from a source system to the target
system. You can do it in different ways. If you want to copy texts within a
system from one client to the other you can execute the report RSTXTCPY. In
other cases, i.e. transporting the texts between the different systems, you
can use the report RSTXTRAN. This report (RSTXTRAN) itself does not perform
any transporting but is used to prepare a Transport Task (TT). Having
prepared the TT with RSTXTRAN you have then to release it and the
corresponding Transport Request (TR) in a normal way (e.g. with an
assistance of Customizing Organizer - se10).
Please note the Type of Transport Requests (WBO or Customizing) depends on
the system settings.
Working with RSTXTRAN
1. Execute the report RSTXTRAN (e.g. within the transaction se38)
2. On the selection screen appeared you may specify:
2.1. Name of the Transport Task (TT). Make sure you specify the
Transport TASK number, NOT the Transport REQUEST ! You may leave this
field empty if you did not create to this moment the appropriate TT.
Later you will be able to create it within the report.
2.2. Text Key. This composite key consists of four fields: Object,
Name, Id and Language. You may specify these fields also generic
(caution: until Rel.4.6A you have to specify \'*\' if you need a generic
selection; leaving a field empty will cause a search for the blank
field that usually returns no results!). This key serves as
preliminary search restriction only and does NOT mean all the texts
which satisfied the specified key must be included into TT.
3. Having specified some fields on the selection screen you can go
further with \'Execute\'(F8).
4. On the screen appeared you will see the list of texts that satisfy the
specified restrictions. By default all the texts are selected for
including in the TT. You can deselect all the texts or select all of
them again using the function \'deselect all\' or \'select all\'
respectfully. Certainly you may select the texts individually as well.
In order to proceed you have to use function code \'continue\' clicking
on the icon \'OK\' or pressing the button \'ENTER\'.
5. At this stage you get another list of texts that already exactly
defines the list of texts to be included in a Transport Task. You
cannot change this list any more. If you want to change something (add
new texts or exclude any of them) you have to go one step back (F3)
and update your selection. You can now include this list to the TT by
pressing the button in the toolbar \'Transfer texts to correction
request\' and confirming the action.
6. If you have left the field \'Name of Correction\' empty on the first
selection screen you will then be asked to provide the Transport
Request number. You can select it from already existed ones or create
a new one. However if you specify anything(!) in the field \'Name of
correction\' on the first selection screen and the specified TT does
NOT exist (generic input is not allowed there) you will get an error
message \'Request/Task xxx does not exist\' (TR 806). In that case
please go to the first screen and fill out this field correctly, or
leave it completely empty. Then repeat the selection again.
7. When you have performed all the steps properly you get a message the
selected texts were included into TT. Now you can leave the report and
release the appropriate Transport Task/Request in Customizing
Organizer (se10).
Edited by: Henry Hsu on Nov 27, 2010 3:37 AM

SAPScript: how tu adjust heigh and width of standard text (logo)?

Hi!
how to adjust heigh and width of standard text (logo)?
I do not want to edit the logo, because it is used elsewhere, so I need to adjust heigh and width when using it in a form.
For now stadard text comes over the window. Here is how I use it:
INCLUDE ZHEX-LOGO OBJECT TEXT ID ST
Will reward,
Mindaugas

Hi Mindaugas,
While uploading using RSTXLDMC. You have to maintain your size of the logo.
Go through below mentioned document.
Upload TIFF files to SAPscript texts
Description
The report RSTXLDMC allows a TIFF graphics file to be uploaded from the file system of the R/3 GUI to a standard text in the R/3 word processor SAPscript. (TIFF is a registered trademark of the Aldus Corporation.)
When uploading, the TIFF graphic is converted either into a black and white raster image (parameter type=BMON ) or as a color raster image with a maximum of 256 colors (parameter type=BCOL).
The black and white raster images ( BMON) can be printed using the following printer types:
PCL-5 printer
PostScript printer
Kyocera PRESCRIBE printer
Device type SAPWIN (with SAPlpd 32-bit as of Version 2.41 for Windows NT or Windows 95)
The color raster images (BCOL) can be printed using the following printer types:
PCL-5 printer with color capability (e.g. HP Color LaserJet). Color graphics are not printed properly on monochrome PCL-5 printers (e.g. HP LaserJet 5), because the printer cannot set the color palette as required and does not perform any gray-level conversion.
PostScript printer (color graphics are automatically converted to gray levels on black and white printers using PostScript) Device type SAPWIN (with SAPlpd 32-bit as of Version 2.41 for Windows NT or Windows 95) During TIFF graphic import, the basic set " Baseline TIFF 6.0 " of the TIFF specification 6.0 is supported.
To maintain compatibility with earlier versions of the report RSTXLDMC, it is also possible to convert the TIFF graphic directly into a black and white raster image for a particular printer type when uploading. These are the three printer types PCL-5 (parameter type=PCL ), PostScript (parameter type=POST) and Kyocera PRESCRIBE (parameter type=PRES ). A raster image uploaded in this manner can only be printed using the appropriate printer type.
Besides TIFF raster graphics, direct printer commands in the respective printer language (PCL-5, PostScript or Prescribe) can also be contained in the file which is to be uploaded (printer macros). They are then transferred to the standard text unmodified.
The graphics are output by inserting the standard text into the document which is to be printed, directly or using an INCLUDE command. The printer commands, which for example draw a company logo on the page, are only output if the print request is processed by the printer driver corresponding to the macro type, otherwise they are ignored. Example: A macro of type PCL is contained in a print request. If the request is output to a printer with type HPLJIIID (to which the driver HPL2 is assigned), the macro data is sent to the printer. If the request is printed on a printer of type POSTSCPT (to which the driver POST is assigned), the output of the macro data is suppressed.
In the standard text, the printer commands are inserted between the HEX ... ENDHEX command lines in hex notation. Various report parameters allow the graphic or printer macro to be placed on the page or at the current text position. Note: When the /:HEX command line which precedes the macro appears in the text, a line break is generally made before the graphic is output. The output of the macro therefore begins in the next text line at the left window border of the current page window, as long as a shift to the right is not specified (see below).
If your own printer macros are uploaded and not TIFF files, you must ensure yourself that the normal (text) output of the driver is not impaired when the printer commands are inserted in the output from the uploaded file. The printer drivers pass the data contained in the file to the printer unmodified, therefore without control over the individual actions this triggers on the printer. For example, syntax errors should not be generated by the PostScript commands (type POST), or form feeds should not be contained in the file (unless this was intended) for PCL-5 (type PCL).
Restrictions:
In general, the output of graphics generated via RSTXLDMC from R/3 is not suitable for mass printing (that is, unless you are using the "Graphic resident on printer" feature): the R/3 spooler has to hold significantly more data in its output files. If the graphics occur several times in a spool request, the data also reoccurs. Apart from this, the network is more heavily loaded in sending the increased volume of data to the printer and the printer output is slowed significantly (varies according to printer model) if raster graphics are output as well as the text.
If your graphics reside on your printer during a printing job, the degree of 'correctness' with which they are printed depends on the amount of memory available in your printer. R/3 print drivers are unable to determine whether the amount of memory available is enough! If one of the graphics that you have marked as resident is not displayed, try reloading the graphic and switching off the parameter "Graphic resident on printer".
When printing black and white graphics on PCL-5 printers, image data is compressed in order to greatly reduce the file size.
The output of graphics and macros on PCL-5 printers, PostScript printers and device type SAPWIN (type BMON, BCOL, PCL, POST) is adapted to the page orientation used, that is if landscape is used instead of portrait, the graphic is also turned when output. This is not the case for the PRESCRIBE printers (type BMON, PRES)! With these printers, the graphic is not automatically turned when landscape is used, but appears on the page in the identical position as for portrait. You are therefore recommended not to output raster images when printing in landscape on PRESCRIBE printers.
PRESCRIBE printers do not support the resolutions 200 and 600 dots per inch when printing raster images.
Not all PCL-5 compatible printers support the resolutions 200 and 600 dots per inch when printing raster images.
TIFF graphics with compression type 2 ("CCITT Group 3 1-Dimensional Modified Huffman run length encoding ") can currently not be imported although this is a component of the Baseline TIFF 6.0 specification for monochrome images.
Color TIFF graphics with full color representation (ie. a lot more than 256 colors) are automatically converted into 256 gray levels when uploading with type BCOL.
When TIFF graphics are converted to black and white raster images (type BMON, PCL, POST, PRES) there is no default simulation of gray levels or colors of the original image on the printer (for example, by using different tones of gray). Each pixel of the original image is converted to a white or black pixel on the printer according to its intensity value.
The parameter "Number of TIFF gray levels" does, however, allow a simulation of gray/colour tones of the original image through levels of gray on the printer, when using type PCL, POST or PRES. This parameter is ignored for type BMON.
The conversion of TIFF graphics can be so time-consuming that it is recommendable to execute the report RSTXLDMC in batch processing. Note: in batch, the file is always read from the file system of the application server (ie. not from the file system of the GUI).
The length of an individual text in the text file is limited. When importing TIFF graphics with very large dimensions, especially if more than 2 gray levels are used, a termination can therefore occur when saving the standard text ("EXPORT_TOO_MUCH_DATA"). This restriction can only be avoided by reducing the TIFF graphics. Note: The display of a raster image in Postscript or PRESCRIBE format needs from two to three times as much space as displaying in PCL-5.
When processing very large TIFF images on PostScript printers, a print termination can occur with PS error message "limitcheck". In this case the internal memory of the printer is insufficient to scale the required raster image. This implementation limit cannot be influenced by changing the report parameters when importing.
Requirement
The file which is to be uploaded can contain the following formats/ commands:
Baseline TIFF 6.0 raster image files. The image information of the TIFF file is converted into black and white/color raster images when uploading. Note: As the TIFF format allows a variety of variants, only a basic set of TIFF 6.0 formats is supported here described in the TIFF 6.0 specification as Baseline TIFF 6.0.
PCL : PCL-5, Hewlett Packard Printer Control Language 5 for HP LaserJet 3, 4, 5 series and compatible printers. The data is output by the printer driver HPL2 only.
PRES: Kyocera PRESCRIBE for Kyocera laser printers. The data is output by the printer driver PRES only.
POST: Adobe PostScript or EPS format (encapsulated PostScript ) for PostScript printers. The data is output by the printer driver POST only. In the upload, one of the end-of-file markers (CTRL-D, hex $04) which may be contained in the PostScript file is not transferred.
For PostScript files which contain a bounding box entry (for example, all EPS files) the macro/graphic can be scaled to a size specified by the user. In this case, a small lead text and trailer are generated by the report for the macro data and inserted in the standard text.
Parameters of RSTXLDMC
File name
Path and file name of the file to be uploaded in the file system of the R/3 frontend (dialog processing) or in the file system of the application server (batch processing)
Type
Way which the data contained in the file is to be converted. Possible values are BMON, BCOL, PCL, POST and PRES. With parameter values BMON and BCOL, a TIFF 6.0 file is expected. This is converted into either a black and white raster image (BMON) or a color raster image (BCOL). These raster images are printer-independent and can be printed using various printer types (see above).
With parameter values PCL, POST and PRES, either a TIFF 6.0 file or a file with printer commands in the appropriate printer langauge is expected. If the file is a TIFF file, it is converted into a black and white raster image for the printer type specified in the parameter. The presence of a TIFF file is recognized automatically. If the file is not a TIFF file, the file contents are regarded as the printer macro of the respective type. Data loaded with type PCL, POST or PRES can only be printed on the respective printer type.
Resolution for TIFF raster images
Resolution which should be used when importing a TIFF raster image, in dots per inch (dpi). If an allowed value is entered here, this overrides the resolution information in the TIFF file. The allowed values are:
75 dpi
100 dpi
150 dpi
200 dpi (not for type PRES, for PCL only HP LaserJet 4,5 series)
300 dpi
600 dpi (not for type PRES, for PCL only HP LaserJet 4,5 series)
Changing the resolution affects the size of the graphic on the printer. If a resolution of 300 dpi is stated in the TIFF file and this parameter is set to 75 dpi, the graphic is four times as big when printed as at the outset.
Note: Kyocera PRESCRIBE printers do not support 200 and 600 dpi resolutions.
Note: Not all PCL-5 printers support resolutions 200 and 600 dpi, for example HP LaserJet 3 series does not, but LaserJet 4 and 5 series do.
Graphic Resident on Printer
Normally, graphics that occur more than once in a printing job (a company logo that appears on each page, for example) are sent to the printer repeatedly each time they are needed. In order to avoid this kind of redundancy, you can select this checkbox on the selection screen. The R/3 print driver then stores the graphic in the printer's memory and the printer retrieves the 'resident' graphic memory every time that re-occurs in your job.
Caution: Whether or not the printer correctly reproduces the graphic depends on the amount of memory available in the printer during the printing job! You should avoid using this feature with color graphics since they take up a lot more memory than monochrome graphics.
This parameter can only be used with types "BMON" and "BCOL".
Absolute positioning
Determines whether the macro/graphic is positioned absolutely or is to be output at the current text position. If this checkbox is selected, the graphic is positioned absolutely (parameters "X-position" and "Y-position" are used), if this checkbox is not selected, the graphic is positioned at the current text position (parameters "Reserved height" and "Shift to right" are used)
Absolute X-position
Horizontal position (space from left border) of the macro/graphic, if absolute positioning is required. This is the parameter XPOS of the HEX command.
Absolute Y-position
Vertical position (space from upper border) of the macro/graphic, if absolute positioning is required. This is the parameter YPOS of the HEX command.
Reserve height automatically
If this checkbox is selected, the system automatically inserts the actual height of the graphic during printing into the subsequent "Reserved height" parameter.
Reserved height
If positioned at the current text position, this parameter specifies the horizontal spacing to be reserved for the macro/graphic, which must not be printed with text from the paragraph. This is the parameter HEIGHT of the HEX command.
Shift to right
If positioned at the current text position, this parameter specifies the space between the left border of the macro/graphic and the left border of the page window. If this value is increased, the macro/graphic is shifted to the right. This is the parameter LEFT of the HEX command.
Unit of measurement for positioning
The unit of measurement in which the position values (X,Y, height, shift) are specified. Possible values are CM (centimeters), MM (millimeters), IN (inches), PT (typographic point = 1/72 inch), TW (1/20 point = 1/1440 inch)
Text title
Comment used for the attribute "Title" of the standard text generated as well as as a comment line in the text itself
Line width
Number of columns to be used in the standard text when generating the HEX...ENDHEX command lines. The default value is 132
Text name
Name of the standard text to be generated. If an * character occurs in the name, it is replaced by the value of the parameter "Printer type". For example, if the entry is ZHEX-IMAGE1-* and the printer type = PCL, the text name ZHEX-IMAGE1-PCL is generated. The default value for the name is ZHEX-MACRO-<printer type>, but the standard text can be named as required (take into account customer reserve). Standard texts are client-dependent!
Note: The name of a standard text can be up to 32 characters long !
Text ID
ID of the standard text to be generated. The default value is ST (general standard texts)
Text language
Language key of the standard text to be generated. The default value is the logon language
PostScript scaling
Flag which determines how the macros/graphics of type POST are handled. If set to 'X', the report expects a PostScript comment line in the file
%%BoundingBox llx lly urx ury (e.g. %%BoundingBox -1.5 0 21.4 14.1)
as present, for example, in all EPS files, in which the dimensions and the position of the macro/graphic are specified (if a bounding box comment is not included, 0 0 1 1 is assumed as the default value). This information is then used by the report to insert PostScript commands which scale the macro/graphic to the size specified in the parameters "Width" and "Height" (listed below).
If the flag is set to ' ' (blank), the PostScript file is transferred to the standard text without any additions (any transformations to the coordinate system used by the printer driver must already be contained in the file).
The flag must be set to 'X' for the import of TIFF files for type POST.
Width according to PS scaling
Required width of the macro/graphic if the flag PostScript scaling is set. Can remain at zero for the import of TIFF files, the size is then determined by the resolution of the graphic.
Height according to PS scaling
Required height of the macro/graphic if the flag PostScript scaling is set. Can remain at zero for the import of TIFF files, the size is then determined by the resolution of the graphic.
If you want to scale the PostScript graphic with these parameters, one of the two values, width or height, can be specified with zero. The graphic is then scaled so that the width-to-height ratio remains unchanged and the original graphic is not distorted.
Unit of measurement for PS scaling
Unit of measurement in which the parameters "Width" and "Height" are specified. Possible values are CM (centimeters), MM (millimeters), IN (inches), PT (typographic point = 1/72 inch), TW (1/20 point = 1/1440 inch)
Number of TIFF gray levels
Number of gray tones which are to be used on the printer for displaying the original image. Note: This parameter is only evaluated when using types PCL, POST or PRES!
Possible values are 2,4,9. With the default value 2, each pixel of the original image is converted either to a white or a black pixel on the printer. With the value 4, each pixel of the original image is converted on the printer with 4 pixels, which simulate 4 different gray levels. With the value 9, each pixel of the original image is converted on the printer with 9 pixels which simulate 9 different gray levels.
Note: With values 4 or 9 the resolution of the image is doubled or tripled. The restrictions on the possible resolutions (see previous parameter) then apply for the resulting resolution.
Output
Individual steps of the upload procedure are logged in the report list generated and, if necessary, errors reported. The uploading of TIFF graphics, in particular, is cancelled if there is a variant which is not supported. A message to this effect is then issued. If execution is successful, the report generates a standard text with the key specified in the parameters. If the standard text already exists, a window appears with a warning before the text is overwritten.
Regards,
Ameer Baba.

Printing Standard Text in Task List via IA17

We currently use a lot of standard text in task list. However when I run IA17 to display and print a task list, the standard text does not display as the actual text, only the standard text include is displayed.
Is there a way to get the actual text from the standard text to display as well?

Okay, I know I keep answering my own questions, but every answer leads to a new question.
What I've discovered is that if the include statement for the standard text is not in all caps, then it does not print in IA17
For example, we had the include as: Include Z0000438 OBJECT TEXT ID IPRT
However it would appear that the statement needs to be like this: INCLUDE Z0000438 OBJECT TEXT ID IPRT
Has any one else experienced this?
Edited by: Darrell Dorsey on Sep 23, 2010 3:19 PM

Converting language on standard texts

Hello Gurus,
I have copied standard text LLE00 (language *) from client 000 to client 500 in transaction SO10, however the document is is language DE and I wish to convert it to language EN. Is there an easy way to do this. I fave looked, but I cannot find anything. In transaction SE71, I can see that I can convert there, but I am asked for Form details and LLE00 does not appear in the search string. What am I doing wrong. Can anyone help please.
Regards
Jackie

Hi Jackie,
Try using the translation tool from SE63.
For further info refer the following link.
Link: [http://help.sap.com/saphelp_sm32/helpdata/en/b4/54601d77f38e429ffad9e3e11c1b25/content.htm]

QUERY ON STANDARD TEXTS

Hi all,
 I am using a standard text and using it to output data in a classical report using a function module.The output is displayed but after every paragraph i need a line gap which is not appearing in the output. I tried all format options and commands in standard texts but they are not working.
The output is displayed with out any gap after each paragarph.
Please suggest me any ideas to follow.
Thanks and Regards
Lokesh

This is the function module i have been working on:
DATA:ID LIKE THEAD-TDID VALUE 'ST'.
DATA:LANGUAGE LIKE THEAD-TDSPRAS VALUE 'E'.
DATA:NAME LIKE THEAD-TDNAME VALUE 'ZTERMS_CONDITIONS'.
DATA:OBJECT LIKE THEAD-TDOBJECT VALUE 'TEXT'.
DATA:BEGIN OF ITAB OCCURS 0.
INCLUDE STRUCTURE TLINE.
DATA:END OF ITAB.
CALL FUNCTION 'READ_TEXT'
EXPORTING
* CLIENT = SY-MANDT
 ID = ID
 LANGUAGE = SY-LANGU
 NAME = NAME
 OBJECT = OBJECT
* ARCHIVE_HANDLE = 0
* LOCAL_CAT = ' '
* IMPORTING
* HEADER =
TABLES
 LINES = ITAB
* EXCEPTIONS
* ID = 1
* LANGUAGE = 2
* NAME = 3
* NOT_FOUND = 4
* OBJECT = 5
* REFERENCE_CHECK = 6
* WRONG_ACCESS_TO_ARCHIVE = 7
* OTHERS = 8
IF SY-SUBRC <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
LOOP AT ITAB.
WRITE:/ itab-tdline.
ENDLOOP.

Adding Standard Text to the Selection Screen obtained using PARAMETERS

Hi all,
I have a report program which has the selection screen declared by the key word PARAMETERS.
Now I need to make the changes to this program such that a Text Editor appears on the Selection Screen and has a Standard text that should be displayed.
How can I do it?
I saw the screen number of the Selection Screen and went to screen painter and tried to add the Text Editot..but it did not let me dou2026.Why?
How should I add a standard text to a selection screen? The standard text should not be on top , but some where on the screen.
Regards,
Jessica Sam

Hi Sam,
I dont want to create a new screen for this. On the existing screen whihc was built using PARAMETERS key word..i should insert a blokc of text whihc is mpre than 5-6 lines..how should i do it.
I navigated to Text Elements---->Selection Texts
it is now asking for Name and Text and i see in Name column the name of the parametsr that they used for Check box, radio button etc and in Text i see the text that is appearing on the screen
Now i am not sure what is should do next
My req is..i should display a block of standard text that doesnt change and whihc is of 4-6 lines?
how should i do it?
please also help me with what data declartions that i should do in parametrs key word in program?
Regards,
Jessica Sam

Transport STANDARD TEXT KEY from CA10

Hi ,
Is it possible to transport the STANDARD TEXT KEY created in CA10? Please give your suggestion on how it can be done or is it advisable to create entries in each client manually.
Thank you.

You can only transport the standard text key along with its short text, long text transportation is difficult as they are not stored in transparent tables.
Follow the steps:
1. Go to transaction SE10. Click on Create.
2. Following pop-up appears. Select Workbench request.
3. Now double-click on the request
4. give the following details:
Prog ID: R3TR
Object type: TABU
Object Name: T435T
5. Now click on the key button available under the name u201CFunctionu201D
6. Following screen appears. Double-click on the first empty line.
7. Here we can provide the entries that we would need to transport.
Client: Client name
Language:*
Std text key: *
8. Now you can check for the entries that would be transported as per the given condition, by clicking on the table button
Select the third radio button u201CTable contents specified by current keyu201D.
9. Click on Save. A warning message would appear.
Ignore the warning message and click on Save. Now transport this request to transport the data to any other system.

# appearing in standard text.

Similar Messages

Maybe you are looking for