SAP LXE_PP1_HASH_CREATE Function Module for









LXE_PP1_HASH_CREATE is a standard lxe pp1 hash create SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 pp1 hash create FM, simply by entering the name LXE_PP1_HASH_CREATE into the relevant SAP transaction such as SE37 or SE38.

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



Function LXE_PP1_HASH_CREATE 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_PP1_HASH_CREATE'"
EXPORTING
LANGUAGE = "ISO Language ID
TEXT = "Translation Unit for Short Text (Line)
* INSERT_DB = '' "Single-Character Flag
* NO_ENQ = '' "

IMPORTING
HASH = "Hash
ENQ_COMMIT = "Single-Character Flag

EXCEPTIONS
INTERNAL_ERROR = 1
.



IMPORTING Parameters details for LXE_PP1_HASH_CREATE

LANGUAGE - ISO Language ID

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

TEXT - Translation Unit for Short Text (Line)

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

INSERT_DB - Single-Character Flag

Data type: CHAR1
Default: ''
Optional: Yes
Call by Reference: Yes

NO_ENQ -

Data type: CHAR1
Default: ''
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for LXE_PP1_HASH_CREATE

HASH - Hash

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

ENQ_COMMIT - Single-Character Flag

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

EXCEPTIONS details

INTERNAL_ERROR - Internal Error

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for LXE_PP1_HASH_CREATE 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_hash  TYPE LXE_PPHASH, "   
lv_language  TYPE LXEISOLANG, "   
lv_internal_error  TYPE LXEISOLANG, "   
lv_text  TYPE LXEUNITLIN, "   
lv_enq_commit  TYPE CHAR1, "   
lv_insert_db  TYPE CHAR1, "   ''
lv_no_enq  TYPE CHAR1. "   ''

  CALL FUNCTION 'LXE_PP1_HASH_CREATE'  "
    EXPORTING
         LANGUAGE = lv_language
         TEXT = lv_text
         INSERT_DB = lv_insert_db
         NO_ENQ = lv_no_enq
    IMPORTING
         HASH = lv_hash
         ENQ_COMMIT = lv_enq_commit
    EXCEPTIONS
        INTERNAL_ERROR = 1
. " LXE_PP1_HASH_CREATE




ABAP code using 7.40 inline data declarations to call FM LXE_PP1_HASH_CREATE

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.

 
 
 
 
 
DATA(ld_insert_db) = ''.
 
DATA(ld_no_enq) = ''.
 


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!