Contact us at +1.415.901.7500 or

Fusion Applications at IT Convergence – The Latest as on 3rd April ’12

Fusion Applications at IT Convergence – The Latest as on 3rd April ’12
ITC has been meeting almost every day with the Oracle team, following up the progress of the tickets with support on the installation. Oracle has assigned a single point of contact -because that is where resides the biggest challenge, getting the right resource within Oracle Support- who will be taking care of any service request create by IT Convergence.

We have set an aggressive date with Oracle to get the installation performed the week of April 9th.

A new training path for Fusion was shared among the steering committee and business users that will be involved on the Fusion Product. This learning path will be shared within the next days with the different departments of IT Convergence so everyone can start learning Fusion Applications.

During the past week we’ve talked to some clients about Fusion and they were concerned about its Globalization strategy.

Let’s start with definitions:

Internationalization: the process of designing one product with the flexibility to function worldwide Product is designed to allow for a choice of locales (MLS) and the ability to handle language data and locale specific format (NLS)

Translation: changing product UI strings and help from English into another language. All products requiring translation must first undergo translatability testing to ensure files meet translation standards

Localization: the process of developing specific functionality designated to certain regions or countries. Localization is handled by each development group based on their working model, and market requirement

The way that displaying multiple languages in Fusion Application works is from an architecture point of view is very similar to what was done in E-Business Suite. For every base table where the system might have something that needs a description like an inventory item. What Fusion will do is create a translation table to support that as well. The way that the translation table works there is a unique row for every language that is installed.

When fusion applications are installed there will be a primary language that is usually English for most global instances but could be any of the languages that are supported. Then additionally other languages can be installed. What will happen is the language table will then support a row for a description for each base table that requires specific translation. Then the way that that is wrapped together presented either in the user interface or through reporting or some of the other technology layers is through a language view. The language view basically joins the base table to the language that the user is accessing or wants preference to, to display the actual language value as opposed to the base table value. If in a given example a particular language does not have a translated value; so going back to the item description.

There’s a new concept in Fusion Apps called a “legal entity time zone”. This basically allows us to calculate what the accounting date default should be for a given transaction if someone is writing in a global single instance. An example, which will work for many global companies and even IT Convergence, is to have a shared service center that’s entering invoices for the world. In this case they may be doing it for a US legal entity. Even though the India time is on February 1st in the middle of the day the default accounting date should still be back to January 31st because it’s for the legal entity that the transaction is being entered.

Now in addition to this legal entity time zone there are still the capabilities related to the user preferred time zone. Some of the location based time zone around services and shipments that are available. The legal entity time zone actually drives logic to control accounting date to make sure that accounting policies are being met based on the legal entity for whom that transaction’s are being created. The way that that is configured is on the legal entity setup.

Based on the enabling architecture that Oracle covered, the components that will be covered in Fusion Applications V1 are:

  • Oracle will provide language out of the box capabilities for eight languages. On the bottom of the figure below you’ll see the details. In addition to this Fusion V1 has the capability within the application to support another 24 languages.
  • What Oracle has tried to do is, base the languages on some of the key markets that they think they will be able to go after for V1 adoption.
  • After that for some of the capabilities the global capabilities around key components like HCM and financials.
  • At the top of the figure below what you see are the country support. As you would expect things like CRM and sourcing in contracts have very good global coverage because they don’t tend to have legal requirements or other capabilities that are there. HCM and financials have limited global capabilities in V1 and Oracle will be adding localizations in subsequent releases.
That is a quick overview of Fusion Applications global capabilities for V1 and the fusion architecture related to Oracle’s global strategy.

Stay tuned for more information on the progress of the Oracle Fusion Applications implementation.

Thanks for your support!