SAP LXE_PC1_XML_FILE_EXPORT_FIX Function Module for NOTRANSL: Export einer PC*-Gruppe in lokale Datei (fixer Kunde)









LXE_PC1_XML_FILE_EXPORT_FIX is a standard lxe pc1 xml file export fix 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: Export einer PC*-Gruppe in lokale Datei (fixer Kunde) 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 pc1 xml file export fix FM, simply by entering the name LXE_PC1_XML_FILE_EXPORT_FIX into the relevant SAP transaction such as SE37 or SE38.

Function Group: LXE_PC1
Program Name: SAPLLXE_PC1
Main Program: SAPLLXE_PC1
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function LXE_PC1_XML_FILE_EXPORT_FIX 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_PC1_XML_FILE_EXPORT_FIX'"NOTRANSL: Export einer PC*-Gruppe in lokale Datei (fixer Kunde)
EXPORTING
LANGUAGE = "ISO Language ID
OBJNAME = "Name of Translation Object
* CODING = 'UTF-8' "
* USE_SIMPLE_LANG = 'X' "
.



IMPORTING Parameters details for LXE_PC1_XML_FILE_EXPORT_FIX

LANGUAGE - ISO Language ID

Data type: LXEISOLANG
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)

CODING -

Data type: STRING
Default: 'UTF-8'
Optional: Yes
Call by Reference: No ( called with pass by value option)

USE_SIMPLE_LANG -

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

Copy and paste ABAP code example for LXE_PC1_XML_FILE_EXPORT_FIX 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_language  TYPE LXEISOLANG, "   
lv_objname  TYPE LXEOBJNAME, "   
lv_coding  TYPE STRING, "   'UTF-8'
lv_use_simple_lang  TYPE CHAR1. "   'X'

  CALL FUNCTION 'LXE_PC1_XML_FILE_EXPORT_FIX'  "NOTRANSL: Export einer PC*-Gruppe in lokale Datei (fixer Kunde)
    EXPORTING
         LANGUAGE = lv_language
         OBJNAME = lv_objname
         CODING = lv_coding
         USE_SIMPLE_LANG = lv_use_simple_lang
. " LXE_PC1_XML_FILE_EXPORT_FIX




ABAP code using 7.40 inline data declarations to call FM LXE_PC1_XML_FILE_EXPORT_FIX

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_coding) = 'UTF-8'.
 
DATA(ld_use_simple_lang) = 'X'.
 


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!