SAP Function Modules

COND_N_WRITE_DOCUMENT SAP Function module - ===> Object COND_N , generated by program RSSCD000







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

Associated Function Group: V16N
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM COND_N_WRITE_DOCUMENT - COND N WRITE DOCUMENT





CALL FUNCTION 'COND_N_WRITE_DOCUMENT' "===> Object COND_N         , generated by program 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_kondat = SPACE          " cdpos-chngind
    n_kondn =                   " kondn
    o_kondn =                   " kondn
    upd_kondn = SPACE           " cdpos-chngind
    upd_kondns = SPACE          " cdpos-chngind
  TABLES
    xkondat =                   " vkondat
    ykondat =                   " vkondat
    xkondns =                   " vkondns
    ykondns =                   " vkondns
    .  "  COND_N_WRITE_DOCUMENT

ABAP code example for Function Module COND_N_WRITE_DOCUMENT





The ABAP code below is a full code listing to execute function module COND_N_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_xkondat  TYPE STANDARD TABLE OF VKONDAT,"TABLES PARAM
wa_xkondat  LIKE LINE OF it_xkondat ,
it_ykondat  TYPE STANDARD TABLE OF VKONDAT,"TABLES PARAM
wa_ykondat  LIKE LINE OF it_ykondat ,
it_xkondns  TYPE STANDARD TABLE OF VKONDNS,"TABLES PARAM
wa_xkondns  LIKE LINE OF it_xkondns ,
it_ykondns  TYPE STANDARD TABLE OF VKONDNS,"TABLES PARAM
wa_ykondns  LIKE LINE OF it_ykondns .


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

DATA(ld_n_kondn) = 'Check type of data required'.
DATA(ld_o_kondn) = 'Check type of data required'.

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


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


"populate fields of struture and append to itab
append wa_xkondat to it_xkondat.

"populate fields of struture and append to itab
append wa_ykondat to it_ykondat.

"populate fields of struture and append to itab
append wa_xkondns to it_xkondns.

"populate fields of struture and append to itab
append wa_ykondns to it_ykondns. . CALL FUNCTION 'COND_N_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_kondat = ld_upd_kondat n_kondn = ld_n_kondn o_kondn = ld_o_kondn upd_kondn = ld_upd_kondn upd_kondns = ld_upd_kondns TABLES xkondat = it_xkondat ykondat = it_ykondat xkondns = it_xkondns ykondns = it_ykondns . " COND_N_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_xkondat  TYPE STANDARD TABLE OF VKONDAT ,
wa_xkondat  LIKE LINE OF it_xkondat,
ld_tcode  TYPE CDHDR-TCODE ,
it_ykondat  TYPE STANDARD TABLE OF VKONDAT ,
wa_ykondat  LIKE LINE OF it_ykondat,
ld_utime  TYPE CDHDR-UTIME ,
it_xkondns  TYPE STANDARD TABLE OF VKONDNS ,
wa_xkondns  LIKE LINE OF it_xkondns,
ld_udate  TYPE CDHDR-UDATE ,
it_ykondns  TYPE STANDARD TABLE OF VKONDNS ,
wa_ykondns  LIKE LINE OF it_ykondns,
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_kondat  TYPE CDPOS-CHNGIND ,
ld_n_kondn  TYPE KONDN ,
ld_o_kondn  TYPE KONDN ,
ld_upd_kondn  TYPE CDPOS-CHNGIND ,
ld_upd_kondns  TYPE CDPOS-CHNGIND .


SELECT single OBJECTID
FROM CDHDR
INTO ld_objectid.


"populate fields of struture and append to itab
append wa_xkondat to it_xkondat.

SELECT single TCODE
FROM CDHDR
INTO ld_tcode.


"populate fields of struture and append to itab
append wa_ykondat to it_ykondat.

SELECT single UTIME
FROM CDHDR
INTO ld_utime.


"populate fields of struture and append to itab
append wa_xkondns to it_xkondns.

SELECT single UDATE
FROM CDHDR
INTO ld_udate.


"populate fields of struture and append to itab
append wa_ykondns to it_ykondns.

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

ld_n_kondn = 'Check type of data required'.
ld_o_kondn = 'Check type of data required'.

SELECT single CHNGIND
FROM CDPOS
INTO ld_upd_kondn.


SELECT single CHNGIND
FROM CDPOS
INTO ld_upd_kondns.

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