Migrate Standard Text via RFC

Hi,
I wanna migrate Standard Textes (ST) from one SAP-System to another via RFC.
Is there a standard Function Module from SAP available ?
or let me know a User FM if possible!
So, I don't wanna store the ST temporary and I don't wanna use the Report RSTXTRAN.
thanks for your help in advance
Franz

done

Similar Messages

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

How to add standard text in PO and how it is maintained ?

How to add standard text (paragraph) in PO and how it is maintained ?

Hi
Please go through this document.which has a step by step
Working with Frequently Used Texts
Use
You can copy texts from various sources to create PO texts:
Standard texts
Certain standard texts are supplied with the system and can be assigned to a purchasing document in Customizing.
The content of some standard texts is predefined by your system administrator.
You can also create standard texts yourself and copy them into purchasing documents.
Master records
Database fields
Activities
Creating Standard Texts
You can create your own standard texts via Tools ® SAPscript ® Standard text.
Inserting Standard Texts
You can insert your standard text on the long text screen via Insert ® Text ® Standard.
For more information, refer to the Basis documentation under BC Word Processing with the SAPscript Editor: Including Texts.
You can display the print preview via Text ® Print ® Print preview.
Inserting Texts from the Master Record
There are three ways of linking texts from a master record with a purchasing document. The relevant settings are made for each text type in Customizing for Purchasing. The indicator in the status column shows the nature of the linkage.
Option                                              Indicator in status column
The text is copied:
It is then independent of the text                 None
in the master record. Changes to
the text in the material master record
have no influence on the text in the document.
The text is displayed only:
It cannot be adopted.                                          N
The text is offered for copying:
It can be copied via Header or Item ® Texts ® Adopt text. (In requisitions: Goto ® Texts ® Adopt text.) Changes made in the master record will also be adopted in the document until such time as you copy the text.
Inserting Texts from Database Fields
You can include the content of a database field at any point in the text on the long text screen. A value specific to the relevant document is displayed in the printed document.
Choose Insert ® Symbols ® Program symbols.
Choose DDIC fields.
Search for the relevant table/structure (in the case of PO items, this is EKPO) and then choose ENTER .
Choose the relevant table field.
Choose Text ® Print preview to see the print preview.
Reward if useful
Aasif

SRM Standard Texts on PO's

In SRM how do you create standard texts, and how do you make them visible for the buyer to place on the PO?
I am able to create a standard text via SO10, but unable to pull it into the PO so that it will be visible to the supplier. Please note these texts are unlimited in length in R/3. What config controls how to pull these into the PO?
thanks for your help!

Hi,
The following is the standatd help available over the issue.
Define Copying Rules for Header Texts
In this step, you define the copying rules for header texts in purchase orders.
You use copying rules to determine which texts can be adopted from other objects (for example, RFQs) to the header text of the purchase order. You link text types in the purchase order with text types in other objects.
You can adopt header texts from the following objects:
RFQ / Quotation
Purchase order
Contract
Vendor master
Activities
Check the predefined links for adopting text.
If you want to modify these links to fit your requirements, proceed as follows:
1. Select the text type required and choose Text linkages.
2. Enter the source object required (for example, RFQ) and the source text (for example, header text).
Regards,

Standard Text Correspondence emailed

Hi,
I hope this is the correct forum for this question.
I've created some standard texts (via SO10) for correspondence in the recruitment module (PA-RC), when I send this to a candidate it produces an email with a PDF document which has the correspondence but the body of the email is empty (other than the attachment). Does anyone know how, or have any suggestions on how to either input the content of the PDF into the body of the email, or how to generate some text in the body?
I've had a look through the forums and can only see this question asked by others, but with no resoultion.
Thanks
Tom

Hi,
Standard text is "<b>client depedent</b>". ( so is SAPScript )
You can transport it with two different ways.
[1]. Program <b>RSTXTCPY</b>
[2]. Create a manual transport of standard text. For this follow these steps.
- Go to transaction SE10. Create a transport request ( workbench ) and task under it.
- Select task and hit button "Disply object list (Shift + F11)".
- On the next screen, switch to change mode.
- Hit button "New entries".
- Now create entry with these values
PgmID = R3TR
Obj = TEXT
Object Name = TEXT,MY_TEXT_NAME,ST,E
here, MY_TEXT_NAME is your standard text created in SO10 and 'E' is language. ( i assume the text is in english ).
Let me know if you have any question.
Regards,
RS

Printing Standard Text in Task List via IA17

We currently use a lot of standard text in task list. However when I run IA17 to display and print a task list, the standard text does not display as the actual text, only the standard text include is displayed.
Is there a way to get the actual text from the standard text to display as well?

Okay, I know I keep answering my own questions, but every answer leads to a new question.
What I've discovered is that if the include statement for the standard text is not in all caps, then it does not print in IA17
For example, we had the include as: Include Z0000438 OBJECT TEXT ID IPRT
However it would appear that the statement needs to be like this: INCLUDE Z0000438 OBJECT TEXT ID IPRT
Has any one else experienced this?
Edited by: Darrell Dorsey on Sep 23, 2010 3:19 PM

