End-of-Day Processing as Event Control 
Use
The following section describes how to use event control to organize end-of-day processing. You schedule the relevant reports as jobs with the Job Definition transaction. This means that they run automatically.
Events have been defined for each function to control these jobs. These events inform the job administration when the function has run successfully. Therefore, the next step is started only once the final event of the previous function has been reached. The previous job must be defined in the subsequent jobs. You can do this with the Start After Event XY attribute. If this is a general step that applies to more than one bank area, then it is triggered more than once. The parameter is the bank area.
The following table provides an overview of the report and the corresponding events (the events relating to standing orders and fixed-term deposits apply only to banks):
Report name |
Event DescriptionSAP_BKK_… |
Description |
|---|---|---|
RFBKCONA |
ACCRUAL_JOB_END |
End of job processing ‘interest accrual/deferral’ |
RFBKACCL |
ACCNTCL_JOB_END |
End of job processing ‘account closure’ |
RFBKBSST |
BANKSTAT_JOB_END |
End of job processing ‘bank statement’ |
RFBKKC20 |
CASH_CONCENTR_JOB_END |
End of job processing ‘cash concentration’ |
RFBKCONC |
CLOSING_JOB_END |
End of job processing ‘account balancing’ |
RFBKCLEB |
CLOSPOSTDAT_JOB_END |
End of job processing ‘set balancing posting date’ |
RFBKSOCR (obsolete from EA-FINSERV 200) |
STANDORDER_JOB_END |
End of job processing ‘standing order’ |
RFBKSOCRPAR (new from EA-FINSERV 200) |
STANDORDER_JOB_END |
End of job processing ‘standing order’ |
RFBKPDT2 |
PAYMPOSTDAT_JOB_END |
End of job processing ‘set payment transactions posting date’ |
RFBKGLBSPREP |
BSPREB_JOB_END |
End of job processing ‘balance sheet preparation’ |
RFBKGL01 |
GLTRANSFER_JOB_END |
End of job processing ‘general ledger transfer’ |
RFBKTTERMCONTROL (changed for EA-FINSERV 500) |
TERMCONTROL_JOB_END |
End of job processing ‘fix fixed-term deposit’ |
RFBKTTTERMMATURE (new for EA-FINSERV 500) |
TERMDEP_MATURE_JOB_END |
End of job processing ‘call fixed-term deposit’ |
RFBKTDEPOSITCOLLECTION |
TERMDEP_COLLECT_JOB_END |
End of job processing ‘collect deposit amount for fixed-term deposit’ |
RFBKTTERMPRENOTICE |
TERMPRENOT_JOB_END |
End of job processing ‘prenotification of maturity for fixed-term deposit’ |
RFBKGL_VA_CALC_POST |
VALUE_ADJ_JOB_END |
End of job processing ‘value adjustment’ |
The final event of a function in a chain is triggered if:
All accounts have been processed and
Processing was successful.
On some accounts, errors may have occurred during processing, for example, because they were not active. These accounts are locked for all further steps of the run. However, the event is triggered so that processing can continue for the remaining accounts.
If this is the case, proceed as follows to check the accounts:
In the overview of the mass runs, determine the mass runs where errors occurred. Note the key (program name, date, and number) of each run. See also Displaying Overview of Mass Runs .
Use the overview of the locked accounts to find each locked account. See also Displaying an Overview of Locked Accounts .
In the application log, determine the run where an error occurred (marked red). The log provides you with more details of the reason for account lock. You can call up specific application logs by choosing
Periodic Tasks 
End-of-Day Processing Application Logsfrom the SAP Easy Access menu. 
Correct the error and start each mass run by choosing Restart , or Restart Individual Step . This removes the lock from the account. See also Display Report Overview / Control End-of-Day Processing Chain . In some applications you can also restart the job by choosing
Periodic Tasks <application> Restart.
In this case the status is also changed in the chain.
Start all the subsequent mass runs of the job by choosing Restart . These process the account accordingly. See also Displaying Report Overview/Controlling End-of-Day Processing Chain .
The event is not triggered if a mass run was terminated (for example, due to a system error). If this is the case, the accounts of the subsequent runs are not processed, and the batch processing is interrupted. The corresponding runs must also be started with Restart or Restart Individual Step .