When sending email PO in a PDF attachment, the attachment can not be openen

Question

Hi all,
We are trying to send an email with the PO in PDF format.  We got the email but the attachment can not be opened. 
Error reads: Adobe could not open test.pdf because  it is either  not a supported file type  or because  the file has been damaged (for example , it was send as a email attachemnet and was not  correctly decoded).
Could any body bring some light?   We know that everything in SCOT is fine because we can email the PO through configuration to the vendor without problem. It is just these extra copies that do not work.
a) We are modifying our custom Print program to add the code below after closing the form.
in few words:
a) We are getting the OTF from closing the form.
b) Converting the OTF to PDF
c) Sending the PDF as attachment.
data: lt_docs      TYPE TABLE OF docs.
data: pdf_bytecount TYPE i.
data: begin of pdfout occurs 0,
   tline type tline,
end of pdfout.
Ende Formulardruck --------------------------------------------------*
  CALL FUNCTION 'CLOSE_FORM'
       IMPORTING
            result = result
       tables
            otfdata = otf.
  IF RESULT-TDSPOOLID NE SPACE.
    SPOOLID = RESULT-TDSPOOLID.
    PERFORM PROTOCOL_UPDATE USING '320' SPOOLID SPACE SPACE SPACE.
  ENDIF.
  if result-userexit eq 'C' or
      result-userexit eq 'E'.
    retco = '9'.
  endif.
  CALL FUNCTION 'CONVERT_OTF_2_PDF'
    IMPORTING
      bin_filesize           = pdf_bytecount
    TABLES
      otf                    = otf
      doctab_archive         = lt_docs
      lines                  = pdfout
    EXCEPTIONS
      err_conv_not_possible  = 1
      err_otf_mc_noendmarker = 2
      OTHERS                 = 3.
Creation of the document to be sent File Name
   maildata-obj_name = 'TEST'.
Mail Subject
   maildata-obj_descr = 'Subject'.
Mail Contents
   append mailtxt.
  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.
Move OTF code to structure SOLI form email
CLEAR solisti1. REFRESH solisti1.
LOOP AT otf.
  solisti1-line = otf.
  APPEND solisti1.
ENDLOOP.
Move pdf code to structure soli form email
  clear solisti1. refresh solisti1.
  loop at pdfout.
    solisti1-line = pdfout.
    append solisti1.
  endloop.
  loop at solisti1.
     move-corresponding solisti1 to mailbin.
     append mailbin.
  endloop.
  describe table mailbin lines tab_lines.
mailhead = 'TEST.OTF'.
  mailhead = 'TEST.PDF'.
  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-doc_type = 'PDF'.
  mailpack-obj_name = 'TEST'.
  mailpack-obj_descr = 'Subject'.
  mailpack-doc_size = tab_lines * 255.
  append mailpack.
  mailrec-receiver = '[email protected]'.
  mailrec-rec_type = 'U'.
  append mailrec.
  mailrec-receiver = '[email protected]'.
  mailrec-rec_type = 'U'.
  append mailrec.
  CALL FUNCTION 'SO_NEW_DOCUMENT_ATT_SEND_API1'
          EXPORTING
               DOCUMENT_DATA              = maildata
          TABLES
               PACKING_LIST               = mailpack
               OBJECT_HEADER              = mailhead
               CONTENTS_TXT               = mailtxt
               RECEIVERS                  = mailrec
          EXCEPTIONS
               TOO_MANY_RECEIVERS         = 1
               DOCUMENT_NOT_SENT          = 2
               DOCUMENT_TYPE_NOT_EXIST    = 3
               OPERATION_NO_AUTHORIZATION = 4
               PARAMETER_ERROR            = 5
               X_ERROR                    = 6
               ENQUEUE_ERROR              = 7
               OTHERS                     = 8.
ENDFORM.

Answer 1

Dear Monica,
  You need to configure the system with respect to functional point of view and need to write the following code in print program. i have done this and solution is as follows.
<b>  Reward me for this solution.</b>
Process 11 (MM)     Sending RFQs and POs to vendors directly from the system instead of sending thru Courier or Fax     
Existing Process (AS-IS)     Presently system is not supporting this requirement
Business Requirements     RFQ’s to be linked with vendor master with e-mail to send enquiries directly through system instead of courier/fax. Vice versa P.O’s.  Specifications, drawings should also go to vendor along with mail.
To-Be     
Configuration Settings:                  
1) Spro – Materials management – Purchasing – Messages – Output control – Message types – Define message types for RFQ/ PO
•     Created ZEK1,ZMI and ZEK2 for RFQs
•     Created ZIK,ZOC,ZOK,ZOM,ZSI, ZSK2 and ZSM for Pos
•     The above New output types Included with existing Print Forms and Programs but modified with External send(5) medium, and added company’s letter head thru ABAP developments (details provided below)
•     The above new output types also maintained for Fine- tuned control (thru same navigation) for New(1) and Change(2) operations
      2) Spro – Materials management – Purchasing – Messages – Output control – Message   determination schemas – Define message schema for RFQ/ PO
