SAP TPM_THX_HDOC_SAVE_LOC Function Module for Save hdoc locally
TPM_THX_HDOC_SAVE_LOC is a standard tpm thx hdoc save loc SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Save hdoc locally 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 tpm thx hdoc save loc FM, simply by entering the name TPM_THX_HDOC_SAVE_LOC into the relevant SAP transaction such as SE37 or SE38.
Function Group: TPM_THX_UI
Program Name: SAPLTPM_THX_UI
Main Program: SAPLTPM_THX_UI
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function TPM_THX_HDOC_SAVE_LOC 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 'TPM_THX_HDOC_SAVE_LOC'"Save hdoc locally.
EXPORTING
IV_MSGNO = "Message Number
CHANGING
C_P_PROTOCOL_HANDLER = "Protocol Manager
* CT_HDOC = "Table type for HDOC display straucture
IMPORTING Parameters details for TPM_THX_HDOC_SAVE_LOC
IV_MSGNO - Message Number
Data type: SY-MSGNOOptional: No
Call by Reference: Yes
CHANGING Parameters details for TPM_THX_HDOC_SAVE_LOC
C_P_PROTOCOL_HANDLER - Protocol Manager
Data type: CL_PROTOCOL_HANDLER_TRPOptional: No
Call by Reference: Yes
CT_HDOC - Table type for HDOC display straucture
Data type: THXY_DISP_HDOCOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for TPM_THX_HDOC_SAVE_LOC 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_msgno | TYPE SY-MSGNO, " | |||
| lv_c_p_protocol_handler | TYPE CL_PROTOCOL_HANDLER_TRP, " | |||
| lv_ct_hdoc | TYPE THXY_DISP_HDOC. " |
|   CALL FUNCTION 'TPM_THX_HDOC_SAVE_LOC' "Save hdoc locally |
| EXPORTING | ||
| IV_MSGNO | = lv_iv_msgno | |
| CHANGING | ||
| C_P_PROTOCOL_HANDLER | = lv_c_p_protocol_handler | |
| CT_HDOC | = lv_ct_hdoc | |
| . " TPM_THX_HDOC_SAVE_LOC | ||
ABAP code using 7.40 inline data declarations to call FM TPM_THX_HDOC_SAVE_LOC
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.| "SELECT single MSGNO FROM SY INTO @DATA(ld_iv_msgno). | ||||
Search for further information about these or an SAP related objects