SAP EXIT_SAPLE10U_001 Function Module for Customer Exit: Check Source Lots when Merging Lots
EXIT_SAPLE10U_001 is a standard exit saple10u 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 Customer Exit: Check Source Lots when Merging Lots 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 saple10u 001 FM, simply by entering the name EXIT_SAPLE10U_001 into the relevant SAP transaction such as SE37 or SE38.
Function Group: X10T
Program Name: SAPLX10T
Main Program: SAPLX10T
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function EXIT_SAPLE10U_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_SAPLE10U_001'"Customer Exit: Check Source Lots when Merging Lots.
EXPORTING
X_DEST_LOT = "Sample Lot - Target
TABLES
T_SRC_LOTS = "Sample Lot - Source
EXCEPTIONS
LOT_NOT_ALLOWED = 1
Related Function Modules
Below is a list of related SAP function modules this CUSTOMER FUNCTION exit / user exit is relevant for.ISU_BW_LOT_BACKGROUND_PROC For Background Task
ISU_BW_LOT_PARALLEL_PROCESSING RFC for Parallel BW Extraction
ISU_DB_TE271E_UPDATE
ISU_LOT_OBJECT_PUBLISH Publish Current Object for Generic Object Services
ISU_O_LOT_ACTION INTERNAL: Actions of Subscreen LOT
ISU_O_LOT_CLOSE INTERNAL: Ends Processing of an Object from Category LOT
ISU_O_LOT_INPUT INTERNAL: Checks and Transfers Entries
ISU_O_LOT_OPEN INTERNAL: Opens an Instance of Class LOT
ISU_O_LOT_PAI_AFTER INTERNAL: Closes the CALL SUBSCREEN PAI
ISU_O_LOT_PAI_BEFORE INTERNAL: Prepares the CALL SUBSCREEN PAI
ISU_O_LOT_PBO INTERNAL: Prepares the CALL SUBSCREEN PBO
ISU_O_LOT_PREPARE_CLOSE INTERNAL: PREPARE Module for Object
ISU_O_LOT_STATUS INTERNAL: STATUS Module for Object Class
ISU_S_LOT_CHANGE INTERNAL: Change Lot
ISU_S_LOT_CREATE INTERNAL: Create Lot
ISU_S_LOT_DISPLAY INTERNAL: Display Lot
IMPORTING Parameters details for EXIT_SAPLE10U_001
X_DEST_LOT - Sample Lot - Target
Data type: TE271Optional: No
Call by Reference: Yes
TABLES Parameters details for EXIT_SAPLE10U_001
T_SRC_LOTS - Sample Lot - Source
Data type: TE271Optional: No
Call by Reference: Yes
EXCEPTIONS details
LOT_NOT_ALLOWED - Specified Lots Not permitted
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for EXIT_SAPLE10U_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.DATA: | ||||
lt_t_src_lots | TYPE STANDARD TABLE OF TE271, " | |||
lv_x_dest_lot | TYPE TE271, " | |||
lv_lot_not_allowed | TYPE TE271. " |
  CALL FUNCTION 'EXIT_SAPLE10U_001' "Customer Exit: Check Source Lots when Merging Lots |
EXPORTING | ||
X_DEST_LOT | = lv_x_dest_lot | |
TABLES | ||
T_SRC_LOTS | = lt_t_src_lots | |
EXCEPTIONS | ||
LOT_NOT_ALLOWED = 1 | ||
. " EXIT_SAPLE10U_001 |
ABAP code using 7.40 inline data declarations to call FM EXIT_SAPLE10U_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