See in OSS note 305414 - F110: Unintelligible grouping of documents:
The grouping of items in the payment program can have different causes.Check whether the following criteria are applicable in your case:
1. You can pay open items collectively using the automatic payment transactions but only if certain fields are identical.Structure ZHLG1 specifies these fields.Important fields are for instance, currency, receiver, payment method in the item, bank details in the item.For more about this see Note 164835.
2. A grouping key is stored in the master record of the vendor/customer.The fields according to which the payment program groups the documents are defined per grouping key in Customizing (Transaction OBAP).
If this grouping key does not work the way you expect it to, check whether report RSZGR000 contains the respective source code (the keys defined in Transaction OBAP have to exist in the CASE statement for G01-ZGRUP). If this not the case, you have to generate the report. You can do this by changing one of the entries in the transaction and subsequently saving it.
3. In the master record of the vendor, flag 'Individual payment' (LFB1-XPORE) has been selected.In this case, every open item is paid separately independent of all other criteria, i.e. no grouping takes place.
4. In payment program Customizing you have made an entry in field T042E-ANZPO (Line items per form) for the form data (Transaction FBZP / Pmnt methods in company code / Form data) and have not set the flag '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 define 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.
5. Items which contain a payment method in the document cannot be offset against items without a payment method for technical reasons.
6. In Customizing, the "Separate Payment for each Payment Reference" flag (T042B-XKIDS) is set in the 'Data for paying company code' which has the effect, that with one payment you can only pay invoices and credit memos that have the same payment reference.
7. flag (T042E-XEIPO) is set in 'Payment methods in company code' which has the effect that 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.
8. In Customizing, the "Payment per Due Day" flag (T042E-XZFAE) is set in 'Payment methods in company code' which has the effect that with one payment you can only pay items that are due on the same day.
Bluesky
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.