SAP SO_OBJECT_STATUS_UPDATE Function Module for









SO_OBJECT_STATUS_UPDATE is a standard so object status 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 object status update FM, simply by entering the name SO_OBJECT_STATUS_UPDATE into the relevant SAP transaction such as SE37 or SE38.

Function Group: SOE2
Program Name: SAPLSOE2
Main Program: SAPLSOE2
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function SO_OBJECT_STATUS_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_OBJECT_STATUS_UPDATE'"
EXPORTING
* RECEIVE_INFO = "
* DOCUMENT_DATA = "
* OBJECT_ID = "ID of the original message
* MESSAGE_TYPE = 'M' "
* NODE = ' ' "
* JOBNAME = ' ' "
* JOBCOUNT = ' ' "
* NOTIFICATION = "

TABLES
* RECEIVERS = "Recipient (Office)
* RECIPIENT_ADDRS = "Recipient (SAPconnect)
* PACKING_LIST = "Descriptive list for transport tables
* OBJECT_HEADER = "Specific header entries
* CONTENTS_BIN = "Binary contents
* CONTENTS_TXT = "ASCII contents
* OBJECT_PARA = "SET/GET parameter of the main document
* OBJECT_PARB = "Processing parameter of the main document

EXCEPTIONS
ERR_SEND_PROC_NOT_FOUND = 1 ERR_ENQUEUE = 2 ERR_ORIG_NOT_FOUND = 3 ERR_REC_NOT_SPECIFIED = 4 ERR_STATUS_NOT_SET = 5 X_ERROR = 6
.



IMPORTING Parameters details for SO_OBJECT_STATUS_UPDATE

RECEIVE_INFO -

Data type: SXRECINFI1
Optional: Yes
Call by Reference: No ( called with pass by value option)

DOCUMENT_DATA -

Data type: SXDOCCHGI1
Optional: Yes
Call by Reference: No ( called with pass by value option)

OBJECT_ID - ID of the original message

Data type: SX_OBJ_ID
Optional: Yes
Call by Reference: No ( called with pass by value option)

MESSAGE_TYPE -

Data type: SX_MSGTYPE
Default: 'M'
Optional: Yes
Call by Reference: No ( called with pass by value option)

NODE -

Data type: SOES-NODE
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

JOBNAME -

Data type: SOES-JOBNAME
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

JOBCOUNT -

Data type: SOES-JOBCOUNT
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

NOTIFICATION -

Data type: CL_SEND_REQUEST_BCS
Optional: Yes
Call by Reference: Yes

TABLES Parameters details for SO_OBJECT_STATUS_UPDATE

RECEIVERS - Recipient (Office)

Data type: SXEXTRECI1
Optional: Yes
Call by Reference: No ( called with pass by value option)

RECIPIENT_ADDRS - Recipient (SAPconnect)

Data type: SX_RECIPIENT_TAB
Optional: Yes
Call by Reference: No ( called with pass by value option)

PACKING_LIST - Descriptive list for transport tables

Data type: SOPCKLSTI1
Optional: Yes
Call by Reference: No ( called with pass by value option)

OBJECT_HEADER - Specific header entries

Data type: SOLI
Optional: Yes
Call by Reference: No ( called with pass by value option)

CONTENTS_BIN - Binary contents

Data type: SOLI
Optional: Yes
Call by Reference: No ( called with pass by value option)

CONTENTS_TXT - ASCII contents

Data type: SOLI
Optional: Yes
Call by Reference: No ( called with pass by value option)

OBJECT_PARA - SET/GET parameter of the main document

Data type: SOPARAI1
Optional: Yes
Call by Reference: No ( called with pass by value option)

OBJECT_PARB - Processing parameter of the main document

Data type: SOPARBI1
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

ERR_SEND_PROC_NOT_FOUND - Send operation not found

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

ERR_ENQUEUE - Lock problem

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

ERR_ORIG_NOT_FOUND - Document sent originally not found

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

ERR_REC_NOT_SPECIFIED - Unknown recipient

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

ERR_STATUS_NOT_SET - No status set

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

X_ERROR - Unknown error / database inconsistency

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for SO_OBJECT_STATUS_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_receivers  TYPE STANDARD TABLE OF SXEXTRECI1, "   
lv_receive_info  TYPE SXRECINFI1, "   
lv_err_send_proc_not_found  TYPE SXRECINFI1, "   
lv_err_enqueue  TYPE SXRECINFI1, "   
lv_document_data  TYPE SXDOCCHGI1, "   
lt_recipient_addrs  TYPE STANDARD TABLE OF SX_RECIPIENT_TAB, "   
lv_object_id  TYPE SX_OBJ_ID, "   
lt_packing_list  TYPE STANDARD TABLE OF SOPCKLSTI1, "   
lv_err_orig_not_found  TYPE SOPCKLSTI1, "   
lv_message_type  TYPE SX_MSGTYPE, "   'M'
lt_object_header  TYPE STANDARD TABLE OF SOLI, "   
lv_err_rec_not_specified  TYPE SOLI, "   
lv_node  TYPE SOES-NODE, "   SPACE
lt_contents_bin  TYPE STANDARD TABLE OF SOLI, "   
lv_err_status_not_set  TYPE SOLI, "   
lv_jobname  TYPE SOES-JOBNAME, "   SPACE
lv_x_error  TYPE SOES, "   
lt_contents_txt  TYPE STANDARD TABLE OF SOLI, "   
lv_jobcount  TYPE SOES-JOBCOUNT, "   SPACE
lt_object_para  TYPE STANDARD TABLE OF SOPARAI1, "   
lt_object_parb  TYPE STANDARD TABLE OF SOPARBI1, "   
lv_notification  TYPE CL_SEND_REQUEST_BCS. "   

  CALL FUNCTION 'SO_OBJECT_STATUS_UPDATE'  "
    EXPORTING
         RECEIVE_INFO = lv_receive_info
         DOCUMENT_DATA = lv_document_data
         OBJECT_ID = lv_object_id
         MESSAGE_TYPE = lv_message_type
         NODE = lv_node
         JOBNAME = lv_jobname
         JOBCOUNT = lv_jobcount
         NOTIFICATION = lv_notification
    TABLES
         RECEIVERS = lt_receivers
         RECIPIENT_ADDRS = lt_recipient_addrs
         PACKING_LIST = lt_packing_list
         OBJECT_HEADER = lt_object_header
         CONTENTS_BIN = lt_contents_bin
         CONTENTS_TXT = lt_contents_txt
         OBJECT_PARA = lt_object_para
         OBJECT_PARB = lt_object_parb
    EXCEPTIONS
        ERR_SEND_PROC_NOT_FOUND = 1
        ERR_ENQUEUE = 2
        ERR_ORIG_NOT_FOUND = 3
        ERR_REC_NOT_SPECIFIED = 4
        ERR_STATUS_NOT_SET = 5
        X_ERROR = 6
. " SO_OBJECT_STATUS_UPDATE




ABAP code using 7.40 inline data declarations to call FM SO_OBJECT_STATUS_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_message_type) = 'M'.
 
 
 
"SELECT single NODE FROM SOES INTO @DATA(ld_node).
DATA(ld_node) = ' '.
 
 
 
"SELECT single JOBNAME FROM SOES INTO @DATA(ld_jobname).
DATA(ld_jobname) = ' '.
 
 
 
"SELECT single JOBCOUNT FROM SOES INTO @DATA(ld_jobcount).
DATA(ld_jobcount) = ' '.
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!