SAP OIG_VALUE_REQUEST_VEHICLE Function Module for TD Value-request list for vehicles in a shipment
OIG_VALUE_REQUEST_VEHICLE is a standard oig value request vehicle SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for TD Value-request list for vehicles in a shipment 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 oig value request vehicle FM, simply by entering the name OIG_VALUE_REQUEST_VEHICLE into the relevant SAP transaction such as SE37 or SE38.
Function Group: OIGV
Program Name: SAPLOIGV
Main Program: SAPLOIGV
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function OIG_VALUE_REQUEST_VEHICLE 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 'OIG_VALUE_REQUEST_VEHICLE'"TD Value-request list for vehicles in a shipment.
CHANGING
PX_VEHICLE = "
TABLES
PI_OIGSV_TAB = "
EXCEPTIONS
CANCELLED = 1 NO_VALUES = 2
CHANGING Parameters details for OIG_VALUE_REQUEST_VEHICLE
PX_VEHICLE -
Data type: OIGV-VEHICLEOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for OIG_VALUE_REQUEST_VEHICLE
PI_OIGSV_TAB -
Data type: ROIGSVOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
CANCELLED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_VALUES -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for OIG_VALUE_REQUEST_VEHICLE 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_cancelled | TYPE STRING, " | |||
| lv_px_vehicle | TYPE OIGV-VEHICLE, " | |||
| lt_pi_oigsv_tab | TYPE STANDARD TABLE OF ROIGSV, " | |||
| lv_no_values | TYPE ROIGSV. " |
|   CALL FUNCTION 'OIG_VALUE_REQUEST_VEHICLE' "TD Value-request list for vehicles in a shipment |
| CHANGING | ||
| PX_VEHICLE | = lv_px_vehicle | |
| TABLES | ||
| PI_OIGSV_TAB | = lt_pi_oigsv_tab | |
| EXCEPTIONS | ||
| CANCELLED = 1 | ||
| NO_VALUES = 2 | ||
| . " OIG_VALUE_REQUEST_VEHICLE | ||
ABAP code using 7.40 inline data declarations to call FM OIG_VALUE_REQUEST_VEHICLE
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 VEHICLE FROM OIGV INTO @DATA(ld_px_vehicle). | ||||
Search for further information about these or an SAP related objects