SAP TG_GET_PARALLEL_TRIPKEYS Function Module for

Search SAP Function Modules

TG_GET_PARALLEL_TRIPKEYS is a standard tg get parallel tripkeys 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 tg get parallel tripkeys FM, simply by entering the name TG_GET_PARALLEL_TRIPKEYS into the relevant SAP transaction such as SE37 or SE38.

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

Function TG_GET_PARALLEL_TRIPKEYS 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 'TG_GET_PARALLEL_TRIPKEYS'"
  EXPORTING
   EMPLOYEENUMBER =  "Personnel Number
   PERIODE_DAT_BEGIN =  "Start Date of Trip Segment
   PERIODE_UHR_BEGIN =  "Beginning Time of Trip Segment
   PERIODE_DAT_END =  "End Date of Trip Segment
   PERIODE_UHR_END =  "End Time of Trip Segment
*  NOGEN =  "

TABLES
   T_PERIO_KEY =  "Key for Travel Expenses Table PTRV_PERIO

EXCEPTIONS
   TABLE_PERIO_READ_ERROR = 1    NO_PARALLEL_TRIPS = 2 

.

IMPORTING Parameters details for TG_GET_PARALLEL_TRIPKEYS

EMPLOYEENUMBER - Personnel Number

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

PERIODE_DAT_BEGIN - Start Date of Trip Segment

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

PERIODE_UHR_BEGIN - Beginning Time of Trip Segment

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

PERIODE_DAT_END - End Date of Trip Segment

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

PERIODE_UHR_END - End Time of Trip Segment

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

NOGEN -

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

TABLES Parameters details for TG_GET_PARALLEL_TRIPKEYS

T_PERIO_KEY - Key for Travel Expenses Table PTRV_PERIO

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

EXCEPTIONS details

TABLE_PERIO_READ_ERROR -

Data type:
Optional: No
Call by Reference: Yes

NO_PARALLEL_TRIPS -

Data type:
Optional: No
Call by Reference: Yes

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

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