Advertising:
Classic extensibility: Difference between revisions
From SAP Knowledge Base
No edit summary |
No edit summary |
||
Line 6: | Line 6: | ||
|- | |- | ||
|'''Purpose''' | |'''Purpose''' | ||
|'''Type | |'''Type | ||
|'''Name''' | |'''Name''' | ||
|'''Trigger''' | |'''Trigger''' |
Revision as of 12:26, 27 December 2024
All classic extension options are listed here. All listed BAdIs are classic that means for onPremise (private cloud) systems.
Purpose | Type | Name | Trigger |
Finance (FI) | |||
---|---|---|---|
Adjust batch input folders before bookings after uploading the account statement | BAdI | FEB_BADI - Method CHANGE_POSTING_DATA | Execution Tcode FF_5 |
Change of external document with BAPI_ACC_DOCUMENT_POST | BAdI | ACC_DOCUMENT - Method CHANGE | Execution of BAPI_ACC_DOCUMENT_POST if extension parameter 'extension2' is maintained |
Adjust raw data from upload of an account statement 'MT940' | Customer Exit | FEB00004 - Exit fm EXIT_RFEKA400_001 | Execution Tcode FF_5 with format MT940 so that program RFEKA400 is called |
Materials Management (MM) | |||
Different ToDos when saving and updating in reservation, e.g. creating outbound IDoc MRESCR | Customer Exit | MBCF0007 - EXIT_SAPMM07R_001 | Saving/changing the reservation with MB21/22 |
Production Planning and Control (PP) | |||
Different extension in transaction code COOIS | BAdI | WORKORDER_INFOSYSTEM | Several e.g. after selection / layout output |