SAP TREX_EXT_PE_REPOST Function Module for Repost

Search SAP Function Modules

TREX_EXT_PE_REPOST is a standard trex ext pe repost SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Repost 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 trex ext pe repost FM, simply by entering the name TREX_EXT_PE_REPOST into the relevant SAP transaction such as SE37 or SE38.

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

Function TREX_EXT_PE_REPOST 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 'TREX_EXT_PE_REPOST'"Repost
  EXPORTING
   I_SESSION_INDEX_ID =  "Planning: Session Index ID
   I_BASE_VIEW_ID =  "Calculation View Representing Planning Operation Result
   I_SOURCE_INDEX_ID =  "Index Id
*  I_SOURCE_VIEW_ID =  "Calculation View Representing Planning Operation Result
   I_KEYFIGURES =  "Attributes
   I_REPOST_MAPPINGS =  "Repost Join Attributes
*  I_FILTER_NAME =  "Attribute name
*  I_REPOST_FILTERS =  "Repost Filter

 IMPORTING
   E_RESULT_VIEW_ID =  "Calculation View Representing Planning Operation Result
   E_RESULT_VIEW_ID2 =  "
   E_RETURN_CODE =  "Returncode
   E_RETURN_TEXT =  "Rückgabetext

EXCEPTIONS
   CONVERSION_ERROR = 1 

.

IMPORTING Parameters details for TREX_EXT_PE_REPOST

I_SESSION_INDEX_ID - Planning: Session Index ID

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

I_BASE_VIEW_ID - Calculation View Representing Planning Operation Result

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

I_SOURCE_INDEX_ID - Index Id

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

I_SOURCE_VIEW_ID - Calculation View Representing Planning Operation Result

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

I_KEYFIGURES - Attributes

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

I_REPOST_MAPPINGS - Repost Join Attributes

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

I_FILTER_NAME - Attribute name

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

I_REPOST_FILTERS - Repost Filter

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

EXPORTING Parameters details for TREX_EXT_PE_REPOST

E_RESULT_VIEW_ID - Calculation View Representing Planning Operation Result

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

E_RESULT_VIEW_ID2 -

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

E_RETURN_CODE - Returncode

Data type: TREX_RFC-RETURN_CODE
Optional: No
Call by Reference: Yes

E_RETURN_TEXT - Rückgabetext

Data type: TREX_RFC-RETURN_TEXT
Optional: No
Call by Reference: Yes

EXCEPTIONS details

CONVERSION_ERROR - Error during conversion

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

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

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