SO_NAME_CONVERT SAP Function module

SO_NAME_CONVERT is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name SO_NAME_CONVERT into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: SOA3
Released Date: Not Released
Processing type: Remote-Enabled

Pattern for FM SO_NAME_CONVERT - SO NAME CONVERT

CALL FUNCTION 'SO_NAME_CONVERT' "
* EXPORTING
*   deleted_included = SPACE    " sonv-flag     Flag: also deleted users are converted
*   name_in = SPACE             " soud3         Field string for SAPoffice names and SAP names
*   no_address_name = SPACE     " sonv-flag
*   no_insert = SPACE           " sonv-flag
  IMPORTING
    name_out =                  " soud3         Field string for SAPoffice names and SAP names
  EXCEPTIONS
    COMMUNICATION_FAILURE = 1   "
    OFFICE_NAME_NOT_EXIST = 2   "               SAPoffice name does not exist
    PARAMETER_ERROR = 3         "               Incorrect entry of data
    SAP_NAME_NOT_EXIST = 4      "               SAP name does not exist
    SYSTEM_FAILURE = 5          "
    USER_NOT_EXIST = 6          "
    .  "  SO_NAME_CONVERT

ABAP code example for Function Module SO_NAME_CONVERT

The ABAP code below is a full code listing to execute function module SO_NAME_CONVERT including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_name_out  
 
 TYPE SOUD3
.



DATA(ld_deleted_included) = some text here

DATA(ld_name_in) = 'Check type of data required'.


DATA(ld_no_address_name) = some text here


DATA(ld_no_insert) = some text here
.

CALL FUNCTION 'SO_NAME_CONVERT'
* EXPORTING
*   deleted_included =           ld_deleted_included
*   name_in =                    ld_name_in
*   no_address_name =            ld_no_address_name
*   no_insert =                  ld_no_insert
  IMPORTING
    name_out =                   ld_name_out
  EXCEPTIONS
    COMMUNICATION_FAILURE =      1
    OFFICE_NAME_NOT_EXIST =      2
    PARAMETER_ERROR =            3
    SAP_NAME_NOT_EXIST =         4
    SYSTEM_FAILURE =             5
    USER_NOT_EXIST =             6
    .  "  SO_NAME_CONVERT

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 3. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 4. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 5. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 6. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_name_out
 
 TYPE SOUD3 ,
ld_deleted_included
 
 TYPE SONV-FLAG ,
ld_name_in
 
 TYPE SOUD3 ,
ld_no_address_name
 
 TYPE SONV-FLAG ,
ld_no_insert
 
 TYPE SONV-FLAG .



ld_deleted_included = some text here
ld_name_in = 'Check type of data required'.

ld_no_address_name = some text here

ld_no_insert = some text here