Process Flow of End-of-Day Processing
End-of-day processing can be carried out daily or at longer intervals, depending on how current the data needs to be.
Prerequisites
Before you start end-of-day processing, it is advisable to execute some programs (reports) several times during the day (approximately every two hours) by using a job. The reports must run at least once, directly before the posting cut-off for payment transactions and the other end-of-day processing steps.
Take note of the following reports:
Report RBCA_PO_RESEND_EXTERN (Repeated Transfer of Payment Orders to PTS)
During payment order processing where there is at least one external recipient, the system transfers the order to the feeder system to determine the routing. If communication errors occur, the system flags the order with an error indicator. The report selects all these payment orders and sends the information once again to the previous/feeder system. If this corrects the error, the error indicator is removed and the payment order is completely edited. If the error still persists, the error indicator remains and the payment order is selected again during the next run.
Report RBCA_PAYMITEM_PROCESS_ENQ (Post Payment Items from BCA_PAYMITEM_ENQ in BCA_PAYMITEM)
This report ensures the correct posting of the payment items that were placed in a special table during daily business.
When a payment item comes to Account Management by way of the payment transaction system, the system checks, as part of the item check, whether the account is technically available or locked by other competing activities. If this is the case, the system places the item in a queue. You can use the report to process this queue at a later time.
Process
End-of-day processing includes the following tasks that need to be carried out periodically:
Set Posting Date for Payment Transactions (RBCA_DATE_POST_SET)
This is where you increase the current date for payment transactions. This operation is described as the
Posting Cut-Off
. All payment transaction postings have the new date that you specified (taking account of the posting calendar). We recommend that you execute the posting cut-off before any other settlement tasks (such as account settlement) to ensure that there are no additional postings during the period being settled during the account settlement run (value dates in the past are still possible). The posting date for end-of-day processing remains unaffected and thus generally falls (if executed daily) on the last posting date for payment transactions. The posting date for end-of-day processing is not increased until the end of end-of-day processing.Run Account Settlement (RBCA_SETTLE_RUN_PP)
See Account Settlement.
The system calculates interest and charges for the accounts due for settlement and posts them on the respective accounts.
Execute Interest and Charge Accrual/Deferral (RBCA_ACCRUE_RUN_PP)
See Accruing/Deferring Account Results.
The accrual/deferral of the interest already incurred but not yet posted can be calculated separately from the other periodic tasks, particularly account settlement.
Increase Posting Date for End-of-Day Processing (RBCA_DATE_CLOSE_SET)
After all the settlement tasks are completed, the posting date for end-of-day processing is increased. You need to increase the posting date every working day, even if no account settlement has taken place.
If you have the same settlement and bank statement dates for all your accounts within the selected bank posting area, (for example, end of the quarter), you do not need to execute the account settlement and bank statement runs daily, but only on this date. If you do not settle the accounts daily but, for example, monthly, note the following:
Do not increase the posting date for end-of-day processing beyond the last bank working day of this period until the period settlement for all accounts has taken place. If you settle the account on a day in the following period, proceed as follows: Set the posting date for end-of-day processing on the last day of the old period and do not change this until the settlement has been executed.
Due Product Changes (RBCA_OR_COP_TEV_START_BCA_BOCP)
Execute Bank Statement Run (RBCA_BAST_RUN_PP)
This involves a mass run in which all the bank statement data is generated for all agreements for accounts due for the issuing of a bank statement, and correspondence requests are created.
Post Standing Orders (RBCA_SORD_RUN_PP)
The system selects the standing orders due for the current posting date. Postings are created (with the current posting date for payment transactions) and transferred to the payment transaction system.
If you adhere to this sequence in end-of-day processing, the system generates the standing orders that are due for the following day, since the posting cut-off has already been made. This ensures that the orders are placed in external payment transactions in good time.