SAP SO_DYNP_OBJECT_SEND_DETAILS Function Module for
SO_DYNP_OBJECT_SEND_DETAILS is a standard so dynp object send details 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 so dynp object send details FM, simply by entering the name SO_DYNP_OBJECT_SEND_DETAILS into the relevant SAP transaction such as SE37 or SE38.
Function Group: SO09
Program Name: SAPLSO09
Main Program: SAPLSO09
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SO_DYNP_OBJECT_SEND_DETAILS 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_DYNP_OBJECT_SEND_DETAILS'".
EXPORTING
FOLDER_ID = "
OBJECT_ID = "
FORWARDER = "
* SNDART = "
OWNER = "
* SEND_REQUEST_GUID = "Send Request
EXCEPTIONS
OWNER_NOT_EXIST = 1 OPERATION_NO_AUTHORIZATION = 2 OBJECT_NOT_EXIST = 3 FOLDER_NOT_EXIST = 4 OBJECT_NO_AUTHORIZATION = 5 PARAMETER_ERROR = 6 X_ERROR = 7
IMPORTING Parameters details for SO_DYNP_OBJECT_SEND_DETAILS
FOLDER_ID -
Data type: SOODKOptional: No
Call by Reference: No ( called with pass by value option)
OBJECT_ID -
Data type: SOODKOptional: No
Call by Reference: No ( called with pass by value option)
FORWARDER -
Data type: SOUD-USRNAMOptional: No
Call by Reference: No ( called with pass by value option)
SNDART -
Data type: SOER-SNDARTOptional: Yes
Call by Reference: No ( called with pass by value option)
OWNER -
Data type: SOUD-USRNAMOptional: No
Call by Reference: No ( called with pass by value option)
SEND_REQUEST_GUID - Send Request
Data type: OS_GUIDOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
OWNER_NOT_EXIST -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
OPERATION_NO_AUTHORIZATION -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
OBJECT_NOT_EXIST -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
FOLDER_NOT_EXIST -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
OBJECT_NO_AUTHORIZATION -
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_DYNP_OBJECT_SEND_DETAILS 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_folder_id | TYPE SOODK, " | |||
| lv_owner_not_exist | TYPE SOODK, " | |||
| lv_object_id | TYPE SOODK, " | |||
| lv_operation_no_authorization | TYPE SOODK, " | |||
| lv_forwarder | TYPE SOUD-USRNAM, " | |||
| lv_object_not_exist | TYPE SOUD, " | |||
| lv_sndart | TYPE SOER-SNDART, " | |||
| lv_folder_not_exist | TYPE SOER, " | |||
| lv_owner | TYPE SOUD-USRNAM, " | |||
| lv_object_no_authorization | TYPE SOUD, " | |||
| lv_parameter_error | TYPE SOUD, " | |||
| lv_send_request_guid | TYPE OS_GUID, " | |||
| lv_x_error | TYPE OS_GUID. " |
|   CALL FUNCTION 'SO_DYNP_OBJECT_SEND_DETAILS' " |
| EXPORTING | ||
| FOLDER_ID | = lv_folder_id | |
| OBJECT_ID | = lv_object_id | |
| FORWARDER | = lv_forwarder | |
| SNDART | = lv_sndart | |
| OWNER | = lv_owner | |
| SEND_REQUEST_GUID | = lv_send_request_guid | |
| EXCEPTIONS | ||
| OWNER_NOT_EXIST = 1 | ||
| OPERATION_NO_AUTHORIZATION = 2 | ||
| OBJECT_NOT_EXIST = 3 | ||
| FOLDER_NOT_EXIST = 4 | ||
| OBJECT_NO_AUTHORIZATION = 5 | ||
| PARAMETER_ERROR = 6 | ||
| X_ERROR = 7 | ||
| . " SO_DYNP_OBJECT_SEND_DETAILS | ||
ABAP code using 7.40 inline data declarations to call FM SO_DYNP_OBJECT_SEND_DETAILS
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 USRNAM FROM SOUD INTO @DATA(ld_forwarder). | ||||
| "SELECT single SNDART FROM SOER INTO @DATA(ld_sndart). | ||||
| "SELECT single USRNAM FROM SOUD INTO @DATA(ld_owner). | ||||
Search for further information about these or an SAP related objects