SAP BAPI_RE_AO_GET_LIST Function Module for Return Data of Multiple Architectural Objects









BAPI_RE_AO_GET_LIST is a standard bapi re ao get list SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Return Data of Multiple Architectural Objects 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 bapi re ao get list FM, simply by entering the name BAPI_RE_AO_GET_LIST into the relevant SAP transaction such as SE37 or SE38.

Function Group: REBD_BAPI_ARCH_OBJECT
Program Name: SAPLREBD_BAPI_ARCH_OBJECT
Main Program: SAPLREBD_BAPI_ARCH_OBJECT
Appliation area:
Release date: 19-Aug-2005
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function BAPI_RE_AO_GET_LIST 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 'BAPI_RE_AO_GET_LIST'"Return Data of Multiple Architectural Objects
  EXPORTING
*  DETAIL_DATA_FROM =  "Date: Detailed Data Valid From
*  DETAIL_DATA_TO =  "Date: Detailed Data Valid To
*  SELECT_X =  "Arch. Object - Fields for Mass Selection
*  MAX_ROWS = 0 "Maximum Number of Lines of Hits

TABLES
   SELOPTION =  "Selection Options
*  ARCH_RELMS =  "Architectural Linkage Object Parts
*  RESUBM_RULE =  "Reminder Rules
*  RESUBM_DATE =  "Reminder Dates
*  STATUS =  "Status
*  EXTENSION_OUT =  "Data of User Fields
*  RETURN =  "Return Parameter(s)
*  INFRASTRUCTURE =  "Infrastructure
*  TEXT =  "Texts/Memos
*  ARCH_OBJECT =  "Architectural Objects
*  OBJECT_ADDRESS =  "Addresses
*  NUMBER_RANGE =  "Number Ranges of Arch. Objects
*  MEASUREMENT =  "Measurements
*  PARTNER =  "Partner
*  CHARACT =  "Fixtures and Fittings Characteristic of RE Object
*  OBJ_ASSIGN =  "Object Assignments
*  ARCH_REL =  "Architectural Linkage Objects
.



IMPORTING Parameters details for BAPI_RE_AO_GET_LIST

DETAIL_DATA_FROM - Date: Detailed Data Valid From

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

DETAIL_DATA_TO - Date: Detailed Data Valid To

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

SELECT_X - Arch. Object - Fields for Mass Selection

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

MAX_ROWS - Maximum Number of Lines of Hits

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

TABLES Parameters details for BAPI_RE_AO_GET_LIST

SELOPTION - Selection Options

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

ARCH_RELMS - Architectural Linkage Object Parts

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

RESUBM_RULE - Reminder Rules

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

RESUBM_DATE - Reminder Dates

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

STATUS - Status

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

EXTENSION_OUT - Data of User Fields

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

RETURN - Return Parameter(s)

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

INFRASTRUCTURE - Infrastructure

Data type: BAPI_RE_INFRA
Optional: Yes
Call by Reference: Yes

TEXT - Texts/Memos

Data type: BAPI_RE_TEXT
Optional: Yes
Call by Reference: Yes

ARCH_OBJECT - Architectural Objects

Data type: BAPI_RE_ARCH_OBJECT
Optional: Yes
Call by Reference: Yes

OBJECT_ADDRESS - Addresses

Data type: BAPI_RE_OBJ_ADDRESS
Optional: Yes
Call by Reference: Yes

NUMBER_RANGE - Number Ranges of Arch. Objects

Data type: BAPI_RE_NUMBER_RANGE
Optional: Yes
Call by Reference: Yes

MEASUREMENT - Measurements

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

PARTNER - Partner

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

CHARACT - Fixtures and Fittings Characteristic of RE Object

Data type: BAPI_RE_CHARACT
Optional: Yes
Call by Reference: Yes

OBJ_ASSIGN - Object Assignments

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

ARCH_REL - Architectural Linkage Objects

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

