SAP LXE_OBJ_CREATE_TRANSPORT_ENTRY Function Module for









LXE_OBJ_CREATE_TRANSPORT_ENTRY is a standard lxe obj create transport entry 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 obj create transport entry FM, simply by entering the name LXE_OBJ_CREATE_TRANSPORT_ENTRY into the relevant SAP transaction such as SE37 or SE38.

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



Function LXE_OBJ_CREATE_TRANSPORT_ENTRY 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_CREATE_TRANSPORT_ENTRY'"
  EXPORTING
   LANGUAGE =  "ISO Language ID
   CUSTMNR =  "Customer Number
   OBJTYPE =  "Type of Translation Object
   OBJNAME =  "Name of Translation Object
*  TABKEY =  "Object Name in Object List
*  ADD_TADIR = '' "Additional TADIR entries for non-SMODILOG relevant objects

 IMPORTING
   TADIR_OBJECT =  "
   TADIR_OBJ_NAME =  "
   PSTATUS =  "Process Status

TABLES
*  EX_E071 =  "Change & Transport System: Object Entries of Requests/Tasks
*  EX_E071K =  "Change & Transport System: Key Entries of Requests/Tasks
.



IMPORTING Parameters details for LXE_OBJ_CREATE_TRANSPORT_ENTRY

LANGUAGE - ISO Language ID

Data type: LXEISOLANG
Optional: No
Call by Reference: No ( called with pass by value option)

CUSTMNR - Customer Number

Data type: LXECUSTMNR
Optional: No
Call by Reference: No ( called with pass by value option)

OBJTYPE - Type of Translation Object

Data type: LXEOBJTYPE
Optional: No
Call by Reference: No ( called with pass by value option)

OBJNAME - Name of Translation Object

Data type: LXEOBJNAME
Optional: No
Call by Reference: No ( called with pass by value option)

TABKEY - Object Name in Object List

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

ADD_TADIR - Additional TADIR entries for non-SMODILOG relevant objects

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

EXPORTING Parameters details for LXE_OBJ_CREATE_TRANSPORT_ENTRY

TADIR_OBJECT -

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

TADIR_OBJ_NAME -

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

PSTATUS - Process Status

Data type: LXESTATPRC
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for LXE_OBJ_CREATE_TRANSPORT_ENTRY

EX_E071 - Change & Transport System: Object Entries of Requests/Tasks

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

EX_E071K - Change & Transport System: Key Entries of Requests/Tasks

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

Copy and paste ABAP code example for LXE_OBJ_CREATE_TRANSPORT_ENTRY 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:
lt_ex_e071  TYPE STANDARD TABLE OF E071, "   
lv_language  TYPE LXEISOLANG, "   
lv_tadir_object  TYPE TROBJTYPE, "   
lv_custmnr  TYPE LXECUSTMNR, "   
lt_ex_e071k  TYPE STANDARD TABLE OF E071K, "   
lv_tadir_obj_name  TYPE SOBJ_NAME, "   
lv_objtype  TYPE LXEOBJTYPE, "   
lv_pstatus  TYPE LXESTATPRC, "   
lv_objname  TYPE LXEOBJNAME, "   
lv_tabkey  TYPE TROBJ_NAME, "   
lv_add_tadir  TYPE CHAR1. "   ''

  CALL FUNCTION 'LXE_OBJ_CREATE_TRANSPORT_ENTRY'  "
    EXPORTING
         LANGUAGE = lv_language
         CUSTMNR = lv_custmnr
         OBJTYPE = lv_objtype
         OBJNAME = lv_objname
         TABKEY = lv_tabkey
         ADD_TADIR = lv_add_tadir
    IMPORTING
         TADIR_OBJECT = lv_tadir_object
         TADIR_OBJ_NAME = lv_tadir_obj_name
         PSTATUS = lv_pstatus
    TABLES
         EX_E071 = lt_ex_e071
         EX_E071K = lt_ex_e071k
. " LXE_OBJ_CREATE_TRANSPORT_ENTRY




ABAP code using 7.40 inline data declarations to call FM LXE_OBJ_CREATE_TRANSPORT_ENTRY

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_add_tadir) = ''.
 


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!