SAP LXE_CUSTMNR_SET_LOCK Function Module for LXE_CUSTMNR_SET_LOCK









LXE_CUSTMNR_SET_LOCK is a standard lxe custmnr set lock SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for LXE_CUSTMNR_SET_LOCK 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 lxe custmnr set lock FM, simply by entering the name LXE_CUSTMNR_SET_LOCK into the relevant SAP transaction such as SE37 or SE38.

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



Function LXE_CUSTMNR_SET_LOCK 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 'LXE_CUSTMNR_SET_LOCK'"LXE_CUSTMNR_SET_LOCK
EXPORTING
TRL_AREA = "Translation Area
* WITH_DATE = "Boolean
.



IMPORTING Parameters details for LXE_CUSTMNR_SET_LOCK

TRL_AREA - Translation Area

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

WITH_DATE - Boolean

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

Copy and paste ABAP code example for LXE_CUSTMNR_SET_LOCK 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_trl_area  TYPE LXECUSTMNR, "   
lv_with_date  TYPE LXEBOOL. "   

  CALL FUNCTION 'LXE_CUSTMNR_SET_LOCK'  "LXE_CUSTMNR_SET_LOCK
    EXPORTING
         TRL_AREA = lv_trl_area
         WITH_DATE = lv_with_date
. " LXE_CUSTMNR_SET_LOCK




ABAP code using 7.40 inline data declarations to call FM LXE_CUSTMNR_SET_LOCK

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!