OBJECT_MODELLING_CHECK SAP Function module

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

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

Pattern for FM OBJECT_MODELLING_CHECK - OBJECT MODELLING CHECK

CALL FUNCTION 'OBJECT_MODELLING_CHECK' "
  EXPORTING
    f_objh =                    " v_obj_h
    message_type =              " edidc-mestyp
    sending_system =            " tbdls-logsys
    receiving_system =          " tbdls-logsys
*   model_valid_date = SY-DATUM  " sy-datum
  TABLES
    t_check_log =               " bdi_log
  EXCEPTIONS
    CHECK_STOP = 1              "
    .  "  OBJECT_MODELLING_CHECK

ABAP code example for Function Module OBJECT_MODELLING_CHECK

The ABAP code below is a full code listing to execute function module OBJECT_MODELLING_CHECK 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:
it_t_check_log  
 
 TYPE STANDARD TABLE OF BDI_LOG,"TABLES PARAM
wa_t_check_log
 
 LIKE LINE OF it_t_check_log
.


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

SELECT single MESTYP 
  FROM EDIDC 
  INTO @DATA(ld_message_type).

 

SELECT single LOGSYS 
  FROM TBDLS 
  INTO @DATA(ld_sending_system).

 

SELECT single LOGSYS 
  FROM TBDLS 
  INTO @DATA(ld_receiving_system).


DATA(ld_model_valid_date) = '20210129'.
 

"populate fields of struture and append to itab
append wa_t_check_log to it_t_check_log.
.

CALL FUNCTION 'OBJECT_MODELLING_CHECK'
  EXPORTING
    f_objh =                     ld_f_objh
    message_type =               ld_message_type
    sending_system =             ld_sending_system
    receiving_system =           ld_receiving_system
*   model_valid_date =           ld_model_valid_date
  TABLES
    t_check_log =                it_t_check_log
  EXCEPTIONS
    CHECK_STOP =                 1
    .  "  OBJECT_MODELLING_CHECK

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_f_objh
 
 TYPE V_OBJ_H ,
it_t_check_log
 
 TYPE STANDARD TABLE OF BDI_LOG ,
wa_t_check_log
 
 LIKE LINE OF it_t_check_log,
ld_message_type
 
 TYPE EDIDC-MESTYP ,
ld_sending_system
 
 TYPE TBDLS-LOGSYS ,
ld_receiving_system
 
 TYPE TBDLS-LOGSYS ,
ld_model_valid_date
 
 TYPE SY-DATUM .


ld_f_objh = '20210129'. 

"populate fields of struture and append to itab
append wa_t_check_log to it_t_check_log.

SELECT single MESTYP 
  FROM EDIDC 
  INTO ld_message_type.


SELECT single LOGSYS 
  FROM TBDLS 
  INTO ld_sending_system.


SELECT single LOGSYS 
  FROM TBDLS 
  INTO ld_receiving_system.

ld_model_valid_date = '20210129'.