SAP CUA_PFKEY_GET Function Module for Determine GUI F keys and place in table









CUA_PFKEY_GET is a standard cua pfkey get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Determine GUI F keys and place in table 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 cua pfkey get FM, simply by entering the name CUA_PFKEY_GET into the relevant SAP transaction such as SE37 or SE38.

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



Function CUA_PFKEY_GET 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 'CUA_PFKEY_GET'"Determine GUI F keys and place in table
EXPORTING
LANGU = "
PROGRAM = "
* STATUS = '*' "

TABLES
CUA_PFKEY = "

EXCEPTIONS
CUA_NOT_FOUND = 1 STATUS_NOT_FOUND = 2
.



IMPORTING Parameters details for CUA_PFKEY_GET

LANGU -

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

PROGRAM -

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

STATUS -

Data type: RSDCC-STATUS
Default: '*'
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for CUA_PFKEY_GET

CUA_PFKEY -

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

EXCEPTIONS details

CUA_NOT_FOUND -

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

STATUS_NOT_FOUND -

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

Copy and paste ABAP code example for CUA_PFKEY_GET 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_langu  TYPE SY-LANGU, "   
lt_cua_pfkey  TYPE STANDARD TABLE OF RSDCB, "   
lv_cua_not_found  TYPE RSDCB, "   
lv_program  TYPE TSTC-PGMNA, "   
lv_status_not_found  TYPE TSTC, "   
lv_status  TYPE RSDCC-STATUS. "   '*'

  CALL FUNCTION 'CUA_PFKEY_GET'  "Determine GUI F keys and place in table
    EXPORTING
         LANGU = lv_langu
         PROGRAM = lv_program
         STATUS = lv_status
    TABLES
         CUA_PFKEY = lt_cua_pfkey
    EXCEPTIONS
        CUA_NOT_FOUND = 1
        STATUS_NOT_FOUND = 2
. " CUA_PFKEY_GET




ABAP code using 7.40 inline data declarations to call FM CUA_PFKEY_GET

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 LANGU FROM SY INTO @DATA(ld_langu).
 
 
 
"SELECT single PGMNA FROM TSTC INTO @DATA(ld_program).
 
 
"SELECT single STATUS FROM RSDCC INTO @DATA(ld_status).
DATA(ld_status) = '*'.
 


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!