SAP CO_BADI_GET_BUSINESS_ADD_IN Function Module for NOTRANSL: Handle zu BADI besorgen und Prüfung, ob aktive Implementierung v
CO_BADI_GET_BUSINESS_ADD_IN is a standard co badi get business add in SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Handle zu BADI besorgen und Prüfung, ob aktive Implementierung v processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.
See here to view full function module documentation and code listing for co badi get business add in FM, simply by entering the name CO_BADI_GET_BUSINESS_ADD_IN into the relevant SAP transaction such as SE37 or SE38.
Function Group: COBADI
Program Name: SAPLCOBADI
Main Program: SAPLCOBADI
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
![](https://www.se80.co.uk/training-education/wp-content/uploads/2019/07/normal-function-module.png)
Function CO_BADI_GET_BUSINESS_ADD_IN pattern details
In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.CALL FUNCTION 'CO_BADI_GET_BUSINESS_ADD_IN'"NOTRANSL: Handle zu BADI besorgen und Prüfung, ob aktive Implementierung v.
EXPORTING
I_BADI_NAME = "DE-EN-LANG-SWITCH-NO-TRANSLATION
CHANGING
C_BADI_INSTANCE = "DE-EN-LANG-SWITCH-NO-TRANSLATION
EXCEPTIONS
NOT_ACTIVE = 1
IMPORTING Parameters details for CO_BADI_GET_BUSINESS_ADD_IN
I_BADI_NAME - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: RSEXSCRN-EXIT_NAMEOptional: No
Call by Reference: Yes
CHANGING Parameters details for CO_BADI_GET_BUSINESS_ADD_IN
C_BADI_INSTANCE - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: ANYOptional: No
Call by Reference: Yes
EXCEPTIONS details
NOT_ACTIVE - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for CO_BADI_GET_BUSINESS_ADD_IN Function Module
The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.DATA: | ||||
lv_not_active | TYPE STRING, " | |||
lv_i_badi_name | TYPE RSEXSCRN-EXIT_NAME, " | |||
lv_c_badi_instance | TYPE ANY. " |
  CALL FUNCTION 'CO_BADI_GET_BUSINESS_ADD_IN' "NOTRANSL: Handle zu BADI besorgen und Prüfung, ob aktive Implementierung v |
EXPORTING | ||
I_BADI_NAME | = lv_i_badi_name | |
CHANGING | ||
C_BADI_INSTANCE | = lv_c_badi_instance | |
EXCEPTIONS | ||
NOT_ACTIVE = 1 | ||
. " CO_BADI_GET_BUSINESS_ADD_IN |
ABAP code using 7.40 inline data declarations to call FM CO_BADI_GET_BUSINESS_ADD_IN
The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8."SELECT single EXIT_NAME FROM RSEXSCRN INTO @DATA(ld_i_badi_name). | ||||
Search for further information about these or an SAP related objects