SAP SO_USER_COMP_ADDR_CHANGE Function Module for If company address is changed via CAM, show change in where-used list









SO_USER_COMP_ADDR_CHANGE is a standard so user comp addr 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 If company address is changed via CAM, show change in where-used list 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 comp addr change FM, simply by entering the name SO_USER_COMP_ADDR_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_COMP_ADDR_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_COMP_ADDR_CHANGE'"If company address is changed via CAM, show change in where-used list
  EXPORTING
   SAPNAME =  "SAP user
   PERSNUMBER =  "
   OLDADDRNUMBER =  "
   NEWADDRNUMBER =  "

EXCEPTIONS
   SAPNAME_HAS_NO_OFFICE = 1    REF_PERSON_NOT_EXIST = 2    REF_INTERNAL_ERROR = 3    REF_PARAMETER_ERROR = 4    REF_OLD_REF_NOT_EXIST = 5    REF_NEW_REF_EXISTS = 6    REF_NUMBERRANGE_ERROR = 7    X_ERROR = 8
.



IMPORTING Parameters details for SO_USER_COMP_ADDR_CHANGE

SAPNAME - SAP user

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

PERSNUMBER -

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

OLDADDRNUMBER -

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

NEWADDRNUMBER -

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

EXCEPTIONS details

SAPNAME_HAS_NO_OFFICE -

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

REF_PERSON_NOT_EXIST -

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

REF_INTERNAL_ERROR -

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

REF_PARAMETER_ERROR -

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

REF_OLD_REF_NOT_EXIST -

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

REF_NEW_REF_EXISTS -

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

REF_NUMBERRANGE_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_COMP_ADDR_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_sapname_has_no_office  TYPE SOUD, "   
lv_persnumber  TYPE ADRP-PERSNUMBER, "   
lv_ref_person_not_exist  TYPE ADRP, "   
lv_oldaddrnumber  TYPE ADRC-ADDRNUMBER, "   
lv_ref_internal_error  TYPE ADRC, "   
lv_newaddrnumber  TYPE ADRC-ADDRNUMBER, "   
lv_ref_parameter_error  TYPE ADRC, "   
lv_ref_old_ref_not_exist  TYPE ADRC, "   
lv_ref_new_ref_exists  TYPE ADRC, "   
lv_ref_numberrange_error  TYPE ADRC, "   
lv_x_error  TYPE ADRC. "   

  CALL FUNCTION 'SO_USER_COMP_ADDR_CHANGE'  "If company address is changed via CAM, show change in where-used list
    EXPORTING
         SAPNAME = lv_sapname
         PERSNUMBER = lv_persnumber
         OLDADDRNUMBER = lv_oldaddrnumber
         NEWADDRNUMBER = lv_newaddrnumber
    EXCEPTIONS
        SAPNAME_HAS_NO_OFFICE = 1
        REF_PERSON_NOT_EXIST = 2
        REF_INTERNAL_ERROR = 3
        REF_PARAMETER_ERROR = 4
        REF_OLD_REF_NOT_EXIST = 5
        REF_NEW_REF_EXISTS = 6
        REF_NUMBERRANGE_ERROR = 7
        X_ERROR = 8
. " SO_USER_COMP_ADDR_CHANGE




ABAP code using 7.40 inline data declarations to call FM SO_USER_COMP_ADDR_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 PERSNUMBER FROM ADRP INTO @DATA(ld_persnumber).
 
 
"SELECT single ADDRNUMBER FROM ADRC INTO @DATA(ld_oldaddrnumber).
 
 
"SELECT single ADDRNUMBER FROM ADRC INTO @DATA(ld_newaddrnumber).
 
 
 
 
 
 


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!