SAP SEEF_GET_TP_MODE Function Module for
SEEF_GET_TP_MODE is a standard seef get tp mode 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 seef get tp mode FM, simply by entering the name SEEF_GET_TP_MODE into the relevant SAP transaction such as SE37 or SE38.
Function Group: ENH_VERSION_MANAGEMENT
Program Name: SAPLENH_VERSION_MANAGEMENT
Main Program: SAPLENH_WB_VO
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SEEF_GET_TP_MODE 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 'SEEF_GET_TP_MODE'".
EXPORTING
IV_TRKORR = "
IMPORTING
EV_TP_MODE = "
EXCEPTIONS
ERROR_READING_SPAM_QUEUE = 1 ERROR_READING_UPG_INFO = 2 WRONG_TP_ORDER = 3
IMPORTING Parameters details for SEEF_GET_TP_MODE
IV_TRKORR -
Data type: TRKORROptional: No
Call by Reference: Yes
EXPORTING Parameters details for SEEF_GET_TP_MODE
EV_TP_MODE -
Data type: SYCHAR01Optional: No
Call by Reference: Yes
EXCEPTIONS details
ERROR_READING_SPAM_QUEUE -
Data type:Optional: No
Call by Reference: Yes
ERROR_READING_UPG_INFO -
Data type:Optional: No
Call by Reference: Yes
WRONG_TP_ORDER -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for SEEF_GET_TP_MODE 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.| DATA: | ||||
| lv_iv_trkorr | TYPE TRKORR, " | |||
| lv_ev_tp_mode | TYPE SYCHAR01, " | |||
| lv_error_reading_spam_queue | TYPE SYCHAR01, " | |||
| lv_error_reading_upg_info | TYPE SYCHAR01, " | |||
| lv_wrong_tp_order | TYPE SYCHAR01. " |
|   CALL FUNCTION 'SEEF_GET_TP_MODE' " |
| EXPORTING | ||
| IV_TRKORR | = lv_iv_trkorr | |
| IMPORTING | ||
| EV_TP_MODE | = lv_ev_tp_mode | |
| EXCEPTIONS | ||
| ERROR_READING_SPAM_QUEUE = 1 | ||
| ERROR_READING_UPG_INFO = 2 | ||
| WRONG_TP_ORDER = 3 | ||
| . " SEEF_GET_TP_MODE | ||
ABAP code using 7.40 inline data declarations to call FM SEEF_GET_TP_MODE
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