SAP Function Modules

comments icon Comments

FVDD_WRITE_VDUNTR SAP Function module - Write VDUNTR (Filed Documents)







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

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


Pattern for FM FVDD_WRITE_VDUNTR - FVDD WRITE VDUNTR 





CALL FUNCTION 'FVDD_WRITE_VDUNTR' "Write VDUNTR (Filed Documents)
  EXPORTING
    i_direction =               " rmf67-sland   IN = Eigehende Dokument, OUT = Ausgehende Dok.
*   i_object_id =               " toa_dara-object_id  SAPArchiveLink: Objektidentifikation
*   i_document_date = SY-DATUM  " sy-datum      Retirement Date
*   i_tzkvt =                   " tzkvt         Korrespondenzvorfall-text (bei Ausg.Doks)
*   i_document_address =        " adrs          Adress (bei ausgehende Dokumente)
*   i_snuntr =                  " vduntr-snuntr  SNUNTR für neue Satz
    i_unterlagenart =           " vduntr-suart  Document type
*   i_brief =                   " ttxbf-xbrfbs  Letter Name
  TABLES
    contracts =                 " vdarl         Contracts
  EXCEPTIONS
    INSERT_ERROR = 1            "               Fehler bei INSERT VDUNTR
    MISSING_SNUNTR = 2          "               SNUNTR soll bei Ausg.Dokumente vorhanden sein
    FALSE_DIRECTION = 3         "               I_DIRECTION hat weder IN noch OUT
    .  "  FVDD_WRITE_VDUNTR

ABAP code example for Function Module FVDD_WRITE_VDUNTR





The ABAP code below is a full code listing to execute function module FVDD_WRITE_VDUNTR 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_contracts    TYPE STANDARD TABLE OF VDARL,"TABLES PARAM
wa_contracts  LIKE LINE OF it_contracts
.





DATA(ld_i_direction) = some text here


DATA(ld_i_object_id) = some text here

DATA(ld_i_document_date) = '20210129'.

DATA(ld_i_tzkvt) = '20210129'.

DATA(ld_i_document_address) = '20210129'.
 

SELECT single SNUNTR 
  FROM VDUNTR 
  INTO @DATA(ld_i_snuntr).

 

SELECT single SUART 
  FROM VDUNTR 
  INTO @DATA(ld_i_unterlagenart).

 

SELECT single XBRFBS 
  FROM TTXBF 
  INTO @DATA(ld_i_brief).

 

"populate fields of struture and append to itab
append wa_contracts to it_contracts.
.

CALL FUNCTION 'FVDD_WRITE_VDUNTR'
  EXPORTING
    i_direction =                ld_i_direction
*   i_object_id =                ld_i_object_id
*   i_document_date =            ld_i_document_date
*   i_tzkvt =                    ld_i_tzkvt
*   i_document_address =         ld_i_document_address
*   i_snuntr =                   ld_i_snuntr
    i_unterlagenart =            ld_i_unterlagenart
*   i_brief =                    ld_i_brief
  TABLES
    contracts =                  it_contracts
  EXCEPTIONS
    INSERT_ERROR =               1
    MISSING_SNUNTR =             2
    FALSE_DIRECTION =            3
    .  "  FVDD_WRITE_VDUNTR

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 3. "Exception
  "Add code for exception here
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_i_direction  TYPE RMF67-SLAND ,
it_contracts  TYPE STANDARD TABLE OF VDARL ,
wa_contracts  LIKE LINE OF it_contracts,
ld_i_object_id  TYPE TOA_DARA-OBJECT_ID ,
ld_i_document_date  TYPE SY-DATUM ,
ld_i_tzkvt  TYPE TZKVT ,
ld_i_document_address  TYPE ADRS ,
ld_i_snuntr  TYPE VDUNTR-SNUNTR ,
ld_i_unterlagenart  TYPE VDUNTR-SUART ,
ld_i_brief  TYPE TTXBF-XBRFBS .





ld_i_direction = some text here 

"populate fields of struture and append to itab
append wa_contracts to it_contracts.

ld_i_object_id = some text here
ld_i_document_date = '20210129'.
ld_i_tzkvt = '20210129'.
ld_i_document_address = '20210129'.

SELECT single SNUNTR 
  FROM VDUNTR 
  INTO ld_i_snuntr.


SELECT single SUART 
  FROM VDUNTR 
  INTO ld_i_unterlagenart.


SELECT single XBRFBS 
  FROM TTXBF 
  INTO ld_i_brief.

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


   
 

FVDD_WRITE_VDUNTR - Write VDUNTR (Filed Documents)
FVDD_CONVERT_GENERIC_TCODE - Defines Specific Transaction Codes from Generic Transaction Codes
FVDB_BUPA_EVENT_XCHNG - 
FVDB_BUPA_EVENT_ISSTA - 
FVDB_BUPA_EVENT_ISDAT - 
FVDB_BUPA_EVENT_FCODE -