SAP OIUOW_COMBINE_GET_DO_DO_WK Function Module for OIUOW: COMBINE_GET_DO_DO
OIUOW_COMBINE_GET_DO_DO_WK is a standard oiuow combine get do do wk SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for OIUOW: COMBINE_GET_DO_DO 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 combine get do do wk FM, simply by entering the name OIUOW_COMBINE_GET_DO_DO_WK into the relevant SAP transaction such as SE37 or SE38.
Function Group: OIUOW_OWNER_COMBINE_DETERM
Program Name: SAPLOIUOW_OWNER_COMBINE_DETERM
Main Program: SAPLOIUOW_OWNER_COMBINE_DETERM
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function OIUOW_COMBINE_GET_DO_DO_WK 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_COMBINE_GET_DO_DO_WK'"OIUOW: COMBINE_GET_DO_DO.
EXPORTING
F3_BUKRS = "Company code
F3_VNAME = "Joint Venture
F3_DOI_NO = "Division of Interest
F3_OWN_NO = "E&P Owner
F3_OWN_INT_TYPE_CD = "Participant Interest Type
* F3_ISQ_NO = ' ' "Transferor owner interest sequence number
* F3_MAX_EFF_FROM_DT = "Effective From Date
* F3_MIN_EFF_TO_DT = "Effective To Date
F3_MAX_ROWS = "
TABLES
T_IOIU_DO_DO = "Division of Interest Ownership
EXCEPTIONS
NOT_FOUND = 1
IMPORTING Parameters details for OIUOW_COMBINE_GET_DO_DO_WK
F3_BUKRS - Company code
Data type: BUKRSOptional: No
Call by Reference: Yes
F3_VNAME - Joint Venture
Data type: JV_NAMEOptional: No
Call by Reference: Yes
F3_DOI_NO - Division of Interest
Data type: OIU_DOI_NOOptional: No
Call by Reference: Yes
F3_OWN_NO - E&P Owner
Data type: OIU_OWN_NOOptional: No
Call by Reference: Yes
F3_OWN_INT_TYPE_CD - Participant Interest Type
Data type: OIU_PART_INT_TYPEOptional: No
Call by Reference: Yes
F3_ISQ_NO - Transferor owner interest sequence number
Data type: OIUOW_OOWN_ISQ_NODefault: SPACE
Optional: Yes
Call by Reference: Yes
F3_MAX_EFF_FROM_DT - Effective From Date
Data type: OIU_EFF_FROM_DTOptional: Yes
Call by Reference: Yes
F3_MIN_EFF_TO_DT - Effective To Date
Data type: OIU_EFF_TO_DTOptional: Yes
Call by Reference: Yes
F3_MAX_ROWS -
Data type: IOptional: No
Call by Reference: Yes
TABLES Parameters details for OIUOW_COMBINE_GET_DO_DO_WK
T_IOIU_DO_DO - Division of Interest Ownership
Data type: OIU_DO_DOOptional: No
Call by Reference: Yes
EXCEPTIONS details
NOT_FOUND - Not found
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for OIUOW_COMBINE_GET_DO_DO_WK 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_f3_bukrs | TYPE BUKRS, " | |||
| lv_not_found | TYPE BUKRS, " | |||
| lt_t_ioiu_do_do | TYPE STANDARD TABLE OF OIU_DO_DO, " | |||
| lv_f3_vname | TYPE JV_NAME, " | |||
| lv_f3_doi_no | TYPE OIU_DOI_NO, " | |||
| lv_f3_own_no | TYPE OIU_OWN_NO, " | |||
| lv_f3_own_int_type_cd | TYPE OIU_PART_INT_TYPE, " | |||
| lv_f3_isq_no | TYPE OIUOW_OOWN_ISQ_NO, " SPACE | |||
| lv_f3_max_eff_from_dt | TYPE OIU_EFF_FROM_DT, " | |||
| lv_f3_min_eff_to_dt | TYPE OIU_EFF_TO_DT, " | |||
| lv_f3_max_rows | TYPE I. " |
|   CALL FUNCTION 'OIUOW_COMBINE_GET_DO_DO_WK' "OIUOW: COMBINE_GET_DO_DO |
| EXPORTING | ||
| F3_BUKRS | = lv_f3_bukrs | |
| F3_VNAME | = lv_f3_vname | |
| F3_DOI_NO | = lv_f3_doi_no | |
| F3_OWN_NO | = lv_f3_own_no | |
| F3_OWN_INT_TYPE_CD | = lv_f3_own_int_type_cd | |
| F3_ISQ_NO | = lv_f3_isq_no | |
| F3_MAX_EFF_FROM_DT | = lv_f3_max_eff_from_dt | |
| F3_MIN_EFF_TO_DT | = lv_f3_min_eff_to_dt | |
| F3_MAX_ROWS | = lv_f3_max_rows | |
| TABLES | ||
| T_IOIU_DO_DO | = lt_t_ioiu_do_do | |
| EXCEPTIONS | ||
| NOT_FOUND = 1 | ||
| . " OIUOW_COMBINE_GET_DO_DO_WK | ||
ABAP code using 7.40 inline data declarations to call FM OIUOW_COMBINE_GET_DO_DO_WK
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.| DATA(ld_f3_isq_no) | = ' '. | |||
Search for further information about these or an SAP related objects