SAP MM_COND_SINGLE_CHANGE_CHECK Function Module for NOTRANSL: Prüfen, ob aktuelle Konditionsänderung (ein Satz) zu Beleganpass

Search SAP Function Modules

MM_COND_SINGLE_CHANGE_CHECK is a standard mm cond single change 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 NOTRANSL: Prüfen, ob aktuelle Konditionsänderung (ein Satz) zu Beleganpass 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 cond single change check FM, simply by entering the name MM_COND_SINGLE_CHANGE_CHECK into the relevant SAP transaction such as SE37 or SE38.

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

Function MM_COND_SINGLE_CHANGE_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 'MM_COND_SINGLE_CHANGE_CHECK'"NOTRANSL: Prüfen, ob aktuelle Konditionsänderung (ein Satz) zu Beleganpass
  EXPORTING
   I_VARIABLE_KEY =  "Variable key
*  I_CONDITION_HEADER =  "
*  I_DOCUMENT_VALIDITY =  "
*  I_PRICING_VALIDITY =  "
*  I_ALV = 'X' "General Indicator

TABLES
*  T_CONDITION_RECORD =  "
*  T_ERROR_MESSAGES =  "Notifications
*  T_VAKE_FOR_BLTYP =  "

EXCEPTIONS
   T6I1_SELECT_ERROR = 1    INDEX_DATA_NOT_FOUND = 2    DATALOST_ERROR = 3    DOCUMENT_UPDATE_PREPARE = 4    OTHER_MESSAGES = 5 

.

IMPORTING Parameters details for MM_COND_SINGLE_CHANGE_CHECK

I_VARIABLE_KEY - Variable key

Data type: VAKE
Optional: No
Call by Reference: No ( called with pass by value option)

I_CONDITION_HEADER -

Data type: KONH
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_DOCUMENT_VALIDITY -

Data type: WIN1_DATS
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_PRICING_VALIDITY -

Data type: WIN1_DATS
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_ALV - General Indicator

Data type: FLAG
Default: 'X'
Optional: Yes
Call by Reference: Yes

TABLES Parameters details for MM_COND_SINGLE_CHANGE_CHECK

T_CONDITION_RECORD -

Data type: KONPDB
Optional: Yes
Call by Reference: No ( called with pass by value option)

T_ERROR_MESSAGES - Notifications

Data type: BELIND_ERR
Optional: Yes
Call by Reference: No ( called with pass by value option)

T_VAKE_FOR_BLTYP -

Data type: WIND_VAKE_FOR_BLTYP_TAB
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

T6I1_SELECT_ERROR -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

INDEX_DATA_NOT_FOUND -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

DATALOST_ERROR -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

DOCUMENT_UPDATE_PREPARE -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

OTHER_MESSAGES -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

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

ABAP code using 7.40 inline data declarations to call FM MM_COND_SINGLE_CHANGE_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.

Search for further information about these or an SAP related objects