SAP UR_EXAPI_REANIMATE_OPEN Function Module for
UR_EXAPI_REANIMATE_OPEN is a standard ur exapi reanimate open 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 ur exapi reanimate open FM, simply by entering the name UR_EXAPI_REANIMATE_OPEN into the relevant SAP transaction such as SE37 or SE38.
Function Group: UR_EXTINCTION_API
Program Name: SAPLUR_EXTINCTION_API
Main Program: SAPLUR_EXTINCTION_API
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function UR_EXAPI_REANIMATE_OPEN 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 'UR_EXAPI_REANIMATE_OPEN'".
EXPORTING
I_ID = "
IMPORTING
E_CHGRUN = "
E_TYPENAME = "
EXCEPTIONS
NOT_NOW = 1 MEGRIM = 2 CANT_LOCK = 3
IMPORTING Parameters details for UR_EXAPI_REANIMATE_OPEN
I_ID -
Data type: UR_IDOptional: No
Call by Reference: Yes
EXPORTING Parameters details for UR_EXAPI_REANIMATE_OPEN
E_CHGRUN -
Data type: UR_CHGRUNOptional: No
Call by Reference: Yes
E_TYPENAME -
Data type: TYPENAMEOptional: No
Call by Reference: Yes
EXCEPTIONS details
NOT_NOW -
Data type:Optional: No
Call by Reference: Yes
MEGRIM -
Data type:Optional: No
Call by Reference: Yes
CANT_LOCK -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for UR_EXAPI_REANIMATE_OPEN 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_i_id | TYPE UR_ID, " | |||
| lv_not_now | TYPE UR_ID, " | |||
| lv_e_chgrun | TYPE UR_CHGRUN, " | |||
| lv_megrim | TYPE UR_CHGRUN, " | |||
| lv_e_typename | TYPE TYPENAME, " | |||
| lv_cant_lock | TYPE TYPENAME. " |
|   CALL FUNCTION 'UR_EXAPI_REANIMATE_OPEN' " |
| EXPORTING | ||
| I_ID | = lv_i_id | |
| IMPORTING | ||
| E_CHGRUN | = lv_e_chgrun | |
| E_TYPENAME | = lv_e_typename | |
| EXCEPTIONS | ||
| NOT_NOW = 1 | ||
| MEGRIM = 2 | ||
| CANT_LOCK = 3 | ||
| . " UR_EXAPI_REANIMATE_OPEN | ||
ABAP code using 7.40 inline data declarations to call FM UR_EXAPI_REANIMATE_OPEN
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.Search for further information about these or an SAP related objects