OIJ_GET_VEH_PERF_DATA SAP Function module - Get Vehicle Performance Data

OIJ_GET_VEH_PERF_DATA is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name OIJ_GET_VEH_PERF_DATA into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: OIJ_SS
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM OIJ_GET_VEH_PERF_DATA - OIJ GET VEH PERF DATA

CALL FUNCTION 'OIJ_GET_VEH_PERF_DATA' "Get Vehicle Performance Data
  EXPORTING
*   iv_refresh_buffer =         " boolean       boolean variable (X=true, -=false, space=unknown)
*   iv_bypass_buffer =          " boolean       boolean variable (X=true, -=false, space=unknown)
    iv_vehicle =                " oig_vhlnmr    TD Vehicle Number
*   iv_locid =                  " oij_locid     Location ID
  TABLES
    t_oij_veh_perf =            " oij_veh_perf  Marine Scheduling - Table to Store vehicle Performanace
  EXCEPTIONS
    VEHICLE_MISSING = 1         "               Vehicle Is Missing
    NO_DATA_FOUND = 2           "               No Data Found
    .  "  OIJ_GET_VEH_PERF_DATA

ABAP code example for Function Module OIJ_GET_VEH_PERF_DATA

The ABAP code below is a full code listing to execute function module OIJ_GET_VEH_PERF_DATA including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
it_t_oij_veh_perf  
 
 TYPE STANDARD TABLE OF OIJ_VEH_PERF,"TABLES PARAM
wa_t_oij_veh_perf
 
 LIKE LINE OF it_t_oij_veh_perf
.


DATA(ld_iv_refresh_buffer) = 'Check type of data required'.

DATA(ld_iv_bypass_buffer) = 'Check type of data required'.

DATA(ld_iv_vehicle) = 'Check type of data required'.

DATA(ld_iv_locid) = 'Check type of data required'.
 

"populate fields of struture and append to itab
append wa_t_oij_veh_perf to it_t_oij_veh_perf.
.

CALL FUNCTION 'OIJ_GET_VEH_PERF_DATA'
  EXPORTING
*   iv_refresh_buffer =          ld_iv_refresh_buffer
*   iv_bypass_buffer =           ld_iv_bypass_buffer
    iv_vehicle =                 ld_iv_vehicle
*   iv_locid =                   ld_iv_locid
  TABLES
    t_oij_veh_perf =             it_t_oij_veh_perf
  EXCEPTIONS
    VEHICLE_MISSING =            1
    NO_DATA_FOUND =              2
    .  "  OIJ_GET_VEH_PERF_DATA

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_iv_refresh_buffer
 
 TYPE BOOLEAN ,
it_t_oij_veh_perf
 
 TYPE STANDARD TABLE OF OIJ_VEH_PERF ,
wa_t_oij_veh_perf
 
 LIKE LINE OF it_t_oij_veh_perf,
ld_iv_bypass_buffer
 
 TYPE BOOLEAN ,
ld_iv_vehicle
 
 TYPE OIG_VHLNMR ,
ld_iv_locid
 
 TYPE OIJ_LOCID .


ld_iv_refresh_buffer = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_t_oij_veh_perf to it_t_oij_veh_perf.
ld_iv_bypass_buffer = 'Check type of data required'.
ld_iv_vehicle = 'Check type of data required'.
ld_iv_locid = 'Check type of data required'.