Smartforms invoice

hi,
i have copied the smartform from lb_bil_invoice to zb_bil_invoice and using the stand program rlb_invoice.
to generate a from using smartforms.
when i place breakpoints on my driver program on the function module ssf_function_module_name and then on entering my form name zb_bil_invoice it was displaying the form.
but all of a sudden when i excute the same driver program it goes back to the transaction vfo3 i was unable to see my form?
culd u give me a suggestion

Hi Hari,
The invoice which you have selected may contain more number of items... which it cannot accomidate in a single page... so it is trying print the remaining items in the next page. But in the NEXT PAGE option of your first page you may have not mentioned any thing.
What you can do is, create a new page, then copy the main window from first page, then in the NEXT PAGE option of the first page and the newly created page select the newly created page.
Thanks and Regards,
Bharat Kumar Reddy.V

Similar Messages

SMARTFORM INVOICE PRINTING

HI,
Kindly could explain me that, how can the invoice in material management, also forward me one sample invoice include steps.
thanks
sujatha

Goto Tcode SMARTFORM, COPY the standard invoice and make the required modifications according to requirement.
SF_LB_INVOICE
SF_LB_INVOICE01
SF_LB_INVOICE_02
LB_BIL_INVOICE
LB_BIL_INVOICE26012000
LB_BIL_INVOICE_140100
LB_BIL_INVOICE_2001200
LB_BIL_INVOICE_25012000
LB_BIL_INVOICE_27012000
Regards,
SaiRam

Smartforms-invoice modification

hi,
kindly help me that, one zinvoice is there is smartforms, i have to change the font size as well as more changes of the particular invoice, let me know how to do the changes. In smartforms i am not familier, help me out pls.
thanks,
sujatha

hi ,
steps:-
1)use txn smartforms ,create a style
2)in that style create paragraph formate , character formate
3)go to smartform , and than corresponding window
4) go to output option & put name of created style
5)go to general attributes and use ur Paragarph formate & character formate
regards
Gaurav Khare

Multiple languages - Smartforms - Invoices

Hi,
I'm having problems getting the following scenario to work:
All the texts on the form are displayed like this::
Polish phrase / foreign translation
Foreign translation: language taken from invoice (i.e. English or German or Italian ).
The problem arises when i want to print Polish characters: 'ąęńś'' etc, some other characters are printed instead, but not hashes ('#').
When a German invoice is to be previewed/printed the OTF instructions contain 'D' language suffix - it screws Polish character set. On the other hand if I modify substitute 'L' for 'D' (thus forcing Polish language) both Polish and German characters are displayed correctly.
Is it possible to configure the system in such a way that regardless of suffix 'D', 'E' or any other the system will always display / print the proper characters in this scenario ? ( system is not unicode )
Cheers,
Bart

Hi,
Project Online comes out-of-the-box with all languages for the project templates, evenif your instance is configured for a specific language. As far as I know, there is no way to "clean" this up. In my point of view, this is not annoying since
only admins can access to the EPT configuration pages.
Hope this helps,
Guillaume Rouyre, MBA, MCP, MCTS |

Smartform Invoice - Credit memo

Hi, I have do an invoice who work in french.
I have translate each window in english and in One window i have a problem :
I have a window and in this window a text : VAT reg. n° :
when i display the invoice RD00 in VF31. He don't display this text ( VAT reg. n° but credit memo.
do you know this problem?
Thanks for your help and your reply.
Spawnrad

Hi, I have do an invoice who work in french.
I have translate each window in english and in One window i have a problem :
I have a window and in this window a text : VAT reg. n° :
when i display the invoice RD00 in VF31. He don't display this text ( VAT reg. n° but credit memo.
do you know this problem?
Thanks for your help and your reply.
Spawnrad

This is a question: Smartforms for RCTI Invoice generation

Hi Guys (and Girls),
I have client who would like to generate an RCTI invoice via smartforms. The system has been configured to immediately print a form once transaction MRRL has been called. However, our attempts to date to get a Smartform to print on creation of the invoice via MRRL has failed miserably.
SAP comes pre-configured to generate RCTI invoices via SAP Script with Form MR_PRINT. This can be changed in config via transaction NACE (Output type MR) to enable a smartform to be selected instead - but the standard program RX08NAST does not appear to be set up to execute smartforms, so all attempts to call the Custom smartform result in SAP Script being called instead. And attempts to change the program from RX08NAST to something like RLB_INVOICE causes the invoice generation program to generate a workflow error and not print anything.
SO, the 8 point question - does anyone know of a program that can be assigned to the RCTI invoice generation output type that will result in a Smartform being called instead if s SAP Script form?
And secondly , the 2 point question, is LB_BIL_INVOICE the best smartform to copy for an RCTI invoice (The RCTI looks the same as a standard Sales Invoice, but I'm concerned because we require vendor data, not customer data, and I don't know if the data structure passed into the LB_BIL_INVOICE form is set up for that)? Can anyone confirm or deny this?
Cheers,
Steve
Message was edited by:
 Stephen Keam

r u printing this invoice from the VF01/02/03
if Yes you can do this as follows.. As i understood.. you are printing a form for Inovice... you need to print invoice details and Venodr and Purchase order Details.
you can achive this as follows..
Note1: in LB_BIL_INVOICE you wont get the vendor details and Purchase Order details... but still you cane achive this bye writing you own select query in Smart form layout - Gobal declaraions>initialization..
Use the RLB_invoice as u r print Program.. Creat your own Layout in SMrtforms ther retrieve the VEnodr and PO Details.. and confiur the output type as Print program is RLB_Invoice and layout is your zLayout.
now you have Invoice details and Vendor and PO details... Prepare a invoice in Smatform asd your Requirement...
In Smartform "Create Form inter face as mentioned in the Print Pogram
JUST this is Exampl only
first call this * Determine smartform function module for invoice
 CALL FUNCTION 'SSF_FUNCTION_MODULE_NAME'
 EXPORTING FORMNAME = LF_FORMNAME
 variant = ' '
 direct_call = ' '
 IMPORTING FM_NAME = LF_FM_NAME
 EXCEPTIONS NO_FORM = 1
 NO_FUNCTION_MODULE = 2
 OTHERS = 3.
 IF SY-SUBRC <> 0.
 Error handling
 CF_RETCODE = SY-SUBRC.
 PERFORM PROTOCOL_UPDATE.
 ENDIF.
then
 Call smartform invoice
 CALL FUNCTION LF_FM_NAME
 EXPORTING
 ARCHIVE_INDEX = TOA_DARA
 ARCHIVE_PARAMETERS = ARC_PARAMS
 CONTROL_PARAMETERS = LS_CONTROL_PARAM
 MAIL_RECIPIENT = LS_RECIPIENT
 MAIL_SENDER = LS_SENDER
 OUTPUT_OPTIONS = LS_COMPOSER_PARAM
 USER_SETTINGS = SPACE
 IS_BIL_INVOICE = LS_BIL_INVOICE
 IMPORTING
 JOB_OUTPUT_INFO = LS_JOB_INFO
 EXCEPTIONS
 FORMATTING_ERROR = 1
 INTERNAL_ERROR = 2
 SEND_ERROR = 3
 USER_CANCELED = 4
 OTHERS = 5.
 IF SY-SUBRC <> 0.
 Error handling
 CF_RETCODE = SY-SUBRC.
 endif.
Close this thread if when u r problem ise solved
Regards
Naresh Reddy K

Chinese Character Printing in Smartform (Different Question)

