SAP script as an attachment to fax

How to send sap script to the function module SO_DOCUMENT_SEND_API1
to send fax ?

Hello,
You need to create communication starategy and assign it to the communication medium at the condition record maintanace editor.I assume you are trying to send external mail.
you need to save the addresses and communication methods in central address management. Select Tools ® Business Communication, Office ® Addresses ® External Companies/Contact Person.
Let me know if you need more help.
Thank you.
Regards,
Vasanth M

Similar Messages

Formatted Text Edit & SAP Script Text

I'm working through a business requirement to input some long text, and then update an existing SAP script text object (attached to a sales order).
I'm using a formatted text editor to allow the users to enter the text - however I can't find a utlity that allows me to convert this data into a format that can be saved into a sap script text.
Thanks,
Heather

Hi Heather,
Please check this...
Re: From Web Dypro Text area to SAP Script text object(Tline table)
http:///Tutorials/Smartforms/PassingTableData/Script1.htm ... add saptecnical.com before tutorials.
Cheers,
Kris.

Problem in sending Fax from the Output type - SAP Script

Hi Team,
I am facng a problem with SAP Script while sending the Fax from the output type. I am able to see the entire output in my outbox. But in the fax machine it is only printing the Main window. I checked with some other outputs which are using the Fax option, they are printing fine. Driver program is the Z program. Can anyone give me some Idea?
Regards,
Sasidhar

Hi Sasidhar,
Have you tried with different fax machine.
Regards,
Atish

Sending SAP Script output as a PDF attachment through mail

Dear Guru,
I am using SAP 4.0B version, DATABASE Oracle 8i, OS is sun solaris 7.5.
I want to send SAP script output as a
PDF attachement through mail.Please suggest a solution.
Regards,
Rajesh

Hi Rajesh,
In your print program, while calling OPEN_FORM, pass options-TDGETOTF = 'X'. This is used for returning print output in OTF format.
Then in CLOSE_FORM, get the table OTFDATA returned from the function module. for example
DATA: OTF_DATA LIKE ITCOO OCCURS 0 WITH HEADER LINE.
    CALL FUNCTION 'CLOSE_FORM'
      IMPORTING
        RESULT = RESULT
      TABLES
        OTFDATA = OTF_DATA.
now you can convert this OTF data to PDF using function module CONVERT_OTF
Then send this data as attachment to a mail using function module SO_NEW_DOCUMENT_ATT_SEND_API1
Regards,
Komal.

How to attach print program and sap script for F150 transaction

How to attach print program and Z sap script for F150 transaction

Hi,
you can find the customization for dunning in transaction SPRO under this path: Financial Accounting->Accounts Receivable and Accaounts Payable->Business Transactions->Dunning.
Kostas

Fax through SAP SCRIPT

Hi all,
Could any one suggest me how to apply changes on FAX coversheet through SAP SCRIPT? I need to change the existing Coverpage address to Japanese text.
Please suggest some solution. Useful answers would be rewarded.
Regards,
Kalpana.

Please check following link
http://wiki.ittoolbox.com/index.php/HOWTO:Sap_script
I hope this will help you.
Regards,
Amey

Send email with PDF attachements (Smartform/SAP script)

Hello All,
I have 3 existing programs A, B & C whose output is in SAP Script/Smartform. Now I need to create new program D which needs to execute program A, B & C and then convert their smartform/SAP script output into PDF format and send email with attachements (PDF files). Any pointers how I can proceed. Thanks a lot.

hi Sarita,
v_ctrlparams-no_dialog = 'X'.
v_ctrlparams-getotf = 'X'.
CALL FUNCTION 'SSF_FUNCTION_MODULE_NAME'
    EXPORTING
      formname = 'Smartform name'
    IMPORTING
      fm_name = v_func_mod.
CALL FUNCTION v_func_mod
    EXPORTING
      control_parameters = v_ctrlparams
    IMPORTING
      job_output_info    = v_joboutput
    TABLES
      t_nonsigner        = t_nonsigner.
