SAP TP_CREATE_TICKET_ELEMENT Function Module for
TP_CREATE_TICKET_ELEMENT is a standard tp create ticket element 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 create ticket element FM, simply by entering the name TP_CREATE_TICKET_ELEMENT into the relevant SAP transaction such as SE37 or SE38.
Function Group: FITP_GEN
Program Name: SAPLFITP_GEN
Main Program: SAPLFITP_GEN
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function TP_CREATE_TICKET_ELEMENT 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_CREATE_TICKET_ELEMENT'".
EXPORTING
PROVIDER = "Context
CONTEXT = "Plan Variant Number (Sequential Number)
TABLES
PNR_TICKET_IN = "PNR Ticket Data
* PNR_TICKET_OUT = "Output of Ticket Data in PNR
EXCEPTIONS
INVALID_SYSTEM = 1 INVALID_CONTEXT = 2 CONNECTION_ERROR = 3 TICKET_CREATION_ERROR = 4 GENERAL_API_ERROR = 5
IMPORTING Parameters details for TP_CREATE_TICKET_ELEMENT
PROVIDER - Context
Data type: TA20BA-RES_SYSTEMOptional: No
Call by Reference: No ( called with pass by value option)
CONTEXT - Plan Variant Number (Sequential Number)
Data type: FTPT_VARIANT-VARIANTOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for TP_CREATE_TICKET_ELEMENT
PNR_TICKET_IN - PNR Ticket Data
Data type: FTPS_PNR_TKTOptional: No
Call by Reference: Yes
PNR_TICKET_OUT - Output of Ticket Data in PNR
Data type: FTPS_PNR_TKT_OUTOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
INVALID_SYSTEM -
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 -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
TICKET_CREATION_ERROR -
Data type:Optional: No
Call by Reference: Yes
GENERAL_API_ERROR - General API error
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for TP_CREATE_TICKET_ELEMENT 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_provider | TYPE TA20BA-RES_SYSTEM, " | |||
| lt_pnr_ticket_in | TYPE STANDARD TABLE OF FTPS_PNR_TKT, " | |||
| lv_invalid_system | TYPE FTPS_PNR_TKT, " | |||
| lv_context | TYPE FTPT_VARIANT-VARIANT, " | |||
| lt_pnr_ticket_out | TYPE STANDARD TABLE OF FTPS_PNR_TKT_OUT, " | |||
| lv_invalid_context | TYPE FTPS_PNR_TKT_OUT, " | |||
| lv_connection_error | TYPE FTPS_PNR_TKT_OUT, " | |||
| lv_ticket_creation_error | TYPE FTPS_PNR_TKT_OUT, " | |||
| lv_general_api_error | TYPE FTPS_PNR_TKT_OUT. " |
|   CALL FUNCTION 'TP_CREATE_TICKET_ELEMENT' " |
| EXPORTING | ||
| PROVIDER | = lv_provider | |
| CONTEXT | = lv_context | |
| TABLES | ||
| PNR_TICKET_IN | = lt_pnr_ticket_in | |
| PNR_TICKET_OUT | = lt_pnr_ticket_out | |
| EXCEPTIONS | ||
| INVALID_SYSTEM = 1 | ||
| INVALID_CONTEXT = 2 | ||
| CONNECTION_ERROR = 3 | ||
| TICKET_CREATION_ERROR = 4 | ||
| GENERAL_API_ERROR = 5 | ||
| . " TP_CREATE_TICKET_ELEMENT | ||
ABAP code using 7.40 inline data declarations to call FM TP_CREATE_TICKET_ELEMENT
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 RES_SYSTEM FROM TA20BA INTO @DATA(ld_provider). | ||||
| "SELECT single VARIANT FROM FTPT_VARIANT INTO @DATA(ld_context). | ||||
Search for further information about these or an SAP related objects