cancel
Showing results for 
Search instead for 
Did you mean: 

Payment advice form via email

Former Member
0 Kudos

Hi Gurus,

I encounter this situation that I will try to describe.

The form used for the Payment Advise note, is a custom one launched by program RFFOAVIS_FPAYM, through F110 (automatic payment program)

I already know the possibility that my abaper should check the coding for Function Module 'SAMPLE_PROCESS_00002040' in tcode SE37, within the mentioned program, in order to implement the sending of the form via email. This idea I successfully found within this forum. Thanks


We still need to check from where this automatic email trigger to vendor, that is, where do I have to save the email address so that the payment advice program can get that email address and send the payment advice note. However, I suspect it is the field in Vendor General Data, within address Tag:

Can anybody confirm this to me?.

However, my particular issue with the email address is that my client already used that General field for the email sending of the Purchasing order form. Now, my client is adding a new company code to its SAP systems that needs to send as well the Payment advise note (something not used before) to a different email address, but the email recipient is already occupied for a different purpose, despite you can add more than one email address.

So my core question is: is it possible to save elsewhere ANOTHER email address, different from the one saved at General Data (perhaps at company code level or purchasing organisation level) so that the program RFFOAVIS_FPAYM could get that email and send the Financial form to the email address for the payment advise note? I mean, using standard implementation in Program RFFOAVIS_FPAYM...

Please give advice on how to handle this situation of 2 different emails: one email is already in place, and it is exactly the field at General data (Address), used for the sending of the PO form.

Where can we save a different email address so that the Payment Advice program can easily trigger it and send the financial form? At company level, at Purchase organisation level??

Many thanks in advance!

Accepted Solutions (0)

Answers (4)

Answers (4)

Tiger_007
Active Participant
0 Kudos

Hi

you can achieve this via creating contact person. assigning this contact person at company code level.

since, email maintained at general data the same vendor email will be used to send different company code payment advice. but, you should not send both company code payment advice to both emails maintained here.

i suggest to follow below steps

1. use functional module to add screen field for vendor at company code level. you can use functional module pool SAPLZF_CUSTOMER_ADD_DATA to include.

2. you can add field for mail id or contact person.

3. if you are using contact person you need to ensure field settings at account group level you make optional contact person.

regards

srini

Former Member
0 Kudos

Hi Patxi,

Yes, you can put email address in other field as well and use it to send the payment advice.

In my project, we are maintaining the email address in the Correspondence tab: field- Clrk's Internet (LFB1-INTAD) to send out the payment advices.

Regards,

Mayank

Former Member
0 Kudos

We use the email field on the vendor master , it allows to store multiple emails with different tags.

You can call one MM (for purchasing) for example and another (AP) for payment advices.

Then in your custom BTE code which send the email read the email which comes with the appropriate tag like 'AP'.

Former Member
0 Kudos

Hi Patxi,

Never had such situation but can you check with your ABAP team by using the below:

Under the vendor master data where one email address is already maintained.

Now if you click on Other email Address you can add new mail address:

If you see every time a new ID is getting created so may be ABAPer can use this information to setup the code. Please do check that it should not have any negative impact on your previous setup of sending PO information or else you would have to do some code changes for that as well.

Regards,

Vishal Maheshwari