SAP Function Modules
REIT_OR_WRITE_DOCUMENT SAP Function module - CHDO REIT_OR => Gen. by RSSCD000
REIT_OR_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 REIT_OR_WRITE_DOCUMENT into the relevant SAP transaction such as SE37 or SE80.
Associated Function Group:
REIT_OR_CHDO
Released Date:
Not Released
Processing type: Start of update delayed (Start Delayed)
Pattern for FM REIT_OR_WRITE_DOCUMENT - REIT OR WRITE DOCUMENT
CALL FUNCTION 'REIT_OR_WRITE_DOCUMENT' "CHDO REIT_OR => 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_reit_or = SPACE " cdpos-chngind
upd_viitoptrate = SPACE " cdpos-chngind
TABLES
icdtxt_reit_or = " cdtxt
xviitoptrate = " aviitoptrate
yviitoptrate = " aviitoptrate
. " REIT_OR_WRITE_DOCUMENT
ABAP code example for Function Module REIT_OR_WRITE_DOCUMENT
The ABAP code below is a full code listing to execute function module REIT_OR_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).
| it_icdtxt_reit_or | TYPE STANDARD TABLE OF CDTXT,"TABLES PARAM |
| wa_icdtxt_reit_or | LIKE LINE OF it_icdtxt_reit_or , |
| it_xviitoptrate | TYPE STANDARD TABLE OF AVIITOPTRATE,"TABLES PARAM |
| wa_xviitoptrate | LIKE LINE OF it_xviitoptrate , |
| it_yviitoptrate | TYPE STANDARD TABLE OF AVIITOPTRATE,"TABLES PARAM |
| wa_yviitoptrate | LIKE LINE OF it_yviitoptrate . |
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_reit_or).
SELECT single CHNGIND
FROM CDPOS
INTO @DATA(ld_upd_viitoptrate).
"populate fields of struture and append to itab
append wa_icdtxt_reit_or to it_icdtxt_reit_or.
"populate fields of struture and append to itab
append wa_xviitoptrate to it_xviitoptrate.
"populate fields of struture and append to itab
append wa_yviitoptrate to it_yviitoptrate. . CALL FUNCTION 'REIT_OR_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_reit_or = ld_upd_icdtxt_reit_or upd_viitoptrate = ld_upd_viitoptrate TABLES icdtxt_reit_or = it_icdtxt_reit_or xviitoptrate = it_xviitoptrate yviitoptrate = it_yviitoptrate . " REIT_OR_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_reit_or | TYPE STANDARD TABLE OF CDTXT , |
| wa_icdtxt_reit_or | LIKE LINE OF it_icdtxt_reit_or, |
| ld_tcode | TYPE CDHDR-TCODE , |
| it_xviitoptrate | TYPE STANDARD TABLE OF AVIITOPTRATE , |
| wa_xviitoptrate | LIKE LINE OF it_xviitoptrate, |
| ld_utime | TYPE CDHDR-UTIME , |
| it_yviitoptrate | TYPE STANDARD TABLE OF AVIITOPTRATE , |
| wa_yviitoptrate | LIKE LINE OF it_yviitoptrate, |
| ld_udate | TYPE CDHDR-UDATE , |
| 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_upd_icdtxt_reit_or | TYPE CDPOS-CHNGIND , |
| ld_upd_viitoptrate | TYPE CDPOS-CHNGIND . |
SELECT single OBJECTID
FROM CDHDR
INTO ld_objectid.
"populate fields of struture and append to itab
append wa_icdtxt_reit_or to it_icdtxt_reit_or.
SELECT single TCODE
FROM CDHDR
INTO ld_tcode.
"populate fields of struture and append to itab
append wa_xviitoptrate to it_xviitoptrate.
SELECT single UTIME
FROM CDHDR
INTO ld_utime.
"populate fields of struture and append to itab
append wa_yviitoptrate to it_yviitoptrate.
SELECT single UDATE
FROM CDHDR
INTO ld_udate.
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.
SELECT single CHNGIND
FROM CDPOS
INTO ld_upd_icdtxt_reit_or.
SELECT single CHNGIND
FROM CDPOS
INTO ld_upd_viitoptrate.
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 REIT_OR_WRITE_DOCUMENT or its description.