SAP COND_MNT_RECORD_PUT Function Module for Adds a new record to the maintenance session (create)

Search SAP Function Modules

COND_MNT_RECORD_PUT is a standard cond mnt record put SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Adds a new record to the maintenance session (create) 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 record put FM, simply by entering the name COND_MNT_RECORD_PUT 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_RECORD_PUT 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_RECORD_PUT'"Adds a new record to the maintenance session (create)
  EXPORTING
   IV_HANDLE =  "Handle for Maintenance Session
*  IV_ALLOW_OVERLAP = ABAP_TRUE "Allow Ovelaps?
   RECORD_DATA =  "Key and Data of a Condition Record

 IMPORTING
   EV_REC_ID =  "ID for a Condition Record
   EV_SUBRC =  "Result of Condition Maintenance
   ET_MESSAGES =  "Messages from Condition Maintenance

EXCEPTIONS
   CX_COND_MNT_SESSION = 1    CX_COND_MNT_RECORD = 2 

.

IMPORTING Parameters details for COND_MNT_RECORD_PUT

IV_HANDLE - Handle for Maintenance Session

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

IV_ALLOW_OVERLAP - Allow Ovelaps?

Data type: BOOLEAN
Default: ABAP_TRUE
Optional: No
Call by Reference: Yes

RECORD_DATA - Key and Data of a Condition Record

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

EXPORTING Parameters details for COND_MNT_RECORD_PUT

EV_REC_ID - ID for a Condition Record

Data type: COND_REC_ID
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)

CX_COND_MNT_RECORD - Exceptions During Processing

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

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

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