Email Vendor Remittance Advice

Hi,
We have a requirement of emailing vendor remittance, I have activate the BTE 2040 and it is working fine for me. Now my question is I need your help in two areas
1) Changing the file name, currently it is generating payment advice note dated XXXXXXXx, we have current requirment as combination of company code/vendor name etc....
2) I need to fill the body of the email with some standard text, how can I do this.
Can anyone help me in finding a solution for this.
Thanks,
Srini

Hello,
Copy the SAMPLE_PROCESS_00002040 function module to ZSAMPLE_PROCESS_00002040 and make the required changes within the FM.
Please refer:
SAP NOTE 1033893, 836169.
Also see Note 521587.
Regards,
Ravi

Similar Messages

Emailing payment remittance advice

Dear all,
Within our company we want to use the functionality of emailing payment remittance advices.
It should work as follow:
When the payment run within F110 has completed then the remittance advice should be mailed in a PDF file to our vendors if the email address is maintained in the vendor master. If the email address is not maintained then the remittance should be faxed. if the fax is also not maintained then nothing should happen and we will then print the remittance advice manually and fax it to our vendors.
Has anyone of you set this up before and what are the steps you have taken to implement this functionality.
kind regards,
Camilla

In case this helps, the steps I used to setup payment advices are included below:
Copy SAPScript Form F110_US_AVIS in client 000 into ZF110_US_AVIS in active client and modify the form to meet your needs,
Setup Paying Company Codes for Payment Transactions (Pay CoCd 110, Form for payment advice ZF110_US_AVIS),
Setup Payment Methods per Company Code for Payment Transactions (CoCd 110, PayType W, Always Payment Advice),
Setup Payment Methods per Country for Payment Transactions (Country US, PayType W, Payment Medium Program RFFOD__S),
Define Accounting Clerks linked to appropriate userids
Setup accounting clerk userids with appropriate names, e-mail addresses and phone numbers. These will be printed in the payment advices.
Setup Payment Run (Trans F110) with appropriate print variant,
Follow instructions in OSS Notes 836169, 521587 and 674985 if payment advices should be sent via e-mail.

F110 Email Vendor payment advices.

Hi SAP Gurus,
Today we are printing email advices to our vendors, we would like to change this so that we can email payment advices to our vendors.
I have looked at different messages here at SDN, but I cannot get it to work.
I have in FIBF - settings, process modules and customer - created Z_SAMPLE_Process_00002040.
We are using form F110_IN_AVIS.
We are using payment medium program RFFOEDI1.
I have defined a email adress on the vendor and set the standard communication mth. to INT E.Mail.
But it is not working, what am I missing ?.
Thanks and best regards
Pernille

Dear Pernille,
please kindly check the following hints to help you:
1) Please check whether you selected the check box in the variant
configuration "print payment advice". The variant is of the variant
that you maintain in the printout/data medium tab of transaction F110.
2) Unfortunately it's technically not possible to send remittance
advices per e-mail and to spool at the same time. You can only either
send advices per e-mail or send them to spool. This is the standard
system design.
3) Please check FBZP to the desired company code and payment method to
see if the customer has selected the flag "NoPaymentAdv.". It must be
set as "Always payment Advice" and afterwards the advices via e-mail is
executed.
4) Please refer the documentation on the sample function module:
'SAMPLE_PROCESS_00002040' in FIBF by following the Menu Path:
FIBF > Environment > Infosystem (Processes) > Click 'Execute' >
Select: 00002040 Autom. pmnt transactns: Output of pmnt advice note
5) To send a business partner a payment advice note by fax or email,You
must use the process interface 00002040 (Business Transaction Events)
define the selection of the message type (printout, fax or email).
Before you can do this, however, you must have carried out the
necessary technical (Basis) settings for faxing or sending emails.
6) Also consider the SAP note 836169.
Thanks.
Mauri

Xdodelivery.cfg file - email supplier remittance advice R12

