FI Accounts Payable and Receivable

Prévia do material em texto

4/11/2024
1This is custom documentation. For more information, please visit the SAP Help Portal
Financial Accounting
Generated on: 2024-04-11 22:17:50 GMT+0000
Support Content | 1.0
PUBLIC
Original content: https://help.sap.com/docs/SUPPORT_CONTENT/�accounting?locale=en-
US&state=PRODUCTION&version=1.0
Warning
This document has been generated from the SAP Help Portal and is an incomplete version of the official SAP product
documentation. The information included in custom documentation may not re�ect the arrangement of topics in the SAP Help
Portal, and may be missing important aspects and/or correlations to other topics. For this reason, it is not for productive use.
For more information, please visit the https://help.sap.com/docs/disclaimer.
https://help.sap.com/docs/disclaimer
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting?locale=en-US&state=PRODUCTION&version=1.0
https://help.sap.com/docs/disclaimer
4/11/2024
2This is custom documentation. For more information, please visit the SAP Help Portal
Accounts Payable and Accounts Receivable
WELCOME TO THE ACCOUNTS PAYABLE AND ACCOUNTS RECEIVABLE EXPERT
CONTENT PAGE
What is Accounts Payable and Accounts Receivable?
The Accounts Payable application component records and manages accounting data for all vendors. It is also an integral part of
the purchasing system: Deliveries and invoices are managed according to vendors. The system automatically triggers postings
in response to the operative transactions. In the same way, the system supplies the Cash Management application component
with �gures from invoices in order to optimize liquidity planning.
The Accounts Receivable application component records and manages accounting data of all customers. It is also an integral
part of sales management. All postings in Accounts Receivable are also recorded directly in the General Ledger. Different G/L
accounts are updated depending on the transaction involved (for example, receivables, down payments, and bills of exchange).
The system contains a range of tools that you can use to monitor open items, such as account analyses, alarm reports, due date
lists, and a �exible dunning program.
Accounts Payable and Accounts Receivable
General Documentation - Accounts Payable and Accounts Receivable
Accounts Payable (Vendor)
Accounts Receivable (Customer)
Accounts Business Transactions: Bill of Exchange(BoE)
Payment Program
DME Creation-Payment Medium
Line item display issues
Supportability Tools - Accounts Payable and Accounts Receivable
Access SAP For Me Visit the SAP Community View Product Documentation
 
 
https://help.sap.com/docs/disclaimer
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880530.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361881769.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878722.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880820.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361881743.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880870.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880329.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880336.html
https://me.sap.com/
https://community.sap.com/
https://help.sap.com/docs/
4/11/2024
3This is custom documentation. For more information, please visit the SAP Help Portal
 
 
General Documentation - Accounts Payable and Accounts Receivable
This section covers topics related to Account Payable and Account Receivable
General Documentation - Accounts Payable and Accounts Receivable
https://help.sap.com/docs/disclaimer
4/11/2024
4This is custom documentation. For more information, please visit the SAP Help Portal
Accounts Payable (Vendor)
Accounts Payable - Master Records
Sensitive Fields for Dual Control de�nition
Accounts Payable - Periodic Processing
Free Selections on "Create payment runs for payment request" ( RFPRQZLP )
How to Use Program RFF110S
Periodic Vendor Dunning
Clearing Vendors Against Customers
Accounts Receivable (Customer)
Accounts Receivable - Master Records
Accounts Receivable - Credit Management
Classic Credit Management
Credit control area in FBL5N
F_KNB1_ANA authorization check
Main Credit Check Methods in FI (OVA8) in classic credit management (ECC system)
Accounts Receivable - Periodic Processing
Periodic Customer Dunning
Accounts Business Transactions: Bill of Exchange(BoE)
Bill of Exchange(BoE) for customers
Fields Bank Key and Bank Account are missing during Bill of Exchange posting
Bill of Exchange(BoE) for vendors
Payment Program
Automatic Payment Run
Delete Output in F110
Manual payment for vendor or customer account
Payment Program - Error Message FZ 326
Selection of Partner Bank Type (BVTYP) From Vendor Master Data in F110
Error FZ506 'No valid payment method found' in F110 payment proposal
General procedures and Tables in Automatic paymnt run
Authorization Check in F110
Reorganization in F110
Difference Between FBZP and F11CU
Display long account number RFZALI20
How to avoid error FZ331 during payment for tax jurisdiction country
Message FZ361 occurs in the T-CD F110
Update termination in Payment programs (F110 and F111)
DME Creation-Payment Medium
VIA CLASSIC PROGRAM
Bank Charge in RFFOJP_T
Classic Print Program: General Information
https://help.sap.com/docs/disclaimer
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361881769.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880683.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361879134.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880685.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880604.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880751.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880943.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361881805.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878722.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880703.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880676.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880481.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880440.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361881244.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878884.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880680.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880941.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880820.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880932.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880818.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880657.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361881743.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878218.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361882152.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880816.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880901.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880167.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878518.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878657.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878428.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878327.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361881237.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880926.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880304.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361881967.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878528.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880870.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880829.htmlhttps://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878810.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880771.html
4/11/2024
5This is custom documentation. For more information, please visit the SAP Help Portal
Classic Program: Output Medium FZ205 Error
Classic Program for outgoing IDOC creation RFF0EDI1-2
Classic Program - RFFOUS_C
Classic Programs: Codepage
Dump with GETWA_NOT_ASSIGNED_RANGE in RFFO* report
Payment Advice, Accompanying sheet creation via classic print program
Payment from HR
Reprinting Checks for Payment Documents Through Classic Payment Medium Program (RFFOUS_C)
VIA PMW
ACH Formats
Checks
Country speci�c formats
Format IDOC
Modifying Standard PMW Formats
Payment Advice Creation
Payment formats supported in S/4 HANA and in ERP
PMW: General Information and DMEE (Data Medium Exchange Engine) or DMEEX (Data Medium Exchange
Engine Extended)
PMW formats: Codepage
PMW formats: Customizing
SEPA and CGI Format Tree
Line item display issues
Dynamic Selection Fields for Line Items transactions FBL1N, FBL3N and FBL5N
Low performance of FBL1N, FBL3N and FBL5N
Special Fields in FBL*N transactions
How to add ʻNet due date’ �eld in T-code: FBL1N and FBL5N
FAGLL03 display issues
Dynamic Selection Fields for FAGLL03
Low performance in transaction FAGLL03 or TIME_OUT short dump
Special Fields in FAGLL03 transaction
Offsetting Account Report
Access SAP For Me Visit the SAP Community View Product Documentation
Accounts Payable (Vendor)
This section covers the Account Payable (AP) in Financials.
Accounts Payable (Vendor)
Accounts Payable - Master Records
Sensitive Fields for Dual Control de�nition
Accounts Payable - Periodic Processing
https://help.sap.com/docs/disclaimer
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880772.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880748.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880752.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880773.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878263.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880770.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880750.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878268.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880828.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880842.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880776.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880777.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880775.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878619.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880764.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880779.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880730.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880759.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880761.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880760.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880329.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880327.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880330.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880331.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878608.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880322.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880324.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880854.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880707.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361881806.html
https://me.sap.com/
https://community.sap.com/
https://help.sap.com/docs/
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880683.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361879134.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880685.html
4/11/2024
6This is custom documentation. For more information, please visit the SAP Help Portal
Free Selections on "Create payment runs for payment request" ( RFPRQZLP )
How to Use Program RFF110S
Periodic Vendor Dunning
Clearing Vendors Against Customers
Accounts Payable - Master Records
In transactions FK01, FK02 and FK03 �nancials vendor master data can be created, modi�ed and displayed respectively.
For this purpose, some preparation activities should be carried out in the customizing (SPRO transaction):
In the settings for preparing to create vendor master records following objects are required:
https://help.sap.com/docs/disclaimer
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880604.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880751.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880943.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361881805.html
4/11/2024
7This is custom documentation. For more information, please visit the SAP Help Portal
Number ranges
The number range determines the number interval from which the account number for the master record is to be
selected. The account number must be assigned when creating a vendor master record. Using the number range, it is
also determined whether the numbers are assigned internally by the system or externally by the vendor.
Account group
The account group is a grouping of properties which control the creation of master records. It determines which �elds
need to be �lled when creating the master record. A number range is assigned to the account group. Accounts which
require the same master record �elds and use the same number range are created using the same account group.
Field status
The �eld status de�nitions determine the status of the �elds on the screens for the master data. The status is de�ned
dependent on the account group. It can also be determined the status dependent on the processing type (transaction)
and on the company code.
To do this, the following should be considered:
How many number ranges are required for vendor master records?
For the size of the number intervals, not only the current vendor master but also future developments need to be considered.
How many account groups are required?
At least one account group must be created in case of not using the groups available in the standard system.
The number of number ranges gives an initial clue about the number of account groups. The number ranges are assigned to the
account groups. If it is determined that several number ranges would be required, then there should be created at least as
many account groups so that the number ranges can be used.
The number of account groups needed also depends on if these groups would be used for the layout of the screens. For
example, in the standard system two account groups are recommended: one group for standard accounts and another group
for one-time accounts.
Should the screen �elds have a special �eld status dependent on the account group?
This status can depend on
the company code in which the master record is created
the transactions with which the master record is processed.
From S/4 HANA release 1511 on, transaction BP substitutes these transactions.
 
Sensitive Fields for Dual Control de�nition
De�ning a �eld in the customer/vendor master record as "sensitive", the corresponding customer/vendor account is blocked for
the payment run if the entry is changed. The block is removed when a second person with authorization checks the change and
con�rms or rejects it.
Example
https://help.sap.com/docs/disclaimer
4/11/2024
8This is custom documentation. For more information, please visit the SAP Help Portal
The alternative payee �eld has been de�ned as sensitive in the Customizing table. If the accounting clerk responsible changesthe entry in this �eld in the customer/vendor master record, the account is blocked for the payment run until a second person
with authorization con�rms the change to the master data.
Transaction FK08 displays all the changes to Sensitive �elds. Nevertheless, sometimes changes done in all the sensitive �elds
are not displayed.
Instead, in FK08 only few sensitive �elds are displayed. For e.g. if in Customer/Vendor Master Data changes are done in Bank
Details for e.g. Bank Account, Bank Country, Reference Details and Account Holder then, in FK08 changes in Reference Details
and Account Holder will not be displayed.
System Behaviour
The bank data are stored in database table LFBK.
This database table has (besides the Account Number of the Vendor) three key �elds:
1. Bank Country Key (BANKS)
2. Bank Key (BANKL)
3. Bank Account Number (BANKN)
Other �elds (Partner Bank Category, Bank Control Key, Reference Speci�cation, and so on) are not key �elds.
If you change any of these key �elds, you are technically deleting one entry in table LFBK and inserting a new one. In case a
database entry is deleted, only one change document is written, saying that an entry has been deleted. The same is true when a
new entry is created. A single entry is written saying that the entry has been created. It is not possible to write a change
document for every �eld that has been deleted or created. This would make then number of change documents explode after a
short time.
This means, every time you change one of the �elds BANKS, BANKL and BANKN one sentence is deleted in the database table
and a new entry is created. This is because you changed one of the key �elds. When the data are deleted from LFBK for every
single �eld of LFBK a change document is created noting the old value of the �eld and the fact that it is deleted. Therefore, if
you change BKREF and e.g. BANKN you will see in FK08:
BKREF ****deleted**** old value.
Since you changed one of the key �elds also a new entry is created in LFBK. When a new entry is created in a database table
change documents are only written for the key �elds of the table. If change documents would be written for ALL �elds in the
database table the database tables containing the change document would be too huge very quickly. Consequently in FK08 it is
not possible to show the new value of BKREF when one of the key �elds for LFBK have been changed.
Bank data are CHANGED when the key �elds of the database table LFBK remain the same. In this case a change document is
created for the �eld that was changed. Thus, you will only get a change document for BKREF if BANKS, BANKL and BANKN
remain the same. This is the system standard behavior.
System Behavior with Example
1. De�ne Sensitive �eld. Here we are de�ning Sensitive Fields for Customer Master Data.
Go to SPRO
https://help.sap.com/docs/disclaimer
4/11/2024
9This is custom documentation. For more information, please visit the SAP Help Portal
https://help.sap.com/docs/disclaimer
4/11/2024
10This is custom documentation. For more information, please visit the SAP Help Portal
2. Now in Customer Master Data FD02 modify all the sensitive �elds
3. In Master Data if you display the changes done through Environment->Account Changes, It displays as shown below
Here it doesn’t show changes to Account Holder and Reference Details.
4. Now, checking the �elds in FK08
https://help.sap.com/docs/disclaimer
4/11/2024
11This is custom documentation. For more information, please visit the SAP Help Portal
5. Clicking on "Changes to sensitive �elds"
Here, in FK08 also it does not show Account Holder and Reference Details.
6. Now, in FD02 modify only the Reference Field and keep other data same
7. In Master Data if you display the changes done through Environment->Account Changes, It displays as shown below
Here, it shows reference details have been changed
https://help.sap.com/docs/disclaimer
4/11/2024
12This is custom documentation. For more information, please visit the SAP Help Portal
It displays the old value and the new value. Similarly it will display in FK08.
Bank data are CHANGED when the key �elds of the database table LFBK remain the same. In this case a change
document is created for the �eld that was changed. Thus, we will only get a change document for BKREF if BANKS,
BANKL and BANKN remain the same.
Related SAP Notes/KBAs
73039 - Display master record changes: bank details
Accounts Payable - Periodic Processing
This area contains information in relation to Account Payable Periodic Processing
Accounts Payable - Periodic Processing
Free Selections on "Create payment runs for payment request" ( RFPRQZLP )
How to Use Program RFF110S
Periodic Vendor Dunning
Free Selections on "Create payment runs for payment request" ( RFPRQZLP )
Purpose
The purpose of this content is to provide some guidance about the system logic involving Free Selections on RFPRQZLP.
Overview
This function is not available on the screen or it's not working then we will show you how to have the free selections available.
When does the issue appear?
When you're trying to create a new payment run for the payment requests ( program RFPRQZLP ). 
Solution:
First, apply the SAP Note 1374936 and all manual steps advised in this note. Then, you'll be able to use the free selections within
the program following the steps below:
https://help.sap.com/docs/disclaimer
https://me.sap.com/notes/73039/E
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880604.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880751.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880943.html
https://service.sap.com/sap/support/notes/1374936
4/11/2024
13This is custom documentation. For more information, please visit the SAP Help Portal
Then you have to �ll all the required �elds:
https://help.sap.com/docs/disclaimer
4/11/2024
14This is custom documentation. For more information, please visit the SAP Help Portal
Then you'll see a change in the selections button:
https://help.sap.com/docs/disclaimer
4/11/2024
15This is custom documentation. For more information, please visit the SAP Help Portal
Now you can click on the button and you'll see the free selections:
https://help.sap.com/docs/disclaimer
4/11/2024
16This is custom documentation. For more information, please visit the SAP Help Portal
Related SAP Notes/KBAs
1374936 - RFPRQZLP Custom selections
How to Use Program RFF110S
Purpose
The purpose is to show the program RFF110S and where �nd the results of its run.
Overview
This Expert content page shows the difference of the program RFF100S of the transaction F110 and how to use it. This page also
shows the parameters screen and how to access this program and see its results in transaction F110.
Program RFF110S x Transaction F110
Different of the transaction F110, that runs automatic payments online, the program RFF110S is used to schedule payment
program SAPF110S in the background. It does not run the payment although it offers the same parameters as are available in
https://help.sap.com/docs/disclaimer
https://service.sap.com/sap/support/notes/1374936
4/11/2024
17This is custom documentation. For more information, please visit the SAP Help Portal
transaction F110.
To run the program RFF110S do the following steps:
1. Access the transaction SE38.
2. Execute the program RFF110S.
You can access the log of the scheduled payment run and also the lists generated both via job administration (the update run is
scheduled under the name F110 - 'Date' 'Identi�cation', for the proposal run only 'X' is appended) and using transaction F110. If
you scheduled the report in the Schedule Manager then the output of the payment program is likewise available there.
https://help.sap.com/docs/disclaimer
4/11/2024
18This is custom documentation. For more information, please visit the SAP Help Portal
https://help.sap.com/docs/disclaimer
4/11/2024
19This is custom documentation. For more information,please visit the SAP Help Portal
Related SAP Notes/KBAs
SAP Note 86578 - Guidelines for F110 Payment Program (W/Check mgmt)
SAP Note 1229647 - F110 ... Using transaction variants to control payment runs
SAP KBA 2798234 - F110: How to schedule payment runs sequentially?
Periodic Vendor Dunning
Purpose
This page provides insight into vendor Dunning procedure. It is the process of Correspondence with the company Vendors about
pending bills (Vendor open items). 
Overview
Sometimes your vendors may fall behind on payments. You can send them a payment reminder or a dunning notice to remind
them of their outstanding debts.
The SAP System allows you to dun business partners automatically. The system duns the open items from business partner
accounts in which the overdue items create a debit balance. The dunning program selects the overdue open items, determines
the dunning level of the account in question, and creates a dunning notice. It then saves the dunning data determined for the
items and accounts affected.
You can use the dunning program to dun both customers and vendors. It may be necessary to dun a vendor if he or she has a
debit balance as a result of a credit memo. If a customer is also a vendor, you can offset the account balances against one
another.
Description
In SAP we can schedule the Dunning Process and maintain different Dunning Levels for Dunning run .The Dunning process
involves the following steps:
1. Entering Parameters in the dunning program. The parameters of old dunning run can be copied and dates can be
adjusted.
2. The Dunning run selects the accounts, examines them for overdue items, checks if they have to be dunned, and assigns
dunning levels to them. All dunning data is stored in a dunning proposal.
3. The Dunning Proposal can be edited, deleted and recreated as often as necessary until the dunning clerk is satis�ed with
the result.
4. If desired, this step can be skipped and the dunning run can be followed directly by the printout of dunning notices.
5. In One Click, Dunning notices are printed and dunning data is updated in the master records and associated documents.
The following is an example of Complete Dunning run for vendors as a background scheduled job.
 First enter the Transaction F150 in the SAP Command Field
https://help.sap.com/docs/disclaimer
https://service.sap.com/sap/support/notes/86578
https://service.sap.com/sap/support/notes/1229647
https://me.sap.com/notes/2798234
4/11/2024
20This is custom documentation. For more information, please visit the SAP Help Portal
In the next screen enter the Following:
1. Enter the Dunning run date
2. Enter the Dunning run Identi�cation
 
In the 'Parameters' Tab
1. Enter the Dunning Date
2. Enter the Date up to which the documents for dunning are to be considered
3. Enter the Company Code for dunning
4. Enter the vendors accounts be dunned. This can be done for a single vendor or for a speci�c range of vendors.
https://help.sap.com/docs/disclaimer
4/11/2024
21This is custom documentation. For more information, please visit the SAP Help Portal
Save the Dunning Parameters and go back to the previous tab 'Status'
 
Next step will be to schedule the Dunning run by pressing the Schedule button. This can be found in the 'Status' tab.
 
In the next screen select the printer to print the dunning notices to be generated
https://help.sap.com/docs/disclaimer
4/11/2024
22This is custom documentation. For more information, please visit the SAP Help Portal
 
And after this you need to schedule the time of dunning run.
 
At this stage the �nal status can be checked
Output
You can view the Dunning Notice in the spool request with the amount and list of pending bills for vendors in question.
https://help.sap.com/docs/disclaimer
4/11/2024
23This is custom documentation. For more information, please visit the SAP Help Portal
https://help.sap.com/docs/disclaimer
4/11/2024
24This is custom documentation. For more information, please visit the SAP Help Portal
Related SAP Notes/KBAs
SAP note 1489317 - Dunning: Vendor credit memos
SAP note 957556 - Dunning: Vendor credit memos without invoice reference
SAP note 6591 - Resetting dunning data after printing
SAP note 982658 - Required �eld check for dunning data
SAP note 3320712 - F150: RFMAHN_CHECK post-implementation steps for SAP Note 3290501
SAP note 3290501 - F150: New check report RFMAHN_CHECK: Lock entries and status of dunning runs
Clearing Vendors Against Customers
Clearing of accounts - If Customer is vendor or Vice Versa:
The clearing between the customer and vendor can happen by following the below settings
1. The customer number must be entered in the corresponding vendor master record
 a. FK02->General Data -> Control
 In the 'Account control' tab, in the 'Customer' �eld, enter the customer number
 b. In the Company Code Data --> Payment Transaction Accounting, select the checkbox - 'Clrg with Cust'
