SAP SO_USER_ADDR_REFERENCE_CHANGE Function Module for Function for changing where-used list for addresses









SO_USER_ADDR_REFERENCE_CHANGE is a standard so user addr reference change SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Function for changing where-used list for addresses 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 so user addr reference change FM, simply by entering the name SO_USER_ADDR_REFERENCE_CHANGE into the relevant SAP transaction such as SE37 or SE38.

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



Function SO_USER_ADDR_REFERENCE_CHANGE 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 'SO_USER_ADDR_REFERENCE_CHANGE'"Function for changing where-used list for addresses
EXPORTING
SAPNAME = "
* SO_KEY = ' ' "
* IDADTYPE = '99' "
* CHANGEFLAG = ' ' "
* SUPPRESS_EXPORT_TO_MEMORY = ' ' "

EXCEPTIONS
SAP_NAME_NOT_EXIST = 1 SAP_OFFICE_NOT_EXIST = 2 REFERENCE_ERROR = 3 NO_ADDR_FOR_SO_KEY = 4 SO_KEY_IS_SPACE = 5 PARAMETER_ERROR = 6 X_ERROR = 7
.



IMPORTING Parameters details for SO_USER_ADDR_REFERENCE_CHANGE

SAPNAME -

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

SO_KEY -

Data type: SOUD-USRADR
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

IDADTYPE -

Data type: USR21-IDADTYPE
Default: '99'
Optional: Yes
Call by Reference: No ( called with pass by value option)

CHANGEFLAG -

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

SUPPRESS_EXPORT_TO_MEMORY -

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

EXCEPTIONS details

SAP_NAME_NOT_EXIST -

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

SAP_OFFICE_NOT_EXIST -

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

REFERENCE_ERROR -

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

NO_ADDR_FOR_SO_KEY -

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

SO_KEY_IS_SPACE -

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

PARAMETER_ERROR -

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

X_ERROR -

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

Copy and paste ABAP code example for SO_USER_ADDR_REFERENCE_CHANGE 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_sapname  TYPE SOUD-SAPNAM, "   
lv_sap_name_not_exist  TYPE SOUD, "   
lv_so_key  TYPE SOUD-USRADR, "   SPACE
lv_sap_office_not_exist  TYPE SOUD, "   
lv_idadtype  TYPE USR21-IDADTYPE, "   '99'
lv_reference_error  TYPE USR21, "   
lv_changeflag  TYPE USR21, "   SPACE
lv_no_addr_for_so_key  TYPE USR21, "   
lv_so_key_is_space  TYPE USR21, "   
lv_suppress_export_to_memory  TYPE SO_FLAG, "   SPACE
lv_parameter_error  TYPE SO_FLAG, "   
lv_x_error  TYPE SO_FLAG. "   

  CALL FUNCTION 'SO_USER_ADDR_REFERENCE_CHANGE'  "Function for changing where-used list for addresses
    EXPORTING
         SAPNAME = lv_sapname
         SO_KEY = lv_so_key
         IDADTYPE = lv_idadtype
         CHANGEFLAG = lv_changeflag
         SUPPRESS_EXPORT_TO_MEMORY = lv_suppress_export_to_memory
    EXCEPTIONS
        SAP_NAME_NOT_EXIST = 1
        SAP_OFFICE_NOT_EXIST = 2
        REFERENCE_ERROR = 3
        NO_ADDR_FOR_SO_KEY = 4
        SO_KEY_IS_SPACE = 5
        PARAMETER_ERROR = 6
        X_ERROR = 7
. " SO_USER_ADDR_REFERENCE_CHANGE




ABAP code using 7.40 inline data declarations to call FM SO_USER_ADDR_REFERENCE_CHANGE

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 SAPNAM FROM SOUD INTO @DATA(ld_sapname).
 
 
"SELECT single USRADR FROM SOUD INTO @DATA(ld_so_key).
DATA(ld_so_key) = ' '.
 
 
"SELECT single IDADTYPE FROM USR21 INTO @DATA(ld_idadtype).
DATA(ld_idadtype) = '99'.
 
 
DATA(ld_changeflag) = ' '.
 
 
 
DATA(ld_suppress_export_to_memory) = ' '.
 
 
 


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!