I have created xdodelivery.cfg file in $XDO_TOP/resource directory.
1. What is host name? like my apps server host name or email server host name?
2. What is server name again? (isn't it same as host name? which server?)
3. what is IEX: SMTP Host profile option? (is it same as host name in .cfg)
Are all these values same or each has different meaning?
<?xml version="1.0" encoding="UTF-8" ?>
<config xmlns="http://xmlns.oracle.com/oxp/delivery/config">
<servers>
<server name="mysmtp1" type="smtp_email" default="true">
<host>myhost.mydomain</host>
<port>25</port>
</server>
</servers>
<properties>
<property name="ds-temp-dir">/tmp</property>
<property name="ds-buffering">true</property>
<property name="SMTP_CONTENT_TYPE:String">"application/pdf"</property>
</properties>
</config>
1. Set the IBY: XML Publisher Delivery Manager Configuration File system profile with the directory where the xdodelivery.cfg file is located.
2. Verify both of the following profiles are set and are correct:
IEX: SMTP From
IEX: SMTP Host
3. Additionally, go to application developer application -> messages query up IBY_FD_SRA_EMAIL_FROM change the email from to your desired text
Thanks,
Munna

Hi Vinay,
You'll have some reassurance in at least that I had the same problem with a R12 upgrade with Separate Remittance Advice. Unfortunately, I was not able to remain on the client site long enough to solve this, although I do have the following to offer, even if its not a solution:
1) The xdodelivery.cfg file for one of our clients where this does work is as follows:
<?xml version="1.0" encoding="UTF-8" ?>
<config xmlns="http://xmlns.oracle.com/oxp/delivery/config">
<servers>
<server name="mysmtp1" type="smtp_email" default="true">
<host>r12p660.<company_name>.co.uk</host>
<port>25</port>
</server>
</servers>
<properties>
<property name="ds-temp-dir">/usr/tmp/PROD</property>
<property name="ds-buffering">true</property>
<property name="SMTP_CONTENT_TYPE:String">"application/pdf"</property>
</properties>
</config>
2) I note in the error the the SMTP sever is null. In my example setup the local host (e.g KWDMXV41). The XML file may be in $INST_TOP/appl/admin and will be called <ORACLE_SID>_KWDMXV41.xml
3) You have the following error in the stack: "oracle.apps.xdo.delivery.MissingRequiredPropertyException: Required property missing. Property name :HOST". This may imply that either the host is not defined in some profile option or the host is not being recognised by the program. Is this a multi-tier system, is there an entry in the /etc/hosts file?
I hope that may be so some help.
Thanks,
Mark

Email Payment(Remittance) advice to specific vendors or Company Code

Hi ,
I want to send Payment advice via email.I know how to configure this in FIBF.
But I want this email to be triggered for a specific company code and not all.
Can you please advise how to do it.
Kind Regards,
Venkat

Please let me know if there is a solution to the above.
Venkat

Vendor Remittance Advice

Hi Guys,
Where can I get the remittance advise for a vendor? I want to send an email to a vendor with all their remittance advise.
cheers
Sam

Hi,
I have configured automatic email process in my company. The process is as follows:
Step 1- Define Std communication method as SMTP (Internet mail) in vendor master
Step 2 Maintain email address via FK02.
Step 3 - T-Code BERP Code to find Find event 00002040 This is a Function called SAMPLE_PROCESS_00002040, copy with another name i.e. ZSAMPLE_PROCESS_00002040
Step 4 T-Code FIBF -> Option -> Product ->a Customer, Write product name at your choice (for example ZMAIL) and make it active.
Step 5 T-Code FIBIF -> Option ->Process Function (or Module) ->. A Customer.
Process = 00002040
Module Function = ZSAMPLE_PROCESS_00002040
Product = ZMAIL (name of product define by you in step 4)
Also maintain configuration in FBZP (Payment methods in company code) under forms - Always send payment advice.
Cheers adn good luck
Rajesh
it will automatically send mail to vendor provided SCOT is configured.

