2791468 - Instance Refresh Tool for BizX & LMS

Symptom

How to enable the Instance Refresh Tool for my Instance
Setting Permissions for Instance Refresh Tool
Accessing the Instance Refresh Tool
Pairing the Instances
Creating an Instance Refresh Request
Monitoring instance refresh Tool
How to handle various refresh status
What's new in instance refresh? Check out the SAP Help guide.

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

Environment

SAP SuccessFactors HCM Suite
SAP SuccessFactors Learning

Resolution

BEST PRACTICE SUGGESTIONS:

Allow adequate time when scheduling a refresh in case of any validation issues. If you have deadlines to meet that the refresh needs to be done in advance of, we recommend scheduling the refresh in advance of these deadlines, rather than one or two days before.
In the event of failure or any refresh issues where you need to open a case under LOD-SF-PLT-IRT, always include the refresh log from the Instance Refresh Center to allow us to investigate and reach a solution ASAP.
The Instance Refresh Tool should always be used when scheduling BizX refreshes, manual refresh requests are only accepted when the tenant is not eligible for IRT usage.
In the event of a scheduled IRT failure, and you need to run the manual refresh instead, please proactively provide a completed manual refresh request form, which is found attached to our Manual Refresh KBA linked below.This will allow Support to get the refresh scheduled ASAP.

Please check the limitations listed below. Should you plan to perform a cross Data Center refresh or if you have reverse proxy configured in your Source or Target instance, please proceed with Manual Refresh (Refer to KBA 2277508 - SuccessFactors Cloud Manual Instance Refresh Process & FAQ.)

LIMITATIONS:

The tool does not support cross Data Center refreshes at this time (e.g., DC2 to DC4).
The maximum supported tenant schema size for BizX refreshes using the Instance Refresh Tool is 550GB. To know your schema size, please refer to KBA 3168167 for more details.
For LMS Refreshes, only LMS tenant schema sizes that are less than 500 GB can be refreshed via IRT (the best way to determine if this is a limitation is by scheduling IRT for LMS, since the tool will notify you if not eligible due to size limitation). Moreover, to know if you are eligible for LMS refreshes via IRT, please open a case under the "LOD-SF-LMS-IRT" component for Customer Support to check. Further details on LMS Refreshes via IRT can be found in KBA 2835061.
Similar for Manual Refreshes, refreshes from Higher to Lower Version (e.g., Source - b2105 and Target - b2011) are not supported during blackout periods. The blackout period is the time between the two tenants not being on the same version.
As is also the case with Manual Refreshes, weekend refreshes are not supported using the Instance Refresh Tool. We can only support refreshes from Monday through Thursday between 8pm to 8am in the timezone of the Data Center where these instances are located.
Onboarding 2.0 Enabled instances are part of the BizX Refresh and supported via the IRT tool. However, where Source instance does not have Onboarding 2.0 enabled and the target instance does have Onboarding 2.0, it will result in overwriting Onboarding on the target to a blank configuration. See 2912722 for further details. Note: For Onboarding 1.0 customers, this module is not part of BizX, and you will be required to create a support case with the Onboarding team for manual Onboaring refresh. The IRT tool does not yet support Onboarding 1.0 refreshes.
Refreshes to Production type tenants are blocked using the tool. Proceeding will result to "Validation Failed" status. See 2978845 for further details. Note: Non-Production tenants hosted in Production server stacks do not fall under this limitation and can be refreshed using the tool.
The Instance Refresh Tool usage is not supported for Sales Demo tenants.
Starting b2111 release, if the instance refresh request for HXM Suite, SAP SuccessFactors Learning, or a combination of both HXM Suite and SAP SuccessFactors Learning products fails, then the next refresh will be blocked until the failed application is restored to its original state.

Instance Refresh entitlement:

Every company is entitled to two refreshes per tenant for a calendar year. For example, if a Customer has 5 tenants, including Production and Non-Production, then they will be entitled to get 10 refreshes every year as a part of the standard purchase. More details are in the help guide Knowing Your Company's Refresh Entitlement.

