SAP HRTV_ORIGIN_GET_DRB Function Module for









HRTV_ORIGIN_GET_DRB is a standard hrtv origin get drb 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 hrtv origin get drb FM, simply by entering the name HRTV_ORIGIN_GET_DRB into the relevant SAP transaction such as SE37 or SE38.

Function Group: HRRW_ADDON
Program Name: SAPLHRRW_ADDON
Main Program: SAPLHRRW_ADDON
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function HRTV_ORIGIN_GET_DRB 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 'HRTV_ORIGIN_GET_DRB'"
EXPORTING
OBJKEY = "

EXCEPTIONS
DOES_NOT_EXIST = 1 EXISTS_IN_ARCHIVE = 2
.



IMPORTING Parameters details for HRTV_ORIGIN_GET_DRB

OBJKEY -

Data type: BAPIACHE04-OBJ_KEY
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

DOES_NOT_EXIST -

Data type:
Optional: No
Call by Reference: Yes

EXISTS_IN_ARCHIVE -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for HRTV_ORIGIN_GET_DRB 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_objkey  TYPE BAPIACHE04-OBJ_KEY, "   
lv_does_not_exist  TYPE BAPIACHE04, "   
lv_exists_in_archive  TYPE BAPIACHE04. "   

  CALL FUNCTION 'HRTV_ORIGIN_GET_DRB'  "
    EXPORTING
         OBJKEY = lv_objkey
    EXCEPTIONS
        DOES_NOT_EXIST = 1
        EXISTS_IN_ARCHIVE = 2
. " HRTV_ORIGIN_GET_DRB




ABAP code using 7.40 inline data declarations to call FM HRTV_ORIGIN_GET_DRB

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 OBJ_KEY FROM BAPIACHE04 INTO @DATA(ld_objkey).
 
 
 


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!