SAP LXE_OBJ_EXIT_SAVE_STYL Function Module for Exit for SE76 (Save Form Translation)

Search SAP Function Modules

LXE_OBJ_EXIT_SAVE_STYL is a standard lxe obj exit save styl SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Exit for SE76 (Save Form Translation) 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 obj exit save styl FM, simply by entering the name LXE_OBJ_EXIT_SAVE_STYL into the relevant SAP transaction such as SE37 or SE38.

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

Function LXE_OBJ_EXIT_SAVE_STYL 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_OBJ_EXIT_SAVE_STYL'"Exit for SE76 (Save Form Translation)
  EXPORTING
   STYL_NAME =  "Style name
   SRC_LANG =  "Source Language
   TGT_LANG =  "Target Language

.

IMPORTING Parameters details for LXE_OBJ_EXIT_SAVE_STYL

STYL_NAME - Style name

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

SRC_LANG - Source Language

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

TGT_LANG - Target Language

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

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

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