SAP OIUCM_READ_BUKRS Function Module for Read table OIUOW_DOC_TYPE (buffered)
OIUCM_READ_BUKRS is a standard oiucm read bukrs 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 oiucm read bukrs FM, simply by entering the name OIUCM_READ_BUKRS into the relevant SAP transaction such as SE37 or SE38.
Function Group: OIU_COMMON_TABLE_READS
Program Name: SAPLOIU_COMMON_TABLE_READS
Main Program: SAPLOIU_COMMON_TABLE_READS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function OIUCM_READ_BUKRS 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 'OIUCM_READ_BUKRS'"Read table OIUOW_DOC_TYPE (buffered).
EXPORTING
BUKRS = "Company code
* FORCE_DB = "Checkbox
IMPORTING
E_T001 = "Company Code
EXCEPTIONS
NOT_FOUND = 1
IMPORTING Parameters details for OIUCM_READ_BUKRS
BUKRS - Company code
Data type: BUKRSOptional: No
Call by Reference: Yes
FORCE_DB - Checkbox
Data type: OIU_COMMON-XFELDOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for OIUCM_READ_BUKRS
E_T001 - Company Code
Data type: T001Optional: No
Call by Reference: Yes
EXCEPTIONS details
NOT_FOUND - No record found
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for OIUCM_READ_BUKRS 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_bukrs | TYPE BUKRS, " | |||
| lv_e_t001 | TYPE T001, " | |||
| lv_not_found | TYPE T001, " | |||
| lv_force_db | TYPE OIU_COMMON-XFELD. " |
|   CALL FUNCTION 'OIUCM_READ_BUKRS' "Read table OIUOW_DOC_TYPE (buffered) |
| EXPORTING | ||
| BUKRS | = lv_bukrs | |
| FORCE_DB | = lv_force_db | |
| IMPORTING | ||
| E_T001 | = lv_e_t001 | |
| EXCEPTIONS | ||
| NOT_FOUND = 1 | ||
| . " OIUCM_READ_BUKRS | ||
ABAP code using 7.40 inline data declarations to call FM OIUCM_READ_BUKRS
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 XFELD FROM OIU_COMMON INTO @DATA(ld_force_db). | ||||
Search for further information about these or an SAP related objects