How to attach logos in smartforms using standard text??

logos in smartforms using standard text

Hi,
After going into SO10>Menu Bar->Include->Graphics-->Select the logo you have to include that in the standard text. ->save->Activate.
IN the smartform.
Create a Logo Node and fill the information in the right side under general attributes.
Name---Standard text name.
Object
Id.
You can upload the logo using SE78.
Thanks,
Sree.

Similar Messages

How to use standard texts in smartforms

Hi Friends,
How to use standard texts in smartforms, ie in scripts we are using standard texts using tr so10.
thanks in advance,
regards,
sharma.

For long text
method1
Create TEXT node- general attributes change text type to include text
then you can input text name/text object/text id/language
method2
create PROGRAM LINE node - use FM READ_TEXT to read it to a internal table
then use LOOP or TABLE node to display it
For TEXT module(For foreign language)
Tr-code:smartforms -- choose Text module(not choose form)--create a text module object
then enter smartform Create TEXT node- general attributes change text type to text module
input the text module name which created by above
btw SO10 is just for Scriptform, in smartforms we use text module to replace SO10

Hi..how we enter standard text for smartform using include text

hi
guru
..how we enter standard text for smartform using include text..
i know only using so10 we write text..
in smartform it asking text-object
text-id,
so what values we should give to get text

Hi,
Do u want to print Standard Text or the Texts that are maintained at the Transaction level.
If it is standard text , then u use text id as ST or if it is Texts that are maintained at the Transaction level then u have to go to that specific transaction and check for that text , then go to text editor ,in the goto menu u have header data where u get the Text id , text name.... , use them in ur smartform in the INCLUDE text.
Further u have the option of text modules in smartforms which act as standard texts, so if u r going for creation of standard texts then its better to use text modules.
Regards,
Shafivullah Mohammad

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

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

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

How to use Standard Text in ALV

How to use Standard Text in ALV header part? Can you please help me by giving the answer?

Hi ,
You can read the Standard text using read_text function module and then print in LV header part.

Need to use standard text in smartforms

Hi,
My requirement is like to use standard text for the address like ...
Company Name
Street, State, PIN
Phone: 111-111-1111
All the above lines should be aligned in the middle and 'Company Name' should be displayed in the bold.
1) I have created the standard text, and included statement in text window as 'INCLUDE XXXX OBJECT TEXT ID ST LANGUAGE EN' but unfortunately it was not displaying anything in the output.
2) I have tried the another method like using the 'Include Text' as a text type in the text window. It was coming but BOLD and center alignment was not coming.
Here my question is why it was not coming in 1) case and if i use READ_TEXT function module will it solve the problem ? in case 2) how can i get all the 3 lines gets center aligned and first line should be bold.
Thanks in advance for your help.

Hi Jaya ,
if u wnt ur Addr first line should come in bold letter than for that
u first *** to "sap smart forms : initial screen" there is option 'STYLE' click on that radiobutton and creat ur own STYLE (Zxxx) on there u vl find al ur answer...
hope this vl help u ,
plz reward paint.
regards
wasim
Edited by: mdwasim akram on Jun 11, 2008 1:09 PM

How to Maintain documentation (se38) using standard text (SO10)

Hi,
I have created standard text using SO10. Now I want to include the standard text in documentation (SE38) section of my ABAP program.
I tried using /: INCLUDE 'YTEST' OBJECT TEXT ID ST LANGUAGE EN
But the standard text is not showing up when I click the documentation icon in the selection screen.
Can you please let me know how to maintain documentation for ABAP programs using Standard Texts.
Thanks in advance.
Sincerely,
Vidya