Emailing remittance advice

Hi all,
i have configured emails for remittance advice using business transaction event 2040 from FIBF. This works fine but does anyone have an idea where I could configure the email content? At the moment I just get a PDF of the SAPscript remittance form - but I would like to add some company specific text to the body of the email and also change the subject line. Is there a user exit somewhere?
Cheers,
Gavin

Hello Gavin,
Take a look at OSS note 521587. It will help with changing the subject line using
BTE 2050. The reason we used this was that the subject line and the file name of the attachement sent in the email are the same. The subject line always has the value "Payment advice note from <DATE>". Since DATE is formatted as YYYY/MM/DD or whatever, the filename always had some '/s' in it . Some of the recipients of these emails were finding that their AntiVirus software was filtering these emails. So we changed the subject line( and therefore the filename) and the emails were then received.
Sorry I don't have any ideas about your other question
Regards
Greg Kern

Disable R12 Remittance Advice Emails

Hi All,
We have just setup workflow mailer for first time in PROD.
Suppliers started getting emails for remittance advice emails after workflow mailer setup. We do not want this feature of remittance advice emails.
How can we disable remittance advice emails for all the users in R12?
Also, How can someone find out that remittance advice emails are being sent or not from backend using plsql?
Please help.
We are on R12.1.3
Thanks,
Sachin

Hello Gurus,
Any help please?
Regards,
Sachin

Vendor remittence advice

Hi SAP Techies
Our client is looking for a Vendor remittance advice, notifying the vendors when a payment has been made. Is there any way we can use SAP to raise our remittance advices? We would need to be able to chose which invoices to include on the paperwork. How do we configure in SAP. Please advice.
Kind regards
Edited by: akausar on Apr 23, 2010 4:50 AM
Edited by: akausar on Apr 23, 2010 5:11 AM

You must have created a form with the help of ABAPer and assign it in FBZP settings.
COT must have been configured by your Basis Consultants (pre-requisite)
In SOST, gateway, the entries generated to SMTP server can be seen
Go FIBF
Settings ==> Process Modules => of an SAP application
Process: 00002040
Application: FI-FI
Function Module: ZSAMPLE_PROCESS_00002040
This function module must have been changed by copying from standard SAP function module SAMPLE_PROCESS_00002040, to suit your requirements. (accordingly the field from which the email address has to be picked also needs to be changed.)
When you run F110, you can see SOST, that the email are getting generated.
Thanks,
Ravi
PS:
Refer following notes:
Note 836169 - Consulting: Payment advice notes by email or fax
Configure in FIBF transaction code for process 00002040
Copy the Function Module SAMPLE_PROCESS_00002040 to ZSAMPLE_PROCESS_00002040 according to your requirement, as described in the above SAP note.

Send remittance advice by email to vendors

When automatic payment (F110) run is done to make payment to vendors,it generates a PAYEXT IDOC to be send to bank for payments.
Print output program is RFFOEDI1
Remittance advice standard SAP script is F110_IN_AVIS.
What are the ways to send email in PDF format? DO we need to write a code or is there ay facility like message control?

you need to use available FM's to convert the data into PDF and send as attachment via email..

Remittance advice to multiple email id for one vendor

Hi All,
in vendor master data, we maintain email id for sending remittance advice to vendor. We have requirement to send remittance advice on more than one email id for a single vendor.
Could you please advice how we can do this.
Regards
Deepak

Hi ,
We have done this . We created Z table where we can keep upte 3 mails ID for one Vendor and Payment ment progran look for that table when Generates Payment Advice .
Many Thanks

Mailing remittance advice to multiple email id of vendor

