Solution : https://service.sap.com/sap/support/notes/305414 (SAP Service marketplace login required)
Summary :
In SAP environments, the payment program often classifies items for mass payment based on specific criteria which might seem arbitrary at first. A payment document is generated for each category. This classification can be influenced by numerous factors. Ensuring identical fields like currency, payee details, and payment methods in items is critical, as detailed in structure ZHLG1 (Note 164835). Additionally, the payment software utilizes grouping keys defined in the OBAP transaction that determine document classification. If discrepancies exist, modifying the OBAP entries might be necessary. Moreover, master record settings and customization options like "Individual payment" or "Payment per Due Day" flags directly impact the payment program behavior, affecting how items are grouped and processed.
Key words :
item text bseg-sgtxt, line item text beginning, company code / form data, additional key words sapf110s, pay open items collectively, transaction fbzp / pmnt methods, payment program groups items, line item text, flag 'pmnt advice, structure zhlg1 specifies
Related Notes :
| 367809 | Problem with release upgrade to 4.6C: groupings in FI |
| 164835 | F110: Clearing credit memos and invoices |
| 109233 | F110: message FZ347 or several payment documents |
| 86578 | Guidelines for F110 Payment Program (W/Check mgmt) |