SAP Function Modules

FMCI_WRITE_DOCUMENT SAP Function module - CHDO FMCI => Gen. by RSSCD000







FMCI_WRITE_DOCUMENT 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 FMCI_WRITE_DOCUMENT into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: FMCI7
Released Date: Not Released
Processing type: Start update immediately (start immed)
update module start immediate settings


Pattern for FM FMCI_WRITE_DOCUMENT - FMCI WRITE DOCUMENT





CALL FUNCTION 'FMCI_WRITE_DOCUMENT' "CHDO FMCI => Gen. by RSSCD000
  EXPORTING
    objectid =                  " cdhdr-objectid
    tcode =                     " cdhdr-tcode
    utime =                     " cdhdr-utime
    udate =                     " cdhdr-udate
    username =                  " cdhdr-username
    planned_change_number = SPACE  " cdhdr-planchngnr
    object_change_indicator = 'U'  " cdhdr-change_ind
    planned_or_real_changes = SPACE  " cdhdr-change_ind
    no_change_pointers = SPACE  " cdhdr-change_ind
    upd_icdtxt_fmci = SPACE     " cdpos-chngind
    upd_fmci = SPACE            " cdpos-chngind
    upd_fmcit = SPACE           " cdpos-chngind
    upd_fmzubsp = SPACE         " cdpos-chngind
  TABLES
    icdtxt_fmci =               " cdtxt
    xfmci =                     " cfmci
    yfmci =                     " cfmci
    xfmcit =                    " cfmcit
    yfmcit =                    " cfmcit
    xfmzubsp =                  " cfmzubsp
    yfmzubsp =                  " cfmzubsp
    .  "  FMCI_WRITE_DOCUMENT

ABAP code example for Function Module FMCI_WRITE_DOCUMENT





The ABAP code below is a full code listing to execute function module FMCI_WRITE_DOCUMENT 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:
it_icdtxt_fmci  TYPE STANDARD TABLE OF CDTXT,"TABLES PARAM
wa_icdtxt_fmci  LIKE LINE OF it_icdtxt_fmci ,
it_xfmci  TYPE STANDARD TABLE OF CFMCI,"TABLES PARAM
wa_xfmci  LIKE LINE OF it_xfmci ,
it_yfmci  TYPE STANDARD TABLE OF CFMCI,"TABLES PARAM
wa_yfmci  LIKE LINE OF it_yfmci ,
it_xfmcit  TYPE STANDARD TABLE OF CFMCIT,"TABLES PARAM
wa_xfmcit  LIKE LINE OF it_xfmcit ,
it_yfmcit  TYPE STANDARD TABLE OF CFMCIT,"TABLES PARAM
wa_yfmcit  LIKE LINE OF it_yfmcit ,
it_xfmzubsp  TYPE STANDARD TABLE OF CFMZUBSP,"TABLES PARAM
wa_xfmzubsp  LIKE LINE OF it_xfmzubsp ,
it_yfmzubsp  TYPE STANDARD TABLE OF CFMZUBSP,"TABLES PARAM
wa_yfmzubsp  LIKE LINE OF it_yfmzubsp .


SELECT single OBJECTID
FROM CDHDR
INTO @DATA(ld_objectid).


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).


SELECT single CHANGE_IND
FROM CDHDR
INTO @DATA(ld_object_change_indicator).


SELECT single CHANGE_IND
FROM CDHDR
INTO @DATA(ld_planned_or_real_changes).


SELECT single CHANGE_IND
FROM CDHDR
INTO @DATA(ld_no_change_pointers).


SELECT single CHNGIND
FROM CDPOS
INTO @DATA(ld_upd_icdtxt_fmci).


SELECT single CHNGIND
FROM CDPOS
INTO @DATA(ld_upd_fmci).


SELECT single CHNGIND
FROM CDPOS
INTO @DATA(ld_upd_fmcit).


SELECT single CHNGIND
FROM CDPOS
INTO @DATA(ld_upd_fmzubsp).


"populate fields of struture and append to itab
append wa_icdtxt_fmci to it_icdtxt_fmci.

"populate fields of struture and append to itab
append wa_xfmci to it_xfmci.

"populate fields of struture and append to itab
append wa_yfmci to it_yfmci.

"populate fields of struture and append to itab
append wa_xfmcit to it_xfmcit.

"populate fields of struture and append to itab
append wa_yfmcit to it_yfmcit.

"populate fields of struture and append to itab
append wa_xfmzubsp to it_xfmzubsp.

