SAP EHPRC_CP_LB16_LINK_CREATE Function Module for









EHPRC_CP_LB16_LINK_CREATE is a standard ehprc cp lb16 link create SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 ehprc cp lb16 link create FM, simply by entering the name EHPRC_CP_LB16_LINK_CREATE into the relevant SAP transaction such as SE37 or SE38.

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



Function EHPRC_CP_LB16_LINK_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 'EHPRC_CP_LB16_LINK_CREATE'"
EXPORTING
I_SUBID = "
* I_LANGU = "
* IS_GENVAR = "
* IT_LINKOBJECTS = "
* I_FLG_DIALOG_MODE = ESP1_FALSE "
* I_REPSTATUS = 'W6' "Status 'ready'
I_GENVAR = "
I_EHSDOCCAT = "
* I_REQREASON = 'MANUAL' "
I_DOCKEY = "
* I_VALDAT = "
* I_VERSION = "
* I_SUBVERSION = "
* I_REMARK = "

IMPORTING
E_FLG_ERROR = "
ET_MESSAGE = "
ES_API_HEADER = "EHS: API Structure Report Header
.



IMPORTING Parameters details for EHPRC_CP_LB16_LINK_CREATE

I_SUBID -

Data type: ESESUBID
Optional: No
Call by Reference: Yes

I_LANGU -

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

IS_GENVAR -

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

IT_LINKOBJECTS -

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

I_FLG_DIALOG_MODE -

Data type: ESEBOOLE
Default: ESP1_FALSE
Optional: Yes
Call by Reference: Yes

I_REPSTATUS - Status 'ready'

Data type: C
Default: 'W6'
Optional: Yes
Call by Reference: Yes

I_GENVAR -

Data type: EHPRC_LDEPID
Optional: No
Call by Reference: Yes

I_EHSDOCCAT -

Data type: ESEEHDOKAR
Optional: No
Call by Reference: Yes

I_REQREASON -

Data type: ESEREQREAS
Default: 'MANUAL'
Optional: No
Call by Reference: Yes

I_DOCKEY -

Data type: ESEDMSKEY
Optional: No
Call by Reference: Yes

I_VALDAT -

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

I_VERSION -

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

I_SUBVERSION -

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

I_REMARK -

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

EXPORTING Parameters details for EHPRC_CP_LB16_LINK_CREATE

E_FLG_ERROR -

Data type: ESEBOOLE
Optional: No
Call by Reference: Yes

ET_MESSAGE -

Data type: EHPRCT_MESSAGE
Optional: No
Call by Reference: Yes

ES_API_HEADER - EHS: API Structure Report Header

Data type: RCGAPIDH
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for EHPRC_CP_LB16_LINK_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_i_subid  TYPE ESESUBID, "   
lv_e_flg_error  TYPE ESEBOOLE, "   
lv_i_langu  TYPE ESELANGU, "   
lv_is_genvar  TYPE ESTLP, "   
lv_it_linkobjects  TYPE EHPRCT_APPLOBJ, "   
lv_i_flg_dialog_mode  TYPE ESEBOOLE, "   ESP1_FALSE
lv_i_repstatus  TYPE C, "   'W6'
lv_i_genvar  TYPE EHPRC_LDEPID, "   
lv_et_message  TYPE EHPRCT_MESSAGE, "   
lv_i_ehsdoccat  TYPE ESEEHDOKAR, "   
lv_es_api_header  TYPE RCGAPIDH, "   
lv_i_reqreason  TYPE ESEREQREAS, "   'MANUAL'
lv_i_dockey  TYPE ESEDMSKEY, "   
lv_i_valdat  TYPE ESEREPVDAT, "   
lv_i_version  TYPE ESEREPVERS, "   
lv_i_subversion  TYPE ESEREPVERS, "   
lv_i_remark  TYPE ESEREM. "   

  CALL FUNCTION 'EHPRC_CP_LB16_LINK_CREATE'  "
    EXPORTING
         I_SUBID = lv_i_subid
         I_LANGU = lv_i_langu
         IS_GENVAR = lv_is_genvar
         IT_LINKOBJECTS = lv_it_linkobjects
         I_FLG_DIALOG_MODE = lv_i_flg_dialog_mode
         I_REPSTATUS = lv_i_repstatus
         I_GENVAR = lv_i_genvar
         I_EHSDOCCAT = lv_i_ehsdoccat
         I_REQREASON = lv_i_reqreason
         I_DOCKEY = lv_i_dockey
         I_VALDAT = lv_i_valdat
         I_VERSION = lv_i_version
         I_SUBVERSION = lv_i_subversion
         I_REMARK = lv_i_remark
    IMPORTING
         E_FLG_ERROR = lv_e_flg_error
         ET_MESSAGE = lv_et_message
         ES_API_HEADER = lv_es_api_header
. " EHPRC_CP_LB16_LINK_CREATE




ABAP code using 7.40 inline data declarations to call FM EHPRC_CP_LB16_LINK_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.

 
 
 
 
 
DATA(ld_i_flg_dialog_mode) = ESP1_FALSE.
 
DATA(ld_i_repstatus) = 'W6'.
 
 
 
 
 
DATA(ld_i_reqreason) = 'MANUAL'.
 
 
 
 
 
 


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!