SAP LXE_PC1_READ_HEADER Function Module for NOTRANSL: Lesen eines PC*-Gruppen-Headers









LXE_PC1_READ_HEADER is a standard lxe pc1 read header 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: Lesen eines PC*-Gruppen-Headers 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 read header FM, simply by entering the name LXE_PC1_READ_HEADER 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_READ_HEADER 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_READ_HEADER'"NOTRANSL: Lesen eines PC*-Gruppen-Headers
EXPORTING
CUSTMNR = "Customer Number
OBJNAME = "Name of Translation Object

IMPORTING
LS_PC_HD = "Header Data for PC* Objects
PSTATUS = "Process Status
EX_PC_AD = "

TABLES
* LT_PC_AP = "Texts for PCX Objects
.



IMPORTING Parameters details for LXE_PC1_READ_HEADER

CUSTMNR - Customer Number

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

OBJNAME - Name of Translation Object

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

EXPORTING Parameters details for LXE_PC1_READ_HEADER

LS_PC_HD - Header Data for PC* Objects

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

PSTATUS - Process Status

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

EX_PC_AD -

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

TABLES Parameters details for LXE_PC1_READ_HEADER

LT_PC_AP - Texts for PCX Objects

Data type: LXE_PC_AP
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for LXE_PC1_READ_HEADER 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_custmnr  TYPE LXECUSTMNR, "   
lv_ls_pc_hd  TYPE LXE_PC_HD, "   
lt_lt_pc_ap  TYPE STANDARD TABLE OF LXE_PC_AP, "   
lv_objname  TYPE LXEOBJNAME, "   
lv_pstatus  TYPE LXESTATPRC, "   
lv_ex_pc_ad  TYPE LXE_PC_AD_S. "   

  CALL FUNCTION 'LXE_PC1_READ_HEADER'  "NOTRANSL: Lesen eines PC*-Gruppen-Headers
    EXPORTING
         CUSTMNR = lv_custmnr
         OBJNAME = lv_objname
    IMPORTING
         LS_PC_HD = lv_ls_pc_hd
         PSTATUS = lv_pstatus
         EX_PC_AD = lv_ex_pc_ad
    TABLES
         LT_PC_AP = lt_lt_pc_ap
. " LXE_PC1_READ_HEADER




ABAP code using 7.40 inline data declarations to call FM LXE_PC1_READ_HEADER

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!