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

Function OIUOW_READ_DOCUMENT_TYPE 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 'OIUOW_READ_DOCUMENT_TYPE'"Read table OIUOW_DOC_TYPE (buffered).
EXPORTING
DOC_TYPE = "Request document type
* FORCE_DB = "Checkbox
IMPORTING
E_OIUOW_DOC_TYPE = "Ownership Request Document Types
EXCEPTIONS
INVALID_DOC_TYPE = 1
IMPORTING Parameters details for OIUOW_READ_DOCUMENT_TYPE
DOC_TYPE - Request document type
Data type: OIUOW_DTCH-DOC_TYPEOptional: No
Call by Reference: No ( called with pass by value option)
FORCE_DB - Checkbox
Data type: OIU_COMMON-XFELDOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for OIUOW_READ_DOCUMENT_TYPE
E_OIUOW_DOC_TYPE - Ownership Request Document Types
Data type: OIUOW_DOC_TYPEOptional: No
Call by Reference: Yes
EXCEPTIONS details
INVALID_DOC_TYPE - Invalid Document Type Entered
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for OIUOW_READ_DOCUMENT_TYPE 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_doc_type | TYPE OIUOW_DTCH-DOC_TYPE, " | |||
| lv_e_oiuow_doc_type | TYPE OIUOW_DOC_TYPE, " | |||
| lv_invalid_doc_type | TYPE OIUOW_DOC_TYPE, " | |||
| lv_force_db | TYPE OIU_COMMON-XFELD. " |
|   CALL FUNCTION 'OIUOW_READ_DOCUMENT_TYPE' "Read table OIUOW_DOC_TYPE (buffered) |
| EXPORTING | ||
| DOC_TYPE | = lv_doc_type | |
| FORCE_DB | = lv_force_db | |
| IMPORTING | ||
| E_OIUOW_DOC_TYPE | = lv_e_oiuow_doc_type | |
| EXCEPTIONS | ||
| INVALID_DOC_TYPE = 1 | ||
| . " OIUOW_READ_DOCUMENT_TYPE | ||
ABAP code using 7.40 inline data declarations to call FM OIUOW_READ_DOCUMENT_TYPE
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 DOC_TYPE FROM OIUOW_DTCH INTO @DATA(ld_doc_type). | ||||
| "SELECT single XFELD FROM OIU_COMMON INTO @DATA(ld_force_db). | ||||
Search for further information about these or an SAP related objects