SAP J_8A3_CUX_SELECT_KEY Function Module for Model for Customerexit 'KEY'









J_8A3_CUX_SELECT_KEY is a standard j 8a3 cux select key SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Model for Customerexit 'KEY' 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 j 8a3 cux select key FM, simply by entering the name J_8A3_CUX_SELECT_KEY into the relevant SAP transaction such as SE37 or SE38.

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



Function J_8A3_CUX_SELECT_KEY 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 'J_8A3_CUX_SELECT_KEY'"Model for Customerexit 'KEY'
EXPORTING
* KEY = "
METHOD = "
OBJECT = "
* TITLE_DIALOG = ' ' "

IMPORTING
KEY = "
PE_USE_STANDARD = "

CHANGING
* PC_PARAMETERS = "

TABLES
* PT_PARAMETER = "

EXCEPTIONS
EXC_OBJECT_NOT_FOUND = 1 EXC_REQUEST_ERROR = 2 EXC_USER_CANCEL = 3 OTHERS = 4
.



IMPORTING Parameters details for J_8A3_CUX_SELECT_KEY

KEY -

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

METHOD -

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

OBJECT -

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

TITLE_DIALOG -

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

EXPORTING Parameters details for J_8A3_CUX_SELECT_KEY

KEY -

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

PE_USE_STANDARD -

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

CHANGING Parameters details for J_8A3_CUX_SELECT_KEY

PC_PARAMETERS -

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

TABLES Parameters details for J_8A3_CUX_SELECT_KEY

PT_PARAMETER -

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

EXCEPTIONS details

EXC_OBJECT_NOT_FOUND -

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

EXC_REQUEST_ERROR -

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

EXC_USER_CANCEL -

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

OTHERS -

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

Copy and paste ABAP code example for J_8A3_CUX_SELECT_KEY 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_key  TYPE OJINT-KEY, "   
lv_key  TYPE OJINT-KEY, "   
lt_pt_parameter  TYPE STANDARD TABLE OF J_8ASPARM, "   
lv_pc_parameters  TYPE J_8A3S0001, "   
lv_exc_object_not_found  TYPE J_8A3S0001, "   
lv_method  TYPE OJINT-METHOD, "   
lv_pe_use_standard  TYPE C, "   
lv_exc_request_error  TYPE C, "   
lv_object  TYPE OJINT-NAME, "   
lv_exc_user_cancel  TYPE OJINT, "   
lv_others  TYPE OJINT, "   
lv_title_dialog  TYPE OJINT. "   SPACE

  CALL FUNCTION 'J_8A3_CUX_SELECT_KEY'  "Model for Customerexit 'KEY'
    EXPORTING
         KEY = lv_key
         METHOD = lv_method
         OBJECT = lv_object
         TITLE_DIALOG = lv_title_dialog
    IMPORTING
         KEY = lv_key
         PE_USE_STANDARD = lv_pe_use_standard
    CHANGING
         PC_PARAMETERS = lv_pc_parameters
    TABLES
         PT_PARAMETER = lt_pt_parameter
    EXCEPTIONS
        EXC_OBJECT_NOT_FOUND = 1
        EXC_REQUEST_ERROR = 2
        EXC_USER_CANCEL = 3
        OTHERS = 4
. " J_8A3_CUX_SELECT_KEY




ABAP code using 7.40 inline data declarations to call FM J_8A3_CUX_SELECT_KEY

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 KEY FROM OJINT INTO @DATA(ld_key).
 
"SELECT single KEY FROM OJINT INTO @DATA(ld_key).
 
 
 
 
"SELECT single METHOD FROM OJINT INTO @DATA(ld_method).
 
 
 
"SELECT single NAME FROM OJINT INTO @DATA(ld_object).
 
 
 
DATA(ld_title_dialog) = ' '.
 


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!