SAP UMM_COCKPIT_UPDATE Function Module for









UMM_COCKPIT_UPDATE is a standard umm cockpit update 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 update FM, simply by entering the name UMM_COCKPIT_UPDATE into the relevant SAP transaction such as SE37 or SE38.

Function Group: UMM_CUSTDATA
Program Name: SAPLUMM_CUSTDATA
Main Program: SAPLUMM_CUSTDATA
Appliation area: R
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function UMM_COCKPIT_UPDATE 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_UPDATE'"
EXPORTING
IS_COCKPITDATA = "
* I_UPDATE_DESCR = ' ' "
* IT_WALLTAB = "
* IT_VARTAB = "Variable Assignment in Cockpit
* IT_DESCRIPTION = "Business Document Service: File Content
* I_UPDATE_HEADER = ' ' "
* I_UPDATE_TEXTS = ' ' "
* I_UPDATE_HYNODE = ' ' "
* I_UPDATE_WALLS = ' ' "
* I_UPDATE_VARS = ' ' "

EXCEPTIONS
COCKPIT_NOT_FOUND = 1 NO_AUTHORITY = 2 OBJECT_LOCKED = 3 NO_UPDATE_REQUESTED = 4
.



IMPORTING Parameters details for UMM_COCKPIT_UPDATE

IS_COCKPITDATA -

Data type: UMM_YS_CUST_COCKPITDATA
Optional: No
Call by Reference: Yes

I_UPDATE_DESCR -

Data type: C
Default: ' '
Optional: Yes
Call by Reference: Yes

IT_WALLTAB -

Data type: UMM_YT_CUST_COCKPITWALLS
Optional: Yes
Call by Reference: Yes

IT_VARTAB - Variable Assignment in Cockpit

Data type: UMM_YT_CUST_COCKPITVARS
Optional: Yes
Call by Reference: Yes

IT_DESCRIPTION - Business Document Service: File Content

Data type: SBDST_CONTENT
Optional: Yes
Call by Reference: Yes

I_UPDATE_HEADER -

Data type: C
Default: ' '
Optional: Yes
Call by Reference: Yes

I_UPDATE_TEXTS -

Data type: C
Default: ' '
Optional: Yes
Call by Reference: Yes

I_UPDATE_HYNODE -

Data type: C
Default: ' '
Optional: Yes
Call by Reference: Yes

I_UPDATE_WALLS -

Data type: C
Default: ' '
Optional: Yes
Call by Reference: Yes

I_UPDATE_VARS -

Data type: C
Default: ' '
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

COCKPIT_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

NO_AUTHORITY - No Authorization

Data type:
Optional: No
Call by Reference: Yes

OBJECT_LOCKED - Object Locked

Data type:
Optional: No
Call by Reference: Yes

NO_UPDATE_REQUESTED -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for UMM_COCKPIT_UPDATE 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_is_cockpitdata  TYPE UMM_YS_CUST_COCKPITDATA, "   
lv_cockpit_not_found  TYPE UMM_YS_CUST_COCKPITDATA, "   
lv_i_update_descr  TYPE C, "   ' '
lv_it_walltab  TYPE UMM_YT_CUST_COCKPITWALLS, "   
lv_no_authority  TYPE UMM_YT_CUST_COCKPITWALLS, "   
lv_it_vartab  TYPE UMM_YT_CUST_COCKPITVARS, "   
lv_object_locked  TYPE UMM_YT_CUST_COCKPITVARS, "   
lv_it_description  TYPE SBDST_CONTENT, "   
lv_no_update_requested  TYPE SBDST_CONTENT, "   
lv_i_update_header  TYPE C, "   ' '
lv_i_update_texts  TYPE C, "   ' '
lv_i_update_hynode  TYPE C, "   ' '
lv_i_update_walls  TYPE C, "   ' '
lv_i_update_vars  TYPE C. "   ' '

  CALL FUNCTION 'UMM_COCKPIT_UPDATE'  "
    EXPORTING
         IS_COCKPITDATA = lv_is_cockpitdata
         I_UPDATE_DESCR = lv_i_update_descr
         IT_WALLTAB = lv_it_walltab
         IT_VARTAB = lv_it_vartab
         IT_DESCRIPTION = lv_it_description
         I_UPDATE_HEADER = lv_i_update_header
         I_UPDATE_TEXTS = lv_i_update_texts
         I_UPDATE_HYNODE = lv_i_update_hynode
         I_UPDATE_WALLS = lv_i_update_walls
         I_UPDATE_VARS = lv_i_update_vars
    EXCEPTIONS
        COCKPIT_NOT_FOUND = 1
        NO_AUTHORITY = 2
        OBJECT_LOCKED = 3
        NO_UPDATE_REQUESTED = 4
. " UMM_COCKPIT_UPDATE




ABAP code using 7.40 inline data declarations to call FM UMM_COCKPIT_UPDATE

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_update_descr) = ' '.
 
 
 
 
 
 
 
DATA(ld_i_update_header) = ' '.
 
DATA(ld_i_update_texts) = ' '.
 
DATA(ld_i_update_hynode) = ' '.
 
DATA(ld_i_update_walls) = ' '.
 
DATA(ld_i_update_vars) = ' '.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!