SAP LECI_UPDATE_RULES Function Module for NOTRANSL: Regelwerk zum Aufruf der Create/Change-Bausteine aus dem Dialog

Search SAP Function Modules

LECI_UPDATE_RULES is a standard leci update rules SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Regelwerk zum Aufruf der Create/Change-Bausteine aus dem Dialog 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 leci update rules FM, simply by entering the name LECI_UPDATE_RULES into the relevant SAP transaction such as SE37 or SE38.

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

Function LECI_UPDATE_RULES 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 'LECI_UPDATE_RULES'"NOTRANSL: Regelwerk zum Aufruf der Create/Change-Bausteine aus dem Dialog
  EXPORTING
   IS_EVENT_OLD =  "Activities Within the Check-in/Check-out Process
   IS_EVENT_DATA_OLD =  "Activity Data Within the Check-in/Check-out Process
   IF_SAVE_CODE =  "Screens, Function Code That Triggered PAI
   IF_DYNNUMBER =  "Text field, length 4

 IMPORTING
   ES_EVENT_DATA_NEW =  "Activity Data Within the Check-in/Check-out Process

CHANGING
   IS_TRA_PRO =  "Record Check-in Data for Means of Transport
   IS_PER_PRO =  "Record Check-in Data for Means of Transport

TABLES
*  ET_EVENT_NEW =  "Activities Within the Check-in/Check-out Process

.

IMPORTING Parameters details for LECI_UPDATE_RULES

IS_EVENT_OLD - Activities Within the Check-in/Check-out Process

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

IS_EVENT_DATA_OLD - Activity Data Within the Check-in/Check-out Process

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

IF_SAVE_CODE - Screens, Function Code That Triggered PAI

Data type: SY-UCOMM
Optional: No
Call by Reference: Yes

IF_DYNNUMBER - Text field, length 4

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

EXPORTING Parameters details for LECI_UPDATE_RULES

ES_EVENT_DATA_NEW - Activity Data Within the Check-in/Check-out Process

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

CHANGING Parameters details for LECI_UPDATE_RULES

IS_TRA_PRO - Record Check-in Data for Means of Transport

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

IS_PER_PRO - Record Check-in Data for Means of Transport

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

TABLES Parameters details for LECI_UPDATE_RULES

ET_EVENT_NEW - Activities Within the Check-in/Check-out Process

Data type: LECI_EVENT
Optional: Yes
Call by Reference: Yes

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

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