SAP OIRC_GET_BADI_DESCRIPTION Function Module for SSR - BADI description access
OIRC_GET_BADI_DESCRIPTION is a standard oirc get badi description SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for SSR - BADI description access 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 oirc get badi description FM, simply by entering the name OIRC_GET_BADI_DESCRIPTION into the relevant SAP transaction such as SE37 or SE38.
Function Group: OIRC_APP02
Program Name: SAPLOIRC_APP02
Main Program: SAPLOIRC_APP02
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function OIRC_GET_BADI_DESCRIPTION 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 'OIRC_GET_BADI_DESCRIPTION'"SSR - BADI description access.
EXPORTING
I_EXIT_NAME = "Business Add-in Definition
I_FLT_VAL = "Filter name
CHANGING
X_TEXT = "Text field
IMPORTING Parameters details for OIRC_GET_BADI_DESCRIPTION
I_EXIT_NAME - Business Add-in Definition
Data type: EXIT_DEFOptional: No
Call by Reference: Yes
I_FLT_VAL - Filter name
Data type: FILTNAMEOptional: No
Call by Reference: Yes
CHANGING Parameters details for OIRC_GET_BADI_DESCRIPTION
X_TEXT - Text field
Data type: CUS_TEXTOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for OIRC_GET_BADI_DESCRIPTION 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_x_text | TYPE CUS_TEXT, " | |||
| lv_i_exit_name | TYPE EXIT_DEF, " | |||
| lv_i_flt_val | TYPE FILTNAME. " |
|   CALL FUNCTION 'OIRC_GET_BADI_DESCRIPTION' "SSR - BADI description access |
| EXPORTING | ||
| I_EXIT_NAME | = lv_i_exit_name | |
| I_FLT_VAL | = lv_i_flt_val | |
| CHANGING | ||
| X_TEXT | = lv_x_text | |
| . " OIRC_GET_BADI_DESCRIPTION | ||
ABAP code using 7.40 inline data declarations to call FM OIRC_GET_BADI_DESCRIPTION
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.Search for further information about these or an SAP related objects