This document explains how you specify which scenario(s) to apply for the individual bank statement transactions during bank statement allocation.
For each type of bank statement transaction, you can specify several scenarios and prioritize them amongst themselves, thereby considerably increasing the part of the allocation that can be done automatically.
You have controlled how the allocation of a certain type of bank statement transaction will be carried out.
When you select the automatic allocation option in 'Bank Statement. Open' (ABS100) for a statement, or when the allocation is started in some other way, the bank statement transactions will be processed according to the scenario(s) for the respective type of statement transaction.
The 'Scenario number priority' (FABTAB) file is updated.
|Program ID/Panel||Field||The field indicates …|
|(ABS910/E)||Start value 1–5||
… the value for one of the five fields that can be used as start values: bank account ID, transaction type, business transaction code, transaction text and debit/credit code.
The values specified for these fields together identify a certain type of bank statement transaction. For each type of transaction, you can connect five scenarios, which control how the allocation will be carried out.
Note that the valid values that exist for each of the five fields are controlled by the bank (except bank account IDs, which are defined in CRS692). For example, an extract from a list of valid business transaction codes provided by a German bank, might look like this:
Code Explanation:010 Direct debit020 Payment order070 Deposit of checks.
You want to control how to allocate invoices to statement lines that refer to payment orders for bank account 9999-99.
Background: Bank account ID is used as start value 1 and the bank account ID in this case is 9999-99. The business transaction code is used as start value 2, and the code for payment orders is 020.
Solution: Create a record by specifying bank account ID 9999-99 and business transaction code 020. On the E panel, specify which scenario(s) to apply when allocating the payment order transactions.
The fields that are used as start values 1–5 are predefined. The fields are defined in 'Generic Object Control Table. Open' (CRS016), for (ABS910).
|(ABS910/E)||Scenario number priority 1–5||
… the scenario that applies during the allocation of a certain type of bank statement transaction.
A scenario is a set of rules controlling how the allocation of a bank statement transaction is done. The scenario can for example search after, and allocate, an invoice to the line or create an on-account payment.
Up to five scenarios can be used, and they are prioritized amongst themselves. The scenario with number priority 1 has the highest priority and so on. If a scenario fails, the next one applies.
You want to allocate supplier invoices to payment orders in bank account 9999-99. If no invoices are found, you want to create an on account payment in accounts payable for the order.
Solution: Create a record for bank account 9999-99 and payment orders using the start values that your company uses for identifying different types of transactions. Specify the scenario that searches for an invoice to allocate as scenario number priority 1 and the scenario that create an on account payment as scenario number priority 2.
Start 'Scenario Number Priority. Open' (ABS910/B). Set the panel sequence to E.
Define a type of bank statement transaction, by specifying values in the 'Start values 1–5' fields. Select New.
On the E panel, specify the first scenario to apply for the type of statement transaction in the 'Scenario number priority 1' field.
If other scenarios should apply if the first one fails, specify these scenarios in the other scenario number priority fields. Press Enter.