SAP RMSA104_BADI_FOR_FIRST_DISPLAY Function Module for NOTRANSL: RMS-ATL:
RMSA104_BADI_FOR_FIRST_DISPLAY is a standard rmsa104 badi for first display 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: RMS-ATL: 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 rmsa104 badi for first display FM, simply by entering the name RMSA104_BADI_FOR_FIRST_DISPLAY into the relevant SAP transaction such as SE37 or SE38.
Function Group: RMSA104
Program Name: SAPLRMSA104
Main Program: SAPLRMSA104
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RMSA104_BADI_FOR_FIRST_DISPLAY 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 'RMSA104_BADI_FOR_FIRST_DISPLAY'"NOTRANSL: RMS-ATL:.
EXPORTING
I_APPL_CONTEXT = "Application Area of Table-Based Value Assignment
I_SUBSCREEN = "ABAP Program, Current Screen Number
IMPORTING
E_EVENT_HANDLED = "
CHANGING
* X_FLG_FIRST_DISPLAY = "
* XS_VARIANT = "Layout (External Use)
* X_SAVE = "Character Field of Length 1
IMPORTING Parameters details for RMSA104_BADI_FOR_FIRST_DISPLAY
I_APPL_CONTEXT - Application Area of Table-Based Value Assignment
Data type: EHSBE_VAI_APPL_CONTEXTOptional: No
Call by Reference: No ( called with pass by value option)
I_SUBSCREEN - ABAP Program, Current Screen Number
Data type: SYDYNNROptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for RMSA104_BADI_FOR_FIRST_DISPLAY
E_EVENT_HANDLED -
Data type: ESP1_BOOLEANOptional: No
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for RMSA104_BADI_FOR_FIRST_DISPLAY
X_FLG_FIRST_DISPLAY -
Data type: ESP1_BOOLEANOptional: Yes
Call by Reference: Yes
XS_VARIANT - Layout (External Use)
Data type: DISVARIANTOptional: Yes
Call by Reference: Yes
X_SAVE - Character Field of Length 1
Data type: CHAR01Optional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for RMSA104_BADI_FOR_FIRST_DISPLAY 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_i_appl_context | TYPE EHSBE_VAI_APPL_CONTEXT, " | |||
| lv_e_event_handled | TYPE ESP1_BOOLEAN, " | |||
| lv_x_flg_first_display | TYPE ESP1_BOOLEAN, " | |||
| lv_xs_variant | TYPE DISVARIANT, " | |||
| lv_i_subscreen | TYPE SYDYNNR, " | |||
| lv_x_save | TYPE CHAR01. " |
|   CALL FUNCTION 'RMSA104_BADI_FOR_FIRST_DISPLAY' "NOTRANSL: RMS-ATL: |
| EXPORTING | ||
| I_APPL_CONTEXT | = lv_i_appl_context | |
| I_SUBSCREEN | = lv_i_subscreen | |
| IMPORTING | ||
| E_EVENT_HANDLED | = lv_e_event_handled | |
| CHANGING | ||
| X_FLG_FIRST_DISPLAY | = lv_x_flg_first_display | |
| XS_VARIANT | = lv_xs_variant | |
| X_SAVE | = lv_x_save | |
| . " RMSA104_BADI_FOR_FIRST_DISPLAY | ||
ABAP code using 7.40 inline data declarations to call FM RMSA104_BADI_FOR_FIRST_DISPLAY
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