SAP R/3 форум ABAP консультантов

[admin]

Symptom
By now, the electronic bank statement contains a variety of options that you enhance by using programming. This note provides you with an overview of these enhancements.
Note: As of Release 4.6B, you can now use the search string function to search the note to payee simply by using Customizing and (as of Release 4.6C) you can also change the bank data storage so that these user exits are unnecessary in many cases. For more information on this subject, refer to point 'Define Search String for Electronic Bank Statement' in Customizing for the electronic bank statement.
In the user exit (regardless which one), do not program any COMMIT WORK nor, in particular, any ROLLBACK WORK as they may result in inconsistencies in the database.

Other terms
Bank statement, BADI, USEREXIT, OPEN, FI, RFEBBU10, RFEBBU00

Solution
1. User exit FEB00001: For the documentation and the implementation of this enhancement, go to the point 'Develop Enhancements for Electronic Bank Statement (General)' in Customizing for the electronic bank statement. This user exit is called immediately after the interpretation of the note to payee in program RFEBBU10.
2. As of Release 4.70, there is a Business Add-In (BADI) with definition name FIEB_CHANGE_BS_DATA that is called before the interpretation algorithms and before the search string in program RFEBBU10. For the implementation go to the SAP menu, choose 'Tools->ABAP Workbench->Business Add-In', and create an enhancement that you assign to the BAdI FIEB_CHANGE_BS_DATA and implement method CHANGE_DATA. You use the BADI to change the bank data storage before the standard interpretation of the note to payee.
3. As of Release 45B, you can implement Open FI modules for the callup points 2810 and 2820. For general information about the Open FI / BTE function, go to 'Financial Accounting->Financial Accounting Basic Settings -> Business Transaction Events' in Customizing. For the callup points in the bank statement, choose 'Environment->Info system (P/S)' or 'Environment->Infosystem (Processes)' and enter interfaces 00002810 and 00002820 respectively. Then you see the sample function module and the documentation for the corresponding interface. The following is a brief summary of these interfaces:
a) The Publish & Subscribe interface 2810 is used for the registration of a line item for the processing through the respective application. Note in particular, that for the registration under Settings -> P/S function module of an SAP application (of a partner or of a customer) you need to define not only the function module but also an application. As a standard application, you can simply select FI-BA. In this case, you can also decide whether you want to suppress the standard posting for the line item. The respective function module is called before the interpretation algorithms and the search string.
b) The process interface 2820 is used for changing bank statement data. The respective module is called immediately after module Publish & Subscribe 2810 (therefore, also before the search string and the interpretation algorithms). In this case, you can change the bank data storage as in BADI FIEB_CHANGE_BS_DATA (see point 2). The module is only called if the P/S module 2810 has been implemented and if it is registered for the memo record.
c) The process interface 2810 is used to update a sale. The module is called in the posting RFEBBU00 report if the P/S module 2810 is registered for these sales.
d) The Publish & Subscribe interface 2820 is used for the display of the documents that were posted in process 2810 in postprocessing. The function module is called during the display of a line item in the postprocessing transaction (FEBA) by choosing the 'Document' button.
4. As of Release 4.70, there is a Business Add-In (BADI) with the definition name FEB_BADI that is called immediately before the standard posting in program RFEBBU00. In this case, you can change the procedure of the standard posting or make additional account assignments by changing the tables that are to be transferred to the posting interface (FTPOST, FTCLEAR). To do this, go to the SAP menu and follow the path Tools->ABAP-Workbench->Business Add-ins, create an enhancement that you assign to the FEB_BADI BAdI and then implement the CHANGE_POSTING_DATA method.
When you activate the BAdI, you receive a message, telling you that the active implementation of this BAdI already exists. If you do not use the public sector industry solution, you can deactivate the active BAdI of the IBS_PS area and activate your own implementation.
5. As of Release 3.1I, to change the standard posting you can also write your own function module that is called at the same callup point as the BAdI FEB_BADI (see point 4). For this, you have to register in user exit FEB00001 (see point 1) for the memo record first. To do this, attach a row to table t_febcl with t_febcl-selfd = 'FB' and t_febcl-selvon = 'Z_FEB_1_ZZZZ', if you want to make a change in posting area 1 or with t_febcl-selfd = 'FB' and t_febcl-selvon = 'change Z_FEB_2_ZZZZ', for changes in posting area 2. Z_FEB_1_ZZZZ or Z_FEB_2_ZZZZ are the names of the function modules for the respective areas. Here you can also select other names; however, the name of the module that is called in the area 1 must contain character string FEB_1_ and the same applies for the name of the function module of area 2 - it must contain FEB_2_. The interface of both modules must be the same as the interface of module FEB_2_STO_LASTSCHR2 or FEB_2_IMMO_LASTSCHR.
6. Enterprise Add-On EA-FIN provides the new postprocessing transaction (Transaction FEBAN or FEBA, if the add-on is set to active). For Release 2.0 of this add-on there are the following Open-FI events:
a) 2830 process: Application-specific display in the subscreen.
b) 2830 P/S: Transfer of the OK code to the application subscreen.
c) 2840 P/S: Application-specific display in the subscreen which is not item-related and which does not switch off the standard display unlike event 2830. Up to five subscreens may be included here.
d) 2850 P/S and process: Intervention when changing the bank data storage in postprocessing. This allows you to automate the filling of certain fields with the same values in postprocessing: If you change one field in the bank data storage, other fields are changed automatically.
e) 2860 process: Allows a third posting (except for posting area 1 and 2) that is only possible in postprocessing. If you carry out this posting you should display the posted document (field FEBEP-SDOC2) in postprocessing. For this purpose use event 2830 (see above).
f) 2870 process: Replace the tree or list display in postprocessing. You may also replace only one of the two with a separate display.
g) 2880 P/S and process: Replace the selection screen through with a separate selection screen.

