Professional Documents
Culture Documents
1 Instance Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Learn about changes to the documentation for configuring and managing Instance Synchronization in recent
releases.
1H 2023
Change Syncing the Career Development Plan Sync Artifact for Career Development
Templates artifact from the source in Plan Templates [page 9]
stance to the target instance using the
Instance Synchronization Tool will reach
the End of Maintenance in 1H 2023 and
will be Deleted in 2H 2023.
Change Configuration sync of the MDF Object Sync Artifact for MDF Object Definitions
Definitions from the source instance to [page 27]
the target instance using the Instance
Synchronization Tool has reached the End
of Maintenance in 2H 2022 and will be
Deleted in 2H 2023.
2H 2022
Instance synchronization is a means of copying the configuration of your multiple SAP SuccessFactors instances.
This enables you to "push" new configurations from one instance to another, such as from your Test instance to
your Production instance.
SAP SuccessFactors provides several Instance Synchronization ("Instance Sync") tools to enable you to copy
configuration settings from one instance to another.
• Use the Instance Synchronization Wizard to set up and run new sync jobs.
• Use the Manage Sync Packages page to view, edit, and run your previously saved sync jobs.
• Use the Instance Synchronization Monitor Tool to monitor sync job status and view sync reports.
Instance sync uses a "push" model, meaning that configuration settings are selectively "pushed" from a designated
source instance into another designated target instances. Configurations cannot be "pulled" into the target from
the source. Instance Sync tools support artifact-level permission control and synchronization across different
datacenters.
You can set up your system to support either one-way and two-way synchronization. In a one-way sync, you choose
one instance as the source and one as the target and only the source can initiate a sync. In a two-way sync, both
instances can be a source as well as a target, allowing them to copy configurations back and forth.
For example, if you have three instances for Development, Test, and Production, your Test instance might be both-
the target of sync jobs initiated in Development and the source of sync jobs targeting Production.
To setup Instance Sync tool in your system, enable the tool from Upgrade Center. Once enabled, you will need to
pair the source and target instances. This is a one-time task for initial setup.
You can pair the source and target instances using the Instance Sync tool.
After instance sync setup in your system, you can use the Instance Sync tools to create, run, manage, and monitor
synchronization jobs.
Additional Information
Permission Model Available with both role-based permissions (RBP) and legacy
permissions
Certain consideration to know before you enable Instance Synchronization tools and set up Instance Sync job.
1. Learn about instance sync features and think about how you want to use them. Some questions to consider
are:
• Which instance will be a source instance from which you want to copy configurations?
• Which instance will be a target instance to which configurations can be copied from the source?
• Which configuration artifacts should be enabled for each source instance? You can selectively enable
instance sync for any or all of the available configuration artifacts.
• Which users should have sync permission for each type of configuration artifact? You can grant sync
permission separately, to different users or roles, for each type of configuration artifact.
2. Enable Instance Synchronization tool from Upgrade Center.
3. Get the pairing done for the source and target instances in your system.
4. Grant sync permissions to the appropriate users or roles in each source instance. Sync permissions allow
users to set up and run sync jobs for each type of configuration artifact. Again, you can grant sync permission
separately for each type of configuration artifact. For example, one user might have permission to sync Goal
Management Templates, while another person might have permission to sync MDF Picklists and MDF Object
Definitions.
An instance sync artifact represents one type of configuration that you can sync with instance sync tools.
Every sync job or sync package includes one or more sync artifacts. During the set-up of a sync job, you select
the sync artifacts you want to include in the Instance Synchronization Wizard. Each artifact contains a collection of
related configuration settings and has its own separate set-up steps and sync behavior.
• Prerequisites - Prerequisite features that must be enabled in your system to use the artifact
• Permissions - Permission required to sync the artifact in Instance Synchronization Wizard.
• Selection Options - What you can choose to include in the sync during set-up.
• Overwrite Options - What you want instance sync to do when a selection already exists in the target instance,
overwrite it or ignore it
• Dependencies - Dependencies of the artifact, which should be synced before or at the same time as that
artifact
• Copy Logic - Artifact-specific copy logic to determine exactly what is synced from source to target
• Filter by Last Modified - Filter options available during set-up. Last modified date is displayed in UTC
timezone.
• Exists At Target - Ability to see during set-up if your selections already exist in the target
1. MDF Picklist
2. Data Model
3. Foundation Objects
4. Workflow(Route Maps), Workflow Groups
5. MDF Configuration UI
6. MDF rules
7. MDF Data
8. RBP groups
9. RBP roles
10. Rating Scale, System Properties, OBjective template, Form Lable Transaltion, Families and Roles, Goal
Management Templates, Career Development Plan Templates, Compensation Lookup Table, Competencies
Form Templates
11. Homepage Tile Configurations, Homepage Tile Groups
Certain prerequisites, guidelines, considerations, and permissions apply when syncing the Career Development
Plan Templates artifact from the source to target instance.
Note
Syncing the Career Development Plan Templates artifact from the source instance to the target instance using
the Instance Synchronization Tool will reach the End of Maintenance in 1H 2023 and will be Deleted in 2H 2023.
Details about the Career Development Plan Templates Instance Sync Artifact
Prerequisites This artifact requires SAP SuccessFactors Succession and Development, with Career Develpment and
Planning enabled.
Permissions In order to sync this artifact in the Instance Synchronization Wizard, you need to have Sync Career-
Development-Plan Templates permission.
Selection Options You can select one or more Career Development Plan Templates to include in the sync.
Note
The method for selecting Goal Management and Career Development Plan Templates in the
Instance Synchronization Wizard is different from most artifacts. At the start of the wizard, select
Goal Templates, which includes both of these template types. If you have permission to sync both
of these template types, you can select one or more templates from a list. You can use the Select
Template Type menu to filter the list by type.
Overwrite Options You can specify what to do when the selected Career Development Plan Templates already exist in the
target instance:
• Overwrite - If selected, existing Career Development Plan Templates in the target instance are
replaced by ones in the source.
• Ignore - If selected, existing Career Development Plan Templates in the target instance are
retained and are NOT replaced by ones in from the source.
Dependencies To avoid errors, you should always sync dependent artifacts at the same time, or sync parent depend
encies before their children. This artifact is dependent on the following other artifacts:
Copy Logic The tool will copy all settings within the template (xml). The template ID will be sustained.
Filter by Last Modified Supported. You can filter this artifact by Last Modified date in the Instance Synchronization Wizard.
Exists At Target Supported. The Instance Synchronization Wizard indicates which of the selected Career Development
Plan Templates, if any, already exists in the target instance.
Certain prerequisites, guidelines, considerations, and dependencies apply when syncing the Compensation Lookup
Table artifact from the source to target instance.
Selection Options You can select the Compensation Lookup Table to include in the sync.
Overwrite Options You can specify what to do when the Compensation Lookup Table already exists in the target instance:
• Overwrite - If selected, the existing Compensation Lookup Table in the target instance is replaced
by the one in the source.
• Ignore - If selected, the existing Compensation Lookup Table in the target instance is retained and
is NOT replaced by the one in from the source.
Filter by Last Modified Supported. You can filter this artifact by Last Modified date in the Instance Synchronization Wizard.
Exists At Target Supported. The Instance Synchronization Wizard indicates if the Compensation Lookup Table already
exists in the target instance.
Related Information
Certain prerequisites, guidelines, considerations, and permissions apply when syncing the Competencies artifact
from the source to target instance.
Prerequisites • This artifact requires that the Competency Library Management Suite is enabled.
• Both the source and target instances must have Job Description Manager (JDM V1.0) as their
Competency version.
Permissions In order to sync this artifact in the Instance Synchronization Wizard, you must have Sync
Competencies permission.
Selection Options You can select one or more Competencies to include in the sync, based on library, locale, and compe
tency name.
Overwrite Options You can specify what to do when the selected Competencies already exist in the target instance:
• Overwrite - If selected, existing Competencies in the target instance are replaced by ones in the
source.
• Ignore - If selected, existing Competencies in the target instance are retained and are NOT
replaced by ones in from the source.
Copy Logic The tool copies all content within a competency, however, the ID is changed.
Filter by Last Modified Not supported. You can’t filter this artifact by Last Modified date in the Instance Synchronization
Wizard.
Exists At Target Supported. The Instance Synchronization Wizard indicates which of the selected Competencies, if any,
already exists in the target instance.
Other Information
Note
Existing competency definition: comparison is done by comparing the GUID + Locale + Library.
Related Information
Certain prerequisites, guidelines, considerations, and permissions apply when syncing the Data Model artifact from
the source to target instance.
Prerequisites To sync Corporate Data Model and Country Specific Corporate Data Model, Employee Central
Foundation Object must be enabled from Provisioning in your target instance.
Remember
As a customer, you don't have access to Provisioning. To complete tasks in Provisioning, contact
your implementation partner or Account Executive. For any non-implementation tasks, contact
Product Support.
Permissions In order to sync this artifact in the Instance Synchronization Wizard, you need to have Sync Data Model
permission.
Selection Options You can select one or more of the following Data Models to include in the sync:
Overwrite Options This sync will always be an overwrite. Any existing Data Models in the target instance are replaced by
ones in the source.
Dependencies To avoid errors, you should always sync dependent artifacts at the same time, or sync parent depend
encies before their children. This artifact is dependent on the following other artifacts:
• Picklists
• MDF Picklists
Filter by Last Modified Not supported. You cannot filter this artifact by Last Modified date in the Instance Synchronization
Wizard.
Exists At Target Not supported.You cannot view which of the selected Data Models, if any, already exists in the target
instance in the Instance Synchronization Wizard.
The Succession Data Model is an essential part of all SAP SuccessFactors instances and does not
require SAP SuccessFactors Succession & Development.
The Country Specific Succession Data Model is mostly used with SAP SuccessFactors Employee
Central, but can be used in anyone.
The Corporate Data Model and Country Specific Corporate Data Model are only used with SAP
SuccessFactors Employee Central.
Note
If your not using SAP SuccessFactors Employee Central and you want to sync the Country Spe
cific Succession Data Model, you may encounter errors. For the sync to be successful, you must
have one of the following settings enabled: (1) External Learning User or (2) Manager Transfer for
Employee Profile.
Related Information
Compare data models between source and target instances and downloading the data model XML file for the
source and target instances in the Instance Synchronization Wizard, prior to running your sync, so that you can
identify discrepancies that might cause an error.
Procedure
1. In the Instance Synchronization Wizard, open a sync job that includes the Data Model artifact and proceed
through the wizard to the Data Model screen.
2. Click the Compare button for the data model you want to compare between source and target.
You may only have one data model available to select. Every SAP SuccessFactors instance has at least one
data model, commonly known as the "Succession Data Model" (although it does not require use of SAP
SuccessFactors Succession and Development). If you are using SAP SuccessFactors Employee Central, you
may also have up to three other data models.
It can take up to two minutes to open the comparison. The time required to generate the data model
comparison varies based on the size of the data models and the number of differences.
You can use the downloaded data models to review legacy permissions and build equivalent role-based
permissions. You can also use the downloaded target XML as a backup in case you wish to revert data model
sync once done.
6. Close the comparison window to return to the wizard.
Next Steps
If there is any XML in the target that you wish to retain and that is not present in the source, you should update
the data model in the source before proceeding. If you continue with the sync, the data model in the target will be
overwritten with the data model in the source.
Certain prerequisites, guidelines, considerations, and permissions apply when syncing the Families and Roles
artifact from the source to target instance.
Permissions In order to sync this artifact in the Instance Synchronization Wizard, you need to have Sync Families
and Roles permission.
Selection Options You can select one or more Families and Roles to include in the sync.
• Overwrite - If selected, existing Families and Roles in the target instance are replaced by ones in
the source.
• Ignore - If selected, existing Families and Roles in the target instance are retained and are NOT
replaced by ones in from the source.
Copy Logic The tool will copy all content within a family and role.
Filter by Last Modified Not supported. You cannot filter this artifact by Last Modified date in the Instance Synchronization
Wizard.
Exists At Target Supported. The Instance Synchronization Wizard indicates which of the selected Families and Roles, if
any, already exists in the target instance.
Related Information
Certain prerequisites, guidelines, considerations, and permissions apply when syncing the Form Label Translations
artifact from the source to target instance.
Permissions In order to sync this artifact in the Instance Synchronization Wizard, you need to have Sync Form Label
Translation permission.
Selection Options There is no granular selection for this artifact. All Form Label Translations are included in the sync..
Overwrite Options You can specify what to do when the selected Form Label Translations already exist in the target
instance:
• Overwrite - If selected, existing Form Label Translations in the target instance are replaced by
ones in the source.
• Ignore - If selected, existing Form Label Translations in the target instance are retained and are
NOT replaced by ones in from the source.
Copy Logic The tool will copy all Form Label Translations.
Related Information
Certain prerequisites, guidelines, considerations, and permissions apply when syncing the Foundation Objects
artifact from the source to target instance.
Note
Syncing the Dynamic Role and Position Dynamic Role Foundation Object artifacts is not supported
during the blackout period, that is, from Preview to Production environment, or from Production
to Preview environment. The blackout period is the time during post Preview release until Produc
tion release. For successful syncing of this artifact, please wait until the Production version is
migrated to a version similar to the Preview version.
Permissions In order to sync this artifact in the Instance Synchronization Wizard, you need to have Sync Foundation
Objects permission.
Selection Options You can select one or more Foundation Objects to include in the sync.
Overwrite Options You can specify what to do when the selected Foundation Objects already exist in the target instance:
• Overwrite - If selected, existing Foundation Objects in the target instance are replaced by ones in
the source.
• Ignore - If selected, existing Foundation Objects in the target instance are retained and are NOT
replaced by ones in from the source.
• MDF Object Definition, MDF Rules, MDF Picklists, Data Model, Picklists
In addition, each of your selected Foundation Objects may or may not have its own associated
dependencies. Please refer to the dependencies shown in the Instance Synchronization Wizard.
Copy Logic The tool will copy all data within the selected Foundation Object.
Filter by Last Modified Supported. You can filter this artifact by Last Modified date in the Instance Synchronization Wizard.
Exists At Target Supported. The Instance Synchronization Wizard indicates which of the selected Foundation Objects,
if any, already exists in the target instance.
Other Information
Caution
Before synching Foundation Objects, you need to ensure that the data models of the source and
target instances are in sync. Both data models must have the same modules enabled and share
the same data element and dynamic group definitions, or the sync will fail and return the relevant
error code.
Caution
Admin users in the source and target instances should use the same locale. In other words, the
source instance user who performs the sync and the target instance user whose user name
is identified in the Instance Synchronization Wizard should both be using the same locale, or
language preference setting (such as US English). If these users have a different locale, it can
result in a corruption of Foundation Object Data.
Related Information
Certain prerequisites and permissions apply when syncing the Homepage Tile Configurations artifact from the
source to target instance.
Caution
The legacy home page is in deprecation. It's no longer available for most customers.
Prerequisites This artifact is only for the new SAP Fiori-based Home Page.
Permissions In order to sync this artifact in the Instance Synchronization Wizard, you need to have Sync Homepage
Tile Configurations permission.
Related Information
Certain prerequisites, guidelines, considerations, and permissions apply when syncing the Homepage Tile Groups
artifact from the source to target instance.
Caution
The legacy home page is in deprecation. It's no longer available for most customers.
Visit the SAP SuccessFactors Customer Community Migration to Reimagined Home Page - Innovation Alert
for all the latest updates.
Prerequisites This artifact is only for the new SAP Fiori-based Home Page.
Note
Syncing the Homepage Tile Groups artifact is not supported from Production to Preview environ
ment due to blackout period for Preview upgrade. The blackout period is the time during post
Preview release until Production release. For successful syncing of this artifact, please wait until
the Production version is migrated to a version similar to the Preview version.
Permissions In order to sync this artifact in the Instance Synchronization Wizard, you need to have Sync RBP
Permission Groups permission.
Certain prerequisites, guidelines, considerations, and permissions apply when syncing the MDF Configuration UI
artifact from the source to target instance.
Prerequisites This artifact requires that the Metadata Framework (also known as "MDF" or "Generic Objects") is
enabled.
Permissions In order to sync this artifact in the Instance Synchronization Wizard, you need to have Sync MDF
Configuration UI permission.
Selection Options You can select one or more MDF Configurable UI Settings to include in the sync.
Overwrite Options You can specify what to do when the selected MDF Configurable UI Settings already exist in the target
instance:
• Overwrite - If selected, existing MDF Configurable UI Settings in the target instance are replaced
by ones in the source.
• Ignore - If selected, existing MDF Configurable UI Settings in the target instance are retained and
are NOT replaced by ones in from the source.
Copy Logic The tool will copy all content within the selected MDF Configurable UI's.
Filter by Last Modified Supported. You can filter this artifact by Last Modified date in the Instance Synchronization Wizard.
Exists At Target Supported. The Instance Synchronization Wizard indicates which of the selected MDF Configurable UI
Settings, if any, already exists in the target instance.
Related Information
Certain prerequisites, guidelines, considerations, and permissions apply when syncing the MDF Data artifact from
the source to target instance.
Prerequisites This artifact requires that the Metadata Framework (also known as "MDF" or "Generic Objects") is
enabled.
Permissions In order to sync this artifact in the Instance Synchronization Wizard, you need to have Sync MDF Data
permission.
Note
Due to ongoing technical changes, the sync of data in certain MDF objects is temporarily unavaila
ble in instance sync tools.
Note
Some MDF objects are hidden in instance sync tools to help prevent errors. Non-editable objects
and objects that do not conform to certain technical standards are hidden in the UI. The limita
tions of these MDF objects result in sync errors so we hide them to prevent you from including
them in your sync job.
Note
You can identify the MDF objects to sync based on the business key in addition to the exter
nal code. The business key appears in the Key1 column for the corresponding MDF object in
Instance Synchronization Wizard only if the business key is defined to the MDF object and has the
externalCode field as Auto Number.
Dependencies To avoid errors, you should always sync dependent artifacts at the same time, or sync parent depend
encies before their children. This artifact is dependent on the following other artifacts:
In addition, each of your MDF Data object selections may or may not have its own associated depend
encies. Please refer to the dependencies shown in the Instance Synchronization Wizard.
Filter by Last Modified Supported. You can filter this artifact by Last Modified date in the Instance Synchronization Wizard.
Exists At Target Supported. The Instance Synchronization Wizard indicates which of the selected MDF Data, if any,
already exists in the target instance.
Related Information
Certain prerequisites, guidelines, considerations, and permissions apply when syncing the MDF Object Definitions
artifact from the source to target instance.
Note
Configuration sync of MDF Object Definitions from the source instance to the target instance will be deleted as
of 2H 2023.
Prerequisites This artifact requires that the Metadata Framework (also known as "MDF" or "Generic Objects") is
enabled.
Permissions In order to sync this artifact in the Instance Synchronization Wizard, you need to have Sync MDF
Object Definitions permission.
Note
Some MDF objects are hidden in instance sync tools to help prevent errors. Non-editable objects
and objects that do not conform to certain technical standards are hidden in the UI. The limita
tions of these MDF objects result in sync errors so we hide them to prevent you from including
them in your sync job.
Note
You can identify the MDF objects to sync based on the business key in addition to the exter
nal code. The business key appears in the Key1 column for the corresponding MDF object in
Instance Synchronization Wizard only if the business key is defined to the MDF object and has the
externalCode field as Auto Number.
Overwrite Options You can specify what to do when the selected MDF Object Definitions already exist in the target
instance:
• Overwrite - If selected, existing MDF Object Definitions in the target instance are replaced by
ones in the source.
• Ignore - If selected, existing MDF Object Definitions in the target instance are retained and are
NOT replaced by ones in from the source.
Dependencies To avoid errors, you should always sync dependent artifacts at the same time, or sync parent depend
encies before their children.
Copy Logic The tool will copy all content within the selected MDF Object Definitions.
Filter by Last Modified Supported. You can filter this artifact by Last Modified date in the Instance Synchronization Wizard.
Exists At Target Supported. The Instance Synchronization Wizard indicates which of the selected MDF Object Defini-
tions, if any, already exists in the target instance.
Related Information
Compare MDF Object Definitions between source and target instances in the Instance Synchronization Wizard, prior
to running your sync, so that you can identify discrepancies that might cause an error.
Procedure
1. In the Instance Synchronization Wizard, open a sync job that includes the configuration artifact MDF Object
Definition and proceed through the wizard to the MDF Object Definition screen.
2. Select each MDF object definition you want to compare by clicking the icon in the Compare column.
Selected object definitions are indicated above the search results, below the Compare button, as shown here.
In this example, the BenefitCompanyCar object definition has been selected to compare.
3. Click the Compare button to open the comparison tool in a new window.
4. In the comparison window, you can:
a. Use expand and collapse icons to view a comparison of each selected object definition.
b. Use the "equal" and "not equal" signs to identify metadata values that are different (indicated with "not
equal" sign) between source and target.
Note
Due to a known UI issue, the comparison tool currently does not easily identify the exact metadata value
that differs. For each row where a difference is indicated (with the "not equal" sign), you need to scroll
through the columns and visually scan for the differing value. Longer values are truncated, so you may need
to compare them one-by-one in the Detailed View.
5. When you have verified that an object definition is the same in the source and the target instance, select the
checkbox next to the name of the object, in the first column of the comparison tool, so that you can add it to
your sync.
6. To add the MDF object definitions you've selected in the comparison tool to your sync, click Add to Sync.
This action is only enabled if at least one object definition is selected in the comparison tool.
This closes the comparison tool and returns you to the Instance Synchronization Wizard.
Results
The selected MDF object definitions, which you have confirmed as identical in the comparison tool, are now added
to your sync job.
Next Steps
Certain prerequisites, guidelines, considerations, and permissions apply when syncing the MDF Rules artifact from
the source to target instance.
Prerequisites This artifact requires that the Metadata Framework (also known as "MDF" or "Generic Objects") is
enabled.
Permissions In order to sync this artifact in the Instance Synchronization Wizard, you need to have Sync MDF Rule
permission.
Selection Options You can select one or more MDF Rules to include in the sync.
Note
You can identify the MDF objects to sync based on the business key in addition to the exter
nal code. The business key appears in the Key1 column for the corresponding MDF object in
Instance Synchronization Wizard only if the business key is defined to the MDF object and has the
externalCode field as Auto Number.
• Overwrite - If selected, existing MDF Rules in the target instance are replaced by ones in the
source.
• Ignore - If selected, existing MDF Rules in the target instance are retained and are NOT replaced
by ones in from the source.
Dependencies To avoid errors, you should always sync dependent artifacts at the same time, or sync parent depend
encies before their children.
Copy Logic The tool will copy all content within the selected MDF Rules.
Filter by Last Modified Supported. You can filter this artifact by Last Modified date in the Instance Synchronization Wizard.
Exists At Target Supported. The Instance Synchronization Wizard indicates which of the selected MDF Rules, if any,
already exists in the target instance.
Related Information
Following are two example use cases showing how to sync MDF Objects and Rules across instances with instance
sync.
User Case 1
Rule 1
Rule 2
System behavior in target: Object Definition A associated with Rule 1 and Rule 2 get synced.
System behavior in target: Rule 1 gets synced; Object Definition A is also synced because the underlying Rule 1 is
synced.
Step 3: Add new Rule 3 and associate it to Object Definition A in source instance, then perform instance sync by
selecting
Rule 3 (Only)
System behavior in target: Rule 3 gets synced; Object Definition A is also synced and associated with Rule 3
(Because its underlying Rule is synced.)
User Case 2
Object Definition A
Rule 2
System behavior in target: Object Definition A associated with Rule 1 and Rule 2 get synced.
Object Definition A
System behavior in target: Object Definition A sync will fail (Since can't sync all the rules association. The
information will be indicated in Instance Sync Monitor report.)
Rule 2
System behavior in target: Rule 2 gets synced; Object Definition A is also synced and associated with Rule 2
(Because its underlying Rule is synced.)
Note
Important
Before synching MDF artifacts, you need to ensure that the data models of the source and target instances
are in sync. Both data models must have the same modules enabled and share the same data element and
dynamic group definitions, or the sync will fail and return the relevant error code.
Related Information
Certain prerequisites, guidelines, considerations, and permissions apply when syncing the Role-Based Permission
Groups artifact from the source to target instance.
Permissions In order to sync this artifact in the Instance Synchronization Wizard, you need to have Sync RBP
Permission Groups permission.
Selection Options You can select one or more Role-Based Permission Groups to include in the sync.
Overwrite Options You can specify what to do when the selected Role-Based Permission Groups already exist in the
target instance:
• Overwrite - If selected, existing Role-Based Permission Groups in the target instance are replaced
by ones in the source.
• Ignore - If selected, existing Role-Based Permission Groups in the target instance are retained
and are NOT replaced by ones in from the source.
Dependencies To avoid errors, you should always sync dependent artifacts at the same time, or sync parent depend
encies before their children. This artifact is dependent on the following other artifacts:
Copy Logic The tool will copy all of the groups selected.
Filter by Last Modified Supported. You can filter this artifact by Last Modified date in the Instance Synchronization Wizard.
Exists At Target Supported. The Instance Synchronization Wizard indicates which of the selected Role-Based Permis
sion Groups, if any, already exists in the target instance.
Other Information
Note
Instance sync does not support static permission groups at this time. Static permission groups
not listed among the available options in the Instance Synchronization Wizard.
Related Information
Certain prerequisites, guidelines, considerations, and permissions apply when syncing the Role-Based Permission
Roles artifact from the source to target instance.
Note
Syncing the RBP Roles artifact is not supported during the blackout period, that is, from Preview
to Production environment, or from Production to Preview environment. The blackout period
is the time during post Preview release until Production release. For successful syncing of this
artifact, please wait until the Production version is migrated to a version similar to the Preview
version.
Permissions In order to sync this artifact in the Instance Synchronization Wizard, you need to have Sync RBP
Permission Roles permission.
Selection Options You can select one or more Role-Based Permission Roles to include in the sync.
Overwrite Options You can specify what to do when the selected Role-Based Permission Roles already exist in the target
instance:
• Overwrite - If selected, existing Role-Based Permission Roles in the target instance are replaced
by ones in the source.
• Ignore - If selected, existing Role-Based Permission Roles in the target instance are retained and
are NOT replaced by ones in from the source.
Dependencies To avoid errors, you should always sync dependent artifacts at the same time, or sync parent depend
encies before their children. This artifact is dependent on the following other artifacts:
• RBP Permission Groups, MDF Object Definition, MDF Rules, Data Model, Picklists
Copy Logic The tool will copy all of the roles selected.
Filter by Last Modified Supported. You can filter this artifact by Last Modified date in the Instance Synchronization Wizard.
Exists At Target Supported. The Instance Synchronization Wizard indicates which of the selected Role-Based Permis
sion Roles, if any, already exists in the target instance.
Related Information
Certain prerequisites, guidelines, considerations, and permissions apply when syncing the System Properties
artifact from the source to target instance.
Permissions In order to sync this artifact in the Instance Synchronization Wizard, you need to have Sync System
Properties permission.
• Company Process
Note
You will not be able to sync Process and Forms from this system property.
Note
You will not be able to sync Manage Security Questions and Settings from this system prop
erty.
Note
You will not be able to sync Form Templates from this system property.
Overwrite Options This sync will always be an overwrite. Any existing System Properties in the target instance are
replaced by ones in the source.
Copy Logic The tool will copy all content within the selected system property settings.
Certain prerequisites, guidelines, considerations, and permissions apply when syncing the Workflow Groups
artifact from the source to target instance.
Note
Syncing the Workflow Groups artifact is not supported from Production to Preview environment
due to blackout period for Preview upgrade. The blackout period is the time during post Preview
release until Production release. For successful syncing of this artifact, please wait until the
Production version is migrated to a version similar to the Preview version.
Permissions In order to sync this artifact in the Instance Synchronization Wizard, you need to have Sync RBP
Permission Groups permission.
Selection Options You can select one or more Workflow Groups to include in the sync.
Overwrite Options You can indicate if you want to overwrite Workflow Groups that already exist in the target instance.
• Yes - If selected, existing Workflow Groups in the target instance are replaced by ones in the
source.
• No - If selected, existing Workflow Groups in the target instance are retained and are NOT
replaced by ones in the source.
Dependencies To avoid errors, you should always sync dependent artifacts at the same time, or sync parent depend
encies before their children. This artifact is dependent on the following other artifacts:
• MDF Picklist
• Picklists
Copy Logic The tool will copy all content within dynamic workflow groups.
Filter by Last Modified Supported. You can filter this artifact by Last Modified date in the Instance Synchronization Wizard.
Exists At Target Supported. The Instance Synchronization Wizard indicates which of the selected Workflow Groups, if
any, already exists in the target instance.
You can now enable Instance Synchronization from the Upgrade Center.
Context
The different synchronization tools allow you to sync artifacts between instances as well as manage your instances.
It is important that you enable Instance Synchronization for all the source and the target instances that you want to
manage.
Caution
Once Instance Sync is enabled, you will not be able to disable it.
Procedure
A dialog box appears providing more information about Instance Synchronization. Review the information
before proceeding.
4. Click Upgrade Now to enable Instance Synchronization Wizard.
Results
Once the upgrade is complete, you will see Instance Synchronization Tool Expert Self Service under Completed
Upgrades.
Instance Sync administrator permissions are required to access the Instance Sync tools in the source instance and
to sync artifacts to the target instance. These permissions are set up in Admin Center, using the system permission
tools (either role-based or legacy permissions).
After instance sync has been successfully enabled, three Admin Tools become available in Admin Center of the
source instance:
However, in order to access these tools, you must be granted permission to sync at least one type of artifact
between instances. Any user with permission to sync at least one artifact can access and use all of the Instance
Sync Admin Tools in the source instance.
Note
Instance Sync permissions are granted on a by-artifact basis. That is, you can grant permission separately
for each type of instance sync artifact enabled in your system. For example, one user might be allowed to
sync Performance and Goals form templates, while another is allowed to sync permission roles and permission
groups. Administrators can only sync artifacts for which they have been granted the appropriate permission.
To access the Instance Sync tools and sync artifacts from the source instance to the target instance, you must have
certain permissions.
Prerequisites
Procedure
1. Go to Admin Center Manage Permission Roles and edit the appropriate administrative role.
To pair the target instance with the source instance, you require Admin access to MDF OData API
permission. Go to Administrative Permissions Metadata Framework and select Administrative
Permissions Manage Instance Synchronization .
Results
Note
You can sync only those artifacts to which sync permission is granted.
If you are using legacy permissions, you can grant instance sync permissions by completing the following steps.
Prerequisites
Only users with the ability to manage system permission roles can grant instance sync access. If you are able to
manage system permissions in the source instance, you can grant access to the instance sync tools.
Procedure
To pair the source and target instances, you need to complete the following steps.
Procedure
This is the bare minimum implementation, enabling at least one customer administrator to access and use
Instance Sync tools. You may also continue working with your customer to set up all of the necessary sync
permissions for every enabled configuration artifact and/or help verify the implementation through testing.
Related Information
You need to define each target-source relationship separately. That is, you need to set up instance sync company
permissions separately for each target instance, for a specified source.
For example, if the customer has two instances for Test and Production and you want to enable a two-way sync
between them , you need to go through the set up process two separate times, in order to:
Or, for example, if the customer has three instances for Development, Test, and Production and you want to set up
a one-way sync between them, you need to go through the set up process two separate times, in order to:
After you have completed setting up instance sync company permissions, you can proceed to setting up
administrator permissions in each source instance.
Parent topic: Consideration for Pairing the Source and Target Instances [page 43]
Before admins can sync artifacts between source and target instances, instances must be paired. Pairing of the
instances is a one-time task.
The first step to pair the target instance with the source instance is to initiate an authentication token generation
from the source instance.
Prerequisites
• Admin access to MDF OData API permission must be enabled in the source instance.
• Instance Synchronization must be enabled in both the source and target instances.
Context
To copy any artifact using the Instance Synchronization wizard, you must select the target instance details like,
target environment, target data center from the source instance. The target instance details are available for
selection in Instance Synchronization Wizard of the source only when target instance is paired to the source
instance.
The Instance Management page appears with the Configuration Copy (Instance Synchronization) option
selected.
4. Click Next.
Instance Pair Wizard opens with the Select Target Details step active on it.
Note
You can also open the Instance Pair Wizard by navigating to Admin Center Tools Manage Sync
Packages and clicking Add New Pair.
Generate Authentication Token step is active on the Instance Pair Wizard that displays a message on the
procedure to get the authentication token when the token generation is successful.
Results
Caution
The generated token is valid only for one hour from the time it has been generated. If the token expires, you
must regenerate the authentication token again.
Task overview: Pairing the Source and Target Instances [page 45]
Next task: Copying the Generated Authentication Token from the Target Instance [page 47]
Before complete the pairing process, you must copy the authentication token that you initiated for generation from
the source instance, back to the source instance from the target instance.
Procedure
The Instance Management page appears with the Configuration Copy (Instance Synchronization) option
selected.
4. Click Next.
You can also fine the expiry time of the authentication token next the source instance company ID.
6. Click Copy Token.
Results
Task overview: Pairing the Source and Target Instances [page 45]
Previous task: Generating an Authentication Token from the Source Instance [page 45]
Next task: Adding the Authentication Token in the Source Instance [page 48]
Entering the copied authentication token from the target instance to the source instance, completes the pairing of
target instance with the source instance.
Procedure
The Instance Management page appears with the Configuration Copy (Instance Synchronization) option
selected.
4. Click Next.
Instance Pair Wizard opens with the Select Target Details step active on it.
7. Click the radio button that has the name of your target instance company Id, from which authentication token
was copied.
Results
Pairing the target instance with the source instance is successful. You can now find the target instance details in
Instance Synchronization Wizard welcome page to sync the artifacts from your source instance.
Task overview: Pairing the Source and Target Instances [page 45]
Previous task: Copying the Generated Authentication Token from the Target Instance [page 47]
You can delete the pairing between source and target instances to remove unwanted target instances that are
paired with your source instance.
Prerequisites
Procedure
Note
You can also delete the pairing between source and target instances from the Manage Sync Packages page.
The Instance Management page appears with the Configuration Copy (Instance Synchronization) option
selected.
4. Click Next.
You can't find the target instance in the Instance Synchronization Wizard of the source instance for syncing
artifacts.
If you have been granted at least one Manage Instance Synchronization permission for at least one configuration
artifact, you can access the Instance Synchronization Wizard in the source instance. To access the wizard, see
Setting Up a Configuration Sync Job in the Related Information section.
Note
The text of the link you see will vary, depending on which stage of the set-up process you are in. To prevent you
or other administrators from running conflicting sync jobs, only one sync set-up can be in progress at a time.
If there is an incomplete set-up in progress, you are given a choice on the Synchronize Instance Configurations
page to either resume the incomplete set-up or restart the Instance Synchronization Wizard from the beginning.
Note
Because instance sync uses a "push" model, all configuration sync jobs are set up and run within the source
instance. For this reason, the Instance Synchronization Wizard is only accessible in the source instance.
Related Information
Sync jobs take time to complete. The Instance Synchronization Wizard does not actually complete the configuration
sync itself, but enables you to set up and initiate a sync job request. The sync job then runs in the background until
it is either completed successfully or results in an error that requires attention.
A sync job can be a true sync, in which configuration settings are transferred from one instance to another, or it can
be a test sync, which simulates the transfer and checks for potential errors. A test sync enables you to troubleshoot
potential errors before any configuration settings are actually transferred from one instance to another. If your
test is successful, you can then run a true sync to copy the selected configuration settings from the source to the
target. As a best practice, you should always run a test sync before running the true sync.
Set up configuration sync job to push the configurations from the source to target instance.
Prerequisites
• To set up a configuration sync job, the source and target instances must be paired.
• The permission to sync the required artifact must be enabled.
• The sync permission for the artifact must be enabled.
Context
An instance sync job can be a test sync or a true sync. A test sync is a simulation that shows you what would
happen when the sync would actually run, but no configurations are transferred to the target instance. A true sync
actually transfers the selected configuration artifacts and settings from the source to the target instance.
You can use the Instance Synchronization Wizard to set up and initiate either a test sync or a true sync. The setup is
the same for either type of sync. At the end of the wizard, you can choose whether you want it to be a test or true
sync. As a best practice, you should always run a test sync first, to check for potential errors.
Caution
If the sync job has Data Model as an artifact, the Data Model cannot be reverted once it has been synced to
the target instance. Download the target Data Model from the comparing data model page to have a backup of
the artifact and prevent data loss or corruption in the target instance. To download the target Data Model, refer
Comparing Data Models Between Source and Target in related links.
Procedure
The Instance Management page appears with the Configuration Copy (Instance Synchronization) option
selected.
Note
If you do not find any of your target information like Target Datacenter, Target Environment, or Target
Company ID for selection you must pair your target instance with the logged in source instance. Once you
have paired, you can create a sync job. For information on instance pairing, refer the link in the related
information section.
Remember
Tip
If you have multiple target instances to sync with the source, you can create a reusable "instance sync
package" to save time. The instance sync package allows you to run the same sync job for different
instances without specifying configuration artifacts again.
Note
Select Sychronization Type is only available when your instance is enabled with data artifacts. This option
helps you to select either data or configuration artifacts separately without creating a dependency with
each other during artifact sync process.
To enable the data artifacts, create a support ticket with the source and target instance information for
Company ID, Data Center, Environment, and a written approval to enable the artifacts in the support ticket.
10. Select the configuration artifacts that you wish to sync, then click Start to proceed with the wizard.
Note
You can select any number of artifacts. If you select an artifact with dependencies, the dependent artifacts
are indicated. As a best practice, dependent artifacts should be synced together. If you do not have
permission to sync the dependency of a selected artifact, the dependency is indicated in red.
For example, if you select the Data Model artifact, it is indicated that the data model artifact depends on the
Picklists artifact. Therefore, as a best practice, you should sync both data models and picklists together. If
you have permission to sync data models but not picklists, then the dependency on picklists is highlighted
in red.
Note
If there are any missing features or permissions in the target instance based on the selected artifacts, the
Validation of the Sync Configuration dialog box appears when you click Next. Please enable the features and
permissions for the target instance listed in the Validation of the Sync Configuration dialog box for the sync
job to be successful.
13. Enter the admin user name of the target instance for your sync job in User Name (target instance).
Note
The user name is only requested the first time you attempt to sync an artifact using the wizard. This name
is provided only once for each artifact.
For example, for the RBP Permission Groups artifact, you can select which groups you want to sync. Or, for the
System Properties artifact, you can choose to sync only the password and login policy settings. You can select
any number of configuration settings.
Note
• For some artifacts, you can sort and filter the available by Last Modified date. This filter helps you
identify settings that have been changed since your last sync.
• Instance sync tool restricts the retrieval of MDF object records to 50,000. Please refine search filters to
get to specific records.
Note
• Test Sync
• Run Sync Now runs a true instance sync. The selected artifacts and settings are copied to the target
instance. The true sync job request is submitted and sent to the monitoring tool. runs a simulation and
Results
If no errors are detected that block the sync, after completing the wizard you are navigated to the Instance
Synchronization Monitor Tool. In the monitoring tool, you can check the status of your sync job request, to confirm
that it was successful or to identify potential errors.
Initially, the status shows as Ready in the monitoring tool, pending completion of the request. Most sync jobs,
including test syncs, take at least a few minutes to complete. The status of these sync jobs is not updated in the
Instance Synchronization Monitor Tool unless the browser is refreshed. Please navigate away from the Instance
Synchronization Monitoring Tool page and check your results later.
If you ran a test sync, no settings are actually transferred. When the test sync job is complete, the status shows as
Test Run Completed and you can view test results.
If you ran a true sync, the status shows as Completed when then sync job is complete. If the sync is successful, the
selected artifacts and settings are now transferred to the target instance.
Related Information
Set up data sync job in provisioning, as creating data sync job in Instance Synchronization Wizard is stuck at Ready
status. Contact SAP SuccessFactors or your SAP partner with the Sync ID to complete this procedure.
Prerequisites
To set up data sync job, you need the Sync ID number and the access to Provisioning.
As a customer, you don't have access to Provisioning. To complete tasks in Provisioning, contact your
implementation partner or Account Executive. For any non-implementation tasks, contact Product Support.
Context
To sync data artifacts from the source instance to target instance, the sync job must be set in the provisioning.
Procedure
9. In the Action column, click Select Run It Now , for the corresponding job created.
10. Click Monitor Jobs, to navigate and view the status of the created job.
Results
Instance Sync tools, such as the Instance Synchronization Wizard and Manage Sync Packages tool, will validate
permission and feature settings in the source and target instances before performing a sync. If there are
discrepancies between the instances that need to be resolved, you are alerted before the sync is run.
For each artifact, Instance Sync tools perform three kinds of permission checks:
• Source User Permissions (granted to the logged-in user in the source instance)
• Target User Permissions (granted to the specified admin user in the target instance)
For those artifacts that require certain feature settings, Instance Sync tools check whether these settings are
enabled in Provisioning for both the source and target instances.
For example, imagine that you are setting up a sync containing Data Models and PM Templates. When you try to
run a test sync, you are presented with the following Sync Configuration Validation dialog:
• that PM Templates can not be synced between this source instance and its target;
All of these issues need to be resolved so that the source and target are aligned before you can proceed with the
sync. Before, in these scenarios, the sync would run and fail. Now, the Instance Sync tools warn you in advance and
do not permit you to run the sync until the required permission and feature settings are in place, in both the source
and target instance.
You can use the Instance Synchronization Monitor Tool to check the status of submitted sync jobs and to view
details about the job. Job details enable you to track changes to your system and to troubleshoot errors you
encounter.
If you have been granted at least one Manage Instance Synchronization permission for at least one configuration
artifact, you can access the Instance Synchronization Monitor Tool in the source instance. To access the monitoring
tool, go to Admin Center Instance Synchronization Monitor Tool .
Note
Because instance sync uses a "push" model, all configuration sync jobs are set up and run within the source
instance. For this reason, the Instance Synchronization Monitor Tool is only accessible in the source instance.
You can use a variety of search filters to find and view the status of your submitted sync jobs. You can view the
status of both test syncs and true syncs. To find a specific sync job, complete the following steps.
Procedure
Search results are displayed in the Instance Synchronization Monitor Tool. You can view the current status of each
listed job, along with other basic information, such as the submission date and the user who submitted the job. You
can also link to more detailed results. An example of search results is shown below.
Related Information
Basic Information About Sync Jobs in the Instance Sync Monitor [page 62]
To view detailed results of a specific sync job in the Instance Synchronization Monitor Tool, complete the following
steps.
Procedure
1. Find the sync in search results of the Instance Synchronization Monitor Tool.
2. In the Actions column of search results, click the Details link.
Results
The Sync Details dialog window opens, telling you how many settings were successfully transferred to the target
instance (Add and Update Count) and how many settings failed to sync (Failed Count).
To download a report in CSV format with details about a specific sync job, complete the following steps.
Prerequisites
Procedure
1. Open the Sync Details dialog window in the Instance Synchronization Monitor Tool.
2. Click the Download Report button.
3. A zip file opens, containing the report. You can now save the file to your local machine or network.
Results
To help you understand response details, a list of possible response codes is visible in the Instance Synchronization
Monitor Tool.
Related Information
You can access a complete list of all the response codes used in Sync Reports. You can view the list
Procedure
1. Go to the Instance Synchronization Monitor Tool and click Instance Synchronization Response Codes.
2. View response codes in the dialog window.
Note
Response codes are listed in two formats, by the newer "message key" format and the legacy format.
Message keys are translatable UI text strings and allow you to view response codes in the same language
that you use the rest of the application. Legacy codes are still listed, for your reference.
3. To download the list in CSV format for future reference, click Download Response Codes. The downloaded file
also contains both response code formats.
The following information explains how to understand and use the information you find in the Instance
Synchronization Monitor Tool.
Understand each data points shown in the search results of the Instance Synchronization Monitor Tool.
• Queued
• In Progress
• Completed (true sync)
• Test Run Complete (test sync)
Submission Date Date on which the sync request was submitted by the Instance
Synchronization Wizard
Actions You can use the Details link to open detailed results of the sync
job in a dialog window.
• Test Sync
• Actual Sync
After viewing details of a test sync, you correct certain errors in your sync job to double check that test results by
rerunning it again. This test sync helps you to run the test again without setting up a new sync job from scratch.
Prerequisites
Submit a test sync while setting up a configuration sync job. For details on Submitting test sync, see Setting Up a
Configuration Sync Job in the Related Information link.
Procedure
The Sync Details dialog opens with the information on the artifacts that are synced.
5. Click Test Sync.
Results
A test job is created successfully and you can check the status and download the sync report in Instance
Synchronization Monitor Tool page.
After you identify and correct the errors by viewing details of a test sync, you can run a true sync of the same sync
job without creating it from scratch.
Prerequisites
Submit a test sync while setting up a configuration sync job. For details on Submitting test sync, see Setting Up a
Configuration Sync Job in the Related Information link.
Procedure
The Sync Details dialog opens with the information on the artifacts that are synced.
5. Click Run Sync Now.
Results
A sync job is created successfully and you can check the status in Instance Synchronization Monitor Tool page.
Related Information
Instance sync packages are sync jobs that you have set up and saved for easier set up and reuse in the future..
If you have more than two instances, you may often need to perform the same configuration sync multiple times.
You can save a sync job that you have set up in the Configuration Sync Wizard as a reusable "sync package." Sync
packages enable you to replicate identical syncs from your Staging instance to your Test instance, and then from
Test to Production.
For example, imagine that you have three SuccessFactors instances for Staging, Test, and Production. You might
create a new MDF object in your Staging instance that you want to transfer to Test. To do this, you migh need
to sync the configuration settings for MDF Object Definition A, Rule B, and Picklist C into your Test instance for
validation. When the new object has been tested and validated, you would then need to sync the same settings into
your Production instance. To do this, you would create an instance sync package containing all of these settings
(MDF Object Definition A, Rule B, and Picklist C) and use the same package to sync these settings between any of
your instances.
To create an instance sync package in the source instance, complete the following steps.
Procedure
1. Use the Instance Synchronization Wizard to set up your sync job in the source instance.
2. On the summary page, at the end of the wizard, you can use the Save sync bundle as package option to create a
sync package. For convenience, this option is selected by default, but you can de-select it if you do not want to
save the sync as a package.
Results
The saved package is now accessible on the Manage Sync Packages page.
You can sync an instance package that has already been created with the required artifacts to sync in your target
instance. You can re-use this package whenever you want a set of pre-defined artifacts to be synced in you target
instace .
Procedure
Note
Due to a known theming issue, in some cases the checkbox to select a package may not be visible in the
first column of the Available Packages list. However, you can select the package by clicking in the first
column.
3. In the Available target data centers dropdown list, select the target instance data center.
4. In the Available target environments dropdown list, select the target instance environment.
5. In the Available target instances dropdown list, select the target instance that you want to sync.
6. In the User Name (target instance) field, enter the administrative user name of the target instance.
7. Select the option Sync Package Contents.
8. Click Sync to submit the job.
Note
If you want to run a test sync, click Test Sync. To clear the settings done above, click Clear.
Results
Settings in the package are synced to the selected target without the need for you to go through the Instance
Synchronization Wizard again from scratch.
You can copy a instance sync package saved in source instance to another target instance.
Procedure
1. Open the Manage Sync Packages page by clicking the link on the first page of the Instance Synchronization
Wizard, or by going to Admin Center Company Settings Manage Sync Packages .
2. Find the package you want to use in the Available Packages list and select it.
Note
Due to a known theming issue, in some cases the checkbox to select a package may not be visible in the
first column of the Available Packages list. However, you can select the package by clicking in the first
column.
3. In the Available target data centers dropdown list, select the target instance data center.
4. In the Available target environments dropdown list, select the target instance environment.
5. In the Available target instances dropdown list, select the target instance that you want to sync.
6. In the User Name (Target Instance) field, enter the administrative user name of the target instance.
7. Select the option Copy Package.
8. Click Sync to submit the job.
Results
The selected package is now available on the Manage Sync Packages page of the selected target.
To edit or delete an existing instance sync package, complete the following steps.
Procedure
Due to a known theming issue, in some cases the checkbox to select a package may not be visible in the
first column of the Available Packages list. However, you can select the package by clicking in the first
column.
3. Select the Edit icon (pencil) to edit the package using the Instance Synchronization Wizard. Select the Delete
icon (trash can) to delete the package.
To manage your instances correctly, you must identify the right tool for migrating your configurations and data.
There are certain points that help you to identify the difference between the Instance Synchronization and Instance
Refresh tools.
Use Instance Refresh when you want to copy all the configura- Use Instance Synchronization when you sync/copy the se
tions and data of the source instance in to your target instance lected configuration from the source instance to the target
without impacting the integrations in your target. instance without changing its data.
When you want to have a periodic copy of the configuration When you want to adopt incremental implementation of con
and data into your test instance figuration or feature.
When you want to refresh configuration and data from produc When you want to sync the required configurations from pre
tion (Productive/Live) instance to Preview(Test) instance. view to any other instance:
Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:
• Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your agreements
with SAP) to this:
• The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.
• SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.
• Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering an SAP-hosted Web site. By using such links,
you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this information.
Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax and
phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of example
code unless damages have been caused by SAP's gross negligence or willful misconduct.
Bias-Free Language
SAP supports a culture of diversity and inclusion. Whenever possible, we use unbiased language in our documentation to refer to people of all cultures, ethnicities, genders,
and abilities.
SAP and other SAP products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP
SE (or an SAP affiliate company) in Germany and other countries. All
other product and service names mentioned are the trademarks of their
respective companies.