SAP RMSA360_ENTRY Function Module for NOTRANSL: RMS-ATL: Einstieg in die Stoffbewertung (Subscreen)

Search SAP Function Modules

RMSA360_ENTRY is a standard rmsa360 entry 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: Einstieg in die Stoffbewertung (Subscreen) 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 rmsa360 entry FM, simply by entering the name RMSA360_ENTRY into the relevant SAP transaction such as SE37 or SE38.

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

Function RMSA360_ENTRY 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 'RMSA360_ENTRY'"NOTRANSL: RMS-ATL: Einstieg in die Stoffbewertung (Subscreen)
  EXPORTING
   I_ACTYPE =  "Current Activity Type
   I_TRTYPE =  "Current Transaction Type
   I_KEYPATH =  "
   I_ADDINF =  "Additional information
*  I_RECNTVA =  "Sequential Number of Data Record
*  I_FLG_SIN_INST_POP = ESP1_FALSE "

 IMPORTING
   E_FLG_CHANGED =  "
   E_DYNNR =  "ABAP Program, Current Screen Number
   E_REPID =  "
   E_ACTYPE =  "Activity Type in the Transaction
   E_KEYPATH =  "EHS: 'Key' path substance/list/property for FM call

EXCEPTIONS
   REFERENCE_CONFLICT = 1    NO_AUTHORITY = 2    SUBST_UPD_FIELDS_SET_ERROR = 3    CONVMODE_SET_FAILED = 4 

.

IMPORTING Parameters details for RMSA360_ENTRY

I_ACTYPE - Current Activity Type

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

I_TRTYPE - Current Transaction Type

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

I_KEYPATH -

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

I_ADDINF - Additional information

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

I_RECNTVA - Sequential Number of Data Record

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

I_FLG_SIN_INST_POP -

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

EXPORTING Parameters details for RMSA360_ENTRY

E_FLG_CHANGED -

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

E_DYNNR - ABAP Program, Current Screen Number

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

E_REPID -

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

E_ACTYPE - Activity Type in the Transaction

Data type: RCGDIALCTR-ACTYPE
Optional: No
Call by Reference: Yes

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

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

EXCEPTIONS details

REFERENCE_CONFLICT -

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

NO_AUTHORITY - No Authorization

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

SUBST_UPD_FIELDS_SET_ERROR -

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

CONVMODE_SET_FAILED -

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

Copy and paste ABAP code example for RMSA360_ENTRY 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.

ABAP code using 7.40 inline data declarations to call FM RMSA360_ENTRY

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