SAP RH_READ_PERS_ORG_STRU Function Module for









RH_READ_PERS_ORG_STRU is a standard rh read pers org stru 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 read pers org stru FM, simply by entering the name RH_READ_PERS_ORG_STRU into the relevant SAP transaction such as SE37 or SE38.

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



Function RH_READ_PERS_ORG_STRU 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_READ_PERS_ORG_STRU'"
EXPORTING
* BEGDA = '19000101' "Start date of selection period
* ENDDA = '99991231' "End date of selection period
* PERNR = "Personnel number
* IMPORTED_PLVAR = "Plan version
* PLSTE = "Position number
* SPLIT_PLOGISPLIT = 'X' "
* CUT_POSITIONS = ' ' "
* WITH_STRU_AUTH = 'X' "

TABLES
STRU_TAB = "Transfer table

EXCEPTIONS
INTEGRATION_NOT_ACTIVE = 1 PARAMETERS_MISSING = 2
.



IMPORTING Parameters details for RH_READ_PERS_ORG_STRU

BEGDA - Start date of selection period

Data type: P1001-BEGDA
Default: '19000101'
Optional: Yes
Call by Reference: No ( called with pass by value option)

ENDDA - End date of selection period

Data type: P1001-ENDDA
Default: '99991231'
Optional: Yes
Call by Reference: No ( called with pass by value option)

PERNR - Personnel number

Data type: P0000-PERNR
Optional: Yes
Call by Reference: No ( called with pass by value option)

IMPORTED_PLVAR - Plan version

Data type: P1001-PLVAR
Optional: Yes
Call by Reference: No ( called with pass by value option)

PLSTE - Position number

Data type: P1001-OBJID
Optional: Yes
Call by Reference: No ( called with pass by value option)

SPLIT_PLOGISPLIT -

Data type: CHAR1
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

CUT_POSITIONS -

Data type: FLAG
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

WITH_STRU_AUTH -

Data type: BOOLE_D
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for RH_READ_PERS_ORG_STRU

STRU_TAB - Transfer table

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

EXCEPTIONS details

INTEGRATION_NOT_ACTIVE - No integration between PD and PA

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

PARAMETERS_MISSING -

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

Copy and paste ABAP code example for RH_READ_PERS_ORG_STRU 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_begda  TYPE P1001-BEGDA, "   '19000101'
lt_stru_tab  TYPE STANDARD TABLE OF P1001, "   
lv_integration_not_active  TYPE P1001, "   
lv_endda  TYPE P1001-ENDDA, "   '99991231'
lv_parameters_missing  TYPE P1001, "   
lv_pernr  TYPE P0000-PERNR, "   
lv_imported_plvar  TYPE P1001-PLVAR, "   
lv_plste  TYPE P1001-OBJID, "   
lv_split_plogisplit  TYPE CHAR1, "   'X'
lv_cut_positions  TYPE FLAG, "   SPACE
lv_with_stru_auth  TYPE BOOLE_D. "   'X'

  CALL FUNCTION 'RH_READ_PERS_ORG_STRU'  "
    EXPORTING
         BEGDA = lv_begda
         ENDDA = lv_endda
         PERNR = lv_pernr
         IMPORTED_PLVAR = lv_imported_plvar
         PLSTE = lv_plste
         SPLIT_PLOGISPLIT = lv_split_plogisplit
         CUT_POSITIONS = lv_cut_positions
         WITH_STRU_AUTH = lv_with_stru_auth
    TABLES
         STRU_TAB = lt_stru_tab
    EXCEPTIONS
        INTEGRATION_NOT_ACTIVE = 1
        PARAMETERS_MISSING = 2
. " RH_READ_PERS_ORG_STRU




ABAP code using 7.40 inline data declarations to call FM RH_READ_PERS_ORG_STRU

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.

"SELECT single BEGDA FROM P1001 INTO @DATA(ld_begda).
DATA(ld_begda) = '19000101'.
 
 
 
"SELECT single ENDDA FROM P1001 INTO @DATA(ld_endda).
DATA(ld_endda) = '99991231'.
 
 
"SELECT single PERNR FROM P0000 INTO @DATA(ld_pernr).
 
"SELECT single PLVAR FROM P1001 INTO @DATA(ld_imported_plvar).
 
"SELECT single OBJID FROM P1001 INTO @DATA(ld_plste).
 
DATA(ld_split_plogisplit) = 'X'.
 
DATA(ld_cut_positions) = ' '.
 
DATA(ld_with_stru_auth) = 'X'.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!