SAP MS_CONTRACT_CONDITION_EXIST Function Module for Prüf ob zu einer Leistung bereits ein Konditionssatz existiert ( Kontrakt)

Search SAP Function Modules

MS_CONTRACT_CONDITION_EXIST is a standard ms contract condition exist SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Prüf ob zu einer Leistung bereits ein Konditionssatz existiert ( Kontrakt) 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 ms contract condition exist FM, simply by entering the name MS_CONTRACT_CONDITION_EXIST into the relevant SAP transaction such as SE37 or SE38.

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

Function MS_CONTRACT_CONDITION_EXIST 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 'MS_CONTRACT_CONDITION_EXIST'"Prüf ob zu einer Leistung bereits ein Konditionssatz existiert ( Kontrakt)
  EXPORTING
   I_KAPPL =  "
   I_PACKNO =  "
   I_INTROW =  "
*  I_WERKS =  "
*  I_KSCHL =  "
*  I_DATAB =  "
*  I_DATBIS =  "

EXCEPTIONS
   NOTHING_FOUND = 1 

.

IMPORTING Parameters details for MS_CONTRACT_CONDITION_EXIST

I_KAPPL -

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

I_PACKNO -

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

I_INTROW -

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

I_WERKS -

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

I_KSCHL -

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

I_DATAB -

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

I_DATBIS -

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

EXCEPTIONS details

NOTHING_FOUND -

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

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

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