SAP ISU_M_UNICODE_CHECK Function Module for INTERNAL: Check for UNICODE System









ISU_M_UNICODE_CHECK is a standard isu m unicode check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for INTERNAL: Check for UNICODE System 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 isu m unicode check FM, simply by entering the name ISU_M_UNICODE_CHECK into the relevant SAP transaction such as SE37 or SE38.

Function Group: EMIM
Program Name: SAPLEMIM
Main Program: SAPLEMIM
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function ISU_M_UNICODE_CHECK 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 'ISU_M_UNICODE_CHECK'"INTERNAL: Check for UNICODE System
EXPORTING
* X_CODEPAGE = 1100 "SAP character set identification

IMPORTING
Y_IS_UC_SYSTEM = "
Y_CHARSIZE = "
.



IMPORTING Parameters details for ISU_M_UNICODE_CHECK

X_CODEPAGE - SAP character set identification

Data type: CPCODEPAGE
Default: 1100
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for ISU_M_UNICODE_CHECK

Y_IS_UC_SYSTEM -

Data type: C
Optional: No
Call by Reference: Yes

Y_CHARSIZE -

Data type: I
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for ISU_M_UNICODE_CHECK 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_x_codepage  TYPE CPCODEPAGE, "   1100
lv_y_is_uc_system  TYPE C, "   
lv_y_charsize  TYPE I. "   

  CALL FUNCTION 'ISU_M_UNICODE_CHECK'  "INTERNAL: Check for UNICODE System
    EXPORTING
         X_CODEPAGE = lv_x_codepage
    IMPORTING
         Y_IS_UC_SYSTEM = lv_y_is_uc_system
         Y_CHARSIZE = lv_y_charsize
. " ISU_M_UNICODE_CHECK




ABAP code using 7.40 inline data declarations to call FM ISU_M_UNICODE_CHECK

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_x_codepage) = 1100.
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!