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

Similar Messages

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

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.

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.

Acrobat X standard pb pour modifier le texte d'un document

Je n'arrive pas modifier le texte d'un document sous acrobat X standart qui a été crée à partir de acrobat distiller 7.0.5.
Message d'erreur: le texte accumulé dans la zone de seléction tentée a subi une rotation ni horizontalement ni verticale. L'outil de retouche ne peut pas créer de sélection de texte.
Le plus étonnant c'est que je peux modifier le texte avec avec acrobat pro 7 mais pas avec acrobat X standard pour ce meme document.
Test effectué sous windows XP pro service pack3 et windows 7 pro service pack1.
Merci d'avance

Salut,
il n'y a malheureusement rien à faire à part essayer de modifier les Préférences comme indiqué sur la capture d'écran jointe…
Par contre ça fait plaisir de rencontrer un utilisateur des abracadabraTools !

Standard text in Routings - Word documents

Hi all
I want to attach word documents to Standard Routers. I checked the standard text CA10 but did not find a way to upload word documents. I saw an option only for uploading 'ASCII', RTF or RTF files. Is there a way I can attach word documents to the Routings. What is the best way to do it? Is it standard text or some other process.
Am using ECC 6.0
thanks

Dear,
you cannot attach,....but you can copy from word document to text click on long text and copy the word document data to the long text page and save

How to convert a Word Document to SAP SCript standard text.

Hi team,
Does any one know how to convert a word document or text in Word format to standard text.
So that we can use that standard text in Script output.
This might be very useful if we need to convert a lot of text into standard text.

Hi,
Create the name of the standard text you want in SO10.
When the editor is called up, select Text -> Upload and then browse for your file(s). Must be saved in RTF format in Word remember.
Cheers
Colin.

Smartforms : print standard texts or texts out of document with command in.

We used to have an output via Sapscript (printout of a purchase order) and the output was containing standard texts or text out of the purchase order, which contains commands (a test in the standard text or an include of another standard text). This text was correctly printed via sapsript, command were taken into account.
Now we have a new output for the purchase order which is working with smartforms. When working in the smartforms with a text type 'include text', commands in the text are not working.
When working with smartforms, is it not possible to include texts (out of the STXH table) which contains commands? These commands are not taken into account.
Thanks.

Thanks for the answers!
Example how they work here : in the material master, purchasing text => somtimes include of a 'standard' text. This to avoid typing the text in all materials which use this text. We can avoid this by instead of including the text, to 'append' the standard text.
Also in some standard texts, some tests were done (on output type, purchasing organisation,.....) which we can change by reading the text in the print program and building those tests in the print program itself.
I just wanted to be sure that there was a possibility or not in Smartforms to work like that because we worked like this using sapscripts and it worked fine.
We will change this way of working and build the logic into the print program. We will inform the master data team not to use the 'include' command into a material master text but instead append the standard text directly into the material master text.
Best regards,
Ann.

Extract final content of Standard text (function?)

Hallo
I'm dealing with such a problem I need to have in table
standard text I mean the final version of it:
I have to textes e.g.:
TEXT01
Test 1
Test 1
TEXT02
Test 2
:/ INCLUDE TEXT01 OBJECT TEXT ID ST LANGUAGE 'DE'
:/ DEFINE &TEST& := 'Define Text'
&TEST&
Is there any function that provide the FINAL version of Text02
Because READ TEXT for TEXT02
results as table:
Test 2
:/ INCLUDE TEXT01 OBJECT TEXT ID ST LANGUAGE 'DE'
Instead of:
Test 2
Test 1
Test 1
Define text
Anybody has an idea?
thank you very muc in advance
Bogumila

Yes, here is how we handle it. In our case, if there is any INCLUDE text, it will be on the first line of the text. Here you can see that we are looking for the INCLUDE on the first line, and then processing accordingly.    This will give you some idea, but of course you will need to modify a bit.
clear xtext. refresh xtext.
* Retrieve the text
call function 'READ_TEXT'
       exporting
            client                  = sy-mandt
            id                      = id
            language                = sy-langu
            name                    = name
            object                  = object
       tables
            lines                   = xtext
       exceptions
            id                      = 1
            language                = 2
            name                    = 3
            not_found               = 4
            object                  = 5
            reference_check         = 6
            wrong_access_to_archive = 7
            others                  = 8.
