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

Similar Messages

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 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

Email payment advice for multiple emails

Hi There,
I have configured the BTE 00002040, every thing works perfectly to send the payment advice to a single email id from vendor master but out client wants a copy of the payment advice also to sent to their group email id, so with the help of our abaper we are trying to hard code the group email id and try to send the email to both vendor email id and group email id but is it nor working.
Can any body tell me how to send the payment advice to multiple emails?
Thank you in advance
Madhu

Thank you Hugo,
We tried this but for some reason it is not working, i know some body else also suggested the same on SDN but no luck.
It works fine for one emaild from vendor master but not when we put the group email id in the program as a hard code.
pl let me know, if you have any other thoughts.
Thanks
Madhu

Send Payment advice to multiple email ids

Hi,
We have requirement that payment advice need to be send to multiple vendor email ids.
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 not going , when i tried to send with one email id . its working fine.
i am using RFFOAVIS_FPAYM to send the payment list.
Please help if you know any solution..
Thanks,
Geeta

Hi,
Create the distribution list and maintain the email ids in that.
T.code : SO23 - to create a distribution list.
And fuctional consultant that whether they can assign this distriution list in SRO to get the all email ids or u may have to write code in user exit.
Thanks.
Balu

To send Payment advice note as Email to vendor

Hi
I like to know how can we send the payment advice note created after F110 run to be send as email to the vendor?
your help would be appreciated a lot
regards
auro

Hi Arvind,
Check out the following link
Re: f110 payment advice
Assign points if useful
Regards
Genie

Multiple Email Addresses in the Seperate Remittance Advice Delivery setup

In R12 Oracle Payables, is it posssible to specify multiple email addresses in the Email field under the Separate Remittance Advice Delivery tab. This is to send separate remittance advice to multiple email addresses for a given supplier / supplier site.
Navigation:
Responsibility: Payables Manager
(N): Suppliers -> Entry
Query a supplier.
On the left side, click on Payment Details
Click on the Update Payment Details icon for a supplier site
Click on the tab Separate Remittance Advice Delivery
Select Delivery Method = Email
Enter email address in the Email field.
Does Oracle support comma or semi-color delimited email addresses entered in the Email field, by which Separate Remittance Advices can be sent to those email addresses?
Thanks.

Oracle support comma to specify multiple email address.
I have tested the same in R11i instance and specified multiple email address with comma as separator.
Hope this helps.
Thanks and Regards
Manish Jain.

Remittance Advice to Vendor

Hi Expertise,
In fact I am required to deliver the Remittance Advice in SMARTFORMS to the vendor for thier invoices paid. For example after running the automatic payment run (F110), we issue a check or do EFT transfer direct to the vendor's bank account. But along with this we also required to give remittance advice containing the invoice details paid etc. Now I am unable to find out these details to make a SMARTFORMS for the remittance advice. Following are the informations to appear in the remittance advice :
Rimittance Date (SAP payment date)
Vendor Invoice No. ( We put the same in reference field during MIRO / FB60 )
Vendor Invoice date ( We put the same in document date filed MIRO / FB60 )
Vendor Invoice Amount
Discount Amount
Net Amount paid agst each advice
Total amount paid
Vendor's BSB & Account no.( We maintain in the vendor master data )
Reference ( ie the FI doc no of the vendor invoices )
Which table will give all the above informations to make a SMARTFORMS for Remittance Advice.
Your's early and accurate reply will be sincerely appreciated.
Rgds,
BABA

Hi,
From REGUP, you can identify the vendor, the vendor invoice and the amount that has been considered for the payment run. You can then refer to BKPF for the fields like vendor invoice date, vendor invoice no., reference., which I guess you input in the document header data of the invoice.
In REGUP, the entries are populated both at the time of proposal run and at the time of payment run, you will need to eliminate proposal lines using field XVORL.
If there is some info in the vendor item, then you may need to refer to BSEG (BSAK/BSIK).
Cheers
Neeraj

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..

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

Multiple email addresses against Vendor. What is the ID / sequence number?

