RE RFFOEDI1

____________________________________________________
Short Text
International Payment Medium - Payment Orders by EDI

Description
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.
For a more detailed description of the entire functionality, see EDI Outgoing Payment Orders.

Requirements
Payment Program Configuration
The parameters that control the way in which the payment medium programs function are configured in
Customizing. For more information on configuring the payment program, refer to the Implementation Guide.
Configure payment program
1. Here you need to make specifications for the paying company code. To do this, select the relevant
paying company code by choosing Paying Company Codes ->.
If payment advices are to be printed, define a SAPscript payment advice form for use with all company
code payment methods. You will find the form F110_IN_AVIS as an example in the standard system.
You need to create and enter text modules in which the texts for the header, footer, signature and
sender are stored. These modules can be included in the forms when they are used. To do this,
choose Sender Details, from where you can also branch into text maintenance by selecting the
modules. The names of the text can be defined by the user, for example F_0001_HEADER for the
letter header in company code 0001.
Proceed
In addition to the payment advice form, you also define here the EDI accompanying sheet
(F110_EDI_01 in the standard system).
2. Use Payment methods -> In country to set up a payment medium program. This payment medium
program should only be started if an IDoc communication is temporarily not possible, or if errors
occurred during the communication. For further information on what to do when there are errors, see
the RFFOEDI2 program documentation. For documentation on the conventional payment medium
programs, see RFFOUS_T or RFFOD__U, for example.
3. Here you need to make company code specifications for the payment method. To do this, choose
Payment Methods In Company Code, then select the paying company code and the payment method.
In this menu maintain the following data by choosing Form data or Payment Advice Control:
o

The issuer data.

Sorting the correspondence.

Sorting the line items.

Proceed
Note: The issuer details are used on the accompanying sheet and must be filled out as follows:
Line 1 Issuer name 1
Line 2 Issuer name 2
Line 3 Street/P.O.box
Line 4 City
4. The user must define instruction keys to control which instructions are given to the banks that are
required to carry out the payment order.
Proceed.
Note: Note that you can define the four instructions when you post the invoice document.
5. You need to make further specifications for creating the payment medium in Customizing of the
house banks. Select the relevant paying company code by choosing House Banks. In the maintenance
of the house banks select your house bank and then maintain the required data via the button Data
Medium Exchange. For more details refer to the online documentation for the relevant fields.
Proceed
Define a partner number for each house bank that offers EDI. Choose Goto to maintain the partner
profiles and the payment methods allowed for EDI for each house bank.
6. You must define state central bank indicators which are used in the report to the central bank.
Proceed
These central bank indicators are specified when posting the invoice document. The "SCB/supplying
country" field group of the payments abroad data must therefore be set to required entry or optional
entry fields via the reconciliation account field status.
Proceed

Setting up and changing the SAPscript forms (layout sets)

The following describes the layout of the SAPscript forms in brief. If the forms available in the standard system
are sufficient for your requirements, you can skip this part of the documentation.
You can find further information on forms and the SAPscript editor in the guides on styles and form
maintenance and word-processing in the SAPscript editor: Select the menu path Help -> SAP Library.
1. When setting up SAPscript forms (layout sets), symbols are included in the text; these are then
replaced by actual values when the payment medium programs are run. The fields which can be used
for this are defined in the Repository and contained in the following structures:
REGUH Settlement data from the payment program
REGUP Edited invoice items from the payment program
REGUD Formatted data for printing the forms
SPELL Amounts and digits in words.
FSABE Data on accounting clerk.
2. If you want the document long text for an accounting invoice document to be printed on the payment
advice form, you must make the following enhancement in element "Long text for invoice document"
(specially designed for this purpose):

/: DEFINE &TXT& := '&REGUP-BUKRS(*)&&REGUP-BELNR(*RF0)&&REGUP-GJAHR&'

/: INCLUDE &TXT& OBJECT BELEG ID xyz
The text ID that you must enter for this text (xyz) is defined in the configuration menu and can be read
from there. In the standard system, text ID 0003 is predefined for the payment advice information.
Proceed
Note: the check totals in the EDI accompanying sheet can be issued via structure E1IDRS1.
3. Layout of the payment advice form (F110_IN_AVIS in the standard system)

Pages

FIRST First page per payment advice

