Collections from EBS source - restricting the Currencies entity, and hardcoding US language for Mode
We collect from an EBS source into Cloud SCP. Cloud has only US (American English) installed; EBS has multiple languages. Entities with a LANGUAGE / LANGUAGE_CODE column emit one row per source language, and the non-US rows error on load. We will not install additional language packs in Cloud. Affected entities: Currencies (LANGUAGE), Mode of Transport (LANGUAGE_CODE), Service Level (LANGUAGE_CODE).
Questions:
- Currencies: We plan to stop loading Currencies (with CurrencyConversion and CurrencyConversionType). Is excluding Currencies supported, and does it impact entities that reference a currency code — Item Cost, Organizations, Work Center Resources (values include USD and EUR)? Do those codes resolve against the Cloud currency setup (Manage Currencies) even if Currencies is not collected? Any impact to value-based or cross-currency planning?
Tagged:
0