SAP RH_OM_ATTRIBUTES_VALUE_CHECK Function Module for
RH_OM_ATTRIBUTES_VALUE_CHECK is a standard rh om attributes value 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 rh om attributes value check FM, simply by entering the name RH_OM_ATTRIBUTES_VALUE_CHECK 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_ATTRIBUTES_VALUE_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 'RH_OM_ATTRIBUTES_VALUE_CHECK'".
EXPORTING
* PLVAR = "Plan Version
OTYPE = "Object Type
OBJID = "Object ID
SCENARIO = "General Attribute Maintenance: Scenario
* SELDATE = SY-DATUM "Key Date
* BUFFER_REFRESH = "
* LOG_MODE = "
* APPEND_LOG = "
* ACTI_CHECK = ' ' "
IMPORTING
ERRORLEVEL = "
CHANGING
* LOGHANDLE = "
TABLES
* USE_TAB = "
EXCEPTIONS
NO_ACTIVE_PLVAR = 1 NO_ATTRIBUTES = 2 NO_VALUES = 3 VALUE_ERROR = 4 LOG_ERROR = 5
IMPORTING Parameters details for RH_OM_ATTRIBUTES_VALUE_CHECK
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 - Object ID
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SCENARIO - General Attribute Maintenance: Scenario
Data type: OM_ATTRSCNOptional: No
Call by Reference: No ( called with pass by value option)
SELDATE - Key Date
Data type: OMSELDATEDefault: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)
BUFFER_REFRESH -
Data type: FLAGOptional: Yes
Call by Reference: No ( called with pass by value option)
LOG_MODE -
Data type: FLAGOptional: Yes
Call by Reference: No ( called with pass by value option)
APPEND_LOG -
Data type: FLAGOptional: Yes
Call by Reference: No ( called with pass by value option)
ACTI_CHECK -
Data type: FLAGDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for RH_OM_ATTRIBUTES_VALUE_CHECK
ERRORLEVEL -
Data type: OM_ATTCONSOptional: No
Call by Reference: Yes
CHANGING Parameters details for RH_OM_ATTRIBUTES_VALUE_CHECK
LOGHANDLE -
Data type: BALLOGHNDLOptional: Yes
Call by Reference: Yes
TABLES Parameters details for RH_OM_ATTRIBUTES_VALUE_CHECK
USE_TAB -
Data type: OMATTVALRTOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_ACTIVE_PLVAR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_ATTRIBUTES -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_VALUES -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
VALUE_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
LOG_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RH_OM_ATTRIBUTES_VALUE_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_plvar | TYPE PLVAR, " | |||
| lt_use_tab | TYPE STANDARD TABLE OF OMATTVALRT, " | |||
| lv_loghandle | TYPE BALLOGHNDL, " | |||
| lv_errorlevel | TYPE OM_ATTCONS, " | |||
| lv_no_active_plvar | TYPE OM_ATTCONS, " | |||
| lv_otype | TYPE OTYPE, " | |||
| lv_no_attributes | TYPE OTYPE, " | |||
| lv_objid | TYPE OTYPE, " | |||
| lv_no_values | TYPE OTYPE, " | |||
| lv_scenario | TYPE OM_ATTRSCN, " | |||
| lv_value_error | TYPE OM_ATTRSCN, " | |||
| lv_seldate | TYPE OMSELDATE, " SY-DATUM | |||
| lv_log_error | TYPE OMSELDATE, " | |||
| lv_buffer_refresh | TYPE FLAG, " | |||
| lv_log_mode | TYPE FLAG, " | |||
| lv_append_log | TYPE FLAG, " | |||
| lv_acti_check | TYPE FLAG. " SPACE |
|   CALL FUNCTION 'RH_OM_ATTRIBUTES_VALUE_CHECK' " |
| EXPORTING | ||
| PLVAR | = lv_plvar | |
| OTYPE | = lv_otype | |
| OBJID | = lv_objid | |
| SCENARIO | = lv_scenario | |
| SELDATE | = lv_seldate | |
| BUFFER_REFRESH | = lv_buffer_refresh | |
| LOG_MODE | = lv_log_mode | |
| APPEND_LOG | = lv_append_log | |
| ACTI_CHECK | = lv_acti_check | |
| IMPORTING | ||
| ERRORLEVEL | = lv_errorlevel | |
| CHANGING | ||
| LOGHANDLE | = lv_loghandle | |
| TABLES | ||
| USE_TAB | = lt_use_tab | |
| EXCEPTIONS | ||
| NO_ACTIVE_PLVAR = 1 | ||
| NO_ATTRIBUTES = 2 | ||
| NO_VALUES = 3 | ||
| VALUE_ERROR = 4 | ||
| LOG_ERROR = 5 | ||
| . " RH_OM_ATTRIBUTES_VALUE_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM RH_OM_ATTRIBUTES_VALUE_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_seldate) | = SY-DATUM. | |||
| DATA(ld_acti_check) | = ' '. | |||
Search for further information about these or an SAP related objects