SAP UPE_DOC_CHECK_LOCAL_OK_CODE Function Module for Check ok_code of SD-integration without control-events
UPE_DOC_CHECK_LOCAL_OK_CODE is a standard upe doc check local ok code SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Check ok_code of SD-integration without control-events 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 upe doc check local ok code FM, simply by entering the name UPE_DOC_CHECK_LOCAL_OK_CODE into the relevant SAP transaction such as SE37 or SE38.
Function Group: UPE_DOC
Program Name: SAPLUPE_DOC
Main Program: SAPLUPE_DOC
Appliation area: R
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function UPE_DOC_CHECK_LOCAL_OK_CODE 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 'UPE_DOC_CHECK_LOCAL_OK_CODE'"Check ok_code of SD-integration without control-events.
EXPORTING
I_CODE = "
EXCEPTIONS
NOT_MINE = 1
IMPORTING Parameters details for UPE_DOC_CHECK_LOCAL_OK_CODE
I_CODE -
Data type: SY-UCOMMOptional: No
Call by Reference: Yes
EXCEPTIONS details
NOT_MINE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for UPE_DOC_CHECK_LOCAL_OK_CODE 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_code | TYPE SY-UCOMM, " | |||
| lv_not_mine | TYPE SY. " |
|   CALL FUNCTION 'UPE_DOC_CHECK_LOCAL_OK_CODE' "Check ok_code of SD-integration without control-events |
| EXPORTING | ||
| I_CODE | = lv_i_code | |
| EXCEPTIONS | ||
| NOT_MINE = 1 | ||
| . " UPE_DOC_CHECK_LOCAL_OK_CODE | ||
ABAP code using 7.40 inline data declarations to call FM UPE_DOC_CHECK_LOCAL_OK_CODE
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 UCOMM FROM SY INTO @DATA(ld_i_code). | ||||
Search for further information about these or an SAP related objects