Dear all
all of the last years we have used only "Standard EHS import" to do "something" (import data). Now there might be the need to learn on "practical level" how to use "OCC" for laoding purposes. For this I have one question
1.) We would like to use the "EXCEL" Variant to generate "input" (no "XML" file, but EXCEL file)
2.) EXCEL as such is "UNICODE" like oriented
3.) SAP as well the same
4.) so if SAP connection to OCC is "Unicode" enabled we whould be in a good starting position
But for two topics I have some doubts.
As you know: Using OCC we can load phrase data and specification data
Trouble 1 (which i would like to avoid): Example: If you need to prepare a load file (EXCEL): is there any risk in loading an "identifier" with more than 132 characters? (long text).. Or precise: is there any "obstacle" to look at if we would like to load identifiers, user- defined texts and phrases have a "long text" (which can come up often; mainly in the "phrase" area)
Trouble 2
Is there any risk regarding "Unicode"?
Example:.. as you know.. most of the language goes from "left to right"; but not e.g hebrew, arabic... => can we load such data (either identifier, phrase, user defined text) without risk?
From time to time in daily business I tave seen trouble with languages as japanese, thai, chinese etc.
Is there any risk here?
I would be very interested to get feedback as I do not feel well with the eastern languages
Thanks
C.B.