HR_ADDON_OBJECTTYPE_GET SAP Function module

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

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

Pattern for FM HR_ADDON_OBJECTTYPE_GET - HR ADDON OBJECTTYPE GET

CALL FUNCTION 'HR_ADDON_OBJECTTYPE_GET' "
  EXPORTING
    i_fcode =                   " sy-xcode
    i_procl =                   " t52a0-procl
    i_otype =                   " t52a0-otype
    i_oname =                   " t52a0-oname
    i_numra =                   "
  IMPORTING
    e_otype =                   "
  EXCEPTIONS
    NO_TADIR_ENTRY = 1          "
    NO_TDEVC_ENTRY = 2          "
    NO_ALLOWED_PROCL = 3        "
    NO_ALLOWED_OTYPE = 4        "
    .  "  HR_ADDON_OBJECTTYPE_GET

ABAP code example for Function Module HR_ADDON_OBJECTTYPE_GET

The ABAP code below is a full code listing to execute function module HR_ADDON_OBJECTTYPE_GET 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_e_otype  
 
 TYPE STRING
.


DATA(ld_i_fcode) = 'some text here'.
 

SELECT single PROCL 
  FROM T52A0 
  INTO @DATA(ld_i_procl).

 

SELECT single OTYPE 
  FROM T52A0 
  INTO @DATA(ld_i_otype).

 

SELECT single ONAME 
  FROM T52A0 
  INTO @DATA(ld_i_oname).


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

CALL FUNCTION 'HR_ADDON_OBJECTTYPE_GET'
  EXPORTING
    i_fcode =                    ld_i_fcode
    i_procl =                    ld_i_procl
    i_otype =                    ld_i_otype
    i_oname =                    ld_i_oname
    i_numra =                    ld_i_numra
  IMPORTING
    e_otype =                    ld_e_otype
  EXCEPTIONS
    NO_TADIR_ENTRY =             1
    NO_TDEVC_ENTRY =             2
    NO_ALLOWED_PROCL =           3
    NO_ALLOWED_OTYPE =           4
    .  "  HR_ADDON_OBJECTTYPE_GET

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_e_otype
 
 TYPE STRING ,
ld_i_fcode
 
 TYPE SY-XCODE ,
ld_i_procl
 
 TYPE T52A0-PROCL ,
ld_i_otype
 
 TYPE T52A0-OTYPE ,
ld_i_oname
 
 TYPE T52A0-ONAME ,
ld_i_numra
 
 TYPE STRING .


ld_i_fcode = 'some text here'.

SELECT single PROCL 
  FROM T52A0 
  INTO ld_i_procl.


SELECT single OTYPE 
  FROM T52A0 
  INTO ld_i_otype.


SELECT single ONAME 
  FROM T52A0 
  INTO ld_i_oname.

ld_i_numra = 'some text here'.