SAP EPS_RESET_DELIVERY_REQUEST Function Module for









EPS_RESET_DELIVERY_REQUEST is a standard eps reset delivery request 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 eps reset delivery request FM, simply by entering the name EPS_RESET_DELIVERY_REQUEST into the relevant SAP transaction such as SE37 or SE38.

Function Group: EPSS
Program Name: SAPLEPSS
Main Program:
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function EPS_RESET_DELIVERY_REQUEST 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 'EPS_RESET_DELIVERY_REQUEST'"
EXPORTING
* IV_COMMIT = 'X' "
IV_PARCEL_NUMBER = "
IV_PARCEL_ORIGIN = "
IV_RECEIVER = "

EXCEPTIONS
NOT_YET_DELIVERED = 1 PARCEL_IS_DELETED = 2 PARCEL_IS_EXPIRED = 3 PARCEL_IS_LOCKED = 4 PARCEL_NOT_FOUND = 5 REQUEST_NOT_FOUND = 6 UPDATE_REQUEST_FAILED = 7
.



IMPORTING Parameters details for EPS_RESET_DELIVERY_REQUEST

IV_COMMIT -

Data type: EPSF-EPSFLAG
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_PARCEL_NUMBER -

Data type: TEPSDELI-EPSPCLNUM
Optional: No
Call by Reference: No ( called with pass by value option)

IV_PARCEL_ORIGIN -

Data type: TEPSDELI-EPSPCLORI
Optional: No
Call by Reference: No ( called with pass by value option)

IV_RECEIVER -

Data type: TEPSDELI-EPSRECADR
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

NOT_YET_DELIVERED -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

PARCEL_IS_DELETED -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

PARCEL_IS_EXPIRED -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

PARCEL_IS_LOCKED -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

PARCEL_NOT_FOUND -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

REQUEST_NOT_FOUND -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

UPDATE_REQUEST_FAILED -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for EPS_RESET_DELIVERY_REQUEST 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_iv_commit  TYPE EPSF-EPSFLAG, "   'X'
lv_not_yet_delivered  TYPE EPSF, "   
lv_iv_parcel_number  TYPE TEPSDELI-EPSPCLNUM, "   
lv_parcel_is_deleted  TYPE TEPSDELI, "   
lv_iv_parcel_origin  TYPE TEPSDELI-EPSPCLORI, "   
lv_parcel_is_expired  TYPE TEPSDELI, "   
lv_iv_receiver  TYPE TEPSDELI-EPSRECADR, "   
lv_parcel_is_locked  TYPE TEPSDELI, "   
lv_parcel_not_found  TYPE TEPSDELI, "   
lv_request_not_found  TYPE TEPSDELI, "   
lv_update_request_failed  TYPE TEPSDELI. "   

  CALL FUNCTION 'EPS_RESET_DELIVERY_REQUEST'  "
    EXPORTING
         IV_COMMIT = lv_iv_commit
         IV_PARCEL_NUMBER = lv_iv_parcel_number
         IV_PARCEL_ORIGIN = lv_iv_parcel_origin
         IV_RECEIVER = lv_iv_receiver
    EXCEPTIONS
        NOT_YET_DELIVERED = 1
        PARCEL_IS_DELETED = 2
        PARCEL_IS_EXPIRED = 3
        PARCEL_IS_LOCKED = 4
        PARCEL_NOT_FOUND = 5
        REQUEST_NOT_FOUND = 6
        UPDATE_REQUEST_FAILED = 7
. " EPS_RESET_DELIVERY_REQUEST




ABAP code using 7.40 inline data declarations to call FM EPS_RESET_DELIVERY_REQUEST

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 EPSFLAG FROM EPSF INTO @DATA(ld_iv_commit).
DATA(ld_iv_commit) = 'X'.
 
 
"SELECT single EPSPCLNUM FROM TEPSDELI INTO @DATA(ld_iv_parcel_number).
 
 
"SELECT single EPSPCLORI FROM TEPSDELI INTO @DATA(ld_iv_parcel_origin).
 
 
"SELECT single EPSRECADR FROM TEPSDELI INTO @DATA(ld_iv_receiver).
 
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!