on 02-13-2019 3:09 AM
Hi,
In the 'Clear Incoming Payments' app, if I go to the 'payment reference' tab and then enter a payment advice that I have manually created, what basis should the system be using for proposing items to be cleared?
As far as I can see, the system seems to only recognise 'journal entry' as a field on which to propose items for clearing - this is obviously of very limited practical use, since the customer will never supply this reference (as it is the internal FI document number). My assumption is that the customer would provide a 'reference document no' (or we could put this value in the 'assignment' field on the payment advice) - these equate to the SD billing document number.
In the On Prem / ECC world, I would have always set the number ranges up such that the FI document always had the same number as the SD billing document - but this is not an option in S4HC.
Am I missing something - or is this a bug?
Hi Clare,
You can enter the Invoice number , Customer number , payment reference or reason for payment in the "Payment Reference" field . Do any of these work for you?
Regards,
Anirban
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Damn - posted a lengthy response - but my laptop seems to have swallowed it.
In this scenario, I am wanting to clear multiple invoices - which I have added to a payment advice. I am therefore entering in the 'payment advice' rather than 'payment reference' field on the clearing transaction.
On the payment advice itself, it would appear that the only field that works in selecting the correct line items for clearing is 'journal no' - which a customer would never supply - so it appears to me that this functionality does not work correctly - unless I am missing something obvious
Hi Clare,
In this case , suggest you raise this topic in the Customer Influence Portal https://influence.sap.com/ .
Regards,
Anirban
User | Count |
---|---|
97 | |
11 | |
11 | |
6 | |
6 | |
4 | |
4 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.