Hi all,
Can anyone explain to me further the OSS Note 776507 that Anji Reddy Vangala recently posted? It involves the preview and printing of different character sets. Currently I've managed to preview my form correctly, but it still prints out #'s. Do I need to re-assign the fonts to the printer device or something, or do I need to use a different printer? The printer I am currently using is an HP 2100. Please please help, anyone?
EDIT: Probably a better question would be how to map the conversion font of CNSONG to something that can be read by the printer?
A copy of the note for everyone's reference:
OSS Note: 776507
Symptom
Documents printed via SAPscript or SmartForms do not print with correct special characters, e.g. ### prints instead of Japanese or Russian characters. What to do?
Other terms
SAPscript, SmartForms, printing, device types, OTF
Reason and Prerequisites
Help required to choose proper fonts in a SAPscript or SmartForm
Solution
When using SAPscript or SmartForms to print (or email or fax) a form from a business application, many factors influence the outcome of the actual text within the form. All these factors must be checked in order to ensure a correct printout:
1) The language version of the form used to produce the printout.
Example: If you want to print a French invoice, you need to have a FR version of your SAPscript or SmartForms invoice form RVINVOICE01. And the application program must specify the corresponding language key (FR) when calling the SAPscript or SmartForms API.
2) The font selections specified in the form (possibly also in a SAPscript style or SmartStyle used in a form).
Example: In a SAPscript form or a SmartStyle you need to specify HELVE if you want to print German text in Helvetica (or similar) font. If you want to print Japanese text, HELVE is not a valid choice but you need to specify a Japanese font like JPMINCHO in your Japanese form.
3) The output character set of the device type
Every printer in transaction SPAD has a "device type" assigned. Device types used by the spooler for printing support only one single specific output character set. All text from the form has to be converted (using SAP's built-in character conversion mechanism) to this output character set.
A character set can typically support either a single language (e.g. Shift-JIS which supports only Japanese) or a set of languages (e.g. ISO 8859-1, which supports Western-European languages). It is possible that a given language (such as German) can be supported by several output character sets, e.g. you may use either ISO 8895-1 (Latin-1) or ISO 8859-2 (Latin-2) to represent German text. This is so because both character sets contain the special characters used in German.
Example: HPLJ4000 is a HP LaserJet device type supporting the ISO 8859-1 (Latin-1) character set. ISO 8859-1 can be used to represent e.g. Dutch, English, French, German, Spanish, Swedish but NOT Russian or Japanese.
As a consequence, it is ok to use HPLJ4000 to print English, German French etc. but not for Japanese or Russian.
4) The set of available printer fonts for a given device type
When formatting a document, SAPscript and SmartForms perform an automatic mapping of the font definitions in the form (e.g. "HELVE 14 point bold") and the available printer fonts of the device type. A replacement printer font is chosen, should the specified font selection not be available in the device type. Now this replacement can be problematic if a language-specific font, such as Chinese CNSONG, is specified in a form and it gets replaced by a font which does not support this language, e.g. COURIER.
To solve this problem, font families in SE73 have language attribute assigned, e.g. some fonts are characterized as being suitable only for certain languages. And when a replacement has to be chosen because the original font from the form is not available in the device type, a replacement font is chosen which has the same language attributes.
If no fonts for the language in question exist in the device type, the resulting font will not be able to print the special characters and you will see "wrong" output characters in the printout.
Note on SAPscript/SmartForms Print Preview:
The OTF Print Preview available in Windows GUI (e.g. from transaction SP01) will sometimes not show the "wrong" characters which appear on the final printout. Here is the reason: since the Print Preview runs in Windows environment, it will use Windows fonts to represent the actual printer fonts. A Windows font typically has more available characters (i.e. covers more character sets) than are actually available in a printer's resident font.
A typical example where the Print Preview will differ from the printout is here: if you have a Chinese PCL5 printer such as CNHPLJ4 and use the Western Latin font COURIER in your document, the print preview will show you Chinese characters if you (by accident) tried to format Chinese characters in COURIER font. This is because Windows will automatically choose a font that can output Chinese characters (which is actually not Courier). But when you print the job on an actual PCL5 printer with resident Western and Chinese fonts, the Courier font will not print any Chinese characters but Western special characters instead, because the printer's resident Courier font does not include Chinese characters.
Rule of thumb: all Asian device types (e.g. CNHPLJ4, JPHPLJ4, JPPOST, KPHPLJ4) support not only Asian fonts but also COURIER, HELVE and TIMES fonts. But these Latin fonts can only be used to print English text, not Chinese/Japanese/Korean characters.
Which fonts are suitable for a given language?
Language(s): Font family to use in a form:
Latin-1 (Western Europe/Americas) *******
DE,EN,FR,ES,NL,SV COURIER, HELVE, TIMES
(LETGOTH, LNPRINT)
Latin-2 (Central Europe) ****************
PL, CZ COURIER, HELVE, TIMES
ISO 8859-4 (Baltic) *********************
ET, LT, LV COURIER, HELVE, TIMES
ISO 8859-5 (Cyrillic) *******************
BG, RU, SR, UK COURCYR, HELVCYR, TIMECYR
ISO 8859-7 (Greek) **********************
EL COUR_I7, HELV_I7, TIME_I7
ISO 8859-8 (Hebrew) *********************
HE COURIER, HELVE, TIMES
ISO 8859-9 (Turkish) ********************
TR COURIER, HELVE, TIMES
Simplified Chinese **********************
ZH CNHEI, CNKAI, CNSONG
Japanese ********************************
JA JPMINCHO, DBMINCHO, DBGOTHIC
Korean **********************************
KP KPBATANG, KPDODUM, KPGULIM
KPGUNGSE, KPSAMMUL
Traditional Chinese *********************
ZF TWDPHEI, TWMING, TWSONG
Thai ************************************
TH THANGSAN, THDRAFT, THVIJIT
Arabic (Unicode systems only) ***********
AR ANDALE_J
Verify your output by examining the OTF data
When analysing printing problems of this type, be sure to check the OTF data which gets produced by SAPscript or SmartForms. OTF or "Output Text Format" is the intermediate page-description format generated from SAPscript or SmartForms. OTF will contain the final printer font names and character set/language identifiers which help to solve the problem. OTF will even name the form and the language of the form used to create the output.
The easiest way to do this is to create a spool request from your application, run transaction SP01, use menu
Goto->Display Requests->Settings
and choose
Display Mode: Raw
Now display your spool request. If this is a SAPscript or SmartForms spool request, you will see OTF data. Each line represents one OTF command, every command starts with a 2-character cmd identifier and possibly some cmd parameters follow.
Here is an excerpt from a sample OTF file where we highlight the most interesting commands:
//XHPLJ8000 0700 00000000001
IN04EALEXTEST_ZEBRA
IN05%PAGE1
OPDINA4 P 144 240 1683811906000010000100001
IN06%WINDOW2
MT0024401289
CP11000000E
FCHELVE 120 00109XSF100SF101110000067E X
UL +0000000000000
SW00067
CT00000000
ST0453037Dieses SF hat Stil ALEXTEST_ZEBRA mit
The 1st line with the // (Control) command reveals the device type usedto print: HPLJ8000
//XHPLJ8000 0700 00000000001
The 2nd line (IN = Info command) shows the name and (internal 1-char)language key of the form:
IN04EALEXTEST_ZEBRA
In this case it is the English (E = EN) SmartForm ALEXTEST_ZEBRA
The OP-line (OP = Open Page) gives the page format used in the form, it is DINA4 Portrait orientation:
OPDINA4 P 144 240 1683811906000010000100001
The CP (CodePage) cmd shows the SAP system codepage used to code the text and the active language. In our case it is codepage 1100 and language E = EN = English.
CP11000000E
Finally, the FC-cmd (Font Call) lists a printer font selected within SmartForms. Please note that every SmartForm has a designated default SmartStyle under "Form Attributes->Output Options". In addition, every text node can have a SmartStyle attached (which will override the definitions from the default style for the text). In our case the resulting printer font that was selected is HELVE 12.0 pt bold-off, italic-off.
FCHELVE 120 00109XSF100SF101110000067E X

