SAP TP_1G_DELETE_PNR Function Module for
TP_1G_DELETE_PNR is a standard tp 1g delete pnr 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 tp 1g delete pnr FM, simply by entering the name TP_1G_DELETE_PNR into the relevant SAP transaction such as SE37 or SE38.
Function Group: FITP_GALILEO_GENERAL
Program Name: SAPLFITP_GALILEO_GENERAL
Main Program: SAPLFITP_GALILEO_GENERAL
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function TP_1G_DELETE_PNR 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 'TP_1G_DELETE_PNR'".
EXPORTING
CONTEXT_NUMBER = "Context
REC_LOC = "Passenger Name Record Locator
EXCEPTIONS
NO_DESTINATION = 1 INVALID_CONTEXT = 2 CONNECTION_ERROR = 3 RFC_ERROR = 4 GENERAL_API_ERROR = 5 NO_SEGMENTS_TO_CANCEL = 6
IMPORTING Parameters details for TP_1G_DELETE_PNR
CONTEXT_NUMBER - Context
Data type: FTPT_VARIANT-VARIANTOptional: No
Call by Reference: No ( called with pass by value option)
REC_LOC - Passenger Name Record Locator
Data type: FTPT_VARIANT-REC_LOCATOROptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_DESTINATION -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INVALID_CONTEXT - Invalid context
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
CONNECTION_ERROR - Connection Error
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
RFC_ERROR - RFC error
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
GENERAL_API_ERROR - General API error
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_SEGMENTS_TO_CANCEL -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for TP_1G_DELETE_PNR 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_context_number | TYPE FTPT_VARIANT-VARIANT, " | |||
| lv_no_destination | TYPE FTPT_VARIANT, " | |||
| lv_rec_loc | TYPE FTPT_VARIANT-REC_LOCATOR, " | |||
| lv_invalid_context | TYPE FTPT_VARIANT, " | |||
| lv_connection_error | TYPE FTPT_VARIANT, " | |||
| lv_rfc_error | TYPE FTPT_VARIANT, " | |||
| lv_general_api_error | TYPE FTPT_VARIANT, " | |||
| lv_no_segments_to_cancel | TYPE FTPT_VARIANT. " |
|   CALL FUNCTION 'TP_1G_DELETE_PNR' " |
| EXPORTING | ||
| CONTEXT_NUMBER | = lv_context_number | |
| REC_LOC | = lv_rec_loc | |
| EXCEPTIONS | ||
| NO_DESTINATION = 1 | ||
| INVALID_CONTEXT = 2 | ||
| CONNECTION_ERROR = 3 | ||
| RFC_ERROR = 4 | ||
| GENERAL_API_ERROR = 5 | ||
| NO_SEGMENTS_TO_CANCEL = 6 | ||
| . " TP_1G_DELETE_PNR | ||
ABAP code using 7.40 inline data declarations to call FM TP_1G_DELETE_PNR
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 VARIANT FROM FTPT_VARIANT INTO @DATA(ld_context_number). | ||||
| "SELECT single REC_LOCATOR FROM FTPT_VARIANT INTO @DATA(ld_rec_loc). | ||||
Search for further information about these or an SAP related objects