SAP SBCOMS_SOOD_FOR_DOCUMENT_GET Function Module for
SBCOMS_SOOD_FOR_DOCUMENT_GET is a standard sbcoms sood for document 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 sbcoms sood for document get FM, simply by entering the name SBCOMS_SOOD_FOR_DOCUMENT_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: SBCOMSUT
Program Name: SAPLSBCOMSUT
Main Program: SAPLSBCOMSUT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SBCOMS_SOOD_FOR_DOCUMENT_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 'SBCOMS_SOOD_FOR_DOCUMENT_GET'".
EXPORTING
I_DOCUMENT = "
* I_OWNER = "
* I_LANGUAGE = "
IMPORTING
SOOD = "
EXCEPTIONS
X_ERROR = 1
IMPORTING Parameters details for SBCOMS_SOOD_FOR_DOCUMENT_GET
I_DOCUMENT -
Data type: IF_DOCUMENT_BCSOptional: No
Call by Reference: Yes
I_OWNER -
Data type: IF_SENDER_BCSOptional: Yes
Call by Reference: Yes
I_LANGUAGE -
Data type: SOOD-OBJLAOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for SBCOMS_SOOD_FOR_DOCUMENT_GET
SOOD -
Data type: SOODOptional: No
Call by Reference: Yes
EXCEPTIONS details
X_ERROR -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for SBCOMS_SOOD_FOR_DOCUMENT_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_sood | TYPE SOOD, " | |||
| lv_x_error | TYPE SOOD, " | |||
| lv_i_document | TYPE IF_DOCUMENT_BCS, " | |||
| lv_i_owner | TYPE IF_SENDER_BCS, " | |||
| lv_i_language | TYPE SOOD-OBJLA. " |
|   CALL FUNCTION 'SBCOMS_SOOD_FOR_DOCUMENT_GET' " |
| EXPORTING | ||
| I_DOCUMENT | = lv_i_document | |
| I_OWNER | = lv_i_owner | |
| I_LANGUAGE | = lv_i_language | |
| IMPORTING | ||
| SOOD | = lv_sood | |
| EXCEPTIONS | ||
| X_ERROR = 1 | ||
| . " SBCOMS_SOOD_FOR_DOCUMENT_GET | ||
ABAP code using 7.40 inline data declarations to call FM SBCOMS_SOOD_FOR_DOCUMENT_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.| "SELECT single OBJLA FROM SOOD INTO @DATA(ld_i_language). | ||||
Search for further information about these or an SAP related objects