Hi,
We have requirement that remittance advice need to be send to multiple email ids of vendor.
I have implemented SAP note Note 1033893, which says after applying the note the email can be sent to multiple email ids by seperating the email ids by space in field c_finaa-intad in BTE 2040.
But when i am trying to send the email to multiple ids is its throughing an error 'Advice note for pymt 1000 1500010133 will be printed; dispatch via e-mail not poss.', but when i tried to send with one email id . its working fine.
Please help if you know any solution..
Thanks,
Rasmi Ranjan Mishra
ABAP Programmer
<removed by moderator>
Edited by: Thomas Zloch on Aug 12, 2011 3:35 PM - please do not post contact information

Any one has solution for this ? We are also looking for solution. Thanks in advance.

Remittance advice to multiple Emails of Vendor

Hi Friends,
Business would like to have the functionality of sending Remittance advices to multiple email ids of a vendor.
As we know, we can add as many email ids as in the vendor master but only one email id is active at a time.
As I see in this forum - one way of doing is creating the group id in which we maintain all email ids of a vendor in the exchange server and assign it to the vendor master.
When F110 runs remittance advices goes automatically to group id and hence to multiple emails of vendor.
I would like to know, is there any other method of acheiving the same result. ( either with any functional module or userexits)?
Can we achieve the same result with ABAP modification in the standard payment program RFFOUS_T.?
Thanks in advance.
Kris

Hi
Please check these function modules:
SO_DOCUMENT_RECEIVE_API1
SO_DOCUMENT_RESUBMIT_API1
SO_DOCUMENT_SEND_API1
SO_DOCUMENT_SET_STATUS_API1
SO_DOCUMENT_UPDATE_API1
Regards
Suresh

Trigerring email to vendor in remittance advice script

hi,
I have finished remittance advice using script, nw i have to send mail to the vendor and e-mail has to be picked from the Vendor e-mail Id field.please let me know how to do this action.
thanks in advanace

Hi,
http://www.sapdevelopment.co.uk/reporting/rep_spooltopdf.htm
or
*& Report ZSPOOLTOPDF                                                 *
*& Converts spool request into PDF document and emails it to           *
*& recipicant.                                                         *
*& Execution                                                           *
*& This program must be run as a background job in-order for the write *
*& commands to create a Spool request rather than be displayed on      *
*& screen                                                              *
REPORT zspooltopdf.
PARAMETER: p_email1 LIKE somlreci1-receiver
                                    DEFAULT '@sapdev.co.uk',
           p_sender LIKE somlreci1-receiver
                                    DEFAULT '@sapdev.co.uk',
           p_delspl AS CHECKBOX.
*DATA DECLARATION
DATA: gd_recsize TYPE i.
Spool IDs
TYPES: BEGIN OF t_tbtcp.
        INCLUDE STRUCTURE tbtcp.
TYPES: END OF t_tbtcp.
DATA: it_tbtcp TYPE STANDARD TABLE OF t_tbtcp INITIAL SIZE 0,
      wa_tbtcp TYPE t_tbtcp.
Job Runtime Parameters
DATA: gd_eventid LIKE tbtcm-eventid,
      gd_eventparm LIKE tbtcm-eventparm,
      gd_external_program_active LIKE tbtcm-xpgactive,
      gd_jobcount LIKE tbtcm-jobcount,
      gd_jobname LIKE tbtcm-jobname,
      gd_stepcount LIKE tbtcm-stepcount,
      gd_error    TYPE sy-subrc,
      gd_reciever TYPE sy-subrc.
DATA: w_recsize TYPE i.
DATA: gd_subject   LIKE sodocchgi1-obj_descr,
      it_mess_bod LIKE solisti1 OCCURS 0 WITH HEADER LINE,
      it_mess_att LIKE solisti1 OCCURS 0 WITH HEADER LINE,
      gd_sender_type     LIKE soextreci1-adr_typ,
      gd_attachment_desc TYPE so_obj_nam,
      gd_attachment_name TYPE so_obj_des.
Spool to PDF conversions
DATA: gd_spool_nr LIKE tsp01-rqident,
      gd_destination LIKE rlgrap-filename,
      gd_bytecount LIKE tst01-dsize,
      gd_buffer TYPE string.
