BDT and standard texts

Hello colleagues,
I want to maintain a standard text using s view maintained by BDT.
The standard text is of the type you can maintain with function module 'EDIT_TEXT' or transaction SO10.
This text has to be displayed in a view in a new tab created using BDT. (The text should be an advertisement text for the object)
I did create the view, and in the transaction I can go to the tab where I want to maintain the text. But it turns up as just an empty screen.
I did try to use the option in the customizing for the view in BDT: Views with the text object. This option is on the same page where you normally assign the program and the screen. Does anybody know how to use this option?
Thanks in advance,
( I will reward points for helpful answers )

Hi
You can call standard text and text modules by the following options :
Create One Text Window by right clicking the option. In this general attributes tab select the 'Text Type' as 'Text Module' and it will ask for the Name of the text module.
Press f 4 help to select the text module. And enter the language also.
Thanks

Similar Messages

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

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

Smart form Text module translation and Standard text

Hi i have a requirement in smartforms in which i need to create text modules and transtale into diffrent languages.
I have created text modules they are in my transport,
when i am translating through SE63 into target language it is not asking for any transport request , Can any one help me regarding how i can assign Transaltion thing to my transport.
Another thing is i require to use standard text, i am not much aware of it also as per my understanding i need to create it through SO10 Transaction , and i can use it in include text please correct me if i am wrong, i need this standart text also in two language but while creating standard text it is not asking transport request, and how i would convert standard text in diff lang and how can i assign to my transport.
Surely i would provide points for the valid reply.
Thanks in advance.

Hi Gudia San,
To transport Standard text, use the standard Report Program RSTXTRAN, execute it, on the selection screen, enter your standard text name as
Text key - name, press F8, it will display a ouput list. Now press F5 key and it will ask for transport request number.
Regards,
Abdul.
P.S: Rewards points, if useful!

How to use standard text in sapscripts

Hi,
I want to place a part of text to be displayed in my sapscript in the form of a standard text. I want to make the text bold with italics and also want to set a perticualr size to it.
I am new to SAPscripts can anybody please help me with this.
regards

hi
Use character formats in the script itself for the specific text. and in it mention font as bold and italic
and in text elements keep the text between <C1>......</> where C1 is your character format
or
create global style with
U can adjust the bold formats in the standard text itself.(se72).
In the standard text give the character formats and apply them in the text editor of ur sapscript as
text between <C1>......</>
In the text editor go to insert -> text elements-> and standard text.
u can give the standard text name there.
regards
prasanth

Standard text / Text module not printed correctly in Adobe forms

Hi All,
I need to print the dunning level text which is static. I have created text module and standard text with the same static text.
In the content I have created the text with text module tyoe and given the text module name. Similarly I created the include text as well.
But the text is getting printed continously, eventhough I have maintained as paragraphs.
For Example: I have maintained text as    TEST1
                                                                   TEST2
                                                                   TEST3
Now the same format shud be printed in the output. But TEST1 TEST2 TEST3 is printed.
Can anyone help me out how to print the text as in the above case and what is the reason for not printing in paragraphs.
Thanks and Rewards,
Karthik Ganti.
Message was edited by: Dezso Pap - Moderator

Hi Kartik,
1. ead standard text by FM READ_TEXT.
2. Read text lines content Read internal table LINES into wa_lines.
Concat wa_lines-tdline into string separated by as CL_ABAP_CHAR_UTILITIES=>CR_LF.
Bind that String to variable to text.
That will display text as you create.
Santosh

Standard Text not starting on current page in sap script

Hi all,
       I have a sapscript which displays a dynamic table. After that table I have included the standard text.
Ideally this standard text should display immediately after the table. But this is not happening. After the table, entrire page is left blank, and standard text starts from the next page.
How can i display standard text immediately after the table.

Hi,
    Try with calling PROTECT and ENDPROTECT using function module CONTROL_FORM in driver program.
CALL FUNCTION 'CONTROL_FORM'
          EXPORTING
            command = 'PROTECT'.
        PERFORM item_dynamic_table.
        PERFORM item_standard_text.
        CALL FUNCTION 'CONTROL_FORM'
          EXPORTING
            command = 'ENDPROTECT'.
Call the TEXT elements in corresponding performs.
Regards
Bala Krishna

How to make a 2-column text in sapscript via standard text?

Hello ABAP Gurus! I'm having a hard time thinking on how I'm going to display a two-column text in the MAIN window of the form Using Form Painter(se71) and Standard Text (SO10). Let's put it this way, the scenario is like you are formatting a paragraph on MS word in to two columns by Format > Columns > Two. What am I going to do with this similar situation in SAP? Any help will be highly appreciated. Thanks

This is nothing with standard text.
Call READ_TEXT FM and here use two variables ,read first line and move to first variable ,again read second line and move to second variable.
Thanks
Seshu

How to get the Hardcoded text and the Standard text in the same line

Hi,
I have an SAP Layout. In that, it should show the Consignee name as below.
     Consignee: SAP LABS
In this, the text 'Consignee: ' should be hardcoded in the layout itself. and the customer has requested to create a standard text for 'SAP LABS' sothat if they want to change the value in future, they would go and change the Standard text. I have created the Standard Text for SAP LABS. I am not able to get both these texts on the same line. I wrote in the layout like below and AS is the Paragraph format.
AS     Consignee:
/:        INCLUDE ZVRU_CONSIGNEE OBJECT TEXT ID ST LANGUAGE EN PARAGRAPH 'AS'
But, both are coming in dofferent lines. As /: is a command line, it is coming in the next line. Is there any way of getting these two texts in the same line..? While Inserting the Standard Texts, will there be any option/command to print it in the same line..?
Please share your thoughts. Thanks in advance.
Thanks & Regards,
Paddu.

