Replicating Data From EC To ERP HCM Config Guide 2H23
Replicating Data From EC To ERP HCM Config Guide 2H23
2 Change History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3 Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
4 Activation of Content. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
5 Configuration Steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
5.1 Configuration Steps in ERP HCM System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Common Steps for Replication and Migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8
Replication-Specific Delta Configuration Steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Other Recommendations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
5.2 Manual Configuration Steps in SAP ERP HCM System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Enable Use of New Infotype Framework. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Country Specific Gender. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
5.3 Adaptations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Updating Metadata. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Updating Picklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Updating Value Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
Updating Field Mappings for Organizational Data/Employee Data. . . . . . . . . . . . . . . . . . . . . . . 29
Copying Best Practices Templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29
Cost Center Derivation Logic When Cost Centers Being Replicated are not 14 Characters Long
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
This guide is primarily intended for the core hybrid deployment option. The core hybrid deployment option
means that Employee Central is used as the system of record holding all organizational data, but existing
processes such as Payroll, Time Management, or custom HR processes still run in an SAP ERP HCM on-
premise system landscape.
Learn about changes to the documentation for Replicating Data to ERP HCM in recent releases.
2H 2022
1H 2022
2H 2021
Before setting up the replication, ensure that the following system landscape is in place:
The prerequisites are described in the Getting Started Guide. Ensure that the Getting Started Guide and
Technical Integration Settings configurations are in place.
The Best Practices content is shipped as Business Configuration Sets as part of the PA_SE_IN component,
however they are not active by default. In order to activate and see the configuration content, perform the
following steps:
Procedure
As a result of the execution of the program, the SAP Best Practices content for migration/replication is
automatically activated. The configuration is inserted into appropriate IMG activities which are described in
detail in the subsequent sections of this guide. Together with some manual steps (Configuration Steps in ERP
HCM System [page 7]) and considering some assumptions (Manual Configuration Steps in SAP ERP HCM
System [page 24]), you may be ready to run the EC-ERP migration.
Note
If you need to modify/adapt the SAP Best Practices content, for example, for custom fields in Employee
Central instance, refer to section: Adaptations [page 27].
The configuration steps for migration/integration with SuccessFactors Employee Central can be accessed via
the SAP Implementation Guide.
Procedure
The configuration steps are listed under SAP Reference IMG Personnel Management Integration with
SuccessFactors Employee Central Business Integration Builder .
Most of these settings have been pre-delivered in a Business Configuration Set and the activation of the
Business Configuration set will populate the IMG activities with the appropriate entries needed to get started
with the migration process. Review the IMG activities and make any adjustments as needed based on your
specific needs.
If you have already implemented the Migrating Data from ERP HCM to Employee Central guide, then
the Best Practices content for both migration and replication is already in the system. You can go to
sectionReplication-Specific Delta Configuration Steps [page 18] for the delta configuration steps for
replication.
Several steps are common for Migration and Replication and are listed in this section.
After the activation of the automated content, it is still necessary to perform the following manual activities.
This section describes the manual activities required at a high-level. The details of each manual activity are
found in the corresponding sections of IMG activities.
1. Import Picklists into ERP: Import Picklists from the EC Instance into SAP ERP HCM system using the
program ECPAO_PICKLIST_WRITER.
2. Adjust the Value Mapping Entity Definitions: Execute transaction SPRO and choose SAP Reference IMG for
the SAP Implementation Guide. Navigate to Personnel Management Integration with SuccessFactors
Employee Central Business Integration Builder Basic Settings Define Value Mapping Define Value
Mapping Entities . Choose EC instance SBP_MODEL_US. Replace the Dummy Picklists (denoted by Picklist
ID = 1) with the correct Picklist ID based on your latest picklist import from the Employee Central Instance.
3. If using the employee cost distribution template, you would need to implement the SAP Note 2543191
4. If you would like to adapt the Best Practices content, see the Adaptations [page 27] section.
5. If you would like to use a country specific gender, then see Country Specific Gender [page 25] section.
6. If you would like to copy the Best Practices templates into your own namespace, refer to the section
Copying Best Practices Templates [page 29].
Procedure
Procedure
Execute transaction SPRO and choose SAP Reference IMG for the SAP Implementation Guide. Navigate to
Personnel Management Integration with SuccessFactors Employee Central Business Integration Builder
Basic Settings Specify Employee Central Instance ID .
The delivered EC Instance ID for Best Practices is SBP_MODEL_US – SAP Best Practices for USA.
Procedure
Execute transaction SPRO and choose SAP Reference IMG for the SAP Implementation Guide. Navigate to
Personnel Management Integration with SuccessFactors Employee Central Business Integration Builder
Basic Settings Define Additional Foundation Objects for Migrating Data to EC .
Metadata from the Best Practices Employee Central content such as Field Names and Field Descriptions for
each of the EC templates are pre-delivered in the system. They are used for field mappings to ERP HCM fields.
The delivered metadata corresponds to a standard Best Practices Employee Central instance metadata and
is delivered as part of the table ECPAO_FLD. It can be viewed by navigating to the following path in IMG and
specifying the EC Instance ID: Personnel Management Integration with SuccessFactors Employee Central
Business Integration Builder Basic Settings Import Metadata from Employee Central Transport Imported
Metadata and Check Metadata for File-Based Data Transfer .
Picklist Option IDs can change from one SuccessFactors EC instance to another. Hence, it is required to import
picklists from the Employee Central instance. Prior to import, confirm that the picklists in Employee Central
have been migrated to MDF objects. This has been described in detail as part of the Getting Started Guide and
should already be completed.
Procedure
Note
If using a different EC instance ID other than SBP_MODEL_US, the other related configurations will have to
be copied over to the new instance.
Value mapping entries and value mapping details are delivered as part of the Best Practices content. To
view them and modify if needed, execute transaction SPRO and choose SAP Reference IMG for the SAP
Implementation Guide. Navigate to Personnel Management Integration with SuccessFactors Employee
Central Business Integration Builder Basic Settings Define Value Mapping .
Best Practices Content associates a dummy picklist ID to some pre-delivered Value Mapping Entities, You
need to replace it with the correct Picklist IDs after you import as described in section Import Picklists from
Employee Central to SAP ERP HCM system [page 11].
Procedure
1. Log on to the SAP ERP HCM system. Execute transaction SPRO and choose SAP Reference IMG for
the SAP Implementation Guide. Navigate to Personnel Management Integration with SuccessFactors
Employee Central Business Integration Builder Basic Settings Define Value Mapping .
2. To change the EC Picklist IDs associated to value mapping entities, navigate to Define Value Mapping
Entities.
3. Provide SBP_MODEL_US as the EC Instance when prompted. The value mappings that have been shipped
as part of the SAP Best Practices content are displayed.
4. Switch to the Change mode if you are in the Display mode.
5. Find the Value Mapping Entities that are mapped to the dummy picklists (EC Picklist ID column = 1).
ASSIGNMENT_TYPE_WS global_assignment_type
CHALLENGED_WS typeOfChallenge
CHALLENGE_GROUP challengeGroup
CHALLENGE_GROUP_DEU challengeGroup_DEU
COMMITMENT_INDICATOR commitmentIndicator
CONTINUED_PAY_MEASURE periodIndicator
CONTRACT_ID Contract_ID
CONTRACT_TYPE_WS contractType
COUNTRY_CODE_PHONE SFCC_PhoneCountryCode
COUNTRY_CODE_PHONE_ITA SFCC_PhoneCountryCode
COUNTY_GBR COUNTY_GBR
DEGREEOFCHALLENGE_DEP_ESP DEGREEOFCHALLENGE_ESP
DEGREEOFCHALLENGE_ESP DEGREEOFCHALLENGE_ESP
DEGREEOFCHALLENGE_ESP_REP DEGREEOFCHALLENGE_ESP
DEPARTMENT_FRA DEPARTMENT_FRA
DOCUMENT_TYPE_BRA permitdoctype
EDUCATION_LEVEL_BRA EDUCATIONLEVEL_BRA
EMAIL_TYPE ecEmailType
EMPLOYEE_CLASS_WS EMPLOYEECLASS
EMPLOYEE_CLASS_WS_GLOBAL EMPLOYEECLASS
EMPLOYMENT_RELATIONSHIP employmentRelationship
EMPLOYMENT_TYPE_WS employmentType
EMPLOYMENT_TYPE_WS_GLOBAL employmentType
ETHNIC_GROUP_USA ETHNICGROUP_USA
ETHNIC_GROUP_GBR ETHNICGROUP_GBR
EVENT_WS event
GRADE_BRA GRADE_BRA
HARMFUL_AGENT_EXP harmfulAgentExposureCode
INTERNSHIP_LEVEL_BRA InternshipLevel_BRA
INTERNSHIP_SCHOOL_BRA InternshipSchool_BRA
ISOCOUNTRYCODE ISOCountryList
ISSUINGAUTHORITY_DEU IssuingAuthority_DEU
LANGUAGE_CODE_WS language
MANDATORY_INTERNSHIP_BRA yesNo
MARITAL_STATUS_WS ecMaritalStatus
MILITARYSTATUS_GBR MILITARYSTATUS_GBR
MINIMUMFAMILYTAXBASIS_ESP MINIMUMFAMILYTAXBASIS_ESP
NAME_PREFIX nameprefix
PERMITDOCTYPE permitdoctype
PHONE_TYPE ecPhoneType
PHONE_TYPE_ITA ecPhoneType
PROVINCE_ESP PROVINCE_ESP
PROVINCE_ITA PROVINCE_ITA
RACE_BRA RACE_BRA
RELATION_TYPE_WS personRelationshipType
RELIGION_BRA RELIGION_BRA
RELIGION_IND RELIGION_IND
SALUTATION salutation
SALUTATION_DEP salutation
SPECIFICATION_BRA SPECIFICATION_BRA
STATE_BRA STATE_BRA
STATE_IND STATE_IND
STATE_WS STATE_USA
STREETTYPE_ESP STRTYPE_ESP
SUFFIX_WS namesuffix
TITLE_WS title
TYPE_OF_CHALLENGE typeOfChallenge
WORKER_CATEGORY workerCategory
YES_NO yesNo
Procedure
1. Execute transaction SPRO and choose SAP Reference IMG for the SAP Implementation Guide. Navigate
to Personnel Management Integration with SuccessFactors Employee Central Business Integration
Builder Organizational Data Integration .
This section describes the configurations that are required and pre-delivered as part of the SAP Best Practices
content.
Procedure
Execute transaction SPRO and choose SAP Reference IMG for the SAP Implementation Guide. Navigate to
Personnel Management Integration with SuccessFactors Employee Central Business Integration Builder
Organizational Data Integration Map Languages from Employee Central and ERP .
Procedure
Execute transaction SPRO and choose SAP Reference IMG for the SAP Implementation Guide. Navigate to
Personnel Management Integration with SuccessFactors Employee Central Business Integration Builder
Organizational Data Integration Define Org Data Settings for Employee Central instance .
The following Organizational Data setting configuration is pre-delivered as part of the SAP Best Practices
content:
Procedure
Execute transaction SPRO and choose SAP Reference IMG for the SAP Implementation Guide. Navigate to
Personnel Management Integration with SuccessFactors Employee Central Business Integration Builder
Employee Data Integration .
Procedure
Execute transaction SPRO and choose SAP Reference IMG for the SAP Implementation Guide. Navigate to
Personnel Management Integration with SuccessFactors Employee Central Business Integration Builder
Employee Data Integration Define Employee Data Settings for Employee Central Instance .
Procedure
Execute transaction SPRO and choose SAP Reference IMG for the SAP Implementation Guide. Navigate to
Personnel Management Integration with SuccessFactors Employee Central Business Integration Builder
Employee Data Integration Define Relationship Types for Managers and Employee-Related Org. Mgmt. Data .
Note
SAP Best Practices uses the standard evaluation path MANAGER. You can change this if required.
If you have already followed the Migrating Data from ERP HCM to Employee Central guide, then the following
steps are the delta configuration required for Replication.
Procedure
Execute transaction SPRO and choose SAP Reference IMG for the SAP Implementation Guide. Navigate to
Personnel Management Integration with SuccessFactors Employee Central Business Integration Builder
Basic Settings Maintain the Constant Values .
Procedure
The following configuration steps are delivered as part of the SAP Best Practices content.
Procedure
Execute transaction SPRO and choose SAP Reference IMG for the SAP Implementation Guide. Navigate to
Personnel Management Integration with SuccessFactors Employee Central Business Integration Builder
Organizational Data Integration Define Field Mappings for Organizational Data .
Field mappings between ERP fields and Best Practices EC fields for organizational data objects are defined in
this configuration activity. SAP Best Practices delivers the following as part of the content:
The following transformation templates are active by default in each of the template group:
The standard delivered field mappings are also provided as an Excel workbook along with the Best Practices
package.
If you wish to change the default templates or mappings, you can copy them into a separate template group
and modify as needed.
Procedure
The following configuration are required and are pre-delivered as part of the SAP Best Practices activation
report.
Procedure
Execute transaction SPRO and choose SAP Reference IMG for the SAP Implementation Guide. Navigate to
Personnel Management Integration with SuccessFactors Employee Central Business Integration Builder
Employee Data Integration Define Field Mappings for Employee Data .
Field mappings between ERP fields and Best Practices EC fields for employee master data are defined in this
configuration activity.
The transformation templates are delivered and are active by default in the template group. You can find further
details in the IMG activity in the system.
Note
• If using the employee cost distribution template, you would need to implement SAP Note 2543191 .
• ERP_WS_18_GB template is delivered as inactive by default as most of the customers in the UK do not
keep IT0004 (Challenge). Activate if it is required.
The Best Practice content uses BAdIs in cases where the logic for deriving the ERP fields is complex or cannot
be achieved through infotype mapping. The following BAdIs have been used:
BAdI logic to modify the mapping results for ERP fields from the EC Data.
In a few cases, even though the derivation of the ERP field has been done using infotype mapping, subsequent
modification of the data is necessary.
Procedure
Execute transaction SPRO and choose SAP Reference IMG for the SAP Implementation Guide. Navigate to
Personnel Management Integration with SuccessFactors Employee Central Business Integration Builder
Business Add-Ins Data Transfer from Employee Central .
Procedure
Execute transaction SPRO and choose SAP Reference IMG for the SAP Implementation Guide. Navigate to
Personnel Management Integration with SuccessFactors Employee Central Business Integration Builder
Employee Data Integration Define Template group to be used for Employee Data Replication from EC .
The following configuration is delivered as part of the SAP Best Practices content:
Procedure
1. Execute transaction SPRO and choose SAP Reference IMG for the SAP Implementation Guide. Navigate
to Personnel Management Integration with SuccessFactors Employee Central Business Integration
Builder Employee Data Integration Define Parameters for Employee Master Data and Org. Assignment
Query .
2. Modify the Target System entry by providing the Target Replication System defined in the EC instance.
Set the Full Transmission Start Date as late as possible, ideally to the date when you start to use the Employee
Central as the master system for organizational data.
This section describes the manual configuration steps required in the SAP ERP HCM system.
Procedure
1. Execute transaction SPRO and choose SAP Reference IMG for the SAP Implementation Guide. Navigate
to Personnel Management Integration with SuccessFactors Employee Central Business Integration
Builder Organizational Data Integration Enable Use of New Infotype Framework When Processing
Replicated Org Data .
2. Enable the flags OANSC, OANSK, OANSO and OANSS in the group SFSFI. This is described here in the
product documentation.
In the Best Practices mapping, the Organizational Object replication takes care of the position relations
such as Department, Job, Cost Center, and Manager Position.
3. Choose New Entries and enter the following data:
This will enable the new Infotype framework for integration between Organizational Management and
Personnel Administration. Refer to the documentation here for further context and information on this
setting.
To be compliant with the country laws it is required to provide the country specific gender based on the values
that are allowed in the corresponding countries. Currently, this is supported only for Germany Best Practices.
The following picklist IDs are added as part of the standard picklist
These are the picklists values for the field Gender in the Global Information Germany. These values are relevant
for translation.
gender_DEU M Male
gender_DEU F Female
In our sample value mapping, the following field is delivered as part of the Global info in Germany.
To support country specific gender values in the SAP ERP HCM system, two tables have been delivered.
• V_T77PAD_GENDER
• V_T77PAD_FRMADDR
These two tables need to be completed for country specific gender values and the same must be mapped
in the value mapping entity during BIB replication (Value mapping is pre-delivered). These will therefore be
replicated to the infotype 0002 GESCH field.
V_T77PAD_GENDER:
V_T77PAD_FRMADDR:
If you have customized the SAP Best Practices Employee Central instance with custom fields, then you will
need to make adaptations to the delivered SAP Best Practices Content.
Important:
Ensure that the SAP Best Practices for the EC instance has been applied as described in the Getting Started
Guide.
Procedure
1. Log on to the EC instance. Go to Admin Center and choose the OData API Metadata Refresh and Export
tool.
2. To make sure that the metadata is up to date, choose Refresh.
3. Choose Export for the Export Metadata to File option.
4. Store the Metadata in XML format on your local disk.
5. Logon to the ERP HCM system. Execute transaction SPRO and choose SAP Reference IMG for the SAP
Implementation Guide. Navigate to Personnel Management Integration with SuccessFactors Employee
Central Business Integration Builder Basic Settings Import Metadata from Employee Central Import
metadata for Web Service-Based Data Transfer from Employee Central .
6. Specify the EC instance to which you would like to upload the metadata.
7. Specify the .xml file previously downloaded in EC Metadata File.
8. Choose Update Metadata as the Action Type.
9. Optionally, carry out a test run by checking the Test Run checkbox.
10. Clear the Test Run checkbook and execute the program to update/insert metadata in the specified EC
instance.
11. If you have added custom fields to the organizational data, navigate to Personnel Management
Integration with SuccessFactors Employee Central Business Integration Builder Organizational Data
Integration Define Field Mappings for Org Data . Maintain the appropriate mapping with ERP HCM data
for the custom fields here.
12. If you have added custom fields to the organizational data, navigate to Personnel Management
Integration with SuccessFactors Employee Central Business Integration Builder Organizational Data
Integration Define Field Mappings for Employee Data . Maintain the appropriate mapping with ERP HCM
data for the custom fields here.
Procedure
1. Go to Admin Center in the EC instance and choose the Import and Export Data tool.
2. From the Select the action to perform drop-down, select Export Data.
3. From the Select Generic Object drop-down, select Picklist.
4. From the Include Dependencies drop-down, select Yes to include the dependencies.
5. From Select all data records drop-down, select Yes to export all picklists.
6. Choose Export.
7. Choose the Monitor Job tool in Admin Center.
8. Download the Download Status zip file and extract the picklist csv.
9. Log on to the ERP HCM system. Execute transaction SPRO and choose SAP Reference IMG for the SAP
Implementation Guide. Navigate to Personnel Management Integration with SuccessFactors Employee
Central Business Integration Builder Basic Settings Define Value Mapping Import Picklists from
Employee Central .
10. Specify the EC instance to which you would like to upload the picklists.
11. Specify the picklist file previously downloaded in EC Picklist File.
12. Specify EC Locale as en_US.
13. Choose Update Picklist as the Action Type.
14. Optionally, carry out a test run by checking the Test Run checkbox.
15. Clear the Test Run checkbox and execute the program to update/insert picklist in the specified EC
Instance.
Procedure
1. Log on to the ERP HCM system. Execute transaction SPRO and choose SAP Reference IMG for the SAP
Implementation Guide. Navigate to Personnel Management Integration with SuccessFactors Employee
Central Business Integration Builder Basic Settings Define Value Mapping .
2. To change the value mapping entities, navigate to Define Value Mapping Entities.
3. Provide SBP_MODEL_US as the EC instance when prompted. The value mappings that have been shipped
as part of the SAP Best Practices content are displayed.
4. Switch to Change mode if you are in Display mode. You can now modify the value mapping entities.
5. To change the value mapping details, navigate to Define Value Mapping Details.
Procedure
1. If you wish to update field mappings for Organizational data, navigate to Personnel Management
Integration with SuccessFactors Employee Central Business Integration Builder Organizational Data
Integration Define Field Mappings for Org Data . When prompted, provide the SAP Best Practices EC
instance. You can now modify the field mappings in the change view.
2. If you have added custom fields to the organizational data, navigate to Personnel Management
Integration with SuccessFactors Employee Central Business Integration Builder Organizational Data
Integration Define Field Mappings for Employee Data . When prompted, provide the SAP Best Practices
EC instance ID. You can now modify the field mappings in the change view.
You might want to copy the Field mapping (Template Groups) provided by SAP Best Practices and then adapt
them (instead of modifying the delivered templates directly). In this case, the following options are available.
The Best Practices transformation template groups can be copied from the delivered SBP_MODEL_US
Employee Central instance ID to a new Employee Central instance ID. In order to perform this, the following
steps are needed:
Further details for the copying functionality are available in the Program documentation
• Update Metadata: You can do this under IMG Activity Basic Settings Import Metadata from Employee
Central . Choose the first activity under this path.
• Import Picklists: You can do this under IMG Activity Basic Settings Define Value Mapping Import
Picklists from Employee Central (You will need Picklists CSV from EC).
• Define Value Mapping Entities: The value mapping entities associated with SBP_MODEL_US are already
delivered. You may need to adjust these based on your new/updated picklists.
• Define Value Mapping Details: The value mapping details for the Value Mapping Entities are pre-delivered.
However, based on new Picklist values or new Value Mapping Entities you may have to adjust.
• Refine the Template mappings: Check the different templates in detail and look out for any new deleted
EC fields or more fields that you may need to map.
• Lastly, you may need to copy the BAdI implementation classes and adjust the code accordingly. Regarding
BAdIs you can refer to Business Add-ins [page 22].
The solution delivered will be able to derive cost center for the Organizational Object Templates in
the ERP HCM system during replication if the cost center being replicated is 14 characters, that is,
Controlling Area(4) + Cost Center(10). If you need to work with combinations that have a different
pattern of lengths for Controlling Area and/or Cost Center, replication using generic object replication
may fail with the error message Error when mapping Employee Central field cost Center, field value
XXXYYYYYYYYYY (SFIOM_PROCESSING224). Follow the instructions in KBA 0002706481 which
describes how to handle these situations.
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.