SAP OXT_OBJECT_TYPE_NAME_CHECK Function Module for
OXT_OBJECT_TYPE_NAME_CHECK is a standard oxt object type 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 object type name check FM, simply by entering the name OXT_OBJECT_TYPE_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_OBJECT_TYPE_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_OBJECT_TYPE_NAME_CHECK'".
EXPORTING
IV_OBJECT_TYPE = "Type of a Generated Object
IV_OBJECT_NAME = "Name of a Generated Object
* IV_SUB1_TYPE = "GOX Object Type
* IV_SUB1_NAME = "Object Name for Generic Object Extension
* IV_SUB2_TYPE = "GOX Object Type
* IV_SUB2_NAME = "Object Name for Generic Object Extension
* IV_RESET_FLAG = 'X' "Reset Flag
* IV_REPOSITORY = ' ' "General Flag
EXCEPTIONS
TECHNICAL_ERROR = 1 ALREADY_EXISTS = 2
IMPORTING Parameters details for OXT_OBJECT_TYPE_NAME_CHECK
IV_OBJECT_TYPE - Type of a Generated Object
Data type: COMT_GOX_OBJECT_TYPEOptional: No
Call by Reference: Yes
IV_OBJECT_NAME - Name of a Generated Object
Data type: COMT_GOX_OBJECT_NAMEOptional: No
Call by Reference: Yes
IV_SUB1_TYPE - GOX Object Type
Data type: COMT_GOX_OBJECT_TYPEOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_SUB1_NAME - Object Name for Generic Object Extension
Data type: COMT_GOX_OBJECT_NAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_SUB2_TYPE - GOX Object Type
Data type: COMT_GOX_OBJECT_TYPEOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_SUB2_NAME - Object Name for Generic Object Extension
Data type: COMT_GOX_OBJECT_NAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_RESET_FLAG - Reset Flag
Data type: OXT_FL_RESETDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_REPOSITORY - General Flag
Data type: OXT_FL_REPOSDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
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_OBJECT_TYPE_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_iv_object_type | TYPE COMT_GOX_OBJECT_TYPE, " | |||
| lv_technical_error | TYPE COMT_GOX_OBJECT_TYPE, " | |||
| lv_already_exists | TYPE COMT_GOX_OBJECT_TYPE, " | |||
| lv_iv_object_name | TYPE COMT_GOX_OBJECT_NAME, " | |||
| lv_iv_sub1_type | TYPE COMT_GOX_OBJECT_TYPE, " | |||
| lv_iv_sub1_name | TYPE COMT_GOX_OBJECT_NAME, " | |||
| lv_iv_sub2_type | TYPE COMT_GOX_OBJECT_TYPE, " | |||
| lv_iv_sub2_name | TYPE COMT_GOX_OBJECT_NAME, " | |||
| lv_iv_reset_flag | TYPE OXT_FL_RESET, " 'X' | |||
| lv_iv_repository | TYPE OXT_FL_REPOS. " ' ' |
|   CALL FUNCTION 'OXT_OBJECT_TYPE_NAME_CHECK' " |
| EXPORTING | ||
| IV_OBJECT_TYPE | = lv_iv_object_type | |
| IV_OBJECT_NAME | = lv_iv_object_name | |
| IV_SUB1_TYPE | = lv_iv_sub1_type | |
| IV_SUB1_NAME | = lv_iv_sub1_name | |
| IV_SUB2_TYPE | = lv_iv_sub2_type | |
| IV_SUB2_NAME | = lv_iv_sub2_name | |
| IV_RESET_FLAG | = lv_iv_reset_flag | |
| IV_REPOSITORY | = lv_iv_repository | |
| EXCEPTIONS | ||
| TECHNICAL_ERROR = 1 | ||
| ALREADY_EXISTS = 2 | ||
| . " OXT_OBJECT_TYPE_NAME_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM OXT_OBJECT_TYPE_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'. | |||
| DATA(ld_iv_repository) | = ' '. | |||
Search for further information about these or an SAP related objects