SAP OIK_CHANGEPTR_OILDVA_CREATE Function Module for TPI: Create SMD change pointers for Drv/Veh-Assignment
OIK_CHANGEPTR_OILDVA_CREATE is a standard oik changeptr oildva create SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for TPI: Create SMD change pointers for Drv/Veh-Assignment 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 changeptr oildva create FM, simply by entering the name OIK_CHANGEPTR_OILDVA_CREATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: OIKT
Program Name: SAPLOIKT
Main Program: SAPLOIKT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function OIK_CHANGEPTR_OILDVA_CREATE 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_CHANGEPTR_OILDVA_CREATE'"TPI: Create SMD change pointers for Drv/Veh-Assignment.
EXPORTING
I_CHNGIND = "
TABLES
T_OBJECTS = "
EXCEPTIONS
DUPLICATE_POINTER_ID = 1
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_SAPLOIKT_100 Change Driver Vehicle Assignment IDoc
IMPORTING Parameters details for OIK_CHANGEPTR_OILDVA_CREATE
I_CHNGIND -
Data type: CDPOS-CHNGINDOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for OIK_CHANGEPTR_OILDVA_CREATE
T_OBJECTS -
Data type: ROIKVD_KEYOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
DUPLICATE_POINTER_ID -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for OIK_CHANGEPTR_OILDVA_CREATE 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_chngind | TYPE CDPOS-CHNGIND, " | |||
| lt_t_objects | TYPE STANDARD TABLE OF ROIKVD_KEY, " | |||
| lv_duplicate_pointer_id | TYPE ROIKVD_KEY. " |
|   CALL FUNCTION 'OIK_CHANGEPTR_OILDVA_CREATE' "TPI: Create SMD change pointers for Drv/Veh-Assignment |
| EXPORTING | ||
| I_CHNGIND | = lv_i_chngind | |
| TABLES | ||
| T_OBJECTS | = lt_t_objects | |
| EXCEPTIONS | ||
| DUPLICATE_POINTER_ID = 1 | ||
| . " OIK_CHANGEPTR_OILDVA_CREATE | ||
ABAP code using 7.40 inline data declarations to call FM OIK_CHANGEPTR_OILDVA_CREATE
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 CHNGIND FROM CDPOS INTO @DATA(ld_i_chngind). | ||||
Search for further information about these or an SAP related objects