2. The vendor number must be entered in the corresponding customer master record
 a. FD02->General Data -> Control
 In the 'Account control' tab, in the 'Customer' �eld, enter the vendor number
 b. In the Company Code Data --> Payment Transaction Accounting, select the checkbox - 'Clearing with vendor'
3. For testing, create a vendor invoice through FB60 and customer invoice through FB70. Note that customer and vendor are
properly selected.
4. For clearing the open items. Use the Tcode F-32. On clicking the 'Process open Items', the vendor invoice (KR) and customer
invoice (DR) are shown automatically. It will generate the FI document with proper entry.
Note: Partial / Residual payment between customer and vendor is also possible
Accounts Receivable (Customer)
This section covers the Account Receivable (AR) in Financials.
Accounts Receivable (Customer)
Accounts Receivable - Master Records
Accounts Receivable - Credit Management
Accounts Receivable - Periodic Processing
Accounts Receivable - Master Records
In transactions FD01, FD02 and FD03 �nancials customer master data can be created, modi�ed and displayed respectively.
https://help.sap.com/docs/disclaimer
https://service.sap.com/sap/support/notes/1489317
https://me.sap.com/notes/957556
https://service.sap.com/sap/support/notes/6591
https://service.sap.com/sap/support/notes/982658
https://me.sap.com/notes/3320712
https://me.sap.com/notes/3290501
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880703.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880676.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880680.html
4/11/2024
25This is custom documentation. For more information, please visit the SAP Help Portal
For this purpose, some preparation activities should be carried out in the customizing (SPRO transaction):
In the settings for preparing to create customer master records following objects are required:
Number ranges
The number range determines the number interval from which the account number for the master record is to be
selected. The account number must be assigned when creating a customer master record. Using the number range, it is
also determined whether the numbers are assigned internally by the system or externally by the customer.
Account group
The account group is a grouping of properties which control the creation of master records. It determines which �elds
need to be �lled when creating the master record. A number range is assigned to the account group. Accounts which
require the same master record �elds and use the same number range are created using the same account group.
Field status
The �eld status de�nitions determine the status of the �elds on the screens for the master data. The status is de�ned
dependent on the account group. It can also be determined the status dependent on the processing type (transaction)
and on the company code.
To do this, the following should be considered:
How many number ranges are required for customer master records?
https://help.sap.com/docs/disclaimer4/11/2024
26This is custom documentation. For more information, please visit the SAP Help Portal
For the size of the number intervals, not only the current customer master but also future developments need to be considered.
How many account groups are required?
At least one account group must be created in case of not using the groups available in the standard system.
The number of number ranges gives an initial clue about the number of account groups. The number ranges are assigned to the
account groups. If it is determined that several number ranges would be required, then there should be created at least as
many account groups so that the number ranges can be used.
The number of account groups needed also depends on if these groups would be used for the layout of the screens. For
example, in the standard system two account groups are recommended: one group for standard accounts and another group
for one-time accounts.
Should the screen �elds have a special �eld status dependent on the account group?
This status can depend on
the company code in which the master record is created
the transactions with which the master record is processed.
From S/4 HANA release 1511 on transaction BP substitutes these transactions.
Accounts Receivable - Credit Management
This area contains information in relation to Account Receivable Credit Management
Accounts Receivable - Credit Management
Classic Credit Management
Credit control area in FBL5N
F_KNB1_ANA authorization check
Main Credit Check Methods in FI (OVA8) in classic credit management (ECC system)
Classic Credit Management
Classic credit management (ECC system)
Applies to:
All SAP ERP versions 
Summary
The page explains the importance of credit management to a business and basic settings needed to be done to set up in classic
credit management in SAP.
Credit Management : Importance
Regardless of the type of business involved in, one factor which is most important to keep it running is cash. Most businesses
are closed down because they become insolvent due to improper management of cash �ows. Outstanding receivables or bad
https://help.sap.com/docs/disclaimer
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880481.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880440.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361881244.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878884.html
4/11/2024
27This is custom documentation. For more information, please visit the SAP Help Portal
debts can have a considerable impact on a company’s performance. One aspect which goes a long way in helping to have well
managed cash �ows is credit management or credit policy towards customers. Organizations today are recognizing the
importance of this aspect and hence, most of them have a dedicated system for this too. Good credit management forms an
essential part of the organization’s strategy. It is as important as the sales and pro�ts on the P&L statement but should not
deter excellent customer service.
Credit management is just like telling our customers that they need not pay immediately, they can pay at a future point of time
after receiving the goods or services. But, this payment at a future point of time involves risk. So, according to the risk foreseen,
the amount and time of credit granted changes. For some customers, the risk perceived may be high such that we may demand
payment in advance.
This credit management forms a part of Sales and Distribution (SD) as well as Account Receivables (AR). The various roles of
this policy are:** Maintaining good cash �ow
Reducing the risk of bad debt
Managing the company’s largest asset – Debtors
Minimizing the cost of granting credit
Promoting good customer relations and prompt payment
Finally, contributing to maintaining healthy company pro�ts.For this, we have to determine the �nancial situation
of a customer or group of companies, recognize early warning signals, and make decisions more easily with
reference to the credit assignment. This is especially important if we do business with customers in �nancially
unstable sectors or countries, or trade with countries that are politically instable or that adopt a restrictive
exchange rate policy.
Credit Management in SAP
Assuming that we already have SD and AR implemented, credit management can be broadly used to:
Assign credit limit to customers
Facilities like the credit master sheet or early warning list help you monitor the customer’s credit situation
Automatic credit limit checks as well as the points at which they have to be carried out can be speci�ed
The credit representative is automatically alerted to a customer’s critical credit situation as soon as order
processing starts and he may be able to check a customer’s credit situation quickly and reliably, and, in line with
the appropriate credit policy, to decide whether the customer should be granted credit.
Take for instance a simple process �ow through which the way credit management is handled by SAP can be
understood:
1. A sales order is entered
Assuming that this sales order leads to the credit limit being exceeded for this customer, the system now responds in one of
two ways
It outputs an error message preventing from saving the order.
It outputs a warning message, does not prevent from saving the order but blocks it.
In the second case:
1. One can processes the blocked order either from a list of blocked sales and distribution documents, or from his/her
Mailbox. From the list of blocked documents information functions, such as credit master sheet and early warning listcan
be used make the decision.
2. Once the order is released, a delivery can be created and a billing document generated. Once this document is saved, the
system automatically creates a �nancial accounting document.
3. The customer pays the invoice that was created in the previous step. Post the incoming payment in Accounts Receivable.
Organizational unit in credit management
https://help.sap.com/docs/disclaimer
4/11/2024
28This is custom documentation. For more information, please visit the SAP Help Portal
The organizational unit used in credit management is Credit Control Area. It represents the area where customer credit limits
are speci�ed and monitored.Depending on the relationship between credit control area and company code, the credit
management can be categorized as:
Decentralized credit management - Every company code has its own credit control area. Hence, we can de�ne credit
limits for a customer sperately for each company code.
Centralized credit management - Multiple company codes are clubbed under the same credit control area. So, if the
customer transacts with company codes which are under the same credit control area, the limit is set for all the
company codes combined together. If the currencies of these company codes are different from that of the credit control
area, the receivables are converted to the credit control area currency to check with the credit limit set.
Credit limits and credit exposure are managed at both credit control area and customer level. It is to be noted that a company
code cannot be divided into multiple credit control areas.
Credit Limits
The credit limit is that total combined value of the following
Open Sales Order -> A sales order which has been created but not delivered
Open Deliveries -> An order which has been delivered but not yet invoiced
Open Billing Document -> Value of billing document which has not yet been forwarded to accounting
Open Items -> Items which have been forwarded to accounting but not yet settled.
Note : Special G/L transactions and postings with an alternative reconciliation account can be excluded from credit limit check
using settings in the system
De�ning Credit Control Area
To de�ne a credit control area, use the t-code OB45 or the menu path SPRO -> IMG -> Enterprise Structure -> De�nition ->
Financial Accounting -> De�ne Credit Control Area 
Use thebutton New Entries to create a new credit control area or double click on a entry to change an already existing
one
Give the name and long description for the credit control area. The name is a four-character alpha numeric key.
Specify the currency in which this area is to be managed
The type of update controls when the values of open sales orders, deliveries and billing documents are updated
depending upon the type of document being generated
FY Variant is used to specify the �scal year variant for the credit control area. Useful especially when it contains multiple
company codes having different �scal years
Default data can be speci�ed for new customers created in the company codes under the credit control area. At least
one of the three �elds if speci�ed ensures that a credit restriction will be applicable to new customers as soon as they
are created since the default data helps automatically create a credit master record
If the All company codes check box is set, it implies that credit control area is permitted for postings in every company
code created in the system
Note : In the simplest case, each company code corresponds to one credit control area. In this case, it is recommended to use the same key for the
credit control area as for the company code.
Assigning Company code to Credit control area
Each credit control area created in the system has at least one company code. Use t-code OB38 or the menu path SPRO -> IMG
-> Enterprise Structure -> Assignment -> Financial Accounting -> Assign Company Code to Credit Control Area
Specify the credit control area name in the CCAr �eld corresponding to the company codes to which it has to be assigned. The
last check box named overwrite CC area if checked, will help overwrite the credit control area derived from the company code
https://help.sap.com/docs/disclaimer
4/11/2024
29This is custom documentation. For more information, please visit the SAP Help Portal
global data with the one speci�ed here during document posting.
Derivation of Credit control area
Credit control area can be derived in any of the below given 4 ways. The sequence of derivation is as follows:
User exit EXIT_SAPFV45K_001 derives it from all the �elds in the sales order header
Sales area if in customizing of SD, sales areas have been assigned to credit control areas
Customer master
Company code
Customers-Company codes-Credit control areas
If a customer is created only in one company code, the simplest case possible, the credit control area for that company
code controls the customer limits
If a customer is created in many company codes which fall under a common credit control area, then this credit control
area itself controls the customer limits
However, if a customer is created in many company codes which fall under different credit control areas, a separate
credit limit is managed for the customer in each of the different credit control areas.
Customer credit management
For each customer, credit limits are speci�ed in the particular credit master record. If the customer exists in multiple credit
control areas, individual limit can be speci�ed for each credit control area. In addition, a central credit limit can also be speci�ed
for all the credit control areas under which the customer exists. Then, the total of the credit limits for each credit control area
should not exceed the central credit limit.
The customer credit management is done using t-code FD32 or the menu path SAP Easy Access Menu -> Accounting ->
Financial Accounting -> Account Receivable -> Credit Management -> Master Data -> Change
As seen in the screen shot above, enter the customer number and the credit control area for which the data for the customer
credit is to be maintained. There are 5 check boxes which can be selected/de-selected based on the screens which we want to
view. There are 5 check boxes corresponding to 5 screens:
1. Overview Screen:
It gives an overview of credit settings of the customer.
Customerʻs credit limit, credit exposure, percentage of credit limit used and horizon (as applicable in dynamic credit
check) are presented as status
Payment history along with the average number of days taken for payment is shown
Payment data contains details such as authorized cash discount and unauthorized cash discount that was available for
cleared items, the outstanding receivables in sales days
Dunning data consists od dunning area for the customer, when he was last dunned and the dunning level reached during
the last dunning run
Control contains the credit risk category of the customer, date of the last check on customer credit limit, if the customer
is blocked for credit management business transactions, the credit representative group responsible for the customer,
the payment history classi�cation, the �nancial standing of the customer and date when the credit check of the
customer was carried out last.
 2. Address: 
 It gives the customers address details
https://help.sap.com/docs/disclaimer
4/11/2024
30This is custom documentation. For more information, please visit the SAP Help Portal
 3.Central Data: 
 It gives an overview of central credit limit settings of the customer.
The maximum permitted credit limit as a total of limits across all credit control areas to which the customer is assigned
The maximum permitted individual credit limit that a customer can have under any one credit control area
The currency in which the two maximum limits are speci�ed. This is because we can enter the central data in any
currency of choice, independently of the currencies of the control areas
The currently exhausted credit limit as a total (percentage) across all credit control areas to which the customer is
assigned (should be less than or equal to max limit)
The currently assigned largest credit limit across all credit control areas to which the customer is assigned (should be
less than or equal to max limit)
Date on which the most recent general information about the customer was obtained
 4. Status: 
 It shows the customer's actual individual details according to particular credit control area
The credit limit for the credit control area, credit account if the limit is to be speci�ed for a group of customers, the
percentage of credit exposure, horizon date to be taken into consideration, the receivables, special G\L transactions and
the order value not yet transferred to FI used for the credit exposure calculation as well as the amount of secured
receivables is shown under credit limit data
The credit risk category, credit representative group, customer credit group and customer group used mainly for sorting
or reporting, the reference data for customer credit review, if the customer is blocked for credit management business
transactions, the last and next internal review date for the customer credit limit as applicable to the particular credit
control area are shown under Internal data
The date of last external review, the credit information number as applicable to external agency, the classi�cation of
payment history of the customer as well as the �nancial standing is shown under external data
 5. Payment history: 
 Displays the payments made by the customer for a particular credit control area
Resetting credit limits
The credit control area can be changed only if there are no subsequent documents or transactions done in it. Otherwise, the
credit limit needs to be restructured. This resetting is used if:
A company code is to be assigned to a new credit control area
The assignment of company codes to credit control areas is to be changed
The currency of a credit control area is to be changed
The classi�cation of a difference reason code from disputed to non-disputed (or vice versa) is to be altered
This resetting can be done using t-code F.28 or the menu path SAP Easy Access Menu -> Accounting -> Financial Accounting ->
Account Receivable -> Credit Management -> Tools -> Reset creditlimit
Enter the customer and credit control areas as needed and execute.
SD functions in credit management
The following SD functions can be done through credit management screen. They are found under the path SAP Easy Access
Menu -> Accounting -> Financial Accounting -> Account Receivable -> Credit Management -> Sales and Distribution Documents
Processing SD documents blocked for delivery – VA14L
Processing incomplete SD documents – V.01
Processing deliveries – VL06
Processing billing documents – VF05
https://help.sap.com/docs/disclaimer
4/11/2024
31This is custom documentation. For more information, please visit the SAP Help Portal
Released SD documents – VKM2
All SD documents – VKM4
Sales documents – VKM3
Delivery documents – VKM5
The following SD functions are found under the path SAP Easy Access Menu -> Accounting -> Financial Accounting -> Account
Receivable -> Credit Management -> Exceptions
Processing blocked SD documents from a list – VKM1
Processing blocked SD documents from SAP office inbox – SO01
In t-codes VKM1, VKM2 and VKM4, documents can be listed based on the following criteria:
Credit control area
Credit representative group
Next shipping date
Credit account
Risk category
Customer credit group
For the document selected, the following options are available:
Grant the credit and release the document
Reject the credit and cancel the document
Forward the blocked document to another processor
Recheck the blocked document
Reassign the blocked document and specify a new sequence of documents. This enables to give priority to and release
several documents with a low document value until their credit limit is completely used up, instead doing so for a single
document with a high document value that has already exceeded its credit limit.
Related Content
3346140 - DSO calculation in FD33 and in Tcode F.30/S_ALR_87012167
2930159 - Difference between FBL5N and FD32/33
2057405 - How to run the report RFDKLI20?
Credit control area in FBL5N
Overview
For some customer line items posted without KKBER ,the �eld is �lled with the value which is customized for KKBER in the table
T001 (Main data of the Company Code).
Reason
 It is the standard logic in the FBL*N transacton that if the Credit Control Area is not �lled in the documents, the value from the
Company Code data is stored.
https://help.sap.com/docs/disclaimer
https://me.sap.com/notes/3346140
https://me.sap.com/notes/2930159
https://me.sap.com/notes/2057405
4/11/2024
32This is custom documentation. For more information, please visit the SAP Help Portal
F_KNB1_ANA authorization check
By system design, the authority check on object F_KNB1_ANA occurs for each company code in which the customer exists when
one of the following �ags is activated via trans FD32/FD33: 
1) Overview (RF02L-D0105) 
2) Payment history (RF02L-D0220) 
These �ags will check related data in all company codes for Customer.
If the user activates these �ags, the authority is checked for all related company codes. Please verify whether error message
F4492 occurs when the user deactivates these �ags. If you don't check the �ags "overview" and "payment history" on the FD33
screen, there should not be any problem concerning authorizations.
The reason therefore is that with these �ags, you will get all information from all company codes. So, if your user activates
these �ags, she needs to have the authority for all concerned company codes.
Hence please note that the check of F_KNB1_ANA happens only following cases: 
1. The �ag T014-ALLCC (Indicator: Is posting possible for all company codes?) is set: 
If you remove it the system will not check other irrelevant CC (company codes) for that CCA (credit control area) (transaction
OB45).
2. In CC in the global parameters the �eld CCA is �lled with another CCA (transaction OB38, table T001, �eld KKBER). OR
3. There are other CCA's assigned to the CC than allowed (transaction OBZK, table T001CM, �eld KKBER).
In all of these cases all the other CCs have to be checked, because a credit limit relevant updates are theoretical possible there.
Main Credit Check Methods in FI (OVA8) in classic credit management (ECC
system)
Credit Check on Overdue Open Items
Speci�es whether the system performs a check against open items.
This type of credit check works in conjunction with two values that you enter in the adjacent �elds:
Maximum percentage of overdue items for open items
Days by which the open items are overdueThe ratio of open items that are overdue by more than the speci�ed days to
the total open items must not exceed the speci�ed percentage.The relationship between open items overdue by more
than a certain number of days and the balance of the customer cannot exceed a certain percentage rate.Days in arrears
are calculated from the baseline date for payment. For example, with a 30 days term of payment, days in arrears are
calculated after the 30 days have elapsed. 
https://help.sap.com/docs/disclaimer
4/11/2024
33This is custom documentation. For more information, please visit the SAP Help Portal
Credit Check on Oldest Open Items
Speci�es whether the system performs a credit check based on the oldest open item.
 The oldest open item must not be older than the speci�ed number of days.
The day speci�cation determines by how many days the oldest open item can be overdue.
https://help.sap.com/docs/disclaimer
4/11/2024
34This is custom documentation. For more information, please visit the SAP Help Portal
 
 
Credit Check on Highest Dunning Level
Indicates whether the system carries out a credit check based on the highest dunning level.
With this type of credit check, you specify the highest dunning level you want to allow in the adjacent �eld. The dunning level is
tracked and stored in the credit data in the customer master record. If this level is exceeded during order or delivery processing,
the system carries out a credit check.
https://help.sap.com/docs/disclaimer
4/11/2024
35This is custom documentation. For more information, please visit the SAP Help Portal
 
If FSCM credit management is activated, this page is not relevant.
 
Accounts Receivable - Periodic Processing
This area contains information in relation to Account Receivable Periodic Processing
Accounts Receivable - Periodic Processing
Periodic Customer Dunning
Periodic Customer Dunning
Purpose
This page provides insight into customer Dunning procedure. It is the process of Correspondence with the company customers
about pending bills ( Customer open items).
Overview
https://help.sap.com/docs/disclaimer
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880941.html
4/11/2024
36This is custom documentation. For more information, please visit the SAP Help Portal
Sometimes your customers may fall behind on payments. You can send them a payment reminder or a dunning notice to remind
them of their outstanding debts.
The SAP System allows you to dun business partners automatically. The system duns the open items from business partner
accounts in which the overdue items create a debit balance. The dunning program selects the overdue open items, determines
the dunning level of the account in question, and creates a dunning notice. It then saves the dunning data determined for the
items and accounts affected.
You can use the dunning program to dun both customers and vendors. If a customer is also a vendor, you can offset the account
balances against one another.
Description
 In SAP we can schedule the Dunning Process and maintain different Dunning Levels for Dunning run .The Dunning process
