SAP PTRA_UTIL_MEM_GLOBALS_GET Function Module for

Search SAP Function Modules

PTRA_UTIL_MEM_GLOBALS_GET is a standard ptra util mem globals 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 ptra util mem globals get FM, simply by entering the name PTRA_UTIL_MEM_GLOBALS_GET into the relevant SAP transaction such as SE37 or SE38.

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

Function PTRA_UTIL_MEM_GLOBALS_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 'PTRA_UTIL_MEM_GLOBALS_GET'"
  EXPORTING
   I_EMPLOYEENUMBER =  "Personnel Number
   I_DATE =  "
*  I_TRIP_SCHEMA = '01' "Trip Schema

 IMPORTING
   E_MOREI =  "Trip Provision Variant
   E_T702N =  "
   E_T706D =  "
   E_MOLGA =  "Country Grouping
   E_TRVPA =  "Settlement Control Through Characteristic TRVPA
   E_TRVFD =  "Dialog Control Through Characteristic TRVFD
   E_TRVFE =  "Control of Travel Expense Form Through Characteristic TRVFE
   E_TRVFP =  "Control of Travel Planning Form Through Characteristic TRVFP
   E_TRVFR =  "Control of Travel Request Form Through Characteristic TRVFR
   E_PUBSEC_COUNTRY =  "Country Version of Public Sector
   E_TRVFK =  "

EXCEPTIONS
   ERROR_OCCURRED = 1 

.

IMPORTING Parameters details for PTRA_UTIL_MEM_GLOBALS_GET

I_EMPLOYEENUMBER - Personnel Number

Data type: BAPIEMPL-PERNR
Optional: No
Call by Reference: Yes

I_DATE -

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

I_TRIP_SCHEMA - Trip Schema

Data type: RSCHE
Default: '01'
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for PTRA_UTIL_MEM_GLOBALS_GET

E_MOREI - Trip Provision Variant

Data type: HEAD_PERIO-MOREI
Optional: No
Call by Reference: Yes

E_T702N -

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

E_T706D -

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

E_MOLGA - Country Grouping

Data type: HEAD_PERIO-MOLGA
Optional: No
Call by Reference: Yes

E_TRVPA - Settlement Control Through Characteristic TRVPA

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

E_TRVFD - Dialog Control Through Characteristic TRVFD

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

E_TRVFE - Control of Travel Expense Form Through Characteristic TRVFE

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

E_TRVFP - Control of Travel Planning Form Through Characteristic TRVFP

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

E_TRVFR - Control of Travel Request Form Through Characteristic TRVFR

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

E_PUBSEC_COUNTRY - Country Version of Public Sector

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

E_TRVFK -

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

EXCEPTIONS details

ERROR_OCCURRED - Errors have occurred

Data type:
Optional: No
Call by Reference: Yes

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