SAP IF_WM_GET_VARIANT_IDOCMON Function Module for NOTRANSL: Ermitteln von Selektionskriterien aus angegebener Selektionsvari

Search SAP Function Modules

IF_WM_GET_VARIANT_IDOCMON is a standard if wm get variant idocmon 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: Ermitteln von Selektionskriterien aus angegebener Selektionsvari 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 if wm get variant idocmon FM, simply by entering the name IF_WM_GET_VARIANT_IDOCMON into the relevant SAP transaction such as SE37 or SE38.

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

Function IF_WM_GET_VARIANT_IDOCMON 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 'IF_WM_GET_VARIANT_IDOCMON'"NOTRANSL: Ermitteln von Selektionskriterien aus angegebener Selektionsvari
  EXPORTING
   IV_VARIANT =  "Variant Name

 IMPORTING
   EV_RCVPRN =  "Partner number of receiver

TABLES
   ET_RG_MESTYP =  "Range Table for Message Categories
   ET_RG_STATUS =  "Range Table for Statuses
   ET_RG_DATUM =  "Range Table for Date
*  ET_RG_TIME =  "Range Table for Time

EXCEPTIONS
   VARIANT_NON_EXISTENT = 1 

.

IMPORTING Parameters details for IF_WM_GET_VARIANT_IDOCMON

IV_VARIANT - Variant Name

Data type: MAWM_FUNC_INTERFACE-VARIA
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for IF_WM_GET_VARIANT_IDOCMON

EV_RCVPRN - Partner number of receiver

Data type: EDIDC-RCVPRN
Optional: No
Call by Reference: Yes

TABLES Parameters details for IF_WM_GET_VARIANT_IDOCMON

ET_RG_MESTYP - Range Table for Message Categories

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

ET_RG_STATUS - Range Table for Statuses

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

ET_RG_DATUM - Range Table for Date

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

ET_RG_TIME - Range Table for Time

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

EXCEPTIONS details

VARIANT_NON_EXISTENT - Variant does not exist

Data type:
Optional: No
Call by Reference: Yes

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

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