SAP OIK_TPI_PROTOCOL_START Function Module for Starts the protocol for OIL TPI
OIK_TPI_PROTOCOL_START is a standard oik tpi protocol start SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Starts the protocol for OIL TPI 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 oik tpi protocol start FM, simply by entering the name OIK_TPI_PROTOCOL_START into the relevant SAP transaction such as SE37 or SE38.
Function Group: OIKP
Program Name: SAPLOIKP
Main Program: SAPLOIKP
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function OIK_TPI_PROTOCOL_START 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 'OIK_TPI_PROTOCOL_START'"Starts the protocol for OIL TPI.
EXPORTING
* I_PROTOCOL_DETAIL_LEVEL = '4' "
* I_SEVERITY_TRANSFER = ' ' "
* I_PROTOCOL_REFRESH = ' ' "
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLOIKP_100 user exit to change order idoc name
EXIT_SAPLOIKP_110 User exit in module IDOC_INPUT_OILSH1 for user segments
EXIT_SAPLOIKP_120 User exit in the end of order distribution process (TPI)
EXIT_SAPLOIKP_130 TPI Shipment inbound process: Before delivery creation
EXIT_SAPLOIKP_140 TPI: Shipment inbound. Before order creation
EXIT_SAPLOIKP_150 TPI: Distribution of locations before IDoc data is filled
EXIT_SAPLOIKP_160 TPI: Distribution of locations after IDoc data is filled
EXIT_SAPLOIKP_170 exit in oii_scp_change_pointer_set to change message type
EXIT_SAPLOIKP_190 Exit in IDOC_INPUT_OILSH1 to change message type
EXIT_SAPLOIKP_200 TAS/TPI: Calling further IDOC processing
EXIT_SAPLOIKP_210 User Exit to change IDOC control structure for location data
EXIT_SAPLOIKP_230 User Exit to create IDOC for Order distribution to TPS.
EXIT_SAPLOIKP_240 User Exit to modify IDOC control structure for shipment distribution.
IMPORTING Parameters details for OIK_TPI_PROTOCOL_START
I_PROTOCOL_DETAIL_LEVEL -
Data type: SPROT_U-LEVELDefault: '4'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_SEVERITY_TRANSFER -
Data type: RV56A-SELKZDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_PROTOCOL_REFRESH -
Data type: RV56A-SELKZDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for OIK_TPI_PROTOCOL_START 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_i_protocol_detail_level | TYPE SPROT_U-LEVEL, " '4' | |||
| lv_i_severity_transfer | TYPE RV56A-SELKZ, " SPACE | |||
| lv_i_protocol_refresh | TYPE RV56A-SELKZ. " SPACE |
|   CALL FUNCTION 'OIK_TPI_PROTOCOL_START' "Starts the protocol for OIL TPI |
| EXPORTING | ||
| I_PROTOCOL_DETAIL_LEVEL | = lv_i_protocol_detail_level | |
| I_SEVERITY_TRANSFER | = lv_i_severity_transfer | |
| I_PROTOCOL_REFRESH | = lv_i_protocol_refresh | |
| . " OIK_TPI_PROTOCOL_START | ||
ABAP code using 7.40 inline data declarations to call FM OIK_TPI_PROTOCOL_START
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 LEVEL FROM SPROT_U INTO @DATA(ld_i_protocol_detail_level). | ||||
| DATA(ld_i_protocol_detail_level) | = '4'. | |||
| "SELECT single SELKZ FROM RV56A INTO @DATA(ld_i_severity_transfer). | ||||
| DATA(ld_i_severity_transfer) | = ' '. | |||
| "SELECT single SELKZ FROM RV56A INTO @DATA(ld_i_protocol_refresh). | ||||
| DATA(ld_i_protocol_refresh) | = ' '. | |||
Search for further information about these or an SAP related objects