SAP IDOC_START_INBOUND Function Module for Start inbound processing for inbound IDoc
IDOC_START_INBOUND is a standard idoc start inbound SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Start inbound processing for inbound IDoc 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 idoc start inbound FM, simply by entering the name IDOC_START_INBOUND into the relevant SAP transaction such as SE37 or SE38.
Function Group: EDIR
Program Name: SAPLEDIR
Main Program: SAPLEDIR
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function IDOC_START_INBOUND 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 'IDOC_START_INBOUND'"Start inbound processing for inbound IDoc.
EXPORTING
* PI_INBOUND_PROCESS_DATA = ' ' "Inbound process code
* PI_CALLED_ONLINE = ' ' "
* PI_DO_COMMIT = 'X' "
* PI_START_EVENT_ENABLED = 'X' "
* PI_ORG_UNIT = ' ' "
* SUCC_SHOW_FLAG = ' ' "
* PI_PARTNER_OPTION = "
TABLES
T_CONTROL_RECORDS = "
* T_DATA_RECORDS = "
EXCEPTIONS
INVALID_DOCUMENT_NUMBER = 1 ERROR_BEFORE_CALL_APPLICATION = 2 INBOUND_PROCESS_NOT_POSSIBLE = 3 OLD_WF_START_FAILED = 4 WF_TASK_ERROR = 5 SERIOUS_INBOUND_ERROR = 6
IMPORTING Parameters details for IDOC_START_INBOUND
PI_INBOUND_PROCESS_DATA - Inbound process code
Data type: TEDE2Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
PI_CALLED_ONLINE -
Data type: SWWCOMMIT-DIALOGFLAGDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
PI_DO_COMMIT -
Data type: EDIGENERAL-DO_COMMITDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
PI_START_EVENT_ENABLED -
Data type: EDIGENERAL-STARTEVENTDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
PI_ORG_UNIT -
Data type: SWHACTORDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
SUCC_SHOW_FLAG -
Data type: EDIGENERAL-SUCC_FLAGDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
PI_PARTNER_OPTION -
Data type: EDI_PARTNER_INBOUND_OPTIONOptional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for IDOC_START_INBOUND
T_CONTROL_RECORDS -
Data type: EDIDCOptional: No
Call by Reference: No ( called with pass by value option)
T_DATA_RECORDS -
Data type: EDIDDOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
INVALID_DOCUMENT_NUMBER - Invalid IDoc number
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ERROR_BEFORE_CALL_APPLICATION - Error before application was called
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INBOUND_PROCESS_NOT_POSSIBLE - Inbound processing not possible
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
OLD_WF_START_FAILED - Process (up to 2.2) cannot be started
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
WF_TASK_ERROR - Work item/Workflow could not be created
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SERIOUS_INBOUND_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for IDOC_START_INBOUND 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_t_control_records | TYPE STANDARD TABLE OF EDIDC, " | |||
| lv_invalid_document_number | TYPE EDIDC, " | |||
| lv_pi_inbound_process_data | TYPE TEDE2, " SPACE | |||
| lt_t_data_records | TYPE STANDARD TABLE OF EDIDD, " | |||
| lv_pi_called_online | TYPE SWWCOMMIT-DIALOGFLAG, " SPACE | |||
| lv_error_before_call_application | TYPE SWWCOMMIT, " | |||
| lv_pi_do_commit | TYPE EDIGENERAL-DO_COMMIT, " 'X' | |||
| lv_inbound_process_not_possible | TYPE EDIGENERAL, " | |||
| lv_old_wf_start_failed | TYPE EDIGENERAL, " | |||
| lv_pi_start_event_enabled | TYPE EDIGENERAL-STARTEVENT, " 'X' | |||
| lv_pi_org_unit | TYPE SWHACTOR, " SPACE | |||
| lv_wf_task_error | TYPE SWHACTOR, " | |||
| lv_succ_show_flag | TYPE EDIGENERAL-SUCC_FLAG, " ' ' | |||
| lv_serious_inbound_error | TYPE EDIGENERAL, " | |||
| lv_pi_partner_option | TYPE EDI_PARTNER_INBOUND_OPTION. " |
|   CALL FUNCTION 'IDOC_START_INBOUND' "Start inbound processing for inbound IDoc |
| EXPORTING | ||
| PI_INBOUND_PROCESS_DATA | = lv_pi_inbound_process_data | |
| PI_CALLED_ONLINE | = lv_pi_called_online | |
| PI_DO_COMMIT | = lv_pi_do_commit | |
| PI_START_EVENT_ENABLED | = lv_pi_start_event_enabled | |
| PI_ORG_UNIT | = lv_pi_org_unit | |
| SUCC_SHOW_FLAG | = lv_succ_show_flag | |
| PI_PARTNER_OPTION | = lv_pi_partner_option | |
| TABLES | ||
| T_CONTROL_RECORDS | = lt_t_control_records | |
| T_DATA_RECORDS | = lt_t_data_records | |
| EXCEPTIONS | ||
| INVALID_DOCUMENT_NUMBER = 1 | ||
| ERROR_BEFORE_CALL_APPLICATION = 2 | ||
| INBOUND_PROCESS_NOT_POSSIBLE = 3 | ||
| OLD_WF_START_FAILED = 4 | ||
| WF_TASK_ERROR = 5 | ||
| SERIOUS_INBOUND_ERROR = 6 | ||
| . " IDOC_START_INBOUND | ||
ABAP code using 7.40 inline data declarations to call FM IDOC_START_INBOUND
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_pi_inbound_process_data) | = ' '. | |||
| "SELECT single DIALOGFLAG FROM SWWCOMMIT INTO @DATA(ld_pi_called_online). | ||||
| DATA(ld_pi_called_online) | = ' '. | |||
| "SELECT single DO_COMMIT FROM EDIGENERAL INTO @DATA(ld_pi_do_commit). | ||||
| DATA(ld_pi_do_commit) | = 'X'. | |||
| "SELECT single STARTEVENT FROM EDIGENERAL INTO @DATA(ld_pi_start_event_enabled). | ||||
| DATA(ld_pi_start_event_enabled) | = 'X'. | |||
| DATA(ld_pi_org_unit) | = ' '. | |||
| "SELECT single SUCC_FLAG FROM EDIGENERAL INTO @DATA(ld_succ_show_flag). | ||||
| DATA(ld_succ_show_flag) | = ' '. | |||
Search for further information about these or an SAP related objects