SAP ISU_EREPL_ENQUEUE Function Module for Internal: Enqueue of EREPL Table
ISU_EREPL_ENQUEUE is a standard isu erepl enqueue SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Internal: Enqueue of EREPL Table 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 isu erepl enqueue FM, simply by entering the name ISU_EREPL_ENQUEUE into the relevant SAP transaction such as SE37 or SE38.
Function Group: EREPL_ERRORHANDLING
Program Name: SAPLEREPL_ERRORHANDLING
Main Program: SAPLEREPL_ERRORHANDLING
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISU_EREPL_ENQUEUE 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 'ISU_EREPL_ENQUEUE'"Internal: Enqueue of EREPL Table.
EXPORTING
X_EVERD_CRMQ = "Screen Fields for IS-U Contract CRM - Inbound Queue
EXCEPTIONS
FOREIGN_LOCK = 1 ENQUEUE_ERROR = 2 SYSTEM_FAILURE = 3
IMPORTING Parameters details for ISU_EREPL_ENQUEUE
X_EVERD_CRMQ - Screen Fields for IS-U Contract CRM - Inbound Queue
Data type: EVERD_CRMQOptional: No
Call by Reference: Yes
EXCEPTIONS details
FOREIGN_LOCK - FOREIGN_LOCK
Data type:Optional: No
Call by Reference: Yes
ENQUEUE_ERROR - Enqueue errors
Data type:Optional: No
Call by Reference: Yes
SYSTEM_FAILURE - system_failure
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ISU_EREPL_ENQUEUE 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_foreign_lock | TYPE STRING, " | |||
| lv_x_everd_crmq | TYPE EVERD_CRMQ, " | |||
| lv_enqueue_error | TYPE EVERD_CRMQ, " | |||
| lv_system_failure | TYPE EVERD_CRMQ. " |
|   CALL FUNCTION 'ISU_EREPL_ENQUEUE' "Internal: Enqueue of EREPL Table |
| EXPORTING | ||
| X_EVERD_CRMQ | = lv_x_everd_crmq | |
| EXCEPTIONS | ||
| FOREIGN_LOCK = 1 | ||
| ENQUEUE_ERROR = 2 | ||
| SYSTEM_FAILURE = 3 | ||
| . " ISU_EREPL_ENQUEUE | ||
ABAP code using 7.40 inline data declarations to call FM ISU_EREPL_ENQUEUE
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