SAP PTRM_REQUEST_SUBMIT Function Module for Check and save request in backend, retrieve trip number, trigger workflow

Search SAP Function Modules

PTRM_REQUEST_SUBMIT is a standard ptrm request submit SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Check and save request in backend, retrieve trip number, trigger workflow 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 ptrm request submit FM, simply by entering the name PTRM_REQUEST_SUBMIT into the relevant SAP transaction such as SE37 or SE38.

Function Group: PTRM_REQUEST
Program Name: SAPLPTRM_REQUEST
Main Program: SAPLPTRM_REQUEST
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function PTRM_REQUEST_SUBMIT 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_REQUEST_SUBMIT'"Check and save request in backend, retrieve trip number, trigger workflow
  EXPORTING
   I_EMPLOYEENUMBER =  "Personnel Number
*  I_TRIPNUMBER =  "Trip number if existing trip should be accessed
*  I_LANGUAGE = SY-LANGU "UI language, backend system default if blank
*  I_GENERAL_DATA =  "General Trip Data
*  IT_COST_DIST_TRIP =  "Cost Distribution of Trip

 IMPORTING
   E_TRIPNUMBER =  "Trip Number
   E_GENERAL_DATA =  "General Trip Data for External Display
   ET_COST_DIST_TRIP =  "Cost Distribution of Trip
   ET_RETURN =  "Table with BAPI return information: messages

.

IMPORTING Parameters details for PTRM_REQUEST_SUBMIT

I_EMPLOYEENUMBER - Personnel Number

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

I_TRIPNUMBER - Trip number if existing trip should be accessed

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

I_LANGUAGE - UI language, backend system default if blank

Data type: BAPITRVXXX-LANGU
Default: SY-LANGU
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_GENERAL_DATA - General Trip Data

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

IT_COST_DIST_TRIP - Cost Distribution of Trip

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

EXPORTING Parameters details for PTRM_REQUEST_SUBMIT

E_TRIPNUMBER - Trip Number

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

E_GENERAL_DATA - General Trip Data for External Display

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

ET_COST_DIST_TRIP - Cost Distribution of Trip

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

ET_RETURN - Table with BAPI return information: messages

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

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

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