Standard Text Key printing on Job Ticket Shop Paper

Hi,
I have set up using transaction CA10 a series of Standard Text Keys containing approx 500 characters.
I am using the Standard Text Key on a Service Order but when I am printing the Service Order the first 40 characters are only being printed.
We have a requirement to print out on the Service Order the Standard Text Key and all of the text and not the first 40 characters.

Hello,
One suggestion would be to have a programmer check the SAPScript form that calls the standard text to make sure the formatting is not restricting the length of the text that is being printed.
Regards,
Paul

Similar Messages

How to use Standard Text Key in maintenance order header long text?

Dear All,
I have created a standard text key using transaction CA10 and I want to use this in maintenance order header long text. Is there any way to select any standard text key in maintenance order header long text?
Regards & Thanks,
Saif

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

How to get F4 help for Standard Text Key of a operation based on Order type

Hi Experts,
How to get F4 help for Standard Text Key (STK) of a operation based on Order type entered in selection screen. The F4 help should give the STK of related order type. At the same time the F4 help for Task Types based on Notification type. How to acheive the above two. Please provide the table names or any search help name if exists or Function modules...
Thanks in Advance.
Regads,
Bujji

Hi Guys,
Any help on this...
Regards,
Bujji
Edited by: Bujji on Dec 22, 2008 12:42 PM
Edited by: Bujji on Jan 5, 2009 2:00 PM

Standard Text Key in Routings

Hi,
Can we load Standard Text key into SAP. I want to use these standard Text key while creating Routings.
If yes, what is the Procedure.
Thanks,
Kishore

The problem may be in the joining..
In MARC and MAPL join MATNR,WERKS...
JOIN MARC MATNR and MAKT MATNR
JOIN MAPL(werks,plnty,plnnr ) to plpo(werks,plnty,plnnr )
PLPO ARBID to crhd OBJID
Now execute with your sel fields...

Standard Text Key in order

Hi
I created std text key in CA10
How to configure in "Assign standard texts for short messages to order types" ?
Alagesan

The standard text key created by using CA10 will reflect against maintenance order in operation tab when selected from standard text key field in maintenance order operation tab.
For the above said function no configuration is required. what every standard text key is selected for first operation, is copied automatically in maintenance order short message (provided that short message is not given by user different then first operation).
Hope this reply helps you.

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

How to get the real texts according to Standard Text Key maintained in CA10

Hi ;
I have a requirement to fetch the standard text based on the standard text key which is maintained by CA10.
is there any direct way to get those texts without giving 'TEXT NAME', 'TEXT ID' and 'TEXT OBJECT' but just by the standard key?
Thanks in advance.
Regards.
Vindy

Hi Varma,
Even if you want to personalise the Text also you can do without checking the DICTREF checkbox. Dirctly you can give the text in the Text elements by using the Menu GOTO -> Text Elemetns -> Selection Texts.
Regards
Thiru

Upload Standard Text Key

Hi expert,
I am trying to upload Standard Text Key (CA10) for task list. I don't know how to do it, because it contain long text. Can anyone give me a suggestion?
Thanks,
Secundes

I tried CA10 LSMW with fields
VLSH (C 007), TXT (C 040), TXLINE_02 (C 072), TXLINE_03 (C 072), TXLINE_04 (C 072)
The last 3 fields are mutiline content, which are generated through the recording. If you attempt 4 lines during the recording another field TXLINE_05. The answer to your question How many characters? is given in the brackets above.
I did not find a problem here. The problem I faced was some other and was a minor for me.
That is :
While processing (Foreground processing only), It was not filling the VLSH field. So what I did was- Enter this field manually & press F5 (create). The rest of the process went smooth by just keep pressing the Enter button.
So for every record I repeated this initial entry+F5, rest went smooth.
That was my experience. It is possible you might not face this problem even and everything may go smooth for you.
(I used Tab delimited Text file for uploading)
About the BDC programming, I do not have knowledge in this area, so I suggested so.
Regards....

Transport STANDARD TEXT KEY from CA10

