302063 - Correspondence Language

 

Symptom

Other Terms

User defined language, customer reserved language


Reason and Prerequisites

In non-Unicode SAP systems, only a limited number of language codes is available. The following requirements cannot be fulfilled in a non-Unicode system:

  • A language code is required for a variant of an existing language. Different terms or wordings are used to describe the same item in same text format for different variants of one language. For example, there are variants of English like English in Great Britain, English in Australia, etc. 
    (In a Unicode system, most of such variants are already available as predefined language codes.)
  • A language code is required for different, country dependent formats or layouts of a text. Examples are invoices or legal files. 
    (In a Unicode system, this can also be covered by the existing predefined variants.)
  • In a non-Unicode system, documents or forms in an unsupported language code are required. 
    (In a Unicode system, all ISO 639 language codes are supported.)



Solution
 

Concept

Correspondence Languages are a means to partly overcome the limitations of non-Unicode systems outlined above. The available language codes are 'Z2' to 'Z9'. A Correspondence Language in a non-Unicode system can be defined with the same technical properties as one existing language, the 'master language'. It must use a code page which is configured in the system.

Example: A system is configured as a single code page system with English and Spanish (code page 1100). In this system, one could define a Correspondence Language "Basque" using code page 1100.

Limitations and disadvantages

  • The Correspondence Languages 'Z2' to 'Z9' and the customer language 'Z1' are SAP proprietary and only known to ABAP based components. They are not understood in Java or Web based environments. It is therefore no longer recommended to use these language codes.
  • A Correspondence Language is defined within one system. When data is exchanged between systems in a system landscape, the definition of the Correspondence Language must be identical in each system.
  • A Correspondence Language can only be used for creating SAPscript standard texts, forms, and styles, not for other purposes.  It cannot be used as a logon language. This is a difference to the customer language 'Z1' (see SAP Note 112065).
  • Once 'Z1' or a Correspondence Language has been introduced, there is no migration tool available to automatically migrate the data to a regular language code.
  • Before deleting or redefining an existing Correspondence Language, you have to check manually whether this language code is still used in SAPscript or Smartforms documents (forms, styles or standard texts).

Correspondence Languages in Unicode systems

In case you still have a non-Unicode system, we strongly recommend to convert it to Unicode before introducing any new languages. In Unicode systems all ISO 639 language codes are supported, as well as many combinations of language with country or region or script. Please see SAP Note 42305 on how to activate them.

Therefore, it is generally not necessary to set up a Correspondence Language in a Unicode system. Exceptions are the following cases:

  • The language exists in a non-Unicode system, and you want to continue using it after the conversion to Unicode.
  • You need to exchange data in a system landscape between Unicode and non-Unicode systems. The language code used for the data is a Correspondence Language code (see SAP Note 871945).


Maintaining Correspondence Languages

  • Run the report 'RSCPCOLA' to define, redefine, or delete a Correspondence Language.
    • To define or redefine a Correspondence Language:
      • Select a Correspondence Language code (Z2, Z3, Z4, Z5, Z6, Z7, Z8, or Z9).
      • Type the description of that language into the 'New language name' field.
      • Select a master language of the Correspondence Language. In a non-Unicode system, the master language selection determines the character set of the Correspondence Language. The master language must be one of the supported languages in your system.
      • Press the 'Assign' button.
      • Choose 'Yes' to confirm it, otherwise 'No' or 'Cancel'.
    • To delete an existing Correspondence Language:
      • Select the line with the Correspondence Language you want to delete from the 'Currently installed Corresponding Language' table.
      • Press the 'Delete' button.
      • Choose 'Yes' to confirm it, otherwise 'No' or 'Cancel'.
  • Run the report 'RSCPINST' to activate or deactivate a Correspondence Language.

    Follow the steps described in SAP Note 42305, section "Solution", for the Correspondence Language.


Attention

After an upgrade of the SAP system, you have to run the report RSCPCOLA again.

 

  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
社会发展日新月异,用计算机应用实现数据管理功能已经算是很完善的了,但是随着移动互联网的到来,处理信息不再受制于地理位置的限制,处理信息及时高效,备受人们的喜爱。所以各大互联网厂商都瞄准移动互联网这个潮流进行各大布局,经过多年的大浪淘沙,各种移动操作系统的不断面世,而目前市场占有率最高的就是微信小程序,本次开发一套新冠肺炎服务预约微信小程序有管理员,医院,用户三个角色。管理员和医院都可以在后台网页登录,管理员功能有个人中心,医院管理,用户管理,防疫措施管理,疫苗信息管理,核酸检测管理,疫苗预约管理,核酸预约管理,接种信息管理,检测结果管理,系统管理。医院可以注册登录,管理疫苗信息和核酸检测信息,审核疫苗预约信息和核酸预约信息,查看接种信息和检测结果。用户可以在微信小程序注册登录,可以预约疫苗和核酸检查,可以查看到接种信息和检测结果。新冠肺炎服务预约微信小程序服务端用Java开发的网站后台,接收并且处理微信小程序端传入的json数据,数据库用到了MySQL数据库作为数据的存储。这样就让用户用着方便快捷,都通过同一个后台进行业务处理,而后台又可以根据并发量做好部署,用硬件和软件进行协作,满足于数据的交互式处理,让用户的数据存储更安全,得到数据更方便。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值