fill the document
doc_chng-obj_name = 'Descriptoipn'.
Fill the subject line
doc_chng-obj_descr = 'Manpowe'.
doc_chng-obj_descr = 'Reminder .
doc_chng-sensitivty = 'P'.
Fill the content of the mail
objcont = 'Dear all,'.
APPEND objcont.
CLEAR objcont.
APPEND objcont.
CLEAR objcont.
objcont =
'The manpower sign-off is pending for the list of employees as per th' &
'e attached sheet.'
APPEND objcont.
CLEAR objcont.
APPEND objcont.
CLEAR objcont.
objcont =
'Please click on the following link for the manpower sign-off:'.
APPEND objcont.
CLEAR objcont.
APPEND objcont.
CLEAR objcont.
DESCRIBE TABLE objcont LINES entries.
READ TABLE objcont INDEX entries.
doc_chng-doc_size = ( entries - 1 ) * 255 + STRLEN( objcont ).
Creating the entry for the compressed document
CLEAR objpack-transf_bin.
objpack-head_start = 1.
objpack-head_num   = 0.
objpack-body_start = 1.
objpack-body_num   = entries.
objpack-doc_type   = 'RAW'.
APPEND objpack.
Creating the document attachment
(Assume the data in OBJBIN are given in BMP format)
LOOP AT v_joboutput-otfdata INTO wa_otfdata.
    APPEND wa_otfdata TO objbin.
    CLEAR wa_otfdata.
ENDLOOP.
DESCRIBE TABLE objbin LINES tab_lines.
objhead = 'NonSignerDetails.otf'. APPEND objhead.
Creating the entry for the compressed attachment
objpack-transf_bin = 'X'.
objpack-head_start = 1.
objpack-head_num   = 1.
objpack-body_start = 1.
objpack-body_num   = tab_lines.
objpack-doc_type   = 'OTF'.
objpack-obj_name   = 'ATTACHMENT'.
objpack-obj_descr = 'NonSignerDetails'.
objpack-doc_size   = tab_lines * 255.
APPEND objpack.
Sending the document
CALL FUNCTION 'SO_NEW_DOCUMENT_ATT_SEND_API1'
    EXPORTING
      document_data              = doc_chng
      put_in_outbox              = 'X'
      commit_work                = 'X'
    TABLES
      packing_list               = objpack
      object_header              = objhead
      contents_bin               = objbin
      contents_txt               = objcont
      receivers                  = reclist
    EXCEPTIONS
      too_many_receivers         = 1
      document_not_sent          = 2
      operation_no_authorization = 4
      OTHERS                     = 99.
hope this will help u..
regards,
Santosh Thorat

Attaching Transport Req to SAP Script

Hi All,
When i changed the sap script in DEV server, the system is not asking for Transport Request number.
Now, i have to attache it a TR and then move the same to Quality....
How to do it.....????
Regards
Pavan

hi,
goto SE03 select change object directory entries - execute.
give as form formname and execute.
select ur form and click object directory save in package it will ask request.
now u can use this request to transport to quality.
the other alternative is u can use program RSTXFCPY to transport scripts between clients.

How to attach Pacakge for Local made SAP Script

Hi,
I have created a SAP Script, initially I have made it as local without assigning any package, ow I want to attach one package for that SAP Script form to transfer it to quality and production but in chnage mode the package filed is disable.
Also other option is there to copy existing form to new and give the package name but i want to know insted of copy how to add package for existing form.
regards,
zafar

Goto SE03>object directory>change object directory entries> enter FORM in the first text box and script name in the object name select checkbox and execute.....>select the form and press button change object directory above....

Problem with SAP Script FAX output

Hi Friends,
I have problem with SAP Script Fax output.
After I issued output using the messge type, the print preview format shows me correct alignments and the right data. But when I go to List display using the menu bar functions from the print preview screen, the list is showing me the right data, but all the alignments at the main window went wrong.
How do I rectify this problem? I need correct alignments in both form display and list display.

Hi Sasidhar,
Have you tried with different fax machine.
Regards,
Atish

ABAP QUERY PROGRAM OUTPUT SHOULD DISPLAY FROM SAP SCRIPT.

