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

Function ALE_RE_RC_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 'ALE_RE_RC_GET_DETAIL'".
EXPORTING
RECORDCHANGECATEGORY = "
SURVEYOFFICE = "
RECORDCHANGENUMBER = "
* DETAILDATAFROM = RECA0_DATE-MIN "
* DETAILDATATO = RECA0_DATE-MAX "
* OBJ_TYPE = 'BUS1513' "
* SERIAL_ID = '0' "
TABLES
* RCPLREL = "
* APPLICATION_OBJECTS = "
* PARTNER = "
* TEXT = "
* RESUBMRULE = "
* RESUBMDATE = "
* STATUS = "
* EXTENSIONOUT = "
RECEIVERS = "
* COMMUNICATION_DOCUMENTS = "
EXCEPTIONS
ERROR_CREATING_IDOCS = 1
IMPORTING Parameters details for ALE_RE_RC_GET_DETAIL
RECORDCHANGECATEGORY -
Data type: BAPI_RE_RECORD_CHANGE_KEY-RECORD_CHANGE_CATEGORYOptional: No
Call by Reference: No ( called with pass by value option)
SURVEYOFFICE -
Data type: BAPI_RE_RECORD_CHANGE_KEY-SURVEY_OFFICEOptional: No
Call by Reference: No ( called with pass by value option)
RECORDCHANGENUMBER -
Data type: BAPI_RE_RECORD_CHANGE_KEY-RECORD_CHANGE_NUMBEROptional: No
Call by Reference: No ( called with pass by value option)
DETAILDATAFROM -
Data type: BAPI_RE_ADDITIONAL_FIELDS-DETAIL_VALID_FROMDefault: RECA0_DATE-MIN
Optional: No
Call by Reference: No ( called with pass by value option)
DETAILDATATO -
Data type: BAPI_RE_ADDITIONAL_FIELDS-DETAIL_VALID_TODefault: RECA0_DATE-MAX
Optional: No
Call by Reference: No ( called with pass by value option)
OBJ_TYPE -
Data type: SERIAL-OBJ_TYPEDefault: 'BUS1513'
Optional: Yes
Call by Reference: No ( called with pass by value option)
SERIAL_ID -
Data type: SERIAL-CHNUMDefault: '0'
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for ALE_RE_RC_GET_DETAIL
RCPLREL -
Data type: BAPI_RE_RC_PL_RELOptional: Yes
Call by Reference: No ( called with pass by value option)
APPLICATION_OBJECTS -
Data type: SWOTOBJIDOptional: Yes
Call by Reference: No ( called with pass by value option)
PARTNER -
Data type: BAPI_RE_PARTNEROptional: Yes
Call by Reference: No ( called with pass by value option)
TEXT -
Data type: BAPI_RE_TEXTOptional: Yes
Call by Reference: No ( called with pass by value option)
RESUBMRULE -
Data type: BAPI_RE_RESUBM_RULEOptional: Yes
Call by Reference: No ( called with pass by value option)
RESUBMDATE -
Data type: BAPI_RE_RESUBM_DATEOptional: Yes
Call by Reference: No ( called with pass by value option)
STATUS -
Data type: BAPI_RE_STATUSOptional: Yes
Call by Reference: No ( called with pass by value option)
EXTENSIONOUT -
Data type: BAPIPAREXOptional: Yes
Call by Reference: No ( called with pass by value option)
RECEIVERS -
Data type: BDI_LOGSYSOptional: No
Call by Reference: No ( called with pass by value option)
COMMUNICATION_DOCUMENTS -
Data type: SWOTOBJIDOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ERROR_CREATING_IDOCS -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ALE_RE_RC_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: | ||||
| lt_rcplrel | TYPE STANDARD TABLE OF BAPI_RE_RC_PL_REL, " | |||
| lv_error_creating_idocs | TYPE BAPI_RE_RC_PL_REL, " | |||
| lv_recordchangecategory | TYPE BAPI_RE_RECORD_CHANGE_KEY-RECORD_CHANGE_CATEGORY, " | |||
| lt_application_objects | TYPE STANDARD TABLE OF SWOTOBJID, " | |||
| lt_partner | TYPE STANDARD TABLE OF BAPI_RE_PARTNER, " | |||
| lv_surveyoffice | TYPE BAPI_RE_RECORD_CHANGE_KEY-SURVEY_OFFICE, " | |||
| lt_text | TYPE STANDARD TABLE OF BAPI_RE_TEXT, " | |||
| lv_recordchangenumber | TYPE BAPI_RE_RECORD_CHANGE_KEY-RECORD_CHANGE_NUMBER, " | |||
| lt_resubmrule | TYPE STANDARD TABLE OF BAPI_RE_RESUBM_RULE, " | |||
| lv_detaildatafrom | TYPE BAPI_RE_ADDITIONAL_FIELDS-DETAIL_VALID_FROM, " RECA0_DATE-MIN | |||
| lt_resubmdate | TYPE STANDARD TABLE OF BAPI_RE_RESUBM_DATE, " | |||
| lv_detaildatato | TYPE BAPI_RE_ADDITIONAL_FIELDS-DETAIL_VALID_TO, " RECA0_DATE-MAX | |||
| lt_status | TYPE STANDARD TABLE OF BAPI_RE_STATUS, " | |||
| lv_obj_type | TYPE SERIAL-OBJ_TYPE, " 'BUS1513' | |||
| lv_serial_id | TYPE SERIAL-CHNUM, " '0' | |||
| lt_extensionout | TYPE STANDARD TABLE OF BAPIPAREX, " | |||
| lt_receivers | TYPE STANDARD TABLE OF BDI_LOGSYS, " | |||
| lt_communication_documents | TYPE STANDARD TABLE OF SWOTOBJID. " |
|   CALL FUNCTION 'ALE_RE_RC_GET_DETAIL' " |
| EXPORTING | ||
| RECORDCHANGECATEGORY | = lv_recordchangecategory | |
| SURVEYOFFICE | = lv_surveyoffice | |
| RECORDCHANGENUMBER | = lv_recordchangenumber | |
| DETAILDATAFROM | = lv_detaildatafrom | |
| DETAILDATATO | = lv_detaildatato | |
| OBJ_TYPE | = lv_obj_type | |
| SERIAL_ID | = lv_serial_id | |
| TABLES | ||
| RCPLREL | = lt_rcplrel | |
| APPLICATION_OBJECTS | = lt_application_objects | |
| PARTNER | = lt_partner | |
| TEXT | = lt_text | |
| RESUBMRULE | = lt_resubmrule | |
| RESUBMDATE | = lt_resubmdate | |
| STATUS | = lt_status | |
| EXTENSIONOUT | = lt_extensionout | |
| RECEIVERS | = lt_receivers | |
| COMMUNICATION_DOCUMENTS | = lt_communication_documents | |
| EXCEPTIONS | ||
| ERROR_CREATING_IDOCS = 1 | ||
| . " ALE_RE_RC_GET_DETAIL | ||
ABAP code using 7.40 inline data declarations to call FM ALE_RE_RC_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 RECORD_CHANGE_CATEGORY FROM BAPI_RE_RECORD_CHANGE_KEY INTO @DATA(ld_recordchangecategory). | ||||
| "SELECT single SURVEY_OFFICE FROM BAPI_RE_RECORD_CHANGE_KEY INTO @DATA(ld_surveyoffice). | ||||
| "SELECT single RECORD_CHANGE_NUMBER FROM BAPI_RE_RECORD_CHANGE_KEY INTO @DATA(ld_recordchangenumber). | ||||
| "SELECT single DETAIL_VALID_FROM FROM BAPI_RE_ADDITIONAL_FIELDS INTO @DATA(ld_detaildatafrom). | ||||
| DATA(ld_detaildatafrom) | = RECA0_DATE-MIN. | |||
| "SELECT single DETAIL_VALID_TO FROM BAPI_RE_ADDITIONAL_FIELDS INTO @DATA(ld_detaildatato). | ||||
| DATA(ld_detaildatato) | = RECA0_DATE-MAX. | |||
| "SELECT single OBJ_TYPE FROM SERIAL INTO @DATA(ld_obj_type). | ||||
| DATA(ld_obj_type) | = 'BUS1513'. | |||
| "SELECT single CHNUM FROM SERIAL INTO @DATA(ld_serial_id). | ||||
| DATA(ld_serial_id) | = '0'. | |||
Search for further information about these or an SAP related objects