FIOTPDB_UPD_OBJ_KEY SAP Function module

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

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

Pattern for FM FIOTPDB_UPD_OBJ_KEY - FIOTPDB UPD OBJ KEY

CALL FUNCTION 'FIOTPDB_UPD_OBJ_KEY' "
  EXPORTING
    i_otp_object =              " fiotp_object
    i_accrule =                 " accounting_principle
    i_docgroup =                " fiotp_docgroup
    i_testrun =                 " testrun
    i_obj_type =                " awtyp
    i_obj_key =                 " awkey
    i_obj_sys =                 " awsys
  EXCEPTIONS
    ERROR_OCCURED = 1           "
    .  "  FIOTPDB_UPD_OBJ_KEY

ABAP code example for Function Module FIOTPDB_UPD_OBJ_KEY

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

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

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

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

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

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

DATA(ld_i_obj_sys) = '20210129'.
.

CALL FUNCTION 'FIOTPDB_UPD_OBJ_KEY'
  EXPORTING
    i_otp_object =               ld_i_otp_object
    i_accrule =                  ld_i_accrule
    i_docgroup =                 ld_i_docgroup
    i_testrun =                  ld_i_testrun
    i_obj_type =                 ld_i_obj_type
    i_obj_key =                  ld_i_obj_key
    i_obj_sys =                  ld_i_obj_sys
  EXCEPTIONS
    ERROR_OCCURED =              1
    .  "  FIOTPDB_UPD_OBJ_KEY

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_i_otp_object
 
 TYPE FIOTP_OBJECT ,
ld_i_accrule
 
 TYPE ACCOUNTING_PRINCIPLE ,
ld_i_docgroup
 
 TYPE FIOTP_DOCGROUP ,
ld_i_testrun
 
 TYPE TESTRUN ,
ld_i_obj_type
 
 TYPE AWTYP ,
ld_i_obj_key
 
 TYPE AWKEY ,
ld_i_obj_sys
 
 TYPE AWSYS .


ld_i_otp_object = 'some text here'.
ld_i_accrule = 'some text here'.
ld_i_docgroup = 'some text here'.
ld_i_testrun = 'some text here'.
ld_i_obj_type = 'some text here'.
ld_i_obj_key = 'some text here'.
ld_i_obj_sys = '20210129'.