involves the following steps:
1. Entering Parameters in the dunning program. The parameters of old dunning run can be copied and dates can be
adjusted.
2. The Dunning run selects the accounts, examines them for overdue items, checks if they have to be dunned, and assigns
dunning levels to them. All dunning data is stored in a dunning proposal.
3. The Dunning Proposal can be edited, deleted and recreatedas often as necessary until the dunning clerk is satis�ed with
the result.
4. If desired, this step can be skipped and the dunning run can be followed directly by the printout of dunning notices.
5. In One Click, Dunning notices are printed and dunning data is updated in the master records and associated documents.
The following is an example of Complete Dunning run for customers as a background scheduled job.
First enter the Transaction F150 in the SAP Command Field 
 
https://help.sap.com/docs/disclaimer
4/11/2024
37This is custom documentation. For more information, please visit the SAP Help Portal
 
In the next screen enter the Following:
1. Enter the Dunning run date
2. Enter the Dunning run Identi�cation
In the Parameters Tab
1. Enter the Dunning Date
2. Enter the Date up to which the documents for dunning are to be considered
3. Enter the Company Code for dunning
4. Enter the customers accounts be dunned. This can be done for a single customer or for a speci�c range of customers.
 
Save the Dunning Parameters and go back to the previous tab “Status” 
https://help.sap.com/docs/disclaimer
4/11/2024
38This is custom documentation. For more information, please visit the SAP Help Portal
 
Next step will be to schedule the Dunning run by pressing the Schedule button. This can be found in the “Status” tab.
 
In the next screen select the printer to print the dunning notices to be generated
And after this you need to schedule the time of dunning run
https://help.sap.com/docs/disclaimer
4/11/2024
39This is custom documentation. For more information, please visit the SAP Help Portal
Final status can now be checked
Output
Finally you can view the Dunning Notice in the spool request with the amount and list of pending bills for customers in question.
https://help.sap.com/docs/disclaimer
4/11/2024
40This is custom documentation. For more information, please visit the SAP Help Portal
https://help.sap.com/docs/disclaimer
4/11/2024
41This is custom documentation. For more information, please visit the SAP Help Portal
Related Content
Related Documents
Related SAP Notes/KBAs
SAP note 3322796 - F150: Account balance in dunning program (MHNK-SALDO)
SAP note 2219910 - F150: Custom selection
SAP note 6591 - Resetting dunning data after printing
SAP note 1378472 - F150: Poor performance/termination for large dunning runs
SAP note 1318067 - Resetting dunning data aftr printing w/ indiv.dunning notice
SAP note 2893616 - SACF scenario FI_F150_MASTER_DATA – documentation for extended check when displaying FI master data
SAP note 2838984 - F150: Activate dunning by e-mail
SAP note 2894225 - F150: Revision of reports RFCORR14 and RFCORR15
SAP note 3314745 - F150/F107: 'To Date' has incorrect documentation
SAP note 3308645 - F150: Preparations for inclusion of report RFMAHN_CHECK
SAP note 3292817 - F150: SAPF150R: Template dunning runs for RF150SMS should not be deleted
SAP note 3290501 - F150: New check report RFMAHN_CHECK: Lock entries and status of dunning runs
SAP note 3284563 F150: Free selection - check of table name and BKPF/BSEG �elds
SAP note 3320712 - F150: RFMAHN_CHECK post-implementation steps for SAP Note 3290501
SAP note 3290501 - F150: New check report RFMAHN_CHECK: Lock entries and status of dunning runs
SAP KBA 2732898 - How to de�ne the print parameters in report SAPF150D2 or in transaction F150
SAP KBA 2427515 - F150: Dunning charges for application FI-FI
SAP KBA 2405414 - F150: Dunning by e-mail: introductory text / Mailtext (using a PDF form)
SAP KBA 1786657 - Dunning level zero on the dunning letter
SAP KBA 1654983 - Error message TD422 appears in dunning run
https://help.sap.com/docs/disclaimer
https://me.sap.com/notes/3322796
https://me.sap.com/notes/2219910
https://service.sap.com/sap/support/notes/6591
https://service.sap.com/sap/support/notes/1378472
https://service.sap.com/sap/support/notes/1318067
https://me.sap.com/notes/2893616
https://me.sap.com/notes/2838984
https://me.sap.com/notes/2894225
https://me.sap.com/notes/3314745
https://me.sap.com/notes/3308645
https://me.sap.com/notes/3292817
https://me.sap.com/notes/3290501
https://me.sap.com/notes/3284563
https://me.sap.com/notes/3320712
https://me.sap.com/notes/3290501
https://me.sap.com/notes/2732898
https://me.sap.com/notes/2427515
https://me.sap.com/notes/2405414
https://me.sap.com/notes/1786657
https://me.sap.com/notes/1654983
4/11/2024
42This is custom documentation. For more information, please visit the SAP Help Portal
SAP KBA 1649694 - Error message FM120 or FM861 in the dunning run
SAP KBA 1920888 - Transaction F150: error FM804 payment method for incoming payment
Accounts Business Transactions: Bill of Exchange(BoE)
The following documentation explains the process for the posting and processing of Bill of Exchange for customer and Bill of
Exchange for vendors: 
Accounts Business Transactions: Bill of Exchange(BoE)
Bill of Exchange(BoE) for customers
Fields Bank Key and Bank Account are missing during Bill of Exchange posting
Bill of Exchange(BoE) for vendors
Bill of Exchange(BoE) for customers
What is Bill of Exchange(BOE)?
1. Bill of exch. as payment medium with due date
2. Bill of exch. as short term credit for customer
3. Bill of exch. as �exible �nancing medium: Vendor can discount bill of exchange before due date dependent on �nancial
requirements.
4. The bill of exchange is usually created by the Accounts Payable/Accounts Receivable department of a company.
5. Bills of exchange are handled as “Special G/L transactions” in the SAP System and a “Special G/L indicator” is updated
in the respective bill of exchange line items, via which the special account determination is determined.
Types of BOE:
1. Promissory note
The customer is the creator of the bill of exchange and at the same time the drawee of the bill of exchange. He sends the
bill of exchange to his business partner.
2. Paper BOE, BOE payment request 
The vendor sends a bill of exchange to his business partner to be signed. The customer sends it back on a certain date.
The vendor can request that the bill be sent back-> Draft paper bill.
3. Bank bill of exchange
here exists a general agreement between business partners. The vendor creates a bill of exchange, enters the customer
as bene�ciary and sends this bill of exchange directly to the bank-à bank bill of exchange. 
Senarios for example 1:
 ① Posting customer invoice (T-cd:FB01、FB70)
 Customer 1,000,000 / Revenue 1,000,000
 ② BOE payment (F-36 individual processing, F110-> mass processing)
 BOE for Customer 1,000,000 / Customer 1,000,000
 ③ Incoming payment(T-cd:F-28)
https://help.sap.com/docs/disclaimer
https://me.sap.com/notes/1649694
https://me.sap.com/notes/1920888
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880932.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880818.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880657.html
4/11/2024
43This is custom documentation. For more information, please visit the SAP Help Portal
 Bank 1,000,000 / Customer(BOE) 1,000,000
Senarios for example 2
 ①、 ② steps are the same with case 1.
 ③ BOE Presentation-> Bill of exchange presented to the bank(discounting or collection),Contingent liability (commitment set
up) to the bank is set up, because the house bank only requires the money back from the vendor if the bill bounces.
 BOE bank subaccount 1,000,000 / BOE liability account 1,000,000
 ④ After bill due date, reversing contingent liability.
 BOE liability account 1,000,000 BOE for customer 1,000,000
 ⑤ Bank statement(import from FF.5)
 Bank account 1,000,000 BOE subaccount 1,000,000
 In case If bill of exchange bounced, update the failed payment transaction FBZG.
 Instead of mass processing in FBWE, individual process can be done in transaction codes T-cd:F-33/F-34/F-35=FBW3, F-
20=FBW4.
Document display in SAP systemfor example 2:
①Customer invoice in T-code:FB70 
https://help.sap.com/docs/disclaimer
4/11/2024
44This is custom documentation. For more information, please visit the SAP Help Portal
②BOE Payment in T-code:F-36
③BOE Presentation in T-code FBWE
https://help.sap.com/docs/disclaimer
4/11/2024
45This is custom documentation. For more information, please visit the SAP Help Portal
④Reversing contingent liability in T-code:F.72 
 Clearing BOE Liabilities 
