Ansicht
Dokumentation

RFFOAT_A - Payment Medium Austria - Foreign Payment Transactions V3 Format

RFUMSV00 - Advance Return for Tax on Sales/Purchases   General Data in Customer Master  
This documentation is copyright by SAP AG.

Description

Please use the Payment Medium Workbench to create data media with the format PAYMUL V3. Although report RFFOAT_A is still being delivered, the long term intention is to support only the Payment Medium Workbench (program SAPFPAYM), which is to supersede all of the RFFO* reports.

The program creates foreign bank transfers in Austrian V3 format. This format, which is the basis for the EDIFACT format PAYMUL AZV, makes it possible to transfer both in Euros and foreign currency, and also payment by means of check.

In addition to the payment media, you can also print the related payment advice notes, payment summaries, and accompanying sheets in one program run. Other forms are not supported.

Requirements

Payment Program Configuration

The parameters that control the payment medium program process program are set via the payment program Customizing menu. You can find additional information on configuring the payment program in the Implementation Guide (IMG).
Set Up Payment Program

1. You need to make entries for the paying company code. Select the relevant paying company code you want using the button 'Paying Company Codes'.
Define a SAPscript payment advice note form that is used by all payment methods for the company code if payment advice notes are to be printed. You can use form F110_AT_AVIS in the standard system as an example.
Text modules need to be created and entered in which the texts for letter header, footer, signature and sender are stored for each company code. The modules can be included in the forms used. To do this choose the button 'Sender Details', from where by selecting the modules you can also branch to text maintenance. The names of the texts can be freely defined by the user, for example F_0001_HEADER could be used for the letter header in company code 0001.
Proceed

2. You need to assign the name of the payment medium program RFFOAT_A to the payment method,,to avoid incorrect payment media being issued with another program in error.
In addition, you can enter a short name (or print dataset, for example LIST3S) making it easier to find the forms generated in the print manager.
A text key is also needed in the code line or the form or data medium that you likewise have to define. You can obtain the correct text key from the description of the payment medium (for example, ).
To do this, first choose the country of your paying company code under 'Payment Methods in Country', and then the desired payment method, and maintain the data for printing the form.
Proceed

3. The foreign currency statistics of the OeNB require the entry of a service indicator (foreign payment) that can accept the following values:

1 = Import

2 = Own Carryforward

3 = Other

This indicator is maintained in the document.

If the service indicator has the value 3 then a detailed description of the payment reason is required. The text of this description is determined using the state central bank indicator, which you also need to enter in the document.

In V3 format, there is a maximum of four lines available for the note to payee in the case of a foreign bank transfer. If you require more than 4 lines, a payment advice note can be created.

You have to fill in the entries for the issuer as follows:
Line 1,,Name 1 of the issuer
Line 2,,Name 2 of the issuer
Line 3,,Street
Line 4,,City.
Issuer line 1 and 2 are merged in the data carrier for the field 'payer/recipient'.

Note: You need to maintain the bank number of the data medium recipient if this differs from that of the house bank.

The data processing register number, the customer/vendor EB number for the cash payment order, and also the two digit abbreviation for the accounting clerk / telephone number are maintained with the additional entries for the company code.
Proceed

Layout of data medium accompanying sheet (in the standard system F110_AT_DTA_V3)

Pages
FIRST Accompanying sheet
NEXT Accompanying sheet

Windows and elements
KOPF 1BZ_HEADER Header of the accompanying sheet
MAIN 2BZ_NACHRICHT Message data
MAIN 3BZ_LIN LIN data (for collective payment order)
MAIN 4BZ_NACHRICHT_T Close of message

Three internal tables have been defined for filling the accompanying sheet:

bz_dt for the header data. This table contains the following fields amongst others:
EMPF Recipient bank of the data medium
ABS Sender of the data medium
ANSP Accounting clerk
TEL Tel. of the accounting clerk
tel_exten1 Extension of the accounting clerk

BZ_NACH for the messages. One of the fields in this table is:
TYP Type of message ('PAYMUL')

BZ_LIN for each LIN section or collective order. This table contains the following fields amongst others:
ART Type of message ('UEBW')
BLZ Bank number of the processing bank
KTONR Our account number at the processing bank
SUM Total of the amounts of the collective order
UMSATZ Number of individual orders

Output

General information on the structure of V3

Payments that:
-are settled via the same account and in the same currency
-have the same date of execution
-have the same payment method
are grouped together in a collective order.

A file generated by this report can only contain the message 'PAYMUL'. Such a message consists of segments that are assigned to levels:

Level A:

Contains information (segments), describing the following:
-Who sends to whom
-Who to contact if problems arise with the message at the bank

Level B:

Contains information for the settlement of collective orders:
-Settlement account of the collective order
-Date of execution of the collective order
-Total of all amounts of the payments (bank transfers or direct debits) relating to a collective order.

The B level can have several collective orders. A collective order begins with the segment 'LIN' and ends with the next segment 'LIN'. The point of level B is to write all of the entries that remain the same for the single orders (the C level) once in the B level.

Level C:

Describes the single orders:
-To whom (from whom)
-How many
-For what reason

A single order begins with the segment 'SEQ' and ends with the next segment 'SEQ'.

Customer to customer information structures

V3 offers, in addition to the text as note to payee, the structured note to payee, the data of which can then be used direct by the recipient's data processing system.

If you select the field 'Customer-customer info struct.' then the invoice number, the invoice amount, the invoice date and the amount of discount are output in the DME file.

rdisp/max_wprun_time - Maximum work process run time   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Length: 7684 Date: 20240601 Time: 092958     sap01-206 ( 123 ms )