How to make a 2-column text in sapscript via standard text?

Hello ABAP Gurus! I'm having a hard time thinking on how I'm going to display a two-column text in the MAIN window of the form Using Form Painter(se71) and Standard Text (SO10). Let's put it this way, the scenario is like you are formatting a paragraph on MS word in to two columns by Format > Columns > Two. What am I going to do with this similar situation in SAP? Any help will be highly appreciated. Thanks

This is nothing with standard text.
Call READ_TEXT FM and here use two variables ,read first line and move to first variable ,again read second line and move to second variable.
Thanks
Seshu

Adding standard Text as long text in QC01 of General data Section

Hi ,
I want to Append standard text in Certificate Profile Creation(QC01)of General data section. Can you suggest any Exit.
Standard Texts created by SO10 Transaction.
Thanks in advance

Dear Raynard,
Raynard Coscolluela wrote:
As far as I can remember the Travel Request was conceptualize to be a simple ESS Form that's why most of the labels here are hard coded and didn't use OTR.
I have to disagree. None of the labels, except this one are hard-coded via Personalization-Means and most Texts come indeed from the OTR, the Label T_ACTYPE_LABEL also has an entry in OTR (see my posts above) but is only non-changable by enhancements because the component configuration was "abused" to overload the OTR and coding in runtime. I still can't really believe this one is intentional....
Raynard Coscolluela wrote:
We don't recommend changing the label text in Web Portal as it can lead into inconsistency incase a new update will be > deliver by SAP into this fields. So yes this is a consider a modification.
This will be an issue since the word "Spesen" which is a specific German one for "Expenses" is juridically wrong if used within a specific MOREI of the Public Sector. But this is another issue and I don't want to elaborate on this one here.
Raynard Coscolluela wrote:
My colleague who participate in this thread is still on vacation and she ask me to assist here.
I see, and I'm glad you did assist here. Give Sally my regards.
This one is answered then, if not really "solved". I'll close the OSS message now.
thanks a lot and best regards,
Lukas

Gettin data from SAP R/3 4.7 unicode sys to SAP ERP non-unicode sys via RFC

We are trying to get data from SAP R/3 4.7 unicode sys to SAP ERP non-unicode sys via RFC. We are reading field from the database via FM and this field got converted by SAP standard Method (CL_ABAP_CONTAINER_UTILITIES=>fill_CONTAINER_C) from structure. When reading this field from ERP sys and converted back to structure using SAP standard Method the value is un-accurate, and different(blank) giving values.
How, if the data originally was a char or numeric it works fine, but not for decimal.
best regards,
Abu-Qaht

I have a range fields with different type of ranges, am saving these to the database by converting them to a string via the same method. I got the same problem so I tried to convert the string to xstring using function SCMS_STRING_TO_XSTRING, before send it to the other system, but the function raised an exception: CX_SY_CONVERSION_CODEPAGE

Standard Text in IORDER

Hi,
we created a
standard text with SO10
which we use in PM order position (text of step) - IW32
example: INCLUDE IS0054_TEXT OBJECT TEXT ID ZPM
when we print this order everything looks OK (whole text was printed)
but when we send this order to extern system via transaction IORD the standard text is not transfered, but the INCLUDE command!
IDOC type IORDER01
segment E1OROPR_LTXT:
TDFORMAT
TDLINE
INCLUDE IS0054_TEST2 OBJECT TEXT ID ZPM
Does anybody know how to "force" SAP to perform the include command instead of copy it into the IDOC ???
kind regards
Jörg

Hi Raghu,
1. in SO10 you can create standard text to be used in several transactions.
We create text name: IS0054_text / text ID: ZPM
content: "This is an example for standard text to be transfered"
2. in transaction IW32 (change existing PM order) we want to use this standard text:
a) click on long text button of "first operation"
b) in text editor - menu: insert > text > standard (Ctrl + Shift + F5)
result:
INCLUDE IS0054_TEST2 OBJECT TEXT ID ZPM
3. in transaction IORD you can transfer PM orders to subsystems via IDOC
if we do that, an IDOC is created including all order information incl. our text
Problem: we expected that in segement E1OROPR_LTXT (Order Operation Long Text segment) our text "This is an example for standard text to be transfered"will be found, but we found only "INCLUDE IS0054_TEST2 OBJECT TEXT ID ZPM"
So why does SAP not follow the "INCLUDE" command and put linked text into IDOC ???
any ideas how to treat SAP to perform this command before creating the IDOC?
kind regards
Jörg

Standard text in smart form

Hi,
can anyone tell me how to include standard text in smart form
Thanks

