SAP CV120_START_APPLICATION Function Module for NOTRANSL: DVS: Applikation starten









CV120_START_APPLICATION is a standard cv120 start 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: Applikation starten 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 start application FM, simply by entering the name CV120_START_APPLICATION into the relevant SAP transaction such as SE37 or SE38.

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



Function CV120_START_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_START_APPLICATION'"NOTRANSL: DVS: Applikation starten
EXPORTING
* PF_API_MODE = "
PF_DAPPL = "
* PF_APPTP = '1' "
PF_FILE = "File Name
* PF_CHECK_FILE = ' ' "
* PS_DRAW = "Document Data
* PF_APPNR = ' ' "
* PF_URL = ' ' "URL
* PS_FRONTEND = "

TABLES
* PT_DRAZ = "Additional Files
* PT_COMPONENTS = "Components

EXCEPTIONS
ERROR = 1 FILE_NOT_FOUND = 2
.



IMPORTING Parameters details for CV120_START_APPLICATION

PF_API_MODE -

Data type: MCDOK-ACTION
Optional: Yes
Call by Reference: Yes

PF_DAPPL -

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

PF_APPTP -

Data type: TDWX-APPTP
Default: '1'
Optional: Yes
Call by Reference: No ( called with pass by value option)

PF_FILE - File Name

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

PF_CHECK_FILE -

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

PS_DRAW - Document Data

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

PF_APPNR -

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

PF_URL - URL

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

PS_FRONTEND -

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

TABLES Parameters details for CV120_START_APPLICATION

PT_DRAZ - Additional Files

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

PT_COMPONENTS - Components

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

EXCEPTIONS details

ERROR - Errors

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

FILE_NOT_FOUND - File does not exist

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

Copy and paste ABAP code example for CV120_START_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_error  TYPE STRING, "   
lt_pt_draz  TYPE STANDARD TABLE OF DRAZ, "   
lv_pf_api_mode  TYPE MCDOK-ACTION, "   
lv_pf_dappl  TYPE DRAW-DAPPL, "   
lt_pt_components  TYPE STANDARD TABLE OF DMS_TBL_COMP, "   
lv_file_not_found  TYPE DMS_TBL_COMP, "   
lv_pf_apptp  TYPE TDWX-APPTP, "   '1'
lv_pf_file  TYPE C, "   
lv_pf_check_file  TYPE C, "   SPACE
lv_ps_draw  TYPE DRAW, "   
lv_pf_appnr  TYPE C, "   SPACE
lv_pf_url  TYPE MCDOK-URL, "   SPACE
lv_ps_frontend  TYPE DMS_FRONTEND_DATA. "   

  CALL FUNCTION 'CV120_START_APPLICATION'  "NOTRANSL: DVS: Applikation starten
    EXPORTING
         PF_API_MODE = lv_pf_api_mode
         PF_DAPPL = lv_pf_dappl
         PF_APPTP = lv_pf_apptp
         PF_FILE = lv_pf_file
         PF_CHECK_FILE = lv_pf_check_file
         PS_DRAW = lv_ps_draw
         PF_APPNR = lv_pf_appnr
         PF_URL = lv_pf_url
         PS_FRONTEND = lv_ps_frontend
    TABLES
         PT_DRAZ = lt_pt_draz
         PT_COMPONENTS = lt_pt_components
    EXCEPTIONS
        ERROR = 1
        FILE_NOT_FOUND = 2
. " CV120_START_APPLICATION




ABAP code using 7.40 inline data declarations to call FM CV120_START_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 ACTION FROM MCDOK INTO @DATA(ld_pf_api_mode).
 
"SELECT single DAPPL FROM DRAW INTO @DATA(ld_pf_dappl).
 
 
 
"SELECT single APPTP FROM TDWX INTO @DATA(ld_pf_apptp).
DATA(ld_pf_apptp) = '1'.
 
 
DATA(ld_pf_check_file) = ' '.
 
 
DATA(ld_pf_appnr) = ' '.
 
"SELECT single URL FROM MCDOK INTO @DATA(ld_pf_url).
DATA(ld_pf_url) = ' '.
 
 


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!