How to use the Instance Refresh tool?

The following section of our Help guide details how to use the tool, starting from its pre-requisites-> Using the Instance Refresh Tool | SAP Help Portal.

The instance refresh tool will not be visible in your instance until the RBP permission have been granted to your refresh admin.

Business Process Engine (BPE) should be enabled in Provisioning.
Enable Instance Refresh — should be enabled in Provisioning.
Permissions required for the tool-> SAP Help Portal

Warning: Ensure the username/user ID you are using to schedule the refresh has less than twenty (20) characters.

If you still do not find the Manage Instance Refresh permissions, please contact SAP Cloud Support by raising a ticket.

For more details on the Instance Refresh Tool, please refer to the SAP help Document - Instance Refresh Guide.

Considerations Pre-Refresh:

Please refer to the Instance Refresh Tool Admin Guide - "Things to Know Before Refreshing the Target Instance" section for all considerations you will need to check prior to submitting a refresh using the tool.
As of b2205, as a pre-validation check, we've integrated the Check Tool with the Instance Refresh Tool. We recommend that you run the checks using Check Tool before you submit an instance refresh request. Please refer to Check Tool Integration with Instance Refresh Tool.
While scheduling a Refresh from a Source to a Target, make sure the Target instance does not have any other refreshes scheduled (as Source) at a date after this current refresh schedule. Doing so will overwrite the refresh request scheduled from the Target.
Example: Let's say a refresh request is being submitted from A -> B for a future date. Another refresh request is submitted from B -> C, which is scheduled to be executed after the scheduled date of the A -> B refresh. In that case, with the completion of the A -> B refresh, the refresh schedule for B -> C will get wiped off.

In this case, wait for the refresh already scheduled from the Target to be executed first, and then schedule another refresh to that Target.
In addition to the notes on the guide, below are some important updates that you will need to be aware of prior refresh:

