Advertising:

Classic extensibility: Difference between revisions

From SAP Knowledge Base
No edit summary
 
(23 intermediate revisions by the same user not shown)
Line 1: Line 1:
[[Category:In-App]]
{{Template:MetaDesc|A list of extension options in onPremise and cloud private systems for various areas in the system with purpose, name, type and trigger point of the extension.}}
= Business Add-Ins =
[[Category:In-App_Extensibility]]
All classic extension options are listed here.
All listed BAdIs are classic that means for onPremise (private S/4 Cloud) systems.


= Customer Exits =
{| class="wikitable" style="width:100%;"
 
|-
= User Exit =
|'''Purpose'''
|'''Type
|'''Name'''
|'''Trigger'''
|-
!colspan="4"|Finance (FI)
|-
|Adjust batch input folders before bookings after uploading the account statement
|BAdI
|[[Classic_BAdI_FEB_BADI|FEB_BADI]]  - Method CHANGE_POSTING_DATA
|Execution Tcode FF_5
|-
|Change of external document with [[document_posting_in_finance_with_fm_BAPI_ACC_DOCUMENT_POST|BAPI_ACC_DOCUMENT_POST]]
|BAdI
|[[Classic_BAdI_ACC_DOCUMENT|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
|-
!colspan="4"|Materials Management (MM)
|-
|Different ToDos when create a good , e.g. creating outbound [[IDoc_message_type_MRESCR|IDoc MRESCR]]
|BAdI
|MB_DOCUMENT_BADI - MB_DOCUMENT_BEFORE_UPDATE
|Before update
|-
|Different ToDos when saving and updating in reservation, e.g. creating outbound [[IDoc_message_type_MBGMCR|IDoc MBGMCR]]
|Customer Exit
|MBCF0007 - EXIT_SAPMM07R_001
|Saving/changing the reservation with MB21/22
|-
!colspan="4"|Production Planning and Control (PP)
|-
|Different extension in transaction code COOIS
|BAdI
|WORKORDER_INFOSYSTEM
|Several e.g. after selection / layout output
|}

Latest revision as of 17:04, 31 December 2024

All classic extension options are listed here. All listed BAdIs are classic that means for onPremise (private S/4 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 create a good , e.g. creating outbound IDoc MRESCR BAdI MB_DOCUMENT_BADI - MB_DOCUMENT_BEFORE_UPDATE Before update
Different ToDos when saving and updating in reservation, e.g. creating outbound IDoc MBGMCR 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

This is a wiki created in the spare time of a private person working in the SAP ERP area. The aim is to collect knowledge for the own use. The wiki is maintained to the best of knowledge and belief.
All products shown, including in form of screenshots, belong to SAP SE. Their trademarks are, among others: SAP®,ABAP®,SAP Fiori®,SAP HANA®,SAP NetWeaver®,SAP® R/3®,SAP S/4HANA®,SAP S/4HANA® Cloud

Retrieved from "https://unirab.org/index.php?title=Classic_extensibility&oldid=731"