SAP EXIT_SAPLEC50_001 Function Module for IS-U move-in: dtermination of hedge amount and hedge reason
EXIT_SAPLEC50_001 is a standard exit saplec50 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 IS-U move-in: dtermination of hedge amount and hedge reason 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 saplec50 001 FM, simply by entering the name EXIT_SAPLEC50_001 into the relevant SAP transaction such as SE37 or SE38.
Function Group: XECE
Program Name: SAPLXECE
Main Program: SAPLXECE
Appliation area: E
Release date: 23-Oct-1998
Mode(Normal, Remote etc): Normal Function Module
Update:
Function EXIT_SAPLEC50_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_SAPLEC50_001'"IS-U move-in: dtermination of hedge amount and hedge reason.
EXPORTING
* X_EKUN = "Business Partner Data
* X_FKKVKP1 = "Contract Account Data
* X_EVER = "Contract Data
X_V_EANL = "Installation Data
* X_MOVEIN_EXT = "Move-In Data
IMPORTING
Y_REQUEST = "Amount of Cash Security Deposit
Y_WAERS = "Document Currency for Cash Security Deposit
Y_REASON = "Reason for Requesting Cash Security Deposit
Y_WAIVEREAS = "Reason for not Requesting a Deposit
Related Function Modules
Below is a list of related SAP function modules this CUSTOMER FUNCTION exit / user exit is relevant for.ISU_DB_EEIN_UPDATE_MAIN PRIVATE: Move-In Document and Contract Installation Allocation UPDATE
ISU_MI_BPCA_ACCOUNT_ENQUEUE INTERNAL: Put Contract Account for Move-In Document in Queue
ISU_MI_BPCA_VALID_DATE_GET INTERNAL: Determine Valid Change Date for Business Partner / Contract Acct
ISU_MI_BP_FOREIGN_INIT_CALL INTERNAL: Initialization of Business Partner
ISU_MI_CURRENCY_FILL INTERNAL: Fill Currency Field
ISU_MI_ENQUEUE_WAIT_SET
ISU_MI_METDOCS_PRINT INTERNAL: Print Meter Reading Documents in Move-In
ISU_MI_SUBOJECTS_PAI_AFTER INTERNAL: Run PAI_AFTER Module for Subobjects of Move-In
ISU_MI_SUBOJECTS_PAI_BEFORE INTERNAL: Run PAI_BEFORE Module for Subobjects of Move-In
ISU_MI_SUBOJECTS_PBO INTERNAL: Run PBO Module for Subobjects of Move-In
ISU_MOVE_IN_GET_ATTR_FROM_EXT PRIVATE: Make Move-In Attributes Available Externally
ISU_MOVE_IN_GET_BCONTCONF INTERN: Determine Class + Act. f. First Customer Contact to Report Move-In
ISU_O_MOVE_IN_CLOSE INTERNAL: Exits Object Processing
ISU_O_MOVE_IN_INPUT INTERNAL: Check Entries in Move-In
ISU_O_MOVE_IN_OPEN INTERNAL: Opens Processing of an Object
ISU_O_MOVE_IN_WORK INTERNAL: Calls Screen Dialog for Move-In Document
ISU_S_MOVE_IN_CANCEL INTERNAL: Reverse Move-In Document
ISU_S_MOVE_IN_CHANGE INTERNAL: Change Move-In Document
ISU_S_MOVE_IN_CREATE INTERNAL: Create Move-In Document
ISU_S_MOVE_IN_DATE_CHANGE INTERNAL: Change Move-In Date of a Move-In Document
ISU_S_MOVE_IN_DEREG_CLSTR_READ INTERNAL: Move-In/Deregulation: Determine Utility Units
ISU_S_MOVE_IN_DISPLAY INTERNAL: Display Move-In Document
ISU_S_MOVE_IN_INSTLN_ADD INTERNAL: Add Installations to Move-In Document
ISU_S_MOVE_IN_METDOCS_CHNGDATE INTERNAL: Change Move-In Document for Meter Reading Data
ISU_S_MOVE_IN_MR_STATUS_DETERM INTERNAL: Determine Status of Meter Reading Document at Installation Level
ISU_S_MOVE_IN_PROVIDE INTERNAL: Prepares Move-In Document for Processing
ISU_S_MOVE_IN_WLETTER_CREATE INTERNAL: Create Welcome Letter in Move-In
IMPORTING Parameters details for EXIT_SAPLEC50_001
X_EKUN - Business Partner Data
Data type: EKUN_EXTOptional: Yes
Call by Reference: No ( called with pass by value option)
X_FKKVKP1 - Contract Account Data
Data type: FKKVKP1Optional: Yes
Call by Reference: No ( called with pass by value option)
X_EVER - Contract Data
Data type: EVEROptional: Yes
Call by Reference: No ( called with pass by value option)
X_V_EANL - Installation Data
Data type: V_EANLOptional: No
Call by Reference: No ( called with pass by value option)
X_MOVEIN_EXT - Move-In Data
Data type: ISU06_MOVEIN_EXTOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for EXIT_SAPLEC50_001
Y_REQUEST - Amount of Cash Security Deposit
Data type: FKK_SEC_C-REQUESTOptional: No
Call by Reference: No ( called with pass by value option)
Y_WAERS - Document Currency for Cash Security Deposit
Data type: T001-WAERSOptional: No
Call by Reference: No ( called with pass by value option)
Y_REASON - Reason for Requesting Cash Security Deposit
Data type: FKK_SEC-REASONOptional: No
Call by Reference: No ( called with pass by value option)
Y_WAIVEREAS - Reason for not Requesting a Deposit
Data type: EEINV-SECWAIVEREASOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for EXIT_SAPLEC50_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: | ||||
lv_x_ekun | TYPE EKUN_EXT, " | |||
lv_y_request | TYPE FKK_SEC_C-REQUEST, " | |||
lv_y_waers | TYPE T001-WAERS, " | |||
lv_x_fkkvkp1 | TYPE FKKVKP1, " | |||
lv_x_ever | TYPE EVER, " | |||
lv_y_reason | TYPE FKK_SEC-REASON, " | |||
lv_x_v_eanl | TYPE V_EANL, " | |||
lv_y_waivereas | TYPE EEINV-SECWAIVEREAS, " | |||
lv_x_movein_ext | TYPE ISU06_MOVEIN_EXT. " |
  CALL FUNCTION 'EXIT_SAPLEC50_001' "IS-U move-in: dtermination of hedge amount and hedge reason |
EXPORTING | ||
X_EKUN | = lv_x_ekun | |
X_FKKVKP1 | = lv_x_fkkvkp1 | |
X_EVER | = lv_x_ever | |
X_V_EANL | = lv_x_v_eanl | |
X_MOVEIN_EXT | = lv_x_movein_ext | |
IMPORTING | ||
Y_REQUEST | = lv_y_request | |
Y_WAERS | = lv_y_waers | |
Y_REASON | = lv_y_reason | |
Y_WAIVEREAS | = lv_y_waivereas | |
. " EXIT_SAPLEC50_001 |
ABAP code using 7.40 inline data declarations to call FM EXIT_SAPLEC50_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."SELECT single REQUEST FROM FKK_SEC_C INTO @DATA(ld_y_request). | ||||
"SELECT single WAERS FROM T001 INTO @DATA(ld_y_waers). | ||||
"SELECT single REASON FROM FKK_SEC INTO @DATA(ld_y_reason). | ||||
"SELECT single SECWAIVEREAS FROM EEINV INTO @DATA(ld_y_waivereas). | ||||
Search for further information about these or an SAP related objects