Remittance advice E-mail

Hi All,
We have a remittance advice e-mail going out to vendors from AP after the check run is completed by the users. The users kick off conc. request to send the remittance advice. The module is coded to send the rem. advice when the vendors in the check run is > 10.
However, few weeks back, one of the vendors complained that they received the rem. adv of another vendor.
Does any one know if the remittance advice is a standard oracle or not?
Thanks,
Chiru

check the workflow events table...
you need a investigation, why its happen...
check the AP_PAYMENT_EVENT_WF_PKG
and see wf_notification tableThanks for the reply.
But we don't use workflow. The conc.req to send the rem. adv is kicked off manually.
I am just trying to determine if rem.adv is a standard oracle functionality or if this module is a custrom created (by earlier developers)
I opened up the shell script which is pretty intensive. The problem that I am facing is, after the code creates the rem. adv in the PDF format, it invokes the UNIX sendmail. The vendor email address and the correct PDF# to attach to it are read from a file which gets created after the checkrun process (the vendors for that checkrun and their email info is written to that file along with the PDF#). I am not able to determine if it is the sendmail which is causing it, or the company's mail server which sends out the mails after taking it from sendmail.
The module then logs to a table, which rem adv PDF got sent to which vendor. If I go by the log it shows that the correct rem adv PDFis being sent to the correct vendor. However, the vendor is complaining that they got the wrong rem adv PDF. I am trying to prove that Oracle is working correctly and it is the company's windows mail server which is goofing up. LAN admin is refusing that it is their mail server which is goofing up.
Thanks,
Chiru

Similar Messages

F110 Automatic sent remittance advice to vendor per mail

Hi,
I have an question.
Does somebody knows how to sent automatic remittance advices to vendors per mail after you have runned the payment in transaction F110?
Thanks for you help!
Regards,
Edwin

Hi,
You may also look at the possiblity to use BTE with custom function module if you seek more flexibility
FIBF > Process Module > of Customer > Process 0000002040 (Automatic Payment advice)
SAP provide a sample function module but then you need to engage your abaper to develop a custom function module.
Hope that this helps
taro

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 the vendor via mail

I have to send the Remittance Advice to the vendor via mail.
I have configured a copy of the FM SAMPLE_PROCESS_00002040 with the business transaction event 2040 . The mail is successfully sent to the vendor as (OTF) attachment, but it want to send it as (PDF) format.
Can anyone help me in this?
Regards
Shahid Rais

It's there; it just may not be the same menu path or set of keystrokes. Your email node in SCOT may also be named differently in SAPConnect. Sorry, we've been off 4.6C for 1.5 years - can't remember the exact location in that version but it's the same principle. Your SAPConnect config is set to perform no conversion whereas you need to set it to convert OTF to PDF automatically.

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.

Want to add text to mail body of BACS Remittance Advice

Hi Experts,
Blelow is the requirement.
User is sending the remittance advice to vendors, user wants to include a u2018fixedu2019 text also in that mail.
User is sending remittance advice to vendor in PDF format which is attached in a mail, I need to add some text to mail body.
But not able to find how mail body is filled up.
Main program RFFOGB_T u2013 Payment program
Includes RFFORI06 u2013 Remittance advice
Can you please suggest how I will be able to add the text to the mail ?
Regards,
Subhashree.

Hi E_Hinojosa ,
Its helped a lot.
But one doubt,what is process exit and how to search the same from a program or include.
The required code(which is there in note) is there in include 06 but which process exit I will use for the BACS remittance and how to fill the value of finaa-mail_body_text in process exit.
Please give me a clear idea.
Thanks,
Subhashree.

Help: need to insert body text in e-mail of remittance advice

