SAP HR_RU_GET_ADDRESS Function Module for Address









HR_RU_GET_ADDRESS is a standard hr ru get address SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Address 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 ru get address FM, simply by entering the name HR_RU_GET_ADDRESS into the relevant SAP transaction such as SE37 or SE38.

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



Function HR_RU_GET_ADDRESS 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_RU_GET_ADDRESS'"Address
EXPORTING
SPRSL = "Language key
P0006 = "¾áÝÞÒÝÐï ×ÐßØáì ßÕàáÞÝÐÛÐ-ØÝäÞ-âØß 0006 (ÐÔàÕáÐ)
* THINK = "General Flag
* SEPARATOR = "
* WITH' ' = "General Flag

IMPORTING
ADDRESS = "

TABLES
LOOKS = "HR RU structure for DOS convertion
ADDRS = "HR RU structure for DOS convertion

EXCEPTIONS
NOT_FOUND = 1
.



IMPORTING Parameters details for HR_RU_GET_ADDRESS

SPRSL - Language key

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

P0006 - ¾áÝÞÒÝÐï ×ÐßØáì ßÕàáÞÝÐÛÐ-ØÝäÞ-âØß 0006 (ÐÔàÕáÐ)

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

THINK - General Flag

Data type: FLAG
Optional: Yes
Call by Reference: Yes

SEPARATOR -

Data type: STRING
Optional: Yes
Call by Reference: Yes

WITHSPACE - General Flag

Data type: FLAG
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for HR_RU_GET_ADDRESS

ADDRESS -

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

TABLES Parameters details for HR_RU_GET_ADDRESS

LOOKS - HR RU structure for DOS convertion

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

ADDRS - HR RU structure for DOS convertion

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

EXCEPTIONS details

NOT_FOUND - Records not found

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

Copy and paste ABAP code example for HR_RU_GET_ADDRESS 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:
lt_looks  TYPE STANDARD TABLE OF PRU_CHAR255, "   
lv_sprsl  TYPE SPRAS, "   
lv_address  TYPE STRING, "   
lv_not_found  TYPE STRING, "   
lt_addrs  TYPE STANDARD TABLE OF PRU_CHAR255, "   
lv_p0006  TYPE P0006, "   
lv_think  TYPE FLAG, "   
lv_separator  TYPE STRING, "   
lv_withspace  TYPE FLAG. "   

  CALL FUNCTION 'HR_RU_GET_ADDRESS'  "Address
    EXPORTING
         SPRSL = lv_sprsl
         P0006 = lv_p0006
         THINK = lv_think
         SEPARATOR = lv_separator
         WITHSPACE = lv_withspace
    IMPORTING
         ADDRESS = lv_address
    TABLES
         LOOKS = lt_looks
         ADDRS = lt_addrs
    EXCEPTIONS
        NOT_FOUND = 1
. " HR_RU_GET_ADDRESS




ABAP code using 7.40 inline data declarations to call FM HR_RU_GET_ADDRESS

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!