SAP LXE_PP1_PROPOSAL_EDIT_SE63 Function Module for









LXE_PP1_PROPOSAL_EDIT_SE63 is a standard lxe pp1 proposal edit se63 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 pp1 proposal edit se63 FM, simply by entering the name LXE_PP1_PROPOSAL_EDIT_SE63 into the relevant SAP transaction such as SE37 or SE38.

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



Function LXE_PP1_PROPOSAL_EDIT_SE63 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_PP1_PROPOSAL_EDIT_SE63'"
  EXPORTING
   T_LANG =  "ISO Language ID
*  DIRECT_STATUS =  "
   S_LANG =  "ISO Language ID
*  CUSTMNR =  "Customer Number
*  OBJTYPE =  "Type of Translation Object
*  DOMATYP =  "Domain Type
   DOMANAM =  "Domain Name
   PCX_S1 =  "Text Pairs
*  POPUP = '' "
*  DIRECT_COMMAND =  "

 IMPORTING
   STATTRN =  "Translation Status
   T_TEXT =  "Translation Unit for Short Text (Line)
   PSTATUS =  "Process Status
.



IMPORTING Parameters details for LXE_PP1_PROPOSAL_EDIT_SE63

T_LANG - ISO Language ID

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

DIRECT_STATUS -

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

S_LANG - ISO Language ID

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

CUSTMNR - Customer Number

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

OBJTYPE - Type of Translation Object

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

DOMATYP - Domain Type

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

DOMANAM - Domain Name

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

PCX_S1 - Text Pairs

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

POPUP -

Data type: CHAR1
Default: ''
Optional: Yes
Call by Reference: Yes

DIRECT_COMMAND -

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

EXPORTING Parameters details for LXE_PP1_PROPOSAL_EDIT_SE63

STATTRN - Translation Status

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

T_TEXT - Translation Unit for Short Text (Line)

Data type: LXEUNITLIN
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)

Copy and paste ABAP code example for LXE_PP1_PROPOSAL_EDIT_SE63 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_t_lang  TYPE LXEISOLANG, "   
lv_stattrn  TYPE LXESTATTRN, "   
lv_direct_status  TYPE LXEPP_STAT, "   
lv_s_lang  TYPE LXEISOLANG, "   
lv_t_text  TYPE LXEUNITLIN, "   
lv_custmnr  TYPE LXECUSTMNR, "   
lv_pstatus  TYPE LXESTATPRC, "   
lv_objtype  TYPE LXEOBJTYPE, "   
lv_domatyp  TYPE LXEDOMATYP, "   
lv_domanam  TYPE LXEDOMANAM, "   
lv_pcx_s1  TYPE LXE_PCX_S1, "   
lv_popup  TYPE CHAR1, "   ''
lv_direct_command  TYPE CHAR4. "   

  CALL FUNCTION 'LXE_PP1_PROPOSAL_EDIT_SE63'  "
    EXPORTING
         T_LANG = lv_t_lang
         DIRECT_STATUS = lv_direct_status
         S_LANG = lv_s_lang
         CUSTMNR = lv_custmnr
         OBJTYPE = lv_objtype
         DOMATYP = lv_domatyp
         DOMANAM = lv_domanam
         PCX_S1 = lv_pcx_s1
         POPUP = lv_popup
         DIRECT_COMMAND = lv_direct_command
    IMPORTING
         STATTRN = lv_stattrn
         T_TEXT = lv_t_text
         PSTATUS = lv_pstatus
. " LXE_PP1_PROPOSAL_EDIT_SE63




ABAP code using 7.40 inline data declarations to call FM LXE_PP1_PROPOSAL_EDIT_SE63

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_popup) = ''.
 
 


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!