AKB_GET_COMPATIBILITY_STATE SAP Function module

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

Associated Function Group: PA_AKB_COMPCHECK
Released Date: Not Released
Processing type: Remote-Enabled

Pattern for FM AKB_GET_COMPATIBILITY_STATE - AKB GET COMPATIBILITY STATE

CALL FUNCTION 'AKB_GET_COMPATIBILITY_STATE' "
* EXPORTING
*   check_only = 'X'            " flag
*   force_comp_check = ' '      " flag
*   display_result = ' '        " flag          Display check results
*   check_project = '9999'      " akb_project_id  ID of a Backwards-Compatibility Check
*   server =                    " akb_product   Software Product ID
*   client =                    " akb_product   Client Product
*   exception_on_rfc_error = ' '  " flag
*   expand_clas = 'X'           " flag
*   expand_fugr = 'X'           " flag
  CHANGING
    objects =                   " akb_exceptions_type  Usage Exceptions of Basis Objects by Application
  EXCEPTIONS
    RFC_ERROR = 1               "
    .  "  AKB_GET_COMPATIBILITY_STATE

ABAP code example for Function Module AKB_GET_COMPATIBILITY_STATE

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

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

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

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

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

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

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

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

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

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

CALL FUNCTION 'AKB_GET_COMPATIBILITY_STATE'
* EXPORTING
*   check_only =                 ld_check_only
*   force_comp_check =           ld_force_comp_check
*   display_result =             ld_display_result
*   check_project =              ld_check_project
*   server =                     ld_server
*   client =                     ld_client
*   exception_on_rfc_error =     ld_exception_on_rfc_error
*   expand_clas =                ld_expand_clas
*   expand_fugr =                ld_expand_fugr
  CHANGING
    objects =                    ld_objects
  EXCEPTIONS
    RFC_ERROR =                  1
    .  "  AKB_GET_COMPATIBILITY_STATE

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "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_objects
 
 TYPE AKB_EXCEPTIONS_TYPE ,
ld_check_only
 
 TYPE FLAG ,
ld_force_comp_check
 
 TYPE FLAG ,
ld_display_result
 
 TYPE FLAG ,
ld_check_project
 
 TYPE AKB_PROJECT_ID ,
ld_server
 
 TYPE AKB_PRODUCT ,
ld_client
 
 TYPE AKB_PRODUCT ,
ld_exception_on_rfc_error
 
 TYPE FLAG ,
ld_expand_clas
 
 TYPE FLAG ,
ld_expand_fugr
 
 TYPE FLAG .


ld_objects = 'Check type of data required'.
ld_check_only = 'Check type of data required'.
ld_force_comp_check = 'Check type of data required'.
ld_display_result = 'Check type of data required'.
ld_check_project = 'Check type of data required'.
ld_server = 'Check type of data required'.
ld_client = 'Check type of data required'.
ld_exception_on_rfc_error = 'Check type of data required'.
ld_expand_clas = 'Check type of data required'.
ld_expand_fugr = 'Check type of data required'.