Procedure
1. To create a text node, call the context menu for that node in the tree structure that shall
receive the text and choose Create Text.
2. Enter a unique name for the node and a node description (for example, letter).
3. On the General Attributes tab choose Include text as text type.
Since you edit a text element, an included text, or a text module exclusively via the
text node, the system stores only information on the selected type. When you
change the text type, the system therefore asks for your confirmation.
4. In the Text key box, identify the include text.
To identify individual text objects, use the search help in this field.
The search help of the Text name field allows you include the attributes of SAPscript
texts into the search.
7. If required, use the Paragraph formats box to format the include text:
The style assigned to the text node contains a format for the standard paragraph ('*'). If you enter a paragraph format in the Standard paragraph field, this format overwrites the style format for all standard paragraphs in the include text that use this paragraph format.
Use the First paragraph field to set a paragraph format for the first paragraph of the
include text. This format also overwrites the format set in the style. If you set the First
paragraph field but leave the Standard paragraph field empty, the system uses the
format set in the First paragraph field for any standard paragraphs in the include text.
6. In the Text node box choose whether you want the text to start in a new paragraph, in a new
line, or directly at the end of the current paragraph.
7. If desired, choose the Output Options tab to maintain the style or box and shading
of the text.
Result
The system displays the node in the tree structure, including its name and description. The
included text is included only at the moment the form is processed.
Regards

Standard Text with ' include' option doesn't work with order created by FM

Hi ABAPers,
Standard text with 'Include' Option does not work with all the Order created via the Function Module SD_ORDER_CREATE_WWW. Where as Order created via VA01 display the Standard text with 'Include'.
On my analysis I found that, Order created via FM use the '*' 'Comment' instead of ':/' 'Command' in the script editor. So the Standard text inserted was considered as a Text instead of command.
Hence issuing print or print preview, the Script display the INCLUDE statement instead of the text.
Can you please let me know the reason and the way to rectify it.
Thanks & Regards
N.Suresh Kumar

Hi.
Make that * command as /: and try in ur program..
It works..
Hope it helps...
Cheers,
Simha.

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.

What authorization required to post idoc from XI via RFC?

Hi all,
I need to post idoc to SAP R/3 system from XI. I have done all the steps correctly. While creating RFC in XI system to connect to the R/3 system, intially I gave my R/3 username and password and tested teh connection. Everything was working fine but when I actually ran the scenario, IDOC was not getting posted in the R/3. But there was no error anywhere.
fianlly after debugging I fould it might be the issue of authorization the the R/3 user i used in the RFC. I then assigned SAP_ALL authorization to my user and posted the iodc again and it started working fine.
Can anyone please tell me what are th exact authorizations/role i need to assign to the r/3 used to use it in RFC and successfully posting the idoc? I dont want to use SAP_ALL authorization in my production environemnt.
Please help.
Regards,
Yash

Hi,
Even i had faced this problem. Whenever I tried to send IDOCs, i used to get an error in SM58, " No authorization to send IDOC of type DEBMDM".
When i got SAP_ALL it worked. However I raised a note with SAP asking for an alternative and this is the reply gave me.
You can get good information on this topic in your online help files.
The following is taken from the document "General Security Measures
(ALE)":
Use the transaction SALE to maintain the ALE configuration, to include setting up the distribution model and setting up ALE user authorizations and profiles. Note the following:
- Be restrictive when assigning the ALE authorizations.
The authorization profile B_ALE_ALL contains the following
authorization objects that are needed for ALE:
Authorizations for ALE
Authorization Description
B_ALE_CGRP ALE Customizing Distribution: Group Activities
B_ALE_LSYS ALE/EDI: Maintaining logical systems
B_ALE_MAST ALE/EDI: Distributing master data
B_ALE_MODL ALE/EDI: Maintaining customer distribution model
B_ALE_RECV ALE/EDI: Receiving IDocs via RFC
B_ALE_REDU ALE/EDI: Generating messages (ex. reduction)
S_PROGRAM ABAP: Program run checks
S_TABU_DIS Table Maintenance (using standard tools such as SM30)
Protect external users and passwords.
For example, for a non-SAP system to send IDocs to a SAP System using transactional RFC, it must also send a SAP user ID and password.
In most cases, the user and password are stored outside of the SAP System. Make sure that this information is not accessible to external systems or programs. (How you can do this is dependent on the system that you have; therefore, you need to refer to the documentation for the system where the information is stored.)
However, I feel assigining the profile S_IDOC_ALL should also be enough. Just try and see.
Regards,
Merrilly

Assign standard text (SO10) in transport request

Hi Experts,
How can i assign the standard text i've created in SO10 to a transport request. Thanks!
Best Regards,
Kurtt

Hi,
Refer note 3355 in OSS for a complete explanation. The SAPscript objects that should be transported must be written in a transport request.
The entries are as follows:
R3TR FORM NAME (NAME = Name of the layout set)
R3TR STYL NAME (NAME = Name of the style)
R3TR TEXT OBJECT,NAME,ID,L
(OBJECT = Text object, NAME = Text name, ID = Text ID, L = Text language)
If you want to transport a number of texts, you can use report RSTXTRAN to insert the individual text keys into a correction. The transport request must be entered and released via the transport system.
Regards
Sudheer

Migrate Standard Text via RFC

Similar Messages

Maybe you are looking for