SAP LXE_PP1_PROPOSAL_GET Function Module for









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

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



Function LXE_PP1_PROPOSAL_GET 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_GET'"
  EXPORTING
   S_LANG =  "ISO Language ID
   T_LANG =  "ISO Language ID
*  CUSTMNR =  "Customer Number
*  OBJTYPE =  "Type of Translation Object
   DOMATYP =  "Domain Type
   DOMANAM =  "Domain Name
   TEXT =  "Translation Unit for Short Text (Line)
*  UNITMLT = '255' "Maximum Length of Translation Unit

 IMPORTING
   P_TEXT =  "Translation Unit for Short Text (Line)
   P_STATUS =  "Default Status
   FND_PP =  "
   FND_PPA =  "

EXCEPTIONS
   INTERNAL_ERROR = 1
.



IMPORTING Parameters details for LXE_PP1_PROPOSAL_GET

S_LANG - ISO Language ID

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

T_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: No
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)

TEXT - Translation Unit for Short Text (Line)

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

UNITMLT - Maximum Length of Translation Unit

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

EXPORTING Parameters details for LXE_PP1_PROPOSAL_GET

P_TEXT - Translation Unit for Short Text (Line)

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

P_STATUS - Default Status

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

FND_PP -

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

FND_PPA -

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

EXCEPTIONS details

INTERNAL_ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for LXE_PP1_PROPOSAL_GET 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_p_text  TYPE LXEUNITLIN, "   
lv_s_lang  TYPE LXEISOLANG, "   
lv_internal_error  TYPE LXEISOLANG, "   
lv_t_lang  TYPE LXEISOLANG, "   
lv_p_status  TYPE LXEPP_STAT, "   
lv_fnd_pp  TYPE LXE_PP___1, "   
lv_custmnr  TYPE LXECUSTMNR, "   
lv_fnd_ppa  TYPE LXE_PPA__1, "   
lv_objtype  TYPE LXEOBJTYPE, "   
lv_domatyp  TYPE LXEDOMATYP, "   
lv_domanam  TYPE LXEDOMANAM, "   
lv_text  TYPE LXEUNITLIN, "   
lv_unitmlt  TYPE LXEUNITMLT. "   '255'

  CALL FUNCTION 'LXE_PP1_PROPOSAL_GET'  "
    EXPORTING
         S_LANG = lv_s_lang
         T_LANG = lv_t_lang
         CUSTMNR = lv_custmnr
         OBJTYPE = lv_objtype
         DOMATYP = lv_domatyp
         DOMANAM = lv_domanam
         TEXT = lv_text
         UNITMLT = lv_unitmlt
    IMPORTING
         P_TEXT = lv_p_text
         P_STATUS = lv_p_status
         FND_PP = lv_fnd_pp
         FND_PPA = lv_fnd_ppa
    EXCEPTIONS
        INTERNAL_ERROR = 1
. " LXE_PP1_PROPOSAL_GET




ABAP code using 7.40 inline data declarations to call FM LXE_PP1_PROPOSAL_GET

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


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!