SAP TERM_CONVERT_CODEPAGE Function Module for NOTRANSL: String in Unicode XSTRING umwandeln









TERM_CONVERT_CODEPAGE is a standard term convert codepage SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: String in Unicode XSTRING umwandeln 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 term convert codepage FM, simply by entering the name TERM_CONVERT_CODEPAGE into the relevant SAP transaction such as SE37 or SE38.

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



Function TERM_CONVERT_CODEPAGE 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 'TERM_CONVERT_CODEPAGE'"NOTRANSL: String in Unicode XSTRING umwandeln
EXPORTING
INTEXT = "SAPterm Text Field
* LANGU = SY-LANGU "SAP R/3 System, Current Language
* UNICODE = 'X' "

IMPORTING
OUTBUF = "SAPterm Text Field

EXCEPTIONS
CONV_ERROR = 1
.



IMPORTING Parameters details for TERM_CONVERT_CODEPAGE

INTEXT - SAPterm Text Field

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

LANGU - SAP R/3 System, Current Language

Data type: SYLANGU
Default: SY-LANGU
Optional: Yes
Call by Reference: Yes

UNICODE -

Data type: AS4FLAG
Default: 'X'
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for TERM_CONVERT_CODEPAGE

OUTBUF - SAPterm Text Field

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

EXCEPTIONS details

CONV_ERROR - Conversion Error

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for TERM_CONVERT_CODEPAGE 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_intext  TYPE STRING, "   
lv_outbuf  TYPE XSTRING, "   
lv_conv_error  TYPE XSTRING, "   
lv_langu  TYPE SYLANGU, "   SY-LANGU
lv_unicode  TYPE AS4FLAG. "   'X'

  CALL FUNCTION 'TERM_CONVERT_CODEPAGE'  "NOTRANSL: String in Unicode XSTRING umwandeln
    EXPORTING
         INTEXT = lv_intext
         LANGU = lv_langu
         UNICODE = lv_unicode
    IMPORTING
         OUTBUF = lv_outbuf
    EXCEPTIONS
        CONV_ERROR = 1
. " TERM_CONVERT_CODEPAGE




ABAP code using 7.40 inline data declarations to call FM TERM_CONVERT_CODEPAGE

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_langu) = SY-LANGU.
 
DATA(ld_unicode) = 'X'.
 


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!