SAP LXE_PC1_XML_RFC_IMPORT Function Module for NOTRANSL: Import einer PC*-Gruppe per RFC
LXE_PC1_XML_RFC_IMPORT is a standard lxe pc1 xml rfc import 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: Import einer PC*-Gruppe per RFC 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 rfc import FM, simply by entering the name LXE_PC1_XML_RFC_IMPORT 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_RFC_IMPORT 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_RFC_IMPORT'"NOTRANSL: Import einer PC*-Gruppe per RFC.
EXPORTING
CUSTMNR = "Customer Number
* LANGUAGE = '++++' "ISO Language ID
XML_XSTRING = "
* SAVE_TO_DB = 'X' "Single-Character Flag
* COLLTYP = '' "
* COLLNAM = '' "
* DOMATYP = 'X' "
* OBJNAME = '' "
* IN_PC_AD = "
IMPORTING
PSTATUS = "Process Status
ERR_MESS = "
IMP_LANG = "ISO Language ID
IMP_NAME = "Name of Translation Object
TABLES
* LT_PCZ = "Transfer Structure for PCZ Objects
* LT_PCZ_TX_DUM = "Texts of PCZ Objects
IMPORTING Parameters details for LXE_PC1_XML_RFC_IMPORT
CUSTMNR - Customer Number
Data type: LXECUSTMNROptional: No
Call by Reference: No ( called with pass by value option)
LANGUAGE - ISO Language ID
Data type: LXEISOLANGDefault: '++++'
Optional: Yes
Call by Reference: No ( called with pass by value option)
XML_XSTRING -
Data type: XSTRINGOptional: No
Call by Reference: No ( called with pass by value option)
SAVE_TO_DB - Single-Character Flag
Data type: CHAR1Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
COLLTYP -
Data type: LXECOLLTYPDefault: ''
Optional: Yes
Call by Reference: No ( called with pass by value option)
COLLNAM -
Data type: LXECOLLNAMDefault: ''
Optional: Yes
Call by Reference: No ( called with pass by value option)
DOMATYP -
Data type: LXEDOMATYPDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
OBJNAME -
Data type: LXEOBJNAMEDefault: ''
Optional: Yes
Call by Reference: No ( called with pass by value option)
IN_PC_AD -
Data type: LXE_PC_AD_SOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for LXE_PC1_XML_RFC_IMPORT
PSTATUS - Process Status
Data type: LXESTATPRCOptional: No
Call by Reference: No ( called with pass by value option)
ERR_MESS -
Data type: STRINGOptional: No
Call by Reference: No ( called with pass by value option)
IMP_LANG - ISO Language ID
Data type: LXEISOLANGOptional: No
Call by Reference: No ( called with pass by value option)
IMP_NAME - Name of Translation Object
Data type: LXEOBJNAMEOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for LXE_PC1_XML_RFC_IMPORT
LT_PCZ - Transfer Structure for PCZ Objects
Data type: LXE_PCZOptional: Yes
Call by Reference: Yes
LT_PCZ_TX_DUM - Texts of PCZ Objects
Data type: LXE_PCZ_TXOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for LXE_PC1_XML_RFC_IMPORT 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_lt_pcz | TYPE STANDARD TABLE OF LXE_PCZ, " | |||
lv_custmnr | TYPE LXECUSTMNR, " | |||
lv_pstatus | TYPE LXESTATPRC, " | |||
lv_err_mess | TYPE STRING, " | |||
lv_language | TYPE LXEISOLANG, " '++++' | |||
lt_lt_pcz_tx_dum | TYPE STANDARD TABLE OF LXE_PCZ_TX, " | |||
lv_imp_lang | TYPE LXEISOLANG, " | |||
lv_xml_xstring | TYPE XSTRING, " | |||
lv_imp_name | TYPE LXEOBJNAME, " | |||
lv_save_to_db | TYPE CHAR1, " 'X' | |||
lv_colltyp | TYPE LXECOLLTYP, " '' | |||
lv_collnam | TYPE LXECOLLNAM, " '' | |||
lv_domatyp | TYPE LXEDOMATYP, " 'X' | |||
lv_objname | TYPE LXEOBJNAME, " '' | |||
lv_in_pc_ad | TYPE LXE_PC_AD_S. " |
  CALL FUNCTION 'LXE_PC1_XML_RFC_IMPORT' "NOTRANSL: Import einer PC*-Gruppe per RFC |
EXPORTING | ||
CUSTMNR | = lv_custmnr | |
LANGUAGE | = lv_language | |
XML_XSTRING | = lv_xml_xstring | |
SAVE_TO_DB | = lv_save_to_db | |
COLLTYP | = lv_colltyp | |
COLLNAM | = lv_collnam | |
DOMATYP | = lv_domatyp | |
OBJNAME | = lv_objname | |
IN_PC_AD | = lv_in_pc_ad | |
IMPORTING | ||
PSTATUS | = lv_pstatus | |
ERR_MESS | = lv_err_mess | |
IMP_LANG | = lv_imp_lang | |
IMP_NAME | = lv_imp_name | |
TABLES | ||
LT_PCZ | = lt_lt_pcz | |
LT_PCZ_TX_DUM | = lt_lt_pcz_tx_dum | |
. " LXE_PC1_XML_RFC_IMPORT |
ABAP code using 7.40 inline data declarations to call FM LXE_PC1_XML_RFC_IMPORT
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_language) | = '++++'. | |||
DATA(ld_save_to_db) | = 'X'. | |||
DATA(ld_colltyp) | = ''. | |||
DATA(ld_collnam) | = ''. | |||
DATA(ld_domatyp) | = 'X'. | |||
DATA(ld_objname) | = ''. | |||
Search for further information about these or an SAP related objects