⑤Clearing bank subaccount manually or Via T-code FF.5
https://help.sap.com/docs/disclaimer
4/11/2024
46This is custom documentation. For more information, please visit the SAP Help Portal
Account diagram with typical posting steps for customer 
Main Customizing for customer’s BOE.
1.IMG: Financial accounting(NEW) ->Bank Accounting ->Business Transactions ->Bill of Exchange Transactions -> Bill of
Exchange Receivable
 - Present Bill of Post Bill of Exchange Receivable->De�ne Alternative Recon. Acct for Bills / Exch. Receivable(T-
cd:OBYN).
 - Exchange Receivable at Bank-> De�ne Bank subaccounts(OBYK) 
 - Present Bill of Exchange Receivable at Bank-> Maintain house bank details (V_T012K_W-> De�ne the discount 
account and Collection account for a house bank
 - Present Bill of Exchange Receivable at Bank-> Enter Bank assignment(V_T045F) 
2.IMG: Financial accounting(NEW) ->Bank Accounting ->Business Transactions ->Bill of Exchange Transactions ->Bill of Exchange
Receivable
 - Present Bill of Exchange Receivable at Bank-> De�ne User-Speci�c Settings(V_TFBWE)
 - Present Bill of Exchange Receivable at Bank-> Assign Forms for Bill of Exchange Receivable(standard form
F_SAPMFBWE_J10) (OT63)
 - Bill of Exchange Receivable: Reverse Contingent Liability-> De�ne Bill of Exchange Payment Period (OB86)
Missing Bank Key and Bank Account �elds
Fields Bank Key and Bank Account are missing during Bill of Exchange posting
Fields Bank Key and Bank Account are missing during Bill of Exchange posting
Overview
The �elds "Bank Key" (BSEC-BANKL) "Bank Account" (BSEC-BANKN) are not available in the Bill of exchange items (For
instance:posting key 09 ; Special GL ind.: W). The dynpro shown is SAPMF05A 0320 and it doesn´t have the �elds BANKL and
BANKN as input �elds.
Reason
As long as the "Document entry screen variant" is set to Blank (Standard) in the company code settings (OBY6), the screen
number 320 of the module pool SAPMF05A is called which does not have the �elds BANKL and BANKN as input �elds.
https://help.sap.com/docs/disclaimer
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880818.html
4/11/2024
47This is custom documentation. For more information, please visit the SAP Help Portal
Solution
For entering the payment method with the bill of exchange, screen variant 2 must be de�ned within the global data of the
company code (Transaction OBY6, 'Document entry screen variant'). This then calls screen 2320 of the module pool SAPMF05A
and these 2 �elds will be available.
Related SAP Notes/KBAs:
1925370 - Payment Method is missing during BoE posting
Bill of Exchange(BoE) for vendors
BOE senarios 1 for vendor
① Posting vendor invoice (T-cd:FB01、FB60)
 Expense 500,000 Vendor 500,000
② BOE payment for vendor (T-cd:F-40)
 Vendor 500,000 BOE for vendor 500,000
③ Outgoing payment (T-cd:F-53)
 BOE for vendor 500,000 Bank 500,000
BOE senarios 2 for vendor
① Posting vendor invoice (T-cd:FB01、FB60)
 Expense 500,000 Vendor 500,000
② BOE payment (T-cd:F110)
 Vendor 500,000 BOE for vendor 500,000
 BOE liability account 500,000 Bank subaccount 500,000
③ Returned BOE payable (T-cd:FBWD)
 BOE for vendor 500,000 Bank 500,000
 Bank subaccount 500,000 BOE liability account s500,000 
In Customizing for the payment program, it is possible to de�ne for each payment method whether the bill of exchange
only consists of two vendor line items or whether two further bank line items are added (T042E-XWVBU).Only the four
line bill of exchange document is processed further with transaction “returned bills of exchange payable” (FBWD), as
FBWD selects the bills of exchange via bill of exch. liability account.
Document overview in SAP system
①Post 3 vendor document in T-cd:FB01 
https://help.sap.com/docs/disclaimer
https://me.sap.com/notes/1925370
4/11/2024
48This is custom documentation. For more information, please visit the SAP Help Portal
②Run F110 With payment method B(BOE) 
Payment document which is created in T-cd:F110 
https://help.sap.com/docs/disclaimer
4/11/2024
49This is custom documentation. For more information, please visit the SAP Help Portal
③Returned BOE Payable in T-cd:FBWD 
Customizing for Vendor’s BOE.
IMG: Financial accounting(NEW) ->Bank Accounting ->Business Transactions ->Bill of Exchange Transactions->Bill of
Exchange Payable
- Returned Bills of Exchange Payable -> De�ne Account for Returned Bills of Exchange (T-cd:OT68). 
- Returned Bills of Exchange Payable -> De�ne Forms for Returned Bills of Exchange Payable (T-cd:OT65)
The returned bills of exchange account (T012k-wkkon or T046a-wkkon) has Open item maintenance and is relevant to
cash �ow.
The clearing account (T042i-vkont, this case is111380) has Open item maintenance and is NOT relevant to cash �ow.
Account diagram with typical posting steps for customer 
 
Payment Program
https://help.sap.com/docs/disclaimer
4/11/2024
50This is custom documentation. For more information, please visit the SAP Help Portal
Automatic Payment Run
For each company code using the payment program, certain basic speci�cations must be in place.
Since the payment program can be used for more than one company code, you must also specify the company code that is
making the payment.
Detail Steps are as follows.
House Bank Con�guration - FI12.
Payment Program Con�guration - FBZP
De�ne Check numbers - FCHI and Void Reasons - FCHV
Payment Run - F110
To control the payment program, you must specify the following in advance:
How payment requests are selected and, if necessary, grouped together for one payment
The payee
How the payment method is selected
How the bank is selected
Which forms and other data carriers are used
Activities
You make these speci�cations when:
Con�guring the payment program
Entering data in the master records of your business partner
Entering data in the payment requests
Entering data for the payment run in hand
 When con�guring the payment program, you specify the company codes that are involved in automatic payments and
also which company code makes the payments (paying company code).
The payment program identi�es the open payment requests and selects the items to be paid. It basically pays items as late as
possible. You specify the exact time of payment when con�guring the payment program
The selection of open payment requests is determined by the following factors:
The due date of the items is basically determined by the due date and the level of urgency indicator in the payment
request
For each payment run, you specify the date of the next payment run. The program uses this date to determine whether
an item is to be included in the current or the next payment run.
You block the items that, regardless of their due date, you do not want to pay. To do this, you enter a blocking key in the item
that represents the reason for blocking. If you want to block the account of a customer or vendor from payment, you enter the
blocking key in their master record.
The standard system contains several blocking keys, which you can add to or change.
The payment program creates a payment proposal during the payment run. The payment is made on the basis of this payment
proposal list. The blocked items are displayed separately in the list. You can process the payment proposal, and, for example, set
or cancel the payment block on an item.
https://help.sap.com/docs/disclaimer
4/11/2024
51This is custom documentation. For more information,please visit the SAP Help Portal
It is also possible to specify that a blocking key cannot be changed from the payment proposal transaction.
On the whole, the payment date is used as the clearing date. There exist, however, the following exceptions.
Items whose posting date comes after the posting date of the payment run will be paid, provided they are already due.
The clearing date for such payments is not the payment date, but rather the latest posting date possible. Thus any danger of
the clearing date coming before the posting date is prevented in the context of paid items. Errors are avoided in this way.
Grouping of Payment Requests 
Use.
Wherever possible, the payment program will always group payment requests together for payment. However, you can also
specify that an individual payment (separate payment) is made for a particular item. For certain payment methods, only
individual payments are possible.
The payment program can only group together open payment requests into one payment if the open items in an account have
the same:
Payment currency
Payment method in the item
Bank in the item
Contents of the grouping �elds
You can also settle payment requests from different company codes together as well as customer and vendor items.
Items in an account are not grouped together if you:
Make payments separately per business area. This procedure entails separate payments being created per business
area.
Wish to make individual payments.
For further information, follow the link
Control of the Payment Program 
Payment Program
Automatic Payment Run
Delete Output in F110
Manual payment for vendor or customer account
Payment Program - Error Message FZ 326
Selection of Partner Bank Type (BVTYP) From Vendor Master Data in F110
Error FZ506 'No valid payment method found' in F110 payment proposal
General procedures and Tables in Automatic paymnt run
Authorization Check in F110
Reorganization in F110
Difference Between FBZP and F11CU
Display long account number RFZALI20
How to avoid error FZ331 during payment for tax jurisdiction country
Message FZ361 occurs in the T-CD F110
https://help.sap.com/docs/disclaimer
http://help.sap.com/saphelp_erp2005vp/helpdata/en/74/c20672e63d11d1a57a0000e839d005/frameset.htm
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878218.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361882152.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880816.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880901.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880167.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878518.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878657.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878428.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878327.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361881237.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880926.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880304.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361881967.html
4/11/2024
52This is custom documentation. For more information, please visit the SAP Help Portal
Update termination in Payment programs (F110 and F111)
Related SAP Notes/KBAs
SAP KBA 3273670 - Automatic Payment Program - Transaction F110 overview / how-to scenarios
SAP Note 545340 - FAQ: Payment run F110
An Overview of the Payment Process in SAP S/4 HANA
Executing the Payment Program - Online help
Automatic Payment Run
In FI Payment Processing we have two options.
1. Manual Payments
2. Automatic Payments (Payment Run)
This content is about point 2.
 APP is done Via F110. It has many exiting features like, auto DME generation and sending Payment advice to Vendor via Email.
We will discuss various components of Payment Run. 
Payment Methods
C Check
I Immediate Check
S Separate Check
T Electronic Payment (DME)
E EDI (IDOC) 
We can also de�ne payment methods
Posting Key
Posting keys indicate the type of line item entered.
Posting keys commonly used in AP are:
21 Credit Memo Invoice
31 Vendor Invoice
40 Gen. Ledger Debit
50 Gen. Ledger Credit
Payment Terms
A four-digit code identi�es payment terms in SAP. The �rst two digits represent the payment period, and the last two digits
represent the cash discount percentage. For example:
0000 - Payable immediately due net
1000 - Within 10 days due net
TABLES Related to Automatic Payment Run: 
https://help.sap.com/docs/disclaimer
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878528.html
https://me.sap.com/notes/3273670
https://me.sap.com/notes/545340
https://blogs.sap.com/2019/05/03/an-overview-of-the-payment-process-in-sap-s4-hana/
https://help.sap.com/docs/SAP_ERP_SPV/ba20fc74bc8c4669870d4da8e3d8b5a6/8a8cd1538cdf4608e10000000a174cb4.html?version=6.18.06
4/11/2024
53This is custom documentation. For more information, please visit the SAP Help Portal
Tables are most important items to create reports related to APP. 
BSIK AP open items
BSAK AP cleared items
BSEC One time account data
BSET Tax data
WITH_ITEM Withholding data
LFA1 Vendor master (general)
LFB1 Vendor master (company code)
LFBK Vendor bank details
LFBW Vendor withholding codes
REGUH/REGUP Payment run data
PAYR Check Information 
Related SAP Notes/KBAs
SAP KBA 3273670 - Automatic Payment Program - Transaction F110 overview / how-to scenarios
SAP Note 545340 - FAQ: Payment run F110
An Overview of the Payment Process in SAP S/4 HANA
Executing the Payment Program - Online help
Delete Output in F110
Purpose
If the user has used "Edit-> Payments -> Delete output" wrongly. It causes the problems such as cannot perform DME �le
creation, cannot �nd payment data anymore.
Overview
"Edit-> Payments -> Delete output" can only be used if NO payment documents were generated in the payment run. If there
are payment documents have been created in payment run, then it MUST NOT be used.
Explanation
Through two samples to show you 
Case 1 : "Edit-> Payments -> Delete output" can be used 
Case 2 : "Edit-> Payments -> Delete output" CANNOT be used. and what will happen if you use it wrongly.
Case 1
"Edit-> Payments -> Delete output" can only be used when NO payment documents were generated in the payment run. 
※ 1. Refer to below screens, there is no "Posting orders XX Generated, XX Completed" output, and also in table REGUH, REGUP
there is NO payment documents created. 
https://help.sap.com/docs/disclaimer
https://me.sap.com/notes/3273670
https://me.sap.com/notes/545340
https://blogs.sap.com/2019/05/03/an-overview-of-the-payment-process-in-sap-s4-hana/
https://help.sap.com/docs/SAP_ERP_SPV/ba20fc74bc8c4669870d4da8e3d8b5a6/8a8cd1538cdf4608e10000000a174cb4.html?version=6.18.06
4/11/2024
54This is custom documentation. For more information, please visit the SAP Help Portal
※ 2. In such case, you can use 'Delete output'.
※ 3. When you do the deletion, you will get a message says "after deletion payment data, it is no longer possible to create
payment media for the payment run".
https://help.sap.com/docs/disclaimer
4/11/2024
55This is custom documentation. For more information, please visit the SAP Help Portal
If you click YES, then the deletion is performed, and then edit payment proposal per your needs, and re-schedule payment run.
 
Case 2 
"Edit-> Payments -> Delete output" CANNOT be used when payment documents have been generated in the payment run. 
※ 1. Refer to below screens, there is "Posting orders XX Generated, XX Completed" output, and also in table REGUH, REGUP
there are payment documents created.
※ 2. In such case, you should NOT perform "delete output". It is a wrong operation if you perform "delete output", it will cause
payment data in tables are deleted and you can not create DME �le on it anymore.
https://help.sap.com/docs/disclaimer
4/11/2024
56This is custom documentation. For moreinformation, please visit the SAP Help Portal
 
Related SAP Notes/KBAs
SAP KBA 2136594
SAP KBA 1662257
SAP KBA 1703252
Manual payment for vendor or customer account
Missing open items in manual payment for vendor or customer account
https://help.sap.com/docs/disclaimer
https://me.sap.com/notes/2136594
http://me.sap.com/notes/1662257
http://me.sap.com/notes/1703252
4/11/2024
57This is custom documentation. For more information, please visit the SAP Help Portal
When you execute T-codes: (FB05, F-53,F-28,F-32, F-44) to do the clearing for vendor/customer account , you �nd the system
displays fewer open items than when you call up the line item display (FBL1N or FBL5N).
Purpose
To �nd the reason that the open items which missing in the manual payment for K/D account clearing.
Step1.1
Execute FBL1N or FBL5N , you �nd the open item exists in the system.
Step 1.2
in T-codes: (FB05, F-53,F-28,F-32, F-44), you want to clear the open item, but it doesn't exist in the open item process screen.
Step 2.1
Run T-ocde SE16, and enter Table name REGUS, and �ll the company code and the customer/vendor account , you �nd below
entry exist . This means there is payment proposal run exists in F110. 
https://help.sap.com/docs/disclaimer
4/11/2024
58This is custom documentation. For more information, please visit the SAP Help Portal
Step 2.2
You can �nd the payment proposal in F110. Please go to Edit-> proposal -> delete. Then the open item can be selected in the
manual payment clearing.
Related SAP Notes
SAP Note 136754: F-03, F-32, F-44, F-28 missing open items
Payment Program - Error Message FZ 326
Issue: When you run the payment through transaction F110, you face the internal error message FZ 326 in the payment run log. 
In order to solve this issue, please make sure the following combination of notes has been implemented to your system:
Latest notes:
3303809 F110: Balance error during payment of vendor net invoices (II)
3231732 F110: Balance error during payment of vendor net invoices
3127784 F110: Balance error due to alternative exchange rate for taxes with down payments in vendor net procedure
3108307 F110: Balance error for splitting of items using payment forms
2892588 Balance error with cross-company code payment and activated document splitting
2844985 F110: Error FZ326 (doc balance not zero) in payment run
2792811 F110 direct debit pre-noti�cation – error FZ326 with extended withholding tax
SAP KBA 2928806 - Error message FZ372 in F110
Selection of Partner Bank Type (BVTYP) From Vendor Master Data in F110
https://help.sap.com/docs/disclaimer
https://service.sap.com/sap/support/notes/136754
https://me.sap.com/notes/3303809
https://me.sap.com/notes/3231732
https://me.sap.com/notes/3127784
https://me.sap.com/notes/3108307
https://me.sap.com/notes/2892588
https://me.sap.com/notes/2844985
https://me.sap.com/notes/2792811
https://me.sap.com/notes/2928806
4/11/2024
59This is custom documentation. For more information, please visit the SAP Help Portal
Purpose
It will help you to understand how Automatic Payment Program selects one Partner Bank Type (BVTYP) from Vendor master
data if multiple partner bank type details are maintained.
Overview
You have maintained multiple Bank account details in Vendor master data and in automatic payment run you are expecting
Partner Bank Type (BVTYP) say Y to be picked but system is selecting BVYTP as X.
How Partner Bank Type (BVTYP) is selected by Automatic Payment Program
The system selects the bank with the lowest Partner Bank Type (BVTYP), this means that a bank, which has no BVTYP will be,
selected �rst, then one with AAAA, then BBBB.
Program F110SFB0, form banken_partner_lesen.
...
sort xbank by bvtyp banks bankl bankn.
Due to the system design, the bank data is not company code speci�c. This means that in case of automatic payment, the bank
is determined from all banks, which are in the vendor master. The banks are sorted by partner bank type, bank country key, bank
number and bank control key. Starting from the �rst one, each bank checked. After that, the �rst bank, which has passed the
check, is selected.
Below are two scenarios to explain it in detail:
1. If you have partner bank type (BVTYP) de�ned for all the vendor bank details maintained, then automatic payment
program will sort the vendor bank details based on BVTYP and the vendor bank with BVTYP sorted as �rst will be
selected for vendor payment.
For example, you have the following entries available in vendor master for payment transaction.
 Ctry Bank Key Bank Account Partner bank type (BVTYP)
 DE 0003234134 12345668 0002
 DE 10000001 00001212 0003
 DE 67270003 12345679 0001
The system will sort BVTYP, so it will be in order:
0001
0002
0003
So, in this case BVTYP 0001 will be selected i.e. bank details with bank key 67270003 and Bank account 12345679 is used
for payment.
2. If you have partner bank type (BVTYP) partially de�ned or not de�ned, for vendor bank details maintained then
automatic payment program will select the �rst entry available in vendor master payment transactions for vendor
payment.
For example, you have the following entries available in vendor master for payment transaction.
Ctry Bank Key Bank Account Partner bank type (BVTYP)
 DE 0003234134 12345668
 DE 10000001 00001212
 DE 67270003 12345679 001
Then, bank details with bank key 0003234134 and Bank account 12345668 is used for payment.
If you have mentioned Partner Bank Type (BVTYP) during document posting then the same BVTYP will be picked in automatic
payment program for that document because �elds maintained during document posting like BVTYP, payment method etc. are
https://help.sap.com/docs/disclaimer
4/11/2024
60This is custom documentation. For more information, please visit the SAP Help Portal
selected in payment program since these are speci�cally mentioned.
Using Business Transaction Event 00001810 as an alternate solution
If you need system to pick speci�c bank data during automatic payment program then another solution is to use the Business
Transaction Event 00001810.
In Release 4.0A, process interface 00001810 has taken the place of the customer exit. This interface provides more bank
selection options. Two tables with house banks and business partner bank details permitted for the standard view are
transferred to one of the function modules called in this process in addition to payment information (payment method,
currency, amount). You can mark any entries in these tables that are not yet required. The standard bank selection will then only
use those entries that were not marked. You can make a de�nition explicitly (leave only one permitted bank in each table),
de�ne only one of both banks, restrict the selection in another way. This allows you to take advantage of the following functions
that cannot be shown in standard Customizing.
Select business partner bank details depending on currency
Select house bank depending on the size of the payment amount
Default proportional distribution of the entire payment amount to various banks. Further information on open interfaces
(Business Transaction Events) can be found in Open Interfaces in Financial Accounting (Open FI).
If you want help with the BTE, you have to contact with a consulting department.
As it is written in documentation for this BTE: "The purpose of this interface is to provide a way of individually determining which
of its own bank details and which Partner Bank Details should be used for a payment."
Related Content
Related SAP Notes/KBAs
Insert links to any related notes/KBAsthat support your topic or are related. Please hyperlink ONLY Note or KBA number.
Example:
SAP KBA 3273670 - Automatic Payment Program - Transaction F110 overview / how-to scenarios
SAP KBA 2983466 - Incorrect Partner Bank Type (BVTYP) is selected by Automatic Payment Program
SAP KBA 2787843 - Partner bank selection in F110
SAP Note 2648612 - F110/BTE1820: Enhancement of interface with invoice reference and partner bank type
Error FZ506 'No valid payment method found' in F110 payment proposal
Overview
You perform payment proposal run in F110, and the error FZ506 'No valid payment method found' occurs. The selected open line
items are with exception status (in red), so the payment run cannot be continued.
Solution
The error normally occurs due to missing customizing, please check below :-
https://help.sap.com/docs/disclaimer
https://me.sap.com/notes/3273670
https://me.sap.com/notes/2983466
https://me.sap.com/notes/2787843
https://me.sap.com/notes/2648612
4/11/2024
61This is custom documentation. For more information, please visit the SAP Help Portal
The customizing for the Payment Method/House Bank which used in the payment proposal run, please check FBZP
In FBZP, if you have set below �ags as ON in payment method/country, then you should do the related de�nition in the
vendor/customer master data accordingly
.-Street, P.O. box or P.O. box pst code
-Bank details
Check all payment method settings in FBZP
 - Payment method/country
 - Payment method company code
If you still cannot �nd the reason, please refer to below to �nd further useful information
 1. Delete payment proposal.
 2. go to tab 'Additional log' and set below �ags as ON
 - due date check
 - payment method selection in all cases
 - Line items of the payment documents
 3. execute payment proposal again, and then click 'display proposal log' button, you might see the detail reason for the
error FZ506.
Related SAP Notes/KBAs
SAP Note 10770 Automatic payment program
SAP Note 86578 Guidelines for F110 Payment Program (W/Check mgmt)
General procedures and Tables in Automatic paymnt run
Purpose
We will introduce the general tables which are involved in the automatic payment program.
Overview
The automatic payment program is capable of processing both outgoing and incoming payments. It can process in both
Accounts Receivable and Accounts Payable.
Tables
REGUV : Control records for the payment program
REGUS : Accounts blocked by payment proposal
REGUH : Settlement data from payment program
REGUP : Processed items from payment program
https://help.sap.com/docs/disclaimer
https://me.sap.com/notes/10770/E
https://me.sap.com/notes/86578/E
4/11/2024
62This is custom documentation. For more information, please visit the SAP Help Portal
REGUT : TemSe - Administration Data
Step 1. Enter parameters for payment run
After saving the parameters, Table REGUV will be updated with one entry.If you want to know detail information for the proposal
run, you should tick the �ags of 'Due date check", 'Payment method selection in all cases', and 'Line items of the payment
documents', This will bring you clue and information if there are line items with exceptions in the payment proposal (Red
Status).
Step 2. Execute proposal run
After executing proposal run, new entries are created for table REGUS, REGUH,REGUP.And in the same time REGUV-XVORE
(Indicator: Proposal Run Carried Out?) is updated with X.
Through SE16 table REGUS, If you �ll the relevant Account, you can check whether this Account is locked in some payment
https://help.sap.com/docs/disclaimer
4/11/2024
63This is custom documentation. For more information, please visit the SAP Help Portal
proposal run. (Refer to below picture)
Step 3. Execute payment run
If there is no problem in the proposal run phase, you can perform payment run. After executing payment run, new entries are
created for table REGUH,REGUP. And the entry in table REGUS is deleted, in the same time REGUV-XECHT(Indicator:
Production Run Carried Out?) is updated with X . 
※ Before executing printing run, please ensure the number in 'generated' is equal to the number in 'completed' 
Step 3. Execute printing run
https://help.sap.com/docs/disclaimer
4/11/2024
64This is custom documentation. For more information, please visit the SAP Help Portal
After executing printing run, entries will be created for table REGUT. The information such as 'code page', 'program name' ,
'format' can be found in this table.
Related SAP Notes/KBAs
SAP KBA 2933686 - Creation of payment media for payments from �nancial accounting: overview of possible alternatives
SAP KBA 2230933 - F110: Deadlocks in payment program
SAP KBA 2116298 - F110 - Documents contained in a bank �le not posted
SAP Note 1922823 - F110, F111 - schedule payment medium immediately with validation
SAP KBA 1896498 - F110: Error BFIBL02167
Authorization Check in F110
Purpose
Here generally explain the authorization check and the authorization objects used in F110.
General information
From T-code: F110 menu: Environment-> Authorizations. you can found the activities used in this payment program.
Authorization Objects used
 1. F_REGU_BUK
 Using this authorization object, you determine which activities are allowed with payment program for which Company Code.
2. F_REGU_KOA
 Using this authorization object, you determine which activities are allowed with the payment program for which Account Types
(D for Customer, K for Vendor ...).
Others
https://help.sap.com/docs/disclaimer
https://me.sap.com/notes/2933686
https://me.sap.com/notes/2230933
https://me.sap.com/notes/2116298
https://me.sap.com/notes/1922823
https://me.sap.com/notes/1896498
4/11/2024
65This is custom documentation. For more information, please visit the SAP Help Portal
You can use T-code: ST01 to �nd which authozation objects are used, and which activities are needed for your operation. (Trace
Components: set �ag Authorization Check as ON)
<<Sample only >>
While delete payment data, below authorization objects and activities (24) are needed, it can be found in the trace log as below.
Related Content
authority-check 
Related SAP Notes/KBAs
SAP KBA 2381712 - Pro�t center wise restriction in F110
SAP KBA 2245725 - Authorization object F_LFA1_GRP is not checked in F110
SAP KBA 2162637 - Restriction of display or giving display-only authorization of Proposal/Payment in F110
Reorganization in F110
Purpose
Explain brie�y about the function of 'reorganization' in F110.
Overview
The function 'Reorganization' for payment runs,delete the administration data and entries of payment runs which are no longer
needed. Entries in tbles REGU* can be deleted. Once entries are deleted, they cannot be uploaded again
・ Delete the payment run parameters
・ Delete the payment run data and payment proposal data (tables REGUH, REGUP, REGUV) as well as the job logs belonging to
the payment runs. The table deletion depends of the selection
 that you made.
