SAP MSAM_MO_DETERMIN_OBJ_QUE Function Module for Function module to determine Object queue name
MSAM_MO_DETERMIN_OBJ_QUE is a standard msam mo determin obj que SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Function module to determine Object queue name processing and below is the pattern details for this FM, 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 msam mo determin obj que FM, simply by entering the name MSAM_MO_DETERMIN_OBJ_QUE into the relevant SAP transaction such as SE37 or SE38.
Function Group: MSAM_MO_TOOLS
Program Name: SAPLMSAM_MO_TOOLS
Main Program: SAPLMSAM_MO_TOOLS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MSAM_MO_DETERMIN_OBJ_QUE 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 'MSAM_MO_DETERMIN_OBJ_QUE'"Function module to determine Object queue name.
EXPORTING
OBJECT_TYPE = "Character 100
IMPORTING
OBJECT_NO = "Character 100
IMPORTING Parameters details for MSAM_MO_DETERMIN_OBJ_QUE
OBJECT_TYPE - Character 100
Data type: CHAR100Optional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for MSAM_MO_DETERMIN_OBJ_QUE
OBJECT_NO - Character 100
Data type: CHAR100Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for MSAM_MO_DETERMIN_OBJ_QUE 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_no | TYPE CHAR100, " | |||
| lv_object_type | TYPE CHAR100. " |
|   CALL FUNCTION 'MSAM_MO_DETERMIN_OBJ_QUE' "Function module to determine Object queue name |
| EXPORTING | ||
| OBJECT_TYPE | = lv_object_type | |
| IMPORTING | ||
| OBJECT_NO | = lv_object_no | |
| . " MSAM_MO_DETERMIN_OBJ_QUE | ||
ABAP code using 7.40 inline data declarations to call FM MSAM_MO_DETERMIN_OBJ_QUE
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