SAP Function Modules

comments icon Comments

MASS_MARC_SAVE_CHANGE SAP Function module - Reads from cluster table MASS_JOB_ERROR







MASS_MARC_SAVE_CHANGE is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name MASS_MARC_SAVE_CHANGE into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: MASS_MARC_UTILITIES
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM MASS_MARC_SAVE_CHANGE - MASS MARC SAVE CHANGE 





CALL FUNCTION 'MASS_MARC_SAVE_CHANGE' "Reads from cluster table MASS_JOB_ERROR
  EXPORTING
*   i_user =                    " sy-uname      R/3 System, user logon name
*   i_date =                    " sy-datum      Date and time, current (application server) date
*   i_time =                    " sy-uzeit      Dat and time, current application server time
*   i_pgrmid =                  " sy-repid      ABAP program, current main program
    i_good_lines =              " numc5
*   i_old_mckey = SPACE         " char5         R/2 table
    t_records_in =              " mass_marc_table  table for MARC mass maintenance
  IMPORTING
    e_number =                  " mass_job_error-mckey  R/2 table
  TABLES
    t_err_msg_in =              " mass_balmi    Application Log: APPL_LOG_WRITE_MESSAGES interface
  EXCEPTIONS
    ERROR_IN_SAVE_DATA = 1      "
    ERROR_IN_SAVE_ERRORS = 2    "
    ERROR_IN_NUMBER_GENERATE = 3  "
    .  "  MASS_MARC_SAVE_CHANGE

ABAP code example for Function Module MASS_MARC_SAVE_CHANGE





The ABAP code below is a full code listing to execute function module MASS_MARC_SAVE_CHANGE including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_e_number    TYPE MASS_JOB_ERROR-MCKEY
,
it_t_err_msg_in    TYPE STANDARD TABLE OF MASS_BALMI,"TABLES PARAM
wa_t_err_msg_in  LIKE LINE OF it_t_err_msg_in
.




DATA(ld_i_user) = 'some text here'.

DATA(ld_i_date) = '20210129'.

DATA(ld_i_time) = 'Check type of data required'.

DATA(ld_i_pgrmid) = 'Check type of data required'.

DATA(ld_i_good_lines) = 'some text here'.

DATA(ld_i_old_mckey) = 'some text here'.

DATA(ld_t_records_in) = 'some text here'.
 

"populate fields of struture and append to itab
append wa_t_err_msg_in to it_t_err_msg_in.
.

CALL FUNCTION 'MASS_MARC_SAVE_CHANGE'
  EXPORTING
*   i_user =                     ld_i_user
*   i_date =                     ld_i_date
*   i_time =                     ld_i_time
*   i_pgrmid =                   ld_i_pgrmid
    i_good_lines =               ld_i_good_lines
*   i_old_mckey =                ld_i_old_mckey
    t_records_in =               ld_t_records_in
  IMPORTING
    e_number =                   ld_e_number
  TABLES
    t_err_msg_in =               it_t_err_msg_in
  EXCEPTIONS
    ERROR_IN_SAVE_DATA =         1
    ERROR_IN_SAVE_ERRORS =       2
    ERROR_IN_NUMBER_GENERATE =    3
    .  "  MASS_MARC_SAVE_CHANGE

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 3. "Exception
  "Add code for exception here
ENDIF.







ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:


ld_e_number  TYPE MASS_JOB_ERROR-MCKEY ,
ld_i_user  TYPE SY-UNAME ,
it_t_err_msg_in  TYPE STANDARD TABLE OF MASS_BALMI ,
wa_t_err_msg_in  LIKE LINE OF it_t_err_msg_in,
ld_i_date  TYPE SY-DATUM ,
ld_i_time  TYPE SY-UZEIT ,
ld_i_pgrmid  TYPE SY-REPID ,
ld_i_good_lines  TYPE NUMC5 ,
ld_i_old_mckey  TYPE CHAR5 ,
ld_t_records_in  TYPE MASS_MARC_TABLE .




ld_i_user = 'some text here'. 

"populate fields of struture and append to itab
append wa_t_err_msg_in to it_t_err_msg_in.
ld_i_date = '20210129'.
ld_i_time = 'Check type of data required'.
ld_i_pgrmid = 'Check type of data required'.
ld_i_good_lines = 'some text here'.
ld_i_old_mckey = 'some text here'.
ld_t_records_in = 'some text here'.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name MASS_MARC_SAVE_CHANGE or its description.


   
 

MASS_MARC_SAVE_CHANGE - Reads from cluster table MASS_JOB_ERROR
MASS_MARC_READ_CHANGE - Reads from cluster table ZMCINDX
MASS_MARC_READ - Reads MARC, MPOP, WRPL
MASS_MARC_PRE_ERROR_SCREEN - error screen for mass change
MASS_MARC_MERGE - Merge MARC, WRPL, MPOP into MASS_MARC
MASS_MARC_ERROR_SCREEN - error screen for mass change