SAP MM_PROPOSE_DOC_TYPE Function Module for NOTRANSL: Belegart vorschlagen
MM_PROPOSE_DOC_TYPE is a standard mm propose doc type SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Belegart vorschlagen 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 mm propose doc type FM, simply by entering the name MM_PROPOSE_DOC_TYPE into the relevant SAP transaction such as SE37 or SE38.
Function Group: ME59
Program Name: SAPLME59
Main Program: SAPLME59
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MM_PROPOSE_DOC_TYPE 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 'MM_PROPOSE_DOC_TYPE'"NOTRANSL: Belegart vorschlagen.
EXPORTING
IM_EBAN = "Purchase Requisition
IM_GPSTYP = "Boolean type
* IM_NO_EXIT = "Boolean Type
IMPORTING
EX_BSART = "Order Type
EX_PSTYP = "Item Category in Purchasing Document
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLME59_001 Grouping of Requisitions for Automatic Generation of Purchase Orders
IMPORTING Parameters details for MM_PROPOSE_DOC_TYPE
IM_EBAN - Purchase Requisition
Data type: EBANOptional: No
Call by Reference: Yes
IM_GPSTYP - Boolean type
Data type: MMPUR_BOOLOptional: No
Call by Reference: Yes
IM_NO_EXIT - Boolean Type
Data type: MMPUR_BOOLOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for MM_PROPOSE_DOC_TYPE
EX_BSART - Order Type
Data type: BSARTOptional: No
Call by Reference: Yes
EX_PSTYP - Item Category in Purchasing Document
Data type: PSTYPOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for MM_PROPOSE_DOC_TYPE 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_im_eban | TYPE EBAN, " | |||
| lv_ex_bsart | TYPE BSART, " | |||
| lv_ex_pstyp | TYPE PSTYP, " | |||
| lv_im_gpstyp | TYPE MMPUR_BOOL, " | |||
| lv_im_no_exit | TYPE MMPUR_BOOL. " |
|   CALL FUNCTION 'MM_PROPOSE_DOC_TYPE' "NOTRANSL: Belegart vorschlagen |
| EXPORTING | ||
| IM_EBAN | = lv_im_eban | |
| IM_GPSTYP | = lv_im_gpstyp | |
| IM_NO_EXIT | = lv_im_no_exit | |
| IMPORTING | ||
| EX_BSART | = lv_ex_bsart | |
| EX_PSTYP | = lv_ex_pstyp | |
| . " MM_PROPOSE_DOC_TYPE | ||
ABAP code using 7.40 inline data declarations to call FM MM_PROPOSE_DOC_TYPE
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