THIS IS MY URGENT REQUIREMENT ...
I DONT KNOW ABAP QUERY PROGRAM ..
PLEASE SUGGEST ME A WAY ON THIS ....
Functional requirements
Introduction
The wish of the customer is a printable customer overview. All desired fields will be shown in a new query called ZZADDRSS_CO. Double entries are taken for granted because of the data taken from the sales area and because of multiple contact persons. The customer accepts this. It should be made possible that the user creates and saves its own variant.
A second overview is needed, another ABAP will be developed for this requirement. This ABAP will show all the customer data and this list will have the possibility to be printed.
Solution
New Query ZZADDRESS_CO
The desired fields of attachment 1 need to be shown in the query.
The selection criteria are shown in attachment 2.
The column names of the additional data have to changed in the query.
Customer Overview.
Functional specification.
On behalf of this customer overview a standard SAP transaction will be used (transaction VC/2).This transaction will be extended.
The fields are shown on screen with the described headers. Printing of the overview will be done via SAP script. The script makes use of a fixed layout of the data.
The selection criteria are specified in attachment 2.
The layout of the customer overview and the SAP Script are specified in attachment 3.
Specification.
The next steps need to be performed.
1.     A routine per infoblock need to be created in Include RV77UNNN. In this routine the data is retrieved and written down to the screen and script,
Example LST1_901 . In include RV77SNNN you can find the standard infoblocks.
2.     Adapt via transaction SE16 table TFRM.
3.     Create a new view in the customizing (sales and distribution- Sales support-sales summary-Assign Reporting Views).Assign the new view to the infoblocks.(Example view 001 is assigned to block 901).
4.     In customizing it is not possible to assign the correct window and element to the infoblock .so this is done via SE16 in table T182A.
5.     Adapt script. Copy script SD-SALES-SUMMARY to a Z-SALES_SUMM.
Assign this new version to the new view in customizing. Create in the main window the element who writes the data on behalf of the print.
Attachment 1 Desired fields
Header: Address
~ Customer number                          KNA1-KUNNR
~ Title                                               KAN1-ANRED
~ Name1                                           ADRC-NAME1
~ Name2                        ADRC-NAME2
~ Name3                                           ADRC-NAME3
~ Name4                                           ADRC-NAME4
~ PO Box                                         ADRC-PO_BOX
~ PO Box POSTAL CODE             ADRC-POST_CODE2
~ PO Box city                                  ADRC-PO_BOX_LOC
~ Telephone no1                              ADR2-TEL_NUMBER   1ST RECORD
~ Telephone no2                              ADR2-TEL_NUMBER   2ND RECORD
~ Fax number1                                 ADR3-FAX_NUMBER 1ST RECORD
~ Fax number2                                ADR3-FAX_NUMBER 2ND RECORD
~ E-mail                                            ADR6-SMTP_ADDR
~ Search item                                   ADRC-SORT1
~ Notes                                            ADRT-REMARK
Header: control data
~ VAT registration number              KAN1-STCEG
Header: Payment transactions
~Bank country key                         KNBK-BANKS
~Bank key                                      KNBK-BANKL
~Bank Account number                 KNBK-BANKN
Header: Marketing
~ Industry key                                   KNA1-BRSCH
~ Industry code 1                              KNA1-BRAN1
~ Industry code 2                              KNA1-BRAN2
~ Industry code 3                                KNA1-BRAN3
~ Industry code 4                                KNA1-BRAN4
~ Industry code 5                               KNA1-BRAN5
~Annual sales, currency, year           KNA1-UMSA1, KNA1-UWAER, KNA1-UMAH
~ Yearly no of employees, year      KAN1-JMZAH, KNA1-JMJAH
~ Fiscal year variant                          KNA1-PERIV
~Legal status                                      KNA1-GFORM
Header: Correspondence
~ Our account number at customer            KNB1-EIKTO
Header: sales
~ Sales office                                              KNVV-VKBUR
~ Customer group                                       KNVV-KDGRP
~ ABC-classification                                  KNVV-KLABC
Header: Invoice
~Tax classification                          KNVI-TAXKD
~Terms of payment key                    KNVV-ZTERM
~
Header: Contact Persons
~Title                                   KNVK-ANRED
~Name                                   KNVK-NAME1
~Advertising material                         KNVK-NMAIL
~Martial Status                         KNVK-FAMST
~Notes                                   KNVK-PARAU
~Function                              KNVK-PAFKT
~Department                              KNVK-ABTNR
Header: Partnerroles
~Personnel Number                         KNVP-PERNR
~Name of employee                         PA0001-ENAME
Header: Additional Data
~Attribute 1                              KNA1-KATR1
~Creation date                              KNA1-ERDAT
~Attribute 2                              KNA1-KATR2
~Change date of field KNA1-KATR2          CDHDR-UDATE
~Attribute 3                              KNA1-KATR3
~Attribute 4                              KNA1-KATR4
~Attribute 5                              KNA1-KATR5
~Attribute 6                              KNA1-KATR6
Attachment 2 Selection fields
~Customer number
~Sales office
~Personnel Number
~Sales Organization (default NL01)
~Industry key
~Industry codes (1 till 5)
~ABC- classification
~Creation date
~Attribute 1
~Attribute 2
~Attribute 3
~Attribute 4
~Attribute 5
Attachment 3 Customer overview + SAP Script
Customer master data sheet: 11490                 Page1
Requested by karen Dunnewold                Date: 25.08.2004
Address
(Default SAP script ADDRESS statement)
Title
Name1
Street + number
PO Box city
Country
Search term: ADRC-SORT1
Telephone 1:      ADR2-TEL_NUMBER     2: ADR2-TEL_NUMBER
Fax 1:          ADR3-FAX_NUMBER     2: ADR3-FAX_NUMBER
E-mail:          ADR6-SMTP_ADDR
Notes:           ADRT-REMARK
PO BOX
ADRC-PO_BOX
ADRC-POST_CODE2 ADRC-PO_BOX_LOC
T005T-LANDX (T005T-LAND1 = ADRC-COUNTRY)
Control data
VAT registration number:     KNA1-STCEG
Payment transactions
Country: KNBK-BANKS Bank-key: KNBK u2013 BANKL Bank account: KNBK-BANKN
Marketing
Industry           KNA1-BRSCH     Industry Description
Industry code1          KNA1-BRAN1     Industry Description
Industry code2          KNA1-BRAN2     Industry Description
Industry code3          KNA1-BRAN3     Industry Description
Industry code4          KNA1-BRAN4     Industry Description
Industry code5          KNA1-BRAN5     Industry Description
Figures
Annual Sales          KNA1-UMSA1, KNA1-UWAER in KNA1-UMAH
Employees          KNA1-JMZAH                         in KNA1-JMJAH
Legal status           KNA1-GFORM description
Customer master data sheet 11490                         Page 2
Requested by karen Dunnewold                         Date: 25.08.2004
Contact Persons
KNVK-ANRED
Mailings: KNVK-NMAIL           Notes: KNVK-PARAU
KNVK-ANRED
Mailings: KNVK-NMAIL           Notes: KNVK-PARAU
Correspondence
Our account number at customer      KNB1-EIKTO
Sales
Sales office          KNVV-VKBUR     Description
Customer group     KNVV-KDGRP     Description
ABC-classify          KNVV-KLABC
Currency          KNVV-WAERS
Invoice
Terms of payment key KNVV-ZTERM      Tax classification KNV1-TAXKD
                              Description
