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

Function TP_1W_DELETE_SEGMENT 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_1W_DELETE_SEGMENT'".
EXPORTING
CONTEXT_NUMBER = "Plan variant number (sequential number)
* SEGMENT_NUMBER = "2 Byte Integer (Signed)
TABLES
T_FLIGHT_DELETE = "Flight Reservation
T_CAR_DELETE = "Entry Parameter: Car Rental Reservation
T_HOTEL_DELETE = "Entry Parameter: Hotel/Room Reservation
* T_FLIGHT_MARRIED = "
EXCEPTIONS
CANCELLATION_FAILED = 1 NO_DESTINATION = 2 INVALID_CONTEXT = 3 CONNECTION_ERROR = 4 RFC_ERROR = 5
IMPORTING Parameters details for TP_1W_DELETE_SEGMENT
CONTEXT_NUMBER - Plan variant number (sequential number)
Data type: VARIANT_NROptional: No
Call by Reference: No ( called with pass by value option)
SEGMENT_NUMBER - 2 Byte Integer (Signed)
Data type: INT2Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for TP_1W_DELETE_SEGMENT
T_FLIGHT_DELETE - Flight Reservation
Data type: FTPS_FLIGHT_DELETEOptional: No
Call by Reference: Yes
T_CAR_DELETE - Entry Parameter: Car Rental Reservation
Data type: FTPS_CAR_DELETEOptional: No
Call by Reference: Yes
T_HOTEL_DELETE - Entry Parameter: Hotel/Room Reservation
Data type: FTPS_HOTEL_DELETEOptional: No
Call by Reference: Yes
T_FLIGHT_MARRIED -
Data type: FTPT_FLIGHTOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
CANCELLATION_FAILED - Cancellation failed
Data type:Optional: No
Call by Reference: Yes
NO_DESTINATION - Keine RFC-Verbindung gefunden
Data type:Optional: No
Call by Reference: Yes
INVALID_CONTEXT - Invalid context
Data type:Optional: No
Call by Reference: Yes
CONNECTION_ERROR - Allgemeiner Verbindungsfehler
Data type:Optional: No
Call by Reference: Yes
RFC_ERROR - Fehler in der RFC-Verbindung
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for TP_1W_DELETE_SEGMENT 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 VARIANT_NR, " | |||
| lt_t_flight_delete | TYPE STANDARD TABLE OF FTPS_FLIGHT_DELETE, " | |||
| lv_cancellation_failed | TYPE FTPS_FLIGHT_DELETE, " | |||
| lt_t_car_delete | TYPE STANDARD TABLE OF FTPS_CAR_DELETE, " | |||
| lv_no_destination | TYPE FTPS_CAR_DELETE, " | |||
| lv_segment_number | TYPE INT2, " | |||
| lt_t_hotel_delete | TYPE STANDARD TABLE OF FTPS_HOTEL_DELETE, " | |||
| lv_invalid_context | TYPE FTPS_HOTEL_DELETE, " | |||
| lv_connection_error | TYPE FTPS_HOTEL_DELETE, " | |||
| lt_t_flight_married | TYPE STANDARD TABLE OF FTPT_FLIGHT, " | |||
| lv_rfc_error | TYPE FTPT_FLIGHT. " |
|   CALL FUNCTION 'TP_1W_DELETE_SEGMENT' " |
| EXPORTING | ||
| CONTEXT_NUMBER | = lv_context_number | |
| SEGMENT_NUMBER | = lv_segment_number | |
| TABLES | ||
| T_FLIGHT_DELETE | = lt_t_flight_delete | |
| T_CAR_DELETE | = lt_t_car_delete | |
| T_HOTEL_DELETE | = lt_t_hotel_delete | |
| T_FLIGHT_MARRIED | = lt_t_flight_married | |
| EXCEPTIONS | ||
| CANCELLATION_FAILED = 1 | ||
| NO_DESTINATION = 2 | ||
| INVALID_CONTEXT = 3 | ||
| CONNECTION_ERROR = 4 | ||
| RFC_ERROR = 5 | ||
| . " TP_1W_DELETE_SEGMENT | ||
ABAP code using 7.40 inline data declarations to call FM TP_1W_DELETE_SEGMENT
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