SBIZC_GET_OBJECT_INFO SAP Function module

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

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

Pattern for FM SBIZC_GET_OBJECT_INFO - SBIZC GET OBJECT INFO

CALL FUNCTION 'SBIZC_GET_OBJECT_INFO' "
  EXPORTING
    ip_usage =                  " bizc_usage
*   ip_object =                 " bizc_objguid
    ip_langu =                  " sylangu
  IMPORTING
    es_info =                   " bizc_object_info
    et_errors =                 " bizc_error_tab
  EXCEPTIONS
    COMMUNICATION_PROBLEM = 1   "
    INTERNAL_ERROR = 2          "
    NO_INFO_SERVICE = 3         "
    OBJECT_NOT_FOUND = 4        "
    .  "  SBIZC_GET_OBJECT_INFO

ABAP code example for Function Module SBIZC_GET_OBJECT_INFO

The ABAP code below is a full code listing to execute function module SBIZC_GET_OBJECT_INFO 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_info  
 
 TYPE BIZC_OBJECT_INFO
,
ld_et_errors  
 
 TYPE BIZC_ERROR_TAB
.


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

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

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

CALL FUNCTION 'SBIZC_GET_OBJECT_INFO'
  EXPORTING
    ip_usage =                   ld_ip_usage
*   ip_object =                  ld_ip_object
    ip_langu =                   ld_ip_langu
  IMPORTING
    es_info =                    ld_es_info
    et_errors =                  ld_et_errors
  EXCEPTIONS
    COMMUNICATION_PROBLEM =      1
    INTERNAL_ERROR =             2
    NO_INFO_SERVICE =            3
    OBJECT_NOT_FOUND =           4
    .  "  SBIZC_GET_OBJECT_INFO

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
ELSEIF SY-SUBRC EQ 4. "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_info
 
 TYPE BIZC_OBJECT_INFO ,
ld_ip_usage
 
 TYPE BIZC_USAGE ,
ld_et_errors
 
 TYPE BIZC_ERROR_TAB ,
ld_ip_object
 
 TYPE BIZC_OBJGUID ,
ld_ip_langu
 
 TYPE SYLANGU .


ld_ip_usage = 'Check type of data required'.
ld_ip_object = 'Check type of data required'.
ld_ip_langu = 'Check type of data required'.