SAP BAPI_RE_AO_GET_DETAIL Function Module for Return Architectural Object Data
BAPI_RE_AO_GET_DETAIL is a standard bapi re ao get detail 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 Architectural Object Data 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 detail FM, simply by entering the name BAPI_RE_AO_GET_DETAIL 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_DETAIL 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_DETAIL'"Return Architectural Object Data.
EXPORTING
ARCHOBJECTID = "Identification of Architectural Object
* DETAIL_DATA_FROM = "Date: Detailed Data Valid From
* DETAIL_DATA_TO = "Date: Detailed Data Valid To
IMPORTING
ARCH_OBJECT = "Architectural Object
OBJECT_ADDRESS = "Address
TABLES
* NUMBER_RANGE = "Number Ranges
* STATUS = "Status
* EXTENSION_OUT = "Data of User Fields
* RETURN = "Return Parameters
* INFRASTRUCTURE = "Infrastructure
* TEXT = "Texts/Memos
* MEASUREMENT = "Measurements
* PARTNER = "Partner
* CHARACT = "Fixtures and Fittings Characteristic of RE Object
* OBJ_ASSIGN = "Object Assignment
* RESUBM_RULE = "Reminder Rule
* RESUBM_DATE = "Reminder Date
* ARCH_REL = "Architectural Linkage Objects
* ARCH_RELMS = "Architectural Linkage Object Parts
IMPORTING Parameters details for BAPI_RE_AO_GET_DETAIL
ARCHOBJECTID - Identification of Architectural Object
Data type: BAPI_RE_ARCH_OBJECT_KEY-ARCH_OBJECT_IDOptional: No
Call by Reference: No ( called with pass by value option)
DETAIL_DATA_FROM - Date: Detailed Data Valid From
Data type: BAPI_RE_ADDITIONAL_FIELDS-DETAIL_VALID_FROMOptional: 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_TOOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BAPI_RE_AO_GET_DETAIL
ARCH_OBJECT - Architectural Object
Data type: BAPI_RE_ARCH_OBJECTOptional: No
Call by Reference: No ( called with pass by value option)
OBJECT_ADDRESS - Address
Data type: BAPI_RE_OBJ_ADDRESSOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_RE_AO_GET_DETAIL
NUMBER_RANGE - Number Ranges
Data type: BAPI_RE_NUMBER_RANGEOptional: Yes
Call by Reference: Yes
STATUS - Status
Data type: BAPI_RE_STATUSOptional: Yes
Call by Reference: Yes
EXTENSION_OUT - Data of User Fields
Data type: BAPIPAREXOptional: Yes
Call by Reference: Yes
RETURN - Return Parameters
Data type: BAPIRET2Optional: Yes
Call by Reference: Yes
INFRASTRUCTURE - Infrastructure
Data type: BAPI_RE_INFRAOptional: Yes
Call by Reference: Yes
TEXT - Texts/Memos
Data type: BAPI_RE_TEXTOptional: Yes
Call by Reference: Yes
MEASUREMENT - Measurements
Data type: BAPI_RE_MEASUREMENTOptional: Yes
Call by Reference: Yes
PARTNER - Partner
Data type: BAPI_RE_PARTNEROptional: Yes
Call by Reference: Yes
CHARACT - Fixtures and Fittings Characteristic of RE Object
Data type: BAPI_RE_CHARACTOptional: Yes
Call by Reference: Yes
OBJ_ASSIGN - Object Assignment
Data type: BAPI_RE_OBJ_ASSIGNOptional: Yes
Call by Reference: Yes
RESUBM_RULE - Reminder Rule
Data type: BAPI_RE_RESUBM_RULEOptional: Yes
Call by Reference: Yes
RESUBM_DATE - Reminder Date
Data type: BAPI_RE_RESUBM_DATEOptional: Yes
Call by Reference: Yes
ARCH_REL - Architectural Linkage Objects
Data type: BAPI_RE_ARCH_RELOptional: Yes
Call by Reference: Yes
ARCH_RELMS - Architectural Linkage Object Parts
Data type: BAPI_RE_ARCH_RELMSOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for BAPI_RE_AO_GET_DETAIL 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_arch_object | TYPE BAPI_RE_ARCH_OBJECT, " | |||
| lv_archobjectid | TYPE BAPI_RE_ARCH_OBJECT_KEY-ARCH_OBJECT_ID, " | |||
| lt_number_range | TYPE STANDARD TABLE OF BAPI_RE_NUMBER_RANGE, " | |||
| lt_status | TYPE STANDARD TABLE OF BAPI_RE_STATUS, " | |||
| lt_extension_out | TYPE STANDARD TABLE OF BAPIPAREX, " | |||
| 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_measurement | TYPE STANDARD TABLE OF BAPI_RE_MEASUREMENT, " | |||
| lv_object_address | TYPE BAPI_RE_OBJ_ADDRESS, " | |||
| lv_detail_data_from | TYPE BAPI_RE_ADDITIONAL_FIELDS-DETAIL_VALID_FROM, " | |||
| lt_partner | TYPE STANDARD TABLE OF BAPI_RE_PARTNER, " | |||
| lv_detail_data_to | TYPE BAPI_RE_ADDITIONAL_FIELDS-DETAIL_VALID_TO, " | |||
| lt_charact | TYPE STANDARD TABLE OF BAPI_RE_CHARACT, " | |||
| lt_obj_assign | TYPE STANDARD TABLE OF BAPI_RE_OBJ_ASSIGN, " | |||
| lt_resubm_rule | TYPE STANDARD TABLE OF BAPI_RE_RESUBM_RULE, " | |||
| lt_resubm_date | TYPE STANDARD TABLE OF BAPI_RE_RESUBM_DATE, " | |||
| lt_arch_rel | TYPE STANDARD TABLE OF BAPI_RE_ARCH_REL, " | |||
| lt_arch_relms | TYPE STANDARD TABLE OF BAPI_RE_ARCH_RELMS. " |
|   CALL FUNCTION 'BAPI_RE_AO_GET_DETAIL' "Return Architectural Object Data |
| EXPORTING | ||
| ARCHOBJECTID | = lv_archobjectid | |
| DETAIL_DATA_FROM | = lv_detail_data_from | |
| DETAIL_DATA_TO | = lv_detail_data_to | |
| IMPORTING | ||
| ARCH_OBJECT | = lv_arch_object | |
| OBJECT_ADDRESS | = lv_object_address | |
| TABLES | ||
| NUMBER_RANGE | = lt_number_range | |
| STATUS | = lt_status | |
| EXTENSION_OUT | = lt_extension_out | |
| RETURN | = lt_return | |
| INFRASTRUCTURE | = lt_infrastructure | |
| TEXT | = lt_text | |
| MEASUREMENT | = lt_measurement | |
| PARTNER | = lt_partner | |
| CHARACT | = lt_charact | |
| OBJ_ASSIGN | = lt_obj_assign | |
| RESUBM_RULE | = lt_resubm_rule | |
| RESUBM_DATE | = lt_resubm_date | |
| ARCH_REL | = lt_arch_rel | |
| ARCH_RELMS | = lt_arch_relms | |
| . " BAPI_RE_AO_GET_DETAIL | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_RE_AO_GET_DETAIL
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 ARCH_OBJECT_ID FROM BAPI_RE_ARCH_OBJECT_KEY INTO @DATA(ld_archobjectid). | ||||
| "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). | ||||
Search for further information about these or an SAP related objects