・ Delete DME data, which has been created for the selected payment runs (This is only done if you switch on the button 'DME
management - delete admin. data')
When you call transaction F110 > Payment run > Reorganization (report SAPF110R), the system asks for the payment runs you
want to select.
The system will delete all existing payment runs up to and including the speci�ed 'To Date'. Any newer payment runs which are
after this date will not be selected.
When you reorganize a payment run, a job will be created in SM37. You can �nd the person who run the report SAPF110R if the
job was not deleted. The job will have a R at the end. 
(Sample: Job name F110-20090303-XHEN1-R)
Authorization needed
 The person needs to have authorization F_REGU_BUK (activity 14 and 24) to do the reorganization.
https://help.sap.com/docs/disclaimer
https://me.sap.com/notes/2381712
https://me.sap.com/notes/2245725
https://me.sap.com/notes/2162637
4/11/2024
66This is custom documentation. For more information, please visitthe SAP Help Portal
 Related SAP Notes/KBAs
SAP Note 574350: F110: Reorganization of payment data
Difference Between FBZP and F11CU
Purpose
Explain the differences between FBZP and F11C t-codes
Overview
FBZP - is the con�guration for F110 automatic Payment Program
F11CU - is the con�guration for Treasury payment from F111 - is for Payment Request.
Both t-codes have the purpose of maintaining the payment program con�guration, although they share some similarities they
also have some differences.
Difference F11CU and FBZP
Question (1)
If con�gurations are done in F11CU it gets automatically updated in FBZP and vice versa. So what is the purpose two different t-
codes?
 answer: They are similar but not the same. Some things will get update automatically in FBZP, like con�guration of house banks
and banking determination.The t-codes exists separately, so the logical con�gurations for F110 and F111 stays modular.
Question (2)
If you have a scenario where you don't process anything in F110 and require only F111. In that case why con�g should be required
in FBZP?
answer: There is the possibility to use FBZP for house banking con�guration. But if in that scenario you don't have the need to
make F110 runs, attain to maintain F111 con�g, using only F11CU and also the other way around if only use F110 runs, use only
FBZP to con�gure the payments.
Display long account number RFZALI20
Purpose
For some countries the �eld Reference Details (BKREF) is used to store a part of an account number longer than 18 positions
and you can use the Business Transaction Events (BTE) 3070 and 3080 to customise the conversion of long account number
and display it in RFZALI20.
Overview
Banks of certain countries use bank account numbers with more than 18 characters. You split the account number using
Reference (BKREF) in the master data, beside of the �eld account number. In report RFZALI20, the account number is not
displayed completely.
https://help.sap.com/docs/disclaimer
https://launchpad.support.sap.com/#/notes/574350
4/11/2024
67This is custom documentation. For more information, please visit the SAP Help Portal
In the transaction FIBF under "Settings -> P/S Modules -> ...of a customer" add the following 2 entries:
 
Event 00003070
Project <your project name>
Country XX
Application <empty>
Function Module FBKK_3070_ACC_AND_REF
 
Event 00003080
Project <your project name>
Country XX
Application <empty>
Function Module FBKK_3080_ACC_AND_REF
https://help.sap.com/docs/disclaimer
4/11/2024
68This is custom documentation. For more information, please visit the SAP Help Portal
 
The project (and project name) can be maintained using the transaction SM31 and the table TBE24.
 
Then the long account number will be displayed completely.
Related SAP Notes/KBAs
SAP Note 1037617: Customisable conversion of long account number
How to avoid error FZ331 during payment for tax jurisdiction country
Overview 
Now it is trying to pay to a vendor. Following pre-requisition existed:
- The company code has tax jurisdiction code functionality enabled.
- There are cash discounts applicable to the vendor. 
- There are taxes applicable to the vendor.
However, cash discounts are only applied to the net amount excluding taxes. If try to put tax category as '*' for the cash
discount account, the payment proposal results in error FZ331 - "Account & & for cash discounts must not have a tax code".
Explanation & Solution
https://help.sap.com/docs/disclaimer
https://service.sap.com/sap/support/notes/1037617
4/11/2024
69This is custom documentation. For more information, please visit the SAP Help Portal
Please review the Program F110SFA0_ABZUEGE_BUCHEN / FORM ABZUEGE_BUCHEN.
There are tow places where can raise the error FZ331. Let's review and try to �nd the solution to avoid the error.
1.
------------------------------------------------------------
IF TTXD-KALSM NE SPACE
 AND ld_disc_mwskz NE SPACE.
 IF skb1-xmwno EQ 'X' AND T001-XSKFN EQ 'X'. "N1689051
 " tax code is not a required �eld AND
 " discount base amount is the net value
 CLEAR: ld_disc_mwskz.
 ELSE.
 MESSAGE S331 WITH ld_disc_saknr SKB1-BUKRS.
 RAISE FEHLER.
 ENDIF.
ENDIF.
------------------------------------------------------------
2.
------------------------------------------------------------
IF ld_disc_mwskz NE SPACE
 AND ABZTAB-MWSKZ NE SPACE.
 IF T001-XSKFN NE SPACE.
 MESSAGE S331 WITH ld_disc_saknr SKB1-BUKRS.
 RAISE FEHLER.
 ENDIF.
ENDIF.
------------------------------------------------------------
According to above programs, the solution following is able to prevent the error:
Solution 1:
The source code 1, you must set [skb1-xmwno EQ 'X' AND T001-XSKFN EQ 'X'], the error will not raised.
SKB1-XMWNO: "Posting without tax code" in FS00, you should set the indicator.
https://help.sap.com/docs/disclaimer
4/11/2024
70This is custom documentation. For more information, please visit the SAP Help Portal
T001-XSKFN: "Discount base amount is the net value" in OBY6, you should set the indicator.
 
But if you set T001-XSKFN as 'X', in source code 2, you must meet the condition [ld_disc_mwskz NE SPACE AND ABZTAB-
MWSKZ NE SPACE.].
ld_disc_mwskz is the tax category of cash discount account master data, you must set it empty.
Basically, for tax jurisdiction code countries there is no tax calculation for the clearing process (f110, fb05, etc.) in place. You
have to remove the tax category from the gl discount account to get it to work.
Message FZ361 occurs in the T-CD F110
https://help.sap.com/docs/disclaimer
4/11/2024
71This is custom documentation. For more information, please visit the SAP Help Portal
You encountered the message FZ361 when you process Transaction F110 and you want to know why and how to resolve this
problem.
The message is correct once the account is being used by other user. The same account is being used in another process then
system blocks the account to avoid future problems with accounts and postings.
If another customer has blocked the account, by FB60 or any other like this. Or if another payment run executes the same
program point for the same account, then the error FZ361 occurs.
In transaction SM12 you can see all entries in lock table. The lock table on lock server contains locking by ENQUEUE. There you
can see which user is blocking the account and then contact the user to ask him �nish the his process.
Update termination in Payment programs (F110 and F111)
Purpose
The purpose of this page is to help you to identify and proceed when there are update terminations in the payment program. 
Overview
This wiki will help you to identify, handle and audit gaps in documents when an update termination occurs in your system.
It contains valuable information in order to help you to to avoid this issue in your system.
How the payment program post the payment documents?
You should note that the system posts payment documents asynchronously and that the payment program generally �nishes
its run before all the payment documents have been posted. To use the indicator "Payment Document Validation" make sure
you have the note 1922823 applied in your system. This indicator will make sure only documents posted will be created in
payment medium.
How to identify update termination in payment program?
This is stated in the difference between the orders generated and completed (posted) as per example:
Parameters have been entered
Payment proposal has been created
Payment run has been carried out
Posting orders: 51 generated, 50 completed
https://help.sap.com/docs/disclaimer
4/11/2024
72This is custom documentation. For more information, please visit the SAP Help Portal
When this happens, you should check transaction SM13 for update Termination. 
What can be done after check that there are update termination?
Go to transaction SM13 andpost the missing documents.
Always be sure to post the documents missing because of the update termination before the next payment run, as this will
avoid the payment program to create two different payment documents for the same invoice.
After you have analyzed and checked the update termination, you can delete this record from transaction SM13.
In this case, an entry in transaction SM13 is created for every document. Check the user that ran this payment and the time it
was ran and go to SM13, check if there are any signs of an update termination in the payment.
How to avoid update termination?
To avoid including a not paid invoice in RFFO*, you should always select the �ag "Payment doc.validation" on running your RFFO*
report.
Please refer to 1713825 - How to activate the payment document validation.
https://help.sap.com/docs/disclaimer
https://service.sap.com/sap/support/notes/1713825
4/11/2024
73This is custom documentation. For more information, please visit the SAP Help Portal
If you select this parameter, the document will only be included in the bank �le if the payment document has been posted
correctly.
Therefore, we would recommend you to save it in all your variants to void future errors. See SAP note 86578 for further info.
In order to eliminate such a problem in future you should in transaction F110:
1) Execute payment proposal
2) Execute payment run (button 'Payment Run') WITHOUT setting the checkbox 'Create payment medium'.
3) Only when the whole payment run is �nished create a payment medium in a separate step.
https://help.sap.com/docs/disclaimer
https://service.sap.com/sap/support/notes/86578
4/11/2024
74This is custom documentation. For more information, please visit the SAP Help Portal
If you create a payment run with option 'Create payment medium' in one job the update records for the FI documents were send
to the update system and the payment medium is created.
However, it’s recommended to execute the payment program in two steps:
1) Create the FI documents
2) Create the payment medium
If you prefer to execute the payment program in one step than you should reconsider if you set �ag 'Payment document
validation' in the print program.
This �ag was implemented to be sure that no FI documents are reversed when creating a payment medium (in a second step). If
you create it in one step you can exclude that someone has reversed the FI documents.
Please consider the suggestions provided in SAP note 86578, especially the use of the 'Payment document validation'
parameter, to avoid future difficulties.
Also check the SAP note 545340, especially solution part 4.
How to document gaps for system auditors?
You should document this gap in the number assignment using report RFBNUM00 for audit purposes. The documentation for
this report is available through SE38.
You can use report RFVBER00 and RFBNUM00 to document gaps for your system auditors.
Related Content
Related Documents
Payment program Wiki
Related Notes
https://help.sap.com/docs/disclaimer
https://service.sap.com/sap/support/notes/86578
https://service.sap.com/sap/support/notes/545340
http://wiki.sdn.sap.com/wiki/x/5ck
4/11/2024
75This is custom documentation. For more information, please visit the SAP Help Portal
SAP Note 86578 - Guidelines for F110 Payment Program (W/Check mgmt)
SAP Note 545340 - FAQ: Payment run F110
SAP Note 1713825 - How to activate the payment document validation
SAP Note 1922823 - F110, F111 - schedule payment medium immediately with validation
SAP KBA 2116298 - F110 - Documents contained in a bank �le not posted
SAP Note 2783609 - PMW: Activation of payment document validation
SAP KBA 2230933 - F110: Deadlocks in payment program
SAP KBA 3273670 - Automatic Payment Program - Transaction F110 overview / how-to scenarios
DME Creation-Payment Medium
DME Creation-Payment Medium
VIA CLASSIC PROGRAM
VIA PMW
VIA CLASSIC PROGRAM
VIA CLASSIC PROGRAM
Bank Charge in RFFOJP_T
Classic Print Program: General Information
Classic Program: Output Medium FZ205 Error
Classic Program for outgoing IDOC creation RFF0EDI1-2
Classic Program - RFFOUS_C
Classic Programs: Codepage
Dump with GETWA_NOT_ASSIGNED_RANGE in RFFO* report
Payment Advice, Accompanying sheet creation via classic print program
Payment from HR
Reprinting Checks for Payment Documents Through Classic Payment Medium Program (RFFOUS_C)
Bank Charge in RFFOJP_T
Purpose
This Expert content introduces some general information about bank charge generated in F110 printing run program RFFOJP_T.
Overview
You use RFFOJP_T to do payment printing run for JP company code, at this stage FI document will be created. You want to know
under what situation bank charge will be posted.
Answer
https://help.sap.com/docs/disclaimer
https://service.sap.com/sap/support/notes/86578
https://service.sap.com/sap/support/notes/545340
https://service.sap.com/sap/support/notes/1713825
http://service.sap.com/sap/support/notes/1922823
https://me.sap.com/notes/2116298
http://me.sap.com/notes/2783609
https://me.sap.com/notes/2230933
https://me.sap.com/notes/3273670
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880829.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880828.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878810.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880771.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880772.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880748.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880752.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880773.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878263.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880770.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880750.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878268.html
4/11/2024
76This is custom documentation. For more information, please visit the SAP Help Portal
'Instruction key' controls whether bank charge will be posted for RFFOJP_T, please refer to the F1 help of Instruction Key in
vendor master data -> tab payment transactions (FK03)
1. If the instruction key is maintained in the master record, then this instruction key is used. (FK03)
2. If no instruction key exists in the vendor master record, then the default instruction key de�ned for the house bank is
used (FI12). 
If instruction key 02 is used ,the bank charge will be created. If the instruction key is 01, bank charge is not
calculated/created. Please refer to the information in OB47 -> F1 help of 'Cost allocation key'.
 " In Japan the cost allocation key is used for both domestic transfers abroad by DME with the following values:
 1 Charges payable by payer
 2 Charges payable by payee "
Related SAP Notes/KBAs
2923050 - FAQ: Adjustment of Payment Medium Format JP_ZENGINKYO_XML
2894733 - Bank subaccount determination after bank charge posted for RFFOJP_T
2567350 - [Legal change] Japan ZENGINKYO payment medium XML format enablement - XML generation
2758836 - Japan: Documentation on Payment Medium Programs for ZENGINKYO Domestic Transfer
Classic Print Program: General Information
General information
Formats
Available Payment medium formats are listed
SAP Note 101440 - Payment medium formats
There are RFFO* reports which have been made obsolete and they will not be supported further by SAP after 1st Jan, 2013. New
DMEE trees corresponding to these reports are fully functional and legally compliant. The note 1704031 shows the list of the
obsolete reports.
Relevant SAP Notes:
1704031 - FI: Replacement of the RFFO* reports with the DMEE trees
967731 - Recommendation: Switzerland RFFOCH_U / RFFOCH_P
Printout/DME
Data Medium/DME
Store one (or more) variant for your report RFFO* in the transaction F110, tab Printout/data medium.
https://help.sap.com/docs/disclaimerhttps://me.sap.com/notes/2923050
https://me.sap.com/notes/2894733/E
https://me.sap.com/notes/2567350
https://me.sap.com/notes/2758836
https://launchpad.support.sap.com/#/notes/101440/E
https://launchpad.support.sap.com/#/notes/1704031/E
https://launchpad.support.sap.com/#/notes/1704031/E
https://launchpad.support.sap.com/#/notes/967731/E
4/11/2024
77This is custom documentation. For more information, please visit the SAP Help Portal
Known Issues
 Display DME
As it is mentioned in note 855841, Transaction AL11 is not suitable for checking the correctness of the data medium, as the
transaction expects the data in a certain format (UTF-8). Do not use this transaction to check the contents of the data medium.
Display the content of the DME using transaction FDTA.
Relevant SAP note:
855841 - Payment medium in a Unicode system
 File name
If the �le name is not to be speci�ed by parameter, then it is generated by the program. If then consists of the disk format, date
and time of creation as well as a consecutive number so that the �le name in the �le system is unique.
If the �le name is speci�ed by the user, then the consecutive number is likewise added for each program run. From an
organizational point of view, however, you should make sure that already existing �les are not overwritten.
Relevant SAP note:
1460101 - Same �le name or alternative �le name for RFFO* �les
Classic Program - RFFOUS_C
Checks
RFFOUS_C
This program prints prenumbered check forms or non-prenumbered checks whose number is to be assigned from a prede�ned
number range, and links the check number to SAP payment document number or the check number to the settlement result.
Check management – Content of the check register (PAYR) 
In addition to the checks, you can print their payment advice notes and payment summaries in one program run.
- Check number (with company, house bank and account)
- data of the check (payment date, currency, amount)
- address of payee
- status (printed or written manually, extracted, cashed, voided, reversed, replaced, archived) Application DATA
- link to the payee (vendor, customer or personnel number)
- link to the document (FI payment document, HR payroll result)
Check management – transaction overview
Add check information (RFFOUS_C, FBZ4, FBZ5, FCH5)
https://help.sap.com/docs/disclaimer
https://launchpad.support.sap.com/#/notes/855841/E
https://launchpad.support.sap.com/#/notes/855841/E
https://launchpad.support.sap.com/#/notes/1460101/E
4/11/2024
78This is custom documentation. For more information, please visit the SAP Help Portal
Find check (FCH1)
Display check (FCH1, FCH2, FB02, FB03, FBL1, FBL3, FBL5)
Where-used (FCH1)
Check register (FCHN)
Check extract (FCHX, positive payment �le)
Check encashment (RFEBCK00, manually FCHR, FF67 via bank reference)
Archiving (FCAA, FCAR, SARA object FI_SCHECK)
Most of it can be found in AP/AR menu: Environment Check information
After check print – checks not ok -> restart RFFOUS_C (FBZ5/FCH7 print/reprint)
SAP KBA 2198181 - Page over�ow error in check printing
SAP Note 2993014 - Check printing with PMW versus RFFOUS_C
Classic Program for outgoing IDOC creation RFF0EDI1-2
General information
This program generates the Intermediate Documents (IDoc) for payment orders made via EDI -> PAYEXT Idocs. PAYEXT Idoc
goes to the bank
The IDOC format uses Electronic Data Interchange (EDI) to create SAP intermediate documents for payment orders. From a
technical perspective, the format generates payment media by calling program RFFOEDI1.
In addition to the payment media, you can output the related advice notes, EDI accompanying sheets and payment summaries
in a single program run.
Customizing:
TA FI12:
Enter relevant Company Code and House Bank, go to "EDI partner pro�les "and click button "EDI comp. pyt mthds". This is
needed for letting program RFFOEDI generate IDocs.
 Typical errors/Known issues:
 F0073: No records selected
The RFFOEDI1 program will only select records from the REGUH table if the �eld REGUH-EDIBN = X. Check the value of the �eld
"REGUH-EDIBN". In case this is blank then no records are selected and hence you get this error.
SAP Note 4332 RFFOxxxy - Message F0073 (No records selected)
 B1090
Consulting note 1632185 - Idoc is not getting generated by RFFOEDI1 - Error B1090
"..If the IDOC should be generated in the proposal run for testing purposes, an entry with the TEST �ag set should be included
too. .."
This �ag is equivalent to �ag REGUH-XVORL, payment proposal or real run.
If you want to create REMADV for the vendor for real run, you have to change it in WE20.
https://help.sap.com/docs/disclaimer
https://launchpad.support.sap.com/#/notes/2198181/E
https://me.sap.com/notes/2993014
https://launchpad.support.sap.com/#/notes/4332/E
https://launchpad.support.sap.com/#/notes/1632185/E
4/11/2024
79This is custom documentation. For more information, please visit the SAP Help Portal
SAP Note 2229010 - Error message E0336 - EDI: Partner pro�le outbound logical message not available
Related SAP Notes/KBAs:
SAP Note 485737 RFFOEDI1: When is a payment advice note created?
SAP Note 1708911 RFFOEDI2 : Report RFFOEDI2 is changing the status for PAYEXT (REGUH-EDIBN),
1248868 - User exits for PEXR2003/PEXR2002 IDoc generation
1404594 - RFFOEDI1: 'Number of invoice details' parameter
REMADV Idoc
The REMADV advice Idoc is just the information for the vendors, that they receive a payment 
The REMADV advices are created along the payment �le creation by any RFFO* report (�ag 'payment advices') or report
RFFOAVIS_FPAYM for PMW format. 
No REMADV advice has been created, if status REGUH-EDIAV = E for error
Classic Program: Output Medium FZ205 Error
Output medium
Output to �le system
To store the �le in the �le system is useful, when the data should not be accessed using an SAP transaction anymore, but sent
away for further processing (e.g. an external program, to be transferred the data medium to the bank).
If the output medium 'File-System' has been chosen in the variant of the report RFFO*, that means output medium '0'.
When using the �le system, a �le is accessible only using the same instance (server). In your example the job seems to run on
another instance (maybe database server), whereby you are logged to another instance (maybe application server).
The DME maintenance data are stored inside of the SAP system, so you can see that a �le was created, but you cannot access
it, because the �le was stored in �le system of a different server.
Then if you restart the DME �le creation manually, it runs on the same instance and that is why you can display the �le system
data.
When you want to access it manually afterwards, please use the TEMSE to store the DME �les, as there is no limitation in case
of different instances. The data are then accessible from any instance (server).
You can switch the output from �le system to the TEMSE by deactivating the �ag 'Output to �le system' in the corresponding
selection variant of the program payment medium program RFFO*.
Relevant SAP notes:
948785 Consulting: Payment medium on application server
155586 DME contents belongs to another payment run
https://help.sap.com/docs/disclaimer
https://launchpad.support.sap.com/#/notes/2229010/E
https://launchpad.support.sap.com/#/notes/485737/E
https://launchpad.support.sap.com/#/notes/1708911/E
https://launchpad.support.sap.com/#/notes/1248868/E
https://launchpad.support.sap.com/#/notes/1404594/E
https://launchpad.support.sap.com/#/notes/948785/E
https://launchpad.support.sap.com/#/notes/155586/E
4/11/2024
80This is custom documentation. For more information, please visit the SAP Help Portal
25709 FDTA: No data records found FZ208
15960 Data medium exchange: where is the DME �le?
Output into TEMSE
In order to use the TemSe you have to use the output medium '1'.
If required, the �le created can be stored within the SAP System (store in the TemSe and notin the �le system),thus protecting
it from unauthorized external access. You can download the �le into the user's �le system via the DME manager.
The name of the �le to be created during the download can be determined when running the payment medium program: the
contents of the �le name parameter are stored in the management data and defaulted when running the download.
Relevant SAP Notes:
948785 - Consulting: Payment medium on application server
1786620 - Error FZ205 appears in the transaction FDTA
Payment Document Validation
Check SAP Note 545340, question/answer 4.
545340 - FAQ: Payment run F110
Classic Programs: Codepage
Codepage
The �le can be generated either in the TemSe or on the application server.
The code page on which the �le has been created is saved in the table REGUT, �eld CODEPAGE.
If the �le is saved on the application server, the code page depends on the customizing settings.
If the �le is saved in the TEMSE, it is always in the code page of the ERP system and converted to the target code page during
the download via transaction FDTA. The target code page is made dependent on the user parameter DCP in the case of RFFO*
reports.
The DCP parameter works as following:
DCP = "NONE" : no conversion, �le will be downloaded in System codepage 4102, this is unicode codepage, the bank will not
accept this.
DCP = "Parameter not maintained": conversion to codepage 1100
DCP = "nnnn" -> conversion to codepage nnnn
Relevant SAP notes:
972197 - Background information on code page/encoding of �le
1365764 - Codepage of DME �le
970892 - Unicode: Specifying the codepage in RFFO* programs
2199778 - FDTA: RFFO* �le in incorrect coding/code page after download from application server
972197 - Background information on code page/encoding of �le
https://help.sap.com/docs/disclaimer
https://launchpad.support.sap.com/#/notes/25709/E
https://launchpad.support.sap.com/#/notes/15960/E
https://launchpad.support.sap.com/#/notes/948785/E
https://launchpad.support.sap.com/#/notes/1786620/E
https://launchpad.support.sap.com/#/notes/545340/E
https://launchpad.support.sap.com/#/notes/545340/E
https://launchpad.support.sap.com/#/notes/972197/E
https://launchpad.support.sap.com/#/notes/1365764/E
https://launchpad.support.sap.com/#/notes/970892/E
https://launchpad.support.sap.com/#/notes/2199778/E
https://launchpad.support.sap.com/#/notes/972197/E
4/11/2024
81This is custom documentation. For more information, please visit the SAP Help Portal
1365764 - Codepage of DME �le
716454 - FDTA: Code page of downloaded �le 
Dump with GETWA_NOT_ASSIGNED_RANGE in RFFO* report
Overview
When you execute a report for creating payment mediums (RFFO*), a dump occurs with the exception
GETWA_NOT_ASSIGNED_RANGE.
Reason
The dump may be caused by incorrect length of the �elds of the sorting variant , especially the �eld you added. 
Solution
 
Please use transaction O7S1/O7S2 to check the �eld length for sorting variant , and compare with the value of the �eld length
in SE11 table REGUH/REGUP. If there is any difference, please change the value in O7S1/O7S2 according to the one in the table
REGUH/REGUP. 
 
