SAP SO_INCIDENT_READ_INTF Function Module for Read Incident Details
SO_INCIDENT_READ_INTF is a standard so incident read intf SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read Incident Details 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 so incident read intf FM, simply by entering the name SO_INCIDENT_READ_INTF into the relevant SAP transaction such as SE37 or SE38.
Function Group: FGSO_INTERFACE_MODULES
Program Name: SAPLFGSO_INTERFACE_MODULES
Main Program: SAPLFGSO_INTERFACE_MODULES
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function SO_INCIDENT_READ_INTF 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_INCIDENT_READ_INTF'"Read Incident Details.
EXPORTING
IV_ID = "Incident ID
IMPORTING
ET_RETURN = "Return Parameter
ES_INC_ROOT_NODE = "Incident Root
ES_INC_BASIC_INFO_ALL = "Basic Information of an Incident
ET_INC_PERSON_INVOLVED = "Person Involved
ET_INC_PERSON_DETAIL = "Person Detail Table Type
ET_INC_PERSON_ROLE = "Person Role (Safety Observation Application)
ET_INC_ATT_DOCUMENT = "Attached Document
IMPORTING Parameters details for SO_INCIDENT_READ_INTF
IV_ID - Incident ID
Data type: EHHSS_INC_IDOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for SO_INCIDENT_READ_INTF
ET_RETURN - Return Parameter
Data type: BAPIRETURNOptional: No
Call by Reference: No ( called with pass by value option)
ES_INC_ROOT_NODE - Incident Root
Data type: SSSO_INCIDENT_ROOTOptional: No
Call by Reference: No ( called with pass by value option)
ES_INC_BASIC_INFO_ALL - Basic Information of an Incident
Data type: SSSO_INC_BASIC_INFO_ALLOptional: No
Call by Reference: No ( called with pass by value option)
ET_INC_PERSON_INVOLVED - Person Involved
Data type: STSO_PERSON_INVOLVED_STANDARDOptional: No
Call by Reference: No ( called with pass by value option)
ET_INC_PERSON_DETAIL - Person Detail Table Type
Data type: STSO_INC_PERSON_DETAILOptional: No
Call by Reference: No ( called with pass by value option)
ET_INC_PERSON_ROLE - Person Role (Safety Observation Application)
Data type: STSO_INC_PERSON_ROLEOptional: No
Call by Reference: No ( called with pass by value option)
ET_INC_ATT_DOCUMENT - Attached Document
Data type: STSO_INC_ATT_DOCUMENTOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SO_INCIDENT_READ_INTF 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_iv_id | TYPE EHHSS_INC_ID, " | |||
| lv_et_return | TYPE BAPIRETURN, " | |||
| lv_es_inc_root_node | TYPE SSSO_INCIDENT_ROOT, " | |||
| lv_es_inc_basic_info_all | TYPE SSSO_INC_BASIC_INFO_ALL, " | |||
| lv_et_inc_person_involved | TYPE STSO_PERSON_INVOLVED_STANDARD, " | |||
| lv_et_inc_person_detail | TYPE STSO_INC_PERSON_DETAIL, " | |||
| lv_et_inc_person_role | TYPE STSO_INC_PERSON_ROLE, " | |||
| lv_et_inc_att_document | TYPE STSO_INC_ATT_DOCUMENT. " |
|   CALL FUNCTION 'SO_INCIDENT_READ_INTF' "Read Incident Details |
| EXPORTING | ||
| IV_ID | = lv_iv_id | |
| IMPORTING | ||
| ET_RETURN | = lv_et_return | |
| ES_INC_ROOT_NODE | = lv_es_inc_root_node | |
| ES_INC_BASIC_INFO_ALL | = lv_es_inc_basic_info_all | |
| ET_INC_PERSON_INVOLVED | = lv_et_inc_person_involved | |
| ET_INC_PERSON_DETAIL | = lv_et_inc_person_detail | |
| ET_INC_PERSON_ROLE | = lv_et_inc_person_role | |
| ET_INC_ATT_DOCUMENT | = lv_et_inc_att_document | |
| . " SO_INCIDENT_READ_INTF | ||
ABAP code using 7.40 inline data declarations to call FM SO_INCIDENT_READ_INTF
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