Hi,
there a different things to know.
I produce sapscript forms with cinese and english characters for frontend / backend and archiv printing.
Please check:
Editor displays ###: You have to install the chinese language in your e.g. windows-system to display them.
Script: You have to chose the the font family "CNSONG" (customized for chinese simplified and LATIN).
Transaction I18N: May you have to set correct subfonts for the unicode areas (Cascading fonts, Standard is Courier).
You can print in different ways:
For archiv/PDF: Install the unicode truetype font with chinese characters for the pdf-converter.
For Frontend: Use the Frontendprinter SAPWIN or SAPWIN*CF (Cascading Font) to send it to the gui (note: SAPLPD does not support it, use the newer technology.....)
Backend printing: POSTSCRIPT is not yet implemented :-((
PLease note: What you see in spool / print preview is a simulation of the possible print, but backend print is not frontend preview!!!!
Regards,
Christian

Unable to print directly from vf03 txn after converting smartform into PDF

Dear All,
I have converted ond smartform into pdf.now when i am trying to print one document using vf03 transaction whatever button i click(ex-print preview/print) it is asking to save the pdf as local file. but i want to print that document as pdf directly from vf03 without saving it into local file.
I am giving you the code below:-
(all modification done by me are in BOLD)
 Print of a invoice by SAPscript SMART FORMS *
REPORT zrlb_invoice5.
declaration of data
INCLUDE zrlb_invoice_data_declare5.
*INCLUDE ZRLB_INVOICE_DATA_DECLARE.
*INCLUDE rlb_invoice_data_declare.
definition of forms
INCLUDE zrlb_invoice_form015.
*INCLUDE ZRLB_INVOICE_FORM01.
*INCLUDE rlb_invoice_form01.
INCLUDE zrlb_print_forms5.
*INCLUDE ZRLB_PRINT_FORMS.
*INCLUDE rlb_print_forms.
START-OF-SELECTION.
 FORM ENTRY
FORM entry USING return_code us_screen.
DATA: lf_retcode TYPE sy-subrc.
CLEAR retcode.
xscreen = us_screen.
PERFORM processing USING us_screen
 CHANGING lf_retcode.
IF lf_retcode NE 0.
 return_code = 1.
ELSE.
 return_code = 0.
ENDIF.
ENDFORM. "ENTRY
 FORM PROCESSING *
FORM processing USING proc_screen
 CHANGING cf_retcode.
DATA: lv_medium LIKE tnapr-nacha.
DATA: lwa_print_data_to_read TYPE lbbil_print_data_to_read.
DATA: lwa_bil_invoice TYPE lbbil_invoice.
DATA: lf_fm_name TYPE rs38l_fnam.
DATA: lwa_control_param TYPE ssfctrlop.
DATA: lwa_composer_param TYPE ssfcompop.
DATA: lwa_recipient TYPE swotobjid.
DATA: lwa_sender TYPE swotobjid.
DATA: lf_formname TYPE tdsfname.
DATA: lwa_addr_key LIKE addr_key.
DATA: ls_dlv-land LIKE vbrk-land1.
DATA:lv_job_output_info TYPE ssfcrescl,
 lv_document_output_info TYPE ssfcrespd,
 lv_job_output_options TYPE ssfcresop,
 lv_bin_filesize TYPE i,
 gt_docs TYPE STANDARD TABLE OF docs,
 gt_lines TYPE STANDARD TABLE OF tline,
 gt_otf TYPE TABLE OF itcoo, " OTF Structure
 lv_name TYPE string VALUE 'INVOICE',
 lv_guiobj TYPE REF TO cl_gui_frontend_services,
 lv_path TYPE string VALUE 'D:\',
 lv_fullpath TYPE string VALUE 'D:\INVOICE',
 lv_filter TYPE string,
 lv_uact TYPE i,
 lv_filename TYPE string,
++lv_fm_name TYPE rs38l_fnam. +*****************************************
SmartForm from customizing table TNAPR
lf_formname = tnapr-sform.
lv_medium = tnapr-nacha.
determine print data
PERFORM set_print_data_to_read USING lf_formname
 CHANGING lwa_print_data_to_read
 cf_retcode.
IF cf_retcode EQ 0.
select print data
 PERFORM get_data USING lwa_print_data_to_read
 CHANGING lwa_addr_key
 ls_dlv-land
 lwa_bil_invoice
 cf_retcode.
ENDIF.
IF cf_retcode EQ 0.
 PERFORM set_print_param USING lwa_addr_key
 ls_dlv-land
 CHANGING lwa_control_param
 lwa_composer_param
 lwa_recipient
 lwa_sender
 cf_retcode.
ENDIF.
IF cf_retcode EQ 0.
determine smartform function module for invoice
 CALL FUNCTION 'SSF_FUNCTION_MODULE_NAME'
 EXPORTING formname = lf_formname
 variant = ' '
 direct_call = ' '
 IMPORTING fm_name = lf_fm_name
 EXCEPTIONS no_form = 1
 no_function_module = 2
 OTHERS = 3.
 IF sy-subrc NE 0.
error handling
 cf_retcode = sy-subrc.
 PERFORM protocol_update.
 ENDIF.
ENDIF.
IF cf_retcode EQ 0.
 PERFORM check_repeat.
 IF lwa_composer_param-tdcopies EQ 0.
 nast_anzal = 1.
 ELSE.
 nast_anzal = lwa_composer_param-tdcopies.
 ENDIF.
 lwa_composer_param-tdcopies = 1.
 DO nast_anzal TIMES.
In case of repetition only one time archiving
 IF sy-index GT 1 AND nast-tdarmod EQ 3.
 nast_tdarmod = nast-tdarmod.
 nast-tdarmod = 1.
 lwa_composer_param-tdarmod = 1.
 ENDIF.
 IF sy-index NE 1 AND repeat IS INITIAL.
 repeat = 'X'.
 ENDIF.
call smartform invoice
 CALL FUNCTION lf_fm_name
 EXPORTING
 archive_index = toa_dara
 archive_parameters = arc_params
 control_parameters = ls_control_param
 mail_appl_obj =
 mail_recipient = ls_recipient
 mail_sender = ls_sender
 output_options = ls_composer_param
 user_settings = space
 is_bil_invoice = ls_bil_invoice
 is_nast = nast
 is_repeat = repeat
 importing document_output_info =
 job_output_info =
 job_output_options =
 EXCEPTIONS formatting_error = 1
 internal_error = 2
 send_error = 3
 user_canceled = 4
 OTHERS = 5.
 lwa_control_param-getotf = 'X'.
 lwa_control_param-no_dialog = 'X'.
 lwa_control_param-device = 'PRINTER'.
 CALL FUNCTION lf_fm_name
 EXPORTING
 archive_index = toa_dara
Begin of Changes 24/10/2007*
ARCHIVE_INDEX_TAB =*
 ARCHIVE_PARAMETERS = arc_params*
 control_parameters = lwa_control_param
MAIL_APPL_OBJ =*
 MAIL_RECIPIENT = lwa_recipient*
 MAIL_SENDER = lwa_sender*
*End of changes 04/12/2007
 output_options = lwa_composer_param
 user_settings = 'X'
 is_bil_invoice = lwa_bil_invoice
 is_nast = nast
 is_repeat = repeat
 iv_medium = lv_medium
Begin OF Changes 04/12/2007*
IMPORTING
 document_output_info = lv_document_output_info
 job_output_info = lv_job_output_info
 *job_output_options = lv_job_output_options *
End Of Changes 04/12/2007*
EXCEPTIONS
 formatting_error = 1
 internal_error = 2
 send_error = 3
 user_canceled = 4
 OTHERS = 5.
 CALL FUNCTION lf_fm_name
 EXPORTING
 ARCHIVE_INDEX = toa_dara
ARCHIVE_INDEX_TAB =
 ARCHIVE_PARAMETERS = arc_params
 CONTROL_PARAMETERS = lWA_control_param
MAIL_APPL_OBJ =
 MAIL_RECIPIENT = lwa_recipient
 MAIL_SENDER = lwa_sender
 OUTPUT_OPTIONS = lwa_composer_param
 USER_SETTINGS = space
 IS_BIL_INVOICE = LWA_BIL_INVOICE
 IS_NAST = nast
 IS_REPEAT = repeat
 IV_MEDIUM = lv_medium
IMPORTING
DOCUMENT_OUTPUT_INFO =
JOB_OUTPUT_INFO =
JOB_OUTPUT_OPTIONS =
EXCEPTIONS
FORMATTING_ERROR = 1
INTERNAL_ERROR = 2
SEND_ERROR = 3
USER_CANCELED = 4
OTHERS = 5
 gt_otf[] = lv_job_output_info-otfdata[].
 CALL FUNCTION 'CONVERT_OTF'
 EXPORTING
 FORMAT = 'PDF'
 MAX_LINEWIDTH = 132
 ARCHIVE_INDEX = ' '*
 COPYNUMBER = 0*
 ASCII_BIDI_VIS2LOG = ' '*
 IMPORTING
 BIN_FILESIZE = lv_bin_filesize
 BIN_FILE =*
 TABLES
 otf = gt_otf
 lines = gt_lines
 EXCEPTIONS*
 ERR_MAX_LINEWIDTH = 1*
 ERR_FORMAT = 2*
 ERR_CONV_NOT_POSSIBLE = 3*
 ERR_BAD_OTF = 4*
 OTHERS = 5*
 IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO*
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.*
 ENDIF.
*.......................GET THE FILE NAME TO STORE.........
 CONCATENATE 'smrt' '.pdf' INTO lv_name.
 CREATE OBJECT lv_guiobj.
 CALL METHOD lv_guiobj->file_save_dialog
 EXPORTING
 default_extension = 'pdf'
 default_file_name = lv_name
 file_filter = lv_filter
 CHANGING
 filename = lv_name
 path = lv_path
 fullpath = lv_fullpath.
 user_action = lv_uact.*
 IF lv_uact = lv_guiobj->action_cancel.
 EXIT.
 ENDIF.*
 MOVE lv_fullpath TO lv_filename.
 CALL METHOD cl_gui_frontend_services=>gui_download
 EXPORTING
 BIN_FILESIZE = lv_bin_filesize
 filename = lv_fullpath
 FILETYPE = 'BIN'
 APPEND = SPACE
 WRITE_FIELD_SEPARATOR = SPACE
 HEADER = '00'
 TRUNC_TRAILING_BLANKS = SPACE
 WRITE_LF = 'X'
 COL_SELECT = SPACE
 COL_SELECT_MASK = SPACE
 DAT_MODE = SPACE
 CONFIRM_OVERWRITE = SPACE
 NO_AUTH_CHECK = SPACE
 CODEPAGE = SPACE
 IGNORE_CERR = ABAP_TRUE
 REPLACEMENT = '#'
 WRITE_BOM = SPACE
 TRUNC_TRAILING_BLANKS_EOL = 'X'
IMPORTING
 FILELENGTH =
 changing
 data_tab = gt_lines.
EXCEPTIONS
 FILE_WRITE_ERROR = 1
 NO_BATCH = 2
 GUI_REFUSE_FILETRANSFER = 3
 INVALID_TYPE = 4
 NO_AUTHORITY = 5
 UNKNOWN_ERROR = 6
 HEADER_NOT_ALLOWED = 7
 SEPARATOR_NOT_ALLOWED = 8
 FILESIZE_NOT_ALLOWED = 9
 HEADER_TOO_LONG = 10
 DP_ERROR_CREATE = 11
 DP_ERROR_SEND = 12
 DP_ERROR_WRITE = 13
 UNKNOWN_DP_ERROR = 14
 ACCESS_DENIED = 15
 DP_OUT_OF_MEMORY = 16
 DISK_FULL = 17
 DP_TIMEOUT = 18
 FILE_NOT_FOUND = 19
 DATAPROVIDER_EXCEPTION = 20
 CONTROL_FLUSH_ERROR = 21
 NOT_SUPPORTED_BY_GUI = 22
 ERROR_NO_GUI = 23
 others = 24
 IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO*
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.*
 ENDIF.
 Else.
 IF sy-subrc NE 0.*
error handling
 cf_retcode = sy-subrc.
 PERFORM protocol_update.
get SmartForm protocoll and store it in the NAST protocoll
 PERFORM add_smfrm_prot.
 ENDIF.
 ENDDO.
 lwa_composer_param-tdcopies = nast_anzal.
 IF NOT nast_tdarmod IS INITIAL.
 nast-tdarmod = nast_tdarmod.
 CLEAR nast_tdarmod.
 ENDIF.
 ENDIF.
get SmartForm protocoll and store it in the NAST protocoll
PERFORM ADD_SMFRM_PROT.
ENDFORM. "PROCESSING
kindly give me a sloution.

Hi,
Check for the print mode in the print options and set it as 3- print and archive .
Regards,
Ram

To find name for standard smartform of purchase order in Tcode me21n.......

Please do not offer rewards
Hi Abapers,
 I had doubt, regarding how to find the name of standard smartform available for purchase order in tcode - ME21N.
 After executing ME21N, n print preview i get a form without logo. So i want to customize the form according to my clients requirement.For this i want to know the Smartform name, so tat i can copy to 'Z.....' and make the customization.
 Can anybody assist me overcome this problem of how to find out the name of smartform without knwing functionmodule name also....
 <<Text removed>>
Advanced Thanks..............
Edited by: Matt on Mar 25, 2009 10:26 AM

DESIGN ONE SMARTFORM AS PERUR NEED.
DRIVER PROGRAM FOR THISIS
*& ZSAPFM06P
&---- Print of a PO by SMART FORMS *
*& Purchase order printing program
&---- FORM ENTRY
SmartForm from customizing table TNAPR
determine smartform function module for invoice
 variant = ' '
 direct_call = ' '
control-no_open = 'X'.
control-no_close = 'X'.
call smartform invoice
 archive_index = toa_dara
 archive_parameters = arc_params
 mail_appl_obj =
 mail_recipient = ls_recipient
 mail_sender = ls_sender
 output_options = ls_composer_param
 is_bil_invoice = ls_bil_invoice
 is_repeat = repeat
 importing job_output_info = ls_job_info
 document_output_info =
 job_output_options =
error handling
 message id sy-msgid type sy-msgty number sy-msgno
 with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
analyse internal error table of Smart Forms
add your handling
REPORT ZSAPFM06P.
TABLES: TNAPR,
 nast.
DATA: lf_fm_name TYPE rs38l_fnam,
 lf_formname TYPE tdsfname,
 control type ssfctrlop,
 errtab type tsferror.
FORM entry_neu using ent_retco ent_screen.
lf_formname = tnapr-sform.
 CALL FUNCTION 'SSF_FUNCTION_MODULE_NAME'
 EXPORTING formname = lf_formname
 IMPORTING fm_name = lf_fm_name
 EXCEPTIONS no_form = 1
 no_function_module = 2
 OTHERS = 3.
 IF sy-subrc <> 0.
 message id sy-msgid type sy-msgty number sy-msgno
 with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
 ENDIF.
control-no_dialog = 'X'.
control-preview = 'X'.
control-langu = sy-langu.
 CALL FUNCTION lf_fm_name
 EXPORTING
 control_parameters = control
 user_settings = 'X'
 is_nast = nast
 EXCEPTIONS formatting_error = 1
 internal_error = 2
 send_error = 3
 user_canceled = 4
 OTHERS = 5.
if sy-subrc <> 0.
 ent_retco = 0.
else.
 ent_retco = 0.
endif.
call function 'SSF_READ_ERRORS'
 importing
 errortab = errtab.
if not errtab is initial.
endif.
ENDFORM.
DEFINE UR PROGRAM NAME AND SMARTFORM NAME IN NACE.

Preview and Printing of Chinese Characters in Smartform

Hi everyone!
I have a development that needs to output in Smartform a combination of Chinese and English characters, on an English Logon,
When I debug the form, the Chinese characters are shown in the debug screen, but when it is previewed or printed, it shows garbage. Can anyone help me with this?
Thanks a lot! Points for any helpful answer!

Hi
check this OSS Note
OSS Note: 776507
Symptom
Documents printed via SAPscript or SmartForms do not print with correct special characters, e.g. ### prints instead of Japanese or Russian characters. What to do?
Other terms
SAPscript, SmartForms, printing, device types, OTF
Reason and Prerequisites
Help required to choose proper fonts in a SAPscript or SmartForm
Solution
When using SAPscript or SmartForms to print (or email or fax) a form from a business application, many factors influence the outcome of the actual text within the form. All these factors must be checked in order to ensure a correct printout:
1) The language version of the form used to produce the printout.
Example: If you want to print a French invoice, you need to have a FR version of your SAPscript or SmartForms invoice form RVINVOICE01. And the application program must specify the corresponding language key (FR) when calling the SAPscript or SmartForms API.
2) The font selections specified in the form (possibly also in a SAPscript style or SmartStyle used in a form).
Example: In a SAPscript form or a SmartStyle you need to specify HELVE if you want to print German text in Helvetica (or similar) font. If you want to print Japanese text, HELVE is not a valid choice but you need to specify a Japanese font like JPMINCHO in your Japanese form.
3) The output character set of the device type
Every printer in transaction SPAD has a "device type" assigned. Device types used by the spooler for printing support only one single specific output character set. All text from the form has to be converted (using SAP's built-in character conversion mechanism) to this output character set.
A character set can typically support either a single language (e.g. Shift-JIS which supports only Japanese) or a set of languages (e.g. ISO 8859-1, which supports Western-European languages). It is possible that a given language (such as German) can be supported by several output character sets, e.g. you may use either ISO 8895-1 (Latin-1) or ISO 8859-2 (Latin-2) to represent German text. This is so because both character sets contain the special characters used in German.
Example: HPLJ4000 is a HP LaserJet device type supporting the ISO 8859-1 (Latin-1) character set. ISO 8859-1 can be used to represent e.g. Dutch, English, French, German, Spanish, Swedish but NOT Russian or Japanese.
As a consequence, it is ok to use HPLJ4000 to print English, German French etc. but not for Japanese or Russian.
4) The set of available printer fonts for a given device type
When formatting a document, SAPscript and SmartForms perform an automatic mapping of the font definitions in the form (e.g. "HELVE 14 point bold") and the available printer fonts of the device type. A replacement printer font is chosen, should the specified font selection not be available in the device type. Now this replacement can be problematic if a language-specific font, such as Chinese CNSONG, is specified in a form and it gets replaced by a font which does not support this language, e.g. COURIER.
To solve this problem, font families in SE73 have language attribute assigned, e.g. some fonts are characterized as being suitable only for certain languages. And when a replacement has to be chosen because the original font from the form is not available in the device type, a replacement font is chosen which has the same language attributes.
If no fonts for the language in question exist in the device type, the resulting font will not be able to print the special characters and you will see "wrong" output characters in the printout.
Note on SAPscript/SmartForms Print Preview:
The OTF Print Preview available in Windows GUI (e.g. from transaction SP01) will sometimes not show the "wrong" characters which appear on the final printout. Here is the reason: since the Print Preview runs in Windows environment, it will use Windows fonts to represent the actual printer fonts. A Windows font typically has more available characters (i.e. covers more character sets) than are actually available in a printer's resident font.
A typical example where the Print Preview will differ from the printout is here: if you have a Chinese PCL5 printer such as CNHPLJ4 and use the Western Latin font COURIER in your document, the print preview will show you Chinese characters if you (by accident) tried to format Chinese characters in COURIER font. This is because Windows will automatically choose a font that can output Chinese characters (which is actually not Courier). But when you print the job on an actual PCL5 printer with resident Western and Chinese fonts, the Courier font will not print any Chinese characters but Western special characters instead, because the printer's resident Courier font does not include Chinese characters.
Rule of thumb: all Asian device types (e.g. CNHPLJ4, JPHPLJ4, JPPOST, KPHPLJ4) support not only Asian fonts but also COURIER, HELVE and TIMES fonts. But these Latin fonts can only be used to print English text, not Chinese/Japanese/Korean characters.
Which fonts are suitable for a given language?
Language(s):            Font family to use in a form:
Latin-1 (Western Europe/Americas) *******
DE,EN,FR,ES,NL,SV       COURIER, HELVE, TIMES
                        (LETGOTH, LNPRINT)
