SAP OIB_SD_QCI_GET_QUANTITY_API Function Module for Additional Quantities for Delivery - Get Single Quantity
OIB_SD_QCI_GET_QUANTITY_API is a standard oib sd qci get quantity api SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Additional Quantities for Delivery - Get Single Quantity 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 qci get quantity api FM, simply by entering the name OIB_SD_QCI_GET_QUANTITY_API into the relevant SAP transaction such as SE37 or SE38.
Function Group: OIB_SD_QCI_API
Program Name: SAPLOIB_SD_QCI_API
Main Program: SAPLOIB_SD_QCI_API
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function OIB_SD_QCI_GET_QUANTITY_API 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_QCI_GET_QUANTITY_API'"Additional Quantities for Delivery - Get Single Quantity.
EXPORTING
* IV_OLDNEW = '2' "Internal Control f.Interface to receive'Delivery+Quantities'
IV_VBELN_DLV = "Delivery
IV_POSNR_DLV = "Delivery Item
IV_UOM = "Unit of Measurement
* IV_USE_BSPLIT_SUM_QTY = ' ' "Boolean Variable (X=True, -=False, Space=Unknown)
* IV_ONLY_FOR_BSPLIT_MAIN_ITEM = ' ' "Boolean Variable (X=True, -=False, Space=Unknown)
IMPORTING
EV_QTY_P = "Referenced quantity in base unit of measure
EV_QTY_F = "Referenced quantity in base unit of measure (float)
EXCEPTIONS
TEST_HPM_SD_OLD = 1 PARAMETER_INCORRECT = 2 READ_LIPSO1_WRK_ERROR = 3 BATCH_SPLIT_ITEMS_NOT_FOUND = 4 QUANTITY_NOT_AVAILABLE = 5
IMPORTING Parameters details for OIB_SD_QCI_GET_QUANTITY_API
IV_OLDNEW - Internal Control f.Interface to receive'Delivery+Quantities'
Data type: OIB_OLDNEWDefault: '2'
Optional: No
Call by Reference: Yes
IV_VBELN_DLV - Delivery
Data type: VBELN_VLOptional: No
Call by Reference: Yes
IV_POSNR_DLV - Delivery Item
Data type: POSNR_VLOptional: No
Call by Reference: Yes
IV_UOM - Unit of Measurement
Data type: MSEHIOptional: No
Call by Reference: Yes
IV_USE_BSPLIT_SUM_QTY - Boolean Variable (X=True, -=False, Space=Unknown)
Data type: BOOLEANDefault: SPACE
Optional: Yes
Call by Reference: Yes
IV_ONLY_FOR_BSPLIT_MAIN_ITEM - Boolean Variable (X=True, -=False, Space=Unknown)
Data type: BOOLEANDefault: SPACE
Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for OIB_SD_QCI_GET_QUANTITY_API
EV_QTY_P - Referenced quantity in base unit of measure
Data type: RFMNGOptional: No
Call by Reference: Yes
EV_QTY_F - Referenced quantity in base unit of measure (float)
Data type: RFMNG_FLTOptional: No
Call by Reference: Yes
EXCEPTIONS details
TEST_HPM_SD_OLD -
Data type:Optional: No
Call by Reference: Yes
PARAMETER_INCORRECT -
Data type:Optional: No
Call by Reference: Yes
READ_LIPSO1_WRK_ERROR -
Data type:Optional: No
Call by Reference: Yes
BATCH_SPLIT_ITEMS_NOT_FOUND -
Data type:Optional: No
Call by Reference: Yes
QUANTITY_NOT_AVAILABLE -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for OIB_SD_QCI_GET_QUANTITY_API 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_ev_qty_p | TYPE RFMNG, " | |||
| lv_iv_oldnew | TYPE OIB_OLDNEW, " '2' | |||
| lv_test_hpm_sd_old | TYPE OIB_OLDNEW, " | |||
| lv_ev_qty_f | TYPE RFMNG_FLT, " | |||
| lv_iv_vbeln_dlv | TYPE VBELN_VL, " | |||
| lv_parameter_incorrect | TYPE VBELN_VL, " | |||
| lv_iv_posnr_dlv | TYPE POSNR_VL, " | |||
| lv_read_lipso1_wrk_error | TYPE POSNR_VL, " | |||
| lv_iv_uom | TYPE MSEHI, " | |||
| lv_batch_split_items_not_found | TYPE MSEHI, " | |||
| lv_iv_use_bsplit_sum_qty | TYPE BOOLEAN, " SPACE | |||
| lv_quantity_not_available | TYPE BOOLEAN, " | |||
| lv_iv_only_for_bsplit_main_item | TYPE BOOLEAN. " SPACE |
|   CALL FUNCTION 'OIB_SD_QCI_GET_QUANTITY_API' "Additional Quantities for Delivery - Get Single Quantity |
| EXPORTING | ||
| IV_OLDNEW | = lv_iv_oldnew | |
| IV_VBELN_DLV | = lv_iv_vbeln_dlv | |
| IV_POSNR_DLV | = lv_iv_posnr_dlv | |
| IV_UOM | = lv_iv_uom | |
| IV_USE_BSPLIT_SUM_QTY | = lv_iv_use_bsplit_sum_qty | |
| IV_ONLY_FOR_BSPLIT_MAIN_ITEM | = lv_iv_only_for_bsplit_main_item | |
| IMPORTING | ||
| EV_QTY_P | = lv_ev_qty_p | |
| EV_QTY_F | = lv_ev_qty_f | |
| EXCEPTIONS | ||
| TEST_HPM_SD_OLD = 1 | ||
| PARAMETER_INCORRECT = 2 | ||
| READ_LIPSO1_WRK_ERROR = 3 | ||
| BATCH_SPLIT_ITEMS_NOT_FOUND = 4 | ||
| QUANTITY_NOT_AVAILABLE = 5 | ||
| . " OIB_SD_QCI_GET_QUANTITY_API | ||
ABAP code using 7.40 inline data declarations to call FM OIB_SD_QCI_GET_QUANTITY_API
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.| DATA(ld_iv_oldnew) | = '2'. | |||
| DATA(ld_iv_use_bsplit_sum_qty) | = ' '. | |||
| DATA(ld_iv_only_for_bsplit_main_item) | = ' '. | |||
Search for further information about these or an SAP related objects