SAP MSAM_MO_PARTNER_CHECK Function Module for MSAM: Partner Check
MSAM_MO_PARTNER_CHECK is a standard msam mo partner check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for MSAM: Partner Check 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 partner check FM, simply by entering the name MSAM_MO_PARTNER_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: MSAM_MO_PARTNER
Program Name: SAPLMSAM_MO_PARTNER
Main Program: SAPLMSAM_MO_PARTNER
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MSAM_MO_PARTNER_CHECK 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_PARTNER_CHECK'"MSAM: Partner Check.
EXPORTING
I_PARGR = "
* I_PARTNER_TPA_KEY = '' "
* I_NO_POPUP = "General Flag
IT_PARTNER = "Table for Partner Keys
CHANGING
CT_RETURN = "Return parameter table
EXCEPTIONS
PARTNER_NOT_VALID = 1
IMPORTING Parameters details for MSAM_MO_PARTNER_CHECK
I_PARGR -
Data type: PARGROptional: No
Call by Reference: Yes
I_PARTNER_TPA_KEY -
Data type: FLAGDefault: ''
Optional: Yes
Call by Reference: Yes
I_NO_POPUP - General Flag
Data type: FLAGOptional: Yes
Call by Reference: Yes
IT_PARTNER - Table for Partner Keys
Data type: MSAM10_PARTNER_KEY_TOptional: No
Call by Reference: Yes
CHANGING Parameters details for MSAM_MO_PARTNER_CHECK
CT_RETURN - Return parameter table
Data type: BAPIRET2_TOptional: No
Call by Reference: Yes
EXCEPTIONS details
PARTNER_NOT_VALID -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for MSAM_MO_PARTNER_CHECK 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_i_pargr | TYPE PARGR, " | |||
| lv_ct_return | TYPE BAPIRET2_T, " | |||
| lv_partner_not_valid | TYPE BAPIRET2_T, " | |||
| lv_i_partner_tpa_key | TYPE FLAG, " '' | |||
| lv_i_no_popup | TYPE FLAG, " | |||
| lv_it_partner | TYPE MSAM10_PARTNER_KEY_T. " |
|   CALL FUNCTION 'MSAM_MO_PARTNER_CHECK' "MSAM: Partner Check |
| EXPORTING | ||
| I_PARGR | = lv_i_pargr | |
| I_PARTNER_TPA_KEY | = lv_i_partner_tpa_key | |
| I_NO_POPUP | = lv_i_no_popup | |
| IT_PARTNER | = lv_it_partner | |
| CHANGING | ||
| CT_RETURN | = lv_ct_return | |
| EXCEPTIONS | ||
| PARTNER_NOT_VALID = 1 | ||
| . " MSAM_MO_PARTNER_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM MSAM_MO_PARTNER_CHECK
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_i_partner_tpa_key) | = ''. | |||
Search for further information about these or an SAP related objects