Partner (Leave SAP default)
Partnerrole               Number          Name
KNVP-PARVW          KNVP-KUNNR     NAME1
KNVP-PARVW          KNVP-KUNNR     NAME1
Additional data
Attribute1          kna1-katr1     Description
Attribute2          kna1-katr2     Description
Attribute3          kna1-katr3     Description
Attribute4          kna1-katr4     Description
Attribute5          kna1-katr5     Description
Attribute6          kna1-katr6     Description

hi narayana
i think u need to write a driving program and a provided with a smatform u sit along with the SD consultant.
ur further views can be shared.
Rgs,
Venkat.

Send Attachment to Fax.

Hi All,
We have a Z program to FAX invoices to vendors, the way it works is it prepares a Invoice, spools it using SAP Script, further we pick the spool and convert it to PDF. Now, we try to send this PDF as an attacment to Fax numbers using SO_NEW_DOCUMENT_ATT_SEND_API1 function module, my question is would the Fax accept attachments? As per some intial analysis from the Basis team, they belive that the Format of the document should not be PDF however it should be TIF. As per my understanding the fm SO_NEW_DOCUMENT_ATT_SEND_API1 will only send email with attachment to the mentioned e-mail address.
Thank you .

Hi
use this link [http://www.interfax.net/en/help/sap_processing_program.html]
let me know for futhr info.
reg
Ramya

SAP SCRIPT ALIGNMENT

All,
I am developing a form with SAP Script. In the header window (it is a single window using the almost entire width of page format DINA4)i am using three character formats for printing heder lines ofr ex: helve 8, helve 10 Bold and Helve 14 bold. When i see the print preview the alignment is perfect. But when i print the page alignment of header window is distorted. Why is it so? There is some other form using different character formats developed in smart forms. Here print out is coming properly. is this the problem with SAP script. If so what is the work around for this?
Rakesh

Hi
Certain FONTS were not supported by certain printers, hence you may be getting such problem
see the following OSS notes
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
<b>Reward points for useful Answers</b>
Regards
Anji

SAP script printout

Hi,
I have got the output from my sap script.
I want to send the output as a mail to the concerned person.
In menu there is a send mail options but it is disabled.
How to send this SAP script output in a mail (either PDF or the same as output format.

step1:
use the FM CONVERT_OTF to convert otf to pdf.
step 2:
use the folowing code to convert the PDF to a required format and to move the exact content in g_objbin and g_objpack
LOOP AT t_line.
    TRANSLATE t_line USING ' ~'.
   CONCATENATE g_buffer t_line INTO g_buffer.
ENDLOOP.
TRANSLATE g_buffer USING '~ '.
DO.
   g_message1 = g_buffer.
   APPEND g_message1.
SHIFT g_buffer LEFT BY 255 PLACES.
   IF g_buffer IS INITIAL.
    EXIT.
ENDIF.
ENDDO.
g_objbin [] = g_message1 [] .
DESCRIBE TABLE g_objbin LINES g_lines_bin.
READ TABLE g_objbin INDEX g_lines_bin.
g_objpack-transf_bin = 'X'.
g_objpack-head_start = 1.
g_objpack-head_num = 0.
g_objpack-body_start = 1.
g_objpack-doc_size = ( g_lines_bin - 1 ) * 255 + STRLEN( g_objbin ).
g_objpack-body_num = g_lines_bin.
g_objpack-doc_type ='PDF'.
g_objpack-obj_name = text-009.
APPEND g_objpack.
step 3:
use teh following code to attach the content in mail and send it to a recevier
g_reclist-rec_type = 'F'.
g_reclist-fax = l_faxno.
g_reclist-country = 'USA'.
APPEND g_reclist.
CALL FUNCTION 'SO_DOCUMENT_SEND_API1'
    EXPORTING
      document_data           = wa_doc_chng
      put_in_outbox           = 'X'
      commit_work             = 'X'
    TABLES
      packing_list            = g_objpack
      contents_bin            = g_objbin
      contents_txt            = g_objtxt
      receivers               = g_reclist
    EXCEPTIONS
      too_many_receivers      = 1
      document_not_sent       = 2
      document_type_not_exist = 3.
let me know if you need any more help
Edited by: jeevitha krishnaraj on Jul 7, 2009 9:35 AM

SAP Script Docs

HI,
Please give me documents on sapscript..

Check these links.
SAP Scripts
https://forums.sdn.sap.com/click.jspa?searchID=1811669&messageID=2969311
https://forums.sdn.sap.com/click.jspa?searchID=1811669&messageID=2902391
https://forums.sdn.sap.com/click.jspa?searchID=1811669&messageID=3205653
https://forums.sdn.sap.com/click.jspa?searchID=1811669&messageID=3111402
http://www.sap-img.com/sapscripts.htm
http://sappoint.com/abap/
http://www.henrikfrank.dk/abapexamples/SapScript/sapscript.htm
http://help.sap.com/saphelp_crm40/helpdata/en/16/c832857cc111d686e0000086568e5f/content.htm
http://www.sap-basis-abap.com/sapabap01.htm
http://www.sap-img.com/sapscripts.htm
http://searchsap.techtarget.com/tip/1,289483,sid21_gci943419,00.html
http://sap.ittoolbox.com/topics/t.asp?t=303&p=452&h2=452&h1=303
http://www.sapgenie.com/phpBB2/viewtopic.php?t=14007&sid=09eec5147a0dbeee1b5edd21af8ebc6a
Other Links
http://www.virtuosollc.com/PDF/Get_Reporter.pdf
http://help.sap.com/saphelp_47x200/helpdata/en/da/6ada3889432f48e10000000a114084/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/66/bc7d2543c211d182b30000e829fbfe/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/5b/d22cee43c611d182b30000e829fbfe/frameset.htm
http://www.virtuosollc.com/PDF/Get_Reporter.pdf
http://help.sap.com/saphelp_47x200/helpdata/en/da/6ada3889432f48e10000000a114084/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/66/bc7d2543c211d182b30000e829fbfe/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/5b/d22cee43c611d182b30000e829fbfe/frameset.htm
drawing lins, boxes and shadings
http://help.sap.com/saphelp_46c/helpdata/en/d1/802ec5454211d189710000e8322d00/frameset.htm
How to create Box in scripts
http://www.thespot4sap.com/Articles/Code_CostCentreReport.asp
http://www.allsaplinks.com/dialog_programming.html
http://help.sap.com/saphelp_webas630/helpdata/en/9f/db9cdc35c111d1829f0000e829fbfe/frameset.htm
http://www.allsaplinks.com/files/using_table_in_screen.pdf
http://www.geocities.com/ZSAPcHAT
How to copy standard scripts
There are some Standard Sap Scripts in SAP. We cant directly execute them in scripts we have to use some T-codes and by giving some input to the required fields we can see the output printform.
I will show one example. There are some Standard Sap Scripts such as MEDRUCK which is a standard Sap Script for Purchase Order and RVINVOICETH for Sales Order billing and so on...
To see oupt of MEDRUCK go to T-code ME9F give purchase order number and execute select one number and click on dislplay messages button on application tool bar you can find the print form of MEDRUCK.
You cannot change the Standard Sap Scripts but you can use Standard Sap Scripts and Copy them to userdefined Script and can make changes to them and replace standard Sap Script with usedefind script.
Ex: Go to SE71,
on menu bar u find Utilities->copy from Client. click on it u ll find new screen showing
Form name:
Source Clinet:
Target Form:
give Form name as usedefined form name EX: ZFORM1
Source client as 000 and
Target form as MEDRUCK.
execute.
Now, the standard from MEDRUCK is copyied to your form ZFORM1.
NOW, go to SE71 and give form name as ZFORM1 and do some changes to the form such as adding logo any thing. save and Activate.
Now, you have done changes to the Form ZFORM1 and u have to replace your form with standard SAP Script.
Go to NACE Transaction.
on Applications select EF for purchase order and click Output types button on application tool bar.
now select NEU as output types dobule click on Processing Routines.
now click on Change option on application tool bar and on right side u find MEDRUCK in form place replace MEDRUCK with ZFORM1 and SAVE.
go back twice and now go to T-code ME9F give the purchase order number and execute and select one option and click on display messges button .
you will find the changes that you have done in ZFORM1. so we cant chage the standard Sap Scripts by copying the Standard Sap Scripts we can chage and replace with our forms.
Standard SapScripts
SALES ORDER
Output type : BA00
ScriptForm Name : RVORDER01
Driver Program Name : RVADOR01
DELIVERY NOTE
Output type : LD00
ScriptForm Name : RVDELNOTE
Driver Program Name : RVADDN01
smartform name : LE_SHP_DELNOTE
Smartform Driver Pgm: RLE_DELNOTE
INVOICE
Output type : RD00
ScriptForm Name : RVINVOICE01
Driver Program Name : RVADIN01
smartform name : LB_BIL_INVOICE
Smartform Driver Pgm: RLB_INVOICE
PUCHASE ORDER
Output type : NEU
ScriptForm Name : MEDRUCK
Driver Program Name : SAPMF06P
smartform name : /SMB40/MMPO_L
smartform driver program: /SMB40/FM06P
Output Type
OUTPUT Type or Message Type or Condition Type is the same which is used to determine the Output of an Application document, when to send out from the orgn. It may be sent in different mediums like Printout, fax,Mail,edi etc.
We have to some config in SPRO as well as in the application document and in the NACE Tcode.
NACE is the Tcode used to link the Application type, Output Types and its processing Routines like ( Driver programs and attached Script forms or Smartforms).
You should know the Application of a document first Like:
for PO it is EF, for sales Doc's it is V1, for Delivery docs it is V2, for billing Doc's it is V3 etc.
so first select the Application type (ex: EF) for PO and press OUtput types
then a list will come in that you should know the related output type for PO.
in this case it is NEU,
select that and click on the processing Routines button on the left side
it will display the Medium, Driver Program and the Script form or smartform related to that document..
different application documents have different output types;
example:
document Output type
Pur order NEU
Sales order BA00
Delivery LD00
Invoice RD00

SAP script as an attachment to fax

Similar Messages

Maybe you are looking for