Payment Advice, Accompanying sheet creation via classic print program
Creation of Payment advice
If data medium exchange (DME) is required (*), the default settings in customizing (payment advice if form is full) are
irrelevant. The maximum number of the notes to payee lines max. Number depends on the DME format of the country
(documents on this at the bank). In most cases, it is therefore hard-coded but in several cases can also be in�uenced by
program parameters.
Relevant SAP Note
30171 - RFFO* - When are payment advice notes (not) printed?
As an option you could add a second variant for the print program RFFO*, the �rst one with only Data Medium Exchange and
Print Payment summary �agged on and the second one with Print payment advice notes �agged on.
Report RFFOAVIS - the program creates noti�cations for customers/vendors that their receivables and payables balance to
zero (Zero Balance Notice).
Relevant SAP Note
10206 - Print payment advice: RFFOAVIS selects nothing
REMADV Idoc
If you want to create REMADV Idoc for payment advices: �ag in vendor master data: 'Advice via EDI'. Then REGUH-EDIAV is set
to 'X' by payment program F110.
The REMADV advice Idoc is just the information for the vendors, that they receive a payment 
The REMADV advices are created along the payment �le creation by any RFFO* report (�ag 'payment advices') or report
RFFOAVIS_FPAYM for PMW format. 
No REMADV advice has been created, if status REGUH-EDIAV = E for error
https://help.sap.com/docs/disclaimer
https://launchpad.support.sap.com/#/notes/1365764/E
https://launchpad.support.sap.com/#/notes/716454/E
https://launchpad.support.sap.com/#/notes/30171/E
https://launchpad.support.sap.com/#/notes/10206/E
4/11/2024
82This is custom documentation. For more information, please visit the SAP Help Portal
Accompanying sheet
Relevant SAP notes:
1947527 - Accompanying sheet for a DMEE format
2028635 - SEPA: Accompanying sheet with reference number per PmtInf group
1776812 - SEPA �le with hash value/additional function module
1948973 - Accompanying sheet with more �elds (hash value) in exit 41
1936271 - PMW: Hash value is incorrect, hash value of XML �le has errors.
Payment from HR
Payment from HR
The preliminary program RPRDTAD0 �lls FI tables REGUH and REGUP for the DME (bank �le).
The HR-transaction PC00_M99_FPAYM creates the payment �le for personal payments.
Known issues:
 If the data medium is not created, please check the tables REGUH and REGUP (important: ID and date of the payment
run). 
If the tables are empty, in that case the issue is in the report RPRDTAD0. Please create an incident on the component
PY-XX-DME .
If the tables are �lled and you get the error BFIBL02159, please check variant of report SAPFPAYM via the transaction
SE38.
Relevant SAP note 1941183
- Is the button “Proposal run only” �agged in the variant for report SAPFPAYM? If so, remove it.
- Are the dynamic selection �lled? If yes, please compare contents in the table REGUH/REGUP and the �eld in the selection (for
example payment method).
- Dynamic selection with value date – please delete, for HR-payment no relevant.
Relevant SAP notes:
303205 - Authorization for payment media
307758 - Payment medium authorization for personnel payments
Reprinting Checks for Payment Documents Through Classic Payment Medium
Program (RFFOUS_C)
Purpose
This Expert content explains how to reprint checks through Classic Payment Medium Program RFFOUS_C for the payment
documents created through Automatic Payment Run (F110) or Manual Payment (F-58).
Overview
If you have printed the checks through Automatic Payment Program or through Manual Payment and due to some reason, you
need to re-print the checks then this WIKI will help you to re-print the checks.
https://help.sap.com/docs/disclaimer
https://launchpad.support.sap.com/#/notes/1947527/E
https://launchpad.support.sap.com/#/notes/2028635/E
https://launchpad.support.sap.com/#/notes/1776812/E
https://launchpad.support.sap.com/#/notes/1948973/E
https://launchpad.support.sap.com/#/notes/1936271/E
https://launchpad.support.sap.com/#/notes/1941183/E
https://launchpad.support.sap.com/#/notes/303205/E
https://launchpad.support.sap.com/#/notes/307758/E
4/11/2024
83This is custom documentation. For more information, please visit the SAP Help Portal
How to Reprint Check
You have printed checks for your payment document and due to some reason for e.g.
Page over�ow
Update termination where payment document number is generated but payment document does not exist in table, and
check is printed for that document
Incorrect Check, etc.
You would like to reprint the checks.
Suppose you have printed two checks 600002 and 600003 for Payment Documents 4600000073 and 4600000074
respectively. Now you would like to reprint checks for these Payment Documents.
Check Payment Document
6000024600000073
600003 4600000074
1. Go to SE38 and run RFFOUS_C
https://help.sap.com/docs/disclaimer
4/11/2024
84This is custom documentation. For more information, please visit the SAP Help Portal
2. Then provide the parameters
3. Since its reprint, choose the appropriate �eld parameters as below
https://help.sap.com/docs/disclaimer
4/11/2024
85This is custom documentation. For more information, please visit the SAP Help Portal
1. You have to select the checkbox “Void and reprint checks from payment run already printed”. Since you are
reprinting the checks now, you have to void the previous checks.
2. You have to provide the “Void reason code”
There you can select the reason from the pop-up.
4. Then, execute it.
You will get the pop-up to enter the output device. Fill the details here. For e.g. shown in the below screenshot
https://help.sap.com/docs/disclaimer
4/11/2024
86This is custom documentation. For more information, please visit the SAP Help Portal
5. Then your check will be reprinted successfully.
https://help.sap.com/docs/disclaimer
4/11/2024
87This is custom documentation. For more information, please visit the SAP Help Portal
6. You can also see the details in the Check Register (FCHN), as shown below
From above Check Register Report, you can see
Checks
600002
600003
are Voided and new Checks are generated
Check Payment Document
600007 4600000073
600008 4600000074
VIA PMW
VIA PMW
ACH Formats
Checks
Country speci�c formats
Format IDOC
Modifying Standard PMW Formats
Payment Advice Creation
Payment formats supported in S/4 HANA and in ERP
PMW: General Information and DMEE (Data Medium Exchange Engine) or DMEEX (Data Medium Exchange Engine
Extended)
PMW formats: Codepage
PMW formats: Customizing
SEPA and CGI Format Tree
ACH Formats
Purpose
This Expert content will explain more details about the difference between the formats such as PPD, CCD, CTX and others.
https://help.sap.com/docs/disclaimer
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880842.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880776.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880777.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880775.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878619.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880764.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880779.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880730.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880759.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880761.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880760.html
4/11/2024
88This is custom documentation. For more information, please visit the SAP Help Portal
Overview
These abbreviations relate to an 'application' type, and help determine the detail record format. The main goal of this wiki is
explain more details about that.
What are the common applications?
PPD Prearranged Payment and Deposit Entry (Consumer)
This is used for credit transactions such as direct deposit of payroll, pension, dividends, as well as debit transactions such as
payment of utility bills, mortgages, loans and other recurring payments.
CCD Cash Concentration or Disbursement (Corporate)
Can be used to consolidate and sweep cash funds within an entity's controlled accounts, or make/collect payments to/from
other corporate entities. The format and information requirements for PPD and CCD are identical. In addition they each can
support one addendum record.
CTX Corporate Trade Exchange (Corporate)
Supports the transfer of funds (debit or credit) with another entity in which you have an existing trading relationship. This
format supports ANSI ASC X12 payment related information, which can be placed in multiple (up to 9,999) addendum records.
In related content below you can �nd the formats available in SAP PMW. Also, notice that the program RFFOUS_T generates
payment media in ACH format.
Short note
* The CTX format is different than the PPD and CCD.
* You can combine PPD, CCD and CTX batches within the same transmission �le.
Related SAP Notes/KBAs
SAP Note 395679 PMW: Overview of available formats.
Checks
Format CHECK: implemented via events 
SAP Note 2993014 - Check printing with PMW versus RFFOUS_C
SAP Note 2329663 - De�nition of check lot for check printing with PMW or BCM
Country speci�c formats
General notes
2795667 - ISO20022 adoption - global harmonisation & regulation (SEPA in Europe)
https://help.sap.com/docs/disclaimer
https://service.sap.com/sap/support/notes/395679
https://me.sap.com/notes/2993014
https://me.sap.com/notes/2329663
https://me.sap.com/notes/2795667
4/11/2024
89This is custom documentation. For more information, please visit the SAP Help Portal
2682253 - Payment Formats supported in Release S/4HANA 1809 On-Premise
2518834 - Payment Formats available in Release S4/Hana 1709 On-Premise
2253571-Collective information note: CGI_XML_CT, CGI_XML_DD extended with BAdI enhancement
2155263 Collective note for payment format: FR_ETEBAC_VRT-ETR
2159164 Collective note for payment formats: CH_DD, CH_DTA
2163271 Collective note for payment formats: CH_LSV, CH_LSV_PLUS
2165040 Collective note for payment formats: CH_EZAG
2165173 Collective note for payment formats: LUX_VIR2000
2165192 Collective note for payment formats: V3_IZV
2165525 Collective note for payment formats: V3
2165548 Collective note for payment formats: BE_BEPDTA_FOR, BE_PIBDTA_DOM
2165646 Collective note for payment format: FR_ETEBAC_VRT-DOM
2165701 Collective note for payment formats: IE_AIB, IE_BOI, IE_ULSTER
2165706 Collective note for payment formats: HU_GIRO
2165731 Collective note for payment formats: DK_PAYMUL_DOMESTIC
2165743 Collective note for payment format: LM03
2165767 Collective note for payment formats: TS
2165806 Collective note for payment formats: CZ_GEMINI, CZ_GEMINI_F
2168012 Collective note for payment formats: BTL91
2168018 Collective note for payment formats: CLIEOP03
2168052 Collective note for payment formats: PS2
2168056 Collective note for payment formats: PL_ELIXIR-O
2168072 Collective note for payment formats: SE_A_AUTOGIRO
2168074 Collective note for payment formats: SE_BANKGIROT
2168081 Collective note for payment formats: SE_POSTGIROT
2168086 Collective note for payment formats: SE_UTLI_SISU
2168087 Collective note for payment formats: GB_BACS
2168103 Collective note for payment format: FI_LUM2
2168110 Collective note for payment format: FI_XML_CT, FI_XML_CT32
2179939 Collective note for payment format: PL_FICA_ELIXIR-O XX-CSC-PL-FICA
2221365 Collective note for payment formats: LV-FIDAVISTA XX-CSC-LV-FI
SEPA for Italy
1827100 SEPA IN ITALY
2049907 CGI_XML_CT: Italy Speci�c Enhancements in CGI Credit Transfer
2151552 CGI_XML_CT: BADI Implementation for Italy Credit Transfer Format
2152474 CGI CT Italy: How to �ll in CUP/CIG numbers in the CGI_XML_CT tree
2200158 CGI: Italy CBI XML(CGI_XML_CT) format displays CstmrDrctDbtInitn/ BrnchId tag
2223914 CGI: Italy CBI XML(CGI_XML_DD) format displays CstmrDrctDbtInitn/ BrnchId tag
2241311 CGI: CGI_XML_CT country speci�c functionality for ES, IT (CBI) , AT, DK, CN, T
2268123 CGI: CGI_XML_CT(CBI) Italy, Speci�c Enhancement for Credit Transfer
SEPA for Spain
https://help.sap.com/docs/disclaimer
https://me.sap.com/notes/2682253
https://me.sap.com/notes/2518834
https://me.sap.com/notes/2253571
https://me.sap.com/notes/2155263
https://me.sap.com/notes/2159164
https://me.sap.com/notes/2163271
https://me.sap.com/notes/2165040
https://me.sap.com/notes/2165173
https://me.sap.com/notes/2165192
https://me.sap.com/notes/2165525
https://me.sap.com/notes/2165548
https://me.sap.com/notes/2165646
https://me.sap.com/notes/2165701
https://me.sap.com/notes/2165706
https://me.sap.com/notes/2165731
https://me.sap.com/notes/2165743
https://me.sap.com/notes/2165767https://me.sap.com/notes/2165806
https://me.sap.com/notes/2168012
https://me.sap.com/notes/2168018
https://me.sap.com/notes/2168052
https://me.sap.com/notes/2168056
https://me.sap.com/notes/2168072
https://me.sap.com/notes/2168074
https://me.sap.com/notes/2168081
https://me.sap.com/notes/2168086
https://me.sap.com/notes/2168087
https://me.sap.com/notes/2168103
https://me.sap.com/notes/2168110
https://me.sap.com/notes/2179939
https://me.sap.com/notes/2221365
https://me.sap.com/notes/1827100
https://me.sap.com/notes/2049907
https://me.sap.com/notes/2151552
https://me.sap.com/notes/2152474
https://me.sap.com/notes/2200158
https://me.sap.com/notes/2223914
https://me.sap.com/notes/2241311
https://me.sap.com/notes/2268123
4/11/2024
90This is custom documentation. For more information, please visit the SAP Help Portal
1923419 CGI_XML_CT: SEPA changes for Spain
1932850 CGI_XML_CT: SEPA for Spain [VIDEO]
1963806 CGI_XML_CT: SEPA changes for Spain
1988783 CGI_XML_CT: Special characters in DMEE XML Format [VIDEO]
2007449 CGI_XML_CT: Spain Speci�c Additional Requirements
2092528 SEPA transfers in the same day - value date same day of payment run: CGI_XML_CT
2115812 Tag ID (NIF) empty in collective transfers: CGI_XML_CT format Spain.
2195009 CGI_XML_DD: Spain - same bank indicated even if it was not (BIC did not changed
2215552 CGI_XML_CT: DMEE Special characters in address not supported(Spain)
2241311 CGI: CGI_XML_CT country speci�c functionality for ES, IT (CBI) , AT, DK, CN, T
Format IDOC
Format IDOC
Please check SAP Note 2147168 for a implementation with PMW and RFFOEDI1
After the implementation, you can use the new Payment Medium Workbench format IDOC in a payment method (transaction
FBZP). When you do so, note the documentation about the Payment Medium Workbench format IDOC (transaction FBPM).
In Customizing for the payment method, enter the PMW format IDOC. Values speci�ed for format supplement and note
to payee have no impact. You cannot specify a conventional payment medium program in addition.
De�ne the payment method and the house bank not as EDI-capable. To be able to use the PMW format IDOC, you need
to remove any existing corresponding entries in Customizing. Note: From a technical perspective, the format calls
program RFFOEDI2 to ensure that the payments are de�ned as EDI-capable.
Dynamic selections of SAPFPAYM cannot be used. Conversely, you cannot use dynamic selections of RFFOEDI1 because
these are prede�ned by the format implementation.
Unlike with other PMW formats, the format creates the payment advice notes together with the payment media. It is not
necessary to run program RFFOAVIS_FPAYM for the payment methods with the format IDOC.
Modifying Standard PMW Formats
Purpose
The purpose of this Expert content is to show how you can modify standard DME formats using PMW functionality
Overview
The PMW is a �exible tool that provides to the customers the opportunity to modify standards DME formats to meet their
business requirements. These changes can be done directly in DMEE tree or via custom events.
1) Using PMW Events
In transaction OBPM3 you can add events which are Custom Function modules. In the events 06, 21, 31 and 41 you receive the
results of the events 05, 20, 30 and 40 in the table T_FILE_OUTPUT. You can change the contents of the table in the exit.
https://help.sap.com/docs/disclaimer
https://me.sap.com/notes/1923419
https://me.sap.com/notes/1932580
https://me.sap.com/notes/1963806
https://me.sap.com/notes/1988783
https://me.sap.com/notes/2007449
https://me.sap.com/notes/2092528
https://me.sap.com/notes/2115812
https://me.sap.com/notes/2195009
https://me.sap.com/notes/2215552
https://me.sap.com/notes/2241311
https://me.sap.com/notes/2147168/E
4/11/2024
91This is custom documentation. For more information, please visit the SAP Help Portal
The data is in the T_FILE_OUTPUT table in an unstructured form. If you want to access individual �elds, copy the row of the table
to a structure that you take from the standard module of the corresponding event (see transaction OBPM1).
For example, if you want to change a speci�c record, you can use event 31.
2) Using DMEE transaction
If the PMW format is implemented via DMEE tree (DME �ag is set in OBPM1), you can make a Z copy of the standard format via
transaction DMEE and modify the nodes of the Z format copied.
The structures used are FPAYH, FPAYP and FPAYHX, so the �elds of these structures can be used in the nodes.
Related Content
Related Documents
SAP Help - Payment Medium Workbench Overview
Related Notes
SAP Note 965723 : PMW: Use of exits (transaction OBPM3)
PMW formats: Codepage
The DME �le can be generated either in the TemSe or on the application server.
The code page on which the �le has been created is saved in the table REGUT, �eld CODEPAGE.
If the �le is saved on the application server, the code page depends on the customizing settings (transaction OBPM3).
If the �le is saved in the TEMSE (part of the R/3 database), it is always in the code page of the ERP system and converted to the
target code page during the download via transaction FDTA. The target code page is determined from transaction OBPM3 for
PMW payment methods (code page �eld). 
https://help.sap.com/docs/disclaimer
http://help.sap.com/erp2005_ehp_06/helpdata/en/cb/4104aadf2b11d3a550444553540000/content.htm
http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=DISPL_TXT&_NNUM=965723
4/11/2024
92This is custom documentation. For more information, please visit the SAP Help Portal
For more information on codepage check relevant SAP notes:
SAP Note 972197 - Background information on code page/encoding of �le
SAP Note 911190 - PMW: Code page speci�cation when writing and downloading
SAP Note1365764 - Codepage of DME �le
SAP Note 1954679 PMW: Encoding for XML �le/UTF-16/apostrophe/utf-8 in lowercase letters
SAP Note 1972868 Special characters in DMEE/SEPA
SAP KBA 1730272 DME output XML �le in UTF-16 instead of UTF-8 format
SAP Note 1688643 Composite SAP Note: Adjustment to encoding for XML �les
SAP Note 3058340 - Encoding UTF-16 instead of UTF-8 in xml �le
Known Issues
Special Characters
If no special characters should be displayed in the �le, conversion routines can be used in the DMEE tree.
Special characters are deleted without replacement if you excluded the given character in the root node in the tree de�nition of transaction
DMEE and set the checkbox "Exclude/allow de�ned characters" in the conversion routine for the node.
Characters are replaced by one or more characters if you set the checkbox for "Replace national characters" in the node as a conversion
routine.
https://help.sap.com/docs/disclaimer
https://me.sap.com/notes/972197
https://me.sap.com/notes/911190
https://me.sap.com/notes/1365764
https://me.sap.com/notes/1954679
https://me.sap.com/notes/1972868
https://me.sap.com/notes/1730272
https://me.sap.com/notes/1688643
https://me.sap.com/notes/3058340
4/11/2024
93This is custom documentation. For more information, please visit the SAP Help Portal
Alternatively, you can also replace the characters in exit 41 of the PMW. SAP Note 1972868 contains a sample code for this exit .
Relevant SAP Notes:
SAP Note 972868 - Special characters in DMEE/SEPA
SAP Note 1988783 - CGI_XML_CT: Special characters in DMEE XML Format [VIDEO]
SAP Note 1613842 - Apostrophe in DMEE payment �le
PMW formats: Customizing
1. OBPM1
https://help.sap.com/docs/disclaimer
https://me.sap.com/notes/1972868
https://me.sap.com/notes/1972868
https://me.sap.com/notes/1988783
https://me.sap.com/notes/1613842
4/11/2024
94This is custom documentation. For more information, please visit the SAP Help Portal
Payment medium without docs - available Types:
01 File
02 IDoc
03 Obsolete
04 XML
05 XI Proxy
06 FTA
SAP note 921720 - Payment medium: Security and encryption
PMW formats of type FTA (transaction OBPM1):
In the case of PMW �les (transaction FBPM, report SAPFPAFYM), the �le is signed with SSF (Secure Store and Forward) and
encodedwith BASE64 if you select the type FTA in transaction OBPM1 (call module 'SSF_KRN_SIGN_BY_AS', function group
BNK_FTA). This, however, is not encryption.
When switch BNK_SFWS_DDIC_BRM is on, then ʻFTA’ �xed value is available for domain DTTYP_FPM 
Payment medium output divided by level of detail:
Relevant SAP note:
1794408 - PMW: Granularity, denomination, group number, logical �le, sorting
If the report SAPFPAYM is called online and multiple groups exist, a dialog box that allows you to select the group appears.
2. OBPM2
https://help.sap.com/docs/disclaimer
https://me.sap.com/notes/921720
https://me.sap.com/notes/1794408
4/11/2024
95This is custom documentation. For more information, please visit the SAP Help Portal
3. OBPM3
For further info see SAP note
Relevant SAP Notes:
965723 - PMW: use of exits (transaction OBPM3)
1360302 - PMW: Read and change report parameters in the exit
Maximum Number of Payments
1932233 - PMW: Lack of memory in XML, limit number of payments per �le
https://help.sap.com/docs/disclaimer
https://me.sap.com/notes/965723
https://me.sap.com/notes/1360302
https://me.sap.com/notes/1932233
4/11/2024
96This is custom documentation. For more information, please visit the SAP Help Portal
Scheduling of Jobs
2157597 - OBPM3: Scheduling of jobs: Sequential, parallel, SAP values
Create a Variant in SAPFPAYM:
4. OBPM4
https://help.sap.com/docs/disclaimer
https://me.sap.com/notes/2157597
4/11/2024
97This is custom documentation. For more information, please visit the SAP Help Portal
SAP Note 984462 - Report SAPFPAYM/SAPFPAYM_SCHEDULE: Several �les
Schedule the report SAPFPAYM_SCHEDULE, not the report SAPFPAYM. The variants of SAPFPAYM must then be de�ned in
transaction OBPM4.
Background information: The report SAPFPAYM can generate only one payment medium at once. If several payment media
have to be generated, the system issues a dialog box in which you must select which payment medium is to be generated.
The report SAPFPAYM can generate only one payment medium at once.
When scheduling the payment run using transaction F110 Report SAPFPAYM_SCHEDULE is executed, which reads the variants
maintained in OBPM4 and call SAPFPAYM with it.
If you are clicking on the “Print” button in F110 all relevant variants maintained in OBPM4 will be executed. The same is valid for
Programs which have a variant maintained in F110 tab Printout/data medium.
SAP Note 1782685 - OBPM4: Different variants for HR/HCM and FI, determination of parameters in exit.
Output
Output in File System
the created �le to be saved in the �le system of the application server and not in the TemSe in the SAP System (SAP Note
1104567).
Output in the TemSe
If required, the �le created can be held within the SAP System (saved in TemSe, not �led in the �le system), and therefore
protected from external access. The �le can be downloaded to the user's �le system via DME administration.
File name
relevant SAP Note 1234970
You can use exit 21 see consulting note 1234970. In exit 21 (transaction OBPM3), you can change the �le name during runtime.
At event 21, you can add to a header or pre�x of the payment medium that was created by event 20 by changing entries in table
T_FILE_OUTPUT.
The �le name can be changed using changing parameter C_FILENAME.
Import parameter I_XFILESYSTEM speci�es if the �le should be output to the �le system or the TemSe �le that was entered on
the selection
screen of the generic payment medium program.
SAP Note 3280356 - Issues with OBPM4 selection variants during batch and payment medium creation
SAP Note 921720 - Payment medium: Security and encryption
5. Customizing (FBZP)
1. You wish to use different payment formats for the same payment method, depending on house bank and company code.
Example: You use a payment method for SEPA payments. But one house bank is requesting a different SEPA-version than the
other house banks.
https://help.sap.com/docs/disclaimer
https://me.sap.com/notes/984462
https://me.sap.com/notes/1782685
https://me.sap.com/notes/1234970
https://me.sap.com/notes/1234970
https://me.sap.com/notes/3280356
https://me.sap.com/notes/921720
4/11/2024
98This is custom documentation. For more information, please visit the SAP Help Portal
Relevant SAP Notes:
1943453 - PMW-format depending on house bank and company code
2045873 - Jump from transaction FBZP to the view cluster VC_T042ZA_FORMAT
2. Note to payee:
https://help.sap.com/docs/disclaimer
https://me.sap.com/notes/1943453
https://me.sap.com/notes/2045873
4/11/2024
99This is custom documentation. For more information, please visit the SAP Help Portal
Relevant SAP notes:
SAP Note 1837294 - Note to payee DMEE_PAYD-TEXT in �le
SAP note 1404650 - Consulting note: Note to payee in PMW payment medium DMEE
3. How is separation or denomination performed for Payment Medium Workbench (PMW) �les?
Relevant SAP note :
1781325 - SEPA: No separation by company code/�eld and
1794408 - PMW: Granularity, denomination, group number, logical �le, sorting
4. You wish to use different payment formats for the same payment method, depending on house bank and company code.
Example: You use a payment method for SEPA payments. But one house bank is requesting a different SEPA-version than the
other house banks.
Relevant SAP Notes:
1943453 - PMW-format depending on house bank and company code
2045873 - Jump from transaction FBZP to the view cluster VC_T042ZA_FORMAT
PMW: General Information and DMEE (Data Medium Exchange Engine) or DMEEX
(Data Medium Exchange Engine Extended)
General information
The DMEE supports a variety of applications. We create outgoing �les for the Payment Program (tree type PAYM), to submit
payment to bank electronically. For this tree type, we use PMW to con�gure the Payment Media.
The Payment medium format contains �elds which are �lled with contents from SAP system. This is called ʻMapping’
Mapping can be implemented either:
Using the DME Engine.
Using Programming Function Modules.
SAP Note 395679 – ’PMW: Overview of available formats’ specify payment medium formats that are delivered and supported by
SAP.
SAP Note 2253571 - Collective information note: CGI_XML_CT, CGI_XML_DD extended with BAdI enhancement
SAP Note 2784858 - Collective information note: CGI_CT, CGI_DD based on the DMEEX engine
SAP Note 2795667 - ISO20022 adoption - global harmonisation & regulation (SEPA in Europe)
SAP Note 2682253 - Payment Formats supported in Release S/4HANA 1809 On-Premise
SAP Note 2518834 - Payment Formats available in Release S4/Hana 1709 On-Premise
There are two groups of the formats:
Formats that are implemented using function modules: e.g. DTAZV, MT101.
Formats that are implemented using the Data Medium Exchange (DME) Engine: e.g. CH_DTA, SEPA_CT, V3.
The Data Mapping describes how to map data from source �elds to the target �elds in a DME �le. In most cases, it is speci�ed
how data is to be mapped to elements, the nodes in the DMEE format tree that represents these target �elds. Also, it can be
speci�ed a mapping procedure and source information for atoms when an element contains several mappings rules.
https://help.sap.com/docs/disclaimer
https://me.sap.com/notes/1837294
https://me.sap.com/notes/1404650
https://me.sap.com/notes/1781325
https://me.sap.com/notes/1794408
https://me.sap.com/notes/1943453
https://me.sap.com/notes/2045873
https://me.sap.com/notes/395679/E
https://me.sap.com/notes/2253571
https://me.sap.com/notes/2784858
https://me.sap.com/notes/2795667
https://me.sap.com/notes/2682253
https://me.sap.com/notes/2518834
4/11/2024
100This is custom documentation. For more information, please visit the SAP Help Portal
If the format which your bank is requesting is not contained in SAP note 395679, i.e. if you have a requirement to support a
different format as per that speci�ed by your bank, you can use the Payment Medium Workbench where in you can create your
own format in DMEE as per your requirement.
About PMW
The payment medium workbench was created to replace the classicpayment medium programs. The main bene�ts of using the
PMW are as follows:
It separates format speci�c parts from the more complex general part.
You can easily create new formats with customising and mapping functions or mapping with the DME engine.
SAP Note 524520 - PMW - Information on Payment Medium Workbench 
Please also read the IMG documentation and the note 524520, which has basic information how to use it, which customizing set
up is necessary etc.
You can check the formats in transaction DMEE with tree type PAYM.
For the con�guration use the transactions OBPM1, OBPM2, OBPM3, OBPM4.
Create a Variant of the used format in program SAPFPAYM and maintain it in OBPM4.
After you change the de�nitions in OBPM1/OBPM2/OBPM3, you can only activate changed Customizing for a payment medium
run that has already run once, when you start the RFPAYM_RESET report. See note 973549 - Payment medium: Customizing
change does not work.
DMEE (Data Medium Exchange Engine)
SAP Note 3138271 - DMEE - Trace Tool
Don’t you understand why the node or the level is missing in the output �le? Why the mapped value is in a different format than
expected? Or would you like to understand how the conditions are processed internally? DMEE Trace Tool can help you to get
the answers. More on Trace Tool: https://blogs.sap.com/2022/06/27/dmee-trace-tool/
SAP KBA 3326198 - DMEE Trace Tool
DMEEX (Data Medium Exchange Engine Extended)
SAP Note 3077367 - DMEEX - Feature Pack 2 - Trace Tool
Don’t you understand why the node or the level is missing in the output �le? Why the mapped value is in a different format than
expected? Or would you like to understand how the conditions are processed internally? DMEEX Trace Tool can help you to get
the answers. More on Trace Tool: https://blogs.sap.com/2021/06/07/the-dmeex-trace-tool/
SAP KBA 3319911 - DMEEX Trace Tool
DMEEX Trace Tool helps users with analyzing problems that often occur during DMEEX Tree creation or modi�cation
How to create your own DMEE/X Tree Type? Part 1 of 2
DMEE/X tree de�nition https://blogs.sap.com/2019/08/05/how-to-create-your-own-dmee-tree-type-part-1-of-2/
How to create your own DMEE/X Tree Type? Part 2 of 2
https://help.sap.com/docs/disclaimer
https://me.sap.com/notes/395679
https://me.sap.com/notes/524520
https://me.sap.com/notes/524520
https://me.sap.com/notes/973549
https://me.sap.com/notes/3138271
https://blogs.sap.com/2022/06/27/dmee-trace-tool/
https://me.sap.com/notes/3326198
https://me.sap.com/notes/3077367
https://blogs.sap.com/2021/06/07/the-dmeex-trace-tool/
https://me.sap.com/notes/3319911
https://blogs.sap.com/2019/08/05/how-to-create-your-own-dmee-tree-type-part-1-of-2/
4/11/2024
101This is custom documentation. For more information, please visit the SAP Help Portal
DMEE/X tree de�nition https://blogs.sap.com/2019/08/08/how-to-create-your-own-dmee-tree-type-part-2-of-2/
Test Your Custom Bank Statement De�nitions in Map Format Data
Test Tool in Map Format Data https://blogs.sap.com/2023/04/16/test-your-custom-bank-statement-de�nitions-in-map-
format-data/
DMEEX tool delivered across all S/4HANA OnPremise releases
Latest version of DMEEX tool downported to all SAP S/4HANA OnPremise releases to have the same functionality and features
of the tool and delivered payment formats mapping.
https://blogs.sap.com/2020/04/28/dmeex-tool-delivered-across-all-s-4hana-onpremise-releases/
Converting DMEE formats into DMEEX and Manage Payment Formats
Blog : Converting DMEE formats into DMEEX and Manage Payment Formats
https://blogs.sap.com/2018/07/25/converting-dmee-formats-into-dmeex-and-manage-payment-formats/
Payment Advice Creation
Creation of payment advice
SAP Note 1224437 PMW: When are separate payment advice notes created?
It is a complex topic, there are many settings to consider like note point 4 in SAP note 305414:
"..
4. In payment program Customizing you have made an entry in �eld T042E-ANZPO (Line items per form) for the form data
(Transaction FBZP / Pmnt methods in company code / Form data) and have not set the �ag 'Pmnt advice if form is full' (T042E-
XAVIS) A value < 99 denotes that only this number of items can be paid per form. If you de�ne for example the value '4', then
four items are always paid collectively. .."
Furthermore, bear in mind that an additional line is generated for an item which contains a line item text (item text BSEG-
SGTXT) beginning with '*', provided that you want the text output in the form. Thus, if you want to pay four items, each
containing a line item text beginning with '*', a total of 8 items are generated. Consequently, only two documents (i.e., four
items) could be paid at a time per form in the above-mentioned example.
Lack of space for generating XML �les.
Solution: SAP note 1932233
to restrict the number of payments in a Payment Medium Workbench (PMW) �le.
https://help.sap.com/docs/disclaimer
https://blogs.sap.com/2019/08/08/how-to-create-your-own-dmee-tree-type-part-2-of-2/
https://blogs.sap.com/2023/04/16/test-your-custom-bank-statement-definitions-in-map-format-data/
https://blogs.sap.com/2020/04/28/dmeex-tool-delivered-across-all-s-4hana-onpremise-releases/
https://blogs.sap.com/2018/07/25/converting-dmee-formats-into-dmeex-and-manage-payment-formats/
https://me.sap.com/notes/1224437
https://me.sap.com/notes/305414
https://me.sap.com/notes/1932233
4/11/2024
102This is custom documentation. For more information, please visit the SAP Help Portal
Payment formats supported in S/4 HANA and in ERP
SAP Note 2253571 - Collective information note: CGI_XML_CT, CGI_XML_DD extended with BAdI enhancement
SAP Note 2784858 - Collective information note: CGI_CT, CGI_DD based on the DMEEX engine
SAP Note 2795667 - ISO20022 adoption - global harmonisation & regulation (SEPA in Europe)
SAP Note 2682253 - Payment Formats supported in Release S/4HANA 1809 On-Premise
SAP Note 2518834 - Payment Formats available in Release S4/Hana 1709 On-Premise
SEPA and CGI Format Tree
SEPA
The mandatory introduction of the single euro payments area (SEPA) as of February 01, 2014 harmonizes bank transfers and
direct debits for payments in euro. For more information about SEPA direct debits, see the website of the European Payments
Council (http://www.europeanpaymentscouncil.eu).
Check the relevant composite SAP Notes for the various components:
1845689 SEPA composite SAP Note: Direct debit procedure in FI-AR
1848201 SEPA composite SAP Note: Master data
1845440 SEPA composite SAP Note: Mandate and IBAN
1841781 SEPA composite SAP Note: Payment medium
1841123 SEPA composite SAP Note: Payment programs F110 and F111
1855795 SEPA composite SAP Note: Customer Connection
SAP Note 2253571 - Collective information note: CGI_XML_CT, CGI_XML_DD extended with BAdI enhancement
SAP Note 2784858 - Collective information note: CGI_CT, CGI_DD based on the DMEEX engine
SAP Note 2795667 - ISO20022 adoption - global harmonisation & regulation (SEPA in Europe)
SAP Note 2682253 - Payment Formats supported in Release S/4HANA 1809 On-Premise
SAP Note 2518834 - Payment Formats available in Release S4/Hana 1709 On-Premise
Important!
We recommend copying and creating the format in the customer namespace:
A format in the customer namespace is recommended to enable protection against the overwriting of the format by means of a
Support Package import.
Incorrect character in the XML �le
Special characters should have been converted in the standard characters for the information like name, city, and address.
Check if SAP note 1979220 is applied in your system.
https://help.sap.com/docs/disclaimer
https://me.sap.com/notes/2253571
https://me.sap.com/notes/2784858
https://me.sap.com/notes/2795667
https://me.sap.com/notes/2682253
https://me.sap.com/notes/2518834
http://www.europeanpaymentscouncil.eu/
https://me.sap.com/notes/1845689
https://me.sap.com/notes/1848201
https://me.sap.com/notes/1845440
https://me.sap.com/notes/1841781
https://me.sap.com/notes/1841123
https://me.sap.com/notes/1855795
https://me.sap.com/notes/2253571
https://me.sap.com/notes/2784858https://me.sap.com/notes/2795667
https://me.sap.com/notes/2682253
https://me.sap.com/notes/2518834
https://me.sap.com/notes/1979220
4/11/2024
103This is custom documentation. For more information, please visit the SAP Help Portal
Also, you can refer to the KBA 1988783 - CGI_XML_CT: Special characters in DMEE XML Format.
SEPA XML �le does not contain all records
Possible source of error:
Could be related to sort/key �eld de�nition.
Same checks as in the case of an empty result.
Could be caused by wrong setting of repetition limit.
Dump during DME �le creation
You are creating the XML �le (click on the printout button o executing the SAPFPAYM_SCHEDULE program) and ABAP runtime
error “CONVT_NO_NUMBER: Unable to interpret ……… as a number” is triggered.
The reason could be that you have de�ned an element or atom of type P (i.e. currency amount), but source �eld contains non-
numerical symbols.
How to �nd the node with the problem: 
In the short dump, in section ʻInformation on where termination occurred’, you will �nd the information about where the
conversion error has happened. It will say that the error happened in form N_XXXXXXXXXXM. Here, N_XXXXXXXXXX is the
internal node ID of the problem node.
Then, you take this number as a selection value for SE16 for table DMEE_TREE_NODE or you can also search the node in the
DMEE dialog via de internal node ID.
Empty tag has been created in the SEPA XML �le
The SEPA XML �le has been created with the following information, as an example:
 <RmtInf>
 <Ustrd/>
 </RmtInf>
There is not information to send in the node <Ustrd>, then the node <Ustrd/> must not be created in the xml �le.
Solution: 
There are three status of a format tree node which can be assigned:
- Standard: The node is always output to the target �le. If the node does not have a value - because no mapping rule was
assigned, for example - then the node appears empty in the �le
- Mandatory: The node must have a value, otherwise an error message is displayed when the �le is generated.
https://help.sap.com/docs/disclaimer
https://me.sap.com/notes/1988783
4/11/2024
104This is custom documentation. For more information, please visit the SAP Help Portal
- Optional: The node is not output if it does not contain a value.
So, the status of node needs to be set to '2' to make sure that the tag doesn't appear in the output �le of the content of the tag
is empty.
Also, verify that the note 1584497 - DMEE: Status �eld is not considered for elements is applied in your system.
Wrong node information in the SEPA XML �le
When there is wrong information in the SEPA XML �le, �rst of all, you must verify that:
1. You have the last version for CGI_XML_CT/CGI_XML_DD format in your system. For that, you have to refer to the note:
2056456 CGI: CGI_XML_CT/ CGI_XML_DD: Collective note for CGI formats.
2. The variant in transaction FBPM for format CGI_XML_CT/CGI_XML_DD containing ISO code in "Format Parameters" for
the corresponding country since there are some conditions on the node which depend on the Country ISO code. 
As a reference, you can have a look to the KBA 1932850 - CGI_XML_CT: SEPA for Spain [VIDEO] (Also, valid for other
countries, such as Italy)
3. Then, you should check the mapping from the DMEE tool. For instance, the node <Nm> from element <Cdtr> is �lled with
wrong name.
Go to the DMEE format and check the mapping procedure for this node.
https://help.sap.com/docs/disclaimer
4/11/2024
105This is custom documentation. For more information, please visit the SAP Help Portal
Own mapping atoms, this is possible only for elements and the mappings rule are dependent on conditions or if different parts
of the element are to be �lled from different sources.
In this case, every node will be �lled depend on some conditions. We need to check which the conditions are ful�lled in every
node.
When this condition is ful�lled, then this �eld will be mapping to the structure �eld 
https://help.sap.com/docs/disclaimer
4/11/2024
106This is custom documentation. For more information, please visit the SAP Help Portal
If the �eld value is mapped from a source �eld, check the value in corresponding REGUH/REGUP �eld.
Sepa mandate amendments not visible in CGI_XML_DD or SEPA_DD �le
For SEPA Direct Debit, an amendment is sent in the payment medium �le that enables a comparison between the old data and
the new data, after relevant changes in the collection mandate.
This amendment should actually be sent with the �rst payment medium after the mandate change, but not for all subsequent
payment media. (Note 1424561 - SEPA direct debit: B2B mandates and amendments).
The amendment indicator should always be setup automatically, when there is "something to amend".
You can �nd the relevant program code in the function module DMEE_SEPA_MANDATE_FOR_DD. There is the �eld
E_FPAYHX_MDT-AMEND_IND being set to 'X', which should cause the value 'true' in the corresponding DMEE �le tag.
The 'X' will be set, if the mandate ID, the creditor ID, the sender IBAN, the sender BIC, or the receiver name has been changed.
But this does not happen, if a mandate is being used for the �rst time. A situation, where you would need to send an
amendment with �rst usage of a mandate is not supported anyway.
That means, a change in one of the following �elds will trigger the amendment (the �elds are in the right column):
 ORIG_MNDID -> MNDID
 ORIG_REC_CRDID -> REC_CRDID
 ORIG_IBAN -> SND_IBAN
 ORIG_BIC -> SND_BIC
 ORIG_REC_NAME1 -> REC_NAME1
 ORIG_REC_NAME2 -> REC_NAME2
These are the �elds of table SEPA_MANDATE, see the table for details of the �eld.
In DMEE-tree SEPA_DD, the �elds will be put in the following nodes:
DMEE-Node Origin of value
OrgnlCdtrSchmeId ORIG_REC_CRDID
https://help.sap.com/docs/disclaimer
4/11/2024
107This is custom documentation. For more information, please visit the SAP Help Portal
OrgnlMndtId ORIG_MNDID
OrgnlDbtrAcct ORIG_IBAN
You should also check if the following note are applied in your system:
 
 1403874 - SEPA: Additional �elds and amendment �elds
 1414936 - SEPA: Setting ID of payment medium in SEPA mandate
 1831073 - Error in SEPA_MANDATES_API_GET
 2006906 - SEPA mandates: Incorrect sequence type and/or no change �ag 
 
Other known issues:
Elements TP are empty. XML doesn´t allow the declaration of empty elements:
Refer to the KBA 1942196 Payment formats CGI_XML_DD and CGI_XML_CT with empty tag <Tp/> 
The node <ref> is being �lled: 
The reason for that it is because you must have selected the Structured Remittance Info �eld [STRD] in the variant
maintained for the format CGI_XML_DD. So if you select this �eld in the variant, then you will get the Remittance Info in
the �le : RmtInf > Strd > CdtrRefInf > Ref >
The information is not getting �lled in Ustrd tag
This information gets �lled by note to payee and for this, you have to maintain in transaction FBZP, 
Payment method in country -> Note to payee by origin.
For note to payee creation, please do it in the transaction OBPM2.
 After maintaining and assigning it for your country and payment method, the Ustrd node should get �lled.
Line item display issues
Line items are document items that were posted to a speci�c account. In contrast to a document item, a line item only contains
the information from the document item that is relevant from the account view.
You can display the following line items:
Open items
Cleared items
Noted items
Parked items
Items with special G/L transactions (in Accounts Receivable and Accounts Payable)
Items with customer or vendor items (in Accounts Receivable and Accounts Payable)
Line items can be displayed for the following account types:
Vendor accounts
G/L accounts
Customer accounts
Main transactions for line item displayare:
https://help.sap.com/docs/disclaimer
4/11/2024
108This is custom documentation. For more information, please visit the SAP Help Portal
Vendor line item display: FBL1N
G/L account line item display: FBL3N, FAGLL03
Customer line item display FBL5N
As a prerequisite to be able to display the line items for an account, line item display needs to be set up for the respective
accounts, that is, the Line Item Display indicator must be set in the master data of the account:
This setting is mandatory for customer and vendor accounts.
For G/L accounts these setting are to be done in the account master data (FS00).
Line item Display
Dynamic Selection Fields for Line Items transactions FBL1N, FBL3N and FBL5N
Low performance of FBL1N, FBL3N and FBL5N
Special Fields in FBL*N transactions
How to add ʻNet due date’ �eld in T-code: FBL1N and FBL5N
FAGLL03 display issues
Related SAP Notes/KBAs
 3275164 - Line item display reports overview / how-to scenarios
Dynamic Selection Fields for Line Items transactions FBL1N, FBL3N and FBL5N
During display transactions you can include some new �elds in dynamic selection. These �elds are maintained in logical data
bases and can be changed respecting some tables. In these tables you have the �elds that are available to be displayed in
dynamic selection. No other �eld from other structure can be included. Also, �elds in BKPF cannot be added to the dynamic
selections.
What �elds are available for Dynamic Selection
In general ledger account line items display (FBL1N, FBL3N and FBL5N) you can follow SAP note 310886 how to enhance logical
databases (DDF, KDF or SDF) and which tables are available.
For Customers (logical database DDF) you have the following permitted tables:
 KNA1, KNB1: All �elds are permitted that are contained in the VF_DEBI view. If necessary, you have to include additional
�elds in the view �elds category using Transaction SE11.
 BSID: all �elds
For Vendors (logical database KDF) you have the following permitted tables:
https://help.sap.com/docs/disclaimer
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880327.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880330.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880331.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361878608.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880322.html
https://launchpad.support.sap.com/#/notes/3275164
https://service.sap.com/sap/support/notes/310886
https://service.sap.com/sap/support/notes/310886
4/11/2024
109This is custom documentation. For more information, please visit the SAP Help Portal
LFA1, LFB1: All �elds are permitted that are contained in the VF_KRED view. If necessary, you have to include additional
�elds in the view �elds category using Transaction SE11.
BSIK: all �elds
For G/L Accounts (logical database SDF) you have the following permitter tables:
SKA1: all �elds
SKB1: all �elds
BSIS: all �elds
Example accessing transaction SE36 to access logical databases:
 
Dynamic selection in indexes
For constantly use of dynamic �elds in display transactions, it is recommended to include these �elds in database index. These
missing �elds can cause bad performance during the selections. To avoid this kind of performance issues, consult section "Low
performance of FBL1N,FBL3N,FBL5N"
For the following programs, read SAP note 50370:
RFDSLD00 customer balance 
RFKSLD00 vendor balance
RFDUML00 customer sales 
RFKUML00 vendor sales
https://help.sap.com/docs/disclaimer
https://service.sap.com/sap/support/notes/50370
4/11/2024
110This is custom documentation. For more information, please visit the SAP Help Portal
Low performance of FBL1N, FBL3N and FBL5N
How to improve the performance of line item display transactions? 
A performance issue is being issued in FBL1N/FBL3N/FBL5N, sometimes TIME_OUT error is occurring. 
There are 3 processes that impacts performance:
1 - Database Selection
Check whether a suitable database index has been created in the dictionary (transaction SE11 -> indexes). If no index has been
created, create the corresponding indexes and activate it.
BSIS/BSAS: MANDT, BUKRS, HKONT, BUDAT
BSIK/BSAK: MANDT, BUKRS, LIFNR, BUDAT
BSID/BSAD: MANDT, BUKRS, KUNNR, BUDAT
Recreate the database statistics after creating the index so that the index is used. For example, you can use transaction DB20
to do this. The optimizer of the database interface then recognizes the index and uses it depending on the selection. This is not
required for an MS-SQL database because the statistics are created there automatically.
 
2 - Account range in the selection screen
You do not specify any account or use a range of several accounts in the selection screen of the transaction, ex:
How does transactions FBL1N, FBL3N and FBL5N select the data?
These transactions use logical databases (KDF/SDF/DDF) to select the master data and line item data.
These logical databases are used for the selection in many reports for example, for RFDEPL00, RFKEPL00 or RFDOPR10.
In the transactions, the master data is read in advance.
Then, an access to the line items with '25' packages of accounts is created. This is a technical requirement. Otherwise, the
selection may trigger a runtime error.
Example:
https://help.sap.com/docs/disclaimer
4/11/2024
111This is custom documentation. For more information, please visit the SAP Help Portal
You select an account range of 250.000 accounts in a company code.
First, the master data is determined:
FBL1N -> Tables LFA1/LFB1
FBL3N -> Tables SKA1/SKB1
FBL5N -> Tables KNA1/KNB1
 The system then uses the selected account information to read the items in packages.
FBL1N -> Tables BSIK/BSAK
FBL3N -> Tables BSIS/BSAS
FBL5N -> Tables BSID/BSAD
In the example, the document tables are accessed 10.000 times in each case.
However, in every access to the tables, opening the SQL statement requires quite a long runtime.
You can try to improve the performance by using an account range which does not have more than 1.000 accounts.
For the best performance of the transaction, no more than 25 accounts should be selected.
3 - Special �elds and BTE 1650
a) Special �elds are very time consuming, because BSEG/BKPF tables are read in addition of secondary indexes.
If you have special �elds in your layout, try to use standard layout 1SAP when running the transaction, so the performance can
be improved.
b) You’ve implemented BTE 1650 as per note 112312 to display offset account in FBL3N or you use the BTE to display a �eld that
is not available as special �eld. 
This is the same case as for special �elds, this is time consuming, you can test by deactivating the BTE to see if the
performance is improved.
Special Fields in FBL*N transactions
General information
You want to display further �elds in the line item report FBL3N
Refer to the following SAP notes:
984305 - "Line item: De�nition of special �elds(T012S)"
215798 - "FBL*N: Special �elds are not displayed"
https://help.sap.com/docs/disclaimer
https://launchpad.support.sap.com/#/notes/112312
http://service.sap.com/sap/support/notes/373268
http://service.sap.com/sap/support/notes/215798
4/11/2024
112This is custom documentation. For more information, please visit the SAP Help Portal
 Describes the standard procedure to allow the de�nition of special �elds. Please read these notes for general information and
