SAP HRPP_DESTINATION_GET Function Module for









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

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



Function HRPP_DESTINATION_GET 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 'HRPP_DESTINATION_GET'"
EXPORTING
I_BUKRS = "
I_OBJECT = "
I_METHOD = "
I_SW_ASYNC = "

IMPORTING
E_BAPI_RECEIVER = "

TABLES
* T_RECEIVER_INPUT = "
* T_IDOC_RECEIVERS = "
T_RETURN = "
.



IMPORTING Parameters details for HRPP_DESTINATION_GET

I_BUKRS -

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

I_OBJECT -

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

I_METHOD -

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

I_SW_ASYNC -

Data type: C
Optional: No
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for HRPP_DESTINATION_GET

E_BAPI_RECEIVER -

Data type: BDBAPIDEST
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for HRPP_DESTINATION_GET

T_RECEIVER_INPUT -

Data type: BDI_LOGSYS
Optional: Yes
Call by Reference: No ( called with pass by value option)

T_IDOC_RECEIVERS -

Data type: BDI_LOGSYS
Optional: Yes
Call by Reference: No ( called with pass by value option)

T_RETURN -

Data type: BAPIRETURN1
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for HRPP_DESTINATION_GET 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_i_bukrs  TYPE PPDHD-BUKRS, "   
lv_e_bapi_receiver  TYPE BDBAPIDEST, "   
lt_t_receiver_input  TYPE STANDARD TABLE OF BDI_LOGSYS, "   
lv_i_object  TYPE BDI_BAPI-OBJECT, "   
lt_t_idoc_receivers  TYPE STANDARD TABLE OF BDI_LOGSYS, "   
lv_i_method  TYPE BDI_BAPI-METHOD, "   
lt_t_return  TYPE STANDARD TABLE OF BAPIRETURN1, "   
lv_i_sw_async  TYPE C. "   

  CALL FUNCTION 'HRPP_DESTINATION_GET'  "
    EXPORTING
         I_BUKRS = lv_i_bukrs
         I_OBJECT = lv_i_object
         I_METHOD = lv_i_method
         I_SW_ASYNC = lv_i_sw_async
    IMPORTING
         E_BAPI_RECEIVER = lv_e_bapi_receiver
    TABLES
         T_RECEIVER_INPUT = lt_t_receiver_input
         T_IDOC_RECEIVERS = lt_t_idoc_receivers
         T_RETURN = lt_t_return
. " HRPP_DESTINATION_GET




ABAP code using 7.40 inline data declarations to call FM HRPP_DESTINATION_GET

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 BUKRS FROM PPDHD INTO @DATA(ld_i_bukrs).
 
 
 
"SELECT single OBJECT FROM BDI_BAPI INTO @DATA(ld_i_object).
 
 
"SELECT single METHOD FROM BDI_BAPI INTO @DATA(ld_i_method).
 
 
 


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!