2315083 - Instance Refresh for Reporting and WFA Products (WFA/Canvas/Advanced Reporting/Story Reports)

• A HCM Suite instance refresh does not include all reports.
• Additional steps are required for certain reports to work.
• This KBA article covers all the exceptions and the additional steps required. 

Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.

• SAP SuccessFactors HCM Suite
• SAP SuccessFactors Workforce Analytics

1. What is a BizX Refresh?
2. What do you need to consider when getting a BizX Refresh?
3. What reporting tools are refreshed?
4. Instance Refresh Process?
5. List of Reporting products refreshed
6. What to expect and to do per reporting products enabled in my target instance?
7. Q&A Section 

What is a BizX Refresh?

• An instance Refresh is copy of your BizX environment into a target instance. 
• After the refresh, the instance "refreshed" and origin instance will be a "clone" instance.
• For this reason, as we clone all settings and data but your instance might have also different products integrated, SuccessFactors refresh team need to re-establish the link with other products that are stand alone product (not in BizX environment) such as WFA/Canvas Reports/Report Centre/Story Reports and other products.

What do you need to consider when getting a BizX Refresh?

You need to know what products are implemented in your target instance such as Canvas reports, Workforce Analytics/Planning and Advanced Reporting for Employee Central, Report Centre and Story Reports

Instance Refresh Process?

• This task is performed by SuccessFactors Cloud Product Support team & engages different teams.
• This KBA is dedicated for the Reporting/Analytics part. For other products, please refer to the instance refresh KBA. 

List of Reporting products refreshed

Report Type that are supported:	Some features not included in the refresh:
Table	Canvas Reports (Reports itself will not be migrated)
Spreadsheet	Canvas & WFA Users
Dashboard / Youcalc	Canvas & WFA Menu
Pixel Perfect Talent Card (PPTC)	Canvas & WFA Bundles
Classic reports	WFA/P
List views	All Queries in Canvas/WFA
Advanced Reporting for Employee Central	Story Reports File itself will not be migrated
Story Reports	SAC Users from source will not be migrated to target

What to expect and to do per reporting products enabled in my target instance?

Adhoc / Spreadsheet / Dashboard - Youcalc / Pixel Perfect Talent Card (PPTC) / Classic Reports / List view:

• No action needed.
• Your reports will be copied exactly as the origin instance.
• You should have exactly the same configuration between your Origin and Target refreshed instance.
  • NOTE: Tables, tiles and dashboards available before the refresh will NOT be available after the refresh

Canvas Reports:

• You should specify in the instance refresh that Canvas Report is implemented in your target instance.
• The teams working on the instance refresh will reestablish the connection to your Canvas instance. 
• Canvas reports are not copied from Source Instance to Target Instance.

Advanced Reporting for Employee Central:

• The Advanced Reporting refresh will be taken care automatically with the BizX Refresh.
• Why?  - the refresh will overwrite all your Employee Central data + Configuration (Datamodel/MDF/metadata). 
• Advanced Reporting metadata which is stored in a separate database needs to be refreshed.
• This can be done by customer from 'Admin > Purge Advanced Reporting Metadata Cache' (or) they can reach Support to perform the same.
• Canvas reports, built using Advanced Reporting, are not copied from Source Instance to Target Instance.

WFA/P:

• WFA is not included in this refresh.
• However, if you previously had WFA link to your instance, CPS refresh team will reestablish the connection to your Canvas instance.
• Make sure you have specified this product in the refresh case.

Story Reports:

Instance refresh process is supported on Story Reports, so customers can carry their usual instance refresh activity on their Story Reports enabled instances. The steps required for customer on instances refreshes are to:

Before the Instance refresh is triggered:

Please make sure that the property "ips.delete.existedbefore.entities":"true" is maintained for SAC target tenant in IPS.

After the Instance refresh is completed:

• Run the IPS sync twice, but do not reset the source or target. First run: It is important to run it twice because the IPS will read the users once and delete the delta users on the first run. Although you may see users with same email, name, etc. in SF but unique identifier between SF and SAC system is Person UUID. Person UUID is copied over from source system hence SAC will not recognize any user which already exist in there; hence the need to drop all users and re-create

1. • On the second run it will create the users correctly with the new information and Person UUID that came with the source.
     • In case IPS Sync is failing with Authentication Error, after instance refresh, please check the below:

       • If Refresh Source Instance and Target Instance had the same password for the user, then no action will be required

       • You may run a Read job to confirm if it fails to read users, then you need to update the password on above IPS screen. If you do not know the password- reset it on SF, then update on the IPS source system and (only if Password migration from KBA 2950998 has been set up) IAS source system.

Story Reports Notes:

1. Reports of Type Stories are not copied from Source Instance to Target Instance during Instance Refresh.
2. The Stories available in Target Instance prior to refresh will be retained in the Target Instance. However, their ownership will moved to the System User. Customers would have to manually perform 'Change Ownership' of each Story. Hence, after the refresh is completed, the story reports of the target instance will be under "All Reports" tab of Report Center.
3. The instance refresh process will not enable the Story Reports on the target instance if the source instance already has the tool enabled. Story Reports should be enabled separately as per KBA 2877303.

FAQ:

Q: What are the potential issues post instance refresh process?

• Access to WFA/Canvas not available post refresh: 
  For example - A login page is displayed when I try to access to Analytics.
  Make sure that you have notified the refresh team if WFA/Canvas is implemented in your instance. 
  Wait for SuccessFactors confirmation before to log-in to WFA/Canvas. 
  
  
• The Advanced reports doesn't work anymore after refresh: 
  This could be an expected behaviour as you have refreshed all your configuration and data.
  In Canvas or Advanced Reporting, your reports can be no longer valid because you have refreshed your data and configuration for all HXM Cloud suite products. You should revalidate your reports or create new reports.

Q: How long the service will be reestablished after the refresh for WFA / Canvas?
A: It could take 2-3 business days to reestablish the connection between your HXM Cloud instance and WFA/Canvas instance. 

Help Portal Guide: Instance Refresh Overview

sf, success factors, biz x, ORD, ODS, WFA, ANA, reload, Request, Process, Company, center, canvas, table, Story, Story Reports, instance refresh, BizX refresh, reporting tools, SuccessFactors HCM Suite, Workforce Analytics, Canvas Reports, Advanced Reporting, Story Reports, Report Center, Employee Central, SAC sync, metadata cache, WFA connection, reporting products, target instance, refreshed instance , KBA , LOD-SF-ANA , Analytics & Reporting (Ad Hoc, YouCalc, ORD) , LOD-SF-WFA , Workforce Analytics & Planning , LOD-SF-ANA-ADH , Adhoc Reports & Report Builder , LOD-SF-ANA-ADV , Advanced Reporting (ODS) , How To

SAP SuccessFactors HCM Suite 2511 ; SAP SuccessFactors Workforce Analytics all versions