7. As of Release 4.70 there are two Business Add-Ins for processing returned debit memos:
a) The first has the definition name FIEB_RETURNS_ADDIN and is used to read charges from the note to payee. In Customizing for the bank statement under point 'Business Add-In: Processing of Returns', you will find the documentation of this BAdI. From there you can directly call the BAdI Builder.
b) The second BAdI has the definition name FIEB_RET_CHANGE_DOC. Here you can control the document change of the document which is open again after the clearing reset. Refer to Note 576768 for this purpose.

Beside these enhancements there are still some format-specific enhancements.
For this, go to 'Develop Enhancements for Elec.Bank Statement (Format Spec.)'

8. Exit FEB00002 is called at the conversion of the Belgian Coda format to Multicash format in program RFEBBE00.
9. Exit FEB00003 is called at the import of the Finnish TITO format in program RFEBFI20.
10. Exit FEB00004 is called at the import of SWIFT MT940 in program RFEKA400.
11. FEDI0005: This is used to change the bank data storage and the internal payment advice notes (also refer to Note 501966) with the inbound EDI for account statement FINSTA01. Note that you must implement ALL components (=function modules), that is at least set the export parameters equal to the import parameters, so that the bank data storage is not initialized.
12. As of Release 4.6C, you can allocate a 'customer-specific interpretation algorithm' to an external transaction code in Customizing. If such an algorithm is set, first the standard algorithm 001 will run, and then you can perform a separate interpretation in user exit FEB00001. To suppress the standard algorithm here, see Note 414233. As of Release 470 you can implement the algorithms in function modules with Note 597428.

Header Data

Release Status: Released for Customer
Released on: 19.10.2005 12:52:10
Priority: Recommendations/additional info
Category: Consulting
Primary Component: FI-BL-PT-BA bank statement
Release-Independent

Related Notes

935218 - FEBAN: BTE 2850 standard posting is not suppressed
907386 - Account statement: Intervals not available in user exit
770215 - ZEV: BTE 2850 and RFC
738353 - Postprocessing account statement (new): BTE 2870
597428 - El.accnt statement: Customer-specific interpret.algorithms
549277 - FAQ: Electronic account statement
414233 - Accnt statement:customer-specific interpretation algorithms