SAP OIUVL_READ_OSP_DATA Function Module for Reads table OIUVL_OSP
OIUVL_READ_OSP_DATA is a standard oiuvl read osp data SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Reads table OIUVL_OSP 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 oiuvl read osp data FM, simply by entering the name OIUVL_READ_OSP_DATA into the relevant SAP transaction such as SE37 or SE38.
Function Group: OIUVL_OIL_STMT_PROFILE
Program Name: SAPLOIUVL_OIL_STMT_PROFILE
Main Program: SAPLOIUVL_OIL_STMT_PROFILE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function OIUVL_READ_OSP_DATA 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 'OIUVL_READ_OSP_DATA'"Reads table OIUVL_OSP.
EXPORTING
I_BUKRS = "Company code
I_VNAME = "Joint venture
I_DOI_NO = "Division of Interest
I_OWN_NO = "E&P Owner
I_CT_NO = "Contract Number
I_MP_NO = "Measurement point number
IMPORTING
E_COUNT = "
TABLES
REPODATA = "Oil Statement Profile
EXCEPTIONS
NONE_FOUND = 1
IMPORTING Parameters details for OIUVL_READ_OSP_DATA
I_BUKRS - Company code
Data type: OIUVL_OSP-BUKRSOptional: No
Call by Reference: No ( called with pass by value option)
I_VNAME - Joint venture
Data type: OIUVL_OSP-VNAMEOptional: No
Call by Reference: No ( called with pass by value option)
I_DOI_NO - Division of Interest
Data type: OIUVL_OSP-DOI_NOOptional: No
Call by Reference: No ( called with pass by value option)
I_OWN_NO - E&P Owner
Data type: OIUVL_OSP-OWN_NOOptional: No
Call by Reference: No ( called with pass by value option)
I_CT_NO - Contract Number
Data type: OIUVL_OSP-CT_NOOptional: No
Call by Reference: No ( called with pass by value option)
I_MP_NO - Measurement point number
Data type: OIUVL_OSP-MP_NOOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for OIUVL_READ_OSP_DATA
E_COUNT -
Data type: IOptional: No
Call by Reference: Yes
TABLES Parameters details for OIUVL_READ_OSP_DATA
REPODATA - Oil Statement Profile
Data type: OIUVL_OSPOptional: No
Call by Reference: Yes
EXCEPTIONS details
NONE_FOUND -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for OIUVL_READ_OSP_DATA 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_e_count | TYPE I, " | |||
| lv_i_bukrs | TYPE OIUVL_OSP-BUKRS, " | |||
| lt_repodata | TYPE STANDARD TABLE OF OIUVL_OSP, " | |||
| lv_none_found | TYPE OIUVL_OSP, " | |||
| lv_i_vname | TYPE OIUVL_OSP-VNAME, " | |||
| lv_i_doi_no | TYPE OIUVL_OSP-DOI_NO, " | |||
| lv_i_own_no | TYPE OIUVL_OSP-OWN_NO, " | |||
| lv_i_ct_no | TYPE OIUVL_OSP-CT_NO, " | |||
| lv_i_mp_no | TYPE OIUVL_OSP-MP_NO. " |
|   CALL FUNCTION 'OIUVL_READ_OSP_DATA' "Reads table OIUVL_OSP |
| EXPORTING | ||
| I_BUKRS | = lv_i_bukrs | |
| I_VNAME | = lv_i_vname | |
| I_DOI_NO | = lv_i_doi_no | |
| I_OWN_NO | = lv_i_own_no | |
| I_CT_NO | = lv_i_ct_no | |
| I_MP_NO | = lv_i_mp_no | |
| IMPORTING | ||
| E_COUNT | = lv_e_count | |
| TABLES | ||
| REPODATA | = lt_repodata | |
| EXCEPTIONS | ||
| NONE_FOUND = 1 | ||
| . " OIUVL_READ_OSP_DATA | ||
ABAP code using 7.40 inline data declarations to call FM OIUVL_READ_OSP_DATA
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 BUKRS FROM OIUVL_OSP INTO @DATA(ld_i_bukrs). | ||||
| "SELECT single VNAME FROM OIUVL_OSP INTO @DATA(ld_i_vname). | ||||
| "SELECT single DOI_NO FROM OIUVL_OSP INTO @DATA(ld_i_doi_no). | ||||
| "SELECT single OWN_NO FROM OIUVL_OSP INTO @DATA(ld_i_own_no). | ||||
| "SELECT single CT_NO FROM OIUVL_OSP INTO @DATA(ld_i_ct_no). | ||||
| "SELECT single MP_NO FROM OIUVL_OSP INTO @DATA(ld_i_mp_no). | ||||
Search for further information about these or an SAP related objects