Hi all,
I am sending remittance advices via the standard output program RFFOAVIS and want to include body text in the e-mail which is sent.
There is an OSS note for dunning (I know it's a different process) which mentions creating a text with text ID = 'FIKO' in transaction SO10 and then setting the field c_finaa-namep to the name of the custom text inside a function linked to the dunning business transaction. Can't find anything informative on OSS about body text for Remittances.
I have created a custom function linked to process 00002040 in transaction FIBF and changed the value of c_finaa to refer to custom text . I was able to change the recipient e-mail address inside this function (ie. the function is being called successfully) and the remittance itself is correctly output as an attachment but nothing comes out in the body text.
Can anyone out there help ? Any other field which one needs to change to include body text ?
Regards,
Gabriel

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 output should print to file rather than to a printer

Hi all,
We have a requirement in payment process Request,
when we process a payment batch, generally the Remittance Advice will be sent as per the payment system setup i.e, to the Banks server. But, our client has a dedicated team to review these generated Remittance Advises, once they review them, they will upload them to the Bank's Server.
But now we have to make the system to place the generated Remittance Advises to a common place from there the team will take and review them.
The following are some of the considerations of mine
1. use a xdodelivery.cfg file for FTP / SFTP or local file transfer
2. Create a local Transmission Protocol in Transmission Configuration in Payments setup and associate it with Payment Process Profile.
Is there any other solution please provide me.
Also if anyone had written xdodelivery.cfg file please provide me the code. I read the BI Publisher guide but i couldn't get how to proceed in writing the file.
Thanks in Advance
--Giri

Hi,
Remittance advice is specific xml publisher report because you already have data source. You can only make layout and delivery mail,fax,print 1072399.1. I think you should make own Remittance advice with bursting http://vanzweden.org/index.php/blogarticles/categories/xml-publisher/10-creating-text-files-with-bursting.
Regards,
Luko

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

Sap script payment remittance advice email doubt

i have to send mail to vendor of sap script layout . the FM which is configured in the business transaction events of accounts recievable and payable. can any one this code u can explain me
regards
sarath

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 .

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

Remittance advices

Hello Friends,
We have got one requirement. We need to send remittance advices through different output medium based on the vendor(Print, Fax, E-mail, EDI etc). How can we achieve this? Do we need to maintain any output condition records for these? If yes, where do we maintain and output type for this. How do we trigger output to send Remittance advices...
Could anybody please help me in this?
Thanks,
Amol

Hi,
Continue in the same menu. Define Sender details - Assign Program RFKORD00 Print Program Payment Notice to your company code. Please check the standard parameters in the sender details :
Text ID : ADRS;
Standard Texts : Header Text : ADRS_HEADER
                         Footer Text : ADRS_FOOTER
                         Signature Text : ADRS_SIGNATURE
                         Sender : ADRS_SENDER
You can use T.Code F.66 to print letters wherein u give SAP01 in the output control and enter the Printer parameters. You can have print preview. From the tool bar you have the options to save
the file in local file or send to mail receipient etc.
Sadashivan

System Email Address for Remittance Advice

Hello,
We currently send the Remittance Advice by email to Supplier.
The sender address on the email to Supplier is [email protected] and we would like to change this sender address to [email protected]
We can see that the default email address for all output forms can be changed in Fine Tuning Activity 'E-mail and Fax Settings' and it is currently [email protected] However we want to use a specific address for the Purchase Order email and another for the Remittance Advice email.
Can anyone tell us where we set the Remittance (or Purchase Order) specific email address ?
Thanks,
Kevin.

Hi Kevin,
As a standard behavior, the system sends an e-mail from buyer responsible address and not from default sender address. Default sender address will be used if there is no document-specific sender address. It means that if the buyer responsible does not maintain e-mail address, then system will send the Purchase Order from default sender e-mail address; else it will be consider the buyer responsible contact data.
Regards,
Fabio.

Change message in Remittance Advice

Hi,
We have setup our Workflow notification to send Remittance Advice mail whenever a payment is processed. We want to add a line to the message text. How should we do it?
Thanks in advance for any help.
-MS

Check Note: 225417.1 - Can the E-mail Remittance Advice be Modified
https://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=225417.1

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.

Remittance advice E-mail

Similar Messages

Maybe you are looking for