SAP OIB_SD_RCV_FROM_QCI_SCREEN Function Module for Receive results from QCI screen

Search SAP Function Modules

OIB_SD_RCV_FROM_QCI_SCREEN is a standard oib sd rcv from qci screen SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Receive results from QCI screen 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 rcv from qci screen FM, simply by entering the name OIB_SD_RCV_FROM_QCI_SCREEN into the relevant SAP transaction such as SE37 or SE38.

Function Group: OIB_SD
Program Name: SAPLOIB_SD
Main Program: SAPLOIB_SD
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function OIB_SD_RCV_FROM_QCI_SCREEN 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_RCV_FROM_QCI_SCREEN'"Receive results from QCI screen
  EXPORTING
   IF_VBELN =  "Delivery
   IF_POSNR =  "Delivery item
   IF_AKTYP =  "Activity category in SAP transaction
   IF_UECHA =  "Higher-level item of batch split item
   IF_UEPOS =  "Higher-level item in bill of material structures
*  IF_DELIV = 'X' "

 IMPORTING
   EF_QNT_CHANGED =  "

TABLES
   IT_XLIPS =  "Reference structure for XLIPS/YLIPS

EXCEPTIONS
   VAR_MESSAGE = 1 

.

IMPORTING Parameters details for OIB_SD_RCV_FROM_QCI_SCREEN

IF_VBELN - Delivery

Data type: LIPS-VBELN
Optional: No
Call by Reference: Yes

IF_POSNR - Delivery item

Data type: LIPS-POSNR
Optional: No
Call by Reference: Yes

IF_AKTYP - Activity category in SAP transaction

Data type: T180-AKTYP
Optional: No
Call by Reference: Yes

IF_UECHA - Higher-level item of batch split item

Data type: LIPS-UECHA
Optional: No
Call by Reference: Yes

IF_UEPOS - Higher-level item in bill of material structures

Data type: LIPS-UEPOS
Optional: No
Call by Reference: Yes

IF_DELIV -

Data type: C
Default: 'X'
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for OIB_SD_RCV_FROM_QCI_SCREEN

EF_QNT_CHANGED -

Data type: C
Optional: No
Call by Reference: Yes

TABLES Parameters details for OIB_SD_RCV_FROM_QCI_SCREEN

IT_XLIPS - Reference structure for XLIPS/YLIPS

Data type: LIPSVB
Optional: No
Call by Reference: Yes

EXCEPTIONS details

VAR_MESSAGE -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for OIB_SD_RCV_FROM_QCI_SCREEN 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.

ABAP code using 7.40 inline data declarations to call FM OIB_SD_RCV_FROM_QCI_SCREEN

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