SAP Function Modules
LXE_PC2_RFC_EXPORT_NW_X SAP Function module
LXE_PC2_RFC_EXPORT_NW_X is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.
See here to view full function module documentation and code listing, simply by entering the name LXE_PC2_RFC_EXPORT_NW_X into the relevant SAP transaction such as SE37 or SE80.
Associated Function Group:
LXE_PC2
Released Date:
Not Released
Processing type: Remote-Enabled
Pattern for FM LXE_PC2_RFC_EXPORT_NW_X - LXE PC2 RFC EXPORT NW X
CALL FUNCTION 'LXE_PC2_RFC_EXPORT_NW_X' "
EXPORTING
lang = " lxeisolang
custmnr = " lxecustmnr
objname_x = " lxe_xstring
IMPORTING
pstatus = " lxestatprc
err_mess = " string
ex_objname = " lxeobjname
ex_orig_lang = " lxeisolang
ex_collnam = " lxecollnam
ex_domanam = " lxedomanam
ex_developerx = " lxe_xstring
ex_descriptx = " lxe_xstring
ex_pc_exchangetx = " lxe_pc_exchangetx
. " LXE_PC2_RFC_EXPORT_NW_X
ABAP code example for Function Module LXE_PC2_RFC_EXPORT_NW_X
The ABAP code below is a full code listing to execute function module LXE_PC2_RFC_EXPORT_NW_X including all data declarations. The code uses 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 original method of declaring data variables up front. 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).
| ld_pstatus | TYPE LXESTATPRC , |
| ld_err_mess | TYPE STRING , |
| ld_ex_objname | TYPE LXEOBJNAME , |
| ld_ex_orig_lang | TYPE LXEISOLANG , |
| ld_ex_collnam | TYPE LXECOLLNAM , |
| ld_ex_domanam | TYPE LXEDOMANAM , |
| ld_ex_developerx | TYPE LXE_XSTRING , |
| ld_ex_descriptx | TYPE LXE_XSTRING , |
| ld_ex_pc_exchangetx | TYPE LXE_PC_EXCHANGETX . |
DATA(ld_lang) = 'Check type of data required'.
DATA(ld_custmnr) = 'Check type of data required'.
DATA(ld_objname_x) = 'Check type of data required'. . CALL FUNCTION 'LXE_PC2_RFC_EXPORT_NW_X' EXPORTING lang = ld_lang custmnr = ld_custmnr objname_x = ld_objname_x IMPORTING pstatus = ld_pstatus err_mess = ld_err_mess ex_objname = ld_ex_objname ex_orig_lang = ld_ex_orig_lang ex_collnam = ld_ex_collnam ex_domanam = ld_ex_domanam ex_developerx = ld_ex_developerx ex_descriptx = ld_ex_descriptx ex_pc_exchangetx = ld_ex_pc_exchangetx . " LXE_PC2_RFC_EXPORT_NW_X
IF SY-SUBRC EQ 0. "All OK ENDIF.
ABAP code to compare 7.40 inline data declaration with original syntax
The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.
DATA:
| ld_pstatus | TYPE LXESTATPRC , |
| ld_lang | TYPE LXEISOLANG , |
| ld_err_mess | TYPE STRING , |
| ld_custmnr | TYPE LXECUSTMNR , |
| ld_ex_objname | TYPE LXEOBJNAME , |
| ld_objname_x | TYPE LXE_XSTRING , |
| ld_ex_orig_lang | TYPE LXEISOLANG , |
| ld_ex_collnam | TYPE LXECOLLNAM , |
| ld_ex_domanam | TYPE LXEDOMANAM , |
| ld_ex_developerx | TYPE LXE_XSTRING , |
| ld_ex_descriptx | TYPE LXE_XSTRING , |
| ld_ex_pc_exchangetx | TYPE LXE_PC_EXCHANGETX . |
ld_lang = 'Check type of data required'.
ld_custmnr = 'Check type of data required'.
ld_objname_x = 'Check type of data required'.
Contribute (Add Comments)
Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name LXE_PC2_RFC_EXPORT_NW_X or its description.