SAP LXE_PP_FILE_EXPORT_OBJECT_LIST Function Module for Export Proposal pool according to Object list

Search SAP Function Modules

LXE_PP_FILE_EXPORT_OBJECT_LIST is a standard lxe pp file export object list SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Export Proposal pool according to Object list 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 pp file export object list FM, simply by entering the name LXE_PP_FILE_EXPORT_OBJECT_LIST into the relevant SAP transaction such as SE37 or SE38.

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

Function LXE_PP_FILE_EXPORT_OBJECT_LIST 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_PP_FILE_EXPORT_OBJECT_LIST'"Export Proposal pool according to Object list
  EXPORTING
   S_LANG =  "ISO Language ID
   T_LANG =  "ISO Language ID
   FILEPATH =  "Unix File Output Path
*  OLD_LANG_KEY =  "Old keys
*  ADD_BEST =  "Add best proposal
   OBJECT_LIST =  "Reduced object list

 IMPORTING
   PP_TOTAL =  "
   PP_EXPORTED =  "
   PPA_TOTAL =  "
   PPA_EXPORTED =  "
   PPX_TOTAL =  "
   PPX_EXPORTED =  "

EXCEPTIONS
   INVALID_LANGUAGE = 1    FILE_OPEN_ERROR = 2    CONVERSION_ERROR = 3 

.

IMPORTING Parameters details for LXE_PP_FILE_EXPORT_OBJECT_LIST

S_LANG - ISO Language ID

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

T_LANG - ISO Language ID

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

FILEPATH - Unix File Output Path

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

OLD_LANG_KEY - Old keys

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

ADD_BEST - Add best proposal

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

OBJECT_LIST - Reduced object list

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

EXPORTING Parameters details for LXE_PP_FILE_EXPORT_OBJECT_LIST

PP_TOTAL -

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

PP_EXPORTED -

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

PPA_TOTAL -

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

PPA_EXPORTED -

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

PPX_TOTAL -

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

PPX_EXPORTED -

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

EXCEPTIONS details

INVALID_LANGUAGE -

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

FILE_OPEN_ERROR -

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

CONVERSION_ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for LXE_PP_FILE_EXPORT_OBJECT_LIST 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.

ABAP code using 7.40 inline data declarations to call FM LXE_PP_FILE_EXPORT_OBJECT_LIST

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