SAP RH_PM_OBJID_CHECK_INTEGRATION Function Module for

Search SAP Function Modules

RH_PM_OBJID_CHECK_INTEGRATION is a standard rh pm objid check integration 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 pm objid check integration FM, simply by entering the name RH_PM_OBJID_CHECK_INTEGRATION into the relevant SAP transaction such as SE37 or SE38.

Function Group: RHBY_2
Program Name: SAPLRHBY_2
Main Program: SAPLRHBY_2
Appliation area: H
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RH_PM_OBJID_CHECK_INTEGRATION 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_PM_OBJID_CHECK_INTEGRATION'"
  EXPORTING
*  PD_PLVAR =  "
*  PD_OTYPE = 'P ' "
   PD_OBJID =  "
*  PD_ISTAT = '1' "
   PD_BEGDA =  "
   PD_ENDDA =  "
*  PD_CHECK_ONLY_NEW_INTEG = 'X' "
*  IV_CHECK_PBC_INTEGRATION = 'X' "

TABLES
   PT_INTEGRATION_TIMES =  "

EXCEPTIONS
   FIKRS_NOT_FOUND = 1    PLVAR_MISSING = 2    WRONG_OTYPE = 3    INCONSISTENT_INTEGRATION = 4 

.

IMPORTING Parameters details for RH_PM_OBJID_CHECK_INTEGRATION

PD_PLVAR -

Data type: P1000-PLVAR
Optional: Yes
Call by Reference: Yes

PD_OTYPE -

Data type: P1000-OTYPE
Default: 'P '
Optional: Yes
Call by Reference: Yes

PD_OBJID -

Data type: P1000-OBJID
Optional: No
Call by Reference: Yes

PD_ISTAT -

Data type: P1000-ISTAT
Default: '1'
Optional: Yes
Call by Reference: Yes

PD_BEGDA -

Data type: P1000-BEGDA
Optional: No
Call by Reference: Yes

PD_ENDDA -

Data type: P1000-ENDDA
Optional: No
Call by Reference: Yes

PD_CHECK_ONLY_NEW_INTEG -

Data type: SY-BINPT
Default: 'X'
Optional: Yes
Call by Reference: Yes

IV_CHECK_PBC_INTEGRATION -

Data type: FLAG
Default: 'X'
Optional: Yes
Call by Reference: Yes

TABLES Parameters details for RH_PM_OBJID_CHECK_INTEGRATION

PT_INTEGRATION_TIMES -

Data type: HRFPM_INTEGRATION_TIMES
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

FIKRS_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

PLVAR_MISSING -

Data type:
Optional: No
Call by Reference: Yes

WRONG_OTYPE -

Data type:
Optional: No
Call by Reference: Yes

INCONSISTENT_INTEGRATION -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for RH_PM_OBJID_CHECK_INTEGRATION 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.

ABAP code using 7.40 inline data declarations to call FM RH_PM_OBJID_CHECK_INTEGRATION

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.

Search for further information about these or an SAP related objects