SAP DFS_FE_MEASURES_WRITE_DOCUMENT Function Module for CHDO DFS_FE_MEASURES => Gen. by RSSCD000
DFS_FE_MEASURES_WRITE_DOCUMENT is a standard dfs fe measures write document SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for CHDO DFS_FE_MEASURES => Gen. by RSSCD000 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 dfs fe measures write document FM, simply by entering the name DFS_FE_MEASURES_WRITE_DOCUMENT into the relevant SAP transaction such as SE37 or SE38.
Function Group: DFS_FE_MEASURES
Program Name: SAPLDFS_FE_MEASURES
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update: 2

Function DFS_FE_MEASURES_WRITE_DOCUMENT 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 'DFS_FE_MEASURES_WRITE_DOCUMENT'"CHDO DFS_FE_MEASURES => Gen. by RSSCD000.
EXPORTING
OBJECTID = "
* UPD_ICDTXT_DFS_FE_MEASURES = ' ' "
* N_ISDFPS_ORGM = "
* O_ISDFPS_ORGM = "
* UPD_ISDFPS_ORGM = ' ' "
* N_SCMG_T_CASE_ATTR = "
* O_SCMG_T_CASE_ATTR = "
* UPD_SCMG_T_CASE_ATTR = ' ' "
TCODE = "
UTIME = "
UDATE = "
USERNAME = "
* PLANNED_CHANGE_NUMBER = ' ' "
* OBJECT_CHANGE_INDICATOR = 'U' "
* PLANNED_OR_REAL_CHANGES = ' ' "
* NO_CHANGE_POINTERS = ' ' "
TABLES
* ICDTXT_DFS_FE_MEASURES = "
IMPORTING Parameters details for DFS_FE_MEASURES_WRITE_DOCUMENT
OBJECTID -
Data type: CDHDR-OBJECTIDOptional: No
Call by Reference: No ( called with pass by value option)
UPD_ICDTXT_DFS_FE_MEASURES -
Data type: CDPOS-CHNGINDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
N_ISDFPS_ORGM -
Data type: /ISDFPS/ORGMOptional: Yes
Call by Reference: No ( called with pass by value option)
O_ISDFPS_ORGM -
Data type: /ISDFPS/ORGMOptional: Yes
Call by Reference: No ( called with pass by value option)
UPD_ISDFPS_ORGM -
Data type: CDPOS-CHNGINDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
N_SCMG_T_CASE_ATTR -
Data type: SCMG_T_CASE_ATTROptional: Yes
Call by Reference: No ( called with pass by value option)
O_SCMG_T_CASE_ATTR -
Data type: SCMG_T_CASE_ATTROptional: Yes
Call by Reference: No ( called with pass by value option)
UPD_SCMG_T_CASE_ATTR -
Data type: CDPOS-CHNGINDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
TCODE -
Data type: CDHDR-TCODEOptional: No
Call by Reference: No ( called with pass by value option)
UTIME -
Data type: CDHDR-UTIMEOptional: No
Call by Reference: No ( called with pass by value option)
UDATE -
Data type: CDHDR-UDATEOptional: No
Call by Reference: No ( called with pass by value option)
USERNAME -
Data type: CDHDR-USERNAMEOptional: No
Call by Reference: No ( called with pass by value option)
PLANNED_CHANGE_NUMBER -
Data type: CDHDR-PLANCHNGNRDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
OBJECT_CHANGE_INDICATOR -
Data type: CDHDR-CHANGE_INDDefault: 'U'
Optional: Yes
Call by Reference: No ( called with pass by value option)
PLANNED_OR_REAL_CHANGES -
Data type: CDHDR-CHANGE_INDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
NO_CHANGE_POINTERS -
Data type: CDHDR-CHANGE_INDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for DFS_FE_MEASURES_WRITE_DOCUMENT
ICDTXT_DFS_FE_MEASURES -
Data type: CDTXTOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for DFS_FE_MEASURES_WRITE_DOCUMENT 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_objectid | TYPE CDHDR-OBJECTID, " | |||
| lt_icdtxt_dfs_fe_measures | TYPE STANDARD TABLE OF CDTXT, " | |||
| lv_upd_icdtxt_dfs_fe_measures | TYPE CDPOS-CHNGIND, " SPACE | |||
| lv_n_isdfps_orgm | TYPE /ISDFPS/ORGM, " | |||
| lv_o_isdfps_orgm | TYPE /ISDFPS/ORGM, " | |||
| lv_upd_isdfps_orgm | TYPE CDPOS-CHNGIND, " SPACE | |||
| lv_n_scmg_t_case_attr | TYPE SCMG_T_CASE_ATTR, " | |||
| lv_o_scmg_t_case_attr | TYPE SCMG_T_CASE_ATTR, " | |||
| lv_upd_scmg_t_case_attr | TYPE CDPOS-CHNGIND, " SPACE | |||
| lv_tcode | TYPE CDHDR-TCODE, " | |||
| lv_utime | TYPE CDHDR-UTIME, " | |||
| lv_udate | TYPE CDHDR-UDATE, " | |||
| lv_username | TYPE CDHDR-USERNAME, " | |||
| lv_planned_change_number | TYPE CDHDR-PLANCHNGNR, " SPACE | |||
| lv_object_change_indicator | TYPE CDHDR-CHANGE_IND, " 'U' | |||
| lv_planned_or_real_changes | TYPE CDHDR-CHANGE_IND, " SPACE | |||
| lv_no_change_pointers | TYPE CDHDR-CHANGE_IND. " SPACE |
|   CALL FUNCTION 'DFS_FE_MEASURES_WRITE_DOCUMENT' "CHDO DFS_FE_MEASURES => Gen. by RSSCD000 |
| EXPORTING | ||
| OBJECTID | = lv_objectid | |
| UPD_ICDTXT_DFS_FE_MEASURES | = lv_upd_icdtxt_dfs_fe_measures | |
| N_ISDFPS_ORGM | = lv_n_isdfps_orgm | |
| O_ISDFPS_ORGM | = lv_o_isdfps_orgm | |
| UPD_ISDFPS_ORGM | = lv_upd_isdfps_orgm | |
| N_SCMG_T_CASE_ATTR | = lv_n_scmg_t_case_attr | |
| O_SCMG_T_CASE_ATTR | = lv_o_scmg_t_case_attr | |
| UPD_SCMG_T_CASE_ATTR | = lv_upd_scmg_t_case_attr | |
| TCODE | = lv_tcode | |
| UTIME | = lv_utime | |
| UDATE | = lv_udate | |
| USERNAME | = lv_username | |
| PLANNED_CHANGE_NUMBER | = lv_planned_change_number | |
| OBJECT_CHANGE_INDICATOR | = lv_object_change_indicator | |
| PLANNED_OR_REAL_CHANGES | = lv_planned_or_real_changes | |
| NO_CHANGE_POINTERS | = lv_no_change_pointers | |
| TABLES | ||
| ICDTXT_DFS_FE_MEASURES | = lt_icdtxt_dfs_fe_measures | |
| . " DFS_FE_MEASURES_WRITE_DOCUMENT | ||
ABAP code using 7.40 inline data declarations to call FM DFS_FE_MEASURES_WRITE_DOCUMENT
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.| "SELECT single OBJECTID FROM CDHDR INTO @DATA(ld_objectid). | ||||
| "SELECT single CHNGIND FROM CDPOS INTO @DATA(ld_upd_icdtxt_dfs_fe_measures). | ||||
| DATA(ld_upd_icdtxt_dfs_fe_measures) | = ' '. | |||
| "SELECT single CHNGIND FROM CDPOS INTO @DATA(ld_upd_isdfps_orgm). | ||||
| DATA(ld_upd_isdfps_orgm) | = ' '. | |||
| "SELECT single CHNGIND FROM CDPOS INTO @DATA(ld_upd_scmg_t_case_attr). | ||||
| DATA(ld_upd_scmg_t_case_attr) | = ' '. | |||
| "SELECT single TCODE FROM CDHDR INTO @DATA(ld_tcode). | ||||
| "SELECT single UTIME FROM CDHDR INTO @DATA(ld_utime). | ||||
| "SELECT single UDATE FROM CDHDR INTO @DATA(ld_udate). | ||||
| "SELECT single USERNAME FROM CDHDR INTO @DATA(ld_username). | ||||
| "SELECT single PLANCHNGNR FROM CDHDR INTO @DATA(ld_planned_change_number). | ||||
| DATA(ld_planned_change_number) | = ' '. | |||
| "SELECT single CHANGE_IND FROM CDHDR INTO @DATA(ld_object_change_indicator). | ||||
| DATA(ld_object_change_indicator) | = 'U'. | |||
| "SELECT single CHANGE_IND FROM CDHDR INTO @DATA(ld_planned_or_real_changes). | ||||
| DATA(ld_planned_or_real_changes) | = ' '. | |||
| "SELECT single CHANGE_IND FROM CDHDR INTO @DATA(ld_no_change_pointers). | ||||
| DATA(ld_no_change_pointers) | = ' '. | |||
Search for further information about these or an SAP related objects