SAP SO_OBJECT_ID_FOR_SEND_GET Function Module for









SO_OBJECT_ID_FOR_SEND_GET is a standard so object id for send get 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 id for send get FM, simply by entering the name SO_OBJECT_ID_FOR_SEND_GET 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_ID_FOR_SEND_GET 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_ID_FOR_SEND_GET'"
  EXPORTING
*  OBJECT_ID = ' ' "Selected object (reserved)
*  ADDR_TYPE = ' ' "Address type to be selected

 IMPORTING
   OBJECT_ID =  "Selected object (reserved)
   MESSAGE_TYPE =  "Object type (S for status, M for message)
   SENDER =  "Sender as SAP name

TABLES
   RECIPIENT_ADDRS =  "Recipient of the object

EXCEPTIONS
   WNG_NO_OBJECT_WAITS = 1    ERR_NO_RECIPIENTS = 2    X_ERROR = 3
.



IMPORTING Parameters details for SO_OBJECT_ID_FOR_SEND_GET

OBJECT_ID - Selected object (reserved)

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

ADDR_TYPE - Address type to be selected

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

EXPORTING Parameters details for SO_OBJECT_ID_FOR_SEND_GET

OBJECT_ID - Selected object (reserved)

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

MESSAGE_TYPE - Object type (S for status, M for message)

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

SENDER - Sender as SAP name

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

TABLES Parameters details for SO_OBJECT_ID_FOR_SEND_GET

RECIPIENT_ADDRS - Recipient of the object

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

EXCEPTIONS details

WNG_NO_OBJECT_WAITS - No object (of this type) to be sent

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

ERR_NO_RECIPIENTS - Mail or status had no recipients

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

X_ERROR - Unknown error or data inconsistency

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

Copy and paste ABAP code example for SO_OBJECT_ID_FOR_SEND_GET 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 SX_OBJ_ID, "   
lv_object_id  TYPE SX_OBJ_ID, "   SPACE
lt_recipient_addrs  TYPE STANDARD TABLE OF SX_RECIPIENT_TAB, "   
lv_wng_no_object_waits  TYPE SX_RECIPIENT_TAB, "   
lv_addr_type  TYPE SX_ADDR_TYPE, "   SPACE
lv_message_type  TYPE SX_MSGTYPE, "   
lv_err_no_recipients  TYPE SX_MSGTYPE, "   
lv_sender  TYPE SX_ADDRESS, "   
lv_x_error  TYPE SX_ADDRESS. "   

  CALL FUNCTION 'SO_OBJECT_ID_FOR_SEND_GET'  "
    EXPORTING
         OBJECT_ID = lv_object_id
         ADDR_TYPE = lv_addr_type
    IMPORTING
         OBJECT_ID = lv_object_id
         MESSAGE_TYPE = lv_message_type
         SENDER = lv_sender
    TABLES
         RECIPIENT_ADDRS = lt_recipient_addrs
    EXCEPTIONS
        WNG_NO_OBJECT_WAITS = 1
        ERR_NO_RECIPIENTS = 2
        X_ERROR = 3
. " SO_OBJECT_ID_FOR_SEND_GET




ABAP code using 7.40 inline data declarations to call FM SO_OBJECT_ID_FOR_SEND_GET

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_id) = ' '.
 
 
 
DATA(ld_addr_type) = ' '.
 
 
 
 
 


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!