"populate fields of struture and append to itab
append wa_yfmzubsp to it_yfmzubsp. . CALL FUNCTION 'FMCI_WRITE_DOCUMENT' EXPORTING objectid = ld_objectid tcode = ld_tcode utime = ld_utime udate = ld_udate username = ld_username planned_change_number = ld_planned_change_number object_change_indicator = ld_object_change_indicator planned_or_real_changes = ld_planned_or_real_changes no_change_pointers = ld_no_change_pointers upd_icdtxt_fmci = ld_upd_icdtxt_fmci upd_fmci = ld_upd_fmci upd_fmcit = ld_upd_fmcit upd_fmzubsp = ld_upd_fmzubsp TABLES icdtxt_fmci = it_icdtxt_fmci xfmci = it_xfmci yfmci = it_yfmci xfmcit = it_xfmcit yfmcit = it_yfmcit xfmzubsp = it_xfmzubsp yfmzubsp = it_yfmzubsp . " FMCI_WRITE_DOCUMENT
IF SY-SUBRC EQ 0. "All OK 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_objectid  TYPE CDHDR-OBJECTID ,
it_icdtxt_fmci  TYPE STANDARD TABLE OF CDTXT ,
wa_icdtxt_fmci  LIKE LINE OF it_icdtxt_fmci,
ld_tcode  TYPE CDHDR-TCODE ,
it_xfmci  TYPE STANDARD TABLE OF CFMCI ,
wa_xfmci  LIKE LINE OF it_xfmci,
ld_utime  TYPE CDHDR-UTIME ,
it_yfmci  TYPE STANDARD TABLE OF CFMCI ,
wa_yfmci  LIKE LINE OF it_yfmci,
ld_udate  TYPE CDHDR-UDATE ,
it_xfmcit  TYPE STANDARD TABLE OF CFMCIT ,
wa_xfmcit  LIKE LINE OF it_xfmcit,
ld_username  TYPE CDHDR-USERNAME ,
it_yfmcit  TYPE STANDARD TABLE OF CFMCIT ,
wa_yfmcit  LIKE LINE OF it_yfmcit,
ld_planned_change_number  TYPE CDHDR-PLANCHNGNR ,
it_xfmzubsp  TYPE STANDARD TABLE OF CFMZUBSP ,
wa_xfmzubsp  LIKE LINE OF it_xfmzubsp,
ld_object_change_indicator  TYPE CDHDR-CHANGE_IND ,
it_yfmzubsp  TYPE STANDARD TABLE OF CFMZUBSP ,
wa_yfmzubsp  LIKE LINE OF it_yfmzubsp,
ld_planned_or_real_changes  TYPE CDHDR-CHANGE_IND ,
ld_no_change_pointers  TYPE CDHDR-CHANGE_IND ,
ld_upd_icdtxt_fmci  TYPE CDPOS-CHNGIND ,
ld_upd_fmci  TYPE CDPOS-CHNGIND ,
ld_upd_fmcit  TYPE CDPOS-CHNGIND ,
ld_upd_fmzubsp  TYPE CDPOS-CHNGIND .


SELECT single OBJECTID
FROM CDHDR
INTO ld_objectid.


"populate fields of struture and append to itab
append wa_icdtxt_fmci to it_icdtxt_fmci.

SELECT single TCODE
FROM CDHDR
INTO ld_tcode.


"populate fields of struture and append to itab
append wa_xfmci to it_xfmci.

SELECT single UTIME
FROM CDHDR
INTO ld_utime.


"populate fields of struture and append to itab
append wa_yfmci to it_yfmci.

SELECT single UDATE
FROM CDHDR
INTO ld_udate.


"populate fields of struture and append to itab
append wa_xfmcit to it_xfmcit.

SELECT single USERNAME
FROM CDHDR
INTO ld_username.


"populate fields of struture and append to itab
append wa_yfmcit to it_yfmcit.

SELECT single PLANCHNGNR
FROM CDHDR
INTO ld_planned_change_number.


"populate fields of struture and append to itab
append wa_xfmzubsp to it_xfmzubsp.

SELECT single CHANGE_IND
FROM CDHDR
INTO ld_object_change_indicator.


"populate fields of struture and append to itab
append wa_yfmzubsp to it_yfmzubsp.

SELECT single CHANGE_IND
FROM CDHDR
INTO ld_planned_or_real_changes.


SELECT single CHANGE_IND
FROM CDHDR
INTO ld_no_change_pointers.


SELECT single CHNGIND
FROM CDPOS
INTO ld_upd_icdtxt_fmci.


SELECT single CHNGIND
FROM CDPOS
INTO ld_upd_fmci.


SELECT single CHNGIND
FROM CDPOS
INTO ld_upd_fmcit.


SELECT single CHNGIND
FROM CDPOS
INTO ld_upd_fmzubsp.

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 FMCI_WRITE_DOCUMENT or its description.