SAP TP_PLACE_PNR_IN_QUEUE Function Module for
TP_PLACE_PNR_IN_QUEUE is a standard tp place pnr in queue 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 place pnr in queue FM, simply by entering the name TP_PLACE_PNR_IN_QUEUE 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_PLACE_PNR_IN_QUEUE 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_PLACE_PNR_IN_QUEUE'".
EXPORTING
PROVIDER = "Reservation System
CONTEXT = "Plan Variant Number (Sequential Number)
OFFICE = "Sales Office
QUEUE_NR = "Queue
QUEUECAT_NR = "Queue Category
EXCEPTIONS
NO_DESTINATION = 1 INVALID_CONTEXT = 2 CONNECTION_ERROR = 3 RFC_ERROR = 4 API_ERROR = 5 INVALID_SYSTEM = 6 OTHER_ERROR = 7
IMPORTING Parameters details for TP_PLACE_PNR_IN_QUEUE
PROVIDER - Reservation System
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)
OFFICE - Sales Office
Data type: OFFICEOptional: No
Call by Reference: No ( called with pass by value option)
QUEUE_NR - Queue
Data type: QUEUENROptional: No
Call by Reference: No ( called with pass by value option)
QUEUECAT_NR - Queue Category
Data type: QUEUECATOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_DESTINATION -
Data type:Optional: No
Call by Reference: Yes
INVALID_CONTEXT -
Data type:Optional: No
Call by Reference: Yes
CONNECTION_ERROR -
Data type:Optional: No
Call by Reference: Yes
RFC_ERROR -
Data type:Optional: No
Call by Reference: Yes
API_ERROR -
Data type:Optional: No
Call by Reference: Yes
INVALID_SYSTEM -
Data type:Optional: No
Call by Reference: Yes
OTHER_ERROR -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for TP_PLACE_PNR_IN_QUEUE 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, " | |||
| lv_no_destination | TYPE TA20BA, " | |||
| lv_context | TYPE FTPT_VARIANT-VARIANT, " | |||
| lv_invalid_context | TYPE FTPT_VARIANT, " | |||
| lv_office | TYPE OFFICE, " | |||
| lv_connection_error | TYPE OFFICE, " | |||
| lv_queue_nr | TYPE QUEUENR, " | |||
| lv_rfc_error | TYPE QUEUENR, " | |||
| lv_api_error | TYPE QUEUENR, " | |||
| lv_queuecat_nr | TYPE QUEUECAT, " | |||
| lv_invalid_system | TYPE QUEUECAT, " | |||
| lv_other_error | TYPE QUEUECAT. " |
|   CALL FUNCTION 'TP_PLACE_PNR_IN_QUEUE' " |
| EXPORTING | ||
| PROVIDER | = lv_provider | |
| CONTEXT | = lv_context | |
| OFFICE | = lv_office | |
| QUEUE_NR | = lv_queue_nr | |
| QUEUECAT_NR | = lv_queuecat_nr | |
| EXCEPTIONS | ||
| NO_DESTINATION = 1 | ||
| INVALID_CONTEXT = 2 | ||
| CONNECTION_ERROR = 3 | ||
| RFC_ERROR = 4 | ||
| API_ERROR = 5 | ||
| INVALID_SYSTEM = 6 | ||
| OTHER_ERROR = 7 | ||
| . " TP_PLACE_PNR_IN_QUEUE | ||
ABAP code using 7.40 inline data declarations to call FM TP_PLACE_PNR_IN_QUEUE
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