SAP SO_ATTACHMENT_UPDATE Function Module for
SO_ATTACHMENT_UPDATE is a standard so attachment update 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 update FM, simply by entering the name SO_ATTACHMENT_UPDATE 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): Normal Function Module
Update:

Function SO_ATTACHMENT_UPDATE 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_UPDATE'".
EXPORTING
OBJECT_ID = "ID of the object
ATTACH_ID = "Forwarder
* OBJECT_HD_CHANGE = ' ' "SAPoffice header data (modifiable)
* OBJECT_REAPPEAR = ' ' "
* OWNER = ' ' "Owner of object
IMPORTING
OBJECT_HD_DISPLAY = "SAPoffice header data (can be displayed)
TABLES
OBJCONT = "Object contents
OBJHEAD = "Object-specific header
EXCEPTIONS
ACTIVE_USER_NOT_EXIST = 1 OBJECT_NOT_EXIST = 2 OBJECT_NO_AUTHORIZATION = 3 OPERATION_NO_AUTHORIZATION = 4 OWNER_NOT_EXIST = 5 PARAMETER_ERROR = 6 SUBSTITUTE_NOT_ACTIVE = 7 SUBSTITUTE_NOT_DEFINED = 8 X_ERROR = 9
IMPORTING Parameters details for SO_ATTACHMENT_UPDATE
OBJECT_ID - ID of the object
Data type: SOODKOptional: No
Call by Reference: No ( called with pass by value option)
ATTACH_ID - Forwarder
Data type: SOODKOptional: No
Call by Reference: No ( called with pass by value option)
OBJECT_HD_CHANGE - SAPoffice header data (modifiable)
Data type: SOOD1Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
OBJECT_REAPPEAR -
Data type: SONV-FLAGDefault: SPACE
Optional: Yes
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)
EXPORTING Parameters details for SO_ATTACHMENT_UPDATE
OBJECT_HD_DISPLAY - SAPoffice header data (can be displayed)
Data type: SOOD2Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for SO_ATTACHMENT_UPDATE
OBJCONT - Object contents
Data type: SOLIOptional: No
Call by Reference: No ( called with pass by value option)
OBJHEAD - Object-specific header
Data type: SOLIOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ACTIVE_USER_NOT_EXIST - Active user is not a SAPoffice user
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
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 the 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 - User does not exist
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
PARAMETER_ERROR - Combination of the parameter values not allowed
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SUBSTITUTE_NOT_ACTIVE - Substitute not active
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SUBSTITUTE_NOT_DEFINED - 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)
Copy and paste ABAP code example for SO_ATTACHMENT_UPDATE 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_objcont | TYPE STANDARD TABLE OF SOLI, " | |||
| lv_object_id | TYPE SOODK, " | |||
| lv_object_hd_display | TYPE SOOD2, " | |||
| lv_active_user_not_exist | TYPE SOOD2, " | |||
| lt_objhead | TYPE STANDARD TABLE OF SOLI, " | |||
| lv_attach_id | TYPE SOODK, " | |||
| lv_object_not_exist | TYPE SOODK, " | |||
| lv_object_hd_change | TYPE SOOD1, " SPACE | |||
| lv_object_no_authorization | TYPE SOOD1, " | |||
| lv_object_reappear | TYPE SONV-FLAG, " SPACE | |||
| lv_operation_no_authorization | TYPE SONV, " | |||
| lv_owner | TYPE SOUD-USRNAM, " SPACE | |||
| lv_owner_not_exist | TYPE SOUD, " | |||
| lv_parameter_error | TYPE SOUD, " | |||
| lv_substitute_not_active | TYPE SOUD, " | |||
| lv_substitute_not_defined | TYPE SOUD, " | |||
| lv_x_error | TYPE SOUD. " |
|   CALL FUNCTION 'SO_ATTACHMENT_UPDATE' " |
| EXPORTING | ||
| OBJECT_ID | = lv_object_id | |
| ATTACH_ID | = lv_attach_id | |
| OBJECT_HD_CHANGE | = lv_object_hd_change | |
| OBJECT_REAPPEAR | = lv_object_reappear | |
| OWNER | = lv_owner | |
| IMPORTING | ||
| OBJECT_HD_DISPLAY | = lv_object_hd_display | |
| TABLES | ||
| OBJCONT | = lt_objcont | |
| OBJHEAD | = lt_objhead | |
| EXCEPTIONS | ||
| ACTIVE_USER_NOT_EXIST = 1 | ||
| OBJECT_NOT_EXIST = 2 | ||
| OBJECT_NO_AUTHORIZATION = 3 | ||
| OPERATION_NO_AUTHORIZATION = 4 | ||
| OWNER_NOT_EXIST = 5 | ||
| PARAMETER_ERROR = 6 | ||
| SUBSTITUTE_NOT_ACTIVE = 7 | ||
| SUBSTITUTE_NOT_DEFINED = 8 | ||
| X_ERROR = 9 | ||
| . " SO_ATTACHMENT_UPDATE | ||
ABAP code using 7.40 inline data declarations to call FM SO_ATTACHMENT_UPDATE
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_object_hd_change) | = ' '. | |||
| "SELECT single FLAG FROM SONV INTO @DATA(ld_object_reappear). | ||||
| DATA(ld_object_reappear) | = ' '. | |||
| "SELECT single USRNAM FROM SOUD INTO @DATA(ld_owner). | ||||
| DATA(ld_owner) | = ' '. | |||
Search for further information about these or an SAP related objects