SAP UMM_COCKPIT_COMPLETE_COLLECT Function Module for
UMM_COCKPIT_COMPLETE_COLLECT is a standard umm cockpit complete collect 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 umm cockpit complete collect FM, simply by entering the name UMM_COCKPIT_COMPLETE_COLLECT into the relevant SAP transaction such as SE37 or SE38.
Function Group: UMM_TRANSPORT
Program Name: SAPLUMM_TRANSPORT
Main Program: SAPLUMM_TRANSPORT
Appliation area: R
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function UMM_COCKPIT_COMPLETE_COLLECT 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 'UMM_COCKPIT_COMPLETE_COLLECT'".
EXPORTING
I_CONAME = "
* I_DEPOBJ = 'X' "
CHANGING
CT_E071 = "
CT_E071K = "
IMPORTING Parameters details for UMM_COCKPIT_COMPLETE_COLLECT
I_CONAME -
Data type: UMM_Y_CONAMEOptional: No
Call by Reference: No ( called with pass by value option)
I_DEPOBJ -
Data type:Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for UMM_COCKPIT_COMPLETE_COLLECT
CT_E071 -
Data type: TRWBO_T_E071Optional: No
Call by Reference: Yes
CT_E071K -
Data type: TRWBO_T_E071KOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for UMM_COCKPIT_COMPLETE_COLLECT 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_ct_e071 | TYPE TRWBO_T_E071, " | |||
| lv_i_coname | TYPE UMM_Y_CONAME, " | |||
| lv_ct_e071k | TYPE TRWBO_T_E071K, " | |||
| lv_i_depobj | TYPE TRWBO_T_E071K. " 'X' |
|   CALL FUNCTION 'UMM_COCKPIT_COMPLETE_COLLECT' " |
| EXPORTING | ||
| I_CONAME | = lv_i_coname | |
| I_DEPOBJ | = lv_i_depobj | |
| CHANGING | ||
| CT_E071 | = lv_ct_e071 | |
| CT_E071K | = lv_ct_e071k | |
| . " UMM_COCKPIT_COMPLETE_COLLECT | ||
ABAP code using 7.40 inline data declarations to call FM UMM_COCKPIT_COMPLETE_COLLECT
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_i_depobj) | = 'X'. | |||
Search for further information about these or an SAP related objects