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 .

Similar Messages

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 .

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

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.

Smartform form for Payment remittance advice to Vendor

Hi Friends,
My requirement is i have a sapscript "F110_IN_AVIS" (Driver program:RFF0EDI1 This is a standard sap driver program)and it should be converted to Smartform with all the windows as it was present in sapscript. I have migrated the sapscript to smartform (as you all know that only the layout will be copied and not the logic). Now how to identify the table names and the corresponding field names related to each of these windows. Kindly suggest how to proceed with the driver program. Also Kindly send any document or any sample program for Payment remittance advice to vendor. Full pints will be rewarded to valuable answers. Thanks in advance.

Cheers Gusy
Now I Have got this requirement too and iam working on this i will come with the solution soon mean time if any one of u have any inputs cheers to hear from yu guys..
Raj

Payment remittance advice

Hi all
i would like to know the following.
1. T-code to create payment remittance advice.
2.T-code to change paymen remittnce advice.
3. What is the procedure to see print preview of payment remittance advice.
thanks & regards
GP

Hi,
1. T-code to create payment remittance advice.
a) You can configure the remitance/payment advice in T.Code:FBZP >> Paying co.code>>select the co.code>> Assign form F110_IN_AVIS(this form will change country to country) in the field Form for the Payment advice
2.T-code to change paymen remittnce advice.
a) If you would like to change the payment advice form, you can take the help from abaper and they will change the form according to client requirenet.
3. What is the procedure to see print preview of payment remittance advice.
A) You should create a variant for payment advice and you can use the same while executing the t.code:F110.
Once payment run has been completed system will generate a spool for payment advice. You can view that payment advice through t.code:SP01.
All the best
prasad

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

How to see the output of a FORM of REMITTANCE ADVICE ( PAYMENT ADVICE )??

Hi Experts,
I got a SAP Script of REMITTANCE ADVICE (also known as PAYMENT ADVICE).
And I know the VENDOR #.
I need to see the output of this SAP Script on the screen, so, let me know that, How to test it/see its output. (I know, seeing the Customer statemet from the tx of F.27), I mean, wht r the transactions etc. stuff.
thanq

You should create a variant for payment advice and you can use the same while executing the t.code:F110.
Once payment run has been completed system will generate a spool for payment advice. You can view that payment advice through t.code:SP01.

Xdodelivery.cfg for email delivery - R12 Separate Payment Remittance Advice

Hi all,
I'm trying to configure the Email Document Delivery for Separate Remittance Advice in R12 but have been unsuccessful so far. I filled the xdodelivery.cfg file with the relevant information and placed it under $XDO_TOP/resource directory and set up the profile option IBY_XDO_DELIVERY_CFG_FILE to point to this directory. I'm getting the below error message in the log file of the standard program "Send Separate Remittance Advices"
Finished extract and formatting.
Got user profile IBY_XDO_DELIVERY_CFG_FILE: /net/ebs/DEV2/ddcerp012/apps/apps_st/appl/xdo/12.0.0/resource
Loaded email subject from DB: Message { Code = IBY_FD_SRA_EMAIL_SUBJ, Cause = Separate Remittance Advice: payment reference number - 147}
Loaded email send-from from DB: Message { Code = IBY_FD_SRA_EMAIL_FROM, Cause = [email protected]}
Loaded email attachment file prefix from DB: Message { Code = IBY_FD_EMAIL_ATT_PRE, Cause = Payment}
Preparing for email delivery
SMTP server host: null
Email subject: Separate Remittance Advice: payment reference number - 147
Recipient: [email protected]
Content file name: Payment147.html
Email send from: [email protected]
before calling XDO req.setDocument()
before calling XDO req.submit()
oracle.apps.xdo.delivery.MissingRequiredPropertyException: Required property missing. Property name :[HOST]
     at oracle.apps.xdo.delivery.AbstractDeliveryRequest.validateProperties(AbstractDeliveryRequest.java:1367)
     at oracle.apps.xdo.delivery.AbstractDeliveryRequest.submit(AbstractDeliveryRequest.java:1174)
Below is the content of the xdodelivery.cfg that I'm using
<?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>ddcsend001d-vip.dev.abc.com</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">"application/pdf"</property>
</properties>
</config>
Could anyone please suggest if I'm doing something wrong? Or has anyone been able to accomplish this functionality successfully in R12?
Thanks,
Vinay

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

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 to get the output of the Send Separate Remittance Advices in XML in R12

Hi All,
I have a requirement where we want the output of the standard report 'Send Separate Remittance Advices' to come in XML, currently its coming in PDF format.
Can you please help?
Thanks,
Dilip
Edited by: 990784 on Mar 12, 2013 2:57 PM

Refer these links
http://www.sap-img.com/bc037.htm
http://www.members.tripod.com/abap4/Save_Report_Output_to_a_PDF_File.html
CONVERT_ABAPSPOOLJOB_2_PDF FM convert abap spool output to PDF

Diff email subject for diff orgs for Remittance advice email in R12

Hi All,
We are upgrading from 11i to R12. AP Remittance advice workflow in 11i was customized to send emails with different subject for suppliers of different operating unit.
We need to keep this customization in R12. I could find one profile option for setting the subject of the remittance advice which is IBY_FD_SRA_EMAIL_SUBJ. However, it will send the email with same subject to all suppliers. Please help me in finding a way to achieve this.
Also the workflow in 11i is customized to not to send the notification for zero amount invoices. I could not think of any way to achieve this.
Any help in this regard also would be highly appreciated.
Many Thanks,
Priyanka

Hi,
You could copy those customizations from 11i to R12.
Please see
Re: Determining Workflow Customization
Re: Upgrading Workflow from 11i to R12.1.3
Thanks

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

EDI - 820 Payment Remittance Advice

What is the flow process to achieve EDI - 820 functionality in Sap? Need documentation how to upload 820's directly into SAP.
It would be a great help for me if someone could share their experience.
Appreciate your time.
Thanks & Regards,
Victor

No response.

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

PO Output email ID vs Payment Remittance Advice email ID

Similar Messages

Maybe you are looking for