Ansicht
Dokumentation
SAMPLE_INTERFACE_00010038 - Event Controlled Bank Statement (Non-Periodic)
ABAP Short Reference BAL Application Log DocumentationThis documentation is copyright by SAP AG.
Functionality
You can use this event to determine whether a bank statement must be generated for the following events:
- Posting of a payment item or payment order
- Fixing of a term agreement
You can, for example, generate a bank statement in the following scenarios:
- Credit postings over a certain value
- Payment item postings of a particular transaction type
- Payment item postings from a direct debit
The BTE transfers payment item details such as the following:
- Item number
- Internal and external account number
- Bank Area
- Transaction type and amount
- Business partner details
- Note:
- You must implement the BTE so that it returns the "X" flag when a bank statement is to be generated. Bank statements are generated for accounts that have this flag set during the next bank statement mass run.
- After the event-based statement is generated, future statements are triggered based on your settings in the account master.
The BTE sets the return parameter (E_RETURN) if the processing fails and logs the error messages in the application log.
Example
Notes
Further information
Parameters
E_PRNT_BANKSTAT_XE_RETURN
I_ITEM
T_MESG
Exceptions
Function Group
FBI2BAL Application Log Documentation PERFORM Short Reference
This documentation is copyright by SAP AG.
Length: 1852 Date: 20240603 Time: 223214 sap01-206 ( 30 ms )