SAP LXE_PC2_RFC_IMPORT_JAVA_X Function Module for









LXE_PC2_RFC_IMPORT_JAVA_X is a standard lxe pc2 rfc import java x 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 pc2 rfc import java x FM, simply by entering the name LXE_PC2_RFC_IMPORT_JAVA_X into the relevant SAP transaction such as SE37 or SE38.

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



Function LXE_PC2_RFC_IMPORT_JAVA_X 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_PC2_RFC_IMPORT_JAVA_X'"
  EXPORTING
   JAVALANG =  "
   DESCRIPTX =  "
   CUSTMNR =  "
   OBJNAME_X =  "
   COLLTYP =  "
   COLLNAM =  "
   DOMATYP =  "
   DOMANAM =  "
   DEVELOPERX =  "
   IN_PC_EXCHANGETX =  "

 IMPORTING
   EX_OBJNAME =  "
   PSTATUS =  "
   ERR_MESS =  "
.



IMPORTING Parameters details for LXE_PC2_RFC_IMPORT_JAVA_X

JAVALANG -

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

DESCRIPTX -

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

CUSTMNR -

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

OBJNAME_X -

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

COLLTYP -

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

COLLNAM -

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

DOMATYP -

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

DOMANAM -

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

DEVELOPERX -

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

IN_PC_EXCHANGETX -

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

EXPORTING Parameters details for LXE_PC2_RFC_IMPORT_JAVA_X

EX_OBJNAME -

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

PSTATUS -

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

ERR_MESS -

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

Copy and paste ABAP code example for LXE_PC2_RFC_IMPORT_JAVA_X 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_javalang  TYPE LXEJAVALANG, "   
lv_ex_objname  TYPE LXEOBJNAME, "   
lv_descriptx  TYPE LXE_XSTRING, "   
lv_custmnr  TYPE LXECUSTMNR, "   
lv_pstatus  TYPE LXESTATPRC, "   
lv_err_mess  TYPE STRING, "   
lv_objname_x  TYPE LXE_XSTRING, "   
lv_colltyp  TYPE LXECOLLTYP, "   
lv_collnam  TYPE LXECOLLNAM, "   
lv_domatyp  TYPE LXEDOMATYP, "   
lv_domanam  TYPE LXEDOMANAM, "   
lv_developerx  TYPE LXE_XSTRING, "   
lv_in_pc_exchangetx  TYPE LXE_PC_EXCHANGETX. "   

  CALL FUNCTION 'LXE_PC2_RFC_IMPORT_JAVA_X'  "
    EXPORTING
         JAVALANG = lv_javalang
         DESCRIPTX = lv_descriptx
         CUSTMNR = lv_custmnr
         OBJNAME_X = lv_objname_x
         COLLTYP = lv_colltyp
         COLLNAM = lv_collnam
         DOMATYP = lv_domatyp
         DOMANAM = lv_domanam
         DEVELOPERX = lv_developerx
         IN_PC_EXCHANGETX = lv_in_pc_exchangetx
    IMPORTING
         EX_OBJNAME = lv_ex_objname
         PSTATUS = lv_pstatus
         ERR_MESS = lv_err_mess
. " LXE_PC2_RFC_IMPORT_JAVA_X




ABAP code using 7.40 inline data declarations to call FM LXE_PC2_RFC_IMPORT_JAVA_X

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



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!