Time Clock IN and Clock OUT
Starting b2105 release, customers with Time Clock IN and Clock OUT were blocked for IRT refreshes. Starting b2311 release (aka 2H 2023) Time Clock IN and Clock OUT is supported [Reference Support for Clock In Clock Out in Instance Refresh | What's New Viewer - SAP Help Portal]
Career Explorer
The tool will automatically revert the feature (enable/disable) as originally set in the Target instance pre-refresh.
Onboarding 2.0
Onboarding 2.0 is now part of BizX Refresh. However, if Source does not have this enabled, this is not supported. Please refer to KBA 2912722 for further details.

SAP Build Work Zone, advanced edition and SuccessFactors Work Zone : Refresh is not available for SAP Build Work Zone, advanced edition and SuccessFactors Work Zone. However, if you have SuccessFactors instance integrated with Work Zone, then the refresh may have impact on the workzone user sync. Hence, post refresh we recommend you to do a full sync from SuccessFactors to IAS and SuccessFactors to Work Zone for HR Cards to work seemlessly in Work Zone

Recruiting Marketing (RMK)
RMK is not included in BizX Refresh. See 2883870 - RMK Instance Refresh Request - Recruiting Marketing for further details.
Career Site
For Career Site integration with IAS, if your target instance has this configured, please take a backup of the setting in Target > Admin Center > Manage Service Provider Configuration for Identity Authentication Service (IAS) (formerly 'Career Site Identity Provider (IDP) Configuration'). This is not included on the settings automatically reverted for BizX refreshes using IRT, hence you have to revert this manually in Target post-refresh.
Recruiting Management (RCM)
Please note that if RCM is not enabled in the Target instance or planned to be, there could be issues in the future when purging users in the Target instance because of RCM data in the DB that will get copied over during the instance refresh, which will prevent users from being purged.
Workforce Analytics (WFA)
This is not copied as part of the BizX refresh. Refer to 2341764 - Workforce Analytics (WFA) Refresh - FAQ KBA for further details.

Canvas (Advanced Reporting data source) refresh is now part of the BizX refresh. However, Canvas Reports are not included in the refresh. Canvas reports are not copied into the Target instance. Please read KBA 2315083 for more details as well as the reference blog on Advanced reporting.

Note: KBA 2673792 provides instructions on how to export and import Canvas Reports from one instance to another.
People Analytics Report Story
The Instance refresh process will be supported with SAP SuccessFactors People Analytics, so customers can carry their usual instance refresh activity on their SAP SuccessFactors People Analytics enabled instances. It is important to Export the report stories from the Target instance prior to the Instance refresh. Further details are in KBA 2315083.

For Support: To confirm if a customer has Embedded Edition of People Analytics on the instance, you can check this in the Provisioning > Company Settings > SAP Analytics Cloud Application URL.
Attachments
Starting b2005, attachments will not be copied for BizX Refreshes. For more details, please refer to KBA 2900061 - Attachments are empty post BizX Refresh - HXM Suite.

Note : The compensation and variable pay statements will get copied during Instance Refresh. This behavior is expected as Compensation/Variable Pay Statements are not stored as Attachments.
If you do not want to have the statements available in the target instance, you should trigger the Recall Statement job
Note: Attachment filenames will not be anonymized as part of the anonymization in Instance Refresh Data Anonymization Fields.

OpenText
If you are using OpenText as your Document Storage in the Target instance, please refer to KBA 2926317 - Restoring Integration with OpenText - post-refresh.
Email Masking
Only Employee Profile Emails and Recruiting emails are masked as part of the refresh.

Mask Employee Profile Email Address - is applicable if you have populated the field in the IRT during the submission of the request.

Mask Recruiting Candidates Email Address - There is no way to skip external masking field for RCM while submitting the Refresh Request in the IRT. This Mask Recruiting Candidate Email Address for External Candidates field was made as mandatory to avoid the live email notification being sent to external candidates from Target test/dev instances post Instance Refresh (The same thing will happen if you go with Manual Refresh as well skipping the masking part).
Note: If you have Employee Central enabled in Source, please reach out to your administrator to perform a manual import to mask Employee Central emails post-refresh. Not performing this step will result for masked emails in the User Data file to be overwritten by live emails as soon as HRIS sync is triggered.
Single Sign-On (SSO)
If the Source instance has Single Sign-On (SSO) setup and Target has Non-SSO setup, make sure that a Non-SSO admin account is maintained in the Source instance before refreshing your Target instance. This admin account allows you to access the Target instance after refresh.
If you are using IAS in the Target instance, please refer to the "considerations post-refresh" section of this KBA as there are post-refresh activities needed to be carried out by the admin user.
Employee Central - Timesheet integration (Kronos or Workforce)
Restoration of the URLs under Provisioning > Company Settings > Enable Employee Central V2 timesheets link URL is currently not supported in IRT refreshes. If you have this configured in the Target instance, please engage your partner to save a backup of this setting in the target instance, or please save the URL displayed while accessing Time and Attendance page in the Target instance and open a case with Support - "LOD-SF-PLT" to reconfigure this back in Provisioning backend.
Integration Center Jobs
Integration Center jobs are currently not restored in the Target instance as part of manual and IRT refreshes. Should you require these jobs to be reverted in the Target post-refresh, please save a backup of these jobs and revert post-refresh.
Intelligent Services Center
ISC Flows containing custom connectors are not automatically restored post-IRT Refresh.
OAuth Configurations
When a refresh is performed via the tool, the OAuth2 Client Configuration, and other security related artifacts like X.509 certificates, key pairs WILL NOT be copied from Source to Target.
Custom Login Page
If you have a custom login page configured in the Target, you will need to copy and backup the configuration and restore it after the refresh is completed. This is because currently the backup and restore is not happening in IRT for Custom Login Page Settings.
Business Process Engine (BPE)
Business Process Engine (BPE) should be enabled in Source & Target instance Provisioning -> Company Settings page. Set the default option "Use ProcessJob Identity". If the "Specific User Identity" is kept for any particular reason, a valid username must be provided.
Joule, GenAI and Skills
Instance Refresh will have some impacts to Joule, GenAI and Skills. Therefore, pre and post-refresh checks are required by customers. For more details, refer SAP KBA 3531590 - The Impacts to Joule, GenAI and Skills AI during the SuccessFactors Instance Refresh Process.
Microsoft Teams Integration with Work Tech:
1. We recommend to disconnect the Work Tech feature in your target instance before refresh and reconnect post refresh to avoid dirty data which causes intermittent disconnection or unexpected errors in target instance
2. If source instance is connected, post refresh, the target would also appear to be connected. Hence, we recommend you to disconnect the target again.
3. If the target doesn't have any pre-existing connection, then post instance refresh please disconnect the connection.

Jobs
The list below contains the job types and how they are handled during automated refreshes. For any jobs not listed below, please open a separate case with the respective module team owner of the job if you wish those to be reinstated post-refresh.

As an administrator, we highly advise that you check the Job Scheduler Manager tool from Admin Center for you to see which FTP jobs you currently have in the Target instance pre-refresh. Please refer to KBA 2906009 on how to use this tool.

How does COPY work? - These are either background jobs that run as is or were previously scheduled explicitly as per customer’s request and do not have any impact on any of the other integrated systems. Post-refresh, there are no required changes for the jobs listed below.

How does RESTORE work? - These jobs have an impact on integrated systems, e.g., FTP jobs. The listed jobs below are restored in the target instance post-refresh according to its original configuration.

Only “SUBMITTED” and recurring jobs listed below will be “RESTORED” in the target instance post-refresh. Should you require any inactive/not submitted jobs to be reinstated in the instance, this will need to be manually backed up and re-configured in the target post-refresh. Please use “scheduled job manager tool” to view the complete list of jobs.
As the data on the refreshed instance will have changed, the job owner for the mentioned scheduled jobs may need to be updated if the job owner no longer exists in the target post-refresh.

Any jobs not listed below will not be restored nor copied.

Job Type	Action Type
PurgeExpiredReportsJobType	COPY
RegisterMissingAnalyticsArtifactsInActionSearchJobType	RESTORE
AdhocReportExportJobType	RESTORE
MigrateCareerPathV2ToJDM2RolesJobType	COPY
AutoMatchForSupervisedProgramJobType	COPY
GeoLearningActivityLoadJobType	COPY
MentorUnavailabilityNotificationJobType	COPY
UpdateCDPMentoringSACLabelJobType	COPY
DevelopmentTemplateConversionJobType	COPY
CatalogImportJobType	RESTORE
LACmpMappingExportJobType	RESTORE
LACmpMappingImportJobType	RESTORE
MassEditImportJobType	RESTORE
MentoringProgramJamGroupInviteJobType	COPY
MentoringProgramLaunchJamActivityJobType	COPY
MigrateDevGoalDataForAdhocReportBuilderJobType	COPY
SendSignupEmailJobType	COPY
TGMDevGoalImportFTPJobType	RESTORE
UserReLMapImportJobType	RESTORE
InstanceRefreshAuditTablesJobType	COPY
UnifiedSuiteReportingConfigJobType	RESTORE
InvokeSPCAPIToRefreshSACTenantDetailsJobType	RESTORE
DeleteAllUserPhotoJobType	RESTORE
BatchExportPhotoJobType	RESTORE
DeleteDuplicateBackgroundDataJobType	COPY
LiveProfileExportJobType	RESTORE
LiveProfileImportJobType	RESTORE
BatchUploadPhotoJobType	RESTORE
JobServerRegularDataPurgeJobType	COPY
IRAsyncPredictJobType	RESTORE
JobInfoImportFollowUpProcessingJobType	COPY
DeltaUserExportJobType	RESTORE
UserExportJobType	RESTORE
UserImportJobType	RESTORE
SaveReportConfigChangesJobType	RESTORE
IRPredictionReportJobType	RESTORE
PurgeDynamicLoggerGlobalJobType	COPY
NotificationPurgeJobType	COPY
RDFReportExportJobType	RESTORE
MigrateReportTilePreferencesJobType	RESTORE
PicklistExportJobType	RESTORE
PicklistImportJobType	RESTORE
SnapShotLnrJobType	COPY
SyncPIIDataJobType	COPY
HrisPCGSumsSyncJobType	COPY
ECAlertsAndNotificationsJobType	COPY
WFAutoApprovalJobType	COPY
WFAutoEscalationJobType	COPY
WorkflowActionReminderJobType	COPY
PayScalePayIncreaseJobType	COPY
DeltaLiveProfileExportJobType	RESTORE
PositionManagementRegularCleanUpJobType	COPY
PositionManagementRegularCleanUpSchedulerJobType	COPY
BizXDailyRulesProcessingBatchJobType	COPY
CustomerInstanceDataExportJobType	RESTORE
BulkUserImportJobType	RESTORE
DeltaUserImportJobType	RESTORE
HrisSyncJobType	COPY
BIZXReportExportJobType	RESTORE
MDFImportFTPJob	RESTORE
MDFExportJob	COPY
SchedulerServiceHelperTest	RESTORE
SyncWfaAndBizxInstanceJob	RESTORE

RefreshRBPRulesJob

COPY

Note: The RBP Refresh Rules is a legacy job for updating RBP. It is only used by a small number of customers. The majority of customers are using the Realtime refresh framework for updating RBP which is copied and restored with the refresh. See KBA 2766870.

Considerations post-refresh:

As part of the post-refresh activity, select scheduled FTP jobs will get restored Automatically in the Target Instance, e.g., Username, Filename, and Password. Please refer to the list of jobs above.
PGP keys are restored as part of refreshes made throught IRT.
The job owner will also get restored post-refresh, which means if the job owner no longer exists in the newly-refreshed instance, the job will fail with "Invalid job owner".
After a system instance refresh, information such as job requisitions history or applicant history is lost. This is expected behavior. See KBA 2834508 - Job requisition history and applicant history lost after instance refresh - Recruiting Management for further details.
If the Target instance is integrated with SAP Cloud Identity Authentication Service (IAS), please refer to KBA 2954491 for the refresh impact on IAS integration and required actions.
This process is irreversible. Requests for roll back after successful refresh are no longer accepted as restoring data through reverts in already successful refreshed tenants can cause loss of data and broken functionality. It’s a risky proposal that can cause more inconvenience to customers. We do not recommend doing that.

Instance Refresh Tool Statuses:

For the full list of status for Instance refresh tool and required actions (if any) for each status, please refer to the Admin Guide.

[Provisioning Opt-In Feature] Data Anonymization

You can now mask personally identifiable fields for the following modules when performing refreshes using Instance Refresh Tool: Recruiting Management; Employee Central; and, User Management. See KBA 2827300 - Data Anonymization feature in Instance Refresh - SuccessFactors for additional details.

FAQ

Question: What if the refresh status fails or is showing a reverted status?
Answer: If the status of your refresh is showing Failed or Reverted, please contact SAP Cloud Support with the error log file. To download the log file, click the ellipses button under the Action column for the corresponding refresh request, and then click "Download Log". For more details on status of your refresh, please review SAP Help Link here. If your refresh is urgent, download the attached refresh form to proceed with a manual refresh while the RCA is been completed by Engineering on the failed or reverted status of the refresh.

Question: What if the source and target are integrated with IAS and the IPS sync is scheduled?
Answer: We recommend the customer to hold IPS sync job in the target until the refresh is completed.

Question: How much time the Refresh takes to be completed?
Answer: The basic refresh of your target instance will be completed in a couple of hours. In addition to this, depending on your company's data volume, instance stabilization activities like deleting the NoSQL data, deleting the audit logs, rebuilding of the solr indexes, and so on can take longer duration.

Question: What if the refresh completes with warnings?
Answer: If the status of your refresh shows completed with warnings, you can still log in to the updated target instance and continue with other scheduled activities and testing. There may be some actions from SAP Cloud Support or the customer side. See full list of warning messages and actions on KBA 2812823 - Refresh Status Information - Completed with warning - Full List.

Question: You receive the following error: "The application encountered an unknown error". How do I fix the error?
Answer: If you encounter an unknown error when pairing the tool, use KBA 2789795 - "Instance Refresh / Instance Sync Tool: The Application Encountered an Unknown Error" to resolve the error.

Question: Is it possible to delete the existing instance pair in Instance Refresh Tool?
Answer: Delete pair feature is available in Instance Refresh Tool from 2H 2024 release. You can clean-up invalid instance pairs using the Delete Pair feature.

Question: You receive the following error: "Unable to fetch existing requests. Please contact SAP Cloud to run Company Schema Upgrade Job and Company Data Migrate Job from Provisioning, and then refresh the metadata cache. To refresh cache, go to "Admin Center" > "OData API Metadata Refresh And Export" and then click "Refresh"." How do I fix the error?
Answer: If you encounter this error, it is due to missing Role based permission - follow steps in KBA 2819650 - Unable to fetch existing request - Instance Refresh Tool

Question: I receive the Error codes : TENANTREFRESH_MAX_SCHEMA_SIZE_EXCEEDED , Validation failed. Or "The refresh cannot be submitted because the data volume of the source instance is too large for the automated refresh process. Please contact SAP Cloud Support to trigger a refresh with the operations team." How should I proceed?

Answer: If you encounter this error code, please submit a Support ticket with LOD-SF-PLT-REF and complete the attached refresh form to proceed with the manual refresh. See KBA: 2277508 - SuccessFactors Cloud Manual Instance Refresh Process & FAQ.

Question: If you schedule a refresh a month ahead, can it be canceled up to the start of the refresh procedure?

Answer: Yes, it can be canceled before the start of refresh.

Question: Can we make certain sensitive data field scrambled?
Answer: Kindly refer the earlier Data Anonymization section for further details.

Question: Is this tool handling also the Provisioning post-refresh configurations and integrations re-establishment?
Answer: Yes, all existing integration are reverted automatically via the refresh tool. This includes SSO, LMS, ONB, RMK and WFA.

Question: When can we refresh our instance?
Answer: The refresh can be scheduled within the tool on weekdays from Monday to Thursday. (Friday-Sunday is not available due to patches and maintenance.) The refresh will be scheduled during non-working hours.

Question: Is Onboarding 1.0 module is included on the Refresh?
Answer: No. Please submit a case to the Onboarding module to request this type of refresh.

Question: Is LMS available in the Refresh tool?
Answer: Yes, please review KBA 2835061 for further details.
For any other LMS refresh, please open an case with LOD-SF-LMS and refer to KBA 2165346 - Learning Management System Refresh Process.

Question: Schedule dates will need to take into consideration local time or Data Center time?
Answer: The date shown in the tool when you submit a request will be converted and shown according to the browser's time zone. The tool will schedule the refresh between 8pm to 8am in the timezone of the Data Center based on the DBpool availability.

Question: Is the refresh scheduled time also shown in the interface besides the selected Refresh scheduled date so we can see for how late the refresh is scheduled, especially if there is a down-time of the Target instance?
Answer: Yes, the scheduled date will be shown in the Overview page in the tool.

Question: Why are some Weekday (Monday to Thursday) slots shown unavailable in the tool at times?
Answer: There are fixed number of refresh slots available per day, at data center level. Once all the slots for a day get booked, that specific date will become unavailable for further refresh scheduling.

Question: Can we cancel the refresh?
Answer: Once a refresh is in progress, it can't be canceled.

Question: Can we do e-mail masking?
Answer: The Recruiting Candidate e-mail Addresses and the Employee Profile e-mail Addresses can be masked. If you have Employee Central enabled in Source, please refer to the "Considerations Pre-Refresh" section, point #4.

Question: Was the refresh actually done there is a "Validation Failed" failed status? Was it useful? In what kind of scenario system shows this kind of status?
Answer: The refresh is not done if it is in 'Validation Failed' status. This status might pop up if the desired space is not available in the system or if Instance Refresh was disabled in the Target instance for some reason.

Question: Are Custom Themes copied from the Source to the Target instance after a refresh?
Answer: Yes.

Question: Are Custom Navigation links copied from the Source to the Target instance after a refresh?
Answer: Yes.

Question: Is it possible to use the Instance Refresh Tool for cross-Data Center instances?
Answer: The tool currently does not allow to select a different Data Center for the Target environment.

Question: Are cards (including custom cards) copied from Source to Target?
Answer: Yes. If you have custom cards in the Target which you need to revert back post-refresh, please ensure to save the tile settings pre-refresh.

Question: Is company logo copied from Source to Target?
Answer: The logo image is not copied, but the internal company logo Reference URL is copied from Source to Target. When Source and Target are in same Data Center, this can lead to the Source logo being displayed in the Target post-refresh.

Question: Will the candidates (in RCM) be able to log in to the destination Career Site and not the SF system post-refresh? Will the agency users be able to log in to the agency portal in the destination post-refresh?
Answer: The passwords are copied during the refresh and should work on the refreshed instance even if the URLs are different. This is true for both candidate profiles and agency users.

Question: Qualtrics Integration is not available in Target instance, even though I have upgraded it in Source and Target instance before refresh.
Answer: It is an expected behavior (see KBA 3230588). It is also expected that Qualtrics is automatically disabled in the target instance to prevent your system from immediately starting up Qualtrics surveys before you're ready for them to begin. See Enabling Qualtrics After an Instance Refresh.

Question: When performing an Instance Refresh, are there are some points to take into consideration and possibly some actions that may need to be carried out post-migration, in order for the instance to work correctly?
Answer: Refer to 2313764 - Instance Refresh - Employee Central Considerations & FAQ

Question: You receive the Instance Refresh Warning: Tenant copy in Blob Storage Service (BSS) has the following status: Failed. This activity is to copy talent blob in BSS from a source instance to a target instance.
Answer: Refer to 3399451 - Instance Refresh Warning: Tenant copy in Blob Storage Service (BSS) has the following status: Failed. This activity is to copy talent blob in BSS from a source instance to a target instance.

Question: Is there any impact of CSD (Common Super Domain) on Refresh? What is the Instance Refresh behavior?
Answer: There is no change in the refresh behavior. Refresh process retains the product integration URLs on the target tenant post refresh. For example, if BizX-Learning are yet to be migrated to CSD, then the integration will have legacy/old URL and this URL will continue to work post-refresh as well until you explicitly migrate this target tenant to CSD.

POST-REFRESH ISSUES

Investigation of "post-refresh" issues is possible within up to 30 days after the refresh completion. Any data or configuration issues identified in the target post this period should be addressed via standard support process by raising individual ticket to corresponding module teams.

Question: Where can I get information on this from the Guide?

Answer: Guide: Using the Instance Refresh Tool

Keywords

Instance Refresh Tool , IRT , Refresh , refresh , clone , Instance refresh, How to enable the instance refresh tool, Instance refresh form, form, Instance Refresh, instance refresh, refresh, Failed, failed refresh, Reverted, reverted refresh, re application encountered an unknown error, The Application Encountered an Unknown Error, Unable to fetch existing requests, Unable to fetch existing request, Company Schema Upgrade Job, validation failed, TENANTREFRESH_MAX_SCHEMA_SIZE_EXCEEDED , KBA , LOD-SF-PLT-IRT , Instance Refresh Tool , LOD-SF-PLT-REF , Instance Refresh , LOD-SF-EC-HRS , HRIS Sync , LOD-SF-LMS-IRT , Instance Refresh Tool , How To

Product

SAP SuccessFactors HCM Suite all versions ; SAP SuccessFactors Learning all versions

Attachments

BizX Manual Refresh Form_2205_UpdatedDC.docx

2791468 - Instance Refresh Tool for BizX & LMS | Must-Know Guide & FAQ

Symptom

Environment

Resolution

See Also

Keywords

Product

Attachments

Legal

Follow