SAP IDOC_DATA_INBOUND_CONVERT Function Module for Convert IDoc data record from external format to internal format
IDOC_DATA_INBOUND_CONVERT is a standard idoc data inbound convert SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Convert IDoc data record from external format to internal format 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 data inbound convert FM, simply by entering the name IDOC_DATA_INBOUND_CONVERT into the relevant SAP transaction such as SE37 or SE38.
Function Group: EDIN
Program Name: SAPLEDIN
Main Program: SAPLEDIN
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function IDOC_DATA_INBOUND_CONVERT 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_DATA_INBOUND_CONVERT'"Convert IDoc data record from external format to internal format.
EXPORTING
* PI_DATA_RECORD_EXT = "
* PI_DATA_RECORD_EXT_40 = "
* PI_PARALLEL_INT = "
IMPORTING
PE_DATA_RECORD_INT = "
PE_STATUS_MESSAGE = "
EXCEPTIONS
DATA_RECORDS_EMPTY = 1
IMPORTING Parameters details for IDOC_DATA_INBOUND_CONVERT
PI_DATA_RECORD_EXT -
Data type: EDI_DDOptional: Yes
Call by Reference: No ( called with pass by value option)
PI_DATA_RECORD_EXT_40 -
Data type: EDI_DD40Optional: Yes
Call by Reference: No ( called with pass by value option)
PI_PARALLEL_INT -
Data type: BOOLE_DOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for IDOC_DATA_INBOUND_CONVERT
PE_DATA_RECORD_INT -
Data type: EDIDDOptional: No
Call by Reference: No ( called with pass by value option)
PE_STATUS_MESSAGE -
Data type: EDIDSOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
DATA_RECORDS_EMPTY -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for IDOC_DATA_INBOUND_CONVERT 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_data_records_empty | TYPE STRING, " | |||
| lv_pe_data_record_int | TYPE EDIDD, " | |||
| lv_pi_data_record_ext | TYPE EDI_DD, " | |||
| lv_pe_status_message | TYPE EDIDS, " | |||
| lv_pi_data_record_ext_40 | TYPE EDI_DD40, " | |||
| lv_pi_parallel_int | TYPE BOOLE_D. " |
|   CALL FUNCTION 'IDOC_DATA_INBOUND_CONVERT' "Convert IDoc data record from external format to internal format |
| EXPORTING | ||
| PI_DATA_RECORD_EXT | = lv_pi_data_record_ext | |
| PI_DATA_RECORD_EXT_40 | = lv_pi_data_record_ext_40 | |
| PI_PARALLEL_INT | = lv_pi_parallel_int | |
| IMPORTING | ||
| PE_DATA_RECORD_INT | = lv_pe_data_record_int | |
| PE_STATUS_MESSAGE | = lv_pe_status_message | |
| EXCEPTIONS | ||
| DATA_RECORDS_EMPTY = 1 | ||
| . " IDOC_DATA_INBOUND_CONVERT | ||
ABAP code using 7.40 inline data declarations to call FM IDOC_DATA_INBOUND_CONVERT
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