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

Function SO_ATTACHMENT_DELETE 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_ATTACHMENT_DELETE'".
EXPORTING
OBJECT_ID = "Object ID
ATTACH_ID = "
* OWNER = ' ' "Owner of object
* PUT_IN_WASTEBASKET = 'X' "'X' =The document is placed in the trash
EXCEPTIONS
OBJECT_NOT_EXIST = 1 OBJECT_NO_AUTHORIZATION = 2 OPERATION_NO_AUTHORIZATION = 3 OWNER_NOT_EXIST = 4 SUBSTITUTE_NOT_ACTIVE = 5 SUBSTITUTE_NOT_DEFINED = 6 X_ERROR = 7 COMMUNICATION_FAILURE = 8 SYSTEM_FAILURE = 9
IMPORTING Parameters details for SO_ATTACHMENT_DELETE
OBJECT_ID - Object ID
Data type: SOODKOptional: No
Call by Reference: No ( called with pass by value option)
ATTACH_ID -
Data type: SOODKOptional: No
Call by Reference: No ( called with pass by value option)
OWNER - Owner of object
Data type: SOUD-USRNAMDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
PUT_IN_WASTEBASKET - 'X' =The document is placed in the trash
Data type: SONV-FLAGDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
OBJECT_NOT_EXIST - Object does not exist
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
OBJECT_NO_AUTHORIZATION - No authorization for this object
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
OPERATION_NO_AUTHORIZATION - No authorization for the operation
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
OWNER_NOT_EXIST - Owner does not exist
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SUBSTITUTE_NOT_ACTIVE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SUBSTITUTE_NOT_DEFINED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
X_ERROR - Internal error
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
COMMUNICATION_FAILURE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SYSTEM_FAILURE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SO_ATTACHMENT_DELETE 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_object_id | TYPE SOODK, " | |||
| lv_object_not_exist | TYPE SOODK, " | |||
| lv_attach_id | TYPE SOODK, " | |||
| lv_object_no_authorization | TYPE SOODK, " | |||
| lv_owner | TYPE SOUD-USRNAM, " SPACE | |||
| lv_operation_no_authorization | TYPE SOUD, " | |||
| lv_owner_not_exist | TYPE SOUD, " | |||
| lv_put_in_wastebasket | TYPE SONV-FLAG, " 'X' | |||
| lv_substitute_not_active | TYPE SONV, " | |||
| lv_substitute_not_defined | TYPE SONV, " | |||
| lv_x_error | TYPE SONV, " | |||
| lv_communication_failure | TYPE SONV, " | |||
| lv_system_failure | TYPE SONV. " |
|   CALL FUNCTION 'SO_ATTACHMENT_DELETE' " |
| EXPORTING | ||
| OBJECT_ID | = lv_object_id | |
| ATTACH_ID | = lv_attach_id | |
| OWNER | = lv_owner | |
| PUT_IN_WASTEBASKET | = lv_put_in_wastebasket | |
| EXCEPTIONS | ||
| OBJECT_NOT_EXIST = 1 | ||
| OBJECT_NO_AUTHORIZATION = 2 | ||
| OPERATION_NO_AUTHORIZATION = 3 | ||
| OWNER_NOT_EXIST = 4 | ||
| SUBSTITUTE_NOT_ACTIVE = 5 | ||
| SUBSTITUTE_NOT_DEFINED = 6 | ||
| X_ERROR = 7 | ||
| COMMUNICATION_FAILURE = 8 | ||
| SYSTEM_FAILURE = 9 | ||
| . " SO_ATTACHMENT_DELETE | ||
ABAP code using 7.40 inline data declarations to call FM SO_ATTACHMENT_DELETE
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_owner). | ||||
| DATA(ld_owner) | = ' '. | |||
| "SELECT single FLAG FROM SONV INTO @DATA(ld_put_in_wastebasket). | ||||
| DATA(ld_put_in_wastebasket) | = 'X'. | |||
Search for further information about these or an SAP related objects