NEXT Subsequent pages if page overflow
EDI List of payment advice notes sent per EDI
LAST Form summary section per house bank
Windows and elements
HEADER Letter header
ADDRESS Sender and address of the payee
PAGE Page counter
INFO Date, payment document number, etc.
INFO
605 Account number of the sender at the recipient
INFO2 Information on the next pages
REPEAT Information for the test print or proposal run
MAIN Form of address before the letter
MAIN
610-x Short text for payment method x
MAIN
610 Letter when 610-x is missing
MAIN
612 Alternative payee
MAIN
613 Notification takes place in order
MAIN
614 Signature
MAIN
615 Heading of the invoice item information
MAIN
620 Carryforward at page top after page overflow
MAIN
625 Invoice item information
MAIN
625-TX Long text for invoice
MAIN
625-HR Information line for Payroll Accounting
MAIN
630 Sum total
MAIN
631 User-defined text after invoice items
MAIN
675 Header for EDI advices
MAIN
676 List of EDI advices
TOTAL
630 Sum total of fixed items
CARRYFWD 635 Carryforward at page bottom for page overflow
FOOTER Letter footer
SUMMARY Form summary section
4. EDI accompanying sheet layout (F110_EDI_01 in the standard system).
Pages
FIRST EDI accompanying sheet
LAST form summary section per house bank
Windows and elements
MAIN
530 upper section of accompanying sheet
MAIN
531 total per currency
MAIN
532 lower section of sheet
SUMMARY
520 form summary section
Check that the SAPscript forms (layout sets) which you use have the layout described and, in addition, check
that the forms are active (both in the original language as well as in all languages into which the forms were
translated).
Proceed

Set up and change to PDF-based payment advice forms

In the paying company code settings, you can set that a PDF-based form for the payment advice note is output
instead of a SAPscript form. Form F110_AVIS_INT is an example of this in the standard system.
For each company code create SMARTFORM text modules for header, footer, signature and sender, and enter
these text modules in the settings for the paying company code.

If you want to include your company logo or a picture with a signature in the payment advice note, enter the
URL with the directory path and the file name.
Proceed
Create further SMARTFORM function modules for the payment-dependent letter text in the payment advice
note. Enter these texts in the settings 'Letter for payment correspondence (PDF)'.
Proceed
Assign the function modules to the payment methods in the settings for the payment methods in the company
code.
You can copy the example form and adapt it to meet your requirements. You can use all of the data provided in
the form interface in your form.
Proceed

Periodic processing
Before the payment medium programs can be started, the payment program run must have been successfully
completed. Check the status of the payment run, or schedule the payment medium programs by specifying one
or more variants.
Proceed
Note: If you want to use th 'Payment document update' option, the payment documents must be updated
between the time of the payment program run and the time of the payment medium program run.

Output
Forms and lists
Printout files are created per company code and house bank. These can either be printed via the print manager
or immediately. Depending on the parameter you select, you can print out one or more of the following:
o

Accompanying sheet for the payment medium

Payment advice notes (if the information cannot be sent via EDI)

Payment summary

Error log

The number of output files is specified in the flow trace; this makes finding and allocating them within the print
manager easier.
Proceed
Note: If the program was started online, then you reach the print manager from the list by selecting one of the
output files displayed.

Payment Advice Notes

In addition to being able to print payment advice notes, you can also send these via EDI, fax or email.

1. To send a business partner a payment advice note via EDI, you need to select the indicator
Payment advice note per EDI and maintain the partner agreement on screen "Payment Transactions
Accounting" in the master record.
Proceed
Using an external converter, the IDoc created by the program can be converted into the EDI format
you require (REMADV for example) and then sent.
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.

IDoc
Payment instructions that have previously been sent to the bank on disk or by data transmission are now
transmitted by EDI via the IDoc interface.
The payment data are stored in the system as SAP intermediate documents. An external EDI sub-system
generates a standardized message based on these IDocs and sends it to the bank. After receiving confirmation
from the payer (e.g. by electronic signature), the bank processes the payment orders.
Relevant information on each IDoc (file format, creation date, payment amount in local currency, payment
documents used etc.) is stored in the system and, identically to conventional data media, this can be called up
using the DME management functions.
Additional DME management functions include:

Displaying status and contents for the intermediate documents generated

Generating a payment summary for the data medium

Generating an accompanying sheet for the EDI message.

Proceed

Error messages and error log

Termination of processing
You can find out the reason why processing was terminated (for example, production run not yet carried out,
form does not exist or is not active) by looking at the error message or the related long text.

Internal SAPscript error

Check the layout of the forms. It must fulfil the above-mentioned conditions. You cannot, for example, create a
bank transfer with the check print program, since bank transfers and checks have a completely different layout
structure.

Error log

If errors which do not terminate the payment medium program occur when creating the output, the system lists
them in the error log. If such a log is created, you must look it over because only you can decide whether the
payment medium or payment advices are useless due to the errors the system finds, and decide whether they
must be recreated after the errors have been rectified.
During background processing, the system outputs the error log twice, in the flow trace for the job and in a
printout file. The flow trace contains information on how to rectify the errors (from the error message long texts).
You can display the long text online by choosing the error log from the list of generated output files and then the
error message in question.
Payment orders that cannot be issued by EDI due to any errors that have occurred are listed in the error log
and marked as defective. You then have two options:
1. Send the payment orders in question to the bank using a conventional payment medium, which is
created by the program specified for this purpose in the country-specific configuration screen for this
payment method.
2. Solve the problem described in the long text in the log and then change the status of the payment
from 'Transmission error' to 'Not yet transmitted', which enables you to restart the EDI transmission
process.
Proceed