IW_C_CODEPAGE_INFO_GET SAP Function module

IW_C_CODEPAGE_INFO_GET is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name IW_C_CODEPAGE_INFO_GET into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: SI63
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM IW_C_CODEPAGE_INFO_GET - IW C CODEPAGE INFO GET

CALL FUNCTION 'IW_C_CODEPAGE_INFO_GET' "
* EXPORTING
*   use_dst_lang = SPACE        " c
  IMPORTING
    language =                  " sy-langu
    r3_codepage =               " iwcodepage-r3_cp
    html_codepage =             " iwcodepage-html_cp  HTML Character set
    encode_codepage =           " iwcodepage-encode_cp  Word: Document Encoding
  TABLES
    context =                   " sdokpropty
  EXCEPTIONS
    NO_LANGUAGE_FOUND = 1       "
    NO_CODEPAGE_INFO_FOUND = 2  "
    .  "  IW_C_CODEPAGE_INFO_GET

ABAP code example for Function Module IW_C_CODEPAGE_INFO_GET

The ABAP code below is a full code listing to execute function module IW_C_CODEPAGE_INFO_GET including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_language  
 
 TYPE SY-LANGU
,
ld_r3_codepage  
 
 TYPE IWCODEPAGE-R3_CP
,
ld_html_codepage  
 
 TYPE IWCODEPAGE-HTML_CP
,
ld_encode_codepage  
 
 TYPE IWCODEPAGE-ENCODE_CP
,
it_context  
 
 TYPE STANDARD TABLE OF SDOKPROPTY,"TABLES PARAM
wa_context
 
 LIKE LINE OF it_context
.


DATA(ld_use_dst_lang) = 'Check type of data required'.
 

"populate fields of struture and append to itab
append wa_context to it_context.
.

CALL FUNCTION 'IW_C_CODEPAGE_INFO_GET'
* EXPORTING
*   use_dst_lang =               ld_use_dst_lang
  IMPORTING
    language =                   ld_language
    r3_codepage =                ld_r3_codepage
    html_codepage =              ld_html_codepage
    encode_codepage =            ld_encode_codepage
  TABLES
    context =                    it_context
  EXCEPTIONS
    NO_LANGUAGE_FOUND =          1
    NO_CODEPAGE_INFO_FOUND =     2
    .  "  IW_C_CODEPAGE_INFO_GET

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_language
 
 TYPE SY-LANGU ,
ld_use_dst_lang
 
 TYPE C ,
it_context
 
 TYPE STANDARD TABLE OF SDOKPROPTY ,
wa_context
 
 LIKE LINE OF it_context,
ld_r3_codepage
 
 TYPE IWCODEPAGE-R3_CP ,
ld_html_codepage
 
 TYPE IWCODEPAGE-HTML_CP ,
ld_encode_codepage
 
 TYPE IWCODEPAGE-ENCODE_CP .


ld_use_dst_lang = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_context to it_context.