SAP CV110_DOC_CREATE Function Module for NOTRANSL: DVS: Dokumentdaten anlegen









CV110_DOC_CREATE is a standard cv110 doc create 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: Dokumentdaten anlegen 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 cv110 doc create FM, simply by entering the name CV110_DOC_CREATE into the relevant SAP transaction such as SE37 or SE38.

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



Function CV110_DOC_CREATE 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 'CV110_DOC_CREATE'"NOTRANSL: DVS: Dokumentdaten anlegen
EXPORTING
* PS_API_CONTROL = "Checkbox
PF_DOKAR = "
PF_DOKNR = "
PF_DOKTL = "
PF_DOKVR = "
* PS_DRAW = "

IMPORTING
PSX_DRAW = "

TABLES
* PT_DRAT_X = "Descriptions
* PT_DRAD_X = "Object links
* PT_FILES_X = "Originals
* PT_COMP_X = "Components

EXCEPTIONS
EXISTS = 1 NO_AUTH = 2 ERROR = 3 LOCKED = 4
.




Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLCV110_001 Does the customer include exist?
EXIT_SAPLCV110_002 Transfer data to the customer enhancement
EXIT_SAPLCV110_003 Transfer data from the customer enhancement
EXIT_SAPLCV110_004 Transfer/assign values OK-CODE to the customer enhancement

IMPORTING Parameters details for CV110_DOC_CREATE

PS_API_CONTROL - Checkbox

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

PF_DOKAR -

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

PF_DOKNR -

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

PF_DOKTL -

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

PF_DOKVR -

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

PS_DRAW -

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

EXPORTING Parameters details for CV110_DOC_CREATE

PSX_DRAW -

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

TABLES Parameters details for CV110_DOC_CREATE

PT_DRAT_X - Descriptions

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

PT_DRAD_X - Object links

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

PT_FILES_X - Originals

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

PT_COMP_X - Components

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

EXCEPTIONS details

EXISTS - Document Already Exists

Data type:
Optional: No
Call by Reference: Yes

NO_AUTH - No Authorization

Data type:
Optional: No
Call by Reference: Yes

ERROR - General Error

Data type:
Optional: No
Call by Reference: Yes

LOCKED - Document Locked

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CV110_DOC_CREATE 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:
lv_exists  TYPE STRING, "   
lv_psx_draw  TYPE DRAW, "   
lt_pt_drat_x  TYPE STANDARD TABLE OF DMS_DB_DRAT, "   
lv_ps_api_control  TYPE CVAPI_API_CONTROL, "   
lv_no_auth  TYPE CVAPI_API_CONTROL, "   
lv_pf_dokar  TYPE DRAW-DOKAR, "   
lt_pt_drad_x  TYPE STANDARD TABLE OF DMS_DB_DRAD, "   
lv_error  TYPE DMS_DB_DRAD, "   
lv_pf_doknr  TYPE DRAW-DOKNR, "   
lt_pt_files_x  TYPE STANDARD TABLE OF CVAPI_DOC_FILE, "   
lv_locked  TYPE CVAPI_DOC_FILE, "   
lv_pf_doktl  TYPE DRAW-DOKTL, "   
lt_pt_comp_x  TYPE STANDARD TABLE OF CVAPI_DOC_COMP, "   
lv_pf_dokvr  TYPE DRAW-DOKVR, "   
lv_ps_draw  TYPE DRAW. "   

  CALL FUNCTION 'CV110_DOC_CREATE'  "NOTRANSL: DVS: Dokumentdaten anlegen
    EXPORTING
         PS_API_CONTROL = lv_ps_api_control
         PF_DOKAR = lv_pf_dokar
         PF_DOKNR = lv_pf_doknr
         PF_DOKTL = lv_pf_doktl
         PF_DOKVR = lv_pf_dokvr
         PS_DRAW = lv_ps_draw
    IMPORTING
         PSX_DRAW = lv_psx_draw
    TABLES
         PT_DRAT_X = lt_pt_drat_x
         PT_DRAD_X = lt_pt_drad_x
         PT_FILES_X = lt_pt_files_x
         PT_COMP_X = lt_pt_comp_x
    EXCEPTIONS
        EXISTS = 1
        NO_AUTH = 2
        ERROR = 3
        LOCKED = 4
. " CV110_DOC_CREATE




ABAP code using 7.40 inline data declarations to call FM CV110_DOC_CREATE

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 DOKAR FROM DRAW INTO @DATA(ld_pf_dokar).
 
 
 
"SELECT single DOKNR FROM DRAW INTO @DATA(ld_pf_doknr).
 
 
 
"SELECT single DOKTL FROM DRAW INTO @DATA(ld_pf_doktl).
 
 
"SELECT single DOKVR FROM DRAW INTO @DATA(ld_pf_dokvr).
 
 


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!