SAP Function Modules
CV110_DOC_DIALOG SAP Function module
CV110_DOC_DIALOG 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 CV110_DOC_DIALOG into the relevant SAP transaction such as SE37 or SE80.
Associated Function Group:
CV110
Released Date:
Not Released
Processing type: Normal fucntion module
Pattern for FM CV110_DOC_DIALOG - CV110 DOC DIALOG
CALL FUNCTION 'CV110_DOC_DIALOG' "
EXPORTING
* pf_skip_first = 'X' " c Skip first screen
pf_transaction = " syst-tcode Transaction
* pf_commit = SPACE " c Commit Indicator
pf_dokar = " draw-dokar Document Type
pf_doknr = " draw-doknr Document Number
pf_dokvr = " draw-dokvr Document Version
pf_doktl = " draw-doktl Document Part
* ps_draw = " draw
* ps_api_control = " cvapi_api_control
* pf_no_change_trans_fld = SPACE " c
* pf_not_dequeue_all = SPACE " c Do not cancel all blocks
* pf_no_change = SPACE " c
* pf_no_create = SPACE " c
IMPORTING
psx_draw = " draw
pfx_update_flag = " c Document Has Been Changed
* TABLES
* pt_drat_x = " dms_db_drat
* pt_drad_x = " dms_db_drad
* pt_files_x = " cvapi_doc_file
* pt_comp_x = " cvapi_doc_comp
EXCEPTIONS
NOT_FOUND = 1 " Document Does Not Exist
NO_AUTH = 2 " No Authorization
LOCKED = 3 " Document Locked
ERROR = 4 " General Error
. " CV110_DOC_DIALOG
ABAP code example for Function Module CV110_DOC_DIALOG
The ABAP code below is a full code listing to execute function module CV110_DOC_DIALOG 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).
| ld_psx_draw | TYPE DRAW , |
| ld_pfx_update_flag | TYPE C , |
| it_pt_drat_x | TYPE STANDARD TABLE OF DMS_DB_DRAT,"TABLES PARAM |
| wa_pt_drat_x | LIKE LINE OF it_pt_drat_x , |
| it_pt_drad_x | TYPE STANDARD TABLE OF DMS_DB_DRAD,"TABLES PARAM |
| wa_pt_drad_x | LIKE LINE OF it_pt_drad_x , |
| it_pt_files_x | TYPE STANDARD TABLE OF CVAPI_DOC_FILE,"TABLES PARAM |
| wa_pt_files_x | LIKE LINE OF it_pt_files_x , |
| it_pt_comp_x | TYPE STANDARD TABLE OF CVAPI_DOC_COMP,"TABLES PARAM |
| wa_pt_comp_x | LIKE LINE OF it_pt_comp_x . |
DATA(ld_pf_skip_first) = 'Check type of data required'.
DATA(ld_pf_transaction) = some text here
DATA(ld_pf_commit) = 'Check type of data required'.
SELECT single DOKAR
FROM DRAW
INTO @DATA(ld_pf_dokar).
SELECT single DOKNR
FROM DRAW
INTO @DATA(ld_pf_doknr).
SELECT single DOKVR
FROM DRAW
INTO @DATA(ld_pf_dokvr).
SELECT single DOKTL
FROM DRAW
INTO @DATA(ld_pf_doktl).
DATA(ld_ps_draw) = 'Check type of data required'.
DATA(ld_ps_api_control) = 'Check type of data required'.
DATA(ld_pf_no_change_trans_fld) = 'Check type of data required'.
DATA(ld_pf_not_dequeue_all) = 'Check type of data required'.
DATA(ld_pf_no_change) = 'Check type of data required'.
DATA(ld_pf_no_create) = 'Check type of data required'.
"populate fields of struture and append to itab
append wa_pt_drat_x to it_pt_drat_x.
"populate fields of struture and append to itab
append wa_pt_drad_x to it_pt_drad_x.
"populate fields of struture and append to itab
append wa_pt_files_x to it_pt_files_x.
"populate fields of struture and append to itab
append wa_pt_comp_x to it_pt_comp_x. . CALL FUNCTION 'CV110_DOC_DIALOG' EXPORTING * pf_skip_first = ld_pf_skip_first pf_transaction = ld_pf_transaction * pf_commit = ld_pf_commit pf_dokar = ld_pf_dokar pf_doknr = ld_pf_doknr pf_dokvr = ld_pf_dokvr pf_doktl = ld_pf_doktl * ps_draw = ld_ps_draw * ps_api_control = ld_ps_api_control * pf_no_change_trans_fld = ld_pf_no_change_trans_fld * pf_not_dequeue_all = ld_pf_not_dequeue_all * pf_no_change = ld_pf_no_change * pf_no_create = ld_pf_no_create IMPORTING psx_draw = ld_psx_draw pfx_update_flag = ld_pfx_update_flag * TABLES * pt_drat_x = it_pt_drat_x * pt_drad_x = it_pt_drad_x * pt_files_x = it_pt_files_x * pt_comp_x = it_pt_comp_x EXCEPTIONS NOT_FOUND = 1 NO_AUTH = 2 LOCKED = 3 ERROR = 4 . " CV110_DOC_DIALOG
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 ELSEIF SY-SUBRC EQ 4. "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_psx_draw | TYPE DRAW , |
| ld_pf_skip_first | TYPE C , |
| it_pt_drat_x | TYPE STANDARD TABLE OF DMS_DB_DRAT , |
| wa_pt_drat_x | LIKE LINE OF it_pt_drat_x, |
| ld_pfx_update_flag | TYPE C , |
| ld_pf_transaction | TYPE SYST-TCODE , |
| it_pt_drad_x | TYPE STANDARD TABLE OF DMS_DB_DRAD , |
| wa_pt_drad_x | LIKE LINE OF it_pt_drad_x, |
| ld_pf_commit | TYPE C , |
| it_pt_files_x | TYPE STANDARD TABLE OF CVAPI_DOC_FILE , |
| wa_pt_files_x | LIKE LINE OF it_pt_files_x, |
| ld_pf_dokar | TYPE DRAW-DOKAR , |
| it_pt_comp_x | TYPE STANDARD TABLE OF CVAPI_DOC_COMP , |
| wa_pt_comp_x | LIKE LINE OF it_pt_comp_x, |
| ld_pf_doknr | TYPE DRAW-DOKNR , |
| ld_pf_dokvr | TYPE DRAW-DOKVR , |
| ld_pf_doktl | TYPE DRAW-DOKTL , |
| ld_ps_draw | TYPE DRAW , |
| ld_ps_api_control | TYPE CVAPI_API_CONTROL , |
| ld_pf_no_change_trans_fld | TYPE C , |
| ld_pf_not_dequeue_all | TYPE C , |
| ld_pf_no_change | TYPE C , |
| ld_pf_no_create | TYPE C . |
ld_pf_skip_first = 'Check type of data required'.
"populate fields of struture and append to itab
append wa_pt_drat_x to it_pt_drat_x.
ld_pf_transaction = some text here
"populate fields of struture and append to itab
append wa_pt_drad_x to it_pt_drad_x.
ld_pf_commit = 'Check type of data required'.
"populate fields of struture and append to itab
append wa_pt_files_x to it_pt_files_x.
SELECT single DOKAR
FROM DRAW
INTO ld_pf_dokar.
"populate fields of struture and append to itab
append wa_pt_comp_x to it_pt_comp_x.
SELECT single DOKNR
FROM DRAW
INTO ld_pf_doknr.
SELECT single DOKVR
FROM DRAW
INTO ld_pf_dokvr.
SELECT single DOKTL
FROM DRAW
INTO ld_pf_doktl.
ld_ps_draw = 'Check type of data required'.
ld_ps_api_control = 'Check type of data required'.
ld_pf_no_change_trans_fld = 'Check type of data required'.
ld_pf_not_dequeue_all = 'Check type of data required'.
ld_pf_no_change = 'Check type of data required'.
ld_pf_no_create = 'Check type of data required'.
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 CV110_DOC_DIALOG or its description.