SAP SX_OBJECTS_SEND Function Module for
SX_OBJECTS_SEND is a standard sx objects send SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 sx objects send FM, simply by entering the name SX_OBJECTS_SEND into the relevant SAP transaction such as SE37 or SE38.
Function Group: SX01
Program Name: SAPLSX01
Main Program: SAPLSX01
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function SX_OBJECTS_SEND 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 'SX_OBJECTS_SEND'".
EXPORTING
* ADDRESS_TYPES = "SAPconnect: Address type
* OBJECT_ID = "SAPconnect: SAPoffice object ID
* DIALOG = "SAPconnect: Selection
* OUTPUT = "SAPconnect: Selection
* JOB_PARAMS = "
IMPORTING
NR_SO_OBJECTS = "
CANCEL = "
TABLES
* OBJ_CAT = "SAPconnect: Object catalog entry
EXCEPTIONS
PARAMETER_ERROR = 1 DIALOG_ERROR = 2 INTERNAL_ERROR = 3 INVALID_ADDR_TYPE = 4
IMPORTING Parameters details for SX_OBJECTS_SEND
ADDRESS_TYPES - SAPconnect: Address type
Data type: SX_ADDRTABOptional: Yes
Call by Reference: No ( called with pass by value option)
OBJECT_ID - SAPconnect: SAPoffice object ID
Data type: SX_OBJ_IDOptional: Yes
Call by Reference: No ( called with pass by value option)
DIALOG - SAPconnect: Selection
Data type: SX_BOOLEANOptional: Yes
Call by Reference: No ( called with pass by value option)
OUTPUT - SAPconnect: Selection
Data type: SX_BOOLEANOptional: Yes
Call by Reference: No ( called with pass by value option)
JOB_PARAMS -
Data type: SXJOBSOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for SX_OBJECTS_SEND
NR_SO_OBJECTS -
Data type: IOptional: No
Call by Reference: No ( called with pass by value option)
CANCEL -
Data type: SX_BOOLEANOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for SX_OBJECTS_SEND
OBJ_CAT - SAPconnect: Object catalog entry
Data type: SXOBJCATOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
PARAMETER_ERROR -
Data type:Optional: No
Call by Reference: Yes
DIALOG_ERROR -
Data type:Optional: No
Call by Reference: Yes
INTERNAL_ERROR -
Data type:Optional: No
Call by Reference: Yes
INVALID_ADDR_TYPE -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for SX_OBJECTS_SEND 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_obj_cat | TYPE STANDARD TABLE OF SXOBJCAT, " | |||
| lv_address_types | TYPE SX_ADDRTAB, " | |||
| lv_nr_so_objects | TYPE I, " | |||
| lv_parameter_error | TYPE I, " | |||
| lv_cancel | TYPE SX_BOOLEAN, " | |||
| lv_object_id | TYPE SX_OBJ_ID, " | |||
| lv_dialog_error | TYPE SX_OBJ_ID, " | |||
| lv_dialog | TYPE SX_BOOLEAN, " | |||
| lv_internal_error | TYPE SX_BOOLEAN, " | |||
| lv_output | TYPE SX_BOOLEAN, " | |||
| lv_invalid_addr_type | TYPE SX_BOOLEAN, " | |||
| lv_job_params | TYPE SXJOBS. " |
|   CALL FUNCTION 'SX_OBJECTS_SEND' " |
| EXPORTING | ||
| ADDRESS_TYPES | = lv_address_types | |
| OBJECT_ID | = lv_object_id | |
| DIALOG | = lv_dialog | |
| OUTPUT | = lv_output | |
| JOB_PARAMS | = lv_job_params | |
| IMPORTING | ||
| NR_SO_OBJECTS | = lv_nr_so_objects | |
| CANCEL | = lv_cancel | |
| TABLES | ||
| OBJ_CAT | = lt_obj_cat | |
| EXCEPTIONS | ||
| PARAMETER_ERROR = 1 | ||
| DIALOG_ERROR = 2 | ||
| INTERNAL_ERROR = 3 | ||
| INVALID_ADDR_TYPE = 4 | ||
| . " SX_OBJECTS_SEND | ||
ABAP code using 7.40 inline data declarations to call FM SX_OBJECTS_SEND
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