Account number in Standard text in SapScripts

Hello,
I've created a standard text where I've to print account number as 12--1234-1234567-123.
But REGUH-ZBNKL prints the bank number as 123456
Where 1st 2 digits (12) is bank number and 2nd 4 digits (3456) is branch number.
REGUH-ZBNKN displays the account number as 789012343
Where 1st 7 digits (7890123) is account no and last 2 digit (43) is suffix no.
How do I format these two numbers into one as 12-3456-7890123-043
That means if the suffix is 2 digit add a '0' in front of the suffix to make it 3 digit (i.e. 034)

Hi,
You can use a concatenate stmt to prefix '0'.
for eg:
   if ws_int < '99'.
    concatenate '0' ws_int into ws_int.
  endif.
similarly you can use concatenate statement to build your string.
concatenate reguh-zbnkl0(2) reguh-zbnkl2(4)
                   reguh-zbnkn+0(7) reguh-zbnkn ws_int separated by '-'
into ws_account.
regards
Subramanian

Similar Messages

  • How to define & read Standard Text in SAPScript? Urgent Please

    Hi Experts,
    How to define & read Standard Text in SAPScript? Urgent Please..
    Thanks in advance
    good answer will points gud marks.
    sekhar

    Hi
    U can't define a standard text in a SAPScript, you call call it only by statament INCLUDE
    /: INCLUDE <ST TEXT NAME> OBJECT TEXT ID ST LANGUAGE <LANGUAGE>
    U can define it by trx SO10.
    If you need to know the text without to print it, you need to use a routine where u can use the fm READ_TEXT in order to find out the text.
    Max
    Message was edited by:
            max bianchi

  • Recruitment Faxing & e-mailing only possible for standard text in SAPscript

    Hi,
    I am using the old recruitment module PA-RC ion ECC6 and I am trying to send an email to an applicant. When I try and do this I get message "Faxing and e-mailing only possible for standard text in SAPscript". In feature WPROC I am set up to use RTF. Is there no way to send RTF emails? Do I need to create SapScripts for anything that I may possibly want to email?
    Thanks
    Tom

    Apparently only able to carry this out in SAPScript

  • How to create REQUEST NUMBER for STANDARD TEXT (SO10)

    how to create REQUEST NUMBER for STANDARD TEXT ( t-cODE SO10)

    you can do this using program RSTXTRAN .
    Text key - object
    Text key - name
    Text key - ID
    Text key - language, then it will store under one transport that can be moved to other system.
    check out the following link.
    http://help.sap.com/saphelp_47x200/helpdata/en/f4/b4a1ed453611d189710000e8322d00/frameset.htm

  • How to use standard text in sapscripts

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

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

  • Dynamic Standard text in SAPscript

    Hi,
    Can we use dynamica standard text in SAP script?
    The standard text name is supplied by a external field. The standard text contains a address.
    I want to change address based on text name.
    Thanks.
    Shreyas
    Help will be awarded.

    Hi
    In the SAPSCRIPT the std text is called by this statament:
    /: INCLUDE &V_TEXT_NAME& OBJECT TEXT ID ST LANGUAGE &LAN&
    The V_TEXT_NAME is the variable where the name of the std text is stored and it's filled at runtime.
    Now while printing a document you shouldn't (can't) change the std text, so you should have many std text as the addresses you need to print.
    So you can decide which text (address) to be printed inserting the name of the text in the variable V_TEXT_NAME.
    Max

  • Including standard text in SAPScript...

    Hi,
    I have created a standard text Z_NOTE in SO10. If I want to include in Sapscript form, how do I do it ?
    Thanks.
    Rajesh

    use the include control command:
    /: INCLUDE Z_NOTE LANGUAGE 'E'
    Assuming that the text is created in English language, in case if it is in a different lnaguage, modify the above include command with respective language.

  • 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

  • Linking of standard texts in sapscripts

    After creating standard text in so10, how do we link these texts so that it can be used in sap scripts.

    Hi,
    you should have searched first... But here is the answer
    INCLUDE name OBJECT name ID name PARAGRAPH name LANGUAGE   name
    e.g. /:INCLUDE mytext OBJECT TEXT ID ST LANGUAGE EN
             Here the standard text created in SO10 with name mytext is
             included in the form in language EN (English)
    In future please search before posting

  • Including standard text in Sapscripts

    Hi all,
    I want to include standard text by using 'INCLUDE Z_STANDARDTEXT_TEST OBJECT TEXT ID ST' not in a single line.Means I want that Include command not to be included in single line only.Is there any option for this.
    Rgds,
    Balaji

    then you can use '=' in the command line of next line and proceed as you want.
    for example
    <b>/:</b>     INCLUDE Z_STANDARDTEXT_TEST OBJECT TEXT
    <b>=</b>        ID ST
    hope you got it. '=' indicates that its a continuation of previous statement.
    what ever it is.It can be a static text or a command etc...
    regards
    srikanth
    Message was edited by: Srikanth Kidambi

  • Print standard text in a sapscript

    hi,
    I have want to include standard text by ME32k in a sapscript. I need to include the text and the particular format. For example if I use FM READ_TEXT for text object EKKO id F02 for a particular EKKO-EBELN, the FM give me the table LINES with this text:
    TD   TDLINE
    C      K02:HAEDER NOTE
    I need to print the text "K02: HAEDER NOT" with the format C ( Centered).
    Can you help me, please?
    Thank's.

    Hi,
    Tcode SO10 can be used to attach standard text in sapscript.
    For formatting, plz check the below link
    Standard text editor SO10

  • Function module to retrieve the account number linked to an SD invoice item

    Hi all,
    I should retrieve the gl account number linked to a certain SD invoice item. The
    program starts from VBRK and VBRP data. Is there a function module which
    enables to get it starting from these header lines? I already used the function
    module: RV_INVOICE_ACCOUNT_DETERM ( release: 4.0 ), but in some cases it
    doesn't seem to function properly ( the export table TKOMV doesn't contain a
    value for the SAKN1 field ). For the invoices for which the function isn't able to
    retrieve the account number, the standard accounting analysis functionality returns
    the following message: account determination carried out via KOFI type. So I'm
    searching for a function module that's able to retrieve the account number in these
    cases also.
    Thanks in advance.
    Adriano.

    Dear Adriano,
    Try with Function Module 'SD_DETERMINE_ACCOUNT_INVOICE '.
    Additional Info:
    BAPIs related salesorder:
    BAPI_SALESORDER_CHANGE Sales order: Change Sales Order
    BAPI_SALESORDER_CONFIRMDELVRY Sales Order: Confirmation of Delivery; Document Flow Update
    BAPI_SALESORDER_CREATEFROMDAT1 Sales order: Create Sales Order
    BAPI_SALESORDER_CREATEFROMDAT2 Sales order: Create Sales Order
    BAPI_SALESORDER_CREATEFROMDATA Create Sales Order, No More Maintenance
    BAPI_SALESORDER_GETLIST Sales order: List of all Orders for Customer
    BAPI_SALESORDER_GETSTATUS Sales Order: Display Status
    BAPI_SALESORDER_SIMULATE Sales Order: Simulate Sales Order
    FM:
    MB_ADD_PURCHASE_ORDER_QUANTITY (Reading and adding open purchase order quantities)
    SD_SALES_ORDER_STATUS_WWW for complete details including the delivery information.
    Hope this will help.
    Regards,
    Naveen.

  • Including standard text in sapsripts

    Hi all,
    I want to include standard text by using 'INCLUDE Z_STANDARDTEXT_TEST OBJECT TEXT ID ST' not in a single line.Means I want that Include command not to be included in single line only.Is there any option for this.

    you already created the similar post earlier. you can find answers in your old post.
    check this,Including standard text in Sapscripts
    close both the posts once your problem is solved
    Regards
    srikanth
    Message was edited by: Srikanth Kidambi

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

  • Sapscript and Standard Text - Polish Characters not printing

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

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

Maybe you are looking for