Open items can be grouped together in one payment due to different configuration and master data settings.
Open items are paid collectively using the automatic payment transactions only if certain fields are identical. Structure ZHLG1 specifies these fields. Important fields are:
In this blog post an overview is given of the different other ways of grouping open items in the automatic payment program.
The fields according to which the payment program groups the documents are defined per grouping key in customizing transaction OBAP.
Example: group by payment reference
In the company code segment of the business partner role FLVN00 (FI Vendor) / FLCU00 (FI customer), the grouping key is assigned.
In the company code segment of the business partner role FLVN00 (FI Vendor) / FLCU00 (FI customer), the single payment flag is available.
If this indicator is set, every customer/vendor open item is paid separately during automatic payment transactions. This means that open items are not grouped together for payment.
Open items, which contain a payment method in the document, are not offset against items without a payment method.
In customising transaction FBZP under data for paying company code, the 'Separate Payment for each Payment Reference' flag (T042B-XKIDS) is available.
When this flag is set, with one payment only invoices and credit memos are paid that have the same payment reference.
In customising transaction FBZP under payment method for company code, the flag 'Single Payment for Marked Item' (T042E-XEIPO) is available.
When this flag is set, all items, for which the payment method thus flagged has explicitly been entered, are paid separately. If the payment method is not specified explicitly, but instead selected from the by the payment program, you can pay several items at the same time.
In customising transaction FBZP under payment method for company code, the flag 'Payment per Due Day' flag (T042E-XZFAE) is available.
When this flag is set, with one payment only open items are paid that are due on the same day.
OSS note 305414 - F110: Unintelligible grouping of documents
Link: https://launchpad.support.sap.com/#/notes/305414
OSS note 164835 - F110: Clearing credit memos and invoices
Link: https://launchpad.support.sap.com/#/notes/164835
Blog post 'Optimisation of F110 – Use of Grouping Key'
Link: https://blogs.sap.com/2014/08/07/optimisation-of-f110-use-of-grouping-key/
Open items are paid collectively using the automatic payment transactions only if certain fields are identical. Structure ZHLG1 specifies these fields. Important fields are:
- business partner (vendor / customer),
- currency,
- receiver,
- payment method in the item,
- bank details in the item,
- instruction keys.
In this blog post an overview is given of the different other ways of grouping open items in the automatic payment program.
1. A grouping key is stored in the master record of the business partner (vendor / customer)
The fields according to which the payment program groups the documents are defined per grouping key in customizing transaction OBAP.
Example: group by payment reference
In the company code segment of the business partner role FLVN00 (FI Vendor) / FLCU00 (FI customer), the grouping key is assigned.
2. Single payment is flagged in business partner
In the company code segment of the business partner role FLVN00 (FI Vendor) / FLCU00 (FI customer), the single payment flag is available.
If this indicator is set, every customer/vendor open item is paid separately during automatic payment transactions. This means that open items are not grouped together for payment.
3. Open items which contain a payment method in the document
Open items, which contain a payment method in the document, are not offset against items without a payment method.
4. Separate payment for each payment reference
In customising transaction FBZP under data for paying company code, the 'Separate Payment for each Payment Reference' flag (T042B-XKIDS) is available.
When this flag is set, with one payment only invoices and credit memos are paid that have the same payment reference.
5. Single payment for marked item
In customising transaction FBZP under payment method for company code, the flag 'Single Payment for Marked Item' (T042E-XEIPO) is available.
When this flag is set, all items, for which the payment method thus flagged has explicitly been entered, are paid separately. If the payment method is not specified explicitly, but instead selected from the by the payment program, you can pay several items at the same time.
6. Payment per due date
In customising transaction FBZP under payment method for company code, the flag 'Payment per Due Day' flag (T042E-XZFAE) is available.
When this flag is set, with one payment only open items are paid that are due on the same day.
Useful references
OSS note 305414 - F110: Unintelligible grouping of documents
Link: https://launchpad.support.sap.com/#/notes/305414
OSS note 164835 - F110: Clearing credit memos and invoices
Link: https://launchpad.support.sap.com/#/notes/164835
Blog post 'Optimisation of F110 – Use of Grouping Key'
Link: https://blogs.sap.com/2014/08/07/optimisation-of-f110-use-of-grouping-key/
- SAP Managed Tags:
6 Comments
