SAP HRDSYS_GET_OBJNAME Function Module for









HRDSYS_GET_OBJNAME is a standard hrdsys get objname SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.


See here to view full function module documentation and code listing for hrdsys get objname FM, simply by entering the name HRDSYS_GET_OBJNAME into the relevant SAP transaction such as SE37 or SE38.

Function Group: PDOP
Program Name: SAPLPDOP
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function HRDSYS_GET_OBJNAME pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.
CALL FUNCTION 'HRDSYS_GET_OBJNAME'"
EXPORTING
* MANDT = SY-MANDT "
OTYPE = "
* MOLGA = "
ONAME = "
OBJTYPE = "

IMPORTING
OBJNAME = "

EXCEPTIONS
NOT_FOUND = 1
.



IMPORTING Parameters details for HRDSYS_GET_OBJNAME

MANDT -

Data type: SY-MANDT
Default: SY-MANDT
Optional: Yes
Call by Reference: Yes

OTYPE -

Data type: C
Optional: No
Call by Reference: Yes

MOLGA -

Data type: C
Optional: Yes
Call by Reference: Yes

ONAME -

Data type: C
Optional: No
Call by Reference: Yes

OBJTYPE -

Data type: TROBJTYPE
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for HRDSYS_GET_OBJNAME

OBJNAME -

Data type: TDOBNAME
Optional: No
Call by Reference: Yes

EXCEPTIONS details

NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for HRDSYS_GET_OBJNAME Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than 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 newer method of declaring data variables on the fly. 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), which i why i have stuck to the origianl for this example.

DATA:
lv_mandt  TYPE SY-MANDT, "   SY-MANDT
lv_objname  TYPE TDOBNAME, "   
lv_not_found  TYPE TDOBNAME, "   
lv_otype  TYPE C, "   
lv_molga  TYPE C, "   
lv_oname  TYPE C, "   
lv_objtype  TYPE TROBJTYPE. "   

  CALL FUNCTION 'HRDSYS_GET_OBJNAME'  "
    EXPORTING
         MANDT = lv_mandt
         OTYPE = lv_otype
         MOLGA = lv_molga
         ONAME = lv_oname
         OBJTYPE = lv_objtype
    IMPORTING
         OBJNAME = lv_objname
    EXCEPTIONS
        NOT_FOUND = 1
. " HRDSYS_GET_OBJNAME




ABAP code using 7.40 inline data declarations to call FM HRDSYS_GET_OBJNAME

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

"SELECT single MANDT FROM SY INTO @DATA(ld_mandt).
DATA(ld_mandt) = SY-MANDT.
 
 
 
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!