Hi ,
Is it possible to transport the STANDARD TEXT KEY created in CA10? Please give your suggestion on how it can be done or is it advisable to create entries in each client manually.
Thank you.

You can only transport the standard text key along with its short text, long text transportation is difficult as they are not stored in transparent tables.
Follow the steps:
1. Go to transaction SE10. Click on Create.
2. Following pop-up appears. Select Workbench request.
3. Now double-click on the request
4. give the following details:
Prog ID: R3TR
Object type: TABU
Object Name: T435T
5. Now click on the key button available under the name u201CFunctionu201D
6. Following screen appears. Double-click on the first empty line.
7. Here we can provide the entries that we would need to transport.
Client: Client name
Language:*
Std text key: *
8. Now you can check for the entries that would be transported as per the given condition, by clicking on the table button
Select the third radio button u201CTable contents specified by current keyu201D.
9. Click on Save. A warning message would appear.
Ignore the warning message and click on Save. Now transport this request to transport the data to any other system.

Default Standard Text Key or Standard Text to first Operation of Order

I would like to have a standard text key or standard text defaulted for the first operation of an order created via IW31 of certain order type.
For example we have an order type called CORR for corrective orders. When ever there is a break fix, the user would create a CORR order via IW31. When this order type is used I want the first operation to have a predefined Standard text key defaulted. In this case we was our first operation to have a safety message and precautions listed.
This would work similar to a planned order that calls from a task list and has text in the task list.
I did some review and testing of the "Assign Standard Texts for Short Messages to Order Types", but as I understand it, this only works for sending message and not including text on the operation.
Is what I want to do possible? Or would it make more sense to use an exit like IWO10020, Maintenance order: Automatically include task list . I guess I could create a general task list and use that in this exit for all CORR order types.
Edited by: Darrell Dorsey on May 25, 2010 10:26 AM
Edited by: Darrell Dorsey on May 25, 2010 10:30 AM

For the scenario that you are referring to, i believe this would be the option that would be flexible. Yes, you will have to little bit of custom development for this and i don't see any standard functionality to default the standard text on the first operation for specific order types. You should be able to attach a task list where its planning plant differs with that of the Order plant.
There are much more simpler options available, if you are open to using a different work center(You could default the Standard text key on the work center), if you are open to create a separate transaction for this order type (you could default the Standard text by creating a transaction variant through SHDO), If you are using GuiXT widely in your organization you could write a small simple script to default the Standard text for this order type.
Regards
Narasimhan

Standard Text Key

Hello All
Kindly suggest, is there any posibility to attach STANDARD TXT KEY (CA10) in maintenance plan some where, Its already there in maintenance work order,
but i want the same thing i preventive one, so that no need to go fill same manuallly.
Regards
kapil

Hi
use the standard text key in task lists operation. it can be copied to preventive orders.
Regards
Seenu

How to print equipment documents in shop paper

