SAP MASS_MARC_SAVE_PARALLEL Function Module for Save in parallel
MASS_MARC_SAVE_PARALLEL is a standard mass marc 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 marc save parallel FM, simply by entering the name MASS_MARC_SAVE_PARALLEL into the relevant SAP transaction such as SE37 or SE38.
Function Group: MASS_MARC_UTILITIES
Program Name: SAPLMASS_MARC_UTILITIES
Main Program: SAPLMASS_MARC_UTILITIES
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:
Function MASS_MARC_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_MARC_SAVE_PARALLEL'"Save in parallel.
EXPORTING
P_MAX_SIZE = "
P_MAX_NBPROC = "
P_OLD_MCKEY = "R/2 table
TABLES
P_ALL_GT_MARC_FLAT = "mass maintenance structure for MARC data
P_ALL_GT_STYLE_FLAT = "flat structure for mas maintenance style info (for RFC use)
P_INV_GT_MARC_FLAT = "mass maintenance structure for MARC data
P_INV_GT_STYLE_FLAT = "flat structure for mas maintenance style info (for RFC use)
ERROR_MSG = "Meldungsbezogene Einträge für Application Log
T130F_TABLE = "Structure: T130F Extended to Include Table Name, Field Name
IMPORTING Parameters details for MASS_MARC_SAVE_PARALLEL
P_MAX_SIZE -
Data type: IOptional: No
Call by Reference: No ( called with pass by value option)
P_MAX_NBPROC -
Data type: IOptional: No
Call by Reference: No ( called with pass by value option)
P_OLD_MCKEY - R/2 table
Data type: CHAR5Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for MASS_MARC_SAVE_PARALLEL
P_ALL_GT_MARC_FLAT - mass maintenance structure for MARC data
Data type: MASS_MARC_DOptional: No
Call by Reference: Yes
P_ALL_GT_STYLE_FLAT - flat structure for mas maintenance style info (for RFC use)
Data type: MASS_STYLE_INFO_FLATOptional: No
Call by Reference: Yes
P_INV_GT_MARC_FLAT - mass maintenance structure for MARC data
Data type: MASS_MARC_DOptional: No
Call by Reference: Yes
P_INV_GT_STYLE_FLAT - flat structure for mas maintenance style info (for RFC use)
Data type: MASS_STYLE_INFO_FLATOptional: No
Call by Reference: Yes
ERROR_MSG - Meldungsbezogene Einträge für Application Log
Data type: MASS_BALMIOptional: No
Call by Reference: Yes
T130F_TABLE - Structure: T130F Extended to Include Table Name, Field Name
Data type: ST130FOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for MASS_MARC_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.DATA: | ||||
lv_p_max_size | TYPE I, " | |||
lt_p_all_gt_marc_flat | TYPE STANDARD TABLE OF MASS_MARC_D, " | |||
lv_p_max_nbproc | TYPE I, " | |||
lt_p_all_gt_style_flat | TYPE STANDARD TABLE OF MASS_STYLE_INFO_FLAT, " | |||
lv_p_old_mckey | TYPE CHAR5, " | |||
lt_p_inv_gt_marc_flat | TYPE STANDARD TABLE OF MASS_MARC_D, " | |||
lt_p_inv_gt_style_flat | TYPE STANDARD TABLE OF MASS_STYLE_INFO_FLAT, " | |||
lt_error_msg | TYPE STANDARD TABLE OF MASS_BALMI, " | |||
lt_t130f_table | TYPE STANDARD TABLE OF ST130F. " |
  CALL FUNCTION 'MASS_MARC_SAVE_PARALLEL' "Save in parallel |
EXPORTING | ||
P_MAX_SIZE | = lv_p_max_size | |
P_MAX_NBPROC | = lv_p_max_nbproc | |
P_OLD_MCKEY | = lv_p_old_mckey | |
TABLES | ||
P_ALL_GT_MARC_FLAT | = lt_p_all_gt_marc_flat | |
P_ALL_GT_STYLE_FLAT | = lt_p_all_gt_style_flat | |
P_INV_GT_MARC_FLAT | = lt_p_inv_gt_marc_flat | |
P_INV_GT_STYLE_FLAT | = lt_p_inv_gt_style_flat | |
ERROR_MSG | = lt_error_msg | |
T130F_TABLE | = lt_t130f_table | |
. " MASS_MARC_SAVE_PARALLEL |
ABAP code using 7.40 inline data declarations to call FM MASS_MARC_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