Latin-2 (Central Europe) ****************
PL, CZ                  COURIER, HELVE, TIMES
ISO 8859-4 (Baltic) *********************
ET, LT, LV              COURIER, HELVE, TIMES
ISO 8859-5 (Cyrillic) *******************
BG, RU, SR, UK          COURCYR, HELVCYR, TIMECYR
ISO 8859-7 (Greek) **********************
EL                      COUR_I7, HELV_I7, TIME_I7
ISO 8859-8 (Hebrew) *********************
HE                      COURIER, HELVE, TIMES
ISO 8859-9 (Turkish) ********************
TR                      COURIER, HELVE, TIMES
Simplified Chinese **********************
ZH                      CNHEI, CNKAI, CNSONG
Japanese ********************************
JA                      JPMINCHO, DBMINCHO, DBGOTHIC
Korean **********************************
KP                      KPBATANG, KPDODUM, KPGULIM
                        KPGUNGSE, KPSAMMUL
Traditional Chinese *********************
ZF                      TWDPHEI, TWMING, TWSONG
Thai ************************************
TH                      THANGSAN, THDRAFT, THVIJIT
Arabic (Unicode systems only) ***********
AR                      ANDALE_J
Verify your output by examining the OTF data
When analysing printing problems of this type, be sure to check the OTF data which gets produced by SAPscript or SmartForms. OTF or "Output Text Format" is the intermediate page-description format generated from SAPscript or SmartForms. OTF will contain the final printer font names and character set/language identifiers which help to solve the problem. OTF will even name the form and the language of the form used to create the output.
The easiest way to do this is to create a spool request from your application, run transaction SP01, use menu
Goto->Display Requests->Settings
and choose
Display Mode: Raw
Now display your spool request. If this is a SAPscript or SmartForms spool request, you will see OTF data. Each line represents one OTF command, every command starts with a 2-character cmd identifier and possibly some cmd parameters follow.
Here is an excerpt from a sample OTF file where we highlight the most interesting commands:
//XHPLJ8000    0700 00000000001
IN04EALEXTEST_ZEBRA
IN05%PAGE1
OPDINA4 P 144 240 1683811906000010000100001
IN06%WINDOW2
MT0024401289
CP11000000E
FCHELVE 120 00109XSF100SF101110000067E X
UL +0000000000000
SW00067
CT00000000
ST0453037Dieses SF hat Stil ALEXTEST_ZEBRA mit
The 1st line with the // (Control) command reveals the device type usedto print: HPLJ8000
//XHPLJ8000    0700 00000000001
The 2nd line (IN = Info command) shows the name and (internal 1-char)language key of the form:
IN04EALEXTEST_ZEBRA
In this case it is the English (E = EN) SmartForm ALEXTEST_ZEBRA
The OP-line (OP = Open Page) gives the page format used in the form, it is DINA4 Portrait orientation:
OPDINA4 P 144 240 1683811906000010000100001
The CP (CodePage) cmd shows the SAP system codepage used to code the text and the active language. In our case it is codepage 1100 and language E = EN = English.
CP11000000E
Finally, the FC-cmd (Font Call) lists a printer font selected within SmartForms. Please note that every SmartForm has a designated default SmartStyle under "Form Attributes->Output Options". In addition, every text node can have a SmartStyle attached (which will override the definitions from the default style for the text). In our case the resulting printer font that was selected is HELVE 12.0 pt bold-off, italic-off.
FCHELVE   120 00109XSF100SF101110000067E X
Regards
Anji

