Transferring Payment Data by Web Service
Depending on your system settings, real-time payments can be processed synchronously or asynchronously.
In the case of asynchronous processing, the ERP system receives the data, submits it to a technical check, and then stores it in the appropriate tables of external cash desk services (DFKKEXC
, DFKKEXC_ADD
).
Then the processing of the payment begins asynchronously. Errors can occur, for example because business partners are blocked for this processing. In those cases, the system notes this and assigns an appropriate status. Follow-on processing might then be necessary.
Once the lock is removed, you can post the payment from the SAP Easy Access screen by choosing 
Payments
Real-Time Payments
and then choosing 
Repeat
(Post Real-Time Payment Again
) in the monitor.
Or you can repeat the posting from the SAP Easy Access screen under Payments
Real-Time Payments
Repeat Posting
.
You can repeat the posting until it is successful.
A service is available that enables you to find out the status of processing at any time.
Note
Repeating the posting is not recommended for payments with certain statuses. However, using event 6232, you can have the system allow a repetition, for example, even for payments with the status “Bank Was Informed, Waiting for Bank Response”. This is useful, for example, if the bank explicitly requests that the data be resent. For more information, see the documentation for the function module FKK_SAMPLE_6232
.
Note
When processing a real-time payment, you can update additional log data in event 6231. You can display this data in the monitor by choosing 
Log
(Display Log
). You can generate the log entries yourself in your own implementations of events, such as 6207, 6208, 6021, 6231, 1400, and 1402. For more information, see the documentation for the function module FKK_SAMPLE_6231
.
Updating this log data can be useful, for example for tests, for researching errors, or for explaining the rejection of payments.