24-Hour Capability of the Single Transaction Check 

Definition

The purpose of the 24-hour capability is to enable you to carry out a single transaction check (STC) at any time, and in particular when end-of-day processing is running. This also affects the integrated default risk limit check, which is available in TRM Credit Risk Analyzer only. Furthermore, the 24-hour capability enables you to enter reservations at any time.

If you use the non-integrated single transaction check, as it is used in Banking, in conjunction with the 24-hour capability, the results are consistent only for new transactions and external transactions. Note that changes to data pool transactions can be taken into account only if the transactions are first changed using EDT, and are then additionally changed using the single transaction check. The single transaction check is required in this case for triggering the post-run update.

Use

You activate the 24-hour capability in Customizing by choosing: ® Limit Management ® Enter Basic Settings for Limit Management. In addition to activating 24-hour capability, you make other settings here for the single transaction check:

·        Waiting time for the single transaction check

·        Posting deadline

·        Waiting time for the post-run update

·        Setting the indicator for 24-hour capability

When using the single transaction check, it may sometimes be the case that the limit you are checking is blocked by another user. For this reason, you have to enter a maximum waiting time in the basic settings. As part of the 24-hour capability, by entering a posting deadline you are able to specify a fixed point in time after which risk amounts are to be attributed to the following day. The waiting time for the post-run update specifies the time gap between the post-run update and the posting deadline.

Structure

End-of-day processing comprises the generation of utilizations and the post-run update. (As the post-run update is part of end-of-day processing, updating takes place in status 1 and 2.) All the transactions for the day, which were checked by the single transaction check during the generation of utilizations, are updated in the post-run update. In this way, it is possible to apply the single transaction check even during the end-of-day processing run.

If a single transaction check function is started before the end-of-day processing run has finished, the transactions checked by the single transaction check function are updated to the date of the previous end-of-day processing run. The current end-of-day processing run then updates these transactions to the new date.

Exception

When you enter the settings in Customizing, ensure that there is sufficient time between the end of the generation of utilizations and the posting deadline to allow for the post-run update. If this is not the case, it can cause the post-run update to exceed the posting deadline. In this case, the single transaction check is locked for the period of time between the posting deadline and the final completion of the end-of-day processing run.

To avoid this, in Customizing you can leave the field for the posting deadline blank.