Import R/3 SO10 Standard Text to BW Documents

Hi
Please let me know
1. How can Import the Standard Text (SO10) from R/3 to BW Documents?
2. Is there any Function Module to extract the text?
Please let me know since it has become priortized task. Thanks!!
~ Vaishnav

Ok this is easy and not that tough as expected...
I'll write a program that calls the function module READ_TEXT and export the output to the application server and then I'll retrieve the data into BW documents after changing the respective InfoObject as Characteristic is Document Attribute.
~ Vaishnav

Similar Messages

Using text elements in so10 standard texts

How to use text elements in so10 standard texts.

HI,
In DDIC we have two structures :
1. THEAD - Text Header
2. TLINE - Text Lines
SO10 is the tcode..for standard text...
We have a FM to read the text ... read_text...
and save_text is for create text..
this text is are used in SAP scripts...
the standard text is identified by three parameters :
1. Text Name
2. Text ID ( ST for standard text )
3. Language
hope helpfull
Raghunath.S

To read a SO10 Standard text

Hi,
I have created an SO10 Standard text (ZTEXT), now from a report program i have to Read it's text and use further.
How can I read an SO10 Text from a report Program?
Pls provide some sample code.
Thanks in advance,
Pankaj.

To whom?
please close your thread without showing any consolations(Thanks a lot!) towards people if you don't want to assign the poitns.These points are not giving us food but surly these would be enough feed for needed person.
just read below link carefully specially step 4
[Forum Rules of Engagement|https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/rulesofEngagement]

Extract R/3 Standard Texts to BW Documents

Hi Experts,
I would like to know how to extract the R/3 Standard Texts into BW Documents. We can use SO01 Tcode to see the text and STXH to see other fields relative to standard text and we can also use "READ_TEXT" function module to retrieve the values after giving necessary parameters in R/3.
Initially, I thought I can use all these function module and table and do a custom extractor and bring it to BW but in BW it would not allow more than 60 chars and this would be somewhere around 500 to 1000 chars per text. So I'm not sure how to bring the text into BW and save it as a Document in BW.
Please I need your expertise on this issue. Thanks!!
~ Vaishnav

Ok this is easy and not that tough as expected...
I'll write a program that calls the function module READ_TEXT and export the output to the application server and then I'll retrieve the data into BW documents after changing the respective InfoObject as Characteristic is Document Attribute.
~ Vaishnav

Printing text in text area in so10(standard text)

Dear all,
I need to print a text in text area.i mean i need a box in which i can fill text in standard text (tcode-so10).Using box command we will be doing in script.
But is there any possibility that i can solve the issue in so10 itself as i am generating offer letter in pb60 it takes my standard text there itself.So is there any solution for this issue?
This issue is very urgent.
Thank you,
bhavani.

Hi
KEEP a BREAK-POINT and debug the internal table lines how it is coming
some overlap must be happening ..check.
Also check the code where you are getting this text into internal table.
1) One way to debug smartform is to debug the Function Module of that smartforms.
If you want to debug particular smartform node that the solution would be,
insert a "Program Line" just above the node you want to debug and this program line write a normal abap breakpoint.
So whenever you call the smartforms, it will stop at this breakpoint and you can debug onwards.
2) SFTRACE can be used for debugging SMARTFORMS.
Read More here.
http://help.sap.com/saphelp_erp2004/helpdata/en/49/c3d8a4a05b11d5b6ef006094192fe3/frameset.htm
Reward points for useful Answers
Regards
Anji

How to search a SO10 - Standard text by Content

Hi experts,
I have a standard text content. need to know how to identify the standard text object it is contained in.
Example: I have a form output which has Terms and Condition printed. The content has a word like URL:
texst.test.com. There are lot of standard text objects available in that form and many other forms. We are not able to find the corresponding standard text object.
So like to know whether it is possibel to search and find a standard text object by contect say URL:
texst.test.com?
Let me know whether this is possible to do in SAP?
thx
Ganu

It is not possible to get the standard text header by searching the contents. The tables for standard texts are STXH and STXL. Data is stored in raw clustered format.
As Raveesh metioned, manually looking into the smartform (Windows/Templates) and then using FM READ_TEXT to confirm the contents.
Thats the best possible way to get the standard text details from the contents.

Using READ_TEXT to read SO10 (standard texts)

Hi,
When we use READ_TEXT F.M for SO10 texts what are the parameters to pass.
ID - ST
LANGUAGE - EN
NAME - Z_TEL (SO10 text id)
OBJECT - ?
What i should pass to OBJECT & what else i need to input!
Thanks in advance.
Thanks,
Deep.

