SAP LXE_PCZ_WRITE2 Function Module for NOTRANSL: Schreiben eines PCZ Objektes auf die Datenbank









LXE_PCZ_WRITE2 is a standard lxe pcz write2 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: Schreiben eines PCZ Objektes auf die Datenbank 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 pcz write2 FM, simply by entering the name LXE_PCZ_WRITE2 into the relevant SAP transaction such as SE37 or SE38.

Function Group: LXE_PCZ
Program Name: SAPLLXE_PCZ
Main Program: SAPLLXE_PCZ
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function LXE_PCZ_WRITE2 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_PCZ_WRITE2'"NOTRANSL: Schreiben eines PCZ Objektes auf die Datenbank
  EXPORTING
   LANGUAGE =  "Translation Language
   CUSTMNR =  "Translation Area
   OBJTYPE =  "Type of Translation Object
   OBJNAME =  "Name of Translation Object
*  UPDATE_ONLY = '' "Single-Character Flag
*  SLANG = '' "Translation Language

 IMPORTING
   PSTATUS =  "Process Status
   ERR_MESS =  "Predefined Type

TABLES
   IN_PCZ_TX_XML =  "Texts of PCZ Objects
*  LT_DUMTA3 =  "Dummy Structure for Versioning
.



IMPORTING Parameters details for LXE_PCZ_WRITE2

LANGUAGE - Translation Language

Data type: LXEISOLANG
Optional: No
Call by Reference: Yes

CUSTMNR - Translation Area

Data type: LXECUSTMNR
Optional: No
Call by Reference: Yes

OBJTYPE - Type of Translation Object

Data type: LXEOBJTYPE
Optional: No
Call by Reference: Yes

OBJNAME - Name of Translation Object

Data type: LXEOBJNAME
Optional: No
Call by Reference: Yes

UPDATE_ONLY - Single-Character Flag

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

SLANG - Translation Language

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

EXPORTING Parameters details for LXE_PCZ_WRITE2

PSTATUS - Process Status

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

ERR_MESS - Predefined Type

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

TABLES Parameters details for LXE_PCZ_WRITE2

IN_PCZ_TX_XML - Texts of PCZ Objects

Data type: LXE_PCZ_TX_XML
Optional: No
Call by Reference: Yes

LT_DUMTA3 - Dummy Structure for Versioning

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

Copy and paste ABAP code example for LXE_PCZ_WRITE2 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_pstatus  TYPE LXESTATPRC, "   
lv_language  TYPE LXEISOLANG, "   
lt_in_pcz_tx_xml  TYPE STANDARD TABLE OF LXE_PCZ_TX_XML, "   
lv_custmnr  TYPE LXECUSTMNR, "   
lv_err_mess  TYPE STRING, "   
lt_lt_dumta3  TYPE STANDARD TABLE OF LXE_DUMTA3, "   
lv_objtype  TYPE LXEOBJTYPE, "   
lv_objname  TYPE LXEOBJNAME, "   
lv_update_only  TYPE CHAR1, "   ''
lv_slang  TYPE LXEISOLANG. "   ''

  CALL FUNCTION 'LXE_PCZ_WRITE2'  "NOTRANSL: Schreiben eines PCZ Objektes auf die Datenbank
    EXPORTING
         LANGUAGE = lv_language
         CUSTMNR = lv_custmnr
         OBJTYPE = lv_objtype
         OBJNAME = lv_objname
         UPDATE_ONLY = lv_update_only
         SLANG = lv_slang
    IMPORTING
         PSTATUS = lv_pstatus
         ERR_MESS = lv_err_mess
    TABLES
         IN_PCZ_TX_XML = lt_in_pcz_tx_xml
         LT_DUMTA3 = lt_lt_dumta3
. " LXE_PCZ_WRITE2




ABAP code using 7.40 inline data declarations to call FM LXE_PCZ_WRITE2

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_update_only) = ''.
 
DATA(ld_slang) = ''.
 


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!