Text should appear both in chinese and english language in smartform-Urgen

Hi All,
In my requirement in smart form, the standard text and values to be printed should appear both in english and chinese language.
When my login language is EN(English), I cannot able to see the chinese text , but only the english text.
If login in Chinese language, I can able to see the both the Chinese and English text in print preview, even then in printout the chinese text is missing.
Please let me know what will be the problem.
What printer i can use to get both chinese and english text.
Thanks in advance
Saravana

Hi
See the attached 2 OSS notes for your problem
OSSNote:960341
Symptom
In some device types (e.g HPLJ4, HPLJ5) you experience non-uniform character spacing in the PDF document after the PDF conversion of SAPscript or Smart Forms documents, using HELVE or TIMES fonts. You want to know the reason.
Other terms
CONVERT_OTF, SAPscript, Smart Forms
Reason and Prerequisites
The problem is not due to an error in the PDF converter but due to the fact, that the printer font, underlying the device type (e.g. Univers or CG Times in PCL-5 device types), is not available for the PDF converter and is either not available in Adobe Reader. The PDF converter has to try to simulate the layout of the printer font by means of a font which is predefined in Adobe Reader. This is done by assigning the letter widths of the printer font to the font used in Adobe Reader.
The PDF file contains a table with letter widths, used by Adobe Reader in the output of text, for each used printer font (except PostScript fonts).
Example:
%Charwidth values from HP4300 HELVE 060 normal
/Widths
[ 278 333 500 633 633 1000 758 333 333 333 633...
Adobe reader converts this width table, by modifying the space between each character, so that the specified letter width (= space between the current and the next letter) is kept.
This 'Simulation' of printer fonts results in the sometimes visible irregular spaces in PDF.
The PDF converter always uses the Helvetica Adobe PostScript font for the display of HELVE and the Times Roman Adobe PostScript font for the display of TIMES. However, for these Adobe PostScript fonts, Adobe Reader often uses a Windows TrueType font, which differs slightly from the original PostScript font.
Solution
Workaround: Use the POST2 PostScript device type or the PDF1 PDF device type for the PDF conversion of documents in the Latin-1 character set. They both use the Adobe PostScript fonts Helvetica or Times Roman for the HELVE/TIMES printer fonts.
Header Data
Release Status: Released for Customer
Released on: 30.06.2006 12:44:06
Priority: Recommendations/additional info
Category: Consulting
Primary Component: BC-CCM-PRN Print and Output Management
Secondary Components: BC-SRV-SCR SAPscript
OSS Note: 776507
Symptom
Documents printed via SAPscript or SmartForms do not print with correct special characters, e.g. ### prints instead of Japanese or Russian characters. What to do?
Other terms
SAPscript, SmartForms, printing, device types, OTF
Reason and Prerequisites
Help required to choose proper fonts in a SAPscript or SmartForm
Solution
When using SAPscript or SmartForms to print (or email or fax) a form from a business application, many factors influence the outcome of the actual text within the form. All these factors must be checked in order to ensure a correct printout:
1) The language version of the form used to produce the printout.
Example: If you want to print a French invoice, you need to have a FR version of your SAPscript or SmartForms invoice form RVINVOICE01. And the application program must specify the corresponding language key (FR) when calling the SAPscript or SmartForms API.
2) The font selections specified in the form (possibly also in a SAPscript style or SmartStyle used in a form).
Example: In a SAPscript form or a SmartStyle you need to specify HELVE if you want to print German text in Helvetica (or similar) font. If you want to print Japanese text, HELVE is not a valid choice but you need to specify a Japanese font like JPMINCHO in your Japanese form.
3) The output character set of the device type
Every printer in transaction SPAD has a "device type" assigned. Device types used by the spooler for printing support only one single specific output character set. All text from the form has to be converted (using SAP's built-in character conversion mechanism) to this output character set.
A character set can typically support either a single language (e.g. Shift-JIS which supports only Japanese) or a set of languages (e.g. ISO 8859-1, which supports Western-European languages). It is possible that a given language (such as German) can be supported by several output character sets, e.g. you may use either ISO 8895-1 (Latin-1) or ISO 8859-2 (Latin-2) to represent German text. This is so because both character sets contain the special characters used in German.
Example: HPLJ4000 is a HP LaserJet device type supporting the ISO 8859-1 (Latin-1) character set. ISO 8859-1 can be used to represent e.g. Dutch, English, French, German, Spanish, Swedish but NOT Russian or Japanese.
As a consequence, it is ok to use HPLJ4000 to print English, German French etc. but not for Japanese or Russian.
4) The set of available printer fonts for a given device type
When formatting a document, SAPscript and SmartForms perform an automatic mapping of the font definitions in the form (e.g. "HELVE 14 point bold") and the available printer fonts of the device type. A replacement printer font is chosen, should the specified font selection not be available in the device type. Now this replacement can be problematic if a language-specific font, such as Chinese CNSONG, is specified in a form and it gets replaced by a font which does not support this language, e.g. COURIER.
To solve this problem, font families in SE73 have language attribute assigned, e.g. some fonts are characterized as being suitable only for certain languages. And when a replacement has to be chosen because the original font from the form is not available in the device type, a replacement font is chosen which has the same language attributes.
If no fonts for the language in question exist in the device type, the resulting font will not be able to print the special characters and you will see "wrong" output characters in the printout.
Note on SAPscript/SmartForms Print Preview:
The OTF Print Preview available in Windows GUI (e.g. from transaction SP01) will sometimes not show the "wrong" characters which appear on the final printout. Here is the reason: since the Print Preview runs in Windows environment, it will use Windows fonts to represent the actual printer fonts. A Windows font typically has more available characters (i.e. covers more character sets) than are actually available in a printer's resident font.
A typical example where the Print Preview will differ from the printout is here: if you have a Chinese PCL5 printer such as CNHPLJ4 and use the Western Latin font COURIER in your document, the print preview will show you Chinese characters if you (by accident) tried to format Chinese characters in COURIER font. This is because Windows will automatically choose a font that can output Chinese characters (which is actually not Courier). But when you print the job on an actual PCL5 printer with resident Western and Chinese fonts, the Courier font will not print any Chinese characters but Western special characters instead, because the printer's resident Courier font does not include Chinese characters.
Rule of thumb: all Asian device types (e.g. CNHPLJ4, JPHPLJ4, JPPOST, KPHPLJ4) support not only Asian fonts but also COURIER, HELVE and TIMES fonts. But these Latin fonts can only be used to print English text, not Chinese/Japanese/Korean characters.
Which fonts are suitable for a given language?
Language(s):            Font family to use in a form:
Latin-1 (Western Europe/Americas) *******
DE,EN,FR,ES,NL,SV       COURIER, HELVE, TIMES
                        (LETGOTH, LNPRINT)
