SAP CVI_EI_INBOUND_MAIN Function Module for Processing of Complex BP Interface in CVI
CVI_EI_INBOUND_MAIN is a standard cvi ei inbound main SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Processing of Complex BP Interface in CVI 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 cvi ei inbound main FM, simply by entering the name CVI_EI_INBOUND_MAIN into the relevant SAP transaction such as SE37 or SE38.
Function Group: CVI_EI_INBOUND_MAIN
Program Name: SAPLCVI_EI_INBOUND_MAIN
Main Program: SAPLCVI_EI_INBOUND_MAIN
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CVI_EI_INBOUND_MAIN 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 'CVI_EI_INBOUND_MAIN'"Processing of Complex BP Interface in CVI.
EXPORTING
I_DATA = "Complex Interface for BP Within CVI
IMPORTING
E_RETURN = "BAPIRETI Table Type for Multiple Objects
IMPORTING Parameters details for CVI_EI_INBOUND_MAIN
I_DATA - Complex Interface for BP Within CVI
Data type: CVIS_EI_EXTERN_TOptional: No
Call by Reference: Yes
EXPORTING Parameters details for CVI_EI_INBOUND_MAIN
E_RETURN - BAPIRETI Table Type for Multiple Objects
Data type: BAPIRETMOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for CVI_EI_INBOUND_MAIN 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_i_data | TYPE CVIS_EI_EXTERN_T, " | |||
| lv_e_return | TYPE BAPIRETM. " |
|   CALL FUNCTION 'CVI_EI_INBOUND_MAIN' "Processing of Complex BP Interface in CVI |
| EXPORTING | ||
| I_DATA | = lv_i_data | |
| IMPORTING | ||
| E_RETURN | = lv_e_return | |
| . " CVI_EI_INBOUND_MAIN | ||
ABAP code using 7.40 inline data declarations to call FM CVI_EI_INBOUND_MAIN
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