SAP SO_NOTE_READ Function Module for
SO_NOTE_READ is a standard so note read 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 so note read FM, simply by entering the name SO_NOTE_READ into the relevant SAP transaction such as SE37 or SE38.
Function Group: SOA1
Program Name: SAPLSOA1
Main Program: SAPLSOA1
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function SO_NOTE_READ 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 'SO_NOTE_READ'".
EXPORTING
FOLDER_ID = "
OBJECT_ID = "Object ID
* OWNER = ' ' "Mailbox owner
TABLES
OBJCONT = "Object contents
EXCEPTIONS
ACTIVE_USER_NOT_EXIST = 1 X_ERROR = 10 COMMUNICATION_FAILURE = 2 FOLDER_NO_AUTHORIZATION = 3 FOLDER_NOT_EXIST = 4 OBJECT_NOT_EXIST = 5 OWNER_NOT_EXIST = 6 SUBSTITUTE_NOT_ACTIVE = 7 SUBSTITUTE_NOT_DEFINED = 8 SYSTEM_FAILURE = 9
IMPORTING Parameters details for SO_NOTE_READ
FOLDER_ID -
Data type: SOODKOptional: No
Call by Reference: No ( called with pass by value option)
OBJECT_ID - Object ID
Data type: SOODKOptional: No
Call by Reference: No ( called with pass by value option)
OWNER - Mailbox owner
Data type: SOUD-USRNAMDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for SO_NOTE_READ
OBJCONT - Object contents
Data type: SOLIOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ACTIVE_USER_NOT_EXIST - Active user is not a SAPoffice user
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
X_ERROR - Internal Error
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
COMMUNICATION_FAILURE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
FOLDER_NO_AUTHORIZATION - Object Does Not Exist
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
FOLDER_NOT_EXIST -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
OBJECT_NOT_EXIST - Object Does Not Exist
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
OWNER_NOT_EXIST - Owner does not exist
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SUBSTITUTE_NOT_ACTIVE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SUBSTITUTE_NOT_DEFINED - Substitute not defined
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SYSTEM_FAILURE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SO_NOTE_READ 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: | ||||
| lt_objcont | TYPE STANDARD TABLE OF SOLI, " | |||
| lv_folder_id | TYPE SOODK, " | |||
| lv_active_user_not_exist | TYPE SOODK, " | |||
| lv_x_error | TYPE SOODK, " | |||
| lv_object_id | TYPE SOODK, " | |||
| lv_communication_failure | TYPE SOODK, " | |||
| lv_owner | TYPE SOUD-USRNAM, " SPACE | |||
| lv_folder_no_authorization | TYPE SOUD, " | |||
| lv_folder_not_exist | TYPE SOUD, " | |||
| lv_object_not_exist | TYPE SOUD, " | |||
| lv_owner_not_exist | TYPE SOUD, " | |||
| lv_substitute_not_active | TYPE SOUD, " | |||
| lv_substitute_not_defined | TYPE SOUD, " | |||
| lv_system_failure | TYPE SOUD. " |
|   CALL FUNCTION 'SO_NOTE_READ' " |
| EXPORTING | ||
| FOLDER_ID | = lv_folder_id | |
| OBJECT_ID | = lv_object_id | |
| OWNER | = lv_owner | |
| TABLES | ||
| OBJCONT | = lt_objcont | |
| EXCEPTIONS | ||
| ACTIVE_USER_NOT_EXIST = 1 | ||
| X_ERROR = 10 | ||
| COMMUNICATION_FAILURE = 2 | ||
| FOLDER_NO_AUTHORIZATION = 3 | ||
| FOLDER_NOT_EXIST = 4 | ||
| OBJECT_NOT_EXIST = 5 | ||
| OWNER_NOT_EXIST = 6 | ||
| SUBSTITUTE_NOT_ACTIVE = 7 | ||
| SUBSTITUTE_NOT_DEFINED = 8 | ||
| SYSTEM_FAILURE = 9 | ||
| . " SO_NOTE_READ | ||
ABAP code using 7.40 inline data declarations to call FM SO_NOTE_READ
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 USRNAM FROM SOUD INTO @DATA(ld_owner). | ||||
| DATA(ld_owner) | = ' '. | |||
Search for further information about these or an SAP related objects