SAP OIJ_FIND_SUIT_BERTHS Function Module for finds suit. berths at a location acc. do physical atrrs. and matr. avail.
OIJ_FIND_SUIT_BERTHS is a standard oij find suit berths SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for finds suit. berths at a location acc. do physical atrrs. and matr. avail. 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 oij find suit berths FM, simply by entering the name OIJ_FIND_SUIT_BERTHS into the relevant SAP transaction such as SE37 or SE38.
Function Group: OIJ_LDSCHED
Program Name: SAPLOIJ_LDSCHED
Main Program: SAPLOIJ_LDSCHED
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function OIJ_FIND_SUIT_BERTHS 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 'OIJ_FIND_SUIT_BERTHS'"finds suit. berths at a location acc. do physical atrrs. and matr. avail..
EXPORTING
IV_PBLNR = "Location ID
IV_VESSELID = "TD Vehicle Number
* IV_MATNO = "Material number
* IV_VEHARRDRAFT = "Ship Arrival Draft sent from ship
* IV_VEHDEPDRAFT = "Ship Departure Draft sent from ship
* IV_DRFUOM = "UoM of draft of a ship
IMPORTING
ET_SUITBERTHS = "berth id f4 help table
ET_NOTCOMP_BERTHS = "Table of berths at TSW locations
EXCEPTIONS
NO_LOC_FOUND = 1 NO_LOC_BERTH = 2 NO_LOC_MAT = 3 INVALID_VESSEL_ID = 4 NO_SUIT_BERTHS = 5 COMP_ERROR_OCCURRED = 6
IMPORTING Parameters details for OIJ_FIND_SUIT_BERTHS
IV_PBLNR - Location ID
Data type: OIF_PBLNROptional: No
Call by Reference: No ( called with pass by value option)
IV_VESSELID - TD Vehicle Number
Data type: OIG_VHLNMROptional: No
Call by Reference: No ( called with pass by value option)
IV_MATNO - Material number
Data type: MATNROptional: Yes
Call by Reference: Yes
IV_VEHARRDRAFT - Ship Arrival Draft sent from ship
Data type: OIJ_ARRDRAFTOptional: Yes
Call by Reference: Yes
IV_VEHDEPDRAFT - Ship Departure Draft sent from ship
Data type: OIJ_DEPDRAFTOptional: Yes
Call by Reference: Yes
IV_DRFUOM - UoM of draft of a ship
Data type: OIJ_DRF_UOMOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for OIJ_FIND_SUIT_BERTHS
ET_SUITBERTHS - berth id f4 help table
Data type: ROIJ_BERTHIDM_TOptional: No
Call by Reference: Yes
ET_NOTCOMP_BERTHS - Table of berths at TSW locations
Data type: OIJBERLOC_TOptional: No
Call by Reference: Yes
EXCEPTIONS details
NO_LOC_FOUND -
Data type:Optional: No
Call by Reference: Yes
NO_LOC_BERTH -
Data type:Optional: No
Call by Reference: Yes
NO_LOC_MAT -
Data type:Optional: No
Call by Reference: Yes
INVALID_VESSEL_ID -
Data type:Optional: No
Call by Reference: Yes
NO_SUIT_BERTHS -
Data type:Optional: No
Call by Reference: Yes
COMP_ERROR_OCCURRED -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for OIJ_FIND_SUIT_BERTHS 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_iv_pblnr | TYPE OIF_PBLNR, " | |||
| lv_no_loc_found | TYPE OIF_PBLNR, " | |||
| lv_et_suitberths | TYPE ROIJ_BERTHIDM_T, " | |||
| lv_iv_vesselid | TYPE OIG_VHLNMR, " | |||
| lv_no_loc_berth | TYPE OIG_VHLNMR, " | |||
| lv_et_notcomp_berths | TYPE OIJBERLOC_T, " | |||
| lv_iv_matno | TYPE MATNR, " | |||
| lv_no_loc_mat | TYPE MATNR, " | |||
| lv_iv_veharrdraft | TYPE OIJ_ARRDRAFT, " | |||
| lv_invalid_vessel_id | TYPE OIJ_ARRDRAFT, " | |||
| lv_iv_vehdepdraft | TYPE OIJ_DEPDRAFT, " | |||
| lv_no_suit_berths | TYPE OIJ_DEPDRAFT, " | |||
| lv_iv_drfuom | TYPE OIJ_DRF_UOM, " | |||
| lv_comp_error_occurred | TYPE OIJ_DRF_UOM. " |
|   CALL FUNCTION 'OIJ_FIND_SUIT_BERTHS' "finds suit. berths at a location acc. do physical atrrs. and matr. avail. |
| EXPORTING | ||
| IV_PBLNR | = lv_iv_pblnr | |
| IV_VESSELID | = lv_iv_vesselid | |
| IV_MATNO | = lv_iv_matno | |
| IV_VEHARRDRAFT | = lv_iv_veharrdraft | |
| IV_VEHDEPDRAFT | = lv_iv_vehdepdraft | |
| IV_DRFUOM | = lv_iv_drfuom | |
| IMPORTING | ||
| ET_SUITBERTHS | = lv_et_suitberths | |
| ET_NOTCOMP_BERTHS | = lv_et_notcomp_berths | |
| EXCEPTIONS | ||
| NO_LOC_FOUND = 1 | ||
| NO_LOC_BERTH = 2 | ||
| NO_LOC_MAT = 3 | ||
| INVALID_VESSEL_ID = 4 | ||
| NO_SUIT_BERTHS = 5 | ||
| COMP_ERROR_OCCURRED = 6 | ||
| . " OIJ_FIND_SUIT_BERTHS | ||
ABAP code using 7.40 inline data declarations to call FM OIJ_FIND_SUIT_BERTHS
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.Search for further information about these or an SAP related objects