SAP OIIO_ENTRY_EXISTS Function Module for Shows if an entry in roik37x exists for a given item
OIIO_ENTRY_EXISTS is a standard oiio entry exists SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Shows if an entry in roik37x exists for a given item 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 oiio entry exists FM, simply by entering the name OIIO_ENTRY_EXISTS into the relevant SAP transaction such as SE37 or SE38.
Function Group: OIIO
Program Name: SAPLOIIO
Main Program: SAPLOIIO
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function OIIO_ENTRY_EXISTS 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 'OIIO_ENTRY_EXISTS'"Shows if an entry in roik37x exists for a given item.
EXPORTING
I_POSNR = "
EXCEPTIONS
NO_ENTRY = 1
IMPORTING Parameters details for OIIO_ENTRY_EXISTS
I_POSNR -
Data type: OIK37-POSNROptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_ENTRY -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for OIIO_ENTRY_EXISTS 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_i_posnr | TYPE OIK37-POSNR, " | |||
| lv_no_entry | TYPE OIK37. " |
|   CALL FUNCTION 'OIIO_ENTRY_EXISTS' "Shows if an entry in roik37x exists for a given item |
| EXPORTING | ||
| I_POSNR | = lv_i_posnr | |
| EXCEPTIONS | ||
| NO_ENTRY = 1 | ||
| . " OIIO_ENTRY_EXISTS | ||
ABAP code using 7.40 inline data declarations to call FM OIIO_ENTRY_EXISTS
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.| "SELECT single POSNR FROM OIK37 INTO @DATA(ld_i_posnr). | ||||
Search for further information about these or an SAP related objects