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

Function API_RE_PE_CHANGE 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_PE_CHANGE'".
EXPORTING
* ID_PEID = "
* IT_PARTNER = "
* IT_OBJ_ASSIGN = "
* IT_TEXT = "
* IT_RESUBM_RULE = "
* IT_RESUBM_DATE = "
* IT_STATUS = "
* IS_CI_DATA = "
* IF_CI_DATA_X = ' ' "
* IT_EXT_DATA = "
* ID_TRANS = "
* ID_OBJNR = "
* IF_TEST_RUN = ' ' "
* IF_MSGLIST_INSTEAD_OF_EXC = ' ' "
* IO_MSGLIST = "
* ID_INTRENO = "
* IO_OBJECT = "
* IS_PUBLIC_ENC = "
* IS_PUBLIC_ENC_X = "
* IT_PE_CONT_SITE = "
* IT_PE_EASEMNT = "
* IT_PE_EMDOMPL = "
IMPORTING
EF_STORED = "
EXCEPTIONS
ERROR = 1
IMPORTING Parameters details for API_RE_PE_CHANGE
ID_PEID -
Data type: BAPI_RE_PUBLIC_ENC_INTK-PEIDOptional: Yes
Call by Reference: Yes
IT_PARTNER -
Data type: BAPI_RE_T_PARTNER_INTCOptional: Yes
Call by Reference: Yes
IT_OBJ_ASSIGN -
Data type: BAPI_RE_T_OBJ_ASSIGN_INTCOptional: Yes
Call by Reference: Yes
IT_TEXT -
Data type: BAPI_RE_T_TEXT_INTCOptional: Yes
Call by Reference: Yes
IT_RESUBM_RULE -
Data type: BAPI_RE_T_RESUBM_RULE_INTCOptional: Yes
Call by Reference: Yes
IT_RESUBM_DATE -
Data type: BAPI_RE_T_RESUBM_DATE_INTCOptional: Yes
Call by Reference: Yes
IT_STATUS -
Data type: BAPI_RE_T_STATUS_INTCOptional: Yes
Call by Reference: Yes
IS_CI_DATA -
Data type: RELM_PUBLIC_ENCUMBRANCE_CIOptional: Yes
Call by Reference: Yes
IF_CI_DATA_X -
Data type: RECABOOLDefault: ' '
Optional: Yes
Call by Reference: Yes
IT_EXT_DATA -
Data type: RE_T_EXT_DATAOptional: Yes
Call by Reference: Yes
ID_TRANS -
Data type: BAPI_RE_ADDITIONAL_FIELDS-TRANSOptional: Yes
Call by Reference: Yes
ID_OBJNR -
Data type: RECAOBJNROptional: Yes
Call by Reference: Yes
IF_TEST_RUN -
Data type: BAPI_RE_ADDITIONAL_FIELDS-TESTRUNDefault: ' '
Optional: Yes
Call by Reference: Yes
IF_MSGLIST_INSTEAD_OF_EXC -
Data type: RECABOOLDefault: ' '
Optional: Yes
Call by Reference: Yes
IO_MSGLIST -
Data type: OBJECTOptional: 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
IS_PUBLIC_ENC -
Data type: BAPI_RE_PUBLIC_ENC_INTOptional: Yes
Call by Reference: Yes
IS_PUBLIC_ENC_X -
Data type: BAPI_RE_PUBLIC_ENC_INTXOptional: Yes
Call by Reference: Yes
IT_PE_CONT_SITE -
Data type: BAPI_RE_T_PE_CONT_SITE_INTCOptional: Yes
Call by Reference: Yes
IT_PE_EASEMNT -
Data type: BAPI_RE_T_PE_EASEMNT_INTCOptional: Yes
Call by Reference: Yes
IT_PE_EMDOMPL -
Data type: BAPI_RE_T_PE_EMDOMPL_INTCOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for API_RE_PE_CHANGE
EF_STORED -
Data type: RECABOOLOptional: 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_PE_CHANGE 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_peid | TYPE BAPI_RE_PUBLIC_ENC_INTK-PEID, " | |||
| lv_ef_stored | TYPE RECABOOL, " | |||
| lv_it_partner | TYPE BAPI_RE_T_PARTNER_INTC, " | |||
| lv_it_obj_assign | TYPE BAPI_RE_T_OBJ_ASSIGN_INTC, " | |||
| lv_it_text | TYPE BAPI_RE_T_TEXT_INTC, " | |||
| lv_it_resubm_rule | TYPE BAPI_RE_T_RESUBM_RULE_INTC, " | |||
| lv_it_resubm_date | TYPE BAPI_RE_T_RESUBM_DATE_INTC, " | |||
| lv_it_status | TYPE BAPI_RE_T_STATUS_INTC, " | |||
| lv_is_ci_data | TYPE RELM_PUBLIC_ENCUMBRANCE_CI, " | |||
| lv_if_ci_data_x | TYPE RECABOOL, " ' ' | |||
| lv_it_ext_data | TYPE RE_T_EXT_DATA, " | |||
| lv_id_trans | TYPE BAPI_RE_ADDITIONAL_FIELDS-TRANS, " | |||
| lv_id_objnr | TYPE RECAOBJNR, " | |||
| lv_if_test_run | TYPE BAPI_RE_ADDITIONAL_FIELDS-TESTRUN, " ' ' | |||
| lv_if_msglist_instead_of_exc | TYPE RECABOOL, " ' ' | |||
| lv_io_msglist | TYPE OBJECT, " | |||
| lv_id_intreno | TYPE RECAINTRENO, " | |||
| lv_io_object | TYPE OBJECT, " | |||
| lv_is_public_enc | TYPE BAPI_RE_PUBLIC_ENC_INT, " | |||
| lv_is_public_enc_x | TYPE BAPI_RE_PUBLIC_ENC_INTX, " | |||
| lv_it_pe_cont_site | TYPE BAPI_RE_T_PE_CONT_SITE_INTC, " | |||
| lv_it_pe_easemnt | TYPE BAPI_RE_T_PE_EASEMNT_INTC, " | |||
| lv_it_pe_emdompl | TYPE BAPI_RE_T_PE_EMDOMPL_INTC. " |
|   CALL FUNCTION 'API_RE_PE_CHANGE' " |
| EXPORTING | ||
| ID_PEID | = lv_id_peid | |
| IT_PARTNER | = lv_it_partner | |
| IT_OBJ_ASSIGN | = lv_it_obj_assign | |
| IT_TEXT | = lv_it_text | |
| IT_RESUBM_RULE | = lv_it_resubm_rule | |
| IT_RESUBM_DATE | = lv_it_resubm_date | |
| IT_STATUS | = lv_it_status | |
| IS_CI_DATA | = lv_is_ci_data | |
| IF_CI_DATA_X | = lv_if_ci_data_x | |
| IT_EXT_DATA | = lv_it_ext_data | |
| ID_TRANS | = lv_id_trans | |
| ID_OBJNR | = lv_id_objnr | |
| IF_TEST_RUN | = lv_if_test_run | |
| IF_MSGLIST_INSTEAD_OF_EXC | = lv_if_msglist_instead_of_exc | |
| IO_MSGLIST | = lv_io_msglist | |
| ID_INTRENO | = lv_id_intreno | |
| IO_OBJECT | = lv_io_object | |
| IS_PUBLIC_ENC | = lv_is_public_enc | |
| IS_PUBLIC_ENC_X | = lv_is_public_enc_x | |
| IT_PE_CONT_SITE | = lv_it_pe_cont_site | |
| IT_PE_EASEMNT | = lv_it_pe_easemnt | |
| IT_PE_EMDOMPL | = lv_it_pe_emdompl | |
| IMPORTING | ||
| EF_STORED | = lv_ef_stored | |
| EXCEPTIONS | ||
| ERROR = 1 | ||
| . " API_RE_PE_CHANGE | ||
ABAP code using 7.40 inline data declarations to call FM API_RE_PE_CHANGE
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 PEID FROM BAPI_RE_PUBLIC_ENC_INTK INTO @DATA(ld_id_peid). | ||||
| DATA(ld_if_ci_data_x) | = ' '. | |||
| "SELECT single TRANS FROM BAPI_RE_ADDITIONAL_FIELDS INTO @DATA(ld_id_trans). | ||||
| "SELECT single TESTRUN FROM BAPI_RE_ADDITIONAL_FIELDS INTO @DATA(ld_if_test_run). | ||||
| DATA(ld_if_test_run) | = ' '. | |||
| DATA(ld_if_msglist_instead_of_exc) | = ' '. | |||
Search for further information about these or an SAP related objects