Beruflich Dokumente
Kultur Dokumente
Date: 07/02/16
E-Remittance Solution
Executive Summary
An automated Business Processing solution in a cost efficient way is the new Mantra of
the Businesses today. This Paper attempts to describe one such cost effective process
solution developed for sending Automatic Payment Advices to Vendors / Customers via
email or Facsimile Transmission from R/3 (SAP).
Introduction
Currently, many organizations using R/3 generate a Print Out of the Payment Advice after
executing a Payment Run. This Payment Advice is then sent by mail-post to the vendor.
Alternatively this service is availed from the banker for a charge.
The man hours and the cost spent on this clerical work is huge in an organization
Requirement
There is a requirement to send email notification originating from R/3 to vendors /
customers automatically after the Payment Run is executed.
Business Case - There is a strong business case to have this solution in place since it
would save a huge number of man hours spent in mailing the Payment Advices or
manually faxing it. Consequently, there is a substantial savings in the cost incurred.
Conventional Approach
Customized Developments have been done in the past to achieve this. However it was
restricted to only a specific payment program. So every time a new payment program is
used, a separate development was required.
New Solution
The new solution is a generic one with minimal one time development. In the new
solution, a Business Transaction Event (BTE 2040) has been activated. This BTE is
triggered every time a Payment Medium is generated after an Automatic Payment Run
(F110) is done. This BTE is attached to a Function Module (/TPISP/YF_BTE_00002040)
(copy of SAMPLE_PROCESS_00002040). The technical details of this could be seen in
the function module SAMPLE_PROCESS_00002040
Transaction: FIBF
Date: 07/02/16
E-Remittance Solution
Also there is a custom table YFEMAIL_PAYADV maintained in sm30. This table
contains Flags for Emails and Fax for each combination of Company Code and Payment
Method.
Its looks as follows:
Field Notes ID
There is a case where email needs to be sent for Purchase Order to Vendor. In that case
the email is sent to the recipient address where the radio button is checked. Normally a
recipient of P.O does not handle payments in an organisation. Hence to distinguish the
recipient of Payment Advice, the Notes ID is introduced. See the screenshot below
Date: 07/02/16
E-Remittance Solution
The notes ID PAYADV is also maintained in the custom table next to the email flag.
When the Print program is executed, the Payment log in F110 specifies that the mail has
been sent
Date: 07/02/16
E-Remittance Solution
It is advisable to check the SAP Connect gateway to ensure if email has been
executed instead of the spool request. Use transaction SOSB or SOSG
Advantages
1. This solution can be used in future by all company codes who would like to email
or facsimile the Payment Advice after the Payment Run is executed. This solution
would save huge amount of man hours and cost involved in manually despatching
the Payment Advices to vendors / customers
2. The BTE avoids the development of a custom program for the email functionality
and saves the repetitive development cost
3. There are three alternatives in the solution viz. Email or Facsimile Transmission or
a Print Out. The output is sure.
4. This solution is an easy one time set up with minimum maintenance
5. The Business Partners (Vendors and Customers) get the Payment Advice details
immediately thus helping them in their Cash flow Position
Date: 07/02/16
E-Remittance Solution
Summary
A generic solution to email or Facsimile the Payment Advices to Vendors / Customers
could be used in future by many sites without having to develop a custom solution each
time a different Payment program is used.
--------------------------------------------End of Document------------------------------------------
Date: 07/02/16