SAP MASS_VENDOR_SAVE_PARALLEL Function Module for Save in parallel

Search SAP Function Modules

MASS_VENDOR_SAVE_PARALLEL is a standard mass vendor save parallel 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 in parallel 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 parallel FM, simply by entering the name MASS_VENDOR_SAVE_PARALLEL 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): Remote-Enabled
Update:

Function MASS_VENDOR_SAVE_PARALLEL 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_PARALLEL'"Save in parallel
  EXPORTING
   P_MAX_SIZE =  "
   P_MAX_NBPROC =  "
   P_OLD_MCKEY =  "R/2 table

TABLES
*  P_NEW_LFM2 =  "mass maintenance structure for MARC data
*  P_OLD_LFM2 =  "flat structure for mas maintenance style info (for RFC use)
*  P_INV_LFM2 =  "mass maintenance structure for MARC data
*  P_ALL_GT_STYLE =  "flat structure for mas maintenance style info (for RFC use)
*  ERROR_MSG =  "Meldungsbezogene Einträge für Application Log

.

IMPORTING Parameters details for MASS_VENDOR_SAVE_PARALLEL

P_MAX_SIZE -

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

P_MAX_NBPROC -

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

P_OLD_MCKEY - R/2 table

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

TABLES Parameters details for MASS_VENDOR_SAVE_PARALLEL

P_NEW_LFM2 - mass maintenance structure for MARC data

Data type: MASS_LFM2_D
Optional: Yes
Call by Reference: Yes

P_OLD_LFM2 - flat structure for mas maintenance style info (for RFC use)

Data type: LFM2
Optional: Yes
Call by Reference: Yes

P_INV_LFM2 - mass maintenance structure for MARC data

Data type: LFM2
Optional: Yes
Call by Reference: Yes

P_ALL_GT_STYLE - flat structure for mas maintenance style info (for RFC use)

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

ERROR_MSG - Meldungsbezogene Einträge für Application Log

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

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

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