SAP EXIT_SAPLEC55_012 Function Module for IS-U Move-Out: User-Defined Checks

Search SAP Function Modules

EXIT_SAPLEC55_012 is a standard exit saplec55 012 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for IS-U Move-Out: User-Defined Checks 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 saplec55 012 FM, simply by entering the name EXIT_SAPLEC55_012 into the relevant SAP transaction such as SE37 or SE38.

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

Function EXIT_SAPLEC55_012 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_SAPLEC55_012'"IS-U Move-Out: User-Defined Checks
  EXPORTING
   X_MOVEOUT_EXT =  "Move-Out Data

 IMPORTING
   Y_SETFIELD =  "Field Name in Case of Error
   Y_SETLINE =  "Field in Case of Error (for Step Loops)

EXCEPTIONS
   INPUT_ERROR = 1 

.

Related Function Modules

Below is a list of related SAP function modules this CUSTOMER FUNCTION exit / user exit is relevant for.
ISU_O_MOVE_OUT_ACTION INTERNAL: Actions of Move-Out Processing
ISU_O_MOVE_OUT_CLOSE INTERNAL: Ends Processing of Move-Out Document
ISU_O_MOVE_OUT_DIALOG INTERNAL: Calls Screen Dialog for Move-Out Document
ISU_O_MOVE_OUT_INPUT INTERNAL: Checks and Transfers Entries
ISU_O_MOVE_OUT_INTERNAL_OPEN INTERNAL: Opens Move-Out Processing; Does not close if errors occur
ISU_O_MOVE_OUT_OPEN INTERNAL: Opens Processing of Move-Out Document
ISU_O_MOVE_OUT_PAI_AFTER INTERNAL: Closes the CALL SUBSCREEN PAI
ISU_O_MOVE_OUT_PAI_BEFORE INTERNAL: Prepares the CALL SUBSCREEN PAI
ISU_O_MOVE_OUT_PBO INTERNAL: Prepares the CALL SUBSCREEN PBO
ISU_O_MOVE_OUT_PREPARE_CLOSE INTERNAL: Prepares Move-Out Document for Closing
ISU_S_MOVE_OUT_CANCEL INTERNAL: Reverse Move-Out Document
ISU_S_MOVE_OUT_CHANGE INTERNAL: Change Move-Out Document
ISU_S_MOVE_OUT_CREATE INTERNAL: Create Move-Out Document
ISU_S_MOVE_OUT_DATE_CHANGE INTERNAL: Change Move-Out Date of a Move-Out Document
ISU_S_MOVE_OUT_DISPLAY INTERNAL: Display Move-Out Document
ISU_S_MOVE_OUT_GET_OBJECT INTERNAL: Ends Processing of Move-Out Document
ISU_S_MOVE_OUT_PROVIDE INTERNAL: Prepares Move-Out Document for Processing

IMPORTING Parameters details for EXIT_SAPLEC55_012

X_MOVEOUT_EXT - Move-Out Data

Data type: ISU06_MOVEOUT_EXT
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for EXIT_SAPLEC55_012

Y_SETFIELD - Field Name in Case of Error

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

Y_SETLINE - Field in Case of Error (for Step Loops)

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

EXCEPTIONS details

INPUT_ERROR - Error Found During Check

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

Copy and paste ABAP code example for EXIT_SAPLEC55_012 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_SAPLEC55_012

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