SAP MASS_CUSTOMERCONTRACT_CHANGE Function Module for Sichern von Kundenkontrakten
MASS_CUSTOMERCONTRACT_CHANGE is a standard mass customercontract change SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Sichern von Kundenkontrakten 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 mass customercontract change FM, simply by entering the name MASS_CUSTOMERCONTRACT_CHANGE into the relevant SAP transaction such as SE37 or SE38.
Function Group: MASS_SD_SAVE
Program Name: SAPLMASS_SD_SAVE
Main Program: SAPLMASS_SD_SAVE
Appliation area: V
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MASS_CUSTOMERCONTRACT_CHANGE 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 'MASS_CUSTOMERCONTRACT_CHANGE'"Sichern von Kundenkontrakten.
EXPORTING
SELDATA = "Table with Change Infos (Mass Maintenance)
TESTMODE = "
IMPORTING
MSG = "
TABLES
* SMASSCONTHEAD_S = "Header Data Customer Contract
* SMASSCONTVBAP = "Generated Table for View
* SMASSCONTPOSVBKD = "Generated Table for View
IMPORTING Parameters details for MASS_CUSTOMERCONTRACT_CHANGE
SELDATA - Table with Change Infos (Mass Maintenance)
Data type: MASS_TABDATAOptional: No
Call by Reference: No ( called with pass by value option)
TESTMODE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for MASS_CUSTOMERCONTRACT_CHANGE
MSG -
Data type: MASS_MSGSOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for MASS_CUSTOMERCONTRACT_CHANGE
SMASSCONTHEAD_S - Header Data Customer Contract
Data type: MASSCONTHEAD_SOptional: Yes
Call by Reference: Yes
SMASSCONTVBAP - Generated Table for View
Data type: MASSCONTVBAPOptional: Yes
Call by Reference: Yes
SMASSCONTPOSVBKD - Generated Table for View
Data type: MASSCONTPOSVBKDOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for MASS_CUSTOMERCONTRACT_CHANGE 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_msg | TYPE MASS_MSGS, " | |||
| lv_seldata | TYPE MASS_TABDATA, " | |||
| lt_smassconthead_s | TYPE STANDARD TABLE OF MASSCONTHEAD_S, " | |||
| lv_testmode | TYPE MASSCONTHEAD_S, " | |||
| lt_smasscontvbap | TYPE STANDARD TABLE OF MASSCONTVBAP, " | |||
| lt_smasscontposvbkd | TYPE STANDARD TABLE OF MASSCONTPOSVBKD. " |
|   CALL FUNCTION 'MASS_CUSTOMERCONTRACT_CHANGE' "Sichern von Kundenkontrakten |
| EXPORTING | ||
| SELDATA | = lv_seldata | |
| TESTMODE | = lv_testmode | |
| IMPORTING | ||
| MSG | = lv_msg | |
| TABLES | ||
| SMASSCONTHEAD_S | = lt_smassconthead_s | |
| SMASSCONTVBAP | = lt_smasscontvbap | |
| SMASSCONTPOSVBKD | = lt_smasscontposvbkd | |
| . " MASS_CUSTOMERCONTRACT_CHANGE | ||
ABAP code using 7.40 inline data declarations to call FM MASS_CUSTOMERCONTRACT_CHANGE
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