SAP OIB_SD_OIL_BOM_CHECK_OW Function Module for Check, if Item corresponds to Oil BOM
OIB_SD_OIL_BOM_CHECK_OW is a standard oib sd oil bom check ow SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Check, if Item corresponds to Oil BOM 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 oib sd oil bom check ow FM, simply by entering the name OIB_SD_OIL_BOM_CHECK_OW into the relevant SAP transaction such as SE37 or SE38.
Function Group: OIB_SD_CONTEXT_OW
Program Name: SAPLOIB_SD_CONTEXT_OW
Main Program: SAPLOIB_SD_CONTEXT_OW
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function OIB_SD_OIL_BOM_CHECK_OW 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 'OIB_SD_OIL_BOM_CHECK_OW'"Check, if Item corresponds to Oil BOM.
EXPORTING
IS_LIKP = "SD Document: Delivery Header Data
IS_LIPS = "SD document: Delivery: Item data
IT_LIPSVB = "Table for Structure LIPSVB
EXCEPTIONS
READ_LIPSO1_WRK_ERROR = 1 READ_TVAP_ERROR_ITEM = 2 OIL_BOM_HDR_NOT_QCI_TDP_E172 = 3 READ_TVAP_ERROR_HEADER = 4 PUT_LIPSO1_WRK_ERROR = 5
IMPORTING Parameters details for OIB_SD_OIL_BOM_CHECK_OW
IS_LIKP - SD Document: Delivery Header Data
Data type: LIKPOptional: No
Call by Reference: Yes
IS_LIPS - SD document: Delivery: Item data
Data type: LIPSOptional: No
Call by Reference: Yes
IT_LIPSVB - Table for Structure LIPSVB
Data type: VA_LIPSVB_TOptional: No
Call by Reference: Yes
EXCEPTIONS details
READ_LIPSO1_WRK_ERROR -
Data type:Optional: No
Call by Reference: Yes
READ_TVAP_ERROR_ITEM -
Data type:Optional: No
Call by Reference: Yes
OIL_BOM_HDR_NOT_QCI_TDP_E172 -
Data type:Optional: No
Call by Reference: Yes
READ_TVAP_ERROR_HEADER -
Data type:Optional: No
Call by Reference: Yes
PUT_LIPSO1_WRK_ERROR -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for OIB_SD_OIL_BOM_CHECK_OW 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_is_likp | TYPE LIKP, " | |||
| lv_read_lipso1_wrk_error | TYPE LIKP, " | |||
| lv_is_lips | TYPE LIPS, " | |||
| lv_read_tvap_error_item | TYPE LIPS, " | |||
| lv_it_lipsvb | TYPE VA_LIPSVB_T, " | |||
| lv_oil_bom_hdr_not_qci_tdp_e172 | TYPE VA_LIPSVB_T, " | |||
| lv_read_tvap_error_header | TYPE VA_LIPSVB_T, " | |||
| lv_put_lipso1_wrk_error | TYPE VA_LIPSVB_T. " |
|   CALL FUNCTION 'OIB_SD_OIL_BOM_CHECK_OW' "Check, if Item corresponds to Oil BOM |
| EXPORTING | ||
| IS_LIKP | = lv_is_likp | |
| IS_LIPS | = lv_is_lips | |
| IT_LIPSVB | = lv_it_lipsvb | |
| EXCEPTIONS | ||
| READ_LIPSO1_WRK_ERROR = 1 | ||
| READ_TVAP_ERROR_ITEM = 2 | ||
| OIL_BOM_HDR_NOT_QCI_TDP_E172 = 3 | ||
| READ_TVAP_ERROR_HEADER = 4 | ||
| PUT_LIPSO1_WRK_ERROR = 5 | ||
| . " OIB_SD_OIL_BOM_CHECK_OW | ||
ABAP code using 7.40 inline data declarations to call FM OIB_SD_OIL_BOM_CHECK_OW
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