DB6_CALL_COCKPIT SAP Function module - DB6: External entry into DBA Cockpit

DB6_CALL_COCKPIT 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 DB6_CALL_COCKPIT into the relevant SAP transaction such as SE37 or SE80.

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

Pattern for FM DB6_CALL_COCKPIT - DB6 CALL COCKPIT

CALL FUNCTION 'DB6_CALL_COCKPIT' "DB6: External entry into DBA Cockpit
  EXPORTING
    action =                    " i
    system_id =                 " db6navsyst-sysid  Name of SAP R/3 System
*   data =                      " any
*   show_launchpad = 'X'        " boolean       Single-Character Flag
*   as_popup = SPACE            " boolean       Boolean Variable (X=True, -=False, Space=Unknown)
*   requested_command =         " syucomm       Function Code That Triggered PAI
*   force_lock = SPACE          " boolean       Boolean Variable (X=True, -=False, Space=Unknown)
    .  "  DB6_CALL_COCKPIT

ABAP code example for Function Module DB6_CALL_COCKPIT

The ABAP code below is a full code listing to execute function module DB6_CALL_COCKPIT 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_action) = 'Check type of data required'.
 

SELECT single SYSID 
  FROM DB6NAVSYST 
  INTO @DATA(ld_system_id).


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

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

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

DATA(ld_requested_command) = 'some text here'.

DATA(ld_force_lock) = 'some text here'.
.

CALL FUNCTION 'DB6_CALL_COCKPIT'
  EXPORTING
    action =                     ld_action
    system_id =                  ld_system_id
*   data =                       ld_data
*   show_launchpad =             ld_show_launchpad
*   as_popup =                   ld_as_popup
*   requested_command =          ld_requested_command
*   force_lock =                 ld_force_lock
    .  "  DB6_CALL_COCKPIT

IF SY-SUBRC EQ 0.
  "All OK
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_action
 
 TYPE I ,
ld_system_id
 
 TYPE DB6NAVSYST-SYSID ,
ld_data
 
 TYPE ANY ,
ld_show_launchpad
 
 TYPE BOOLEAN ,
ld_as_popup
 
 TYPE BOOLEAN ,
ld_requested_command
 
 TYPE SYUCOMM ,
ld_force_lock
 
 TYPE BOOLEAN .


ld_action = 'some text here'.

SELECT single SYSID 
  FROM DB6NAVSYST 
  INTO ld_system_id.

ld_data = 'some text here'.
ld_show_launchpad = 'some text here'.
ld_as_popup = 'some text here'.
ld_requested_command = 'some text here'.
ld_force_lock = 'some text here'.