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

Function RH_CHECK_OBJECT_IS_ORIGINAL 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_CHECK_OBJECT_IS_ORIGINAL'".
EXPORTING
* CLIENT = SY-MANDT "Client
PLVAR = "Plan Version
OTYPE = "Object Type
OBJID = "Object ID
* READ_DIRECTLY = ' ' "Read directly
IMPORTING
ORIGSYSTEM = "Original system of an object
EXCEPTIONS
OTYPE_IS_NOT_RELEVANT = 1 OBJECT_IS_NOT_ORIGINAL = 2 OBJECT_IS_NOT_EXISTING = 3 OBJECT_NOT_REGISTERED = 4 OWN_LOGICAL_SYSTEM_NOT_DEFINED = 5
IMPORTING Parameters details for RH_CHECK_OBJECT_IS_ORIGINAL
CLIENT - Client
Data type: SYMANDTDefault: SY-MANDT
Optional: Yes
Call by Reference: No ( called with pass by value option)
PLVAR - Plan Version
Data type: PLVAROptional: No
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: HROBJIDOptional: No
Call by Reference: No ( called with pass by value option)
READ_DIRECTLY - Read directly
Data type: FLAGDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for RH_CHECK_OBJECT_IS_ORIGINAL
ORIGSYSTEM - Original system of an object
Data type: ORIGSYSTEMOptional: No
Call by Reference: Yes
EXCEPTIONS details
OTYPE_IS_NOT_RELEVANT -
Data type:Optional: No
Call by Reference: Yes
OBJECT_IS_NOT_ORIGINAL -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
OBJECT_IS_NOT_EXISTING - Object Does Not Exist
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
OBJECT_NOT_REGISTERED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
OWN_LOGICAL_SYSTEM_NOT_DEFINED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RH_CHECK_OBJECT_IS_ORIGINAL 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_client | TYPE SYMANDT, " SY-MANDT | |||
| lv_origsystem | TYPE ORIGSYSTEM, " | |||
| lv_otype_is_not_relevant | TYPE ORIGSYSTEM, " | |||
| lv_plvar | TYPE PLVAR, " | |||
| lv_object_is_not_original | TYPE PLVAR, " | |||
| lv_otype | TYPE OTYPE, " | |||
| lv_object_is_not_existing | TYPE OTYPE, " | |||
| lv_objid | TYPE HROBJID, " | |||
| lv_object_not_registered | TYPE HROBJID, " | |||
| lv_read_directly | TYPE FLAG, " SPACE | |||
| lv_own_logical_system_not_defined | TYPE FLAG. " |
|   CALL FUNCTION 'RH_CHECK_OBJECT_IS_ORIGINAL' " |
| EXPORTING | ||
| CLIENT | = lv_client | |
| PLVAR | = lv_plvar | |
| OTYPE | = lv_otype | |
| OBJID | = lv_objid | |
| READ_DIRECTLY | = lv_read_directly | |
| IMPORTING | ||
| ORIGSYSTEM | = lv_origsystem | |
| EXCEPTIONS | ||
| OTYPE_IS_NOT_RELEVANT = 1 | ||
| OBJECT_IS_NOT_ORIGINAL = 2 | ||
| OBJECT_IS_NOT_EXISTING = 3 | ||
| OBJECT_NOT_REGISTERED = 4 | ||
| OWN_LOGICAL_SYSTEM_NOT_DEFINED = 5 | ||
| . " RH_CHECK_OBJECT_IS_ORIGINAL | ||
ABAP code using 7.40 inline data declarations to call FM RH_CHECK_OBJECT_IS_ORIGINAL
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_client) | = SY-MANDT. | |||
| DATA(ld_read_directly) | = ' '. | |||
Search for further information about these or an SAP related objects