Copy Standard Text into CRM_ORDERH

Hello,
maybe anybody has an idea for my problem: I need an default text in a textscheme in the order-header. I can do this manually, I create a standard text within the textobject "TEXT" with SO10, and in the transaction I can copy the text with help of the sapscripteditor into my text. But, I need this functionality automatised. When I create my transaction, I want to have a default text.
I tried to manage this with access sequence, but I cannot see any possibility with this. The problem is, that the reference object "TEXT", were you can create standard texts, is not accessable from the order-header.
Any ideas?
Best regards and thanks
Sab

I think you should be able to solve this using Transaction Templates.
This allows you to prefill data on the template and saves a lot of effort during business transaction creation.
You can create templates for different transaction categories such as activities, leads, service orders and so on:
Explanation for a service order: 
Definition
The template for the service order business transaction. As is the case with the service order, the service order template is used to map services in the system. A service order template enables you to define and store reusable service descriptions as a useful set of activities, products, services, and materials.
Use
You can use a service order template to reduce the workload involved in creating new business transactions (documents). You create templates for standard service processing tasks, for example. You can:
·        Copy templates to create new business transactions with the same object type
·        Include templates in an existing business transaction (such as service confirmation or product service letter)
·        Create a template as a follow-up document on the basis of an existing service order; business partner data is not transferred
You can copy a template only if it does not contain any errors, has the status is Released, and is currently valid.
The service order template can contain a large number of items and subitems. In the template, you can define a large number of values as attributes (conditions, price information, quantities, and so on). If you create a service order template on the basis of an existing service order, all the items that are not required for a general template, such as the sold-to party, are omitted.
The service order template describes only the scope of services of the planned activities and not the actual execution (when and for whom).
Structure
A service order template has the same data structure as the associated operative business transaction, that is, it consists of a header and items (and subitems) with a large number of sets and enhancements that are valid for the business transaction.
In a service order template, you cannot store any information about the sold-to party. For this reason, not all the functions of the service order transaction are available. You can enter information about the sold-to party in the relevant business transaction.
Three different views of the service order template are available:
Fast Entry view
In the Header Data view, you enter data that is valid for the entire transaction. The top screen area contains the transaction ID, the transaction description, and a pushbutton for changing the status. In the bottom screen area, you can enter an item. You define additional items in the Item Details view.
Item Details view
In the Item Details view, you can enter additional items on various tab pages (Overview, Services, and so on). On the tab pages in the bottom screen area, you maintain detailed information about the individual items, such as statuses and prices.
Transaction Data view
In the Transaction Data view, you enter detailed information about the header data, such as organizational data, actions, and partner data.
Example
-          A service order template is to describe the standard maintenance procedure for a vehicle of a specific type. The catalog for the standard maintenance procedure includes services (filter replacement, oil change, engine check) and materials (1 filter, 12.5 liters of oil).
-          You use a service order template to plan a recall for a specific automotive category. The catalog for the recall contains the following activities: scheduled appointments with customer, repairs, confirmation to car manufacturer, and invoice for car manufacturer.
-          An Engine Replacement service order template already exists. When planning a repair in detail, you have to arrange for the engine to be replaced. You include the Engine Replacement order template in the existing service process (in this case, a repair service order). The system then copies the items from the order template to the service process.
Hope this is usefull for your requirement
cheers
davy

