FDI - Multi language Data Support

Question

Hello Team,

In the fusion source, we have the records maintained in multiple language say in english as well as in arabic..

ex: dept name is stored in both english and arabic in oracle fusion source with 2 records with different language code like EN and AR.

But the same data in FDI is getting extracted only with the english name and the arabic name record is not loaded into the warehouse.

Is this is the expected behaviour that FDI only loads the english record data and not the other language record irrespective of that record exist in fusion?

I can see like global parameter such as analytics language which we can change to english and arabic but i dont want to enable this option as it will entirely change the loaded records in single language in analytics platform.

Kindly let me know your valuable opinions/suggestion on this issue.

Brgds,

Hari

JohnW-Oracle · Accepted Answer

Hello @GTA

Thank you for the question. Yes, you can only select one language at a time. Therefore, having both English and Arabic translation rows in Fusion does not mean the prebuilt warehouse will retain both versions of the department name. See the Pipeline Parameters here:

https://docs.oracle.com/en-us/iaas/analytics-for-applications/doc/pipeline-parameters.html

A workaround to add Arabic department names while keeping the existing English pipeline setting would be to add Arabic department names through a separate dataset.

* Extract the Arabic names from Fusion. Include Department ID, Arabic Department Name, and effective dates where applicable. First check whether an extractable PVO exposes these translations. If it doesn’t, consider a Fusion BI Publisher CSV report.
* Load this extract into a custom FDI table. Use Data Configuration → Data Augmentation → Create → Dataset. Use Fusion Augmentations Source for a suitable PVO, or the BI Publisher connector for a report.
* Check the loaded data. Verify that Arabic characters are correct and that each department/version has only one matching Arabic name.
* Extend the department dimension. Through Semantic Model Extensions, join the custom table to the existing department dimension using the appropriate identifiers and effective dates. Expose an additional attribute called Department Name Arabic.
* Publish and validate. Display English and Arabic names together in a report. Confirm that department counts and measure totals remain unchanged, then schedule the custom dataset refresh.

Regards,

John