SAP RKE_FIELDNAMES_CHECK Function Module for

Search SAP Function Modules

RKE_FIELDNAMES_CHECK is a standard rke fieldnames check 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 rke fieldnames check FM, simply by entering the name RKE_FIELDNAMES_CHECK into the relevant SAP transaction such as SE37 or SE38.

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

Function RKE_FIELDNAMES_CHECK 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 'RKE_FIELDNAMES_CHECK'"
  EXPORTING
   AUSWAHL =  "Type of the COPA field names
   ERKRS =  "Operating Concern
   FNAM =  "COPA field name
*  PA_TYPE = '1' "

 IMPORTING
   SCRTEXT_L =  "
   SCRTEXT_M =  "
   SCRTEXT_S =  "
   E_PLAKZ =  "
   E_AGGTM =  "
   SUBRC =  "EQ 0, if FNAM exists, otherwise GT 0.

EXCEPTIONS
   INV_AUSWAHL = 1    NO_ERKRS_DEFINED = 2 

.

IMPORTING Parameters details for RKE_FIELDNAMES_CHECK

AUSWAHL - Type of the COPA field names

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

ERKRS - Operating Concern

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

FNAM - COPA field name

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

PA_TYPE -

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

EXPORTING Parameters details for RKE_FIELDNAMES_CHECK

SCRTEXT_L -

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

SCRTEXT_M -

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

SCRTEXT_S -

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

E_PLAKZ -

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

E_AGGTM -

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

SUBRC - EQ 0, if FNAM exists, otherwise GT 0.

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

EXCEPTIONS details

INV_AUSWAHL - Invalid selection

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

NO_ERKRS_DEFINED - Financial statement area not available

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

Copy and paste ABAP code example for RKE_FIELDNAMES_CHECK 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.

ABAP code using 7.40 inline data declarations to call FM RKE_FIELDNAMES_CHECK

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.

Search for further information about these or an SAP related objects