SAP RMSA144_APP_SCREEN_INIT Function Module for NOTRANSL: RMS-ATL: Initialisierung generischer Einstieg









RMSA144_APP_SCREEN_INIT is a standard rmsa144 app screen init 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: Initialisierung generischer Einstieg 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 rmsa144 app screen init FM, simply by entering the name RMSA144_APP_SCREEN_INIT into the relevant SAP transaction such as SE37 or SE38.

Function Group: RMSA144
Program Name: SAPLRMSA144
Main Program: SAPLRMSA144
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function RMSA144_APP_SCREEN_INIT 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 'RMSA144_APP_SCREEN_INIT'"NOTRANSL: RMS-ATL: Initialisierung generischer Einstieg
EXPORTING
I_OBJTYPE = "Specification Category
I_TCODE = "ABAP Program, Current Transaction Code

IMPORTING
E_CUA_SET_FB = "
E_HITLIST_OKCODE_FB = "
E_ENTRY_OKCODE_FB = "
E_EHS_COMPONENT = "

CHANGING
* X_RCGDIALCTR = "EHS: Dialog Control Structure
* X_RCGKPATH = "EHS: 'Key' path substance/list/property for FM call

EXCEPTIONS
INTERNAL_ERROR = 1
.



IMPORTING Parameters details for RMSA144_APP_SCREEN_INIT

I_OBJTYPE - Specification Category

Data type: TCGOBJ-OBJTYPE
Optional: No
Call by Reference: No ( called with pass by value option)

I_TCODE - ABAP Program, Current Transaction Code

Data type: SYTCODE
Optional: No
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for RMSA144_APP_SCREEN_INIT

E_CUA_SET_FB -

Data type: ESP1_FUNC_NAME
Optional: No
Call by Reference: No ( called with pass by value option)

E_HITLIST_OKCODE_FB -

Data type: ESP1_FUNC_NAME
Optional: No
Call by Reference: No ( called with pass by value option)

E_ENTRY_OKCODE_FB -

Data type: ESP1_FUNC_NAME
Optional: No
Call by Reference: No ( called with pass by value option)

E_EHS_COMPONENT -

Data type: C
Optional: No
Call by Reference: No ( called with pass by value option)

CHANGING Parameters details for RMSA144_APP_SCREEN_INIT

X_RCGDIALCTR - EHS: Dialog Control Structure

Data type: RCGDIALCTR
Optional: Yes
Call by Reference: No ( called with pass by value option)

X_RCGKPATH - EHS: 'Key' path substance/list/property for FM call

Data type: RCGKPATH
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

INTERNAL_ERROR -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for RMSA144_APP_SCREEN_INIT 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_objtype  TYPE TCGOBJ-OBJTYPE, "   
lv_e_cua_set_fb  TYPE ESP1_FUNC_NAME, "   
lv_x_rcgdialctr  TYPE RCGDIALCTR, "   
lv_internal_error  TYPE RCGDIALCTR, "   
lv_i_tcode  TYPE SYTCODE, "   
lv_x_rcgkpath  TYPE RCGKPATH, "   
lv_e_hitlist_okcode_fb  TYPE ESP1_FUNC_NAME, "   
lv_e_entry_okcode_fb  TYPE ESP1_FUNC_NAME, "   
lv_e_ehs_component  TYPE C. "   

  CALL FUNCTION 'RMSA144_APP_SCREEN_INIT'  "NOTRANSL: RMS-ATL: Initialisierung generischer Einstieg
    EXPORTING
         I_OBJTYPE = lv_i_objtype
         I_TCODE = lv_i_tcode
    IMPORTING
         E_CUA_SET_FB = lv_e_cua_set_fb
         E_HITLIST_OKCODE_FB = lv_e_hitlist_okcode_fb
         E_ENTRY_OKCODE_FB = lv_e_entry_okcode_fb
         E_EHS_COMPONENT = lv_e_ehs_component
    CHANGING
         X_RCGDIALCTR = lv_x_rcgdialctr
         X_RCGKPATH = lv_x_rcgkpath
    EXCEPTIONS
        INTERNAL_ERROR = 1
. " RMSA144_APP_SCREEN_INIT




ABAP code using 7.40 inline data declarations to call FM RMSA144_APP_SCREEN_INIT

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 OBJTYPE FROM TCGOBJ INTO @DATA(ld_i_objtype).
 
 
 
 
 
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!