Hi Gurus,
I`ve maintain DMS to some of the equipments and those were scheduled in maintenace plans.SO whenever work order gets created based on the schedule....documents should also automatically get printed along wih the shop paper.
This is my requirement because users dont want to spend time on printing the documents manually.
Any user exits ?
Help would greatly appreciated with rewards.
Regards,
Vijay

Vijay,
We did something similar but in user-exit IWO10009 (at save).
The reason for using this user-exit and not the BADI described above is because we required a popup box displaying the options for printing. The user could then choose which documents to print.
Pete
[www.pjas.com]

Standard text not printing

Hi all,
I am using /: INCLUDE ZTEST_TEXT OBJECT TEXT ID ST LANGUAGE EN
in my smart form. nothing is printing.What was the mistake in my statement?It gets printed if I use Include text and give same values.But why doesn't it print Standard text value if use above statement in text element.Please help.
I want to use this statement only because I have seen in SAP HELP that this statement gives the latest version of the standard text value.

Hi
Please refer this links
http://help.sap.com/saphelp_nw2004s/helpdata/en/03/7560efcf0d11d3b565006094192fe3/content.htm
regarding smartforms

Standard text in the Window not Printing...

Hi,
I have two pages in a scripts . In the First page I have 10 windows.But in the windows section , I have total 18 windows.
In the windows sections i have a window with name ' WINDOW3'. But it is not there in the Page windows menas it is not there in the First page. But the data is coming.
in the same way , I have one more window 'WINDOW4'. It has standard text. it is also not there in the first page of Page windows. It is not printing.
Why the Standard text is not printing ?
The same Standard text is printing in another script..
Paragraph format ever thing is good ...
if the window is not there in the page window , will it print or not ..?
Regards,
satya.

Hi,
Even though the Window is not there in Page windows, it is printing for some windows like window4.
Why it is happening ...?
Layout is customized but print program is stanadard...
Regards,
satya.

SAPScript: how tu adjust heigh and width of standard text (logo)?

Hi!
how to adjust heigh and width of standard text (logo)?
I do not want to edit the logo, because it is used elsewhere, so I need to adjust heigh and width when using it in a form.
For now stadard text comes over the window. Here is how I use it:
INCLUDE ZHEX-LOGO OBJECT TEXT ID ST
Will reward,
Mindaugas

Hi Mindaugas,
While uploading using RSTXLDMC. You have to maintain your size of the logo.
Go through below mentioned document.
Upload TIFF files to SAPscript texts
Description
The report RSTXLDMC allows a TIFF graphics file to be uploaded from the file system of the R/3 GUI to a standard text in the R/3 word processor SAPscript. (TIFF is a registered trademark of the Aldus Corporation.)
When uploading, the TIFF graphic is converted either into a black and white raster image (parameter type=BMON ) or as a color raster image with a maximum of 256 colors (parameter type=BCOL).
The black and white raster images ( BMON) can be printed using the following printer types:
PCL-5 printer
PostScript printer
Kyocera PRESCRIBE printer
Device type SAPWIN (with SAPlpd 32-bit as of Version 2.41 for Windows NT or Windows 95)
The color raster images (BCOL) can be printed using the following printer types:
PCL-5 printer with color capability (e.g. HP Color LaserJet). Color graphics are not printed properly on monochrome PCL-5 printers (e.g. HP LaserJet 5), because the printer cannot set the color palette as required and does not perform any gray-level conversion.
PostScript printer (color graphics are automatically converted to gray levels on black and white printers using PostScript) Device type SAPWIN (with SAPlpd 32-bit as of Version 2.41 for Windows NT or Windows 95) During TIFF graphic import, the basic set " Baseline TIFF 6.0 " of the TIFF specification 6.0 is supported.
To maintain compatibility with earlier versions of the report RSTXLDMC, it is also possible to convert the TIFF graphic directly into a black and white raster image for a particular printer type when uploading. These are the three printer types PCL-5 (parameter type=PCL ), PostScript (parameter type=POST) and Kyocera PRESCRIBE (parameter type=PRES ). A raster image uploaded in this manner can only be printed using the appropriate printer type.
Besides TIFF raster graphics, direct printer commands in the respective printer language (PCL-5, PostScript or Prescribe) can also be contained in the file which is to be uploaded (printer macros). They are then transferred to the standard text unmodified.
The graphics are output by inserting the standard text into the document which is to be printed, directly or using an INCLUDE command. The printer commands, which for example draw a company logo on the page, are only output if the print request is processed by the printer driver corresponding to the macro type, otherwise they are ignored. Example: A macro of type PCL is contained in a print request. If the request is output to a printer with type HPLJIIID (to which the driver HPL2 is assigned), the macro data is sent to the printer. If the request is printed on a printer of type POSTSCPT (to which the driver POST is assigned), the output of the macro data is suppressed.
In the standard text, the printer commands are inserted between the HEX ... ENDHEX command lines in hex notation. Various report parameters allow the graphic or printer macro to be placed on the page or at the current text position. Note: When the /:HEX command line which precedes the macro appears in the text, a line break is generally made before the graphic is output. The output of the macro therefore begins in the next text line at the left window border of the current page window, as long as a shift to the right is not specified (see below).
If your own printer macros are uploaded and not TIFF files, you must ensure yourself that the normal (text) output of the driver is not impaired when the printer commands are inserted in the output from the uploaded file. The printer drivers pass the data contained in the file to the printer unmodified, therefore without control over the individual actions this triggers on the printer. For example, syntax errors should not be generated by the PostScript commands (type POST), or form feeds should not be contained in the file (unless this was intended) for PCL-5 (type PCL).
Restrictions:
In general, the output of graphics generated via RSTXLDMC from R/3 is not suitable for mass printing (that is, unless you are using the "Graphic resident on printer" feature): the R/3 spooler has to hold significantly more data in its output files. If the graphics occur several times in a spool request, the data also reoccurs. Apart from this, the network is more heavily loaded in sending the increased volume of data to the printer and the printer output is slowed significantly (varies according to printer model) if raster graphics are output as well as the text.
If your graphics reside on your printer during a printing job, the degree of 'correctness' with which they are printed depends on the amount of memory available in your printer. R/3 print drivers are unable to determine whether the amount of memory available is enough! If one of the graphics that you have marked as resident is not displayed, try reloading the graphic and switching off the parameter "Graphic resident on printer".
When printing black and white graphics on PCL-5 printers, image data is compressed in order to greatly reduce the file size.
The output of graphics and macros on PCL-5 printers, PostScript printers and device type SAPWIN (type BMON, BCOL, PCL, POST) is adapted to the page orientation used, that is if landscape is used instead of portrait, the graphic is also turned when output. This is not the case for the PRESCRIBE printers (type BMON, PRES)! With these printers, the graphic is not automatically turned when landscape is used, but appears on the page in the identical position as for portrait. You are therefore recommended not to output raster images when printing in landscape on PRESCRIBE printers.
PRESCRIBE printers do not support the resolutions 200 and 600 dots per inch when printing raster images.
Not all PCL-5 compatible printers support the resolutions 200 and 600 dots per inch when printing raster images.
TIFF graphics with compression type 2 ("CCITT Group 3 1-Dimensional Modified Huffman run length encoding ") can currently not be imported although this is a component of the Baseline TIFF 6.0 specification for monochrome images.
Color TIFF graphics with full color representation (ie. a lot more than 256 colors) are automatically converted into 256 gray levels when uploading with type BCOL.
When TIFF graphics are converted to black and white raster images (type BMON, PCL, POST, PRES) there is no default simulation of gray levels or colors of the original image on the printer (for example, by using different tones of gray). Each pixel of the original image is converted to a white or black pixel on the printer according to its intensity value.
The parameter "Number of TIFF gray levels" does, however, allow a simulation of gray/colour tones of the original image through levels of gray on the printer, when using type PCL, POST or PRES. This parameter is ignored for type BMON.
The conversion of TIFF graphics can be so time-consuming that it is recommendable to execute the report RSTXLDMC in batch processing. Note: in batch, the file is always read from the file system of the application server (ie. not from the file system of the GUI).
The length of an individual text in the text file is limited. When importing TIFF graphics with very large dimensions, especially if more than 2 gray levels are used, a termination can therefore occur when saving the standard text ("EXPORT_TOO_MUCH_DATA"). This restriction can only be avoided by reducing the TIFF graphics. Note: The display of a raster image in Postscript or PRESCRIBE format needs from two to three times as much space as displaying in PCL-5.
When processing very large TIFF images on PostScript printers, a print termination can occur with PS error message "limitcheck". In this case the internal memory of the printer is insufficient to scale the required raster image. This implementation limit cannot be influenced by changing the report parameters when importing.
Requirement
The file which is to be uploaded can contain the following formats/ commands:
Baseline TIFF 6.0 raster image files. The image information of the TIFF file is converted into black and white/color raster images when uploading. Note: As the TIFF format allows a variety of variants, only a basic set of TIFF 6.0 formats is supported here described in the TIFF 6.0 specification as Baseline TIFF 6.0.
PCL : PCL-5, Hewlett Packard Printer Control Language 5 for HP LaserJet 3, 4, 5 series and compatible printers. The data is output by the printer driver HPL2 only.
PRES: Kyocera PRESCRIBE for Kyocera laser printers. The data is output by the printer driver PRES only.
POST: Adobe PostScript or EPS format (encapsulated PostScript ) for PostScript printers. The data is output by the printer driver POST only. In the upload, one of the end-of-file markers (CTRL-D, hex $04) which may be contained in the PostScript file is not transferred.
For PostScript files which contain a bounding box entry (for example, all EPS files) the macro/graphic can be scaled to a size specified by the user. In this case, a small lead text and trailer are generated by the report for the macro data and inserted in the standard text.
Parameters of RSTXLDMC
File name
Path and file name of the file to be uploaded in the file system of the R/3 frontend (dialog processing) or in the file system of the application server (batch processing)
Type
Way which the data contained in the file is to be converted. Possible values are BMON, BCOL, PCL, POST and PRES. With parameter values BMON and BCOL, a TIFF 6.0 file is expected. This is converted into either a black and white raster image (BMON) or a color raster image (BCOL). These raster images are printer-independent and can be printed using various printer types (see above).
With parameter values PCL, POST and PRES, either a TIFF 6.0 file or a file with printer commands in the appropriate printer langauge is expected. If the file is a TIFF file, it is converted into a black and white raster image for the printer type specified in the parameter. The presence of a TIFF file is recognized automatically. If the file is not a TIFF file, the file contents are regarded as the printer macro of the respective type. Data loaded with type PCL, POST or PRES can only be printed on the respective printer type.
Resolution for TIFF raster images
Resolution which should be used when importing a TIFF raster image, in dots per inch (dpi). If an allowed value is entered here, this overrides the resolution information in the TIFF file. The allowed values are:
75 dpi
100 dpi
150 dpi
200 dpi (not for type PRES, for PCL only HP LaserJet 4,5 series)
300 dpi
600 dpi (not for type PRES, for PCL only HP LaserJet 4,5 series)
Changing the resolution affects the size of the graphic on the printer. If a resolution of 300 dpi is stated in the TIFF file and this parameter is set to 75 dpi, the graphic is four times as big when printed as at the outset.
Note: Kyocera PRESCRIBE printers do not support 200 and 600 dpi resolutions.
Note: Not all PCL-5 printers support resolutions 200 and 600 dpi, for example HP LaserJet 3 series does not, but LaserJet 4 and 5 series do.
Graphic Resident on Printer
Normally, graphics that occur more than once in a printing job (a company logo that appears on each page, for example) are sent to the printer repeatedly each time they are needed. In order to avoid this kind of redundancy, you can select this checkbox on the selection screen. The R/3 print driver then stores the graphic in the printer's memory and the printer retrieves the 'resident' graphic memory every time that re-occurs in your job.
Caution: Whether or not the printer correctly reproduces the graphic depends on the amount of memory available in the printer during the printing job! You should avoid using this feature with color graphics since they take up a lot more memory than monochrome graphics.
This parameter can only be used with types "BMON" and "BCOL".
Absolute positioning
Determines whether the macro/graphic is positioned absolutely or is to be output at the current text position. If this checkbox is selected, the graphic is positioned absolutely (parameters "X-position" and "Y-position" are used), if this checkbox is not selected, the graphic is positioned at the current text position (parameters "Reserved height" and "Shift to right" are used)
Absolute X-position
Horizontal position (space from left border) of the macro/graphic, if absolute positioning is required. This is the parameter XPOS of the HEX command.
Absolute Y-position
Vertical position (space from upper border) of the macro/graphic, if absolute positioning is required. This is the parameter YPOS of the HEX command.
Reserve height automatically
If this checkbox is selected, the system automatically inserts the actual height of the graphic during printing into the subsequent "Reserved height" parameter.
Reserved height
If positioned at the current text position, this parameter specifies the horizontal spacing to be reserved for the macro/graphic, which must not be printed with text from the paragraph. This is the parameter HEIGHT of the HEX command.
Shift to right
If positioned at the current text position, this parameter specifies the space between the left border of the macro/graphic and the left border of the page window. If this value is increased, the macro/graphic is shifted to the right. This is the parameter LEFT of the HEX command.
Unit of measurement for positioning
The unit of measurement in which the position values (X,Y, height, shift) are specified. Possible values are CM (centimeters), MM (millimeters), IN (inches), PT (typographic point = 1/72 inch), TW (1/20 point = 1/1440 inch)
Text title
Comment used for the attribute "Title" of the standard text generated as well as as a comment line in the text itself
Line width
Number of columns to be used in the standard text when generating the HEX...ENDHEX command lines. The default value is 132
Text name
Name of the standard text to be generated. If an * character occurs in the name, it is replaced by the value of the parameter "Printer type". For example, if the entry is ZHEX-IMAGE1-* and the printer type = PCL, the text name ZHEX-IMAGE1-PCL is generated. The default value for the name is ZHEX-MACRO-<printer type>, but the standard text can be named as required (take into account customer reserve). Standard texts are client-dependent!
Note: The name of a standard text can be up to 32 characters long !
Text ID
ID of the standard text to be generated. The default value is ST (general standard texts)
Text language
Language key of the standard text to be generated. The default value is the logon language
PostScript scaling
Flag which determines how the macros/graphics of type POST are handled. If set to 'X', the report expects a PostScript comment line in the file
%%BoundingBox llx lly urx ury (e.g. %%BoundingBox -1.5 0 21.4 14.1)
as present, for example, in all EPS files, in which the dimensions and the position of the macro/graphic are specified (if a bounding box comment is not included, 0 0 1 1 is assumed as the default value). This information is then used by the report to insert PostScript commands which scale the macro/graphic to the size specified in the parameters "Width" and "Height" (listed below).
If the flag is set to ' ' (blank), the PostScript file is transferred to the standard text without any additions (any transformations to the coordinate system used by the printer driver must already be contained in the file).
The flag must be set to 'X' for the import of TIFF files for type POST.
Width according to PS scaling
Required width of the macro/graphic if the flag PostScript scaling is set. Can remain at zero for the import of TIFF files, the size is then determined by the resolution of the graphic.
Height according to PS scaling
Required height of the macro/graphic if the flag PostScript scaling is set. Can remain at zero for the import of TIFF files, the size is then determined by the resolution of the graphic.
If you want to scale the PostScript graphic with these parameters, one of the two values, width or height, can be specified with zero. The graphic is then scaled so that the width-to-height ratio remains unchanged and the original graphic is not distorted.
Unit of measurement for PS scaling
Unit of measurement in which the parameters "Width" and "Height" are specified. Possible values are CM (centimeters), MM (millimeters), IN (inches), PT (typographic point = 1/72 inch), TW (1/20 point = 1/1440 inch)
Number of TIFF gray levels
Number of gray tones which are to be used on the printer for displaying the original image. Note: This parameter is only evaluated when using types PCL, POST or PRES!
Possible values are 2,4,9. With the default value 2, each pixel of the original image is converted either to a white or a black pixel on the printer. With the value 4, each pixel of the original image is converted on the printer with 4 pixels, which simulate 4 different gray levels. With the value 9, each pixel of the original image is converted on the printer with 9 pixels which simulate 9 different gray levels.
Note: With values 4 or 9 the resolution of the image is doubled or tripled. The restrictions on the possible resolutions (see previous parameter) then apply for the resulting resolution.
Output
Individual steps of the upload procedure are logged in the report list generated and, if necessary, errors reported. The uploading of TIFF graphics, in particular, is cancelled if there is a variant which is not supported. A message to this effect is then issued. If execution is successful, the report generates a standard text with the key specified in the parameters. If the standard text already exists, a window appears with a warning before the text is overwritten.
Regards,
Ameer Baba.

Standard Text Key printing on Job Ticket Shop Paper

Similar Messages

Maybe you are looking for