QTLS_WRITE_DOCUMENT SAP Function module

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

Associated Function Group: QTLU
Released Date: Not Released
Processing type: Start of update delayed (Start Delayed)

Pattern for FM QTLS_WRITE_DOCUMENT - QTLS WRITE DOCUMENT

CALL FUNCTION 'QTLS_WRITE_DOCUMENT' "
  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
    n_qalt =                    " qalt
    o_qalt =                    " qalt
*   upd_qalt = SPACE            " cdpos-chngind
    n_qave =                    " qave
    o_qave =                    " qave
*   upd_qave = SPACE            " cdpos-chngind
    .  "  QTLS_WRITE_DOCUMENT

ABAP code example for Function Module QTLS_WRITE_DOCUMENT

The ABAP code below is a full code listing to execute function module QTLS_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).

 

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


DATA(ld_n_qalt) = 'Check type of data required'.

DATA(ld_o_qalt) = 'Check type of data required'.
 

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


DATA(ld_n_qave) = 'Check type of data required'.

DATA(ld_o_qave) = 'Check type of data required'.
 

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

.

CALL FUNCTION 'QTLS_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
    n_qalt =                     ld_n_qalt
    o_qalt =                     ld_o_qalt
*   upd_qalt =                   ld_upd_qalt
    n_qave =                     ld_n_qave
    o_qave =                     ld_o_qave
*   upd_qave =                   ld_upd_qave
    .  "  QTLS_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 ,
ld_tcode
 
 TYPE CDHDR-TCODE ,
ld_utime
 
 TYPE CDHDR-UTIME ,
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_n_qalt
 
 TYPE QALT ,
ld_o_qalt
 
 TYPE QALT ,
ld_upd_qalt
 
 TYPE CDPOS-CHNGIND ,
ld_n_qave
 
 TYPE QAVE ,
ld_o_qave
 
 TYPE QAVE ,
ld_upd_qave
 
 TYPE CDPOS-CHNGIND .



SELECT single OBJECTID 
  FROM CDHDR 
  INTO ld_objectid.


SELECT single TCODE 
  FROM CDHDR 
  INTO ld_tcode.


SELECT single UTIME 
  FROM CDHDR 
  INTO ld_utime.


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.

ld_n_qalt = 'Check type of data required'.
ld_o_qalt = 'Check type of data required'.

SELECT single CHNGIND 
  FROM CDPOS 
  INTO ld_upd_qalt.

ld_n_qave = 'Check type of data required'.
ld_o_qave = 'Check type of data required'.

SELECT single CHNGIND 
  FROM CDPOS 
  INTO ld_upd_qave.