Symptom
Language codes that are 'length 1' are being converted to 'length 2' on datasphere after replication.
As a result, Data Type "Sting(2)" is used in the Local Table created by the Replication Flow.
However, when you import the source table as Remote Table in SAP Datasphere, the data type is "String(1)".
Environment
SAP Datasphere
Reproducing the Issue
- You use a replication from ABAP system to bring language data (as example from an ECC system - table T001 SPRAS column) to SAP Datasphere;
- Executing the flow you notice data is truncated, converted from length 1 to 2: String(2)
E (english) is converted to EN (English) as example.
Cause
The system works as designed as datasphere works with the ISO codes instead of LANG type used in ABAP systems.
Resolution
No actions are available to use the ABAP Lang type on Datasphere. ISO codes should be used instead as they are more widely used and available.
See Also
Keywords
Datasphere, conversion, language, ISO, ABAP Integration, Data Type Mapping , KBA , DS-DI-RF , Replication Flow Runtime , Problem
SAP Knowledge Base Article - Public