Using Events to Schedule Creation Dates 

Use

You can use events to control the way in which bank statements are created, and include additional information on the bank statement. You have the following options:

●      You can schedule bank statement creation dates as events for all the bank statement agreements of an account.

●      You can schedule an event whose date is output either on or before the due date, and that triggers the creation of a bank statement in the mass run.

●      You can schedule an event that triggers the creation of a bank statement on the next periodic due date in the mass run, or if there is a request at the bank statement printer, even if no items were selected.

●      You can schedule an event whose data is output during the creation of a bank statement at the next periodic due date in the mass run, or if there is a request at the bank statement printer, if the next settlement data of the corresponding period is on the bank statement.

Prerequisites

To create event-controlled bank statements, you need to make the following settings in the Customizing for Account Management (FS-AM) under Item Management ® Bank Statement ® Triggering Events for Event-Controlled Bank Statements:

●      Define Events

In this IMG activity, you determine, for example, the due date category of the event. In addition, you can decide whether the event is to be scheduled with or without the due date. For more information, see the sections on scheduling events and on the due date categories.

●      Set up Event-Control Parameters

In this IMG activity, you determine, for example, the maximum period of time in which an event-controlled bank statement must be printed. For more information, see the documentation on the data element BCA_DTE_SHIFT_DAYS (shift by x days), in the section on scheduling events, and under Displaying Settlement Information on the Bank Statement in the SAP Library.

To create an event-controlled bank statement for payment items, returns, standing orders, or payment orders, you need to enter the following settings in the Customizing for Account Management:

●        For payment items, choose Item Management  ® Basic Functions ® Transaction Types and Transaction Type Groups ® Maintain and Assign Transaction Types for Payment Items

●        For returns, choose Item Management  ® Basic Functions ® Returns  ® Define Returnable Transaction Types

●        For payment orders, choose Order Management  ® Payment Order ® Select Trigger for Event-Controlled Bank Statement

●        For standing orders, choose Order Management  ® Standing Orders ® Select Trigger for Event-Controlled Bank Statement

Structure

Scheduling Events

If you schedule a due date for an event, the event is processed in the mass run for the bank statement creation once the due date is reached, and its data is included on the bank statement. A bank statement is also output even if no items are selected at this time.

The due date is calculated according to how the scheduling is done.

You can schedule an event with or without a due date:

●      You need to schedule events with a due date if you assigned them with the due date category At Latest On or On.

●      You can schedule events either with or without the due date if you assigned them with the due date category With Next Bank Statement, Also Without Items or With Next Settlement Dates of Corresponding Period.

To schedule a due date, ensure that the Without Date indicator is not set in the IMG activity Define Events.

If you do not want to schedule a due date, ensure that the Without Date indicator is set in the IMG activity Define Events.

For more information, see the documentation of the data element BCA_DTE_BAST_FLG_NO_DUE_DATE (Schedule Event Without Due Date).

For more information, see below under Due Date Categories.

You have the following options for scheduling an event:

●      By means of a process

For information on the Customizing settings for scheduling via processes, see above under Prerequisites.

You can schedule events as result of the following business processes:

○       A payment item is posted with a specific transaction type.

○       A payment item is returned

○       The execution of a standing order or payment item is rejected.

To schedule a due date, define it in the IMG activity Set Up Event-Control Parameters. The number of days that you enter in the Shift by x Days field is added to the posting date of the payment transaction. This is how the system calculates the due date.

●      Manual

Proceed as under Display and Edit Creation Dates.

If you want to schedule using a due date, enter the due date when you create the event.

●      By means of a Business Application Programming Interface (BAPI)

Events in the due date category With Next Settlement Data of Corresponding Period can only be scheduled with the method BankStatement.AddEvent (BAPI_BCA_BANKSTMT_ADD_EVENT).

For more information, see the documentation on the method in the BAPI Explorer.

To schedule a due date, define it by using the SHIFT_DAYS parameter (shift by x days).

If the parameter is not filled when the method is called, the system uses the value from the Shift by x Days field in the IMG activity Set Up Event-Control Parameters.

The number of days that you enter in the relevant field is added to the posting date of the payment transaction. This is how the system calculates the due date.

Due date categories

●      At Latest On

The event data is output once a bank statement is created or once the due date has been reached.

You need to schedule events from this due date category with a due date. For more information, see above under Scheduling Events.

You can schedule events from this due date category via a process, manually, or by using a BAPI.

You can use this due date category to meet certain legal requirements, for example, regulation E of the Federal Reserve Board in the USA.

●      On

The event data is output once the due date is reached.

You need to schedule events from this due date category with a due date. For more information, see above under Scheduling Events.

You can schedule events from this due date category via a process, manually, or by using a BAPI.

●      With Next Bank Statement, Also Without Items

The event data is output once a bank statement is created. A bank statement is created even if no items were selected.

You can schedule events from this due date category with a due date. For more information, see above under Scheduling Events.

You can schedule events from this due date category via a process, manually, or by using a BAPI.

●      With Next Settlement Dates of Corresponding Period

The event data is output once a bank statement is created that contains information on settlement data from the period whose settlement was defined in the event. When you are scheduling, you must always specify a reference to the corresponding settlement (reference to event). The corresponding period is defined if the settlement type and settlement period match.

You can schedule events from this due date category with a due date. For more information, see above under Scheduling Events.

You can schedule events from this due date category with a BAPI only.

For comprehensive examples of all four due date categories, see Application Examples of Due Date Categories.

Customer Enhancements

●      Scheduling Events

○       Method BankStatement.AddEvent (BAPI_BCA_BANKSTMT_ADD_EVENT)

●      Scheduling and evaluating events

○       Business Transaction Events (BTE)

■       BTE 0BCA4470

The BTE is called when the settlement is run.

For an application example with a description of the required settings, see Application Examples of Due Date Categories under With Next Bank Statement, Also Without Items (Account Settlement)

■       BTE 0BCA4180

The BTE is called when the settlement reversal is run.

For an application example with a description of the required settings, see Application Examples of Due Date Categories under With Next Settlement Data of Corresponding Period (Reversal Settlement, Correction Settlement)

■       User exit include in application forms from the form class BCA_BANK_STATEMENT

The user exit include is called by the Print Workbench when the bank statements are output that were created in the mass run or single run.

For an application example with a description of the required settings, see Application Examples of Due Date Categories under With Next Bank Statement, Also Without Items (Account Settlement)

■       BTE 0BCA3132

The BTE is called by the method BankStatement.Execute if the bank statement creation was requested at the bank statement printer.

For an application example with a description of the required settings, see Application Examples of Due Date Categories under With Next Bank Statement, Also Without Items (Account Settlement)