Copy and paste ABAP code example for BAPI_RE_AO_GET_LIST 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:
lt_seloption  TYPE STANDARD TABLE OF BAPI_RE_SELOPTION, "   
lv_detail_data_from  TYPE BAPI_RE_ADDITIONAL_FIELDS-DETAIL_VALID_FROM, "   
lt_arch_relms  TYPE STANDARD TABLE OF BAPI_RE_ARCH_RELMS, "   
lt_resubm_rule  TYPE STANDARD TABLE OF BAPI_RE_RESUBM_RULE, "   
lt_resubm_date  TYPE STANDARD TABLE OF BAPI_RE_RESUBM_DATE, "   
lt_status  TYPE STANDARD TABLE OF BAPI_RE_STATUS, "   
lt_extension_out  TYPE STANDARD TABLE OF BAPI_RE_IDENT_PAREX, "   
lt_return  TYPE STANDARD TABLE OF BAPIRET2, "   
lt_infrastructure  TYPE STANDARD TABLE OF BAPI_RE_INFRA, "   
lt_text  TYPE STANDARD TABLE OF BAPI_RE_TEXT, "   
lt_arch_object  TYPE STANDARD TABLE OF BAPI_RE_ARCH_OBJECT, "   
lv_detail_data_to  TYPE BAPI_RE_ADDITIONAL_FIELDS-DETAIL_VALID_TO, "   
lv_select_x  TYPE BAPI_RE_ARCH_OBJECT_SELX, "   
lt_object_address  TYPE STANDARD TABLE OF BAPI_RE_OBJ_ADDRESS, "   
lv_max_rows  TYPE BAPI_RE_ADDITIONAL_FIELDS-BAPIMAXROW, "   0
lt_number_range  TYPE STANDARD TABLE OF BAPI_RE_NUMBER_RANGE, "   
lt_measurement  TYPE STANDARD TABLE OF BAPI_RE_MEASUREMENT, "   
lt_partner  TYPE STANDARD TABLE OF BAPI_RE_PARTNER, "   
lt_charact  TYPE STANDARD TABLE OF BAPI_RE_CHARACT, "   
lt_obj_assign  TYPE STANDARD TABLE OF BAPI_RE_OBJ_ASSIGN, "   
lt_arch_rel  TYPE STANDARD TABLE OF BAPI_RE_ARCH_REL. "   

  CALL FUNCTION 'BAPI_RE_AO_GET_LIST'  "Return Data of Multiple Architectural Objects
    EXPORTING
         DETAIL_DATA_FROM = lv_detail_data_from
         DETAIL_DATA_TO = lv_detail_data_to
         SELECT_X = lv_select_x
         MAX_ROWS = lv_max_rows
    TABLES
         SELOPTION = lt_seloption
         ARCH_RELMS = lt_arch_relms
         RESUBM_RULE = lt_resubm_rule
         RESUBM_DATE = lt_resubm_date
         STATUS = lt_status
         EXTENSION_OUT = lt_extension_out
         RETURN = lt_return
         INFRASTRUCTURE = lt_infrastructure
         TEXT = lt_text
         ARCH_OBJECT = lt_arch_object
         OBJECT_ADDRESS = lt_object_address
         NUMBER_RANGE = lt_number_range
         MEASUREMENT = lt_measurement
         PARTNER = lt_partner
         CHARACT = lt_charact
         OBJ_ASSIGN = lt_obj_assign
         ARCH_REL = lt_arch_rel
. " BAPI_RE_AO_GET_LIST




ABAP code using 7.40 inline data declarations to call FM BAPI_RE_AO_GET_LIST

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 DETAIL_VALID_FROM FROM BAPI_RE_ADDITIONAL_FIELDS INTO @DATA(ld_detail_data_from).
 
 
 
 
 
 
 
 
 
 
"SELECT single DETAIL_VALID_TO FROM BAPI_RE_ADDITIONAL_FIELDS INTO @DATA(ld_detail_data_to).
 
 
 
"SELECT single BAPIMAXROW FROM BAPI_RE_ADDITIONAL_FIELDS INTO @DATA(ld_max_rows).
 
 
 
 
 
 
 


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!