SAP SO_ADDRESS_CONVERT Function Module for SAPoffice: Recipient determination
SO_ADDRESS_CONVERT is a standard so address convert SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for SAPoffice: Recipient determination 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 address convert FM, simply by entering the name SO_ADDRESS_CONVERT into the relevant SAP transaction such as SE37 or SE38.
Function Group: SOE3
Program Name: SAPLSOE3
Main Program: SAPLSOE3
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SO_ADDRESS_CONVERT 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_ADDRESS_CONVERT'"SAPoffice: Recipient determination.
EXPORTING
RECEIVER = "Recipient of document
* SENDER = ' ' "Document sender
TABLES
* FORMAT = "Document type/format
REC_RESULT = "Table of (new) recipients determined
EXCEPTIONS
ADDRESS_NOT_FOUND = 1 OPERATION_NO_AUTHORIZATION = 2 PARAMETER_ERROR = 3 DLI_NOT_EXIST = 4 X_ERROR = 5
IMPORTING Parameters details for SO_ADDRESS_CONVERT
RECEIVER - Recipient of document
Data type: SX_ADDRESSOptional: No
Call by Reference: No ( called with pass by value option)
SENDER - Document sender
Data type: SX_ADDRESSDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for SO_ADDRESS_CONVERT
FORMAT - Document type/format
Data type: DOC_STRUCTOptional: Yes
Call by Reference: No ( called with pass by value option)
REC_RESULT - Table of (new) recipients determined
Data type: SX_REMOTE_ADDRESS_TABOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ADDRESS_NOT_FOUND - Unable to determine recipient
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
OPERATION_NO_AUTHORIZATION - No authorization for function module call
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
PARAMETER_ERROR - Invalid address (e.g., type missing)
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
DLI_NOT_EXIST - Distribution list specified does not exist
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_ADDRESS_CONVERT 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_format | TYPE STANDARD TABLE OF DOC_STRUCT, " | |||
| lv_receiver | TYPE SX_ADDRESS, " | |||
| lv_address_not_found | TYPE SX_ADDRESS, " | |||
| lv_sender | TYPE SX_ADDRESS, " SPACE | |||
| lt_rec_result | TYPE STANDARD TABLE OF SX_REMOTE_ADDRESS_TAB, " | |||
| lv_operation_no_authorization | TYPE SX_REMOTE_ADDRESS_TAB, " | |||
| lv_parameter_error | TYPE SX_REMOTE_ADDRESS_TAB, " | |||
| lv_dli_not_exist | TYPE SX_REMOTE_ADDRESS_TAB, " | |||
| lv_x_error | TYPE SX_REMOTE_ADDRESS_TAB. " |
|   CALL FUNCTION 'SO_ADDRESS_CONVERT' "SAPoffice: Recipient determination |
| EXPORTING | ||
| RECEIVER | = lv_receiver | |
| SENDER | = lv_sender | |
| TABLES | ||
| FORMAT | = lt_format | |
| REC_RESULT | = lt_rec_result | |
| EXCEPTIONS | ||
| ADDRESS_NOT_FOUND = 1 | ||
| OPERATION_NO_AUTHORIZATION = 2 | ||
| PARAMETER_ERROR = 3 | ||
| DLI_NOT_EXIST = 4 | ||
| X_ERROR = 5 | ||
| . " SO_ADDRESS_CONVERT | ||
ABAP code using 7.40 inline data declarations to call FM SO_ADDRESS_CONVERT
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.| DATA(ld_sender) | = ' '. | |||
Search for further information about these or an SAP related objects