SAP PTRM_VERSION_TABLE_GET Function Module for

Search SAP Function Modules

PTRM_VERSION_TABLE_GET is a standard ptrm version table 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 ptrm version table get FM, simply by entering the name PTRM_VERSION_TABLE_GET into the relevant SAP transaction such as SE37 or SE38.

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

Function PTRM_VERSION_TABLE_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 'PTRM_VERSION_TABLE_GET'"
  EXPORTING
   I_EMPLOYEENUMBER =  "Personnel Number
   I_TRIPNUMBER =  "Trip Number
*  I_PERIODNUMBER = '000' "Number of Trip Period
*  I_TRIP_COMPONENT =  "Plan/Request/Expense Report (Indicator)
*  I_PERIODVERSION =  "Sequential Number of Period

 IMPORTING
   ET_VERSION =  "Version History Table
   ET_VERSION_EXT =  "Table Type for Version History Table with Texts
   EV_REQUEST_ARCHIV_DISPLAY =  "
   EV_EXPENSE_ARCHIV_DISPLAY =  "
   ET_RETURN =  "Table with BAPI Return Information

.

IMPORTING Parameters details for PTRM_VERSION_TABLE_GET

I_EMPLOYEENUMBER - Personnel Number

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

I_TRIPNUMBER - Trip Number

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

I_PERIODNUMBER - Number of Trip Period

Data type: PTRV_PEROD
Default: '000'
Optional: Yes
Call by Reference: Yes

I_TRIP_COMPONENT - Plan/Request/Expense Report (Indicator)

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

I_PERIODVERSION - Sequential Number of Period

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

EXPORTING Parameters details for PTRM_VERSION_TABLE_GET

ET_VERSION - Version History Table

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

ET_VERSION_EXT - Table Type for Version History Table with Texts

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

EV_REQUEST_ARCHIV_DISPLAY -

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

EV_EXPENSE_ARCHIV_DISPLAY -

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

ET_RETURN - Table with BAPI Return Information

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

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

ABAP code using 7.40 inline data declarations to call FM PTRM_VERSION_TABLE_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.

Search for further information about these or an SAP related objects