SAP Function Modules

ICLCLAIM_WRITE_DOCUMENT SAP Function module - CHDO ICLCLAIM => Gen. by RSSCD000







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

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


Pattern for FM ICLCLAIM_WRITE_DOCUMENT - ICLCLAIM WRITE DOCUMENT





CALL FUNCTION 'ICLCLAIM_WRITE_DOCUMENT' "CHDO ICLCLAIM => 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
    n_iclclaim =                " iclclaim
    o_gs_claim_old =            " iclclaim
    upd_iclclaim = SPACE        " cdpos-chngind
    upd_iclpartocc = SPACE      " cdpos-chngind
    upd_iclsubcl = SPACE        " cdpos-chngind
  TABLES
    xiclpartocc =               " viclpartocc
    yiclpartocc =               " viclpartocc
    xiclsubcl =                 " viclsubcl
    yiclsubcl =                 " viclsubcl
    .  "  ICLCLAIM_WRITE_DOCUMENT

ABAP code example for Function Module ICLCLAIM_WRITE_DOCUMENT





The ABAP code below is a full code listing to execute function module ICLCLAIM_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_xiclpartocc  TYPE STANDARD TABLE OF VICLPARTOCC,"TABLES PARAM
wa_xiclpartocc  LIKE LINE OF it_xiclpartocc ,
it_yiclpartocc  TYPE STANDARD TABLE OF VICLPARTOCC,"TABLES PARAM
wa_yiclpartocc  LIKE LINE OF it_yiclpartocc ,
it_xiclsubcl  TYPE STANDARD TABLE OF VICLSUBCL,"TABLES PARAM
wa_xiclsubcl  LIKE LINE OF it_xiclsubcl ,
it_yiclsubcl  TYPE STANDARD TABLE OF VICLSUBCL,"TABLES PARAM
wa_yiclsubcl  LIKE LINE OF it_yiclsubcl .


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

DATA(ld_n_iclclaim) = 'Check type of data required'.
DATA(ld_o_gs_claim_old) = 'Check type of data required'.

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


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


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


"populate fields of struture and append to itab
append wa_xiclpartocc to it_xiclpartocc.

"populate fields of struture and append to itab
append wa_yiclpartocc to it_yiclpartocc.

"populate fields of struture and append to itab
append wa_xiclsubcl to it_xiclsubcl.

"populate fields of struture and append to itab
append wa_yiclsubcl to it_yiclsubcl. . CALL FUNCTION 'ICLCLAIM_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 n_iclclaim = ld_n_iclclaim o_gs_claim_old = ld_o_gs_claim_old upd_iclclaim = ld_upd_iclclaim upd_iclpartocc = ld_upd_iclpartocc upd_iclsubcl = ld_upd_iclsubcl TABLES xiclpartocc = it_xiclpartocc yiclpartocc = it_yiclpartocc xiclsubcl = it_xiclsubcl yiclsubcl = it_yiclsubcl . " ICLCLAIM_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_xiclpartocc  TYPE STANDARD TABLE OF VICLPARTOCC ,
wa_xiclpartocc  LIKE LINE OF it_xiclpartocc,
ld_tcode  TYPE CDHDR-TCODE ,
it_yiclpartocc  TYPE STANDARD TABLE OF VICLPARTOCC ,
wa_yiclpartocc  LIKE LINE OF it_yiclpartocc,
ld_utime  TYPE CDHDR-UTIME ,
it_xiclsubcl  TYPE STANDARD TABLE OF VICLSUBCL ,
wa_xiclsubcl  LIKE LINE OF it_xiclsubcl,
ld_udate  TYPE CDHDR-UDATE ,
it_yiclsubcl  TYPE STANDARD TABLE OF VICLSUBCL ,
wa_yiclsubcl  LIKE LINE OF it_yiclsubcl,
ld_username  TYPE CDHDR-USERNAME ,
ld_planned_change_number  TYPE CDHDR-PLANCHNGNR ,
ld_object_change_indicator  TYPE CDHDR-CHANGE_IND ,
ld_planned_or_real_changes  TYPE CDHDR-CHANGE_IND ,
ld_no_change_pointers  TYPE CDHDR-CHANGE_IND ,
ld_n_iclclaim  TYPE ICLCLAIM ,
ld_o_gs_claim_old  TYPE ICLCLAIM ,
ld_upd_iclclaim  TYPE CDPOS-CHNGIND ,
ld_upd_iclpartocc  TYPE CDPOS-CHNGIND ,
ld_upd_iclsubcl  TYPE CDPOS-CHNGIND .


SELECT single OBJECTID
FROM CDHDR
INTO ld_objectid.


"populate fields of struture and append to itab
append wa_xiclpartocc to it_xiclpartocc.

SELECT single TCODE
FROM CDHDR
INTO ld_tcode.


"populate fields of struture and append to itab
append wa_yiclpartocc to it_yiclpartocc.

SELECT single UTIME
FROM CDHDR
INTO ld_utime.


"populate fields of struture and append to itab
append wa_xiclsubcl to it_xiclsubcl.

SELECT single UDATE
FROM CDHDR
INTO ld_udate.


"populate fields of struture and append to itab
append wa_yiclsubcl to it_yiclsubcl.

SELECT single USERNAME
FROM CDHDR
INTO ld_username.


SELECT single PLANCHNGNR
FROM CDHDR
INTO ld_planned_change_number.


SELECT single CHANGE_IND
FROM CDHDR
INTO ld_object_change_indicator.


SELECT single CHANGE_IND
FROM CDHDR
INTO ld_planned_or_real_changes.


SELECT single CHANGE_IND
FROM CDHDR
INTO ld_no_change_pointers.

ld_n_iclclaim = 'Check type of data required'.
ld_o_gs_claim_old = 'Check type of data required'.

SELECT single CHNGIND
FROM CDPOS
INTO ld_upd_iclclaim.


SELECT single CHNGIND
FROM CDPOS
INTO ld_upd_iclpartocc.


SELECT single CHNGIND
FROM CDPOS
INTO ld_upd_iclsubcl.

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