SAP EPS_BUILD_PARCEL_NAME Function Module for
EPS_BUILD_PARCEL_NAME is a standard eps build parcel name 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 build parcel name FM, simply by entering the name EPS_BUILD_PARCEL_NAME into the relevant SAP transaction such as SE37 or SE38.
Function Group: EPSC
Program Name: SAPLEPSC
Main Program: SAPLEPSC
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function EPS_BUILD_PARCEL_NAME 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_BUILD_PARCEL_NAME'".
EXPORTING
IV_PARCEL_ORIGIN = "
IV_PARCEL_NUMBER = "
IV_PARCEL_EXTENSION = "
* IV_EPS_SUBDIRECTORY = ' ' "
IMPORTING
EV_PARCEL_NAME = "
EV_PARCEL_PATH = "
EV_PARCEL_DIR = "
EXCEPTIONS
INVALID_EPS_SUBDIR = 1 SAPGPARAM_FAILED = 2 BUILD_DIRECTORY_FAILED = 3 BUILD_PATH_FAILED = 4
IMPORTING Parameters details for EPS_BUILD_PARCEL_NAME
IV_PARCEL_ORIGIN -
Data type: TEPSIN-EPSPCLORIOptional: No
Call by Reference: No ( called with pass by value option)
IV_PARCEL_NUMBER -
Data type: TEPSIN-EPSPCLNUMOptional: No
Call by Reference: No ( called with pass by value option)
IV_PARCEL_EXTENSION -
Data type: TEPSIN-EPSPCLEXTOptional: No
Call by Reference: No ( called with pass by value option)
IV_EPS_SUBDIRECTORY -
Data type: EPSF-EPSSUBDIRDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for EPS_BUILD_PARCEL_NAME
EV_PARCEL_NAME -
Data type: EPSF-EPSFILNAMOptional: No
Call by Reference: No ( called with pass by value option)
EV_PARCEL_PATH -
Data type: EPSF-EPSPATHOptional: No
Call by Reference: No ( called with pass by value option)
EV_PARCEL_DIR -
Data type: EPSF-EPSDIRNAMOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
INVALID_EPS_SUBDIR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SAPGPARAM_FAILED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
BUILD_DIRECTORY_FAILED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
BUILD_PATH_FAILED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for EPS_BUILD_PARCEL_NAME 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_ev_parcel_name | TYPE EPSF-EPSFILNAM, " | |||
lv_iv_parcel_origin | TYPE TEPSIN-EPSPCLORI, " | |||
lv_invalid_eps_subdir | TYPE TEPSIN, " | |||
lv_ev_parcel_path | TYPE EPSF-EPSPATH, " | |||
lv_iv_parcel_number | TYPE TEPSIN-EPSPCLNUM, " | |||
lv_sapgparam_failed | TYPE TEPSIN, " | |||
lv_ev_parcel_dir | TYPE EPSF-EPSDIRNAM, " | |||
lv_iv_parcel_extension | TYPE TEPSIN-EPSPCLEXT, " | |||
lv_build_directory_failed | TYPE TEPSIN, " | |||
lv_build_path_failed | TYPE TEPSIN, " | |||
lv_iv_eps_subdirectory | TYPE EPSF-EPSSUBDIR. " SPACE |
  CALL FUNCTION 'EPS_BUILD_PARCEL_NAME' " |
EXPORTING | ||
IV_PARCEL_ORIGIN | = lv_iv_parcel_origin | |
IV_PARCEL_NUMBER | = lv_iv_parcel_number | |
IV_PARCEL_EXTENSION | = lv_iv_parcel_extension | |
IV_EPS_SUBDIRECTORY | = lv_iv_eps_subdirectory | |
IMPORTING | ||
EV_PARCEL_NAME | = lv_ev_parcel_name | |
EV_PARCEL_PATH | = lv_ev_parcel_path | |
EV_PARCEL_DIR | = lv_ev_parcel_dir | |
EXCEPTIONS | ||
INVALID_EPS_SUBDIR = 1 | ||
SAPGPARAM_FAILED = 2 | ||
BUILD_DIRECTORY_FAILED = 3 | ||
BUILD_PATH_FAILED = 4 | ||
. " EPS_BUILD_PARCEL_NAME |
ABAP code using 7.40 inline data declarations to call FM EPS_BUILD_PARCEL_NAME
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 EPSFILNAM FROM EPSF INTO @DATA(ld_ev_parcel_name). | ||||
"SELECT single EPSPCLORI FROM TEPSIN INTO @DATA(ld_iv_parcel_origin). | ||||
"SELECT single EPSPATH FROM EPSF INTO @DATA(ld_ev_parcel_path). | ||||
"SELECT single EPSPCLNUM FROM TEPSIN INTO @DATA(ld_iv_parcel_number). | ||||
"SELECT single EPSDIRNAM FROM EPSF INTO @DATA(ld_ev_parcel_dir). | ||||
"SELECT single EPSPCLEXT FROM TEPSIN INTO @DATA(ld_iv_parcel_extension). | ||||
"SELECT single EPSSUBDIR FROM EPSF INTO @DATA(ld_iv_eps_subdirectory). | ||||
DATA(ld_iv_eps_subdirectory) | = ' '. | |||
Search for further information about these or an SAP related objects