Binary store for PDF
DATA: BEGIN OF it_pdf_output OCCURS 0.
        INCLUDE STRUCTURE tline.
DATA: END OF it_pdf_output.
CONSTANTS: c_dev LIKE sy-sysid VALUE 'DEV',
           c_no(1)     TYPE c   VALUE ' ',
           c_device(4) TYPE c   VALUE 'LOCL'.
*START-OF-SELECTION.
START-OF-SELECTION.
Write statement to represent report output. Spool request is created
if write statement is executed in background. This could also be an
ALV grid which would be converted to PDF without any extra effort
WRITE 'Hello World'.
new-page.
commit work.
new-page print off.
IF sy-batch EQ 'X'.
    PERFORM get_job_details.
    PERFORM obtain_spool_id.
Alternative way could be to submit another program and store spool
id into memory, will be stored in sy-spono.
*submit ZSPOOLTOPDF2
       to sap-spool
       spool parameters   %_print
       archive parameters %_print
       without spool dynpro
       and return.
Get spool id from program called above
IMPORT w_spool_nr FROM MEMORY ID 'SPOOLTOPDF'.
    PERFORM convert_spool_to_pdf.
    PERFORM process_email.
    if p_delspl EQ 'X'.
      PERFORM delete_spool.
    endif.
    IF sy-sysid = c_dev.
      wait up to 5 seconds.
      SUBMIT rsconn01 WITH mode   = 'INT'
                      WITH output = 'X'
                      AND RETURN.
    ENDIF.
ELSE.
    SKIP.
    WRITE:/ 'Program must be executed in background in-order for spool',
            'request to be created.'.
ENDIF.
      FORM obtain_spool_id                                          *
FORM obtain_spool_id.
CHECK NOT ( gd_jobname IS INITIAL ).
CHECK NOT ( gd_jobcount IS INITIAL ).
SELECT * FROM tbtcp
                 INTO TABLE it_tbtcp
                 WHERE      jobname     = gd_jobname
                 AND        jobcount    = gd_jobcount
                 AND        stepcount   = gd_stepcount
                 AND        listident   <> '0000000000'
                 ORDER BY   jobname
                            jobcount
                            stepcount.
READ TABLE it_tbtcp INTO wa_tbtcp INDEX 1.
IF sy-subrc = 0.
    message s004(zdd) with gd_spool_nr.
    gd_spool_nr = wa_tbtcp-listident.
    MESSAGE s004(zdd) WITH gd_spool_nr.
ELSE.
    MESSAGE s005(zdd).
ENDIF.
ENDFORM.
      FORM get_job_details                                          *
FORM get_job_details.
Get current job details
CALL FUNCTION 'GET_JOB_RUNTIME_INFO'
       IMPORTING
            eventid                 = gd_eventid
            eventparm               = gd_eventparm
            external_program_active = gd_external_program_active
            jobcount                = gd_jobcount
            jobname                 = gd_jobname
            stepcount               = gd_stepcount
       EXCEPTIONS
            no_runtime_info         = 1
            OTHERS                  = 2.
ENDFORM.
      FORM convert_spool_to_pdf                                     *
FORM convert_spool_to_pdf.
CALL FUNCTION 'CONVERT_ABAPSPOOLJOB_2_PDF'
       EXPORTING
            src_spoolid              = gd_spool_nr
            no_dialog                = c_no
            dst_device               = c_device
       IMPORTING
            pdf_bytecount            = gd_bytecount
       TABLES
            pdf                      = it_pdf_output
       EXCEPTIONS
            err_no_abap_spooljob     = 1
            err_no_spooljob          = 2
            err_no_permission        = 3
            err_conv_not_possible    = 4
            err_bad_destdevice       = 5
            user_cancelled           = 6
            err_spoolerror           = 7
            err_temseerror           = 8
            err_btcjob_open_failed   = 9
            err_btcjob_submit_failed = 10
            err_btcjob_close_failed = 11
            OTHERS                   = 12.
