SAP OIU_ME_DOC_CHANGE Function Module for E&P Measurement: Change document
OIU_ME_DOC_CHANGE is a standard oiu me doc change SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for E&P Measurement: Change document 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 oiu me doc change FM, simply by entering the name OIU_ME_DOC_CHANGE into the relevant SAP transaction such as SE37 or SE38.
Function Group: OIU_ME_DOC
Program Name: SAPLOIU_ME_DOC
Main Program: SAPLOIU_ME_DOC
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function OIU_ME_DOC_CHANGE 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 'OIU_ME_DOC_CHANGE'"E&P Measurement: Change document.
EXPORTING
* I_CHECK = 'X' "
* I_TCODE = "Transaction code
EXCEPTIONS
ERROR_FOUND = 1
IMPORTING Parameters details for OIU_ME_DOC_CHANGE
I_CHECK -
Data type: CDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_TCODE - Transaction code
Data type: OIU_CM_TXN_CTL-TCODEOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
ERROR_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for OIU_ME_DOC_CHANGE 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_check | TYPE C, " 'X' | |||
| lv_error_found | TYPE C, " | |||
| lv_i_tcode | TYPE OIU_CM_TXN_CTL-TCODE. " |
|   CALL FUNCTION 'OIU_ME_DOC_CHANGE' "E&P Measurement: Change document |
| EXPORTING | ||
| I_CHECK | = lv_i_check | |
| I_TCODE | = lv_i_tcode | |
| EXCEPTIONS | ||
| ERROR_FOUND = 1 | ||
| . " OIU_ME_DOC_CHANGE | ||
ABAP code using 7.40 inline data declarations to call FM OIU_ME_DOC_CHANGE
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_i_check) | = 'X'. | |||
| "SELECT single TCODE FROM OIU_CM_TXN_CTL INTO @DATA(ld_i_tcode). | ||||
Search for further information about these or an SAP related objects