UMM_COCKPIT_GET SAP Function module

UMM_COCKPIT_GET is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name UMM_COCKPIT_GET into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: UMM_CUSTDATA
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM UMM_COCKPIT_GET - UMM COCKPIT GET

CALL FUNCTION 'UMM_COCKPIT_GET' "
  EXPORTING
    i_coname =                  " umm_y_coname
*   i_lock_flg = ' '            " c
  IMPORTING
    es_cockpitdata =            " umm_ys_cust_cockpitdata
    et_walltab =                " umm_yt_cust_cockpitwalls
    et_vartab =                 " umm_yt_cust_cockpitvars  Variable Assignment in Cockpit
    et_description =            " sbdst_content  Business Document Service: File Content
  EXCEPTIONS
    COCKPIT_NOT_FOUND = 1       "
    NO_AUTHORITY = 2            "               No Authorization
    OBJECT_LOCKED = 3           "               Object Locked
    .  "  UMM_COCKPIT_GET

ABAP code example for Function Module UMM_COCKPIT_GET

The ABAP code below is a full code listing to execute function module UMM_COCKPIT_GET including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_es_cockpitdata  
 
 TYPE UMM_YS_CUST_COCKPITDATA
,
ld_et_walltab  
 
 TYPE UMM_YT_CUST_COCKPITWALLS
,
ld_et_vartab  
 
 TYPE UMM_YT_CUST_COCKPITVARS
,
ld_et_description  
 
 TYPE SBDST_CONTENT
.


DATA(ld_i_coname) = 'Check type of data required'.

DATA(ld_i_lock_flg) = 'Check type of data required'.
.

CALL FUNCTION 'UMM_COCKPIT_GET'
  EXPORTING
    i_coname =                   ld_i_coname
*   i_lock_flg =                 ld_i_lock_flg
  IMPORTING
    es_cockpitdata =             ld_es_cockpitdata
    et_walltab =                 ld_et_walltab
    et_vartab =                  ld_et_vartab
    et_description =             ld_et_description
  EXCEPTIONS
    COCKPIT_NOT_FOUND =          1
    NO_AUTHORITY =               2
    OBJECT_LOCKED =              3
    .  "  UMM_COCKPIT_GET

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 3. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_es_cockpitdata
 
 TYPE UMM_YS_CUST_COCKPITDATA ,
ld_i_coname
 
 TYPE UMM_Y_CONAME ,
ld_et_walltab
 
 TYPE UMM_YT_CUST_COCKPITWALLS ,
ld_i_lock_flg
 
 TYPE C ,
ld_et_vartab
 
 TYPE UMM_YT_CUST_COCKPITVARS ,
ld_et_description
 
 TYPE SBDST_CONTENT .


ld_i_coname = 'Check type of data required'.
ld_i_lock_flg = 'Check type of data required'.