SAP RH_CONVERT_KEY_INPUT Function Module for









RH_CONVERT_KEY_INPUT is a standard rh convert key input 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 rh convert key input FM, simply by entering the name RH_CONVERT_KEY_INPUT into the relevant SAP transaction such as SE37 or SE38.

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



Function RH_CONVERT_KEY_INPUT 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 'RH_CONVERT_KEY_INPUT'"
EXPORTING
ACT_OTYPE = "
ACT_OBJID_IN = "

IMPORTING
ACT_OBJID = "
.



IMPORTING Parameters details for RH_CONVERT_KEY_INPUT

ACT_OTYPE -

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

ACT_OBJID_IN -

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

EXPORTING Parameters details for RH_CONVERT_KEY_INPUT

ACT_OBJID -

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

Copy and paste ABAP code example for RH_CONVERT_KEY_INPUT 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_act_objid  TYPE ANY, "   
lv_act_otype  TYPE OTYPE, "   
lv_act_objid_in  TYPE ANY. "   

  CALL FUNCTION 'RH_CONVERT_KEY_INPUT'  "
    EXPORTING
         ACT_OTYPE = lv_act_otype
         ACT_OBJID_IN = lv_act_objid_in
    IMPORTING
         ACT_OBJID = lv_act_objid
. " RH_CONVERT_KEY_INPUT




ABAP code using 7.40 inline data declarations to call FM RH_CONVERT_KEY_INPUT

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.

 
 
 


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!