Ariba Reporting Multi-currency Feature Enablement Process

Slides:



Advertisements
Similar presentations
{Customer} Divisions Plan {Date} – {Version} Salesforce.com.
Advertisements

Testing Relational Database
SolidWorks Enterprise PDM Data Loading Strategies
2014 Supplemental Forms: Automation Instructions.
Module 12: Auditing SQL Server Environments
Polycom Quotes on Demand Tool Partner User Guide Version 1.1
With TimeCard appointments are tagged with information that converts them into time sheets. This way users can report time and expenses from their Outlook.
EORTC Remote Data Capture System For trials with electronic queries
Jason Morrill NCOAUG Training Day February, 2008
Page - 1 Ariba Buyer Upgrade Benefits/Enhancements  Streamlined User Interface  Requisition Function and Company eForms  Increased Performance.
Module 3: Table Selection
Planning for Divisions. Meeting Goals  Provide Baseline Overview of Divisions  Review Divisions Plan & Testing To Date.
TVAC Electronic Call Sheet System Team HeatWave Summer 2007.
Testing Session Testing Team-Release Management Team.
RMsis – v Simplify Requirement Management for JIRA.
ISetup – A Guide/Benefit for the Functional User! Mohan Iyer January 17 th, 2008.
TRW Code Updates for WCRS Document Activity ERD, EAR and Part Generator Changes August, 2006 TRW Automotive August, 2006 TRW Automotive August, 2006.
© ABB Group November 12, 2015 | Slide 1 ICV Implementation in Region ERP- Status update March 2011 & Plan for Go-Live REMSC, 2011.
How to Convert to a Managed Package Winter `07 Ralph Eddy January 4, 2007.
Master Data Management & Microsoft Master Data Services Presented By: Jeff Prom Data Architect MCTS - Business Intelligence (2008), Admin (2008), Developer.
Talentlink Reporting This should be the first page of your presentation.
Retail Transaction Processing Year End Review and Recent Issues RMS January 2007.
RMsis – v now with JIRA 5.0 support Simplify Requirement Management for JIRA.
Copyright © 2007, Oracle. All rights reserved. Using Change Management.
Module 5: Managing Content. Overview Publishing Content Executing Reports Creating Cached Instances Creating Snapshots and Report History Creating Subscriptions.
Ariba Punch-Out Catalog Process Flow
11 Copyright © 2004, Oracle. All rights reserved. Performing a Migration Using Oracle Migration Workbench (Part II)
Founded by Big Five Consulting ex-employees Oracle Gold Partner Focus on PeopleSoft 15 years of PeopleSoft experience Worked in both technical and functional.
2 Copyright © 2008, Oracle. All rights reserved. Building the Physical Layer of a Repository.
11 Copyright © 2009, Oracle. All rights reserved. Enhancing ETL Performance.
Payroll Allocations Information Session 2 nd February 2016 Heidi Woolf Solution Architect Finance Business Solutions Joanna Woo Business Analyst Large.
Migration to Central Data Exchange (CDX)
SCC P2P – Collaboration Made Easy Contract Management training
SUSE Linux Enterprise Server for SAP Applications
Planning the Digital Transformation Readiness Check for SAP S/4HANA
Introduction to CAST Technical Support
Compatible with the latest browsers; Chrome, Safari, Firefox, Opera and Internet Explorer 9 and above.
PearsonAccess EOC Training
Essentials of UrbanCode Deploy v6.1 QQ147
Systems Governance Group
Universal tool of data validation for support of implementation projects of ERP systems Yuri Byteryakov July 31, 2017.
Forecasts and Long Term Forecasts (Formerly Planning Schedules)
Commercial Skills Testing Information Management System (CSTIMS)
Self Healing and Dynamic Construction Framework:
Supplier Registration
The powerhouse PL/SQL upgrade option: Edition-Based Redefinition (EBR)
Introduction With TimeCard users can tag SharePoint events with information that converts them into time sheets. This way they can report.
XRN4361 – UK Link Release 2 Data Migration Plan for XRN /03/18
What Abstractors will love about SEER*Abs
Compliance Monitoring Activities State Inspections
My Oracle Support (The next generation Metalink experience) lynn
Advanced Invitations.
CAR Phase 22 Release Notes
What Abstractors will love about SEER*Abs
JD Edwards Support and Oracle Cloud Infrastructure: A Successful Path to Oracle Cloud
Polycom Quotes on Demand Tool Partner Manager Guide Version 1.1
The following is intended to outline our general product direction
Using JDeveloper.
Engineering Workbench Version 2.0
Audio for this webcast will stream via your computer’s speakers.
Automating and Validating Edits
Introduction to VSTS Database Professional
Ariba Light Account Supplier User Guide.
Workday 32 Alicia Maule January 14, 2019
Forecasts and Long Term Forecasts (Formerly Planning Schedules)
XRN4249 – Part B Data Migration Plan
and Forecasting Resources
OU BATTLECARD: WebLogic Server 12c
Presentation transcript:

Ariba Reporting Multi-currency Feature Enablement Process Latest Update: 03.27.2017

Feature Overview Two additional reportable currency codes made available as of FT14 (March 2015 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

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

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

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

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

Other Product Mgr. responsible for this feature Support contact Manny Cortez (manny.cortez@sap.com) Support contact Venki Namasivayam (venkatesh.namasivayam@sap.com) SA contact Chris Mastramico (christopher.mastramico@sap.com) Original FRD can be found in the following Perforce location //ariba/devweb/SpendVisibility/EER Related FRDs/SV-9009_SGS_Additional_Reportable_Currencies.docx