on 12-14-2011 7:42 AM
When payment is done through F110, an email should go to the vendor with the payment details
We have a requirement currently to send emails to vendors. I have searched in the forum got enough answers, still I have few more questions regarding the setup .
1. we are currently using classic payment medium and program RFFODEI1 to send the ACH payments to the bank.
Payment file using is DME
Anil
Edited by: Anil Kumar on Dec 14, 2011 8:48 AM
hello,
Please check the blog-
https://blogs.sap.com/2018/05/21/workflow-based-approval-of-payment-proposal/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
These are steps you need to carry out to send email.
Emailing SAP Remittance advice:
1.
For the following process to work SAP Connect needs to be configured for outgoing mail. This is carried out by the Basis team. The t-code is SCOT.
2.
Vendor Master Data
Define ‘Std communication method’ as SMTP (Internet mail) and maintain an email address in the vendor master data.
3.
T-Code BERP – Code to find the relevant BTE. Use the Selection Attribute to browse for your business area. In my case, it is AP-Payment Transactions hence FI-AP-AP-PT.
00002040 is the relevant process. This is a Function called SAMPLE_PROCESS_00002040. In this case, the FM only checks for an email address in the Vendor Master. If more logic is required a Z-version would need to be created.
4.
Use t-code FIBF to create the enhancement.
a)
Create a product.
A product groups together customer enhancements to BTE’s developed in the customer's namespace. All customer enhancements assigned to a certain customer product can be released with the Activate Customer Product indicator. The OPEN_FI function module for a certain customer enhancement cannot find the corresponding customer function modules, until this has been done.
Create the product name (for example ZMAIL) and make it active.
FIBF->Settings->Products->…of a Customer
b)
Assign the BTE to the FM:
Settings->Process Modules->…of a customer
Assign the 00002040 process to the FM and Product.
5.
At the end of this process when the payment advice program is run, the event will be called and it will automatically send an email to the vendor.
6.
Assign an email address to the sap user who will be the outgoing accounting clerk. Define the Accounting Clerk for the outgoing email address:
SPRO->FI->AR/AP->Vendor Accounts->Master Data->Preparations for Creating Vendor Master Data->Define Accounting Clerks
Thanks.
Irene
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Irene,
Many thanks for configuration steps
I followed same steps and you can see the screen prints I pasted in same thread.
After executing F110 I noticed an entry got created in SOST but it is pulling data of some inspection lot instead of payment advice, not sure from where is it getting that and why.
I am stuck and not sure what to debug and to findout this.
Many thanks for your inputs and it would be great if you can tell which program to check to know how inspection lot thing is pulled in SOST instead of payment advice.
Regards,
Naveen
Thanks Naveen. Please award points. This link might help you:
http://scn.sap.com/thread/1628016
Thanks.
Irene
Hi Anil,
Did you find solution for this? I am facing similar situation here.
We implemented BTE2040 and maintained email address in Vendor master.
Assigned variant against RFFOAVIS_FPAYM still not able to generate email in SOST.
Please let me know if you have any solution for this.
Regards,
Krishna
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Naveen,
Please check below details.
1. Transaction - FIB F – configure Function module BTE 000002040.
2. The standard Function Module (SAMPLE_PROCESS_00002040) will pick the email id from Vendor address tab under communications.
After assigning these 2 settings also not generating emails to SOST. Then Please check 'other communications' button and make sure that it is having 'INT' (Email).
Still if you have the problem, Please ask abaper to debug the Job created for the print shedule and some times it may be the BASIS issue.
Note that emails will generate only once you perform the 'print schedule'.
Regards,
prasad
Hi Naveen,
Using accounting clerk field for payment advices is normal business requirement. Since vendor communication email field will be used for the different purposes (Purchasing may use same field).
You can achieve this requirement by copying standard Function Module (SAMPLE_PROCESS_00002040) to Z function module and change the field from correspondence to Account clerk internet field (LFB1-INTAD) as a email id.
You can take the abaper help to develop new FM and assign the same FIBF as explained above in thread.
Regards,
Prasad
Hi Prasad,
Many thanks. we followed the same steps but instead of payment medium advice I can see a record for some other thing for inspection lot.
FIBF
1. Products --> Of a Customer
2. Settings --> process module --> Of a Customer
And I have done all other configuration as stated in OSS note and yourself like taking email address from LFB1-INTAD.
Now I can see a record in SOST but it is not payment advice it is pulling something else "Inspection lot"
Note sure why this is triggering instead of payment medium advice. I wanted to debug but not sure which program triggers this to debug.
The only difference I noticed between your steps and mine is I didn't maintain entry in below path.
Settings --> process module-> of an sap application
This table maintainence is a cross client and as per BTE 2040 OSS note they didn't say to maintain an entry here.
Can you please tell me what would be impact if we don't maintain an entry here.
And it would be a great help if you can tell me which program triggers BTE 2040 functional module so that I debug and see why is it pulling "inspection lot" instead of payment advice.
Further to continue, when I ran F110 it created an error see the log below.
Many thanks for your help and inputs.
Regards,
Naveen
HI Naveen,
Please check the job log(SM37) details which has created for your print schedule. In job log you will find all the details about the program generated advices. Please make sure that nothing generated to spool. If some thing is generating to spool means the bte not assigned correctly.
Please assign BTE and Function module as i suggested and test once.
Please let me know if it is not clear.
Regards,
Prasad
Hi Expert,
Please contact your Workflow Consultant, which will done by them. You need share your functional and technical details and he will configure the events accordingly.
Regards,
GK
SAP
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Yes you can send pymt advice via email. I see you are using RFFOEDI1. This program generates the Intermediate Documents (IDoc) for payment orders made via EDI. In addition to the payment media, you can output the related advice notes, EDI accompanying sheets and payment summaries in a single program run.
Please see the program documentation of this program RFFOEDI1 under the below section for more information:
"Payment Advice Notes
In addition to being able to print payment advice notes, you can also send these via EDI, fax or email.
...
2. To send a business partner a payment advice note by fax or email, you must use the process interface 00002040 (Business Transaction Events) to 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.
Process interface 00002050 can also be used to change or configure the print parameters and the parameters for optical archiving for payment advice notes."
Hope this helps.
Kind Regards
Soumya
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
98 | |
12 | |
10 | |
6 | |
6 | |
4 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.