SAP FM_UPDATE_DATE_VALUES Function Module for It keeps static values for FM document/posting date









FM_UPDATE_DATE_VALUES is a standard fm update date values SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for It keeps static values for FM document/posting date 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 fm update date values FM, simply by entering the name FM_UPDATE_DATE_VALUES into the relevant SAP transaction such as SE37 or SE38.

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



Function FM_UPDATE_DATE_VALUES 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 'FM_UPDATE_DATE_VALUES'"It keeps static values for FM document/posting  date
  EXPORTING
*  I_SEND_VALUES = ' ' "Checkbox
*  I_MASS_PROCESS = ' ' "Checkbox
*  I_FM_UPDATE_DATE = 00000000 "Date and Time, Current (Application Server) Date
*  I_FM_UPDATE_PERIOD = 000 "Number of posting periods
*  I_FM_DOC_DATE = 00000000 "Date and time, current (application server) date
*  I_FLG_SRM_ONLY = ' ' "Feld zum Ankreuzen

 IMPORTING
   E_FM_UPDATE_DATE =  "Date and time, current (application server) date
   E_FM_UPDATE_PERIOD =  "Date and time, current (application server) date
   E_FM_DOC_DATE =  "Date and time, current (application server) date
.



IMPORTING Parameters details for FM_UPDATE_DATE_VALUES

I_SEND_VALUES - Checkbox

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

I_MASS_PROCESS - Checkbox

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

I_FM_UPDATE_DATE - Date and Time, Current (Application Server) Date

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

I_FM_UPDATE_PERIOD - Number of posting periods

Data type: T009-ANZBP
Default: 000
Optional: Yes
Call by Reference: No ( called with pass by value option)

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

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

I_FLG_SRM_ONLY - Feld zum Ankreuzen

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

EXPORTING Parameters details for FM_UPDATE_DATE_VALUES

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

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

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

Data type: T009-ANZBP
Optional: No
Call by Reference: No ( called with pass by value option)

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

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

Copy and paste ABAP code example for FM_UPDATE_DATE_VALUES 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_i_send_values  TYPE XFELD, "   SPACE
lv_e_fm_update_date  TYPE SY-DATUM, "   
lv_i_mass_process  TYPE XFELD, "   SPACE
lv_e_fm_update_period  TYPE T009-ANZBP, "   
lv_e_fm_doc_date  TYPE SY-DATUM, "   
lv_i_fm_update_date  TYPE SY-DATUM, "   00000000
lv_i_fm_update_period  TYPE T009-ANZBP, "   000
lv_i_fm_doc_date  TYPE SY-DATUM, "   00000000
lv_i_flg_srm_only  TYPE XFELD. "   SPACE

  CALL FUNCTION 'FM_UPDATE_DATE_VALUES'  "It keeps static values for FM document/posting date
    EXPORTING
         I_SEND_VALUES = lv_i_send_values
         I_MASS_PROCESS = lv_i_mass_process
         I_FM_UPDATE_DATE = lv_i_fm_update_date
         I_FM_UPDATE_PERIOD = lv_i_fm_update_period
         I_FM_DOC_DATE = lv_i_fm_doc_date
         I_FLG_SRM_ONLY = lv_i_flg_srm_only
    IMPORTING
         E_FM_UPDATE_DATE = lv_e_fm_update_date
         E_FM_UPDATE_PERIOD = lv_e_fm_update_period
         E_FM_DOC_DATE = lv_e_fm_doc_date
. " FM_UPDATE_DATE_VALUES




ABAP code using 7.40 inline data declarations to call FM FM_UPDATE_DATE_VALUES

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.

DATA(ld_i_send_values) = ' '.
 
"SELECT single DATUM FROM SY INTO @DATA(ld_e_fm_update_date).
 
DATA(ld_i_mass_process) = ' '.
 
"SELECT single ANZBP FROM T009 INTO @DATA(ld_e_fm_update_period).
 
"SELECT single DATUM FROM SY INTO @DATA(ld_e_fm_doc_date).
 
"SELECT single DATUM FROM SY INTO @DATA(ld_i_fm_update_date).
DATA(ld_i_fm_update_date) = 00000000.
 
"SELECT single ANZBP FROM T009 INTO @DATA(ld_i_fm_update_period).
DATA(ld_i_fm_update_period) = 000.
 
"SELECT single DATUM FROM SY INTO @DATA(ld_i_fm_doc_date).
DATA(ld_i_fm_doc_date) = 00000000.
 
DATA(ld_i_flg_srm_only) = ' '.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!