for common topics such as:
Basic Information
Troubleshooting and know problems
Helpful notes
De�nition of special �elds 
If you have issues regarding addition of Special Fields , see the following sections. 
How to de�ne special �elds?
First de�ne special �elds following customizing paths described in note 984305.
The Field is available in the layout but is empty
Run reports BALVBUFDEL as described in notes 215798.
Check in SE16 if the �eld is �lled in the table (ex. BKPF-BKTXT). If the �eld is empty, the issue is in the transactionwhich
posted the document, there is no display issue.
 
The �eld is not available to be in the layout
The basic structure for displaying the items is RFPOSX.
From this entry and the relevant entries in the table T021S, the system generates the structure RFPOSXEXT, which is used for
the display. The special �elds have the pre�x "U_".
You can check this at the following point of the report:
After run the report and check the report output you can go to the menu "Settings"->"Layout"->"Current..."
The list containing the �elds which are included at your layout will appear.
Press "CTRL+SHIFT+F6" in order to display the technical information and check if the �rst character is "U_".
https://help.sap.com/docs/disclaimer
http://service.sap.com/sap/support/notes/373268
http://service.sap.com/sap/support/notes/215798
4/11/2024
113This is custom documentation. For more information, please visit the SAP Help Portal
When you save or subsequently generate items, you receive an error message, for example "Termination with error 3" or F4 308
("System error: Error in routine GENERATE RFPOSXEXT").
In this case, analyze the activation log of the relevant structure. Call transaction SE11 and enter the relevant structure in the
"Data type" �eld:
RFPOSXEXT Display the structure.
Then, choose "Utilities -> Activation Log" in the menu.
This log contains exact explanations of which errors occurred.
If problems occur when you generate the structure RFPOSXEXT, you can try to regenerate these again using the report
RFPOSXEXTEND.
Other related issues: 
a) You need to use a �eld that is not available as special �eld in T021S
These special �elds can only be taken from the following tables:
BKPF, BSEC, BSED, BSEG, PAYR, BSEGC, BSBV.
 If you need to display a �eld from a different table, then you should use BTE 1650.
