SAP MASS_VENDOR_SAVE_CHANGE Function Module for Save to cluster table MASS_JOB_ERROR

Search SAP Function Modules

MASS_VENDOR_SAVE_CHANGE is a standard mass vendor save 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 Save to cluster table MASS_JOB_ERROR 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 vendor save change FM, simply by entering the name MASS_VENDOR_SAVE_CHANGE into the relevant SAP transaction such as SE37 or SE38.

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

Function MASS_VENDOR_SAVE_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_VENDOR_SAVE_CHANGE'"Save to cluster table MASS_JOB_ERROR
  EXPORTING
*  I_USER =  "R/3 System, user logon name
*  I_DATE =  "Date and time, current (application server) date
*  I_TIME =  "Dat and time, current application server time
*  I_PGRMID =  "ABAP program, current main program
   I_GOOD_LINES =  "
*  I_OLD_MCKEY = ' ' "R/2 table

TABLES
   T_RECORDS_IN =  "Vendor Master Record: Purchasing Data
   T_ERR_MSG_IN =  "Application Log: APPL_LOG_WRITE_MESSAGES interface
   I_STYLE_I =  "to conserve style & color in mass maintenance screen

EXCEPTIONS
   ERROR_IN_SAVE_DATA = 1    ERROR_IN_SAVE_ERRORS = 2    ERROR_IN_NUMBER_GENERATE = 3 

.

IMPORTING Parameters details for MASS_VENDOR_SAVE_CHANGE

I_USER - R/3 System, user logon name

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

I_DATE - Date and time, current (application server) date

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

I_TIME - Dat and time, current application server time

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

I_PGRMID - ABAP program, current main program

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

I_GOOD_LINES -

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

I_OLD_MCKEY - R/2 table

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

TABLES Parameters details for MASS_VENDOR_SAVE_CHANGE

T_RECORDS_IN - Vendor Master Record: Purchasing Data

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

T_ERR_MSG_IN - Application Log: APPL_LOG_WRITE_MESSAGES interface

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

I_STYLE_I - to conserve style & color in mass maintenance screen

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

EXCEPTIONS details

ERROR_IN_SAVE_DATA -

Data type:
Optional: No
Call by Reference: Yes

ERROR_IN_SAVE_ERRORS -

Data type:
Optional: No
Call by Reference: Yes

ERROR_IN_NUMBER_GENERATE -

Data type:
Optional: No
Call by Reference: Yes

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

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