SAP HR_RO_STR2NUM Function Module for Personal Numeric Code
HR_RO_STR2NUM is a standard hr ro str2num SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Personal Numeric Code processing and below is the pattern details for this FM, 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 hr ro str2num FM, simply by entering the name HR_RO_STR2NUM into the relevant SAP transaction such as SE37 or SE38.
Function Group: 3RO2
Program Name: SAPL3RO2
Main Program: SAPL3RO2
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function HR_RO_STR2NUM 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 'HR_RO_STR2NUM'"Personal Numeric Code.
EXPORTING
CFLD_IN = "
CHANGING
* CFLD_OUT = "
* NFLD_OUT = "
EXCEPTIONS
CONVERSION_FAILED = 1
IMPORTING Parameters details for HR_RO_STR2NUM
CFLD_IN -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for HR_RO_STR2NUM
CFLD_OUT -
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
NFLD_OUT -
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
CONVERSION_FAILED -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for HR_RO_STR2NUM 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_cfld_in | TYPE STRING, " | |||
| lv_cfld_out | TYPE STRING, " | |||
| lv_conversion_failed | TYPE STRING, " | |||
| lv_nfld_out | TYPE STRING. " |
|   CALL FUNCTION 'HR_RO_STR2NUM' "Personal Numeric Code |
| EXPORTING | ||
| CFLD_IN | = lv_cfld_in | |
| CHANGING | ||
| CFLD_OUT | = lv_cfld_out | |
| NFLD_OUT | = lv_nfld_out | |
| EXCEPTIONS | ||
| CONVERSION_FAILED = 1 | ||
| . " HR_RO_STR2NUM | ||
ABAP code using 7.40 inline data declarations to call FM HR_RO_STR2NUM
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