1. Ariba Reporting Multi-currency Feature Enablement Process
Latest Update:

2. Feature Overview
Two additional reportable currency codes made available as of FT14 (March SP)
This feature increases the current reportable currency code limit from 5 to 7
New customer realms enabled after March SP release will support up to 7 reportable currencies
Existing customers will not be able to take advantage of the two additional currencies without first talking to Ariba Support or the customer’s SA Delivery Lead(if the customer has SA)
Should not assume every existing customer can take advantage of the two new currencies without first talking to Support. Be careful what you communicate to customers
This feature was approved to be created and deployed for Pepsi and AZ. Evaluation would need to occur to determine if the feature can be made available for other customers
There are plans to increase the number of reportable currency codes for all customers later in the year but for now, Pepsi & AZ are the only two customers approved to receive this feature

3. Technical Background
Due to Oracle performance limitations we were unable to introduce more than 2 additional reportable currency codes
Once we have all customers migrated to HANA we can increase the number of reportable currencies (+10)
Technical changes made with this feature:
Updates to current system level param: Analysis.Admin.AllocateCurrencyColumns
Param currently has a default value of 5
After Mar. SP param value will be changed to 7
All database schemas will be changed to reflect new default value
New application (realm) level param: Analysis.SupportedCurrencyCodes
Introduced with Mar. SP
Supports default value = 7
Currently not possible to change the default value for new realms; will remain = 5
Changing the default would also impact existing customer realms
Upstream & Downstream Enablement teams will need to request to have the param changed for new customers; from 5 to 7
Ariba Support will control changing the param for existing customers
When selecting currency code values the UI will edit against this new param

4. Enablement Process (as of Mar. 2015 SP release)
New Customers
Applicable to all Upstream & Downstream solutions
Applicable to both shared & dedicated schemas
Update realm level param or contact Ariba Support requesting the realm level param to be changed: Analysis.SupportedCurrencyCodes = 7
When configuring reportable currency codes, specify up to 7 codes
Note: if data has already been loaded this will trigger full pull
If issues are encountered, contact Ariba Support
Existing Customers
If customer has SA (dedicated schema), contact the customer’s SA Delivery Lead
Do not enable the new currencies if the customer has SA. Requires truncation of SA tables
If Downstream & Upstream solutions are enabled on the same realm as SA the customer may not be able to take advantage of the additional currency codes
See applicable instructions on how to enable for SA customers

5. Enablement Process (as of Mar. 2015 SP release)
Existing Customers (cont.)
If customer does not have SA (shared schema)
Contact Ariba Support requesting to have the new param changed on the customer’s TEST realm: Analysis.SupportedCurrencyCodes = 7
Plan accordingly - once the reportable currencies are defined it will trigger a full pull of all ASM data
Truncation of reporting tables in advance not required
Configure up to 7 reportable currency codes in the customer’s TEST realm
This will trigger a repull of all ASM data
Depending on the amount of data being pulled Support may need to initiate custom loads in order to have all the data reloaded
All fields including the new measures for the additional currency fields should be populated
Once the ASM load has completed confirm the new currencies are available for reporting. Have the customer confirm results as well
Work with the customer and Ariba Support to plan the rollout to the customer’s prod. realm
If errors are encountered or if any of the loads fail, work with Support to have Eng. investigate the issue or have Support initiate custom loads if necessary

6. Enablement Process for SA (as of Mar. 2015 SP release)
Existing SA Customers
Contact Customer’s SA Delivery Lead
Determine if historical data can be reloaded or if customer is okay with new currencies going forward but no historical data reloaded (historical data would contain empty field values)
Truncate existing SA tables
Contact Ariba Support requesting to have the following new param changed: Analysis.SupportedCurrencyCodes = 7
Configure up to 7 reportable currency codes
Run an empty load on the dataload schema
Refresh data from presentation
Data should be in data load with new empty reportable currency fields
Refresh data from dataload to presentation
New fields will only get populated for new data going forward
Note: star schema export cannot be used to migrate the data. No currency conversation takes place with star schema export/import
If you have questions, reach out to Chris Mastramico (SA DL team). See next slide

7. Other Product Mgr. responsible for this feature Support contact
Manny Cortez
Support contact
Venki Namasivayam
SA contact
Chris Mastramico
Original FRD can be found in the following Perforce location
//ariba/devweb/SpendVisibility/EER Related FRDs/SV-9009_SGS_Additional_Reportable_Currencies.docx