SAP RH_OM_ATTRIBUTE_CHECK_UNIQUE Function Module for
RH_OM_ATTRIBUTE_CHECK_UNIQUE is a standard rh om attribute check unique 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 rh om attribute check unique FM, simply by entering the name RH_OM_ATTRIBUTE_CHECK_UNIQUE into the relevant SAP transaction such as SE37 or SE38.
Function Group: RHOMATTRIBUTES
Program Name: SAPLRHOMATTRIBUTES
Main Program: SAPLRHOMATTRIBUTES
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RH_OM_ATTRIBUTE_CHECK_UNIQUE 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 'RH_OM_ATTRIBUTE_CHECK_UNIQUE'".
EXPORTING
* PLVAR = "Plan Version
OTYPE = "Object Type
OBJID = "
* SELDATE = SY-DATUM "Field of Type DATS
* SELENDDA = "Field of Type DATS
SUBTY = "Subtype
ATTRIB = "General Attribute Maintenance: Attribute Definition
VALUE = "
IMPORTING
ERROR_OBJECT = "Role Resolution Result
EXCEPTIONS
NO_ACTIVE_PLVAR = 1 NOT_UNIQUE = 2
IMPORTING Parameters details for RH_OM_ATTRIBUTE_CHECK_UNIQUE
PLVAR - Plan Version
Data type: PLVAROptional: Yes
Call by Reference: No ( called with pass by value option)
OTYPE - Object Type
Data type: OTYPEOptional: No
Call by Reference: No ( called with pass by value option)
OBJID -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SELDATE - Field of Type DATS
Data type: DATSDefault: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)
SELENDDA - Field of Type DATS
Data type: DATSOptional: Yes
Call by Reference: No ( called with pass by value option)
SUBTY - Subtype
Data type: SUBTYPOptional: No
Call by Reference: No ( called with pass by value option)
ATTRIB - General Attribute Maintenance: Attribute Definition
Data type: OM_ATTRIBOptional: No
Call by Reference: No ( called with pass by value option)
VALUE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for RH_OM_ATTRIBUTE_CHECK_UNIQUE
ERROR_OBJECT - Role Resolution Result
Data type: SWHACTOROptional: No
Call by Reference: Yes
EXCEPTIONS details
NO_ACTIVE_PLVAR -
Data type:Optional: No
Call by Reference: Yes
NOT_UNIQUE -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for RH_OM_ATTRIBUTE_CHECK_UNIQUE 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_plvar | TYPE PLVAR, " | |||
| lv_error_object | TYPE SWHACTOR, " | |||
| lv_no_active_plvar | TYPE SWHACTOR, " | |||
| lv_otype | TYPE OTYPE, " | |||
| lv_not_unique | TYPE OTYPE, " | |||
| lv_objid | TYPE OTYPE, " | |||
| lv_seldate | TYPE DATS, " SY-DATUM | |||
| lv_selendda | TYPE DATS, " | |||
| lv_subty | TYPE SUBTYP, " | |||
| lv_attrib | TYPE OM_ATTRIB, " | |||
| lv_value | TYPE OM_ATTRIB. " |
|   CALL FUNCTION 'RH_OM_ATTRIBUTE_CHECK_UNIQUE' " |
| EXPORTING | ||
| PLVAR | = lv_plvar | |
| OTYPE | = lv_otype | |
| OBJID | = lv_objid | |
| SELDATE | = lv_seldate | |
| SELENDDA | = lv_selendda | |
| SUBTY | = lv_subty | |
| ATTRIB | = lv_attrib | |
| VALUE | = lv_value | |
| IMPORTING | ||
| ERROR_OBJECT | = lv_error_object | |
| EXCEPTIONS | ||
| NO_ACTIVE_PLVAR = 1 | ||
| NOT_UNIQUE = 2 | ||
| . " RH_OM_ATTRIBUTE_CHECK_UNIQUE | ||
ABAP code using 7.40 inline data declarations to call FM RH_OM_ATTRIBUTE_CHECK_UNIQUE
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_seldate) | = SY-DATUM. | |||
Search for further information about these or an SAP related objects