If u r reading text from Purchase Order text then Object ID will be EKKO.It depends what r u reading for.Look at the following code :
    CALL FUNCTION 'READ_TEXT'
      EXPORTING
        CLIENT                  = SY-MANDT
        ID                      = 'F01'
        LANGUAGE                = 'E'
        NAME                    = W_TDNAME
        OBJECT                  = 'EKKO'
      TABLES
        LINES                   = IT_F01
      EXCEPTIONS
        ID                      = 1
        LANGUAGE                = 2
        NAME                    = 3
        NOT_FOUND               = 4
        OBJECT                  = 5
        REFERENCE_CHECK         = 6
        WRONG_ACCESS_TO_ARCHIVE = 7
        OTHERS                  = 8.
Thanks & Regards,
Rock.

SO10 Standard text unable to create std text

I am trying to create std text through SO10, once i have cretaed its not saving , plz help me
Edited by: vishwas shastri on Jun 16, 2011 11:05 AM

vishwas shastri wrote:
> those are not reflecting .(saving) .help me plz..
Hello Vishwas,
Are the changes not reflecting or are they not getting updated? Please be specific.
On more question, do you have separate dev & testing clients? And you're changing the ST in dev client & when checking in testing client the changes are not reflected!
BR,
Suhas

Adopting standard text in the po

Hello there,
does anybody have a clue how to adopt a SO10 standard text automatically in a header or line text in a PO (ME21N) I know how to do this manually, but i do not want interferance of the user.
Thanks in advance.
Roger

It will not get adopted automatically in the PO.
You can automatically get it in the print out (or other output like email, etc) by including it in the layout / smart form.
Lakshman

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.

Columns in a Standard Text

Hello,
I need to add a Terms and Conditions page in a SapScript. This page needs to be formatted to be written in two columns.
I created the SO10 standard text for the terms and conditions page, but when I try to add the columns button to the text editor, this option is inactive.
How can I split the text into two columns?
Thanks!

Hi,
Splitting the text into two columns in the Standard Text is not possible. It is possible only in the layout windows.
I got the same requirement couple of weeks back. Finally what I did is, I just uploaded the word document (followed the same process what we do for uploading logo/bmp/image files etc) and then displayed in the script. If you like this option, you can try with this.In both of our cases, there is no necessary to create the Standard Text itself.
Hope this helps.
Thanks,
Srinivasa

SO10 move texts to another text ID

Dear Friends,
In T Code SO10 Standard text I have maintained texts in text ID ST.
Is there a way to move these texts to a different text ID by Mass change etc...
Please help.
Rgds... Ravi

Hi friend,
There is no such way for MASS MAINTENANCE in Standard Text.
You have to maintain individally for each text.
regards,
santosh

Get Bold letters in Standard text?

Hello
I have created a Z_style in SMARTSTYLES transaction. IT has some bold, colored texts.
Then, i am trying to create a Stnadard Text in SO10 by using the above just created Z_style.
But, when i opened the SO10, gave the custoem name, and trying to use my z_style, but, i did not see any such in SO10? My navigation is SO10-->Menu..._Format->Change Style
Pls. let me know how to fetch my z_style into SO10 tx.
Thank you

Hi,
SO10 - Standard Text is only a container to contain variables with no styles attached. If you need to attach Z-style you have created, you have to apply in SAPScript or SmartForm and in Print, you'll see that styles.
Thanks
Ravi

What is the difference between Standard text and Text Symbols?

Hi,
1.Difference between Standard text and text symbol,?
2. Which we use Standard symbol?

Text symbol
Text symbols are symbols representing text elements. In fact, a text symbol can be defined for every text elements. The reading of the form is easier in the SAPscript editor. The name of the text symbol must not exceed 32 characters and its value 60 characters. The value assignement can be done in two ways:
- Using the following command: "/: DEFINE &SYMBOL&='TEST_SYMBOLE'"
- Using a standard text symbol.
The text symbol value is temporary stored. When the print program finishes the execution, the text symbol does not exist anymore. The text symbol must have a value when it is declared.
Also check this link,
http://www.supinfo-projects.com/en/2005/forms_sapscript_en/5/
Standard text are good, if you are using them in more than one SAPScript, because you have to maintain them only once, and not in every SAPScript.
It is really good to write rarely changing texts into the SO10 standard texts (for example company name, and address).
standard text is not always used in scripts. when ever u want to display some data u need to use standard text so that the data gets displayed. Say, u have a large piece of document which needs to be printed at end of script... rather than writing the whole thing in script, we create standard text using SO10 and then use the name along with standard text in script.

Import and flow the xml text in a indesign document

pls,anyone give me a solution for import and flow the xml text in a document.
thanks,
screen410099

See http://forums.adobe.com/thread/838745?tstart=0
Would you mind waiting a bit before asking again and again and again and then again? It's possible the person who can answer you question just didn't happen to read the forums this week.

Import R/3 SO10 Standard Text to BW Documents

Similar Messages

Maybe you are looking for