SAP SO_OBJECT_MIME_GET Function Module for

Search SAP Function Modules

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

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

Function SO_OBJECT_MIME_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_MIME_GET'"
  EXPORTING
*  OBJECT_ID =  "SAPconnect: SAPoffice object ID
*  MESSAGE_TYPE = 'M' "
   SENDER =  "
*  SENDER_TYPE = 'INT' "

 IMPORTING
   CONTENT_MIME =  "BCOM: MIME Data Stream
   RECEIVE_INFO =  "SAPoffice: Info structure for objects to be received extern.

TABLES
   RECIPIENT_ADDRS =  "

EXCEPTIONS
   ERR_NO_RECIPIENT = 1    ERR_NO_MIME = 2 

.

IMPORTING Parameters details for SO_OBJECT_MIME_GET

OBJECT_ID - SAPconnect: SAPoffice object ID

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

MESSAGE_TYPE -

Data type: SX_MSGTYPE
Default: 'M'
Optional: Yes
Call by Reference: Yes

SENDER -

Data type: SX_ADDRESS
Optional: No
Call by Reference: Yes

SENDER_TYPE -

Data type: SX_ADDR_TYPE
Default: 'INT'
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for SO_OBJECT_MIME_GET

CONTENT_MIME - BCOM: MIME Data Stream

Data type: MIME_DATA
Optional: No
Call by Reference: Yes

RECEIVE_INFO - SAPoffice: Info structure for objects to be received extern.

Data type: SXRECINFI1
Optional: No
Call by Reference: Yes

TABLES Parameters details for SO_OBJECT_MIME_GET

RECIPIENT_ADDRS -

Data type: SX_RECIPIENT_TAB
Optional: No
Call by Reference: Yes

EXCEPTIONS details

ERR_NO_RECIPIENT -

Data type:
Optional: No
Call by Reference: Yes

ERR_NO_MIME -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for SO_OBJECT_MIME_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.

ABAP code using 7.40 inline data declarations to call FM SO_OBJECT_MIME_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.

Search for further information about these or an SAP related objects