SAP EXIT_SAPLE10T_001 Function Module for User Exit: Periodic Replacement

Search SAP Function Modules

EXIT_SAPLE10T_001 is a standard exit saple10t 001 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for User Exit: Periodic Replacement 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 exit saple10t 001 FM, simply by entering the name EXIT_SAPLE10T_001 into the relevant SAP transaction such as SE37 or SE38.

Function Group: X10T
Program Name: SAPLX10T
Main Program: SAPLX10T
Appliation area: E
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function EXIT_SAPLE10T_001 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 'EXIT_SAPLE10T_001'"User Exit: Periodic Replacement
  EXPORTING
   X_V_EGER =  "Structure with device data
*  X_COUNTRY =  "Country key
*  X_CITY_CODE =  "City Key
*  X_STREETCODE =  "Street Key
*  X_REGIOGROUP =  "Region.Group
*  X_UIB =  "Company area

 IMPORTING
   Y_EGTUR_CI =  "Structure with ci_egtur and dummy

.

Related Function Modules

Below is a list of related SAP function modules this CUSTOMER FUNCTION exit / user exit is relevant for.
ISU_DB_EGTUR_HEAD_SINGLE INTERNAL: Read EGTUR_HEAD (Direct Access)
ISU_DB_EGTUR_HEAD_UPDATE INTERNAL: Update EGTUR_HEAD
ISU_DB_EGTUR_SELECT INTERNAL: Read EGTUR (Mass Access)
ISU_DB_EGTUR_SELECT_CUSTOMIZED INTERNAL: Read EGTUR by Fields Filled in Customizing
ISU_DB_EGTUR_SELECT_CUST_ALL INTERNAL: Read All EGTUR by Fields Filled in Customizing
ISU_DB_EGTUR_SELECT_DYNAMIC INTERNAL: Read EGTUR with Dynamically Created Selection Conditions
ISU_DB_EGTUR_SELECT_DYN_ALL INTERNAL: Read All EGTUR with Dynamically Created Selection Conditions
ISU_DB_EGTUR_SINGLE INTERNAL: Read EGTUR (Direct Access)
ISU_DB_EGTUR_UPDATE INTERNAL: Update EGTUR
ISU_DB_TE683_SELECT_VARIANT INTERNAL: Read TE683 (Mass Access)
ISU_DB_TE683_UPDATE INTERNAL: Update TE683
ISU_EGTUR_PARALLEL_PROCESSING INTERNAL: Parallel Processing for Periodic Replacement
ISU_EGTUR_RESET_AUSBDAT INTERNAL: Reset Removal Date in EGTUR (Reverse Removal)
ISU_EGTUR_SET_AUFTRAG INTERNAL: Set Order in EGTUR
ISU_EGTUR_SET_AUSBDAT INTERNAL: Set Removal Date in EGTUR
ISU_EGTUR_SET_MELDUNG INTERNAL: Set Message in EGTUR
ISU_PERIODIC_REPLACEMENT_CRT INTERNAL: Create Periodic Replacement List

IMPORTING Parameters details for EXIT_SAPLE10T_001

X_V_EGER - Structure with device data

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

X_COUNTRY - Country key

Data type: EADRDAT-COUNTRY
Optional: Yes
Call by Reference: No ( called with pass by value option)

X_CITY_CODE - City Key

Data type: EADRDAT-CITY_CODE
Optional: Yes
Call by Reference: No ( called with pass by value option)

X_STREETCODE - Street Key

Data type: EADRDAT-STREETCODE
Optional: Yes
Call by Reference: No ( called with pass by value option)

X_REGIOGROUP - Region.Group

Data type: ADRC-REGIOGROUP
Optional: Yes
Call by Reference: No ( called with pass by value option)

X_UIB - Company area

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

EXPORTING Parameters details for EXIT_SAPLE10T_001

Y_EGTUR_CI - Structure with ci_egtur and dummy

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

Copy and paste ABAP code example for EXIT_SAPLE10T_001 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.

ABAP code using 7.40 inline data declarations to call FM EXIT_SAPLE10T_001

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