Hi Paddu,
I have had a similar requirement. I did not use any FM or anything, simply did the following:
In SO10, for your standard text where u have used the text SAP LABS.
Instead of P1/ default para, change it to =. And then Save ur Standrd text.
Now in the SAPScript Text editor in which you want to print
P1 'Consignee :'
/: INCLUDE TEST OBJECT TEXT ID ST LANGUAGE EN
the output will be
Consignee : SAP LABS
I have tried and tested this method. It will surely work.
With regards,
Niharika.

How to add standard text in PO and how it is maintained ?

How to add standard text (paragraph) in PO and how it is maintained ?

Hi
Please go through this document.which has a step by step
Working with Frequently Used Texts
Use
You can copy texts from various sources to create PO texts:
Standard texts
Certain standard texts are supplied with the system and can be assigned to a purchasing document in Customizing.
The content of some standard texts is predefined by your system administrator.
You can also create standard texts yourself and copy them into purchasing documents.
Master records
Database fields
Activities
Creating Standard Texts
You can create your own standard texts via Tools ® SAPscript ® Standard text.
Inserting Standard Texts
You can insert your standard text on the long text screen via Insert ® Text ® Standard.
For more information, refer to the Basis documentation under BC Word Processing with the SAPscript Editor: Including Texts.
You can display the print preview via Text ® Print ® Print preview.
Inserting Texts from the Master Record
There are three ways of linking texts from a master record with a purchasing document. The relevant settings are made for each text type in Customizing for Purchasing. The indicator in the status column shows the nature of the linkage.
Option                                              Indicator in status column
The text is copied:
It is then independent of the text                 None
in the master record. Changes to
the text in the material master record
have no influence on the text in the document.
The text is displayed only:
It cannot be adopted.                                          N
The text is offered for copying:
It can be copied via Header or Item ® Texts ® Adopt text. (In requisitions: Goto ® Texts ® Adopt text.) Changes made in the master record will also be adopted in the document until such time as you copy the text.
Inserting Texts from Database Fields
You can include the content of a database field at any point in the text on the long text screen. A value specific to the relevant document is displayed in the printed document.
Choose Insert ® Symbols ® Program symbols.
Choose DDIC fields.
Search for the relevant table/structure (in the case of PO items, this is EKPO) and then choose ENTER .
Choose the relevant table field.
Choose Text ® Print preview to see the print preview.
Reward if useful
Aasif

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.

Standard Texts (Tcode CA10 and SO10)

Guys,
Also posted [here|http://www.sapfans.com/forums/viewtopic.php?f=7&t=317636]
Has anyone seen any decent SAP Help documentation on standard texts (TCode CA10 and SO10)
These are the texts that are used in operations, paging and some action-box functions, etc.
PeteA

Kaushal Rai,
I'm looking for some comprehensive documentation relating to the use of standard texts
We are investigating the possibilities/options for use in the PM module.
PeteA

Standard text and Adobe forms

How do you get a standard text created w/ SO10 displayed on the PDF? Can it also have the same formatting... bold, underline, etc.?
Currently on ecc 7.0.

This is where some training may be helpful....
I now have the context tab in SFP by changing the interface type on the interface attached to the form to be dictionary based. This allows me to add the text as you mentioned. The form has ZCI layout assigned.
But now my webdynpro is having issues calling the form. In my webdynpro my template source is the same as the sfp form name; but as I assign the pdfsource and datasource they are either removed and/or changed to a dummy value that is added to my context with no nodes or attributes.
This application currently runs in a production environment. All I was trying to do was add a standard text element to the form.

Standard Texts and Text Modules

Hi,
How to include standard texts and text modules in Adobe Print Forms?
Is there any solution?
Thanks !

Hi
You can call standard text and text modules by the following options :
Create One Text Window by right clicking the option. In this general attributes tab select the 'Text Type' as 'Text Module' and it will ask for the Name of the text module.
Press f 4 help to select the text module. And enter the language also.
Thanks

Standard text and perform in scripts

Hi guys,
can any body tell me how to use perform in scripts.
and how to include these statement it doesn't look like standard text
/: INCLUDE &ZTXTNAME& OBJECT BOM ID MZU
have a nice weekend

Hi Deepthi,
The syntax of Perform statement is
/: PERFORM <form_name> in PROGRAM <program_name>
/: USING &INVAR1&
/: USING &INVAR2&
/: CHANGING &OUTVAR1&
/: CHANGING &OUTVAR2&
/: ENDPERFORM.
In the program <program_name> , you can write the form <form_name> as:
FORM <form_name> TABLES INTTAB STRUCTURE ITCSY
OUTTAB STRUCTURE ITCSY.
endform.
INTTAB will contain all the input parameters like INVAR1, INVAR2 etc and OUTTAB will contain all the output parameters like OUTVAR1, OUTVAR2 etc.
You can download a nice document on SAPScript from this link , but within 1 day.
https://www7.sendthisfile.com/d.jsp?t=asglGjpv25aba8T8sp2G1zyd
Regards,
Amit.

BDT and standard texts

Similar Messages

Maybe you are looking for