SAP CV200_DB_DOC_UPDATE Function Module for NOTRANSL: DVS: Daten auf DB schreiben









CV200_DB_DOC_UPDATE is a standard cv200 db doc update SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: DVS: Daten auf DB schreiben processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.


See here to view full function module documentation and code listing for cv200 db doc update FM, simply by entering the name CV200_DB_DOC_UPDATE into the relevant SAP transaction such as SE37 or SE38.

Function Group: CV200
Program Name: SAPLCV200
Main Program: SAPLCV200
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update: 1



Function CV200_DB_DOC_UPDATE pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.
CALL FUNCTION 'CV200_DB_DOC_UPDATE'"NOTRANSL: DVS: Daten auf DB schreiben
  EXPORTING
   PF_TACODE =  "Transaction Code
*  PF_KPRO_USE =  "Document Storage via Knowledge Provider
*  PF_API_FLAG = ' ' "API Indicator
   PS_DRAW =  "Document Info Record
   PS_DRAW_OLD =  "Document Info Record
   PS_AUDITS =  "DVS: Indicator Audits

TABLES
*  PT_DRAT =  "DVS: Structure for table DRAT
*  PT_DRAZ =  "Additional Files
*  PT_DRAP =  "Status Log
*  PT_DRAD =  "Object Links
*  PT_KPRO =  "Originals in DMS
*  PT_TOAV0 =  "SAP ArchiveLink: Link table
.



IMPORTING Parameters details for CV200_DB_DOC_UPDATE

PF_TACODE - Transaction Code

Data type: SY-TCODE
Optional: No
Call by Reference: No ( called with pass by value option)

PF_KPRO_USE - Document Storage via Knowledge Provider

Data type: TDWA-KPRO_USE
Optional: Yes
Call by Reference: No ( called with pass by value option)

PF_API_FLAG - API Indicator

Data type: MCDOK-ACTION
Default: SPACE
Optional: No
Call by Reference: No ( called with pass by value option)

PS_DRAW - Document Info Record

Data type: DRAW
Optional: No
Call by Reference: No ( called with pass by value option)

PS_DRAW_OLD - Document Info Record

Data type: DRAW
Optional: No
Call by Reference: No ( called with pass by value option)

PS_AUDITS - DVS: Indicator Audits

Data type: DMS_AUDITS
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for CV200_DB_DOC_UPDATE

PT_DRAT - DVS: Structure for table DRAT

Data type: DMS_DB_DRAT
Optional: Yes
Call by Reference: No ( called with pass by value option)

PT_DRAZ - Additional Files

Data type: DMS_DB_DRAZ
Optional: Yes
Call by Reference: No ( called with pass by value option)

PT_DRAP - Status Log

Data type: DRAP
Optional: Yes
Call by Reference: No ( called with pass by value option)

PT_DRAD - Object Links

Data type: DMS_DB_DRAD
Optional: Yes
Call by Reference: Yes

PT_KPRO - Originals in DMS

Data type: DMS_TBL_FILE
Optional: Yes
Call by Reference: Yes

PT_TOAV0 - SAP ArchiveLink: Link table

Data type: TOAV0
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for CV200_DB_DOC_UPDATE Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than 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 newer method of declaring data variables on the fly. 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), which i why i have stuck to the origianl for this example.

DATA:
lt_pt_drat  TYPE STANDARD TABLE OF DMS_DB_DRAT, "   
lv_pf_tacode  TYPE SY-TCODE, "   
lt_pt_draz  TYPE STANDARD TABLE OF DMS_DB_DRAZ, "   
lv_pf_kpro_use  TYPE TDWA-KPRO_USE, "   
lt_pt_drap  TYPE STANDARD TABLE OF DRAP, "   
lv_pf_api_flag  TYPE MCDOK-ACTION, "   SPACE
lv_ps_draw  TYPE DRAW, "   
lt_pt_drad  TYPE STANDARD TABLE OF DMS_DB_DRAD, "   
lt_pt_kpro  TYPE STANDARD TABLE OF DMS_TBL_FILE, "   
lv_ps_draw_old  TYPE DRAW, "   
lt_pt_toav0  TYPE STANDARD TABLE OF TOAV0, "   
lv_ps_audits  TYPE DMS_AUDITS. "   

  CALL FUNCTION 'CV200_DB_DOC_UPDATE'  "NOTRANSL: DVS: Daten auf DB schreiben
    EXPORTING
         PF_TACODE = lv_pf_tacode
         PF_KPRO_USE = lv_pf_kpro_use
         PF_API_FLAG = lv_pf_api_flag
         PS_DRAW = lv_ps_draw
         PS_DRAW_OLD = lv_ps_draw_old
         PS_AUDITS = lv_ps_audits
    TABLES
         PT_DRAT = lt_pt_drat
         PT_DRAZ = lt_pt_draz
         PT_DRAP = lt_pt_drap
         PT_DRAD = lt_pt_drad
         PT_KPRO = lt_pt_kpro
         PT_TOAV0 = lt_pt_toav0
. " CV200_DB_DOC_UPDATE




ABAP code using 7.40 inline data declarations to call FM CV200_DB_DOC_UPDATE

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

 
"SELECT single TCODE FROM SY INTO @DATA(ld_pf_tacode).
 
 
"SELECT single KPRO_USE FROM TDWA INTO @DATA(ld_pf_kpro_use).
 
 
"SELECT single ACTION FROM MCDOK INTO @DATA(ld_pf_api_flag).
DATA(ld_pf_api_flag) = ' '.
 
 
 
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!