среда, 15 января 2014 г.

SAP, Automatic payment program, payment method supplement

So why you need payment method supplement on top of payment method you define on master data and in FBZP t-code.

Here is my very short configuration guide on that:

So start from configuration of your payment method on a company code level:

As it is shown on screenshot above, de-select 'Single payment' option. That's it, save.

Then go to master data of vendor/customer:

On a payment transactions screen de-select 'Individual payment' option and define grouping method, the one that will be used when running F110 t-code in order to merge different invoices using same payment method into one payment order.
Does it makes any sense? :)
What I am trying to say is that This groups line items by using payment method supplement ‘22’, not by vendor in payment order, i.e. if there are 4 invoices with the same payment method, APP generates single payment order for these 4 invoices, grouping them by payment supplement method.

Now run F110, proposal run:


On a screen above we see 2 invoices that were merged into one payment order, with '22' payment supplement method, which means now payment orders will be generated not by vendors, but by payment supplement key, defined in FBZP t-code and in master data.

And let's see payment order that was generated by APP (Environment menu, then go to Payment orders- Display):


That's about it :) 

Later on I am planning to upload my config journal about DMEE tree configuration... But it is huge one, since it covers configurations of APP, once I have more time on that, I will upload that one. Cause as far as I know, there is nor proper information regarding DME engine on the Internet, you don't have it in SAP training courses (they just mention that, but no config exercises and etc.). 




4 комментария: