SAP RMSA145_HITLIST_OKCODE_SPEC Function Module for NOTRANSL: Okcode Handler der Trefferliste

Search SAP Function Modules

RMSA145_HITLIST_OKCODE_SPEC is a standard rmsa145 hitlist okcode spec 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: Okcode Handler der Trefferliste 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 rmsa145 hitlist okcode spec FM, simply by entering the name RMSA145_HITLIST_OKCODE_SPEC into the relevant SAP transaction such as SE37 or SE38.

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

Function RMSA145_HITLIST_OKCODE_SPEC 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 'RMSA145_HITLIST_OKCODE_SPEC'"NOTRANSL: Okcode Handler der Trefferliste
  EXPORTING
   I_ACTYPE =  "Activity Type in the Transaction
   I_PICGRP =  "Screen Group
   I_PANEL =  "Name of Current Screen Display
   I_TRTYPE =  "Transaction Type
   I_ADDINF =  "EHS: Additional Information for Function Module Calls
   I_IOTAB_WA =  "
   I_KEYPATH =  "EHS: 'Key' path substance/list/property for FM call
   I_FLG_WB_CALL =  "General Indicator

 IMPORTING
   E_OKCODE =  "Function Code That Triggered PAI
   E_FLG_STAY =  "General Indicator

CHANGING
   X_OKCODE =  "Function Code That Triggered PAI

.

IMPORTING Parameters details for RMSA145_HITLIST_OKCODE_SPEC

I_ACTYPE - Activity Type in the Transaction

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

I_PICGRP - Screen Group

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

I_PANEL - Name of Current Screen Display

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

I_TRTYPE - Transaction Type

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

I_ADDINF - EHS: Additional Information for Function Module Calls

Data type: RCGADDINF
Optional: No
Call by Reference: Yes

I_IOTAB_WA -

Data type:
Optional: No
Call by Reference: Yes

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

Data type: RCGKPATH
Optional: No
Call by Reference: Yes

I_FLG_WB_CALL - General Indicator

Data type: FLAG
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for RMSA145_HITLIST_OKCODE_SPEC

E_OKCODE - Function Code That Triggered PAI

Data type: SYUCOMM
Optional: No
Call by Reference: Yes

E_FLG_STAY - General Indicator

Data type: FLAG
Optional: No
Call by Reference: Yes

CHANGING Parameters details for RMSA145_HITLIST_OKCODE_SPEC

X_OKCODE - Function Code That Triggered PAI

Data type: SYUCOMM
Optional: No
Call by Reference: Yes

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

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