2.1 Postprocessing Transaction FEBAN

In contrast to FEBA, transaction FEBAN appears clearer and offers more information for postprocessing documents. Numerous small enhancements also ensure a certain degree of flexibility and enable adjustments to individual requirements for bank statement posting. As an example, the following points aim to show how you can adapt the postprocessing further to your requirements.

In the standard SAP system, the following are available for users for further processing of bank statements:

• Tree display
• Grid display (table display)

In the standard system, the bank statements are generally selected via the tree display. However, the standard format is rather spartan and provides insufficient information for the selected house bank.

Therefore, if the tree display is not required here, you can use Note 1741730 to define the default display (tree or grid display) via the user parameter FEBAN_DEF_DISPLAY. Furthermore, you can replace the standard tree with a customer-specific tree using enhancement 2870 of the Business Transaction Event (BTE). After implementing Notes 725650 and 738353, as illustrated in Figure 2.2, a total of three display levels are available:

• Level 1: own house bank (house bank from FI12), company code, and bank ID (e.g., bank number)
• Level 2: own account (account ID from transaction FI12), account number
• Level 3: statement number, statement date, short ID, and closing balance

Figure 2.2: Customer-specific tree for postprocessing with FEBAN

During the import, the SAP standard system automatically creates a payment advice for postings that were not successful in posting area 2 (subledger). Therefore, the payment advices created have to be selected during document postprocessing—meaning additional work that is generally unwelcome to the user. You can use Note 452579 to suppress the creation of payment advices in transaction FEBAN, and the customer or vendor to be corrected can be selected immediately. If necessary, you may have to install this note across all release versions.

Another option for displaying bank statements is via the grid or table display. You can switch to this view via the icon. This display increases the flexibility of the postprocessing even further. On one hand, you can adapt the layout to your own needs by displaying additional optional fields. With this view, you can also change the posting rules for incorrect documents (see Figure 2.3). In Customizing, the business transaction codes (BTCs) are usually defined in a posting rule. However, this assignment is not always correct, meaning that line items can be interpreted incorrectly.

Figure 2.3: Changing the posting rules in the grid or table display

If you want to change an incorrect item, in the grid or table display, select the posting rule to be changed and select a suitable rule for the document. The document can now be interpreted accordingly and the document posted with the new, appropriate rule.