https://help.sap.com/docs/disclaimer
4/11/2024
114This is custom documentation. For more information, please visit the SAP Help Portal
You can use the following SAP Note as a reference to check how the BTE can be implemented:
368310 - LI: Open FI: long text for special G/L transacs
 b) The use of special �elds may cause performance issues in some scenarios.
 Please refer to the following information in order to avoid this kind of issues. 
 1135916 - "Line items: Help for analysis for long runtime"
 1652034- "Line items display performance enhancement"
How to add ʻNet due date’ �eld in T-code: FBL1N and FBL5N
Purpose:
Net Due Date is calculated from the baseline date for payment and the highest number of days within the terms of payment.
This document introduces the steps how to add ʻNet due date’ �eld in T-code: FBL1N and FBL5N.
Overview:
Execute T-code: SU01 and enter the User ID.
Press ʻchange’ button and select parameter tab, then enter the following parameter:
FIT_DUE_DATE_SEL X
https://help.sap.com/docs/disclaimer
https://launchpad.support.sap.com/#/notes/368310
http://service.sap.com/sap/support/notes/1135916
http://service.sap.com/sap/support/notes/1652034
4/11/2024
115This is custom documentation. For more information, please visit the SAP Help Portal
Execute T-code: FBL1N or FBL5N , you can see the �eld ʻNet due date’.
 
FAGLL03 display issues
https://help.sap.com/docs/disclaimer
4/11/2024
116This is custom documentation. For more information, please visit the SAP Help Portal
This report displays a list of line items of the G/L accounts. 
 It is possible to display the line items for one or more G/L accounts in the following views:
In the general ledger view for line item display, line items can be displayed together with the general ledger account
assignments (General Ledger Line Items) and G/L account line items or document data.
In the entry view for line item display, G/L account line items (G/L Account Line Items) can be displayed.
The G/L account line items that were only posted to non-leading ledgers are not displayed in the entry view.
It is also possible to display the items in a cross-company-code list.
In this list, individual documents and multiple posted line items can be changed.
FAGLL03 display issues
Dynamic Selection Fields for FAGLL03
Low performance in transaction FAGLL03 or TIME_OUT short dump
Special Fields in FAGLL03 transaction
Offsetting Account Report
Related SAP Notes/KBAs
 3275164 - Line item display reports overview / how-to scenarios
Dynamic Selection Fields for FAGLL03
 
In New General Ledger account display transaction the additional of dynamic �elds in selection does
not follow the same steps of note 310886.
In the transaction FAGLL03 you can enhance structures SKA1_FS, SKB1_FS, BSIS_FS and
FAGFLEXA_FS using APPEND.
 
How to discover what �elds are available:
 
The �elds available for the dynamic selection in FAGLL03 are only the ones in tables SKA1, SKB1 and
BSIS.
https://help.sap.com/docs/disclaimer
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880324.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880854.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880707.html
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361881806.html
https://launchpad.support.sap.com/#/notes/3275164
4/11/2024
117This is custom documentation. For more information, please visit the SAP Help Portal
For more details on how to add the �elds, check SAP note 945932 .
 
Dynamic selection in indexes
 For constantly use of dynamic �elds in display transactions, it is recommended to include these �elds in database index. These
missing �elds can cause bad performance during the selections. To avoid this kind of performance issues, consult the link below:
Low performance of FBL1N, FBL3N and FBL5N
For the following programs, read SAP note 50370:
RFDSLD00 customer balance 
RFKSLD00 vendor balance
RFDUML00 customer sales 
RFKUML00 vendor sales
 
Low performance in transaction FAGLL03 or TIME_OUT short dump
How to improve the performance of FAGLL03?
You are facing a performance issue in FAGLL03, sometimes TIME_OUT error is occurring. 
There are 3 processes that impacts performance:
1 - Database Selection
Check whether a suitable database index has been created in the FAGLFLEXA table (transaction
SE11 -> indexes). The following index should be created:
FAGLFLEXA~Z3
RCLNT Client
RBUKRS Company code
RACCT Account number
https://help.sap.com/docs/disclaimer
https://service.sap.com/sap/support/notes/945932
https://help.sap.com/docs/SUPPORT_CONTENT/fiaccounting/3361880329.html
https://service.sap.com/sap/support/notes/50370
4/11/2024
118This is custom documentation. For more information, please visit the SAP Help Portal
RLDNR Ledger
BUDAT Posting date
Recreate the database statistics after creating the index so that the index is used. For example,
you can use transaction DB20 to do this. The optimizer of the database interface then recognizes
the index and uses it depending on the selection. This is not required for an MS-SQL database
because the statistics are created there automatically.
2 - G/l account range in the selection screen
 You do not specify any g/l account or use a range of several accounts in the selection screen of
the transaction.
How FAGLL03 selects data:
You select an account range of 10 accounts in a company code.
First, the master data of these accounts (SKA1/SKB1) is selected.
The data determined is used to decide how the access must be created for each account:
 
Line item/open item managed:
In this case, the selection is created using a 'join' of the index tables BSIS/BSAS and the 'new
general ledger' table (for example, FAGLFLEXA). 
If the selected account is a reconciliation account, the system also reads the document segment
table BSEG to provide data, for example, about the relevant customers or vendors.
https://help.sap.com/docs/disclaimer
4/11/2024
119This is custom documentation. For more information, please visit the SAP Help Portal
 
Not line item/open item managed: 
In this case,the selection is created using a 'join' of the document header table BKPF and the
'new general ledger' table (for example, FAGLFLEXA).
In addition, the document segment table BSEG is read to add further information to the data that
is to be displayed. 
 
So, if you have a range of 1.000 accounts, selection of the line items is created for each account.
So you should keep the account range as minimum as possible in order to improve the
performance.
3 - Special �elds / BADI 'FAGL_ITEMS_CH_DATA'
a) Special �elds are very time consuming, because BSEG/BKPF tables are read in addition of
secondary indexes. 
If you have special �elds in your layout, try to use standard layout 1SAP when running the
transaction, so the performance can be improved. 
 
b) You’ve implemented BADI FAGL_ITEMS_CH_DATA as per note 1034354 to display offset
account in FAGLL03 or use the badi to display a �eld that is not available as special �eld using a
custom logic. 
This is the same case as for special �elds, this is time consuming, you can test by deactivating
the BADI to see how much the performance is improved.
Special Fields in FAGLL03 transaction
General information
You want to display further �elds in the line item report FAGLL03
Fpr this purpose, please check SAP note:
https://help.sap.com/docs/disclaimer
https://launchpad.support.sap.com/#/notes/1034354
4/11/2024
120This is custom documentation. For more information, please visit the SAP Help Portal
984305 - "Line item: De�nition of special �elds(T012S)": 
There is described the standard procedure to allow the de�nition of special �elds. Please read these notes for general
information and for common topics such as:
Basic Information
Troubleshooting and know problems
Helpful notes
De�nition of special �elds 
If you have issues regarding addition of Special Fields , see the following sections. 
How to de�ne special �elds?
First de�ne special �elds following customizing paths described in note 984305.
Then include the �led in the ALV layout:
After run the report and check the report output you can go to the menu "Settings"->"Layout"->"Current..."
The list containing the �elds which are included at your layout will appear.
Press "CTRL+SHIFT+F6" in order to display the technical information and check if the �rst character is "U_".
The Field is available in the layout but is empty
Run reports BALVBUFDEL as described in notes 215798.
Check in SE16 if the �eld is �lled in the table (ex. BKPF-BKTXT). If the �eld is empty, the issue is in the transaction which
posted the document, there is no display issue.
 
The �eld is not available to be in the layout
The basic structure for displaying the items is FAGLPOSE. From the relevant entries in the table T021S, the system generates
the FAGLPOSYEXT structure. The special �elds have the pre�x "U_". Both structures are included in the structure FAGLPOSX,
which is used for the display.
If the �eld is not in the FAGLPOSX structure, please delete the special �elds from T021S and insert it again.
In case when you save or subsequently change the special �elds, you receive an error message, for example "Termination with
error 3" or F4 308 ("System error: Error in routine GENERATE FAGLPOSYEXT").
https://help.sap.com/docs/disclaimer
http://service.sap.com/sap/support/notes/373268
http://service.sap.com/sap/support/notes/373268
http://service.sap.com/sap/support/notes/215798
4/11/2024
121This is custom documentation. For more information, please visit the SAP Help Portal
In this case, analyze the activation log of the relevant structure. Call transaction SE11 and enter the relevant structure in the
"Data type" �eld:
 
FAGLPOSYEXT Display the structure.
Then, choose "Utilities -> Activation Log" in the menu.
This log contains exact explanations of which errors occurred.
In certain constellations, the routine AFTER-IMPORT for the table T021S for generating the special �elds may not be started
correctly.
In this case, start the generation manually. To do this, proceed as follows:
Call transaction SE37, enter the function module ITEM_STRUC_EXTENSION and execute it with the following parameters:
BASIC_STRUCNAME FAGLPOSY
EXT_STRUCNAME FAGLPOSYEXT
EXT_FIELDS_TABNAME T021S
I_LSTCL D
X_TRANSPORT ' '
After you have executed the function module, the structure should be regenerated correctly.
Other related issues
 a) You need to use a �eld that is not available as special �eld in T021S
 These special �elds can only be taken from the following tables: 
 BKPF, BSEC, BSED, BSEG, PAYR, BSEGC, BSBV.
 If you need to display a �eld from a different table, then you should use BADI 'FAGL_ITEMS_CH_DATA'
 You can use the following SAP Note as a reference to check how the BTE can be implemented:
 1174945 - FAGLL03: Display of absolute amounts
 b) The use of special �elds may cause performance issues in some scenarios.
 Please refer to the following information in order to avoid this kind of issues. 
 1135916 - "Line items: Help for analysis for long runtime"
 1652034- "Line items display performance enhancement"
Offsetting Account Report
https://help.sap.com/docs/disclaimer
http://service.sap.com/sap/support/notes/1174945
http://service.sap.com/sap/support/notes/1135916
http://service.sap.com/sap/support/notes/1652034
4/11/2024
122This is custom documentation. For more information, please visit the SAP Help Portal
In order to display the offsetting account information in the line item display for the new general ledger (FAGLL03), it is
necessary to create and activate an implementation for the 'FAGL_ITEMS_CH_DATA' BAdI. 
To do so, proceed as explained in SAP Note 1034354 - FAGLL03: Display of offsetting account information
Supportability Tools - Accounts Payable and Accounts Receivable
Tool/App 
Name
Purpose/Bene�t/Objective Documentation Tool/App
 
Location 
Category
RFCORR40 Report shows differences between the total of the account balances and the
total of the credit receivables 
Available
in R/3
Analysis
 RFDKLI20 The RFDKLI20 report recreates the SD and FI credit data after organizational 
changes and also correct differences between open items and credit total
 Available
in R/3
 Analysis
Related SAP Notes/KBAs
SAP KBA 2930159 - Difference between FBL5N and FD32/33
SAP KBA 2057405 - How to run the report RFDKLI20?
Access SAP For Me Visit the SAP Community View Product Documentation
https://help.sap.com/docs/disclaimer
https://launchpad.support.sap.com/#/notes/1034354
https://me.sap.com/notes/2930159
https://me.sap.com/notes/2057405
https://me.sap.com/
https://community.sap.com/
https://help.sap.com/docs/