Hi Mahesh,
In SO10, which format key has been used (AS, /*, /:, *.... to show up in documentation). when you used insert->text-> did you use 'expand immediately' check box. If expand immediately option is used, it won't serve our purpose.
=
(space)
Example
SO10 Yeurope_terms
Inside Yeurope_terms
Terms: For Europe
/* No Tax for Italy
Waiting for your reply.
Sincerely,
Vidya

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

Use standard text (SO10) in report(SE38) to compose the body of email

hello experts,
here i wanna create the body of email with a format, hence i decide to use Standard Text. in this Standard Text, i also maintain some variable such &p_name&( i remember it works in forms,such script and ssf), while i define p_name as 'demo' in the program and try to transfer p_name to standard text, it fails. while i check the output of standard text, it show &p_name& instead of demo.
could anyone tell me how to realize this function?
Thanks in advance.
Desmond

Hi,
try this,
data:w_field(10) type c VALUE '1234'.
DATA:wa_head TYPE THEAD.
data:it_final TYPE TABLE OF tline.
wa_head-tdname = 'Z_SAMPLE'. u201CStandard text,refer screen shot
wa_head-tdid = 'ST'.
wa_head-tdobject = 'TEXT'.
wa_head-tdspras = 'EN'.
CALL FUNCTION 'READ_TEXT'
EXPORTING
CLIENT                        = SY-MANDT
    id                            = wa_head-tdid
    language                      = wa_head-tdspras
    name                          = wa_head-tdname
    object                        = wa_head-tdobject
ARCHIVE_HANDLE                = 0
LOCAL_CAT                     = ' '
IMPORTING
HEADER                        = HEADER
TABLES
    lines                         = it_final
EXCEPTIONS
ID                            = 1
LANGUAGE                      = 2
NAME                          = 3
NOT_FOUND                     = 4
OBJECT                        = 5
REFERENCE_CHECK               = 6
WRONG_ACCESS_TO_ARCHIVE       = 7
OTHERS                        = 8
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
CALL FUNCTION 'REPLACE_TEXTSYMBOL'
EXPORTING
    endline                = 10
FORMATWIDTH            = 72
LANGUAGE               = SY-LANGU
LINEWIDTH              = 132
OPTION_DIALOG          = ' '
REPLACE_PROGRAM        = 'X'
REPLACE_STANDARD       = 'X'
REPLACE_SYSTEM         = 'X'
REPLACE_TEXT           = 'X'
    startline              = 1
IMPORTING
CHANGED                = CHANGED
TABLES
    lines                  = it_final

Using standard texts in reports output

Hi,
Would you please let me know the process of using standard texts created in So10 transaction in reports development. READ_TEXT function module made me to code a lot as per my requirement.
Thanks,
Kumar.

Hi ,
if you want to use READ_TEXT then you have to take help of you functional consultant.Ask him to provide the TEXT ID ,NAME, OBJECT and with the help of these things you can proceed furthur,
If you still need any help.let me know.
Thanks and regards,
Rajeshwar

How to Create a KM folder using Chinese text??????

Hi All,
How to Create a KM folder using Chinese text??????
Plz help..
Regards,
Krish.

Hi Julian,
Frankly speaking, i donot know how to proceed!
we have developed a UICommand (myCopyCommand). As per our requirements, we want to create a KM folder using Chinese text. And see how the copy command works across two different Chinese folders.
I never tried creating KM folder's in another language.
Can you please guide me in this regard.
Waiting for your reply,
Krish.

How to use Standard text in SAP SCRIPTS

Hi all,
Please tell me how can we use the standard text what we have created in SO10 with sap scripts.

Hi Gaurav
You can create standard texts using the transaction SO10. Then to insert these standard texts in the SAPScript choose the menu, Insert->Text->Standard and choose the standard text that you want to choose.
Alternatively, you can display standard texts in your SAP Scripts using the command:
INCLUDE ZSTEXT OBJECT TEXT ID ST LANGUAGE EN
where ZSTEXT refers to the Standard Text name.
Reward pts if found usefull
Regards
Sathish:)

How to print logo in printout using classical report.

Hello Friends,
By using below code i am displaying logo in output using Classical report.
What my problem is it is not displaying in print out.
Please help. or else tell me how to print logo in classical report as well as output print out.
DATA: docking TYPE REF TO cl_gui_docking_container,
      picture_control_1 TYPE REF TO cl_gui_picture,
      url(256) TYPE c ,
      query_table LIKE w3query OCCURS 1 WITH HEADER LINE,
      html_table LIKE w3html OCCURS 1,
      return_code LIKE w3param-ret_code,
      content_type LIKE w3param-cont_type,
      content_length LIKE w3param-cont_len,
      pic_data LIKE w3mime OCCURS 0,
      pic_size TYPE i,
      repid LIKE sy-repid.
repid = sy-repid.
START-OF-SELECTION.
CREATE OBJECT picture_control_1
    EXPORTING
      parent = docking.
CHECK sy-subrc = 0.
CALL METHOD picture_control_1->set_3d_border
    EXPORTING
      border = 5.
CALL METHOD picture_control_1->set_display_mode
    EXPORTING
      display_mode = cl_gui_picture=>display_mode_stretch.
CALL METHOD picture_control_1->set_position
    EXPORTING
      height = 100
      left   = 700
      top    = 1
      width = 200.
"Position
IF url IS INITIAL.
    REFRESH query_table.
    query_table-name = '_OBJECT_ID'.
    " Logo Name
    query_table-value = 'ENJOYSAP_LOGO'.
    APPEND query_table.
    CALL FUNCTION 'WWW_GET_MIME_OBJECT'
      TABLES
        query_string        = query_table
        html                = html_table
        mime                = pic_data
      CHANGING
        return_code         = return_code
        content_type        = content_type
        content_length      = content_length
      EXCEPTIONS
        object_not_found    = 1
        parameter_not_found = 2
        OTHERS              = 3.
    CALL FUNCTION 'DP_CREATE_URL'
      EXPORTING
        type     = 'image'
        subtype = cndp_sap_tab_unknown
        size     = pic_size
        lifetime = cndp_lifetime_transaction
      TABLES
        data     = pic_data
      CHANGING
        url      = url
      EXCEPTIONS
        OTHERS   = 1.
ENDIF.
CALL METHOD picture_control_1->load_picture_from_url
    EXPORTING
      url = url.
WRITE : /'Classical Report Logo'.
Regards,
Phaneendra
Edited by: phaneendra punukollu on Dec 31, 2009 11:38 AM
Code Formatted by: Alvaro Tejada Galindo on Jan 4, 2010 4:52 PM

Hello Nidhi,
Thanks for your sugessition.
Actual we have data from IDOCS and it is maintained in Ztables
and need to dispaly in report ( Service centre - Warranty data ).
The report is completed. So again going to Script means waste of time for us.
So Plz help me if possible in Classical report.
Regards,
Phaneendra

How to use standard text?

hi experts,
i have created a standard text in so01. now i want to use it in my smartform. can anyone help me, plz give the procedure to use that standard text in my form.
thanks in advance for ur responce.

Hi
You cannot use two type to the same text .
Either you have to use TYPE as INCLUDE TEXT for standard text
or TEXT ELEMENT for normal text
One thing you can do if u want to print HI WELCOME together
Then you write both things in different text and print it .
Hope this make some sense to u.
Reward if helpful
Thanks
Krushna

How to use standard text so10

Hello sir
Here the problem is i want get three company adress in the script..
Here i used the satandard text (so10) and created three adress and i went to address window type
There
i written if exgrp =52
<b> include zadress 1 text id language E.
else exgrp=53
<b> include zadress 2 text id langugage e.
this one i did in developement client and i tested and imported threw scc1 its not reflecting while exectuing.
so please tell me how to print the 3 comapny address .. and step by step procedure .
Thankyou
Regars
REDDY

HELLO sir ,
I done wt u said but unable to get that address in script .......
Please check the flow once which done by me ......
firsr created 3 texts and went to the adress window there i used insert option gave standard text ...
in the address window i gave
If P_EXGrp -52( &j_1iexchdr-exgrp&)
include text 1
elseif P_exgrp=53
include text 2
else if P_exgrp=54
endif . this the way i used if condition i .......... if i changed the second statement to Only to "else" its printing the only else part exectuting in script .
and by using RSTXTRAN progarm transported my request . and by scc1 imported but iunable to get Please tell me i didnt change the driver progarm .. selection scrrren &J_1iexchdr-exgrp& is one fileld based on this company code should come ..
Please let me know how to get ....wt changes i should make Please
Thankyou,
Regards

How to attach logos in smartforms using standard text??

Similar Messages

Maybe you are looking for