Latin-2 (Central Europe) ****************
PL, CZ                  COURIER, HELVE, TIMES
ISO 8859-4 (Baltic) *********************
ET, LT, LV              COURIER, HELVE, TIMES
ISO 8859-5 (Cyrillic) *******************
BG, RU, SR, UK          COURCYR, HELVCYR, TIMECYR
ISO 8859-7 (Greek) **********************
EL                      COUR_I7, HELV_I7, TIME_I7
ISO 8859-8 (Hebrew) *********************
HE                      COURIER, HELVE, TIMES
ISO 8859-9 (Turkish) ********************
TR                      COURIER, HELVE, TIMES
Simplified Chinese **********************
ZH                      CNHEI, CNKAI, CNSONG
Japanese ********************************
JA                      JPMINCHO, DBMINCHO, DBGOTHIC
Korean **********************************
KP                      KPBATANG, KPDODUM, KPGULIM
                        KPGUNGSE, KPSAMMUL
Traditional Chinese *********************
ZF                      TWDPHEI, TWMING, TWSONG
Thai ************************************
TH                      THANGSAN, THDRAFT, THVIJIT
Arabic (Unicode systems only) ***********
AR                      ANDALE_J
Verify your output by examining the OTF data
When analysing printing problems of this type, be sure to check the OTF data which gets produced by SAPscript or SmartForms. OTF or "Output Text Format" is the intermediate page-description format generated from SAPscript or SmartForms. OTF will contain the final printer font names and character set/language identifiers which help to solve the problem. OTF will even name the form and the language of the form used to create the output.
The easiest way to do this is to create a spool request from your application, run transaction SP01, use menu
Goto->Display Requests->Settings
and choose
Display Mode: Raw
Now display your spool request. If this is a SAPscript or SmartForms spool request, you will see OTF data. Each line represents one OTF command, every command starts with a 2-character cmd identifier and possibly some cmd parameters follow.
Here is an excerpt from a sample OTF file where we highlight the most interesting commands:
//XHPLJ8000    0700 00000000001
IN04EALEXTEST_ZEBRA
IN05%PAGE1
OPDINA4 P 144 240 1683811906000010000100001
IN06%WINDOW2
MT0024401289
CP11000000E
FCHELVE 120 00109XSF100SF101110000067E X
UL +0000000000000
SW00067
CT00000000
ST0453037Dieses SF hat Stil ALEXTEST_ZEBRA mit
The 1st line with the // (Control) command reveals the device type usedto print: HPLJ8000
//XHPLJ8000    0700 00000000001
The 2nd line (IN = Info command) shows the name and (internal 1-char)language key of the form:
IN04EALEXTEST_ZEBRA
In this case it is the English (E = EN) SmartForm ALEXTEST_ZEBRA
The OP-line (OP = Open Page) gives the page format used in the form, it is DINA4 Portrait orientation:
OPDINA4 P 144 240 1683811906000010000100001
The CP (CodePage) cmd shows the SAP system codepage used to code the text and the active language. In our case it is codepage 1100 and language E = EN = English.
CP11000000E
Finally, the FC-cmd (Font Call) lists a printer font selected within SmartForms. Please note that every SmartForm has a designated default SmartStyle under "Form Attributes->Output Options". In addition, every text node can have a SmartStyle attached (which will override the definitions from the default style for the text). In our case the resulting printer font that was selected is HELVE 12.0 pt bold-off, italic-off.
FCHELVE   120 00109XSF100SF101110000067E X
Header Data
Release Status: Released for Customer
Released on: 22.08.2005 09:57:20
Priority: Recommendations/additional info
Category: Customizing
Primary Component: BC-CCM-PRN Print and Output Management
Secondary Components: BC-SRV-SCR SAPscript
BC-SRV-SSF Smart Forms
reward if useful
regards,
ANJI

Email Invoice as PDF