Similar Messages

  • 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.

  • Adobe Acrobat. Change "Copy selected text into Highlight, Cross-Out, ..." also for highlights made before changing the setting

    I am looking for a solution to apply the "Copy selected text into Highlight, Cross-Out, and Underline comment pop-ups" setting to highlights that I made before I changed this setting.
    Someone wrote a batch for this which costs 60 dollar and this seems to do what I am looking for: Custom-made Adobe Scripts: Acrobat -- Retroactively Copy Highlighted Text into Comments
    Where can I find Adobe's solution for this problem?  I do not want to buy external batches for a professional software suit.
    I expect that this is a common problem for people who start to organize a large literature base with many pdfs and must keep track of highlighted text. I was not previously aware of the "Copy selected..."setting, but I need to change it now for all my pdf files to make them compatible with a reference manager that I want to use. New comments are now compatible, but the hundreds(!) of pdfs that I worked through before are not, so copy pasting the highlighted text into comments is not an option.

    Hi gb145,
    You are posting on acrobat.com online service forums.
    Kindly post this query in Acrobat forums:Acrobat
    Regards,
    Florence

  • Urgent help in copying STANDARD Texts of various lang from 1 client to anot

    Hi,
    I have a require ment in which i have to copy all standard texts in chinese,thai language from one client to another.
    Can any one please help me with this .
    I don't have any idea on proceeding .

    Hi,
    Use the Following Program
    goto se38>RSTXSCRP>EXECUTE.
    CHOOSE THE RADIOBUTTON Standard Text .
    In the Object name type ur Textname(chinese one ).
    choose the Mode as Export.
    GIVE the Language as chinese Code.
    EXECUTE.
    Save to ur desktop.
    Now logon to other client.
    goto se38>RSTXSCRP>EXECUTE.
    CHOOSE THE RADIOBUTTON Standard Text .
    In the Object name type ur Textname(chinese one ).
    choose the Mode as IMPORT.
    GIVE the Language as Chinese Code.
    EXECUTE.
    Give the File name.
    The text will get Imported.
    Regards,
    Morris Bond.
    Reward Points if Helpful.

  • Defaulting Standard Text into Vendor Text

    Hello,
    We have been asked if we can add functionality similar to the S010 standard texts in R/3, so that a SRM user can select from a list of standard texts. The text would default into the Vendor Text on the Shopping Cart, the user would be able to amend the text if required.
    Does anyone know if this is achievable? I assume it would have to be done via a BADI?
    Thank you.
    Kind Regards,
    Jackie Jones

    Hello Jackie,
    Use text schema to achieve your request: you can define fixed values for texts.
    In SRM 7.0 release, it is in IMG:
    SAP Implementation Guide > SAP Supplier Relationship Management > SRM Server > Cross-Application Basic Settings > Text Schema
    I think path is the same for lower releases.
    If you use fixed values, this means vendor text coming from your catalog has to make part of your fixed values.
    Regards.
    Laurent.

  • Copy Header texte into Item text, trasactions FB60-FB50-FB70

    Hi,
    using the transactions FB50, FB60 and FB70 I need to copy automatically the Header text into the Items text.
    Can someone tell me how to do that?
    Thank you and best regards,
    Giorgia

    In the enjoy transaction like FB60-FB50-FB70, header and line items fields are quite mixed up. When you are mentioning Header text, please confirm that you meant "Header text" field in the "Details" tab screen and not the "Text" field in the basic data tab screen.
    Normally when you want to copy the "text" field content in the Basic Data screen to all the G/L line items text fields, you do it through "editing option" in the FB60-FB50-FB70 transaction screen itself. Here in the General entry options you activate the check box "Copy text for GL account enter".
    But if you want to copy really the header text in the Details screen to Vendor and Gl items for example, then you have to create substitution rule
    Thanks
    Ranjit

  • Copying infoobject text into a second language key

    Hi all,
    I need to manage material text in both IT and EN language key. Some material codes are generated in ECC only in IT, some other in both languages.
    Since reporting is in any case required in english, I wish to set up something which is aimed to copy description created in IT into EN language key. This is aimed to avoid report displaying the code in all occurrences text in EN is not mainteined.
    Example:
    Material Code A100: text IT = Materiale A    text EN = Material A
    Material Code B100: text IT = Materiale B    text EN = not maintained
    in this case I wish to copy text Materiale B also into the language key EN.
    I remember there is a standard program to manage these situations in ECC HR and I was wondering if there is something similar in BI.
    Thanks to all

    I'm not talking about translating Infoobject decription.
    I need to have in both languages the text of an infoobject members.
    For istance, considering 0MATERIAL, I need to have in both languages all 1000 material codes managed in the company although in ECC they created description in english only for 600 codes and description in italian for all 1000 codes.

  • Copy Standard Variable into Z variable.

    Hi all,
    I am using a standard variable 0DAT in the query for 0calday.
    Now i want to make a clone of the same variable.i.e i want to copy it with the same structure into Z variable.
    Also, 0DAT is having SAP Exit and that should copy to Z variable.
    Please suggest.
    Regards,
    Macwan James.

    Hello,
    User exit are variable specific, so if u create new z variable you have to write your own user exit.
    Its pretty simple to create:
    1) Create Zvariable type user exit with single and no ready for input
    2) In CMOD write a simple code for this variable as
    when 'zvariable'.
    if i_step = 1.
    l_t_range-low = sy-datum.
    l_t_range-sign = 'I'.
    l_t_range-opt = 'EQ'.
    Regards,
    Shashank

  • Copying header text from PM notification to PM order

    Hi!
    My task is to copy the header long text from the notification into the PM order (made from/attached to the notification). I've checked the customizing, but there is only an option to copy standard texts into the order.
    So I would like to put the text into a memory ID, during notification saving, and put the text into the PM order. And of course without modifying the standard...
    How can I insert text into an order, which does not have its document number yet? I think I can not use the SAVE_TEXT...
    Thank you..
    Tamá

    Hi,
    Try to find userexit after SAVE. so you have document number, then you can use
    SAVE_TEXT.
    aRs

  • How to use table in standard text

    Hi,
    I created one standard text using SO10 and I need to populate my internal table data values in the standard text. Below is the standard text i created.
    XXXXXXXXXXXXXXX
    XXXXXXXXXXXXXXXXXXXXXXXXX
    XXXXXXXXXXXXXXXXXXXXXXXXX
    XXXXXXXXXXXXXXXXXXXXXXXXX
    XXXXXXXXXXXXXXXXXXXXXXXXX
    &GV_ASSIGNMENT&   &COSTCENTER&    &ORGUNIT&
    &GV_ASSIGNMENT&   &COSTCENTER&    &ORGUNIT&
    &GV_ASSIGNMENT&   &COSTCENTER&    &ORGUNIT&
    Thanks,
    XXXXXXXXX
    If an employee have multiple assignments, I have to send a mail to org unit head with the above format.
    I created the above format in standard text (SO10). Now how to populate the values in the standard text.
    Thanks,
    Ram

    Hi Ram,
    A standard text like this does not have the concept of looping through data (which is what you'll have to do if there you have a table of data).
    What are you using to generate the mail?  If is is comning from smartform or SAPscript you should use the form to define the layout and the loop, meaning you'll need to split your standard text into smaller texts.
    Regards,
    Nick

  • Pls explain how to add standard text in sapscript & smartforms

    Dear friends,
    pls explain how to implement standard text into sap script and smartforms.
    in how many we can do.
    and what is diff between include text & text modules in smartforms.
    how we can translate into multiple languages.
    Regards
    Jagadeeshwar.B

    hi,
    for the include text goto tcode so10.
    for changing the smartform and scripts use there methods..
    1. goto se63>translation->abap objects->other long texts->FS Forms and Styles---> for scripts use Forms
                                           for smartforsm use SAPSmart form
                                           for styles use Styles
    2. goto se71->utilities->original language.---> source lang
    (for scripts)                                                     target lang
    to include the include text created in the tcode so10 in the smartforms go to general attributes of the text element--text type> include text...
    regards,
    venkat.
    Edited by: venkat  appikonda on Mar 22, 2008 11:56 AM

  • URGENT :Similar name of standard text  in different systems

    Scenario is:
    We have more than 3 production system as usual and want to merge in one for future convenience.(Sending  the data through interface) now <u>name of the Standard text </u> for the SAP Script say <b>Zabc</b> in one production system  is also available in other Production system with same name <b>Zabc</b> but different text in it and used for different SAP Script.  if we are moving the Standard text into one production system then we  r facing problem because of the similar name of Standard text but it is used with different text init for different SAP Scripts
    Can any one help me in this..
    Regards,
    Nupur

    I have question in SAP Script ..
    I have created one SAP script in original Language EN addition with Key Language HU (Hungary), means when user want to see the SAP Script in EN then all the content will come in EN and when they want see in Hungary they  will get in Hungary. I did this part .but the logo part is troubling me .
    I have uploaded successfully the Logo in Original language EN and test it , it's working well. Now when I am opening the Same SAP script in HU language then I am not able to see the Logo Uploaded .....means when i am going to Logo window  for Hungary SAP Script no Logo unpadded and  Insert Logo option is Grayed (Inactive)
    Could you help me out Please?
    If I run the test case, I am not able to see LOGO for the SAP script in Key language HU.WHY?
    Colud u pls teel me the path How to post a new  queires , I forget how i did for the first time ...I know this is a very stupit  question but pls... do reply me  back..

  • I'm using Firefox w/ Yahoo Mail on a Mac. When I try to copy/paste text in the body of the emai, it thinks I'm inserting a picture & all kinds of little text boxes appear. What can I do to get rid of all the little text boxes?

    This always happens when I try to copy/paste text into the body of my yahoo email. It only started happening when i switched to a mac.

    Try this extension:
    *Extended Copy Menu (fix version): https://addons.mozilla.org/firefox/addon/extended-copy-menu-fix-vers

  • 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.

  • Converting language on standard texts

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

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

Maybe you are looking for