SAP COPA_GET_ERK Function Module for
COPA_GET_ERK is a standard copa get erk 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 copa get erk FM, simply by entering the name COPA_GET_ERK into the relevant SAP transaction such as SE37 or SE38.
Function Group: KEA3
Program Name: SAPLKEA3
Main Program: SAPLKEA3
Appliation area: K
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function COPA_GET_ERK 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 'COPA_GET_ERK'".
EXPORTING
* MODE = 'P' "
IMPORTING
ERKRS = "
PA_TYPE = "
OK_CODE = "
EXCEPTIONS
ERKRS_INACTIVE = 1
IMPORTING Parameters details for COPA_GET_ERK
MODE -
Data type: SY-PFKEYDefault: 'P'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for COPA_GET_ERK
ERKRS -
Data type: TKEB-ERKRSOptional: No
Call by Reference: No ( called with pass by value option)
PA_TYPE -
Data type: CEDDB-PA_TYPEOptional: No
Call by Reference: No ( called with pass by value option)
OK_CODE -
Data type: SY-PFKEYOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ERKRS_INACTIVE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for COPA_GET_ERK 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_mode | TYPE SY-PFKEY, " 'P' | |||
lv_erkrs | TYPE TKEB-ERKRS, " | |||
lv_erkrs_inactive | TYPE TKEB, " | |||
lv_pa_type | TYPE CEDDB-PA_TYPE, " | |||
lv_ok_code | TYPE SY-PFKEY. " |
  CALL FUNCTION 'COPA_GET_ERK' " |
EXPORTING | ||
MODE | = lv_mode | |
IMPORTING | ||
ERKRS | = lv_erkrs | |
PA_TYPE | = lv_pa_type | |
OK_CODE | = lv_ok_code | |
EXCEPTIONS | ||
ERKRS_INACTIVE = 1 | ||
. " COPA_GET_ERK |
ABAP code using 7.40 inline data declarations to call FM COPA_GET_ERK
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 PFKEY FROM SY INTO @DATA(ld_mode). | ||||
DATA(ld_mode) | = 'P'. | |||
"SELECT single ERKRS FROM TKEB INTO @DATA(ld_erkrs). | ||||
"SELECT single PA_TYPE FROM CEDDB INTO @DATA(ld_pa_type). | ||||
"SELECT single PFKEY FROM SY INTO @DATA(ld_ok_code). | ||||
Search for further information about these or an SAP related objects