SAP CV120_DOC_GET_APPLICATION Function Module for NOTRANSL: DVS: Applikationen zu einem Dokument
CV120_DOC_GET_APPLICATION is a standard cv120 doc get application 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: Applikationen zu einem Dokument 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 cv120 doc get application FM, simply by entering the name CV120_DOC_GET_APPLICATION into the relevant SAP transaction such as SE37 or SE38.
Function Group: CV120
Program Name: SAPLCV120
Main Program: SAPLCV120
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CV120_DOC_GET_APPLICATION 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 'CV120_DOC_GET_APPLICATION'"NOTRANSL: DVS: Applikationen zu einem Dokument.
EXPORTING
PF_DOKAR = "Document Type
PF_DOKNR = "Document Number
PF_DOKVR = "Document Version
PF_DOKTL = "Document Part
* PF_APPTP = '1' "Application Type
* PF_HOSTNAME = "Network Address
* PF_CHECK_AL = "
* PS_DRAP_AUDIT = "
IMPORTING
PSX_APPLICATION = "Workstation Applications
PSX_FILE = "
PFX_FCODE = "Function Code
EXCEPTIONS
NOT_FOUND = 1 NO_AUTH = 2 ERROR = 3
IMPORTING Parameters details for CV120_DOC_GET_APPLICATION
PF_DOKAR - Document Type
Data type: DRAW-DOKAROptional: No
Call by Reference: Yes
PF_DOKNR - Document Number
Data type: DRAW-DOKNROptional: No
Call by Reference: Yes
PF_DOKVR - Document Version
Data type: DRAW-DOKVROptional: No
Call by Reference: Yes
PF_DOKTL - Document Part
Data type: DRAW-DOKTLOptional: No
Call by Reference: Yes
PF_APPTP - Application Type
Data type: TDWX-APPTPDefault: '1'
Optional: Yes
Call by Reference: Yes
PF_HOSTNAME - Network Address
Data type: TDWD-NTADROptional: Yes
Call by Reference: Yes
PF_CHECK_AL -
Data type: SY-DATAROptional: Yes
Call by Reference: Yes
PS_DRAP_AUDIT -
Data type: DRAPOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for CV120_DOC_GET_APPLICATION
PSX_APPLICATION - Workstation Applications
Data type: CVAPI_APPLICATIONOptional: No
Call by Reference: Yes
PSX_FILE -
Data type: CVAPI_DOC_FILEOptional: No
Call by Reference: Yes
PFX_FCODE - Function Code
Data type: SYST-UCOMMOptional: No
Call by Reference: Yes
EXCEPTIONS details
NOT_FOUND - Document Does Not Exist
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_AUTH - No Authorization
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ERROR - Errors
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CV120_DOC_GET_APPLICATION 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_pf_dokar | TYPE DRAW-DOKAR, " | |||
| lv_not_found | TYPE DRAW, " | |||
| lv_psx_application | TYPE CVAPI_APPLICATION, " | |||
| lv_no_auth | TYPE CVAPI_APPLICATION, " | |||
| lv_pf_doknr | TYPE DRAW-DOKNR, " | |||
| lv_psx_file | TYPE CVAPI_DOC_FILE, " | |||
| lv_error | TYPE CVAPI_DOC_FILE, " | |||
| lv_pf_dokvr | TYPE DRAW-DOKVR, " | |||
| lv_pfx_fcode | TYPE SYST-UCOMM, " | |||
| lv_pf_doktl | TYPE DRAW-DOKTL, " | |||
| lv_pf_apptp | TYPE TDWX-APPTP, " '1' | |||
| lv_pf_hostname | TYPE TDWD-NTADR, " | |||
| lv_pf_check_al | TYPE SY-DATAR, " | |||
| lv_ps_drap_audit | TYPE DRAP. " |
|   CALL FUNCTION 'CV120_DOC_GET_APPLICATION' "NOTRANSL: DVS: Applikationen zu einem Dokument |
| EXPORTING | ||
| PF_DOKAR | = lv_pf_dokar | |
| PF_DOKNR | = lv_pf_doknr | |
| PF_DOKVR | = lv_pf_dokvr | |
| PF_DOKTL | = lv_pf_doktl | |
| PF_APPTP | = lv_pf_apptp | |
| PF_HOSTNAME | = lv_pf_hostname | |
| PF_CHECK_AL | = lv_pf_check_al | |
| PS_DRAP_AUDIT | = lv_ps_drap_audit | |
| IMPORTING | ||
| PSX_APPLICATION | = lv_psx_application | |
| PSX_FILE | = lv_psx_file | |
| PFX_FCODE | = lv_pfx_fcode | |
| EXCEPTIONS | ||
| NOT_FOUND = 1 | ||
| NO_AUTH = 2 | ||
| ERROR = 3 | ||
| . " CV120_DOC_GET_APPLICATION | ||
ABAP code using 7.40 inline data declarations to call FM CV120_DOC_GET_APPLICATION
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 DOKVR FROM DRAW INTO @DATA(ld_pf_dokvr). | ||||
| "SELECT single UCOMM FROM SYST INTO @DATA(ld_pfx_fcode). | ||||
| "SELECT single DOKTL FROM DRAW INTO @DATA(ld_pf_doktl). | ||||
| "SELECT single APPTP FROM TDWX INTO @DATA(ld_pf_apptp). | ||||
| DATA(ld_pf_apptp) | = '1'. | |||
| "SELECT single NTADR FROM TDWD INTO @DATA(ld_pf_hostname). | ||||
| "SELECT single DATAR FROM SY INTO @DATA(ld_pf_check_al). | ||||
Search for further information about these or an SAP related objects