CHECK sy-subrc = 0.
Transfer the 132-long strings to 255-long strings
LOOP AT it_pdf_output.
    TRANSLATE it_pdf_output USING ' ~'.
    CONCATENATE gd_buffer it_pdf_output INTO gd_buffer.
ENDLOOP.
TRANSLATE gd_buffer USING '~ '.
DO.
    it_mess_att = gd_buffer.
    APPEND it_mess_att.
    SHIFT gd_buffer LEFT BY 255 PLACES.
    IF gd_buffer IS INITIAL.
      EXIT.
    ENDIF.
ENDDO.
ENDFORM.
      FORM process_email                                            *
FORM process_email.
DESCRIBE TABLE it_mess_att LINES gd_recsize.
CHECK gd_recsize > 0.
PERFORM send_email USING p_email1.
perform send_email using p_email2.
ENDFORM.
      FORM send_email                                               *
--> p_email                                                       *
FORM send_email USING p_email.
CHECK NOT ( p_email IS INITIAL ).
REFRESH it_mess_bod.
Default subject matter
gd_subject         = 'Subject'.
gd_attachment_desc = 'Attachname'.
CONCATENATE 'attach_name' ' ' INTO gd_attachment_name.
it_mess_bod        = 'Message Body text, line 1'.
APPEND it_mess_bod.
it_mess_bod        = 'Message Body text, line 2...'.
APPEND it_mess_bod.
If no sender specified - default blank
IF p_sender EQ space.
    gd_sender_type = space.
ELSE.
    gd_sender_type = 'INT'.
ENDIF.
Send file by email as .xls speadsheet
PERFORM send_file_as_email_attachment
                               tables it_mess_bod
                                      it_mess_att
                                using p_email
                                      'Example .xls documnet attachment'
                                      'PDF'
                                      gd_attachment_name
                                      gd_attachment_desc
                                      p_sender
                                      gd_sender_type
                             changing gd_error
                                      gd_reciever.
ENDFORM.
      FORM delete_spool                                             *
FORM delete_spool.
DATA: ld_spool_nr TYPE tsp01_sp0r-rqid_char.
ld_spool_nr = gd_spool_nr.
CHECK p_delspl <> c_no.
CALL FUNCTION 'RSPO_R_RDELETE_SPOOLREQ'
       EXPORTING
            spoolid = ld_spool_nr.
ENDFORM.
*&      Form SEND_FILE_AS_EMAIL_ATTACHMENT
      Send email
FORM send_file_as_email_attachment tables it_message
                                          it_attach
                                    using p_email
                                          p_mtitle
                                          p_format
                                          p_filename
                                          p_attdescription
                                          p_sender_address
                                          p_sender_addres_type
                                 changing p_error
                                          p_reciever.
DATA: ld_error    TYPE sy-subrc,
        ld_reciever TYPE sy-subrc,
        ld_mtitle LIKE sodocchgi1-obj_descr,
        ld_email LIKE somlreci1-receiver,
        ld_format TYPE so_obj_tp ,
        ld_attdescription TYPE so_obj_nam ,
        ld_attfilename TYPE so_obj_des ,
        ld_sender_address LIKE soextreci1-receiver,
        ld_sender_address_type LIKE soextreci1-adr_typ,
        ld_receiver LIKE sy-subrc.
data:   t_packing_list like sopcklsti1 occurs 0 with header line,
        t_contents like solisti1 occurs 0 with header line,
        t_receivers like somlreci1 occurs 0 with header line,
        t_attachment like solisti1 occurs 0 with header line,
        t_object_header like solisti1 occurs 0 with header line,
        w_cnt type i,
        w_sent_all(1) type c,
        w_doc_data like sodocchgi1.
