SAP CV140_LINKS_SCREEN Function Module for NOTRANSL: Anzeigen der Objektverknüpfungen WORKAREA









CV140_LINKS_SCREEN is a standard cv140 links screen 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: Anzeigen der Objektverknüpfungen WORKAREA 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 cv140 links screen FM, simply by entering the name CV140_LINKS_SCREEN into the relevant SAP transaction such as SE37 or SE38.

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



Function CV140_LINKS_SCREEN 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 'CV140_LINKS_SCREEN'"NOTRANSL: Anzeigen der Objektverknüpfungen  WORKAREA
EXPORTING
* PF_INCLUDE_DYNPRO = ' ' "
* PF_FILL_DISPLAY = ' ' "
* PF_CAD_POS = '' "
* PF_PREV_NEXT = "
* PF_PROGRAM_NAME = "
* GF_CHECK_ASSIGN_FB = "Name of Function Module
PF_OPCODE = "
* PF_SUB_SCREEN = ' ' "
* PF_VORSCHLAG_DOKAR = "
PF_DOKOB = "
PF_OBJKY = "
* PF_CHECK_EXIST = ' ' "
* PF_ACTUELL_SHOW = "
* PF_DATUM = SY-DATUM "

IMPORTING
RETURN_CODE = "
VB_FLAG = "
CAD_LEAVE = "

TABLES
* PT_DRAD = "
* PT_DRAD_CHANGE = "
* PT_DRAD_DISPLAY = "Document-Object Link
.



IMPORTING Parameters details for CV140_LINKS_SCREEN

PF_INCLUDE_DYNPRO -

Data type: SY-DYNNR
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

PF_FILL_DISPLAY -

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

PF_CAD_POS -

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

PF_PREV_NEXT -

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

PF_PROGRAM_NAME -

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

GF_CHECK_ASSIGN_FB - Name of Function Module

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

PF_OPCODE -

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

PF_SUB_SCREEN -

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

PF_VORSCHLAG_DOKAR -

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

PF_DOKOB -

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

PF_OBJKY -

Data type: DRAD-OBJKY
Optional: No
Call by Reference: Yes

PF_CHECK_EXIST -

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

PF_ACTUELL_SHOW -

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

PF_DATUM -

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

EXPORTING Parameters details for CV140_LINKS_SCREEN

RETURN_CODE -

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

VB_FLAG -

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

CAD_LEAVE -

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

TABLES Parameters details for CV140_LINKS_SCREEN

PT_DRAD -

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

PT_DRAD_CHANGE -

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

PT_DRAD_DISPLAY - Document-Object Link

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

Copy and paste ABAP code example for CV140_LINKS_SCREEN 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_drad  TYPE STANDARD TABLE OF DRAD, "   
lv_return_code  TYPE C, "   
lv_pf_include_dynpro  TYPE SY-DYNNR, "   ' '
lv_pf_fill_display  TYPE MCDOK-CVHIER, "   ' '
lv_pf_cad_pos  TYPE C, "   ''
lv_pf_prev_next  TYPE MCDOK-CVHIER, "   
lv_pf_program_name  TYPE SY-REPID, "   
lv_gf_check_assign_fb  TYPE RS38L-NAME, "   
lv_vb_flag  TYPE MCDOK-CVHIER, "   
lv_pf_opcode  TYPE MCDOK, "   
lt_pt_drad_change  TYPE STANDARD TABLE OF DRAD, "   
lv_cad_leave  TYPE SY-SUBRC, "   
lv_pf_sub_screen  TYPE MCDOK-CVHIER, "   ' '
lt_pt_drad_display  TYPE STANDARD TABLE OF DRAD, "   
lv_pf_vorschlag_dokar  TYPE DRAD-DOKAR, "   
lv_pf_dokob  TYPE DRAD-DOKOB, "   
lv_pf_objky  TYPE DRAD-OBJKY, "   
lv_pf_check_exist  TYPE MCDOK-CVHIER, "   ' '
lv_pf_actuell_show  TYPE MCDOK-CVHIER, "   
lv_pf_datum  TYPE SY-DATUM. "   SY-DATUM

  CALL FUNCTION 'CV140_LINKS_SCREEN'  "NOTRANSL: Anzeigen der Objektverknüpfungen WORKAREA
    EXPORTING
         PF_INCLUDE_DYNPRO = lv_pf_include_dynpro
         PF_FILL_DISPLAY = lv_pf_fill_display
         PF_CAD_POS = lv_pf_cad_pos
         PF_PREV_NEXT = lv_pf_prev_next
         PF_PROGRAM_NAME = lv_pf_program_name
         GF_CHECK_ASSIGN_FB = lv_gf_check_assign_fb
         PF_OPCODE = lv_pf_opcode
         PF_SUB_SCREEN = lv_pf_sub_screen
         PF_VORSCHLAG_DOKAR = lv_pf_vorschlag_dokar
         PF_DOKOB = lv_pf_dokob
         PF_OBJKY = lv_pf_objky
         PF_CHECK_EXIST = lv_pf_check_exist
         PF_ACTUELL_SHOW = lv_pf_actuell_show
         PF_DATUM = lv_pf_datum
    IMPORTING
         RETURN_CODE = lv_return_code
         VB_FLAG = lv_vb_flag
         CAD_LEAVE = lv_cad_leave
    TABLES
         PT_DRAD = lt_pt_drad
         PT_DRAD_CHANGE = lt_pt_drad_change
         PT_DRAD_DISPLAY = lt_pt_drad_display
. " CV140_LINKS_SCREEN




ABAP code using 7.40 inline data declarations to call FM CV140_LINKS_SCREEN

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 DYNNR FROM SY INTO @DATA(ld_pf_include_dynpro).
DATA(ld_pf_include_dynpro) = ' '.
 
"SELECT single CVHIER FROM MCDOK INTO @DATA(ld_pf_fill_display).
DATA(ld_pf_fill_display) = ' '.
 
DATA(ld_pf_cad_pos) = ''.
 
"SELECT single CVHIER FROM MCDOK INTO @DATA(ld_pf_prev_next).
 
"SELECT single REPID FROM SY INTO @DATA(ld_pf_program_name).
 
"SELECT single NAME FROM RS38L INTO @DATA(ld_gf_check_assign_fb).
 
"SELECT single CVHIER FROM MCDOK INTO @DATA(ld_vb_flag).
 
 
 
"SELECT single SUBRC FROM SY INTO @DATA(ld_cad_leave).
 
"SELECT single CVHIER FROM MCDOK INTO @DATA(ld_pf_sub_screen).
DATA(ld_pf_sub_screen) = ' '.
 
 
"SELECT single DOKAR FROM DRAD INTO @DATA(ld_pf_vorschlag_dokar).
 
"SELECT single DOKOB FROM DRAD INTO @DATA(ld_pf_dokob).
 
"SELECT single OBJKY FROM DRAD INTO @DATA(ld_pf_objky).
 
"SELECT single CVHIER FROM MCDOK INTO @DATA(ld_pf_check_exist).
DATA(ld_pf_check_exist) = ' '.
 
"SELECT single CVHIER FROM MCDOK INTO @DATA(ld_pf_actuell_show).
 
"SELECT single DATUM FROM SY INTO @DATA(ld_pf_datum).
DATA(ld_pf_datum) = SY-DATUM.
 


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!