cancel
Showing results for 
Search instead for 
Did you mean: 

F110 Aggregation of open items after editing proposal

mmklodz
Explorer
0 Kudos
295

Hi all,

I have set up recipient settlement with the supplier. The functionality is generally working correctly. When I generate a payment proposal, all documents are aggregated and included in one payment - this is functioning correctly.

If a document is blocked for payment, the position will not be paid.
We can see that the recipient and supplier positions have been properly offset.
344.69 - 54,339.00 - 2,208.34 = -56,202.65."

mmklodz_2-1719301220178.png

mmklodz_3-1719301242090.png

In such a situation, the user who is processing the payment enters the payment proposal editing mode and has the ability to remove the block.

mmklodz_4-1719301321031.png

HERE MY PROBLEM ARISES

Edited supplier positions from which the block has been removed automatically enter the payment. Unfortunately, the recipient document, which was not blocked, needs to be manually assigned to the payment.

Since we have implemented more precise control and block more positions during the proposal generation, the work takes longer, and there are often multiple recipient invoices that require assignment. Only after the assignment is done, the positions are linked together.

Is it possible to automatically aggregate these positions after removing the block, in order to avoid manual assignment?

AFTER REMOVING THE BLOCK

mmklodz_5-1719301469313.png

MANUAL ASSIGNING THE RECIPIENT DOCUMENT

mmklodz_6-1719301531412.png

mmklodz_7-1719301545944.png

Thank you for all your answers.

Best regards,

Michal

 





View Entire Topic
coleti
Active Contributor
0 Kudos

Dear Michal, 

There are some consideration that you should took into account. Actually, the configuration that will perform the automatic aggregation depends on the Payment Methods and the Vendor Master Data.

I could see on your print screens that your open items don´t have Payment Methods defined, so maybe it will automatically defined by the Vendor Master Data during your payment proposal.

 

1st consideration: make sure the payment method choosen in the proposal for your open item is well configured to avoid single payment(FBZP - Payment Methods in Company Code):

coleti_0-1719315744954.png

 

2nd consideration: check your Vendor Master Data Individual Payment Indicator:

coleti_1-1719315946664.png

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.

 

I hope this could help you on that. Anyway the aggregation will automatically set if these considerations allow grouping items and not individual payment.

 

BR,

 

Gabriel Coleti

 

 

 

 

 

 

 

mmklodz
Explorer
0 Kudos

Thank you for your tips.

I checked configuration and vendor md. It looks ok. 
Proposal works the same. 

mmklodz_0-1719321309487.png

mmklodz_1-1719321418731.png

The more I read about it, the more I have a strong feeling that this is the correct behavior of SAP and cannot be changed with standard configuration.

Michal

coleti
Active Contributor
0 Kudos
On your Vendor Master Data we have defined only Payment Method "C" and in the configuration FBZP you are sharing payment method "K". As I could see, you open item also don´t have payment method defined... so it´s a problem. You should have specfied in the Open Item, the Payment Method or in the Vendor Master because the aggregation logic is done as per payment method. In this case, during the proposal run, neither Vendor nor Open Item is setting the proper payment method "K". That will generating a manual task from your users to reallocate this in the proposal.
mmklodz
Explorer
0 Kudos

I dont believe that this is the issue but lets try, this is the SAP. 

Like you can see before all changes in the first run of proposal SAP aggregate document correctly. 
It looks like SAP don't repeat aggregation on edit mode.

I changed payment method on customer and vendor MD also for documents.
first run of proposal is correct, after edit payment block behavior of the system is the same. 

mmklodz_1-1719387230306.png

mmklodz_2-1719387429274.png