delete xtext where tdline = space.
* Check the text for an include of standard text,
* if present, explode the include.
data: iincl type table of string with header line.
data: iid   type thead-tdid.
data: iname type thead-tdname.
* Read the first line of the text
read table xtext index 1.
* Split the line into a table.
clear iincl. refresh iincl.
split xtext-tdline at space into table iincl.
* Check that the first word is INCLUDE
read table iincl index 1.
check iincl = 'INCLUDE'.
* Get the name of the include
read table iincl index 2.
iname = iincl.
* Get the id of the standard text(ST)
read table iincl index 6.
iid = iincl.
clear xtext. refresh xtext.
<b> call function 'READ_STDTEXT'
       exporting
            id              = iid
            language        = sy-langu
            name            = iname
       tables
            lines           = xtext
       exceptions
            id              = 1
            language        = 2
            name            = 3
            not_found       = 4
            reference_check = 5
            others          = 6.</b>
Regards,
Rich Heilman

ExtendScript: Get all text from a document

Hi all.
I have the following task: I need to translate a document into another language using ExtendScript. So, as "input" I have a document with a text/graphics/tables/etc. in Language_1 and a "somehow-separated file", which will contain data about translation into the Language_2. E.g.:
Some_text_in_language_1     Some_text_in_language_2
Some_other_text_in_language_1     Some_other_text_in_language_2
To get the source text from the document, I've tried to use this:
var pgf = doc.MainFlowInDoc.FirstTextFrameInFlow.FirstPgf;
while(pgf.ObjectValid()){
     var test = pgf.GetText(Constants.FTI_String);
     var text, str;
     text = "";
     for (var i=0; i < test.len ; i +=1)
          var str=test[i] .sdata.replace(/^\s+|\s+$/g, '') ;
          text = text + str;
          PrintTextItem (test[i]);
     pgf = pgf.NextPgfInFlow;
But with this, I can only access the regular text in the document (e.g. the text in tables remains untougched). Is there any way I can the all textual data from specified document? Or maybe, the full list of controls, which can contain it, to iterate throught them and extract it one-by-one? Or maybe there's a better way to solve this problem?
Thanks in advance! Any advice would be greatly appreciated.

There is another way to loop through ALL paragraphs in a document, regardless whether they are in a table or in the main text flow. You can use the FirstPgfInDoc property of the document and loop through all Pgf objects using the NextPgfInDoc property of the Pgf until you reach an invalid object. Note that this also includes all paragraphs in the master and reference pages, so it might be useful to check where the Pgf is located (on a body page or not). There is a script on this forum that does that - I believe it was created and posted by Rick Quatro.
Working your way through the main text flow does not guarantee that you have all the visible text in the doc. There may be multiple flows and there may also be text frames that are placed inside anchored frames. Those text frames are not contained directly in the main flow of the document.
Good luck with your scripting
Jang

Urgent -- using Standard text in SMart forms

Hi Techi's.
I have created a standard text using SO10 , and included the same in smartform.
But the requirement is , i need to change the format of the standard text with my own style, so i craeted a Smart style with relevant Paragraph and Character formats.
Plz help me out in linking the STandard text with the smart style.
I know how to include smart style in smart form, but the issue is "how to include Smart style for the created Standard Text ".
Urgent and helpful answers will be rewraded.
Regards,
Naveen

hi naveen
for Smartforms material
http://www.sap-basis-abap.com/sapsf001.htm
http://www.sap-press.com/downloads/h955_preview.pdf
http://www.ossincorp.com/Black_Box/Black_Box_2.htm
http://www.sap-img.com/smartforms/sap-smart-forms.htm
http://www.sap-img.com/smartforms/smartform-tutorial.htm
http://www.sapgenie.com/abap/smartforms.htm
How to trace smartform
http://help.sap.com/saphelp_47x200/helpdata/en/49/c3d8a4a05b11d5b6ef006094192fe3/frameset.htm
http://www.help.sap.com/bp_presmartformsv1500/DOCU/OVIEW_EN.PDF
http://www.sap-img.com/smartforms/smart-006.htm
http://www.sap-img.com/smartforms/smartforms-faq-part-two.htm
Re: Need FAQ's
check most imp link
http://www.sapbrain.com/ARTICLES/TECHNICAL/SMARTFORMS/smartforms.html
step by step good ex link is....
http://smoschid.tripod.com/How_to_do_things_in_SAP/How_To_Build_SMARTFORMS/How_To_Build_SMARTFORMS.html
regards
ravish
<b>plz dont forget to reward points if helpful</b>

Track Changes log of a specified Standard Text?

Hello Experts,
Am looking to develop a report (change log report) for standard texts, for example, (pls. note all input parameters of this standard text are same)
Yesterday the user entered the standard text as
This is yesterdays standard text
And again user has changed today it to
This is todays standard text
Pls. let me know that is there any standard transaction to track these changes log? is there any table (seems STXH, STXL are not helps me) to store these changes? how can i retrive all these changes for a specified stanrd text?
Thank you

Hi M_S_Raju_0613,
I never heard of a tracking feature for standard texts - standard sapscript texts must be an add on SAP took from any non-SAP development and never integrated well. So you have to change documents for them or the pool tables where they are stored.
If only some texts and only special changes are in question, you may create a special program that stores a copy of the text and compares the copy to the actual text in a recurring job.
No better idea, sorry.
Regards,
Clemens

Standard text displayed correctly in print preview but not in print

Hi,
I have a script in which a standard text has to be printed in the output.
The standard text contains some german characters.
These characters are displayed correctly in print preview but not in print.
The text is maintained in 3 languages DE,EN and Russian.
The same text is being printed in some standard report. But that is displayed correctly both in print and print preview.
Please suggest something.
Regards,
Richa Aggarwal

Hi Richa,
Check this document from SAP: [help doc|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f0652a95-5f0b-2a10-5aba-c085f8bbe6d6?QuickLink=index&overridelayout=true]
It indicates that you have to be sure to select "Unicode" fonts for your SAPScript form to ensure the proper printing of "Unicode" characters. If a character does not display then that means it does not exist in the font that you are using.
Regards,
Ryan Crosby

Copying a standard text into another text in so10

Hello Gurus,
I have an issue where i need to track offer letter,i have a standard text which is been automatically used in pb40 while generating offer letter and that is ww-offer-contract in which i need to change the code ( in textid palt )but it is read only document. i need to copy the text into another text.So that i can do the changes required in that.
If i go with Utilities-->copy from client then it is allowing me to copy but not allowing me to change into it.it is giving me the dump.Since it is asking for the permission,i went for stop protection.but still it is giving me the dump.
Any one plzz help me out with this.
Thank you all.
Edited by: BHAVANI MADIREDDY on Feb 12, 2008 12:34 PM

There is a selection screen parameter
parameters: par_bi like rfpdo1-f100buch default ' '.
Comment this and declare a variable and pass 'X' or space into that as per the requirement.

Changes to the Standard Text Key in a PM order

Hi all,
Is there a better way to track changes to the Standard Text Key in a PM order? When I change the Standard Text Key in the Operations tab (t-code IW32) and I access the change log (menu: Extras > Other documents > Changes) I only see that the language key has been changed. I dont see the actual Standard Text Key value. Any ideas?
Thanks in advance for your help.
Adriana

Hi
To use standard texts, perform the following six steps:
Select the maintenance order and access the operation overview screen using Goto -->Operation overview.
You can enter standard text keys in this screen or in a detail screen for the relevant operation.
Enter a standard text key in the appropriate field and press ENTER .
If the text is longer that the short text line available, the field Text is selected for that operation.
Check the long text and edit it if necessary. To do this, select the operation and choose Operation--> Long text.
The system branches to the text editor screen. If you also entered a short text for the operation and specified that this should not be overwritten by the standard text, you will see the short text displayed in the first line of the editor. The following lines contain the standard text.
Check the standard text and change it if necessary.
Save the final version of the text and return to the previous screen with Goto--> Back.
Save the maintenance order.
Standard texts are created for your system by your system administrator using the Customizing function.
Regards
Makarand Gurjar

Extract R/3 Standard Texts to BW Documents

Similar Messages

Maybe you are looking for