We have a particular vendor with multiple e-mail addresses. These can be viewed via XK03, looking at the address details of the vendor and expanding the e-mail address.
What I see for one particular vendor are two lines, each with a different e-mail address.
Line one has a radio button (standard number) selected, has some text saying ' Remittance advice' and an ID of 001.
Line two has a radio button unselected, has text saying 'PO' and an ID of 002.
The problem that we have is that when PO's are e-mailed it sends it to the e-mail address on line 1 rather than line 2. Obviously this ID/sequence number is configured somewhere and I assume that the PO's somehow need to told to use ID 002 instead of 001, but where is this defined?.
Jas

SAP takes the email adress (fax number) that has the radio button for standard default.
The text ' Remittance advice' is just a note which does not control anything, especially not that this one is taken for the ' Remittance advice' only and all others would use the second mail adress.
If you want it different, then you have to code this yourself in an exit.

PO Output email ID vs Payment Remittance Advice email ID

Hi,
PO output program automatically sends PO to vendors in PDF format. Email ID is picked from vendor master - address tab - communication. Payment remittance advice is emailed to email ID in vendor master - correspondence tab - Clerk's internet field (company code data).
Couple of months back for some unknown reason/ requirement, payment remittance advice program is changed to send to email ID in vendor master - address tab - communication. To accommodate this change, we are now planning to change PO program to send to email ID in vendor master - correspondence tab (company code data).
Now the question, is it OK to use Clerk's internet field for PO email ? Will there be any disadvantage with this approach ? I know Clerk's internet field can take only one email ID whereas address email can take multiple IDs.
* One of the unknown reason/ requirement was : Remittance needs to go to multiple IDs and therefore changed to vendor master - address - communication.
Cheers,
Sankar

A very strange idea from my point of view.
you had used the clerks internet field (company code view) for financial communication in the past,
this was changed to the standard communication
and since you need a different mail address for POs you consider to use the clerks internet field in the company code view.
Undoing the change for the payment remittance advice would be more logical, as then at least Financial communication would pick its email from a financial data source, which is more logical than pulling the data from financial data source for purchasing activities.
In general you can create a PO long before a company code view is needed, this speeds up the procurement process, as the company code view is needed when you do goods or invoice receipt. So you are slowing down the process.
Using the clerks internet field would be really confusing for the users, both FI and purchasing, and it can conflict with your authorization settings too. In our system a buyer has no access to company code data.
I would eventually consider to use the Remark field in the email address to indicate for what purpose this email address is used. If you do this e.g.with a leading number 1 for finance , 2 for purchasing, then you could have a exit check on that and determine the right email address .

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 Payment advice to multiple recipients

I have successfully implemented the function module to allow emailing of payment advices but have a new requirement for the ability to email payment advices to multiple recipients. I am using the communication area in the vendor master maintenance to enter the email addresses. The z_process_2040 function module returns all of the email addresses but I'm looking for suggestions on how to repeat the output for each of the addresses returned. Has anyone done this successfully? Thanks in advance for your help.

Thank you, Naresh, for your suggestion. I will investigate to see if there is a way it can be used for a solution to our situation.
Edited by: Patricia Holland on Nov 17, 2009 3:48 PM

Automatic e-mail of remittance advice to vendors following the Payment Run

Hi,
We are implementing the Automatic e-mail of remittance advice to vendors following the Payment Run(F110) for one of our company code located at UK.
But we have already implemented this process for one of the company code located in US using the Business transaction event 00002040 and it is working fine.
Now i want to find out if we could utilitize emailing the employee reimbursement remittances for UK as we do here in the US using the same BTE.
I just want to know if our current BTE (business transaction event) can be set up for their group also along with generating the SAP script to format the remittance.
Earliest reply will be appreciated.
With regards,
Shree.J

Hi,
do you mind share with me how did you implement the Automatic email of remittnance advice to vendor after payment run?
I am in process research this solution. appreaciate if you can share with me if you have any info.
+91 9791122480
Thanks in advance.
regards
v.krishnamoorthy

Remittance advice to multiple Emails of Vendor

Similar Messages

Maybe you are looking for