SAP INM_INITIATIVE_T_GETLIST Function Module for Initiative Get list
INM_INITIATIVE_T_GETLIST is a standard inm initiative t getlist 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 Get list 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 t getlist FM, simply by entering the name INM_INITIATIVE_T_GETLIST into the relevant SAP transaction such as SE37 or SE38.
Function Group: INM_INITIATIVE_TEMPLATE
Program Name: SAPLINM_INITIATIVE_TEMPLATE
Main Program: SAPLINM_INITIATIVE_TEMPLATE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function INM_INITIATIVE_T_GETLIST 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_T_GETLIST'"Initiative Get list.
EXPORTING
IS_CONTEXT = "Portfolio Hierarchy
* IV_MY_OBJECTS_ONLY = 'X' "Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')
* IV_LANGUAGE = 'EN' "Language according to ISO 639
* IV_SCOPE = '1' "Scope of objects to be returned in dashboard
IMPORTING
EV_RC = "
TABLES
* IT_INITIATIVES_KEY = "Table Type for Initiative Key
ET_INITIATIVES = "Initaitives
* ET_MSG = "Table Type for Messages
* ET_FIELD_DESCRIPTION = "Table for field description
IMPORTING Parameters details for INM_INITIATIVE_T_GETLIST
IS_CONTEXT - Portfolio Hierarchy
Data type: /RPM/TS_OBJECT_HIEROptional: No
Call by Reference: No ( called with pass by value option)
IV_MY_OBJECTS_ONLY - Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')
Data type: BOOLE_DDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_LANGUAGE - Language according to ISO 639
Data type: LAISODefault: 'EN'
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_SCOPE - Scope of objects to be returned in dashboard
Data type: INM_TV_DASHBOARD_SCOPEDefault: '1'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for INM_INITIATIVE_T_GETLIST
EV_RC -
Data type: IOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for INM_INITIATIVE_T_GETLIST
IT_INITIATIVES_KEY - Table Type for Initiative Key
Data type: INM_TT_INITIATIVES_KEYOptional: Yes
Call by Reference: Yes
ET_INITIATIVES - Initaitives
Data type: INM_TT_INITIATIVES_T_EXTOptional: No
Call by Reference: Yes
ET_MSG - Table Type for Messages
Data type: INM_TT_MESSAGESOptional: Yes
Call by Reference: No ( called with pass by value option)
ET_FIELD_DESCRIPTION - Table for field description
Data type: /RPM/TT_FIELDS_DESCRIPTIONOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for INM_INITIATIVE_T_GETLIST 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_ev_rc | TYPE I, " | |||
| lv_is_context | TYPE /RPM/TS_OBJECT_HIER, " | |||
| lt_it_initiatives_key | TYPE STANDARD TABLE OF INM_TT_INITIATIVES_KEY, " | |||
| lt_et_initiatives | TYPE STANDARD TABLE OF INM_TT_INITIATIVES_T_EXT, " | |||
| lv_iv_my_objects_only | TYPE BOOLE_D, " 'X' | |||
| lt_et_msg | TYPE STANDARD TABLE OF INM_TT_MESSAGES, " | |||
| lv_iv_language | TYPE LAISO, " 'EN' | |||
| lv_iv_scope | TYPE INM_TV_DASHBOARD_SCOPE, " '1' | |||
| lt_et_field_description | TYPE STANDARD TABLE OF /RPM/TT_FIELDS_DESCRIPTION. " |
|   CALL FUNCTION 'INM_INITIATIVE_T_GETLIST' "Initiative Get list |
| EXPORTING | ||
| IS_CONTEXT | = lv_is_context | |
| IV_MY_OBJECTS_ONLY | = lv_iv_my_objects_only | |
| IV_LANGUAGE | = lv_iv_language | |
| IV_SCOPE | = lv_iv_scope | |
| IMPORTING | ||
| EV_RC | = lv_ev_rc | |
| TABLES | ||
| IT_INITIATIVES_KEY | = lt_it_initiatives_key | |
| ET_INITIATIVES | = lt_et_initiatives | |
| ET_MSG | = lt_et_msg | |
| ET_FIELD_DESCRIPTION | = lt_et_field_description | |
| . " INM_INITIATIVE_T_GETLIST | ||
ABAP code using 7.40 inline data declarations to call FM INM_INITIATIVE_T_GETLIST
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.| DATA(ld_iv_my_objects_only) | = 'X'. | |||
| DATA(ld_iv_language) | = 'EN'. | |||
| DATA(ld_iv_scope) | = '1'. | |||
Search for further information about these or an SAP related objects