SAP NOTE_CONTROL_INIT Function Module for
NOTE_CONTROL_INIT is a standard note control init SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 note control init FM, simply by entering the name NOTE_CONTROL_INIT into the relevant SAP transaction such as SE37 or SE38.
Function Group: NOTECTL
Program Name: SAPLNOTECTL
Main Program:
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function NOTE_CONTROL_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 'NOTE_CONTROL_INIT'".
EXPORTING
* I_NEW_INSTANCE = ' ' "
* I_DISPLAY = ' ' "
* I_LANGU = SY-LANGU "
* I_FORCE_EDITOR = "
* I_NOTETYPE = "
* I_NODE_ID = "Unique ID - 32 Characters
* I_FOLDER = "Unique ID for notes
* I_NOTE_ID = "Unique ID for notes
CHANGING
P_PROJECT_ID = "Project ID
P_ID = "
P_APPLICATION = "
P_FILTERTREE = "
P_PARENT = "
EXCEPTIONS
ERROR = 1
IMPORTING Parameters details for NOTE_CONTROL_INIT
I_NEW_INSTANCE -
Data type:Default: SPACE
Optional: Yes
Call by Reference: Yes
I_DISPLAY -
Data type: CDefault: SPACE
Optional: Yes
Call by Reference: Yes
I_LANGU -
Data type: SYLANGUDefault: SY-LANGU
Optional: Yes
Call by Reference: Yes
I_FORCE_EDITOR -
Data type: COptional: Yes
Call by Reference: Yes
I_NOTETYPE -
Data type: PROJ_NTYPEOptional: Yes
Call by Reference: Yes
I_NODE_ID - Unique ID - 32 Characters
Data type: HIER_IFACE-NODE_IDOptional: Yes
Call by Reference: Yes
I_FOLDER - Unique ID for notes
Data type: TNOTFPR-IDOptional: Yes
Call by Reference: Yes
I_NOTE_ID - Unique ID for notes
Data type: TNOTFPR-IDOptional: Yes
Call by Reference: Yes
CHANGING Parameters details for NOTE_CONTROL_INIT
P_PROJECT_ID - Project ID
Data type: SPRO_HEAD-PROJECT_IDOptional: No
Call by Reference: Yes
P_ID -
Data type: ISTATIFACE-IDOptional: No
Call by Reference: Yes
P_APPLICATION -
Data type: CHAR6Optional: No
Call by Reference: Yes
P_FILTERTREE -
Data type: HIER_IFACE-TREE_IDOptional: No
Call by Reference: Yes
P_PARENT -
Data type:Optional: No
Call by Reference: Yes
EXCEPTIONS details
ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for NOTE_CONTROL_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_error | TYPE STRING, " | |||
| lv_p_project_id | TYPE SPRO_HEAD-PROJECT_ID, " | |||
| lv_i_new_instance | TYPE SPRO_HEAD, " SPACE | |||
| lv_p_id | TYPE ISTATIFACE-ID, " | |||
| lv_i_display | TYPE C, " SPACE | |||
| lv_i_langu | TYPE SYLANGU, " SY-LANGU | |||
| lv_p_application | TYPE CHAR6, " | |||
| lv_p_filtertree | TYPE HIER_IFACE-TREE_ID, " | |||
| lv_i_force_editor | TYPE C, " | |||
| lv_p_parent | TYPE C, " | |||
| lv_i_notetype | TYPE PROJ_NTYPE, " | |||
| lv_i_node_id | TYPE HIER_IFACE-NODE_ID, " | |||
| lv_i_folder | TYPE TNOTFPR-ID, " | |||
| lv_i_note_id | TYPE TNOTFPR-ID. " |
|   CALL FUNCTION 'NOTE_CONTROL_INIT' " |
| EXPORTING | ||
| I_NEW_INSTANCE | = lv_i_new_instance | |
| I_DISPLAY | = lv_i_display | |
| I_LANGU | = lv_i_langu | |
| I_FORCE_EDITOR | = lv_i_force_editor | |
| I_NOTETYPE | = lv_i_notetype | |
| I_NODE_ID | = lv_i_node_id | |
| I_FOLDER | = lv_i_folder | |
| I_NOTE_ID | = lv_i_note_id | |
| CHANGING | ||
| P_PROJECT_ID | = lv_p_project_id | |
| P_ID | = lv_p_id | |
| P_APPLICATION | = lv_p_application | |
| P_FILTERTREE | = lv_p_filtertree | |
| P_PARENT | = lv_p_parent | |
| EXCEPTIONS | ||
| ERROR = 1 | ||
| . " NOTE_CONTROL_INIT | ||
ABAP code using 7.40 inline data declarations to call FM NOTE_CONTROL_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 PROJECT_ID FROM SPRO_HEAD INTO @DATA(ld_p_project_id). | ||||
| DATA(ld_i_new_instance) | = ' '. | |||
| "SELECT single ID FROM ISTATIFACE INTO @DATA(ld_p_id). | ||||
| DATA(ld_i_display) | = ' '. | |||
| DATA(ld_i_langu) | = SY-LANGU. | |||
| "SELECT single TREE_ID FROM HIER_IFACE INTO @DATA(ld_p_filtertree). | ||||
| "SELECT single NODE_ID FROM HIER_IFACE INTO @DATA(ld_i_node_id). | ||||
| "SELECT single ID FROM TNOTFPR INTO @DATA(ld_i_folder). | ||||
| "SELECT single ID FROM TNOTFPR INTO @DATA(ld_i_note_id). | ||||
Search for further information about these or an SAP related objects