SAP INM_INITIATIVE_DISPLAY Function Module for Initiative Display

Search SAP Function Modules

INM_INITIATIVE_DISPLAY is a standard inm initiative 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 Initiative Display 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 inm initiative display FM, simply by entering the name INM_INITIATIVE_DISPLAY into the relevant SAP transaction such as SE37 or SE38.

Function Group: INM_INITIATIVE
Program Name: SAPLINM_INITIATIVE
Main Program: SAPLINM_INITIATIVE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function INM_INITIATIVE_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 'INM_INITIATIVE_DISPLAY'"Initiative Display
  EXPORTING
   IS_CONTEXT =  "Guid for application objects
*  IV_LANGUAGE =  "Language according to ISO 639
*  IV_EDIT_MODE =  "Edit mode of application objects

 IMPORTING
   ES_ATTRIBUTES =  "Initiative
   ES_MODE =  "Object Change Mode
   EV_SHORT_TEXT =  "
   EV_REASON =  "
   EV_GOAL =  "
   EV_BENEFITS =  "
   EV_STATUS_TEXT =  "
   EV_RC =  "

TABLES
*  ET_MSG =  "Table Type for Messages
*  ET_FIELD_DESCRIPTION =  "Table for field description
*  ET_STATUS =  "Status

.

IMPORTING Parameters details for INM_INITIATIVE_DISPLAY

IS_CONTEXT - Guid for application objects

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

IV_LANGUAGE - Language according to ISO 639

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

IV_EDIT_MODE - Edit mode of application objects

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

EXPORTING Parameters details for INM_INITIATIVE_DISPLAY

ES_ATTRIBUTES - Initiative

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

ES_MODE - Object Change Mode

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

EV_SHORT_TEXT -

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

EV_REASON -

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

EV_GOAL -

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

EV_BENEFITS -

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

EV_STATUS_TEXT -

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

EV_RC -

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

TABLES Parameters details for INM_INITIATIVE_DISPLAY

ET_MSG - Table Type for Messages

Data type: /RPM/TT_MESSAGES
Optional: Yes
Call by Reference: Yes

ET_FIELD_DESCRIPTION - Table for field description

Data type: /RPM/TT_FIELDS_DESCRIPTION
Optional: Yes
Call by Reference: Yes

ET_STATUS - Status

Data type: INM_TT_STATUS
Optional: Yes
Call by Reference: Yes

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

ABAP code using 7.40 inline data declarations to call FM INM_INITIATIVE_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