ld_email   = p_email.
ld_mtitle = p_mtitle.
ld_format              = p_format.
ld_attdescription      = p_attdescription.
ld_attfilename         = p_filename.
ld_sender_address      = p_sender_address.
ld_sender_address_type = p_sender_addres_type.
Fill the document data.
w_doc_data-doc_size = 1.
Populate the subject/generic message attributes
w_doc_data-obj_langu = sy-langu.
w_doc_data-obj_name = 'SAPRPT'.
w_doc_data-obj_descr = ld_mtitle .
w_doc_data-sensitivty = 'F'.
Fill the document data and get size of attachment
CLEAR w_doc_data.
READ TABLE it_attach INDEX w_cnt.
w_doc_data-doc_size =
     ( w_cnt - 1 ) * 255 + STRLEN( it_attach ).
w_doc_data-obj_langu = sy-langu.
w_doc_data-obj_name   = 'SAPRPT'.
w_doc_data-obj_descr = ld_mtitle.
w_doc_data-sensitivty = 'F'.
CLEAR t_attachment.
REFRESH t_attachment.
t_attachment[] = it_attach[].
Describe the body of the message
CLEAR t_packing_list.
REFRESH t_packing_list.
t_packing_list-transf_bin = space.
t_packing_list-head_start = 1.
t_packing_list-head_num = 0.
t_packing_list-body_start = 1.
DESCRIBE TABLE it_message LINES t_packing_list-body_num.
t_packing_list-doc_type = 'RAW'.
APPEND t_packing_list.
Create attachment notification
t_packing_list-transf_bin = 'X'.
t_packing_list-head_start = 1.
t_packing_list-head_num   = 1.
t_packing_list-body_start = 1.
DESCRIBE TABLE t_attachment LINES t_packing_list-body_num.
t_packing_list-doc_type   = ld_format.
t_packing_list-obj_descr = ld_attdescription.
t_packing_list-obj_name   = ld_attfilename.
t_packing_list-doc_size   = t_packing_list-body_num * 255.
APPEND t_packing_list.
Add the recipients email address
CLEAR t_receivers.
REFRESH t_receivers.
t_receivers-receiver = ld_email.
t_receivers-rec_type = 'U'.
t_receivers-com_type = 'INT'.
t_receivers-notif_del = 'X'.
t_receivers-notif_ndel = 'X'.
APPEND t_receivers.
CALL FUNCTION 'SO_DOCUMENT_SEND_API1'
       EXPORTING
            document_data              = w_doc_data
            put_in_outbox              = 'X'
            sender_address             = ld_sender_address
            sender_address_type        = ld_sender_address_type
            commit_work                = 'X'
       IMPORTING
            sent_to_all                = w_sent_all
       TABLES
            packing_list               = t_packing_list
            contents_bin               = t_attachment
            contents_txt               = it_message
            receivers                  = t_receivers
       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.
Populate zerror return code
ld_error = sy-subrc.
Populate zreceiver return code
LOOP AT t_receivers.
    ld_receiver = t_receivers-retrn_code.
ENDLOOP.
ENDFORM.
Regards,
Kumar

How do I add an email body text for remittance advices / payment advices?

Hello,
I am trying to send an email body text with the pdf remittance advice to my vendors.
Background:
We are running automatic payments to vendors via transaction F110. We have configured the pay run to produce remittance advices for vendor payments. Finally we activated the BTE 00002040, through transaction FIBF, to use a custom copy of the function module SAMPLE_PROCESS_00002040.
Our payment run sends emails with pdf-file attachments to our vendors correctly.
<b>The Issue:</b>
I can not find a way to add text to the body of the email with the attached remittance advice.
Has anyone advise on how to populate the email body with text?
Thank you and best regards
Karsten Arold

Hello Subhashree,
I have not implemented the functionality, but I found rerference to SAP Note 1033893 in another forum post.
Email text to Payment Advice in BTE2040
Allan

Email Vendor Remittance Advice

Similar Messages

Maybe you are looking for