Hi folks,
I'm trying to send a sapscript/smartform invoice as a PDF attached to an email. I've been reading a number of posting on this topic but it is still unclear to me how to get this to work. (R/3 4.7)
I need to setup a new output type with transmission media 5. Is that correct? The email address will be pulled from the customer's master data record. Correct?
What do I use as the processing routine? Do I have to create a custom routine?
Do I need to define a communications strategy with communication type INT?
As I understand it, the system will automatically convert to PDF as long as SCOT is configured that way (default).
What else am I missing?
Thanks everyone,
Clint

Hi,
1.No need to create the custom routine.
2.The system default cann't generate the PDF.It generates OTF , Format.
3.We need to convert the OTF into PDF.
4.You have to maintain the Email in SCOT.
The following is the code for sending through mail for script:
Best LInk:
/people/pavan.bayyapu/blog/2005/08/30/sending-html-email-from-sap-crmerp
Observe this:
REPORT Z_SCRIPT .
DATA: itcpo LIKE itcpo,
tab_lines LIKE sy-tabix.
Variables for EMAIL functionality
DATA: maildata LIKE sodocchgi1.
DATA: mailpack LIKE sopcklsti1 OCCURS 2 WITH HEADER LINE.
DATA: mailhead LIKE solisti1 OCCURS 1 WITH HEADER LINE.
DATA: mailbin LIKE solisti1 OCCURS 10 WITH HEADER LINE.
DATA: mailtxt LIKE solisti1 OCCURS 10 WITH HEADER LINE.
DATA: mailrec LIKE somlrec90 OCCURS 0 WITH HEADER LINE.
DATA: solisti1 LIKE solisti1 OCCURS 0 WITH HEADER LINE.
*PERFORM send_form_via_email.
FORM SEND_FORM_VIA_EMAIL *
FORM send_form_via_email.
CLEAR: maildata, mailtxt, mailbin, mailpack, mailhead, mailrec.
REFRESH: mailtxt, mailbin, mailpack, mailhead, mailrec.
Creation of the document to be sent File Name
maildata-obj_name = 'TEST'.
Mail Subject
maildata-obj_descr = 'Subject'.
Mail Contents
mailtxt-line = 'Here is your file'.
APPEND mailtxt.
Prepare Packing List
PERFORM prepare_packing_list.
Set recipient - email address here!!!
mailrec-receiver = 'email.COM'.
mailrec-rec_type = 'U'.
APPEND mailrec.
Sending the document
CALL FUNCTION 'SO_NEW_DOCUMENT_ATT_SEND_API1'
EXPORTING
document_data = maildata
put_in_outbox = ' '
TABLES
packing_list = mailpack
object_header = mailhead
contents_bin = mailbin
contents_txt = mailtxt
receivers = mailrec
EXCEPTIONS
too_many_receivers = 1
document_not_sent = 2
operation_no_authorization = 4
OTHERS = 99.
ENDFORM.
Form PREPARE_PACKING_LIST
FORM prepare_packing_list.
CLEAR: mailpack, mailbin, mailhead.
REFRESH: mailpack, mailbin, mailhead.
DESCRIBE TABLE mailtxt LINES tab_lines.
READ TABLE mailtxt INDEX tab_lines.
maildata-doc_size = ( tab_lines - 1 ) * 255 + STRLEN( mailtxt ).
Creation of the entry for the compressed document
CLEAR mailpack-transf_bin.
mailpack-head_start = 1.
mailpack-head_num = 0.
mailpack-body_start = 1.
mailpack-body_num = tab_lines.
mailpack-doc_type = 'RAW'.
APPEND mailpack.
Creation of the document attachment
This form gets the OTF code from the SAPscript form.
If you already have your OTF code, I believe that you may
be able to skip this form. just do the following code, looping thru
your SOLISTI1 and updating MAILBIN.
PERFORM get_otf_code.
LOOP AT solisti1.
MOVE-CORRESPONDING solisti1 TO mailbin.
APPEND mailbin.
ENDLOOP.
DESCRIBE TABLE mailbin LINES tab_lines.
mailhead = 'TEST.OTF'.
APPEND mailhead.
Creation of the entry for the compressed attachment
mailpack-transf_bin = 'X'.
mailpack-head_start = 1.
mailpack-head_num = 1.
mailpack-body_start = 1.
mailpack-body_num = tab_lines.
mailpack-doc_type = 'OTF'.
mailpack-obj_name = 'TEST'.
mailpack-obj_descr = 'Subject'.
mailpack-doc_size = tab_lines * 255.
APPEND mailpack.
ENDFORM.
Form GET_OTF_CODE
FORM get_otf_code.
DATA: BEGIN OF otf OCCURS 0.
INCLUDE STRUCTURE itcoo .
DATA: END OF otf.
DATA: itcpo LIKE itcpo.
DATA: itcpp LIKE itcpp.
CLEAR itcpo.
itcpo-tdgetotf = 'X'.
Start writing OTF code
CALL FUNCTION 'OPEN_FORM'
EXPORTING
form = 'Z08V3_COLLI'
language = sy-langu
options = itcpo
dialog = ' '
EXCEPTIONS
OTHERS = 1.
CALL FUNCTION 'START_FORM'
EXCEPTIONS
error_message = 01
OTHERS = 02.
CALL FUNCTION 'WRITE_FORM'
EXPORTING
window = 'MAIN'
EXCEPTIONS
error_message = 01
OTHERS = 02.
Close up Form and get OTF code
CALL FUNCTION 'END_FORM'
EXCEPTIONS
error_message = 01
OTHERS = 02.
MOVE-CORRESPONDING itcpo TO itcpp.
CALL FUNCTION 'CLOSE_FORM'
IMPORTING
result = itcpp
TABLES
otfdata = otf
EXCEPTIONS
OTHERS = 1.
Move OTF code to structure SOLI form email
CLEAR solisti1. REFRESH solisti1.
LOOP AT otf.
solisti1-line = otf.
APPEND solisti1.
ENDLOOP.
ENDFORM
Below points is for ur testing purpose.
U can check the status of the mail in the transaction SOST.
Execute this transaction for the date range. If the traffic light is in yellow colour then do like this.
Utilities->Start send process->Give trans method as INT and press enter. Mail will go immediately.
If the above logic don't work for u then TRY FM SO_OBJECT_SEND for sending mail.
for Smartform converting the OTF to PDF:
REPORT zsuresh_test.
Variable declarations
DATA:
w_form_name TYPE tdsfname VALUE 'ZSURESH_TEST',
w_fmodule TYPE rs38l_fnam,
w_cparam TYPE ssfctrlop,
w_outoptions TYPE ssfcompop,
W_bin_filesize TYPE i, " Binary File Size
w_FILE_NAME type string,
w_File_path type string,
w_FULL_PATH type string.
Internal tables declaration
Internal table to hold the OTF data
DATA:
t_otf TYPE itcoo OCCURS 0 WITH HEADER LINE,
Internal table to hold OTF data recd from the SMARTFORM
t_otf_from_fm TYPE ssfcrescl,
Internal table to hold the data from the FM CONVERT_OTF
T_pdf_tab LIKE tline OCCURS 0 WITH HEADER LINE.
This function module call is used to retrieve the name of the Function
module generated when the SMARTFORM is activated
CALL FUNCTION 'SSF_FUNCTION_MODULE_NAME'
EXPORTING
formname = w_form_name
VARIANT = ' '
DIRECT_CALL = ' '
IMPORTING
fm_name = w_fmodule
EXCEPTIONS
no_form = 1
no_function_module = 2
OTHERS = 3
IF sy-subrc 0.
MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
Calling the SMARTFORM using the function module retrieved above
GET_OTF parameter in the CONTROL_PARAMETERS is set to get the OTF
format of the output
w_cparam-no_dialog = 'X'.
w_cparam-preview = space. " Suppressing the dialog box
" for print preview
w_cparam-getotf = 'X'.
Printer name to be used is provided in the export parameter
OUTPUT_OPTIONS
w_outoptions-tddest = 'LP01'.
CALL FUNCTION w_fmodule
EXPORTING
ARCHIVE_INDEX =
ARCHIVE_INDEX_TAB =
ARCHIVE_PARAMETERS =
control_parameters = w_cparam
MAIL_APPL_OBJ =
MAIL_RECIPIENT =
MAIL_SENDER =
output_options = w_outoptions
USER_SETTINGS = 'X'
IMPORTING
DOCUMENT_OUTPUT_INFO =
job_output_info = t_otf_from_fm
JOB_OUTPUT_OPTIONS =
EXCEPTIONS
formatting_error = 1
internal_error = 2
send_error = 3
user_canceled = 4
OTHERS = 5
IF sy-subrc 0.
MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
t_otf] = t_otf_from_fm-otfdata[.
Function Module CONVERT_OTF is used to convert the OTF format to PDF
CALL FUNCTION 'CONVERT_OTF'
EXPORTING
FORMAT = 'PDF'
MAX_LINEWIDTH = 132
ARCHIVE_INDEX = ' '
COPYNUMBER = 0
ASCII_BIDI_VIS2LOG = ' '
PDF_DELETE_OTFTAB = ' '
IMPORTING
BIN_FILESIZE = W_bin_filesize
BIN_FILE =
TABLES
otf = T_OTF
lines = T_pdf_tab
EXCEPTIONS
ERR_MAX_LINEWIDTH = 1
ERR_FORMAT = 2
ERR_CONV_NOT_POSSIBLE = 3
ERR_BAD_OTF = 4
OTHERS = 5
IF sy-subrc 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
To display File SAVE dialog window
CALL METHOD cl_gui_frontend_services=>file_save_dialog
EXPORTING
WINDOW_TITLE =
DEFAULT_EXTENSION =
DEFAULT_FILE_NAME =
FILE_FILTER =
INITIAL_DIRECTORY =
WITH_ENCODING =
PROMPT_ON_OVERWRITE = 'X'
CHANGING
filename = w_FILE_NAME
path = w_FILE_PATH
fullpath = w_FULL_PATH
USER_ACTION =
FILE_ENCODING =
EXCEPTIONS
CNTL_ERROR = 1
ERROR_NO_GUI = 2
NOT_SUPPORTED_BY_GUI = 3
others = 4
IF sy-subrc 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
Use the FM GUI_DOWNLOAD to download the generated PDF file onto the
presentation server
CALL FUNCTION 'GUI_DOWNLOAD'
EXPORTING
BIN_FILESIZE = W_bin_filesize
filename = w_FULL_PATH
FILETYPE = 'BIN'
APPEND = ' '
WRITE_FIELD_SEPARATOR = ' '
HEADER = '00'
TRUNC_TRAILING_BLANKS = ' '
WRITE_LF = 'X'
COL_SELECT = ' '
COL_SELECT_MASK = ' '
DAT_MODE = ' '
CONFIRM_OVERWRITE = ' '
NO_AUTH_CHECK = ' '
CODEPAGE = ' '
IGNORE_CERR = ABAP_TRUE
REPLACEMENT = '#'
WRITE_BOM = ' '
TRUNC_TRAILING_BLANKS_EOL = 'X'
WK1_N_FORMAT = ' '
WK1_N_SIZE = ' '
WK1_T_FORMAT = ' '
WK1_T_SIZE = ' '
IMPORTING
FILELENGTH =
tables
data_tab = T_pdf_tab
FIELDNAMES =
EXCEPTIONS
FILE_WRITE_ERROR = 1
NO_BATCH = 2
GUI_REFUSE_FILETRANSFER = 3
INVALID_TYPE = 4
NO_AUTHORITY = 5
UNKNOWN_ERROR = 6
HEADER_NOT_ALLOWED = 7
SEPARATOR_NOT_ALLOWED = 8
FILESIZE_NOT_ALLOWED = 9
HEADER_TOO_LONG = 10
DP_ERROR_CREATE = 11
DP_ERROR_SEND = 12
DP_ERROR_WRITE = 13
UNKNOWN_DP_ERROR = 14
ACCESS_DENIED = 15
DP_OUT_OF_MEMORY = 16
DISK_FULL = 17
DP_TIMEOUT = 18
FILE_NOT_FOUND = 19
DATAPROVIDER_EXCEPTION = 20
CONTROL_FLUSH_ERROR = 21
OTHERS = 22
IF sy-subrc 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
Regards,
If helpful give points(Don't forget)

Smart form - Sales invoice

Hi all
i have to develop a Sales Invoice in smart forms, is there any standard sap smart form available which I can use.
regards
AJ

Hello AJ,
SAP Standard smartform invoices
SF_LB_INVOICE

Coding in smartforms

Suppose I'm doing the coding in smartforms, then how to make a selection screen.Please explain with a sample code.

you must create a common report program to do the select-screen
then at last to call the smartform and importing parameter
 call function 'SSF_FUNCTION_MODULE_NAME'
 exporting formname = lf_formname 'your smartforms name
 variant = ' '
 direct_call = ' '
 importing fm_name = lf_fm_name
 exceptions no_form = 1
 no_function_module = 2
 others = 3.
 if sy-subrc <> 0.
error handling
 cf_retcode = sy-subrc.
 perform protocol_update.
 endif.
endif.
call smartform invoice
 call function lf_fm_name
 exporting
 archive_index = toa_dara
 archive_parameters = arc_params
 control_parameters = ls_control_param
 mail_appl_obj =
 mail_recipient = ls_recipient
 mail_sender = ls_sender
 output_options = ls_composer_param
 user_settings = 'X'
 is_bil_invoice = ls_bil_invoice
 is_vbdkr = vbdkr
 is_komk = komk
 is_catsxt_data = i_catsxt_flow_back
 importing document_output_info =
 job_output_info =
 job_output_options =
 tables is_vbdpr = t_vbdpr
 is_komv = tkomv
 is_komvd = tkomvd
 exceptions formatting_error = 1
 internal_error = 2
 send_error = 3
 user_canceled = 4
 others = 5.
 if sy-subrc <> 0.
error handling
 cf_retcode = sy-subrc.
 perform protocol_update.
 endif.

Change output device in smartform when using gui_diwnload

can any one please tell me how to change the output device for gui_download into pdf for a smartform.
(i want the setting to be done in my report -driver program ,   not in sap application tool bar settings)
kindly please suggest me,
thanks in advance,
koolspy.

I give you an example
DATA: ls_control_param      TYPE ssfctrlop.
DATA: ls_composer_param     TYPE ssfcompop.
    Parametros por defecto para la generación de la orden de spool.
      ls_composer_param-tddataset = 'PDF'.
      ls_composer_param-tdsuffix1 = 'FACT.'.
      ls_composer_param-tdsuffix2 = nast-OBJKY.
      ls_composer_param-TDDEST   = 'LP02'.
    output_options-tdprinter = 'PRINTER'.
      ls_composer_param-tdnewid = 'X'.
      ls_composer_param-tddelete = 'X'.
      ls_composer_param-tdfinal = ' '.
      ls_composer_param-tdlifetime = 8.
      ls_control_param-no_dialog = 'X'.
      ls_control_param-preview = ' '.
      ls_composer_param-tdimmed = ' '.
      ls_control_param-getotf = 'X'.
call smartform invoice
      CALL FUNCTION lf_fm_name
        EXPORTING
          archive_index        = toa_dara
          archive_parameters   = arc_params
          control_parameters   = ls_control_param
          mail_recipient       = ls_recipient
          mail_sender          = ls_sender
          output_options       = ls_composer_param
          user_settings        = space
          is_bil_invoice       = ls_bil_invoice
          is_nast              = nast
          is_repeat            = repeat
          is_vbdkr             = is_vbdkr
        IMPORTING
          job_output_info      = job_output_info
          document_output_info = document_output_info
          job_output_options   = job_output_options
        TABLES
          gt_vbdpr             = gt_vbdpr
        EXCEPTIONS
          formatting_error     = 1
          internal_error       = 2
          send_error           = 3
          user_canceled        = 4
          OTHERS               = 5.
    Convertimos el fichero OTF a PDF
    CALL FUNCTION 'CONVERT_OTF'
      EXPORTING
        format                      = 'PDF'
        MAX_LINEWIDTH               = 132
        ARCHIVE_INDEX               = ' '
        COPYNUMBER                  = 0
        ASCII_BIDI_VIS2LOG          = ' '
        PDF_DELETE_OTFTAB           = ' '
      IMPORTING
        bin_filesize                = file_size
        BIN_FILE                    =
      TABLES
        otf                         = job_output_info-otfdata
        lines                       = lt_pdf
      EXCEPTIONS
        err_max_linewidth           = 1
        err_format                  = 2
        err_conv_not_possible       = 3
        err_bad_otf                 = 4
        OTHERS                      = 5
Hope it helps.

Smartforms invoice

Similar Messages

Maybe you are looking for