SAP COND_MNT_START Function Module for Start Maintenance (Selection)









COND_MNT_START is a standard cond mnt start SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Start Maintenance (Selection) 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 cond mnt start FM, simply by entering the name COND_MNT_START into the relevant SAP transaction such as SE37 or SE38.

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



Function COND_MNT_START 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 'COND_MNT_START'"Start Maintenance (Selection)
EXPORTING
IV_HANDLE = "Handle for Maintenance Session
* IV_SELDATE = SY-DATLO "Valid On
* IV_SELKNUMH = "Condition Record Number
* IV_VAKEY = "Variable key 100 bytes
* IT_SELECTION = "Selection Range for Reading Condition Records

IMPORTING
EV_RECNO = "Number of Selected Condition Records
ET_RECORD_KEYS = "Table with IDs and Keys of Condition Records
EV_SUBRC = "Result of Condition Maintenance
ET_MESSAGES = "Messages from Condition Maintenance

EXCEPTIONS
CX_COND_MNT_SESSION = 1
.



IMPORTING Parameters details for COND_MNT_START

IV_HANDLE - Handle for Maintenance Session

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

IV_SELDATE - Valid On

Data type: DATAM
Default: SY-DATLO
Optional: No
Call by Reference: Yes

IV_SELKNUMH - Condition Record Number

Data type: VAKE-KNUMH
Optional: Yes
Call by Reference: Yes

IV_VAKEY - Variable key 100 bytes

Data type: VAKE-VAKEY
Optional: Yes
Call by Reference: Yes

IT_SELECTION - Selection Range for Reading Condition Records

Data type: CL_COND_TAB_SEL=>COND_RNGS_T
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for COND_MNT_START

EV_RECNO - Number of Selected Condition Records

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

ET_RECORD_KEYS - Table with IDs and Keys of Condition Records

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

EV_SUBRC - Result of Condition Maintenance

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

ET_MESSAGES - Messages from Condition Maintenance

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

EXCEPTIONS details

CX_COND_MNT_SESSION - Exceptions from Maintenance Session

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

Copy and paste ABAP code example for COND_MNT_START 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_ev_recno  TYPE SYLOOPC, "   
lv_iv_handle  TYPE COND_MNT_HANDLE, "   
lv_cx_cond_mnt_session  TYPE COND_MNT_HANDLE, "   
lv_iv_seldate  TYPE DATAM, "   SY-DATLO
lv_et_record_keys  TYPE COND_MNT_RECORD_KEY_T, "   
lv_ev_subrc  TYPE COND_MNT_RESULT, "   
lv_iv_selknumh  TYPE VAKE-KNUMH, "   
lv_iv_vakey  TYPE VAKE-VAKEY, "   
lv_et_messages  TYPE COND_MNT_MESSAGE_T, "   
lv_it_selection  TYPE CL_COND_TAB_SEL=>COND_RNGS_T. "   

  CALL FUNCTION 'COND_MNT_START'  "Start Maintenance (Selection)
    EXPORTING
         IV_HANDLE = lv_iv_handle
         IV_SELDATE = lv_iv_seldate
         IV_SELKNUMH = lv_iv_selknumh
         IV_VAKEY = lv_iv_vakey
         IT_SELECTION = lv_it_selection
    IMPORTING
         EV_RECNO = lv_ev_recno
         ET_RECORD_KEYS = lv_et_record_keys
         EV_SUBRC = lv_ev_subrc
         ET_MESSAGES = lv_et_messages
    EXCEPTIONS
        CX_COND_MNT_SESSION = 1
. " COND_MNT_START




ABAP code using 7.40 inline data declarations to call FM COND_MNT_START

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_iv_seldate) = SY-DATLO.
 
 
 
"SELECT single KNUMH FROM VAKE INTO @DATA(ld_iv_selknumh).
 
"SELECT single VAKEY FROM VAKE INTO @DATA(ld_iv_vakey).
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!