Skip to content

ABAP Keyword Documentation →  ABAP − Reference →  Processing External Data →  Data Cluster →  IMPORT 

IMPORT - Text Language Rule

The rule described in this section is relevant only in cases where structures defined in ABAP Dictionary in a Unicode system are imported from the database and these same structures were exported in an MDMP system, and vice versa.

Character-like data can be stored in an MDMP system encoded according to different code pages. The character set ID stored in EXPORT is therefore not sufficient. For this reason, the statement IMPORT FROM DATABASE is used for evaluating the text language of database tables or structures defined in the ABAP Dictionary.

The following hierarchy applies to assignments of the text language to a structure:

  • A component that is labeled as a text language in a substructure or table-like component with a structured row type is only valid for this substructure or internal table.
  • A component labeled as a text language in a superordinate structure applies to this structure and to all other structures or table-like components nested in it, which do not have any components of their own that can be identified as a text language.
  • If a component labeled as a text language is among the freely selected components of the export/import tables in which the data is stored, this determines the text language for all elementary fields, structures, and internal tables in the corresponding data cluster that do not have their own language.
  • When importing from structures stored in the database, the text language determines the code page used to handle the character-like components of a structure as follows:

    • Importing MDMP data into a Unicode system

      The code page of the imported data is determined using the text language from the database tables TCPOC (table of text environments) and TCP0D (localization of the database). If no text language component is available, the character set ID stored during export is used.

      This rule is based on the assumption that the Unicode system has resulted from the conversion of an MDMP system. If it has not, this may lead to conversion errors.
    • Importing Unicode data into a MDMP system

      The imported data is handled according to the assignment of languages to code pages defined in the MDMP system, depending on the text language. If no text language component is available, the current text environment language is used.

    Other versions: 7.31 | 7.40 | 7.54


    Structures and internal tables with a structured row type that is based on types defined in the ABAP program do not have a text language. The character set ID stored during export is always used for these.