•     Maintained the new output types in the control data
3)     Maintain Condition records for the New out put types (copied same document types from the existing old output types)
Easy access – Logistics – Materials management – Purchasing – Master data – Messages – MN01 (for RFQs)/ MN04 (for Pos)
4)     Maintain Email id of Vendor in Vendor master.
Developments (ABAP):
1)  Copied the existing print programs and forms of the corresponding out types.
2) Addition of header window in each corresponding form (HEADER window). Uploaded the HEADER3 graphics in the header window.
INCLUDE HEADER3 OBJECT GRAPHICS ID BCOL LANGUAGE EN
3) Added the the following code in TOP includes
                   TYPE-POOLs szadr.
           INCLUDE:  LMEDRUCKF09.
data: intnast         LIKE snast,
      lvs_recipient   LIKE swotobjid,       "Internet
      lvs_sender      LIKE swotobjid,       "Internet
      lvs_comm_type   TYPE ad_comm,
      lvs_comm_values TYPE szadr_comm_values,
      p_retco         TYPE i.
5)     Addition of the perform to SOS include for header window display
       PERFORM WRITE_FORM_HEADER.
*&      Form  WRITE_FORM_HEADER
      text
-->  p1        text
<--  p2        text
FORM WRITE_FORM_HEADER.
CALL FUNCTION 'WRITE_FORM'
EXPORTING
   ELEMENT                        = 'HE1'
   FUNCTION                       = 'SET'
   TYPE                           = 'BODY'
   WINDOW                         = 'HEADER'
IMPORTING
   PENDING_LINES                  =
EXCEPTIONS
   ELEMENT                        = 1
   FUNCTION                       = 2
   TYPE                           = 3
   UNOPENED                       = 4
   UNSTARTED                      = 5
   WINDOW                         = 6
   BAD_PAGEFORMAT_FOR_PRINT       = 7
   SPOOL_ERROR                    = 8
   CODEPAGE                       = 9
   OTHERS                         = 10
ENDFORM.
6)     In the corresponding FORM include the following code has been added.
DATA:  lvs_comm_type     TYPE   ad_comm,
        lvs_comm_values   TYPE   szadr_comm_values,
        xprogramm         type   sy-repid.
  ... use stratagy to get communication type
      CALL FUNCTION 'ADDR_GET_NEXT_COMM_TYPE'
           EXPORTING
                strategy           = nast-tcode
                address_number     = lfa1-adrnr
           IMPORTING
                comm_type          = lvs_comm_type
                comm_values        = lvs_comm_values
           EXCEPTIONS
                address_not_exist  = 1
                person_not_exist   = 2
                no_comm_type_found = 3
                internal_error     = 4
                parameter_error    = 5
                OTHERS             = 6.
      IF sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
           WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
convert communication data
      MOVE-CORRESPONDING nast TO intnast.
      MOVE sy-repid           TO xprogramm.
7) By using the function module we can get sender and reciepient mail ids to variables lvs_recipient    lvs_sender
      CALL FUNCTION 'CONVERT_COMM_TYPE_DATA'
           EXPORTING
                pi_comm_type              = lvs_comm_type
                pi_comm_values            = lvs_comm_values
                pi_country                = lfa1-land1
                pi_repid                  = xprogramm
                pi_snast                  = intnast
           IMPORTING
                pe_itcpo                  = itcpo
                pe_device                 = xdevice
                pe_mail_recipient         = lvs_recipient
                pe_mail_sender            = lvs_sender
           EXCEPTIONS
                comm_type_not_supported   = 1
                recipient_creation_failed = 2
                sender_creation_failed    = 3
                OTHERS                    = 4.
      IF sy-subrc <> 0.
      Avoids cancellation with message TD421
        p_retco = '1'.                                           "831984
        PERFORM protocol_update USING '740' space space space space.
      dummy message to make the message appear in the where-used list
        IF 1 = 2.
          MESSAGE S740(me).
        ENDIF.
        EXIT.
      ENDIF.
      IF xdevice = 'MAIL'.                                       "885787
    Check validity of email address to avoid cancellation with TD463
        CALL FUNCTION 'SX_ADDRESS_TO_DEVTYPE'                    "831984
          EXPORTING
            recipient_id            = lvs_recipient
            sender_id               = lvs_sender
          EXCEPTIONS
            err_invalid_route       = 1
            err_system              = 2
            OTHERS                  = 3.
        IF SY-SUBRC <> 0.
          p_retco = '1'.
          PERFORM protocol_update USING '740' space space space space.
       dummy message to make the message appear in the where-used list
          IF 1 = 2.
            MESSAGE S740(me).
          ENDIF.
          EXIT.
        ENDIF.
      ENDIF.
8)     Attaching the new print program and form in NACE transaction.
Steps for End user:
1)     Creating the Purchase Order or RFQ with suitable document type through ME21N or ME41 .
2)     Executing the transaction ME9F and in selecting the suitable output type.
3)     Executing the transaction ZSEND_PDOC using INT as input.
4) With above steps we can able to send purchase order or RFQ to vendor as an attachment through e-mail in PDF format.
Regards
Badari