SAP API_RE_AO_GET_DETAIL Function Module for
API_RE_AO_GET_DETAIL is a standard api 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 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 api re ao get detail FM, simply by entering the name API_RE_AO_GET_DETAIL into the relevant SAP transaction such as SE37 or SE38.
Function Group: REBD_API_ARCH_OBJECT
Program Name: SAPLREBD_API_ARCH_OBJECT
Main Program: SAPLREBD_API_ARCH_OBJECT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function API_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 'API_RE_AO_GET_DETAIL'".
EXPORTING
* ID_AOID = "
* ID_OBJNR = "
* ID_INTRENO = "
* IO_OBJECT = "
* ID_DETAIL_DATA_FROM = "
* ID_DETAIL_DATA_TO = "
* IF_OLD_DATA = ' ' "
IMPORTING
ES_ARCH_OBJECT = "
ET_ARCH_RELMS = "
ET_TEXT = "
ET_RESUBM_RULE = "
ET_RESUBM_DATE = "
ET_STATUS = "
ES_CI_DATA = "
ET_EXT_DATA = "
ES_OBJECT_ADDRESS = "
ET_NUMBER_RANGE = "
ET_MEASUREMENT = "
ET_INFRASTRUCTURE = "
ET_PARTNER = "
ET_CHARACT = "
ET_OBJ_ASSIGN = "
ET_ARCH_REL = "
EXCEPTIONS
ERROR = 1
IMPORTING Parameters details for API_RE_AO_GET_DETAIL
ID_AOID -
Data type: BAPI_RE_ARCH_OBJECT_INTK-AOIDOptional: Yes
Call by Reference: Yes
ID_OBJNR -
Data type: RECAOBJNROptional: Yes
Call by Reference: Yes
ID_INTRENO -
Data type: RECAINTRENOOptional: Yes
Call by Reference: Yes
IO_OBJECT -
Data type: OBJECTOptional: Yes
Call by Reference: Yes
ID_DETAIL_DATA_FROM -
Data type: BAPI_RE_ADDITIONAL_FIELDS_INT-DETAILVALIDFROMOptional: Yes
Call by Reference: Yes
ID_DETAIL_DATA_TO -
Data type: BAPI_RE_ADDITIONAL_FIELDS_INT-DETAILVALIDTOOptional: Yes
Call by Reference: Yes
IF_OLD_DATA -
Data type: RECABOOLDefault: ' '
Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for API_RE_AO_GET_DETAIL
ES_ARCH_OBJECT -
Data type: BAPI_RE_ARCH_OBJECT_INTOptional: No
Call by Reference: Yes
ET_ARCH_RELMS -
Data type: BAPI_RE_T_ARCH_RELMS_INTOptional: No
Call by Reference: Yes
ET_TEXT -
Data type: BAPI_RE_T_TEXT_INTOptional: No
Call by Reference: Yes
ET_RESUBM_RULE -
Data type: BAPI_RE_T_RESUBM_RULE_INTOptional: No
Call by Reference: Yes
ET_RESUBM_DATE -
Data type: BAPI_RE_T_RESUBM_DATE_INTOptional: No
Call by Reference: Yes
ET_STATUS -
Data type: BAPI_RE_T_STATUS_INTOptional: No
Call by Reference: Yes
ES_CI_DATA -
Data type: REBD_ARCH_OBJECT_CIOptional: No
Call by Reference: Yes
ET_EXT_DATA -
Data type: RE_T_EXT_DATAOptional: No
Call by Reference: Yes
ES_OBJECT_ADDRESS -
Data type: BAPI_RE_OBJ_ADDRESS_INTOptional: No
Call by Reference: Yes
ET_NUMBER_RANGE -
Data type: BAPI_RE_T_NUMBER_RANGE_INTOptional: No
Call by Reference: Yes
ET_MEASUREMENT -
Data type: BAPI_RE_T_MEASUREMENT_INTOptional: No
Call by Reference: Yes
ET_INFRASTRUCTURE -
Data type: BAPI_RE_T_INFRA_INTOptional: No
Call by Reference: Yes
ET_PARTNER -
Data type: BAPI_RE_T_PARTNER_INTOptional: No
Call by Reference: Yes
ET_CHARACT -
Data type: BAPI_RE_T_CHARACT_INTOptional: No
Call by Reference: Yes
ET_OBJ_ASSIGN -
Data type: BAPI_RE_T_OBJ_ASSIGN_INTOptional: No
Call by Reference: Yes
ET_ARCH_REL -
Data type: BAPI_RE_T_ARCH_REL_INTOptional: No
Call by Reference: Yes
EXCEPTIONS details
ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for API_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_error | TYPE STRING, " | |||
| lv_id_aoid | TYPE BAPI_RE_ARCH_OBJECT_INTK-AOID, " | |||
| lv_es_arch_object | TYPE BAPI_RE_ARCH_OBJECT_INT, " | |||
| lv_et_arch_relms | TYPE BAPI_RE_T_ARCH_RELMS_INT, " | |||
| lv_et_text | TYPE BAPI_RE_T_TEXT_INT, " | |||
| lv_et_resubm_rule | TYPE BAPI_RE_T_RESUBM_RULE_INT, " | |||
| lv_et_resubm_date | TYPE BAPI_RE_T_RESUBM_DATE_INT, " | |||
| lv_et_status | TYPE BAPI_RE_T_STATUS_INT, " | |||
| lv_es_ci_data | TYPE REBD_ARCH_OBJECT_CI, " | |||
| lv_et_ext_data | TYPE RE_T_EXT_DATA, " | |||
| lv_id_objnr | TYPE RECAOBJNR, " | |||
| lv_es_object_address | TYPE BAPI_RE_OBJ_ADDRESS_INT, " | |||
| lv_id_intreno | TYPE RECAINTRENO, " | |||
| lv_et_number_range | TYPE BAPI_RE_T_NUMBER_RANGE_INT, " | |||
| lv_io_object | TYPE OBJECT, " | |||
| lv_et_measurement | TYPE BAPI_RE_T_MEASUREMENT_INT, " | |||
| lv_et_infrastructure | TYPE BAPI_RE_T_INFRA_INT, " | |||
| lv_id_detail_data_from | TYPE BAPI_RE_ADDITIONAL_FIELDS_INT-DETAILVALIDFROM, " | |||
| lv_et_partner | TYPE BAPI_RE_T_PARTNER_INT, " | |||
| lv_id_detail_data_to | TYPE BAPI_RE_ADDITIONAL_FIELDS_INT-DETAILVALIDTO, " | |||
| lv_et_charact | TYPE BAPI_RE_T_CHARACT_INT, " | |||
| lv_if_old_data | TYPE RECABOOL, " ' ' | |||
| lv_et_obj_assign | TYPE BAPI_RE_T_OBJ_ASSIGN_INT, " | |||
| lv_et_arch_rel | TYPE BAPI_RE_T_ARCH_REL_INT. " |
|   CALL FUNCTION 'API_RE_AO_GET_DETAIL' " |
| EXPORTING | ||
| ID_AOID | = lv_id_aoid | |
| ID_OBJNR | = lv_id_objnr | |
| ID_INTRENO | = lv_id_intreno | |
| IO_OBJECT | = lv_io_object | |
| ID_DETAIL_DATA_FROM | = lv_id_detail_data_from | |
| ID_DETAIL_DATA_TO | = lv_id_detail_data_to | |
| IF_OLD_DATA | = lv_if_old_data | |
| IMPORTING | ||
| ES_ARCH_OBJECT | = lv_es_arch_object | |
| ET_ARCH_RELMS | = lv_et_arch_relms | |
| ET_TEXT | = lv_et_text | |
| ET_RESUBM_RULE | = lv_et_resubm_rule | |
| ET_RESUBM_DATE | = lv_et_resubm_date | |
| ET_STATUS | = lv_et_status | |
| ES_CI_DATA | = lv_es_ci_data | |
| ET_EXT_DATA | = lv_et_ext_data | |
| ES_OBJECT_ADDRESS | = lv_es_object_address | |
| ET_NUMBER_RANGE | = lv_et_number_range | |
| ET_MEASUREMENT | = lv_et_measurement | |
| ET_INFRASTRUCTURE | = lv_et_infrastructure | |
| ET_PARTNER | = lv_et_partner | |
| ET_CHARACT | = lv_et_charact | |
| ET_OBJ_ASSIGN | = lv_et_obj_assign | |
| ET_ARCH_REL | = lv_et_arch_rel | |
| EXCEPTIONS | ||
| ERROR = 1 | ||
| . " API_RE_AO_GET_DETAIL | ||
ABAP code using 7.40 inline data declarations to call FM API_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 AOID FROM BAPI_RE_ARCH_OBJECT_INTK INTO @DATA(ld_id_aoid). | ||||
| "SELECT single DETAILVALIDFROM FROM BAPI_RE_ADDITIONAL_FIELDS_INT INTO @DATA(ld_id_detail_data_from). | ||||
| "SELECT single DETAILVALIDTO FROM BAPI_RE_ADDITIONAL_FIELDS_INT INTO @DATA(ld_id_detail_data_to). | ||||
| DATA(ld_if_old_data) | = ' '. | |||
Search for further information about these or an SAP related objects