SAP BAPI_PRODORDCONF_CREATE_TT Function Module for Enter Confirmation Time Ticket
BAPI_PRODORDCONF_CREATE_TT is a standard bapi prodordconf create tt SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Enter Confirmation Time Ticket 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 bapi prodordconf create tt FM, simply by entering the name BAPI_PRODORDCONF_CREATE_TT into the relevant SAP transaction such as SE37 or SE38.
Function Group: 2116
Program Name: SAPL2116
Main Program: SAPL2116
Appliation area: C
Release date: 29-Jun-1998
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_PRODORDCONF_CREATE_TT 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 'BAPI_PRODORDCONF_CREATE_TT'"Enter Confirmation Time Ticket.
EXPORTING
* POST_WRONG_ENTRIES = '0' "Ind.: Incorrect Data in Error Pool
* TESTRUN = "Ind.: Test Data Only, Without Saving
IMPORTING
RETURN = "Return Parameter(s)
TABLES
TIMETICKETS = "Table of Confirmations
* GOODSMOVEMENTS = "Table of Goods Movements
* LINK_CONF_GOODSMOV = "Linkage Table for Conf./Goods Movement
* CHARACTERISTICS_WIPBATCH = "Characteristics WIP Batch
* LINK_CONF_CHAR_WIPBATCH = "Linkage of Confirmation with Characteristics WIP Batch
* DETAIL_RETURN = "Return Parameter for Confirmation Table
* CHARACTERISTICS_BATCH = "Batch Characteristics
* LINK_GM_CHAR_BATCH = "Link: Batch Characteristics with Goods Movement Item
IMPORTING Parameters details for BAPI_PRODORDCONF_CREATE_TT
POST_WRONG_ENTRIES - Ind.: Incorrect Data in Error Pool
Data type: BAPI_CORU_PARAM-INS_ERRDefault: '0'
Optional: Yes
Call by Reference: No ( called with pass by value option)
TESTRUN - Ind.: Test Data Only, Without Saving
Data type: BAPI_CORU_PARAM-TESTRUNOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BAPI_PRODORDCONF_CREATE_TT
RETURN - Return Parameter(s)
Data type: BAPIRET1Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_PRODORDCONF_CREATE_TT
TIMETICKETS - Table of Confirmations
Data type: BAPI_PP_TIMETICKETOptional: No
Call by Reference: No ( called with pass by value option)
GOODSMOVEMENTS - Table of Goods Movements
Data type: BAPI2017_GM_ITEM_CREATEOptional: Yes
Call by Reference: No ( called with pass by value option)
LINK_CONF_GOODSMOV - Linkage Table for Conf./Goods Movement
Data type: BAPI_LINK_CONF_GOODSMOVOptional: Yes
Call by Reference: No ( called with pass by value option)
CHARACTERISTICS_WIPBATCH - Characteristics WIP Batch
Data type: BAPI_CHAR_WIPBATCHOptional: Yes
Call by Reference: Yes
LINK_CONF_CHAR_WIPBATCH - Linkage of Confirmation with Characteristics WIP Batch
Data type: BAPI_LINK_CONF_CHAR_WIPBATCHOptional: Yes
Call by Reference: Yes
DETAIL_RETURN - Return Parameter for Confirmation Table
Data type: BAPI_CORU_RETURNOptional: Yes
Call by Reference: No ( called with pass by value option)
CHARACTERISTICS_BATCH - Batch Characteristics
Data type: BAPI_CHAR_BATCHOptional: Yes
Call by Reference: Yes
LINK_GM_CHAR_BATCH - Link: Batch Characteristics with Goods Movement Item
Data type: BAPI_LINK_GM_CHAR_BATCHOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for BAPI_PRODORDCONF_CREATE_TT 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_return | TYPE BAPIRET1, " | |||
| lt_timetickets | TYPE STANDARD TABLE OF BAPI_PP_TIMETICKET, " | |||
| lv_post_wrong_entries | TYPE BAPI_CORU_PARAM-INS_ERR, " '0' | |||
| lv_testrun | TYPE BAPI_CORU_PARAM-TESTRUN, " | |||
| lt_goodsmovements | TYPE STANDARD TABLE OF BAPI2017_GM_ITEM_CREATE, " | |||
| lt_link_conf_goodsmov | TYPE STANDARD TABLE OF BAPI_LINK_CONF_GOODSMOV, " | |||
| lt_characteristics_wipbatch | TYPE STANDARD TABLE OF BAPI_CHAR_WIPBATCH, " | |||
| lt_link_conf_char_wipbatch | TYPE STANDARD TABLE OF BAPI_LINK_CONF_CHAR_WIPBATCH, " | |||
| lt_detail_return | TYPE STANDARD TABLE OF BAPI_CORU_RETURN, " | |||
| lt_characteristics_batch | TYPE STANDARD TABLE OF BAPI_CHAR_BATCH, " | |||
| lt_link_gm_char_batch | TYPE STANDARD TABLE OF BAPI_LINK_GM_CHAR_BATCH. " |
|   CALL FUNCTION 'BAPI_PRODORDCONF_CREATE_TT' "Enter Confirmation Time Ticket |
| EXPORTING | ||
| POST_WRONG_ENTRIES | = lv_post_wrong_entries | |
| TESTRUN | = lv_testrun | |
| IMPORTING | ||
| RETURN | = lv_return | |
| TABLES | ||
| TIMETICKETS | = lt_timetickets | |
| GOODSMOVEMENTS | = lt_goodsmovements | |
| LINK_CONF_GOODSMOV | = lt_link_conf_goodsmov | |
| CHARACTERISTICS_WIPBATCH | = lt_characteristics_wipbatch | |
| LINK_CONF_CHAR_WIPBATCH | = lt_link_conf_char_wipbatch | |
| DETAIL_RETURN | = lt_detail_return | |
| CHARACTERISTICS_BATCH | = lt_characteristics_batch | |
| LINK_GM_CHAR_BATCH | = lt_link_gm_char_batch | |
| . " BAPI_PRODORDCONF_CREATE_TT | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_PRODORDCONF_CREATE_TT
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 INS_ERR FROM BAPI_CORU_PARAM INTO @DATA(ld_post_wrong_entries). | ||||
| DATA(ld_post_wrong_entries) | = '0'. | |||
| "SELECT single TESTRUN FROM BAPI_CORU_PARAM INTO @DATA(ld_testrun). | ||||
Search for further information about these or an SAP related objects