SAP OXT_TABLE_KEY_NAME_CHECK Function Module for
OXT_TABLE_KEY_NAME_CHECK is a standard oxt table key name 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 oxt table key name check FM, simply by entering the name OXT_TABLE_KEY_NAME_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: OXT_TASK_API
Program Name: SAPLOXT_TASK_API
Main Program: SAPLOXT_TASK_API
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function OXT_TABLE_KEY_NAME_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 'OXT_TABLE_KEY_NAME_CHECK'".
EXPORTING
IV_TABLE_NAME = "Table Name
IV_TABKEY = "Parameter Value
* IV_RESET_FLAG = 'X' "Reset Flag
IMPORTING
EV_OCCURENCES = "
EXCEPTIONS
TECHNICAL_ERROR = 1 ALREADY_EXISTS = 2
IMPORTING Parameters details for OXT_TABLE_KEY_NAME_CHECK
IV_TABLE_NAME - Table Name
Data type: TABNAMEOptional: No
Call by Reference: Yes
IV_TABKEY - Parameter Value
Data type: OXT_PARAMVALUEOptional: No
Call by Reference: Yes
IV_RESET_FLAG - Reset Flag
Data type: OXT_FL_RESETDefault: 'X'
Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for OXT_TABLE_KEY_NAME_CHECK
EV_OCCURENCES -
Data type: IOptional: No
Call by Reference: Yes
EXCEPTIONS details
TECHNICAL_ERROR - Technical error
Data type:Optional: No
Call by Reference: Yes
ALREADY_EXISTS - already exists
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for OXT_TABLE_KEY_NAME_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.| DATA: | ||||
| lv_ev_occurences | TYPE I, " | |||
| lv_iv_table_name | TYPE TABNAME, " | |||
| lv_technical_error | TYPE TABNAME, " | |||
| lv_iv_tabkey | TYPE OXT_PARAMVALUE, " | |||
| lv_already_exists | TYPE OXT_PARAMVALUE, " | |||
| lv_iv_reset_flag | TYPE OXT_FL_RESET. " 'X' |
|   CALL FUNCTION 'OXT_TABLE_KEY_NAME_CHECK' " |
| EXPORTING | ||
| IV_TABLE_NAME | = lv_iv_table_name | |
| IV_TABKEY | = lv_iv_tabkey | |
| IV_RESET_FLAG | = lv_iv_reset_flag | |
| IMPORTING | ||
| EV_OCCURENCES | = lv_ev_occurences | |
| EXCEPTIONS | ||
| TECHNICAL_ERROR = 1 | ||
| ALREADY_EXISTS = 2 | ||
| . " OXT_TABLE_KEY_NAME_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM OXT_TABLE_KEY_NAME_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.| DATA(ld_iv_reset_flag) | = 'X'. | |||
Search for further information about these or an SAP related objects