SAP RHOM_READ_RELAT_BUFFERED Function Module for Read Relationships









RHOM_READ_RELAT_BUFFERED is a standard rhom read relat buffered SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read Relationships processing and below is the pattern details for this FM, 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 rhom read relat buffered FM, simply by entering the name RHOM_READ_RELAT_BUFFERED into the relevant SAP transaction such as SE37 or SE38.

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



Function RHOM_READ_RELAT_BUFFERED 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 'RHOM_READ_RELAT_BUFFERED'"Read Relationships
  EXPORTING
*  OTYPE =  "
*  BUFFER_MODE = 'X' "
*  OBJID =  "
*  PLVAR =  "
*  SUBTY =  "
*  ISTAT =  "
*  BEGDA = '19000101' "
*  ENDDA = '99991231' "
*  AUTH_FCODE = 'DISP' "
*  WITH_STRU_AUTH = 'X' "

TABLES
*  OBJECTS =  "
*  I1001 =  "

EXCEPTIONS
   NO_ACTIVE_PLVAR = 1
.



IMPORTING Parameters details for RHOM_READ_RELAT_BUFFERED

OTYPE -

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

BUFFER_MODE -

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

OBJID -

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

PLVAR -

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

SUBTY -

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

ISTAT -

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

BEGDA -

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

ENDDA -

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

AUTH_FCODE -

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

WITH_STRU_AUTH -

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

TABLES Parameters details for RHOM_READ_RELAT_BUFFERED

OBJECTS -

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

I1001 -

Data type: HRI1001
Optional: 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)

Copy and paste ABAP code example for RHOM_READ_RELAT_BUFFERED 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_otype  TYPE OTYPE, "   
lt_objects  TYPE STANDARD TABLE OF HRROOTOB, "   
lv_no_active_plvar  TYPE HRROOTOB, "   
lv_buffer_mode  TYPE FLAG, "   'X'
lt_i1001  TYPE STANDARD TABLE OF HRI1001, "   
lv_objid  TYPE HRI1001, "   
lv_plvar  TYPE PLVAR, "   
lv_subty  TYPE PLVAR, "   
lv_istat  TYPE ISTAT_D, "   
lv_begda  TYPE BEGDATUM, "   '19000101'
lv_endda  TYPE ENDDATUM, "   '99991231'
lv_auth_fcode  TYPE FCODE, "   'DISP'
lv_with_stru_auth  TYPE FLAG. "   'X'

  CALL FUNCTION 'RHOM_READ_RELAT_BUFFERED'  "Read Relationships
    EXPORTING
         OTYPE = lv_otype
         BUFFER_MODE = lv_buffer_mode
         OBJID = lv_objid
         PLVAR = lv_plvar
         SUBTY = lv_subty
         ISTAT = lv_istat
         BEGDA = lv_begda
         ENDDA = lv_endda
         AUTH_FCODE = lv_auth_fcode
         WITH_STRU_AUTH = lv_with_stru_auth
    TABLES
         OBJECTS = lt_objects
         I1001 = lt_i1001
    EXCEPTIONS
        NO_ACTIVE_PLVAR = 1
. " RHOM_READ_RELAT_BUFFERED




ABAP code using 7.40 inline data declarations to call FM RHOM_READ_RELAT_BUFFERED

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_buffer_mode) = 'X'.
 
 
 
 
 
 
DATA(ld_begda) = '19000101'.
 
DATA(ld_endda) = '99991231'.
 
DATA(ld_auth_fcode) = 'DISP'.
 
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!