SAP ACE_SOP_GET_RFC_PARAM_FOR_HR Function Module for
ACE_SOP_GET_RFC_PARAM_FOR_HR is a standard ace sop get rfc param for hr 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 ace sop get rfc param for hr FM, simply by entering the name ACE_SOP_GET_RFC_PARAM_FOR_HR into the relevant SAP transaction such as SE37 or SE38.
Function Group: ACE_SOP_RFC_SERVICES
Program Name: SAPLACE_SOP_RFC_SERVICES
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ACE_SOP_GET_RFC_PARAM_FOR_HR 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 'ACE_SOP_GET_RFC_PARAM_FOR_HR'".
IMPORTING
ED_DESTINATION = "
ED_OBJTYPE = "
ED_METHOD = "
ED_PARAMETER = "
EXCEPTIONS
CONNECTION_NOT_DEFINED = 1
EXPORTING Parameters details for ACE_SOP_GET_RFC_PARAM_FOR_HR
ED_DESTINATION -
Data type: ACE_SOP_RFC_DESTINATIONOptional: No
Call by Reference: Yes
ED_OBJTYPE -
Data type: BAPIF4A-OBJTYPEOptional: No
Call by Reference: Yes
ED_METHOD -
Data type: BAPIF4A-METHODOptional: No
Call by Reference: Yes
ED_PARAMETER -
Data type: BAPIF4A-PARAMOptional: No
Call by Reference: Yes
EXCEPTIONS details
CONNECTION_NOT_DEFINED -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ACE_SOP_GET_RFC_PARAM_FOR_HR 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_ed_destination | TYPE ACE_SOP_RFC_DESTINATION, " | |||
| lv_connection_not_defined | TYPE ACE_SOP_RFC_DESTINATION, " | |||
| lv_ed_objtype | TYPE BAPIF4A-OBJTYPE, " | |||
| lv_ed_method | TYPE BAPIF4A-METHOD, " | |||
| lv_ed_parameter | TYPE BAPIF4A-PARAM. " |
|   CALL FUNCTION 'ACE_SOP_GET_RFC_PARAM_FOR_HR' " |
| IMPORTING | ||
| ED_DESTINATION | = lv_ed_destination | |
| ED_OBJTYPE | = lv_ed_objtype | |
| ED_METHOD | = lv_ed_method | |
| ED_PARAMETER | = lv_ed_parameter | |
| EXCEPTIONS | ||
| CONNECTION_NOT_DEFINED = 1 | ||
| . " ACE_SOP_GET_RFC_PARAM_FOR_HR | ||
ABAP code using 7.40 inline data declarations to call FM ACE_SOP_GET_RFC_PARAM_FOR_HR
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 OBJTYPE FROM BAPIF4A INTO @DATA(ld_ed_objtype). | ||||
| "SELECT single METHOD FROM BAPIF4A INTO @DATA(ld_ed_method). | ||||
| "SELECT single PARAM FROM BAPIF4A INTO @DATA(ld_ed_parameter). | ||||
Search for further information about these or an SAP related objects