SAP Function Modules
LXE_PCX_WRITE2 SAP Function module
LXE_PCX_WRITE2 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_PCX_WRITE2 into the relevant SAP transaction such as SE37 or SE80.
Associated Function Group:
LXE_PCX
Released Date:
Not Released
Processing type: Normal fucntion module
Pattern for FM LXE_PCX_WRITE2 - LXE PCX WRITE2
CALL FUNCTION 'LXE_PCX_WRITE2' "
EXPORTING
language = " lxeisolang
custmnr = " lxecustmnr
objtype = " lxeobjtype
objname = " lxeobjname
IMPORTING
pstatus = " lxestatprc
err_mess = " string
added_texts = " lxe_tt_pcx_tx_xml
changed_texts = " lxe_tt_pcx_tx_xml_change
removed_texts = " lxe_tt_pcx_tx_xml
TABLES
in_pcx_tx_xml = " lxe_pcx_tx_xml
. " LXE_PCX_WRITE2
ABAP code example for Function Module LXE_PCX_WRITE2
The ABAP code below is a full code listing to execute function module LXE_PCX_WRITE2 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_added_texts | TYPE LXE_TT_PCX_TX_XML , |
| ld_changed_texts | TYPE LXE_TT_PCX_TX_XML_CHANGE , |
| ld_removed_texts | TYPE LXE_TT_PCX_TX_XML , |
| it_in_pcx_tx_xml | TYPE STANDARD TABLE OF LXE_PCX_TX_XML,"TABLES PARAM |
| wa_in_pcx_tx_xml | LIKE LINE OF it_in_pcx_tx_xml . |
DATA(ld_language) = 'Check type of data required'.
DATA(ld_custmnr) = 'Check type of data required'.
DATA(ld_objtype) = 'Check type of data required'.
DATA(ld_objname) = 'Check type of data required'.
"populate fields of struture and append to itab
append wa_in_pcx_tx_xml to it_in_pcx_tx_xml. . CALL FUNCTION 'LXE_PCX_WRITE2' EXPORTING language = ld_language custmnr = ld_custmnr objtype = ld_objtype objname = ld_objname IMPORTING pstatus = ld_pstatus err_mess = ld_err_mess added_texts = ld_added_texts changed_texts = ld_changed_texts removed_texts = ld_removed_texts TABLES in_pcx_tx_xml = it_in_pcx_tx_xml . " LXE_PCX_WRITE2
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_language | TYPE LXEISOLANG , |
| it_in_pcx_tx_xml | TYPE STANDARD TABLE OF LXE_PCX_TX_XML , |
| wa_in_pcx_tx_xml | LIKE LINE OF it_in_pcx_tx_xml, |
| ld_err_mess | TYPE STRING , |
| ld_custmnr | TYPE LXECUSTMNR , |
| ld_added_texts | TYPE LXE_TT_PCX_TX_XML , |
| ld_objtype | TYPE LXEOBJTYPE , |
| ld_changed_texts | TYPE LXE_TT_PCX_TX_XML_CHANGE , |
| ld_objname | TYPE LXEOBJNAME , |
| ld_removed_texts | TYPE LXE_TT_PCX_TX_XML . |
ld_language = 'Check type of data required'.
"populate fields of struture and append to itab
append wa_in_pcx_tx_xml to it_in_pcx_tx_xml.
ld_custmnr = 'Check type of data required'.
ld_objtype = 'Check type of data required'.
ld_objname = '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_PCX_WRITE2 or its description.