What You'll Learn In this £-Bite, you'll learn how to implement SAP SuccessFactors with SAP Cloud Platform integration service through several different deployment models. These include talent hybrid, side by side , and fu ll cloud/ core hybrid deployment methods. Then, deploy your integration content with in depth parameter and connection settings. Start planning your SAP SuccessFactors integration project today!
SAP's cloud integration strategy is focused on three key areas: technology, prepackaged integrations, and customer choice. In this E-Bite, we'll focus on the technology area. The driving technology behind SAP's cloud integration strategy is SAP Cloud Platform Integration. This technology provides integration services required for cloud and on-premise applications based on SAP Cloud Platform. SAP Cloud Platform Integration provides an easyto-use mechanism for pulling data and its business processing into a single source of truth. The open, flexible, web-based tool integrates processes and data among the cloud, on-premise systems, and third-party applications. SAP Cloud Platform Integration is a cloud-based, subscription-based service offered through SAP data centers. Multitenancy is available, ensuring that each customer's data is protected by firewalls, rolling software updates (which SAP applies monthly), a strong focus on security isolation, centralized monitoring/administration, and horizontal scalability. SAP Cloud Platform Integration is an open solution that can be extended with new adapters and can be used in projects by partners and customers to enhance standard features and development further. SAP Cloud Platform Integration is available in a standard edition, professional edition, developer edition, application edition (bundled with SAP Cloud apps), and SAP HANA AppServices premium edition. SAP Cloud Platform Integration can be used by SAP S/4HANA, SAP SuccessFactors, SAP Hybris Cloud for Customer, SAP Hybris, SAP Ariba, Concur, and others. Our focus in this book will be on standard SAP SuccessFactors integrations for the cloud deployment models: talent hybrid, side by side, core hybrid, and full cloud. One of the biggest benefits of SAP Cloud Platform Integration is the catalog of prepackaged integration content available for various solutions. SAP has delivered standard prepackaged content for SAP SuccessFactors integrations for all relevant cloud deployment models. The prepackaged integration content can be copied to each customer's own tenant and
5
What Is SAP Cloud Platform?
configured to each customer-specific requirem ent, such as for endpoint configurations. SAP enables your journey to the cloud with productized integrations that connect SAP on-premise solutions with the SAP SuccessFactors cloud solutions. Your starting point is flexible, based on your business situation. There are four main cloud deployment models, as shown in Figure 1: 1. Talent hybrid
This model allows customers to keep all SAP on-premise applicationsSAP Personal Administration/Organizational Management (PA-OM), SAP Time and Attendance, and SAP Payroll - and deploy all talent processes to SAP SuccessFactors Talent Solutions. Standard integrations keep both the data and processes in sync between SAP ERP Human Capital Management (HCM) on-premise and SAP SuccessFactors Talent Solutions in the cloud. 2. Core hybrid
This model allows customers to move all core HR processes to SAP SuccessFactors Employee Central while keeping existing SAP ERP HCM Payroll and Time and Attendance applications in place. Standard integrations ensure that all HR data from SAP SuccessFactors Employee Central is in sync to support SAP Time and Attendance and SAP Payroll . on-premise.
3. Full cloud This model allows customers to deploy all core HR processes, SAP Time and Attendance, and SAP Payroll in the cloud. There are standard integrations delivered for processes that still require some minimal HR data back in SAP ERP. For customers that integrate data with third-party vendors such as ADP or Kronos, standard-delivered integration templates are available via SAP Cloud Platform Integration. 4. Side by side This model allows customers to deploy SAP SuccessFactors Employee Central for employees not on SAP ERP HCM side by side with an existing SAP ERP HCM implementation. This approach is a mixture of cloud
6
I
1
What Is SAP Cloud Platform?
I
1
and on-premise. However, the user interface can be integrated so that users only need access one system. Talent Hybrid
Talent Analytics
Core Hybrid
Full Cloud
,.-..PA&OM
PA&OM Talent Solutions Workforce Analytics
Payroll Talent Solut ions Workforce A nalytics
Side by Side
Talent Analytics Personnel Admin. (PA)
& Org. Mgmt. (OM)
Productized Integrations
Time & Attendance
Time & Attendance
Time & Attendance
Payroll
Payroll
Payroll
OM - Organizational Management PA - Personnel Administration
Figure 1 SAP SuccessFactors Cloud Deployment Models
This E-Bite will focus on cloud deployment models for SAP SuccessFactors integration. We'll cover the basic steps of how to use SAP Cloud Platform Integration to support standard SAP SuccessFactors integration needs, which are the same as when integrating with SAP ERP and with SAP S/4HANA on-premise or cloud applications. This E-Bite focuses mainly on the setup required in SAP Cloud Platform Integration. Note There are also configurations required in SAP ERP and SuccessFactors to complete the entire end-to-end system integration. Please refer to the SAP-delivered integration guides available at t he SAP Help portal for further information: http://help.sap.com/hr_eci ntegrat ion and http://help-legacy.sap.com/erp_sfi.
7
What Is SAP Cloud Platform?
1.1
Basics of SAP Cloud Platform Integration
This section will cover the basic architecture overview within SAP Cloud Platform Integration. Each customer is assigned an account accessible via the Internet, which is the basic entry point to SAP Cloud Platform, a hosted environment provided by SAP that defines a set of authorizations and resources allocated to the customer. Let's now establish some key definitions for important terms used throughout this E-Bite before we dive into the details:
>> SAP Cloud Platform Integration tenant A tenant is a logical entity that represents the physical resources of SAP Cloud Platform allocated to a specific participant and within an application context. SAP Cloud Platform Integration is multitenant capable.
>> Runtime node Processes messages exchanged through the tenant. Integration flows run on this node type. Runtime nodes interact with external systems and the load balancer. >> Tenant management node Manages the runtime nodes of a cluster and acts as an agent between the human user and the runtime components of SAP Cloud Platform Integration. This node type interacts w ith human users who perform tasks such as deploying and monitoring integration artifacts. >> Tenant ID Each tenant has a unique ID. >> Tenant ops server The tenant ops server URL provides access to the SAP Cloud Platform Integration operations environment via the web UI. >> Worker node URL You can access the SAP Cloud Platform Integration environment from different clients via specific worker node URLs.
8
I
1
What Is SAP Cloud Platform?
I
A tenant is a logical entity that represents the virtual physical resources of SAP Cloud Platform allocated to a specific participant within an application context. SAP Cloud Platform Integration is multitenant capable, which means that customers are isolated in terms of memory, data storage, and CPU. Although tenants in SAP Cloud Platform Integration share the same physical resources, they can't interfere with each other, because different database schemas are used for each. Tenants run on shared resources in SAP data centers and are strictly separated from each other. Tenants are composed of two different nodes types: tenant management nodes and runtime nodes. For each tenant, is one or more virtual machines (VMs) are operated. The general architecture setup is illustrated in Figure 2, which depicts an administrator accessing an account through the SAP HANA cockpit. The administrator is then responsible for defining additional authorizations for users.
Sender
Receiver A
R R>
Administrator Manages user permission Integration Dev. Access, deploy, and monitor integration content
R>
R>
Load Balancer
R,
R>
SAP Cloud Platform Tenant Cluster Tenant Management Node
Run ti me Node
Via Persistency Service
Monitoring Data Message Content
Figure 2 Arch itecture Overview
9
1
What Is SAP Cloud Platform?
The integration developer accesses the web-based frontend to design, deploy, and monitor the integration flows. For the tenant assigned to the account, the tenant cluster consists of one or more tenant management nodes and runtime nodes. All inbound traffic is managed by a load balancer, which dispatches messages to the appropriate tenants. The runtime node processes messages and routes them to one or more receiver systems. During the processing of a message by the runtime node, data can be stored in a database at various steps. SAP Cloud Platform Integration Development Cycle via Web UI
The configuration and implementation of the integration scenarios is supported by a dedicated development cycle using the SAP Cloud Platform Integration web UI end-to-end tool. Four main development cycles form parts of the web UI tool:
1. Discover Enables customers/partners to browse through all available, public, standard predelivered integration content. Once the correct integration package has been identified, it can be downloaded and copied into the customer's own tenant/workspace, from which the content can be further configured based on customer requirements. 2. Design Once the integration package has been copied, it can be designed and modeled. A palette section on the left-hand side of the main work area within the Web UI includes all the steps required to model the integration flows, such as signing, encryption details, and mappings. These entries from the palette can be added to the modeling area via drag-anddrop functionali ty. The steps can be connected which then defines the execution sequence. The steps are adjusted in the properties area, which sits beneath the process model. The details relevant for execution are configured here.
10
I
1
What Is SAP Cloud Platform?
3. Run
Once the integration has been configured, it can be deployed in the customer tenant and executed.
4. Monitor Once the integration has been processed, then the message-processing logs for the artifacts can be viewed. Dedicated tiles that display successful and failed messages are available in the SAP Cloud Platform Integration web UI. Also, integration content monitoring can be viewed for details on the integration scenarios deployed; further information regarding credentials and value mappings can be found here.
1.2
SAP Cloud Platform Integration Connectivity Setup
SAP Cloud Platform Integration uses secure communication protocols such as HTTPS, SSH SFTP, or SMTP/S for connecting systems for data exchanges. Depending on the connected system's supported communication protocol, one of these secure communication methods can be used for integrating with SAP Cloud Platform Integration for both inbound and outbound connections. To speed up the integration scenario deployment process, SAP Cloud Platform Integration offers out-of-the-box system-dedicated connection adapters, such as the SAP SuccessFactors adapter, Facebook adapter, Twitter adapter, and so on. These adapters come with system-specific connectivity configuration features, and they use the HTTPS protocol for establishing secure communication between SAP Cloud Platform Integration and connected systems such as SAP SuccessFactors. One of the most scenarios faced with SAP Cloud Platform Integration is integrating SAP SuccessFactors with SAP ERP HCM on-premise for employee master data replication as part of the core hybrid/full cloud deployment model. Connectivity setups for other SAP SuccessFactors integration cloud deployment models will follow the same setup steps. A typical integration landscape will look like the example integration scenario shown in Figure 3 and Figure 4.
11
I
1
What Is SAP Cloud Platform?
I
1
firewall I SAP Cloud
Customer network (on-premise)
I I I
SAP SuccessFactors Employee Central
~ (1) SuccessFactors
adapter over HTTPS
SAP Cloud Platform Integration tenant
1 (2)
I I I I
SOAP adapter over
SAP Web dispatcher (Load balancer)
(3) Forward SOAP
SAP ERP HCM
adapter
over HITPS
HTTPS
Figure 3 Integration Landscape Diagram for Employee Data Extract ion Flow from SAP SuccessFactors Employee Central to SAP ERP HCM
firewall SAP Cloud
SAP SuccessFactors Employee Central
-(2) SuccessFactors adapter over HIT PS
SAP Cloud Platform Integration tenant
I I I I I I
' I
Customer network (on-premi se)
SAP Web dispatcher (load balancer)
SAP ERP HCM
(1) SOAP adapter over HITPS
Figure 4 Integration Landscape Diagram for Employee Data Confirmation from SAP ERP HCM to SAP SuccessFactors Employee Central
As illustrated in Figure 3, SAP Cloud Platform integration is connected to SAP SuccessFactors Employee Central for employee data extraction using the SAP SuccessFactors adapter through HTTPS secure communication. The employee data is then sent over to SAP ERP HCM using a SOAP adapter over HTTPS communication, going through either the SAP Web Dispatcher (as seen in Figure 3 and Figure 4) or SAP Cloud Platform cloud connector. The SAP Web Dispatcher is set up in front of SAP ERP HCM as an additional layer that serves as a load balancer to protect SAP ERP HCM from receiving anonymous inbound calls which do not originate from SAP HCP-IS. The load balancer will only accept inbound calls from SAP HCP-IS. On the other end, in Figure 4, SAP ERP HCM sends an employee confirmation message out to SAP Cloud Platform Integration using a SOAP adapter over HTTPS. The confirmation message is then forwarded by SAP
12
What Is SAP Cloud Platform?
Cloud Platform Integration to SAP SuccessFactors using the SAP SuccessFactors adapter over HTTPS communication to complete the employee data replication integration scenario. SSL Outbound Connection from SAP Cloud Platform Integration to SAP SuccessFactors
The procedure for setting up connectivity between SAP Cloud Platform Integration and an SAP ERP HCM on-premise system/SAP SuccessFactors system is as follows: 1. Download and import the SAP SuccessFactors SSL server root certificate into the SAP Cloud Platform Integration tenant key store. 2. Deploy the SAP SuccessFactors SFAPI user credentials artifact into the SAP Cloud Platform Integration tenant key store for using basic authentication to authorize SAP Cloud Platform Integration to call SAP SuccessFactors. SSL Outbound Connection from SAP Cloud Platform Integration to SAP ERP HCM On-Premise Using SAP Web Dispatcher
The procedure of setting up connectivity between SAP Cloud Platform Integration and SAP ERP HCM on-premise via the SAP Web Dispatcher load balancer is as follows: 1. Whitelist SAP Cloud Platform Integration IP address ranges in the customer's on-premise network firewall rules to accept inbound traffic from these IP address ranges. The exact IP address ranges can be found on the SAP Cloud Platform Integration HELP page under OPERATING AND MONITORING SAP HCI: https://cloudintegration.hana.ondemand.com/ PI/help. 2. Download and import the SAP Web Dispatcher SSL server root certificate into the SAP Cloud Platform Integration tenant key store.
13
I
1
What Is SAP Cloud Platform?
3. Deploy the SAP ERP HCM technical user credentials artifact into the SAP Cloud Platform Integration tenant key store for using basic authentication to authorize SAP Cloud Platform Integration to call SAP ERP HCM. Note If SAP Cloud Platform cloud connector is used as a reverse invoke proxy between t he on-premise network and SAP Cloud Platform Integration instead of the load balancer SAP Web Dispatcher, then there's no need to configure an on-premise network fi rewal l rule to whitelist the SAP Cloud Platform Integration IP address ranges and import the SAP Web Dispatcher SSL server root certificate into the SAP Cloud Platform Integration tenant key store. SAP HANA Cloud Connector runs as an on-premise agent in a secured network and acts a reverse invoke between on-premise network and SAP Cloud Platform Integration. It is an alternative solution to SAP Web Dispatcher that serves as a link between on- premise systems and SAP Cloud Platform Integration
SSL Inbound Connection from SAP ERP HCM On-Premise System to SAP Cloud Platform Integration
To set up the SSL inbound connection from SAP ERP HCM on-premise to SAP Cloud Platform Integration, complete the following steps: 1. Download and import the SAP Cloud Platform Integration SSL server root certificate into the SAP ERP HCM key store (Transaction STRUST); this step applies to all integration scenarios for all cloud deployment models. 2. No user credentials artifact is required to deploy for this communication. However, an SCN user with the SAP Cloud Platform Integration tenant role ESBMessagi ng . send is required for SOAMANAGER web service configuration in SAP ERP HCM on-premise. Note SCN users are used as communication users for inbound communications from the sender system to the SAP Cloud Platform Integration tenant. Th is communication user must be assigned the ESBMessagi ng . send role in the SAP Cloud Platform cockpit.
14
I
1
What Is SAP Cloud Platform?
1.3
Monitoring in SAP Cloud Platform Integration
SAP Cloud Platform Integration offers an easy-to-use, web-based message monitoring tool that allows integration administrators or developers to check the status of integration message flow and integration content artifacts. To access the SAP Cloud Platform Integration web-based messagemonitoring tool shown in Figure 5, go to the SAP Cloud Platform Integration tenant landing page (for example, https:///itspacesl) and navigate to MONITOR from the menu. There, you'll see the following three page sections: )) MONITOR MESSAGE PROCESSING All integration message processing logs can be accessed here. This is where integration administrators or consultants spend most of their time, checking message processing logs for integration error troubleshooting. The MONITOR MESSAGE PROCESSING tool reports every message processing status together with the detailed processing log, including time, date, and the payload attachment if the latter is turned on in the iFlow. )) MANAGE INTEGRATION CONTENT All integration artifacts that are deployed can be monitored here to check the integration artifact runtime status. )) MANAGE SECURITY MATERIAL All security artifacts, such as the key store and basic authentication credentials, can be monitored here. Figure 5 shows the overview page of the Web-Based Message-Monitoring tool where you can access the MONITOR MESSAGE PROCESSING tool, the MANAGE INTEGRATION CONTENT tool, and the MANAGE SECURITY MATERIAL tool.
15
I
1
Overview of SAP Cloud Platform Integration Content by Deployment Model
~1onitor
I
2
tAessage Prooessing
All Integration Flows
All Integration f lO\'IS
P.lst Hoor
P•st Hoi;r
24
All fntegiation Flo\vs
All Integration FIO\vs
All Integration Flows
Past H°"r
Pols I Houf
Past Hour
0
24
fl I 01 f.tC;S$ ~C$
0
Refry loleSsilgeS
0
Compte.led t.lC;SS~ts
Manage Integration Content
All
All
119....
All
105 $t.)rte
13
+
ErrOf
Manage Security Material '--
Security Material
Certificate-to-User M8ppings
47
Afld>lCCS
1
ArtifJClS
Fig ure 5 Web-Based Message-Mon itoring Tool
2
Overview of SAP Cloud Platform Integration Content by Deployment Model
This section describes how to find, download, configure, and implement the standard available SAP SuccessFactors integration content for SAP Cloud Platform Integration for each deployment model. Note that the core hybrid, side by side, and full cloud deployment models use the same standard SAP Cloud Platform Integration content and settings; thus, the content covered for the full cloud model (Section 2.1) will be same for the core hybrid and side by side models and won't be repeated. Only the differences in configuration set up will be noted.
16
Overview of SAP Cloud Platform Integration Content by Deployment Model
2.1
Full Cloud Deployment Model
The full cloud deployment model allows customers to deploy all core HR processes, SAP Time and Attendance, and SAP Payroll in the cloud via SuccessFactors Employee Central. There are standard integrations delivered in SAP Cloud Platform Integration for those processes that still require HR data to be sent back in SAP ERP. For customers that integrate with other third-party vendors such as ADP or Kronos, there are standard-delivered integration templates available, but these won't be discussed in this E-Bite. This section outlines the complete end-to-end process required to set up full cloud integrations with SAP ERP using SAP Cloud Platform Integration.
Prerequisites First, before we begin, please ensure the following prerequisites have been met: >> Have access to the SAP Cloud Platform tenant. >> Obtain the SAP Cloud Platform tenant URL. >> Have access to the SAP ERP system, including access to Transaction SOAMANAGER to activate the web services and Transaction STRUST (Trust Manager) for SSL connection purposes. >> Setting up the SOAMANAGER configuration for the employee data integration replication scenario is required before SAP Cloud Platform Integration configuration can be completed. (Refer to the section "Employee Data Integration Process Scenario" for detailed setup steps.) >> Set up the technical integration (API) user in SAP SuccessFactors Employee Central that SAP Cloud Platform Integration uses to communicate with SAP SuccessFactors Employee Central. >> Set permissions for the technical API user to use SOAP and ODATA APls. >> Enable APis in SAP SuccessFactors provisioning.
17
I
2
Overview of SAP Cloud Platform Int egration Content by Deployment Model
>> Ensure all connections are implemented. (See the Connection subsections of each scenario section for further details.) >> Ensure integration add-on ODTFINCC is installed. >> Enable IDoc change pointers in SAP ERP. >> Define logical system, distribution model, RFC destination, and partner profiles in SAP ERP. Refer to the "Connections" subsection in the section "Cost Center Integration Scenario Overview" for further details. Discovery and Copy
Let's look at the configuration and implementation of integration scenarios for the full cloud deployment model. At the time of writing, SAP offers three main integration scenarios as predelivered integration content to support the full cloud, core hybrid, and side by side deployment models: 1. Replicate cost centers from SAP ERP to SAP SuccessFactors Employee Central 2. Replicate employee data from SAP SuccessFactors Employee Central to SAP ERP 3. Replicate organization data from SAP SuccessFactors Employee Central to SAP ERP To start using the standard predelivered integration content in SAP Cloud Platform Integration, go to the tenant landing page (for example, https:// /itspaces/) and navigate to DISCOVERY from the menu . There, you'll see all the available integration packages published by SAP. Figure 6 shows an excerpt from the DISCOVERY page. The following integration packages are relevant to full cloud, core hybrid, and side by side deployment models: )) ERP TO SUCCESSFACTORS EMPLOYEE COST CENTER )) SUCCESSFACTORS EMPLOYEE CENTRAL TO ERP EMPLOYEE DATA )) SUCCESSFACTORS EMPLOYEE CENTRAL TO ERP ORGANIZATIONAL DATA )) ERP TO SUCCESSFACTORS EMPLOYEE CENTRAL CONFIRMATION
18
I
2
I
Overview of SAP Cloud Platform Integration Content by Deployment Model
NE\'/ ( 10)
2
W>l (65j
$A? Hyl)ti:S $eNICe Engagement center
sp,p M)l:>ftS ,.,.._i:a:rkei#'lg
lnttgration v..lth SAP ERP
StarCh 1n:egrati0f'I
@• SAP
@• ~-""
@• ~. .,,,.
@, ~'"'""
P\dthed 110.,-. ~
,.....,_.. ISd.J)·s •
~ l&clirf• '90
P\otlit'*' 17 days~
SAP &ICCie$$F3(:10r$ Leaming and SAP ERP FS'latldats 1n:egrati0n
SA? Hy0ti$ CIOVO tor ~tomer tn1egratton v.ith SAP Hybns 1.1arttt1ng
SAP SJ.&HANA t.•;).f1(e1;ng
SueoeS$F3C:lOI$ RCtA v.'llh
NI. Ele((IOf'llC VAT Ret11rn
CIOud • SAP ERP Order and
Thilrd Party Assessment
Sta:ement and EC sates Lis<
B\lwitts Partr.e-r lnttgratlO
Vtndor-SHL
@, ::.. ....
@, ~~'"
@, ~'"'"
@, :'-..
_.,_.,._. 2Sdqs ~
~1•cl.1rl•arao
""°"'*' 2'
PIMI,_, M N)' 'lllO
eOOC\ltl'lent Ele<:!tonie lnvolelflO :or Chile
VPrtlOI\ 2 0 1
@• "'-" P\lalit1'411 20 dfY• '9C>
Google Ad'o'/Olds PalO
S\te«$$F .-.C-l.0'$ HCt.4 Suite OnboardlnO v.lh SA..O ERP HCIA
Figure 6 Published Standard Integration Packages from SAP
Note
If you're implementing the SAP Success Factors integration with SAP S/4HANA Cloud, please use only iFlow S4HANA_t o_ SFSF_EC_ CostCenter i ntegrat i on of integration package SucCESSFACTORS EMPLOYEE CENTRAL INTEGRATION WITH SAP S/4HANA, CLOUD EDITION FOR COST CENTER INTEGRATION CONFIGURATION. Use the integration packages listed previously for employee data, organ ization data, and confirmation integration configuration for SAP SuccessFactors integration w ith SAP S/4HANA Cloud.
Once you've found the required integration packages, copy them to your design workspace by hovering over each integration package tile and selecting COPY TO WORKSPACE. For the initial copy of an integration package, SAP Cloud Platform Integration doesn't allow you to copy into your own namespace. Once you copy a second time, SAP Cloud Platform Integration will prompt you to provide your own namespace suffix. Use the following steps to copy and rename the integration package: 1. Select the COPY TO WORKSPACE icon shown in Figure 7 to copy the selected standard integration package to your own workspace. 19
""°
Overview of SAP Cloud Platform Integration Content by Deployment Model
SuccessFactors Employee Central to ERP Employee Data
C® Plj)is hed·
SAP Version. 3.0.0
2 months ago
tr-,.
IGJ J Copy to worksp•ce
j
Figure 7 Copy Integration Package
2. Select CREATE COPY to copy the integration package, as shown in Figure 8.
Messages
O
Could not copy integration package, as rt a1reaay exists In customer workspace; Check the list of auplieatea resources
>
D
Create copy
Figure 8 Create Copy
3. Provide a suffix to create your own integration package file name, as
shown in Figure 9. Provide suffix Create copy wrth sumx 2.1.2017_0.28.19
(Leave blank for aefa
Enter a suffix for the copy
Figure 9 Create Integration Copy with Suffix
Now that you've completed the first step of integration scenarios configuration and implementation, let's discuss the design steps.
20
I
2
Overview of SAP Cloud Platform Integration Content by Deployment Model
2
Design You should have all the relevant integration packages saved in your design workspace by now. To check, navigate to DESIGN from the menu. In the left pane, under OVERVIEW, you should see all the integration packages copied from the D1scoVERY page (see Figure 10). With all the relevant integration packages in place, you can begin the detailed configuration of each individual integration scenario, as discussed in the following subsections.
Design suc~ssFac1ors EmplOyee central 10
SUccessFactors ErnplOyee Central to SAP ERP ErnplOyee Dala Replication
s ®
Q
SuccessFactors Employee Central to SAP ERP Employee Data Replication
overvie\'I
~rSkln
3.0.0
( fjl )
createo By
5uecessF aa ors EmplOyee Central to
1039368
SAP ERP Employee Data \Vlll l>e updated on 11/0312017
1 Qv.neo By SAP
1Creation Date 2119/16 10:34:18 AM
I Last MOdi4eO By: SYSTEM
I Mode ;onligure.
only
I Last MOdi'ieO Dale 1213116 8'. 22.21 AM
Description: Thi$ inregration package en.ables you t o replicate employee master data from SAP Suc-c-essfactOtS Employee Cen1ral to an Enterprise ResOU'c-e Planning (ERP) system With this integation scenario you can manage en-c>loyees using Employee Central as the system of record replicate the employees· data into global infolypes in the ERP sy stem, and run there further processes for these employees. Prerequisite f« us.ing this integration scenario Yoo need to hav e the PA_SE ...IN 100 add-on \\lith
SP13 Of higher installed Note You are only allowed to configure the content as described in 1he guide If you make modifKations not described in the guide, SAP v1i11 oot provide support for lhe modfied con1:eo1
Arllfacts ( 1)
Act1~os
Name
~rsk>n
Type
Act Ion
s EmplO}ee central 10 ERP Employee Data
300 u nmocurieo
I Wil be uixsate<:I on 11/03.,2017
Pro~s.s
Integration
Figure 10 Design Workspace
21
~
Overview of SAP Cloud Platform Integration Content by Deployment Model
Cost Center Integration Scenario Overview
In most organization system design, the master system of cost centers is maintained in SAP ERP Financials. However, the cost center is required in SAP SuccessFactors Employee Central for employee cost center assignment activities. Therefore, cost center integration is required to enable the replication process. The cost center integration scenario consists of only one integration process. In technical system design, the cost center is sent from SAP ERP to SAP Cloud Platform Integration in an !Doc XML format. The !Doc XML is then transformed into an SAP SuccessFactors Employee Central OData web service by SAP Cloud Platform Integration , which then performs a mapping and sends the result to SAP SuccessFactors Employee Central.
Configurations and Parameter Settings To begin configuration, select SAP ERP TO SUCCESSFACTORS EMPLOYEE CENTRAL CosT CENTER REPLICATION from the integration package list. There are two artifacts delivered as standard for supporting the cost center integration scenario: )) ERP TO EMPLOYEE CENTRAL COST CENTER (TYPE: PROCESS INTEGRATION) >> ERP TO EMPLOYEE CENTRAL COST CENTER LANGUAGE TABLE (TYPE: VALUE MAPPING) For the parameter settings and configuration, we'll focus only on the ERP TO EMPLOYEE CENTRAL COST CENTER integration flow. Select CONFIGURE from the ACTIONS dropdown (see Figure 11) to enter integration flow configuration mode. Refer to the configuration and parameters below to complete the standard configuration settings.
22
I
2
Overview of SAP Cloud Platform Int egration Content by Deployment Model
ctnltrs. sue!\ u assigning empk>yffs. ~ Empt0yee Coeflttal PrtrtQUbltt IOI ~ tllls lnttgraOOn sctnano You need IO havt !ht OOTFINCC 600 aoo.on 'o\'il11 SPIOor hlghtr lnstalltd
Note VOi.i a1e ony alOWed lO conngiure Ile oonknl as ecJ In the giukfe. SAP
v.• not P4'0YIOO
$\IPPQft ror the mo
Name
0
,,. 1 oo
vaiue Map~
Figure 11 Enter Configure Mode
Configuration for SAP ERP to SAP SuccessFactors Cost Center Data Replication Sender and Receiver Settings To set up the sender, set the following parameters: >> SENDER: Default value SAP_ERP (leave as-is). >> ADAPTER TYPE: Default value !DOC (leave as-is). >> ADDRESS: Standard value /ERP_To_EC_COSTCENTER_REPLICATION_IDoc (leave as-is). >> CERTIFICATE BROWSE/SUBJECT DN AND ISSUER DN: Import client certificate from sender system (only applicable for client certificate authorization). >> AUTHENTICATION TYPE: Select USER ROLE. See Figure 12, which displays the sender parameter values for the Cost Center Replication iFlow.
23
t!i
Overview of SAP Cloud Platform Integration Content by Deployment Model
Configure "ERP to Employee Central Cost Cente('
Sender
Receiver
Senoer Mapter Type: Moress:
Authorization:
Parameters
SAP_ERP
v
IOOC
v
/ERP_to_EC_Costcenter_Repllcatlo
User Role
v
save
DeplOy
ciose
Figure 12 Configure Sender Settings of ERP to Employee Central Cost Center i Flow
The SAP Cloud Platform Integration flow supports both authorization options either using user role or client certificate authorization to authenticate and authorize the inbound connection from sender system to SAP Cloud Platform Integration. We'll discuss the two options ahead. The user role method uses either basic authentication or client certificate authentication with certificate to user mapping methods. The authorization is based on role-based user permissions, in which the communication user connecting via SAP Cloud Platform Integration must have the ESBMessag i ng . sen d role assigned. The client certificate method uses the sender's digital client certificate for authentication in SAP Cloud Platform Integration. The authorization check is based on evaluation of the client certificate distinguished name (DN) against the configured DN of the integration flow. For more comprehensive information about SAP Cloud Platform Integration authentication and authorization strategies, visit https://cloudintegration.hana.ondemand.com/PI/help and search for the specific topic you want to learn more about.
24
I
2
Overview of SAP Cloud Platform Integration Content by Deployment Model
To set up the receiver, set the following standard parameters: >> RECEIVER: Default value SFSF_EC. >> ADAPTER TYPE: Default value SuCCESSFACTORS. >> ADDRESS: Enter the SAP Successfactors Employee Central API base URL here, for example: https://apisalesdemo4.successfactors.com. >> AUTHENTICATION TYPE: Default value BASIC AUTHENTICATION. >> CREDENTIAL NAME: Enter the name of the SAP SuccessFactors credential artifact you've deployed. The following standard parameter values can be used in the PARAMETERS tab:
>> USE_EXTERNAL_COST_CENTER: Enter "TRUE" if you'd like to replicate SAP cost center IDs as reference cost center IDs in SAP SuccessFactors Employee Central; otherwise, enter "FALSE". >> PERSON_RESP_TARGET_FIELD: Enter the name of the custom field in SAP SuccessFactors Employee Central that holds the name of the person responsible for the cost center from SAP ERP; otherwise, set this option to blank. >> ERP _DEFAULT_LANGUAGE : Enter the mandatory default value language for Cost Center Description to be transferred from SAP ERP to SAP SuccessFactors Employee Central. For example, E for English. >> ENABLE_PAYLOAD_LOGGING: Enter "TRUE" to keep the complete message payload containing all the data transferred in the SAP Cloud Platform Integration message processing log. This feature is useful for issue analysis and troubleshooting purposes. Otherwise, enter "FALSE". >> COMPANY_ID_TARGET_FIELD: Enter the name of the custom field in SAP SuccessFactors Employee Central that holds the company ID from SAP ERP. You're only required to fill this field ifyou're transferring SAP ERP company codes to custom fields in SAP SuccessFactors Employee Central. Otherwise, set it to blank.
25
I
2
Overview of SAP Cloud Platform Integration Content by Deployment Model
Once the preceding configuration is completed, you can deploy the ERP TO EMPLOYEE CENTRAL COST CENTER integration flow in the SAP Cloud Platform Integration runtime node by clicking the DEPLOY button, as illustrated in Figure 13. Configure '"ERP lo Employee Cenlral Cosl Center"
Connections There are two types of connection configurations to set up for using the ERP TO EMPLOYEE CENTRAL COST CENTER iFlow replication: connection from SAP ERP to SAP Cloud Platform Integration and connection from SAP Cloud Platform Integration to SAP SuccessFactors Employee Central. To enable the connection from SAP ERP to SAP Cloud Platform Integration, proceed as follows: 1. Set up a new RFC HTTP connection type Gin Transaction SM59. Fill in
the following details: - SAP Cloud Platform Integration runtime host URL in TARGET HOST. - Cost center iFlow sender address in PATH PREFIX, for example: /cxfl ERP_to_EC_CostCenter_Replication_!Doc. - Select BASIC AUTHENTICATION and enter your SAP Cloud Platform Integration user name and password.
26
I
2
Overview of SAP Cloud Platform Int egration Content by Deployment Model
2. Create a logical system for SuccessFactors Employee Central in Transaction BD54. 3. Create a distribution model view in Transaction BD64 by assigning the SAP ERP logical system as the sender and the newly created SAP SuccessFactors Employee Central logical system as the receiver, with cost center IDoc message type ODTF_OCTR. 4. Create a XML HTTP port for IDoc processing in Transaction WE21 with the following attributes: - RFC DESTINATION name created in step 1 - APPLICATION/X-SAP.IDOC as content type - Select SOAP PROTOCOL checkbox 5. Create a new partner profile in Transaction WE20 with the following attributes: - EMPLOYEE CENTRAL LOGICAL SYSTEM set to PARTNER TYPE LOGICAL SYSTEM - IDoc message type ODTF _OCTR set as outbound parameter - XML HTTP port created in step 4 assigned to outbound parameter RECEIVER PORT for message type ODT F_OC TR To enable the connection from SAP Cloud Platform Integration to SAP SuccessFactors Employee Central. deploy the SAP SuccessFactors user credential artifact in SAP Cloud Platform Integration web UI MANAGE SECURITY MATERIAL tool by navigating withinthe WEBUI • MENU • MONITOR • SECURITY MATERIAL. Click the ADD button, select USER CREDENTIALS, and set the following information: >> ARTIFACT NAME (e.g., SFAPI_USER) >> USER NAME )) PASSWORD >> COMPANY ID >> Select the SUCCESSFACTORS checkbox option
27
I
2
Overview of SAP Cloud Platform Integration Content by Deployment Model
Organization Data Integration Process Scenario
SAP predelivers two separate end-to-end integration processes for supporting organization data integration from SAP SuccessFactors Employee Central to SAP ERP. The first integration process transfers organization objects such as business unit, division, department, position, and job from SAP SuccessFactors Employee Central to form the organization structure hierarchy in SAP ERP. The replication process begins with an extraction query using a SOAP web service call from SAP ERP to SAP Cloud Platform Integration. The extraction request is then sent using an OData query to SAP SuccessFactors Employee Central. The extracted organization data is then transformed, sent, and updated in the staging area of SAP ERP. The subsequent process is then scheduled in the background to run periodically to post organization data from the staging area into SAP Organizational Management (OM) data. The second integration process transfers employee job information assignments from SAP SuccessFactors Employee Central to SAP ERP as employee organization management data. However, this process has a dependency on both employee data replication and organization data replication, because the process forms the relationship between employee data and organization data as an employee organizational assignment in SAP ERP. The replication process begins with an extraction query using a CompoundAPI web service call from SAP Cloud Platform Integration to SAP SuccessFactors Employee Central to extract organization assignment data. The extracted data is then transformed, sent, and updated in the staging area of SAP ERP. The subsequent process is then scheduled in the background to run periodically to post the organization assignment data from the staging area into SAP OM data.
Configurations and Parameter Settings To begin the configuration, select SUCCESSFACTORS EMPLOYEE CENTRAL TO ERP ORGANIZATIONAL DATA from the integration package list. There are
28
I
2
Overview of SAP Cloud Platform Int egration Content by Deployment Model
two artifacts delivered as standard for supporting the organization data integration scenario: )) EMPLOYEE CENTRAL TO SAP ERP GENERIC OBJECT REPLICATION (TYPE: PROCESS INTEGRATION) >> EMPLOYEE CENTRAL TO SAP ERP ORGANIZATIONAL ASSIGNMENTS REPLICATION (TYPE: PROCESS INTEGRATION) Let's start with the parameter settings and configuration of SAP SuccessFactors Employee Central to SAP ERP generic object iFlow for enterprise structure job, position, department, division, business unit, and custom obj ect replication process. Select CONFIGURE from the ACTION dropdown to enter iFlow configuration mode. Refer to the configuration and parameters below to complete the configuration.
Configuration for SAP Successfactors Employee Central to SAP ERP Organizational Data Replication Sender and Receiver Settings To set up the sender settings, configure the following: >> SENDER: Default value SAP_ERP_OUT >> ADAPTER Type: Default value SOAP >> ADDRESS: Default value !EC_to_ERP_Generic_Object_Query >> AUTHORIZATION: Select option USER ROLE or CLIENT CERTIFICATE >> CERTIFICATE BROWSE/SUBJECT DN and ISSUER DN: Import client certificate from sender system To set up of Receiver settings (query to SuccessFactors Employee Central), configure the following: >> RECEIVER: Select value SFSF_EC from the dropdown box >> ADAPTER TYPE: Default value SUCCESSFACTORS >> ADDRESS: Enter the SAP SuccessFactors Employee Central API base URL here, for example: https://apisalesdemo4.successfactors.com >> AUTHENTICATION TYPE: Default value BASIC AUTHENTICATION
29
I
2
Overview of SAP Cloud Platform Integration Content by Deployment Model
>> CERTIFICATE NAME: The name of the SAP SuccessFactors credential artifact you've deployed To set up the receiver settings (for notification to SAP ERP), configure the following: >> RECEIVER: Select valueSAP_ERP_NOTIFICATION_IN from the dropdown box. >> ADAPTER TYPE: Default value SOAP. >> ADDRESS: Enter the SAP ERP notification API URL here. To learn how to get the exact URL, see the section "Enabling SAP Cloud Platform Integration to SAP ERP Connection". >> ALLOW CHUNKING: Selected by default. Delselect this checkbox if your SAP ERP installation doesn't support HTTP chunking. >> PROXY TYPE: Select INTERNET for connecting SAP Cloud Platform Integration to SAP ERP through SAP Web Dispatcher; otherwise, select ONPREMISE if your SAP ERP system is accessed through SAP Cloud Platform cloud connector. >> AUTHENTICATION TYPE: Select BASIC AUTHENTICATION OR CERTIFICATEBASED AUTHENTICATION. See the box ahead for further details on the receiver authentication type options. >> CREDENTIAL NAME: Enter the name of the SAP ERP credential artifact you've deployed if you're using basic authentication. >> PRIVATE l(EY ALIAS: Enter the certificate private key alias here if you're using certificate-based authentication. Receiver Authentication Type Options The SAP Cloud Plat form Int egration iFlow supports either basic authenticat ion or cl ient certificate aut henticat ion to authent icate t he tenant it self against the target system for outbound connection from SAP Cloud Platform Integration t o t he receiver system: .,.. Basic authentication uses a user name and password to authenticate itself against the receiver system.
30
I
2
Overview of SAP Cloud Platform Integration Content by Deployment Model
"' Client certificate authentication uses the sender's digital client certificate to authenticate itself against the receiver system. For more comprehensive information about SAP Cloud Platform Integration authentication and authorizat ion strategies, refer to the relevant topic at https://cloud integration. hana.ondemand .com/Pl/help .
To set up the receiver settings (for organization object replication to SAP ERP) , configure the following: >> RECEIVER: Select value SAP_ERP_IN from the dropdown box. >> ADAPTER TYPE: Default value SOAP. >> ADDRESS: Enter the SAP ERP notification API URL here. To learn how to get the exact URL, see the section "Enabling SAP Cloud Platform Integration to SAP ERP Connection". >> ALLOW CHUNKING: Selected by default. Deselect this checkbox if your SAP ERP installation doesn't support HTTP chunking. >> PROXY TYPE: Select INTERNET for connecting SAP Cloud Platform Integration to SAP ERP through SAP Web Dispatcher; otherwise, select ONPREMISE if your SAP ERP system is accessed through SAP Cloud Platform cloud connector. >> AUTHENTICATION TYPE: Select BASIC AUTHENTICATION or CERTIFICATEBASED AUTHENTICATION. >> CREDENTIAL NAME: Enter the name of the SAP ERP credential artifact you've deployed if you're using basic authentication. >> PRIVATE I> ENABLE_PAYLOAD_LOGGING: Enter "TRUE" to keep the complete message payload containing all the data transferred in the SAP Cloud Platform Integration message processing log. This feature is useful for issue analysis and troubleshooting purposes. Otherwise, enter "FALSE".
31
I
2
Overview of SAP Cloud Platform Integrat ion Content by Deployment Model
Once the preceding configuration is completed, you can deploy the EMPLOYEE CENTRAL TO ERP GENERIC OBJECT iFlow into the SAP Cloud Platform Integration runtime node by clicking the DEPLOY button. Next, let's set up the parameter settings and configuration of the EMPLOYEE CENTRAL TO ERP ORGANIZATION ASSIGNMENT iFlow. Select CONFIGURE from the ACTION dropdown to enter iFlow configuration mode. Refer to the configuration and parameters listed below to complete the configuration for the SAP Successfactors Employee Central to SAP ERP Organizational Assignments Replication Receiver settings and Integration Connections.
Configuration for SAP SuccessFactors Employee Central to SAP ERP Organizational Assignments Replication Timer Settings Here, you can configt1re the iFlow scheduler to trigger the EMPLOYEE CENTRAL TO ERP ORGANIZATIONAL ASSIGNMENTS replication process. You can set the process to RUN ONCE, SCHEDULE ON DAY, or SCHEDULE TO RECUR depending on your requirements.
Configuration for SAP SuccessFactors Employee Central to SAP ERP Organizational Assignments Replication Receiver Settings Set up the receiver settings (query to SAP SuccessFactors Employee Central) as follows: >> RECEIVER: Default value SFSF_EC. >> ADAPTER TYPE: Default value SUCCESSFACTORS. >> ADDRESS: Enter the SAP Successfactors Employee Central API base URL here, for example: https://apisalesdemo4.successfactors.com. >> PAGE SIZE: Default 400. This is the web service query paging parameter. You can set the total number of employees to be queried for each web service call. >> AUTHENTICATION TYPE: Default value BASIC AUTHENTICATION.
32
I
2
Overview of SAP Cloud Platform Integration Content by Deployment Model
>> CERTIFICATE NAME: Enter the name of the SAP SuccessFactors credential artifact you've deployed. Set up the receiver settings (for organization assignment replication to SAP ERP) as fo llows: >> RECEIVER: Default value SAP_ERP. >> ADAPTER TYPE: Default value SOAP. >> ADDRESS: Enter the SAP ERP notification API URL here which can be retrieved via SAP ERP SOAMANAGER. To learn how to get the exact URL, see the section "Enabling SAP Cloud Platform Integration to SAP ERP Connection". >> ALLOW CHUNKING: Selected by default. Deselect if your SAP ERP installation doesn't support HTTP chunking. >> PROXY TYPE: Select INTERNET for connecting SAP Cloud Platform Integration to SAP ERP through SAP Web Dispatcher; otherwise, select ONPREMISE if your SAP ERP system is accessed through SAP Cloud Platform cloud connector. >> AUTHENTICATION TYPE: Select BASIC AUTHENTICATION or CERTIFICATEBASED AUTHENTICATION. >> CREDENTIAL NAME: Enter the name of the SAP ERP credential artifact you've deployed if you're using basic authentication. >> PRIVATE KEY ANALYSIS: Enter the certificate private key alias here if you're using certificate-based authentication. The following standard parameter values can be used in the PARAMETERS tab: >> COMPANIES Enter the legal entity of SAP SuccessFactors Employee Central here if you want to transfer data based on an employee's associated company code. You can enter several company codes separated by commas.
33
I
2
Overview of SAP Cloud Platform Integration Content by Deployment Model
>> INITIATE_FULL_LOAD - Enter "TRUE" to trigger a complete replication of all organizational assignments that were changed after the full transmission start date (FTSD). - Enter "FALSE" to trigger delta replication of organizational assignment that was changed after the FTSD. - Refer to the FTSD parameter for more details about the FTSD processing logic. )) COUNTRIES
- Enter the country code of SAP SuccessFactors Employee Central here if you want to transfer data based on an employee's associated country code. - Enter several country codes separated by commas. - If you're using the country code data transfer restriction feature, make sure the same country code restriction is used in the employee data replication process to avoid any inconsistences or errors in updates to SAP ERP between employee data and employee organization assignment data.
>> ENABLE_ASSOCIATED_EMPLOYEE_INFORMATION - Enter "TRUE" to transfer information about all associated employees entered in the employee's job information in SAP SuccessFactors Employee Central, including the employee's supervisor/manager. Otherwise, enter "FALSE".
>> IGNORE_JOB_INFO_EMPLSTATUSES - Enter the employee's employment status here if you want to prevent a specific employment status from being replicated to SAP ERP. Otherwise, leave it blank to replicate all types of employment status. - Enter several statues separated by commas.
34
I
2
Overview of SAP Cloud Platform Integration Content by Deployment Model
>> EMPLOYEE_CLASSES - Enter the employee class of SAP SuccessFactors Employee Central here if you want to transfer data based on an employee's associated employee classes. - Use comma separators to enter several employee classes. >> CONTINGENT_WORI> ENABLE_TIME_DEPENDENT_EMPLOYEE_SELECTION Enter "TRUE" to enable the FTSD for companies, countries, and employee class filters. Otherwise, enter "FALSE". >> ENABLE_NOTIFICATION Enter "TRUE" to enable notifications sent to SAP SuccessFactors Employee Central for each confirmation message sent by SAP ERP about the employee organization update status. Otherwise, enter "FALSE" to disable notifications. >> REPLICATION_TARGET_SYSTEM Enter the external code of the generic object instance for the replication target system in SAP SuccessFactors Employee Central that you've created for employee master data replication from SAP SuccessFactors Employee Central. >> FULL_TRANSMISSION_START_DATE Enter the date from which employee organizational assignment replication from SAP SuccessFactors Employee Central to the SAP ERP HCM system is to begin.
35
I
2
Overview of SAP Cloud Platform Int egration Content by Deployment Model
>> FULL_TRANSMISSION_START_DATE Enter the date from which employee organizational assignment replication from SAP SuccessFactors Employee Central to the SAP ERP HCM system is to begin. FTSD is the key date used to determine employee organizational assignment record extraction from SAP SuccessFactors Employee Central. FTSD record extraction logic is based on the following criteria: - FTSDs fall within the employee organizational assignment period. - Any employee organizational assignment records that has an effective date after the FTSD.
>> ENABLE_PAYLOAD_LOGGING Enter "TRUE" to keep the complete message payload containing all the data transferred in the SAP Cloud Platform Integration message processing log. This feature is useful for issue analysis and troubleshooting purposes. Otherwise, enter "FALSE".
>> USE_EXTERNAL_COST_CENTER_ID Enter "TRUE" to use the external cost center ID from the SAP ERP HCM system for the mapping. Enter "FALSE" if you don't want the cost center ID from SAP ERP HCM to be used. Once the preceding configuration is completed, you can deploy the EMPLOYEE CENTRAL TO ERP ORGANIZATIONAL ASSIGNMENT iFlow in the SAP Cloud Platform Integration runtime node by clicking the DEPLOY button. Enabling SAP ERP to SAP Cloud Platform Integration Connection
There are three types of communication configuration to set up for using the EMPLOYEE CENTRAL TO ERP GENERIC OBJECT replication and EMPLOYEE CENTRAL TO ORGANIZATIONAL ASSIGNMENT iFlows, involving connections from SAP ERP to SAP Cloud Platform Integration, from SAP Cloud Platform Integration to SAP ERP, and from SAP Cloud Platform Integration to SAP SuccessFactors Employee Central.
I
2
Overview of SAP Cloud Platform Int egration Content by Deployment Model
To enable the connection from SAP ERP to SAP Cloud Platform Integration, proceed as follows: 1. Go to SAP ERP WEB SERVICE CONFIGURATION via Transaction SOAMANAGER. 2. Search for consumer proxy CO_SFIOMX_ORG_OBJECT_REPL_QRY. 3. Create a new logical port by selecting the MANUAL CONFIGURATION button. 4. Select the USER ID/PASSWORD option and enter the communication user ID and password for SAP Cloud Platform Integration. 5. Configure the transport settings with the following parameters: - URL ACCESS PATH: SAP SuccessFactors Employee Central or SAP ERP generic object iFlow sender address , with prefix !cxf!.
- URL PROTOCOL INFORMATION: HTTPS. - COMPUTER NAME OF ACCESS URL: Enter the URL of the runtime node of your SAP Cloud Platform Integration environment. - PORT NUMBER OF ACCESS URL: Port number of your SAP Cloud Platform Integration installation. - LOGON LANGUAGE: LANGUAGE OF USER CONTEXT. - NAME OF PROXY HOST: If you have a forward proxy server set up in your network infrastructure, enter the proxy host; otherwise, leave it blank. - TRANSPORT BINDING TYPE: SOAP 1.1. - MAKE LOCAL CALL: No CALL IN LOCAL SYSTEM. - WSDL STYLE: DOCUMENT STYLE. - OPTIMIZED XML TRANSFER: NONE. - COMPRESS HTTP MESSAGE: INACTIVE. - COMPRESS RESPONSE: TRUE.
37
I
2
Overview of SAP Cloud Platform Integration Content by Deployment Model
6. Configure the MESSAGING parameters as follows:
- RELIABLE MESSAGING PROTOCOL: SAP RM - MESSAGE ID PROTOCOL: SUPPRESS ID TRANSFER - DATA TRANSFER SCOPE: ENHANCED DATA TRANSFER - TRANSFER PROTOCOL: TRANSFER VIA SOAP HEADER 7. Save the SAP Web Service Configuration and set it as the default logical port by selecting the LOG. PORT DEFAULT button. Note
This is only applicable for the lication scenario.
EMPLOYEE CENTRAL TO ERP GENERIC OBJECT
rep-
Enabling SAP Cloud Platform Integration to SAP ERP Connection
You've now completed the first communication set up steps. Next, we'll enable the connection from SAP Cloud Platform Integration to SAP ERP as follows: 1. Go
to SIMPLIFIED WEB SERVICE CONFIGURATION in Transaction SOAMANAGER in your SAP ERP system.
2. Search for the following service definitions, and select the USER ID/ PASSWORD option and save for each service definition: - ORGANISATIONALOBJECTREPLICATION: Replicate organization objects to SAP ERP - ORGOBJREPLNOTIFICATION: Send notifications to SAP ERP - EMPLOYEEORGASSIGNMREPLREQUEST: Replicate organization assignments to SAP ERP 3. For each service definition, select SHOW DETAILS to find the access URL in the CONFIGURATION DETAILS section of the DETAILS popup screen. Note the WSDL URLs with WS Policy; these WSDL URLs must be entered into the relevant receiver addresses of the iFlow configurations
I
2
Overview of SAP Cloud Platform Integration Content by Deployment Model
mentioned in the "Employee Master Data and Organization Management Integration Scenario Overview" section. Please enter the URL into the Address field for the Receiver settings for section above. For setting up the third type of communication to enable the connection from SAP Cloud Platform Integration to SAP SuccessFactors Employee Central, refer back to the "Connections" section in the section "Cost Center Integration Scenario Overview" as the same connection set up can be followed.
Employee Data Integration Process Scenario The integration of employee data between SAP ERP and SAP SuccessFactors Employee Central replicates basic employee information from SAP SuccessFactors Employee Central to SAP ERP. This integration enables the execution of business processes in the connected SAP ERP system. This integration is performed periodically via a web service. The replication begins by triggering the extraction request from SAP Cloud Platform Integration to SAP SuccessFactors Employee Central using a CompoundAPI web service call. The extracted employee master data is then transformed and sent via a SOAP web service to update employee data records directly in SAP ERP. The setup for the employee data for the core hybrid deployment model is the same as the Full Cloud Deployment integration settings discussed in this section; the only difference is the type of employee data replicated in SAP ERP.
Configurations and Parameter Settings To begin with the configuration, select SUCCESSFACTORS EMPLOYEE CENTRAL TO ERP EMPLOYEE DATA from the integration package list. There is one artifact delivered standard to support the employee data integration.
39
I
2
Overview of SAP Cloud Platform Integration Content by Deployment Model
SAP Successfactors Employee Central to SAP ERP Employee Data Let's begin with the parameter settings and configuration of the SAP SuccessFactors Employee Central to SAP ERP employee data iFlow. Select CONFIGURE from the ACTION button to enter iFlow configuration mode. Refer to the configuration and parameters listed below to complete the configuration. Configuration for SAP Successfactors Employee Central to SAP ERP Employee Data Replication Timer Settings Here, you can configure the iFlow scheduler to trigger the SAP SuccessFactors Employee Central to SAP ERP employee data replication process. You can configure the process to RUN ONCE, SCHEDULE ON DAY, or SCHEDULE TO RECUR depending on your requirements. Note
The objective of the employee organization assignments replication process is to create an association between employee data and organization struct ure objects that w ill form the organization assignment s in SAP Organizational Management. Hence, this process has dependencies on both the employee data replication process and t he organization data replication process. To ensu re the replication processes update correctly in SAP ERP, we recommend schedu ling t he replication processes in the following sequence: 1. Either employee data integration replication or organization data replication 2. Either employee data integration replication or organization data replication 3. Employee organization assignments replication
Configuration for SAP Employee Data Replication Receiver Settings Next, set up the receiver settings for queries to SAP SuccessFactors Employee Central as follows: >> RECEIVER: Default value EC_CE_APl_QUERY. >> ADAPTER TYPE: Default value SUCCESSFACTORS.
40
I
2
Overview of SAP Cloud Platform Integration Content by Deployment Model
>> ADDRESS: Enter the SAP Successfactors Employee Central API base URL here, for example: https://apisalesdemo4.successfactors.com. >> ADDRESS SUFFIX: Default value /SFAPI/v1/SOAP. >> PAGE SIZE: Default 400; this is the web service query paging parameter. You can set the total number of employees to be queried at each web service call. >> AUTHENTICATION TYPE: Default value BASIC AUTHENTICATION. >> CERTIFICATE NAME: Enter the name of the SAP SuccessFactors credential artifact you've deployed. Now, set up the receiver settings for employee data replication to SAP ERP as follows: >> RECEIVER: Default value SAP_ERP. >> ADAPTER TYPE: Default value SOAP. >> ADDRESS: Enter the SAP ERP notification API URL here which can be retrieved via SAP ERP SOAMANAGER. To learn how to get the exact URL, see the "Connections" section. >> ALLOW CHUNKING: Selected by default; deselect it if your SAP ERP installation doesn't support HITP chunking. >> PROXY TYPE: Select INTERNET for connecting SAP Cloud Platform Integration to SAP ERP through SAP Web Dispatcher; otherwise, select ONPREMISE if your SAP ERP system is accessed through SAP Cloud Platform cloud connector. >> AUTHENTICATION TYPE: BASIC AUTHENTICATION or CERTIFICATE-BASED AUTHENTICATION. >> CREDENTIAL NAME: Enter the name of the SAP ERP credential artifact you've deployed if you're using basic authentication. >> PRIVATE I
41
I
2
Overview of SAP Cloud Platform Int egration Content by Deployment Model
The following standard parameter values can be used in the PARAMETERS tab: >> MULTIPLE_JOB_EVENTS Enter "TRUE" to replicate employee data with multiple job events within the same day. >> EMPLOYEE_CLASSES Enter the employee class of SAP SuccessFactors Employee Central here if you want to transfer the data based on an employee's associated employee classes. Enter several employee classes with comma separators. >> REPLICATION_TARGET_SYSTEM Enter the external code of the generic object instance for the replication target system in SAP SuccessFactors Employee Central that you 've created for employee master data replication. >> FULL_TRANSMISSION_START_DATE Enter the date from which the employee data replication from SAP SuccessFactors Employee Central to the SAP ERP HCM system is to begin. FTSD is the key date used to determine the employee data record extraction from SAP SuccessFactors Employee Central. FTSD record extraction logic is based on the following criteria: - FTSDs fall within the employee data period. - Any employee data records that has an effective date after the FTSD. >> PERSON_ID _EXTERNAL Enter the SAP SuccessFactors employee ID restrict the employee data replication for testing purpose. Enter several employee IDs using comma separators. >> ENABLE_PAYLOAD_LOGGING Enter "TRUE" to keep the complete message payload containing all the data transferred in the SAP Cloud Platform Integration message processing log. This feature is useful for issue analysis and troubleshooting purposes. Otherwise, enter "FALSE".
I
2
Overview of SAP Cloud Platform Integration Content by Deployment Model
>> COMPANIES Enter the legal entity of SAP SuccessFactors Employee Central here if you want to transfer data based on an employee's associated company code. Enter several company codes with comma separators. >> COUNTRIES Enter the country code of SAP SuccessFactors Employee Central here if you want to transfer data based on an employee's associated country code. Enter several country codes with comma separators. If you're using the country code data transfer restriction feature, make sure the same country code restriction is used in the employee data replication process to avoid any inconsistences or errors in updates to SAP ERP between employee data and employee organization assignments data. >> USE_EXTERNAL_COST_CENTER Enter "TRUE" to use the external cost center ID from the SAP ERP HCM system for the mapping. Enter "FALSE" if you don't want the cost center IDs from SAP ERP HCM to be used. >> CONTINGENT_WORKERS Using this parameter, you can indicate whether you want to replicate organizational assignments of employees or contingent workers. - Enter "1" to exclude contingent workers from replication. - Enter "2" to replicate only contingent workers. - Enter "3" to replicate both employees and contingent workers. >> ENABLE_TIME_D EPENDENT_EMPLOYEE_SELECTI ON Enter "TRUE" to enable the FTSD for companies, countries, and employee class filters. Otherwise, enter "FALSE". >> ENABLE_NOTIFICATION Enter "TRUE" to enable notifications to be sent to SAP SuccessFactors Employee Central for each confirmation message sent by SAP ERP to for the employee organization update status. Enter "FALSE" to disable notifications.
43
I
2
Overview of SAP Cloud Platform Integration Content by Deployment Model
>> USER_SET_LAST_MODIFIED_DATE_TIME This parameter allows you to reset the last modified date back in time by entering the date and time in YYYY-MM-DDThh:mm:ssZ UTC format here. In addition, you must delete the PV_LAST_MODIFIED_DATE global variable entry from the Data Store Viewer. Once the preceding configuration is completed, you can deploy the EMPLOYEE CENTRAL TO ERP EMPLOYEE DATA iFlow into the SAP Cloud Platform Integration runtime node by clicking the DEPLOY button. Connections
There are two types of communication configuration to set up for the EMPLOYEE CENTRAL TO ERP EMPLOYEE DATA replication iFlow: connection from SAP Cloud Platform Integration to SAP ERP and connection from SAP Cloud Platform Integration to SAP Successfactors Employee Central. To enable the connection from SAP Cloud Platform Integration to SAP ERP, proceed as fallows: 1. Go to SIMPLIFIED WEB SERVICE CONFIGURATION in Transaction SOA-
MANAG ER. 2. Search for the following service definition, and select the USER ID/PASS-
WORD option and save: - Emp 1oyeeMas t erDataBundl eRep 1i cation Request_! n: Replicate employee
data to SAP ERP 3. Select SHOW DETAILS to find the access URL in the CONFIGURATION DETAILS section of the DETAILS popup screen. Note the WSDL URLs with WS Policy; these WSDL URLs must be entered into the relevant receiver addresses of the iFlow configuration as mentioned in the section "Configuration for SAP Employee Data Replication Receiver Settings". Please enter the URL into the ADDRESS field for the RECEIVER settings for section above.
44
I
2
Overview of SAP Cloud Platform Integration Content by Deployment Model
Note
The host of the URL listed is on ly accessible internally in your local network. It isn't accessible externally from the Internet. Make sure to replace the host name and port w ith your SAP Web Dispacher- assigned public host name and port that's accessible from the Internet when setting up the receiver address of the relevant iFlow.
For setting up the third type of communication to enable the connection from SAP Cloud Platform Integration to SAP SuccessFactors Employee Central, refer back to the Cost Center Integration Scenario Overview. You can follow the same connection setup. Send Confirmation from SAP ERP to SAP SuccessFactors Employee Central Overview
The integration of confirmation responses from SAP ERP to SAP SuccessFactors Employee Central updates the SAP ERP processing status of employee data and employee organization assignments to SAP SuccessFactors Employee Central. The confirmation SOAP web service message is triggered immediately after the employee data processing or employee organization assignment processing finishes in SAP ERP. Configurations and Parameter settings
To begin, select ERP TO SUCCESSFACTORS EMPLOYEE CENTRAL CONFIRMATION from the integration package list. There is one artifact delivered standard to support the confirmation integration: ERP TO EMPLOYEE CENTRAL CONFIRMATION (TYPE: PROCESS INTEGRATION). Let's begin with the parameter settings and configuration of the ERP TO EMPLOYEE CENTRAL CONFIRMATION iFlow. Select CONFIGURE from the ACTION dropdown to enter iFlow configuration mode. Refer to the configuration and parameters listed below to complete the configuration.
45
I
2
Overview of SAP Cloud Platform Integration Content by Deployment Model
Configuration for SAP Employee Data Confirmation Receiver Settings To set up the receiver settings for sending confirmation to SAP SuccessFactors Employee Central, set the following: >> RECEIVER: Default value SFSF _EC. >> ADAPTER TYPE: Default value HTTP. >> ADDRESS: Enter the SAP SuccessFactors Employee Central API base URL here, for example: https://apisalesdemo4.successfactors.com . >> AUTHENTICATION TYPE: Default value BASIC AUTHENTICATION. >> CREDENTIAL NAME: Enter the name of the SAP SuccessFactors credential artifact you've deployed. The following standard parameter values can be used in the PARAMETERS tab: >> ENABLE_PAYLOAD_LOGGING: Enter "TRUE" to keep the complete message payload containing all the data transferred in the SAP Cloud Platform Integration message processing log. This feature is useful for issue analysis and troubleshooting purposes. Otherwise, enter "FALSE". Once the preceding configuration is completed, you can deploy the ERP TO EMPLOYEE CENTRAL CONFIRMATION iFlow into the SAP Cloud Platform Integration runtime node by clicking the DEPLOY button.
Connections There are two types of communication configuration to be setup for using the ERP TO EMPLOYEE CENTRAL CONFIRMATION replication iFlow: connection from SAP Cloud Platform Integration to SAP ERP and connection from SAP Cloud Platform Integration to SAP SuccessFactors Employee Central. To enable the connection from SAP Cloud Platform Integration to SAP ERP, proceed as follows: 1. Go to WEB SERVICE CONFIGURATION in Transaction SOAMANAGER.
I
2
Overview of SAP Cloud Platform Integration Content by Deployment Model
2. Search for the following service definition and select it: - EmployeeMasterDataRep l icat i onCo nfir mat ion_Out : Replicate con-
firmation data to SAP SuccessFactors Employee Central 3. In the CONFIGURATION section, create a new logical port by using manual configuration and set it as the default logical port. 4. In the MANUAL CONFIGURATION section, proceed as follows: - Fill in the SAP Cloud Platform Integration communication username and password. - Fill in the SAP Cloud Platform Integration runtime host URL in COMPUTER NAME OF ACCESS URL. - Enter the confirmation message iFlow sender address in URL ACCESS PATH -for example: /cxf/ERP_to _EC_EmployeeMasterDataReplication-
Con.firmation. - Select the HTTPS and SAP Cloud Platform Integration default port 443 options. 5. Once you're done, save and activate the configuration. Note
To make sure the configuration is configu red correctly or to test the outbound confirmation message connectivity from SAP ERP to SAP Cloud Platform Integration, click PING WEB SERVICE under t he logical port you have created. You should expect error message HTIP Error 405 if the connectivity is tested successfully.
For setting up the third type of communication to enable the connection from SAP Cloud Platform Integration to SAP SuccessFactors Employee Central, refer back to the Cost Center Integration Scenario Overview. You can follow the same connection setup. Running the Replication Process
Once all the integration scenarios have been designed and setup completed, execution of the replication processes for all three integration
47
I
2
Overview of SAP Cloud Platform Integration Content by Deployment Model
scenarios can now be performed. Each integration scenario requires a different execution process, as discussed in the following subsections. Cost Center Integration
There are two ways to run the cost center replication from SAP ERP to SAP SuccessFactors Employee Central: 1. Initial
cost center replication using one-time manual program execution in SAP ERP.
To manually execute the replication, go to Transaction SA38 to execute program ODTF_REPL_CC. Fill in the necessary details based on your requirements and select the target logical system where you have created the logical system set up during your configuration setup earlier in the Cost Center Integration Scenario Overview under the "Connections" section. Run the report to start replication. 2. Delta cost center replication through background scheduled recurrence job
in SAP ERP. The same program ODTF_REPL_CC with the IDoc change pointers program is used to facilitate the delta replication process. To set up the delta replication job to run in the background, first select the USE VARIANT FOR DELTA REPLICATION USING CHANGE POINTERS checkbox in ODTF_REPL_CC and specify the replication criteria according to your needs, then save it as program variant. Complete the scheduling process by creating a background job in Transaction SM36 using program RBDMIDOC (Creating !Doc Type from Change Pointers), with IDoc message type ODTF _CCTR. Organization Data Integration: SAP Employee Central to SAP ERP Generic Object
The organization data replication comes with two different iFlows, and each has a different trigger point for data replication: 1. EMPLOYEE CENTRAL TO ERP GENERIC OBJECT
The process of organization object replication is triggered from SAP
I
2
Overview of SAP Cloud Platform Integrat ion Content by Deployment Model
ERP using program RH_SFIOM_ORG_OBJ_REPL_QUERY to send a query to replicate organizational objects from SAP SuccessFactors Employee Central to SAP ERP in a staging area. 2. Program RH_SFIOM_PROC_ORG_STRUC_RPRQ
This program can be executed to post the organizational objects from the staging area into SAP ERP HCM Organizational Management (OM) tables. In the program selection screen, you can restrict the object types to be read to specific organizational object types and post to database tables. The same programs can be used for either manual execution or background scheduling jobs via Transaction SM36. Note To avoid data locking errors during the creation of the organ izational objects for business unit, division, and department using the SAP OM creation program name RH _SF IOM_PROC_ORG_STRUC_RPRQ, the recommendation is to execute the creation of the three organization object types using the following sequence starting with the business unit updates, then division updates, and t hen department updates. Run each organization object type one at a time .
Organization Data Integration: SAP SuccessFactors Employee Central to Organizational Assignment
The process of organization assignment replication is triggered from SAP Cloud Platform Integration through the timer schedule set in the iFlow configuration settings. The request query is sent to replicate organizational objects from SAP SuccessFactors Employee Central to the SAP ERP staging area. Like organizational object replication, the second program, RH_SFIOM_ PROC_EE_ORG_ASS_RPRQ, will have to execute to post the organizational objects from the staging area into SAP ERP HCM organizational management tables. The same program can be used for either manual execution or background scheduling jobs via Transaction SM36.
49
I
2
Overview of SAP Cloud Platform Integrat ion Content by Deployment Model
Employee Data Integration
The employee data replication process is triggered from its relevant iFlow timer in SAP Cloud Platform Integration. The request query is sent to replicate employee data from SAP SuccessFactors Employee Central to update SAP ERP HCM personnel administration infotypes directly. Monitoring the Integration Process
Monitoring the integration processes is important to ensure replications are successful; if there are issues, there are several ways to investigate them. We'll discuss the monitoring transactions for each integration scenario in the following subsections. Cost Center Integration
The monitoring processes for cost center integration are as follows:
>> IDoc monitoring using Transaction WE02 in SAP ERP Fill in message type ODTF _CCTR in the selection screen and execute it to read the relevant cost center !Docs. On the OUTBOUND !Docs list, make sure all the cost center !Docs have the following status: 30 !Doc SENT TO SAP SYSTEM OR EXTERNAL PROGRAM. Otherwise, analyze the error messages listed in the status records.
>> SAP Cloud Platform Integration message monitoring Go to WEBUI. MENU . MONITOR. In the MONITOR OVERVIEW page, look for any failed cost center messages and select one to enter the MESSAGES list. Analyze the error message in the MESSAGE PROCESSING LOG. If PAYLOAD ENABLE is turned on, you should be able to retrieve the cost center content XML from the MPL attachment. >> SAP SuccessFactors Employee Central OData API audit log Go to ADMIN CENTER . COMPANY SETTINGS . ODATA API AUDIT LOG. Look for ODATA API CALL ENTITY FOCosTCENTER. Analyze the error messages if the FOCostCenter log entries have a FAILED status.
50
I
2
Overview of SAP Cloud Platform Integration Content by Deployment Model
Organization Data Integration
The monitoring processes for organization data integration are as follows:
>> SAP ERP programs/transactions: - Transaction SXMB_MONI: Monitor incoming SOAP messages for both organization objects replication and organization assignment replication. - Transaction SLG1: Monitor the SAP ERP HCM OM objects updates from staging area. - Transaction SFIOM_VIEW_ORG_REQS: Monitor replication requests for organizational objects in the staging area. - Transaction SF/OM_VIEW_REQUESTS: Monitor replication requests for organizational assignment in the staging area.
>> SAP Cloud Platform Integration message monitoring Go to WEBUI . MENU . MONITOR. On the MONITOR OVERVIEW page, look for any failed cost center messages and select one to enter the MESSAGES list. Analyze the error message in the MESSAGE PROCESSING LOG. If PAYLOAD ENABLE is turned on, you should be able to retrieve the organization data content XML from the MPL attachment. >> SAP SuccessFactors Employee Central OData API audit log Go to ADMIN CENTER . COMPANY SETTINGS . ODATA API AUDIT LOG. Look for ODATA API CALL ENTITY FOCosTCENTER. Analyze the error messages if the FOCostCenter log entries have a FAILED status. Employee Data Integration
The monitoring processes for employee data integration are as follows:
>> SAP ERP programs/transactions: - Transaction SXMB_MONI: Monitor incoming SOAP messages for employee data replication. - Transaction SLG1, with PAOC_SFI_PA as input.field object: Monitor the employee data replication updates error reasons in case of employee data update failure. 51
I
2
Overview of SAP Cloud Platform Integration Content by Deployment Model
>> SAP Cloud Platform Integration message monitoring Go to WEBUI . MENU . MONITOR. On the MONITOR OVERVIEW page, look for any failed cost center messages and select one to enter the MESSAGES list. Analyze the error message in the MESSAGE PROCESSING LOG. If PAYLOAD ENABLE is turned on, you should be able to retrieve the compound API result content XML from the MPL attachment. >> SAP SuccessFactors Employee Central OData API audit log Go to ADMIN CENTER . COMPANYSETTINGS. ODATA API AUDIT LOG. Look for ODATA API CALL ENTITY COMPOUNDEMPLOYEE. Analyze the error messages if the CornpoundErnp l oyee log entries have a FAILED status.
2.2
Side by Side Deployment Model
The side by side deployment model allows customers to deploy both SAP SuccessFactors Employee Central and SAP ERP systems at the same time, but with a consolidated entry point to manage employee data and reporting relationships for all employees via SAP SuccessFactors Employee Central. In this deployment model, core HR processes run in both the onpremise SAP ERP HCM system for a subset of employees and SAP SuccessFactors Employee Central for another subset of employees. Although employee data is kept in sync across the distributed system landscape, HR data changes are still updated in the system of the employee 's master record. There are two different HR data synchronization processes involved in the side by side deployment model, depending on where the core HR processes take place. If the core HR process is in SAP ERP, the HR data synchronization process will be initiated by SAP ERP to SAP SuccessFactors Employee Central. If the core HR process is in SAP SuccessFactors Employee Central, the HR data synchronization process will be initiated by the same to SAP ERP; this is the same integration strategy that we discussed earlier for the full cloud/core hybrid deployment models. In this section, we'll discuss integration scenarios in which HR core processing is based in SAP ERP, in which case HR data is required to transfer to SAP SuccessFactors Employee Central. There are standard integrations
52
I
2
Overview of SAP Cloud Platform Int egration Content by Deployment Model
delivered in SAP Cloud Platform Integration for those processes that still require HR data to be sent from SAP ERP to SAP SuccessFactors Employee Central. There are two standard-delivered integration scenarios for the side by side deployment model: 1. Employee master data integration 2. Organizational management data integration This section describes the necessary settings required in SAP Cloud Platform Integration to enable these integration scenarios .
Prerequisites
Before we begin, please ensure the following prerequisites have been met: >> Have access to the SAP Cloud tenant. >> Obtain the SAP Cloud tenant URL. >> Have access to SAP ERP, including access to Transaction SOAMANAGER (to activate the web services) and Transaction STRUST (Trust Manager; for SSL connection purposes). >> Set up a technical integration (API) user in SAP Successfactors Employee Central that SAP Cloud Platform Integration will use to communicate with SAP SuccessFactors Employee Central. >> Set permissions for the technical API user to use SOAP and OData APis. >> Enable APis in SAP Successfactors provisioning. >> Ensure all certificates are implemented. See Section 1.2 for setting up SSL inbound connections from the SAP ERP HCM on-premise system to SAP Cloud Platform Integration. Discovery and Copy
Let's look at the configuration and implementation of integration scenarios for the side by side deployment model. At the time of writing, there's
53
I
2
Overview of SAP Cloud Platform Integration Content by Deployment Model
one integration package offered by SAP as predelivered integration content for supporting the side by side deployment model: the ERP TO SucCESSFACTORS EMPLOYEE CENTRAL EMPLOYEE AND ORGANIZATIONAL DATA integration package. This package supports the employee data and organizational management data integration scenario. To start the SAP Cloud Platform Integration configuration, copy the integration package from the SAP Cloud Platform Integration DISCOVERY page to your design workspace. Design
You should have all the relevant integration packages saved in your design workspace now. To check, navigate to DESIGN from the menu. On the left pane, under OVERVIEW on the DESIGN page, you should be able to see all integration packages copied from DISCOVERY. With the relevant integration package in place, you're ready to begin the detailed configuration of the integration scenario, as discussed ahead. Employee Master Data and Organization Management Integration Scenario Overview
In this scenario, the employee subset data is core in on-premise SAP ERP HCM system where HR data is maintained in SAP ERP HCM system and the employee data is transferred to SAP SuccessFactors Employee Central for data synchronization. In technical integration design, employee data and organizational management data is transferred from SAP ERP via an OData web service to SAP Cloud Platform Integration; the employee data and organizational management data is then mapped and sent to SAP SuccessFactors Employee Central through OData web services. To begin, select ERP TO SUCCESSFACTORS EMPLOYEE CENTRAL EMPLOYEE AND ORGANIZATIONAL DATA from the integration package list. There are two artifacts delivered with this integration package:
54
I
2
Overview of SAP Cloud Platform Integration Content by Deployment Model
1. ERP TO EMPLOYEE CENTRAL EMPLOYEE l(EY DATA QUERY (TYPE: PROCESS
INTEGRATION) 2. ERP TO EMPLOYEE CENTRAL GENERIC ODATA UPSERT (TYPE: PROCESS INTEGRATION) Let's start with the first iflow configuration. Select CONFIGURE from the ACTION dropdown to enter iflow configuration mode. Refer to the configuration and parameters listed below to complete the standard configuration settings.
Configuration for SAP ERP to SAP SuccessFactors Employee Central Employee and Organizational Data Sender and Receiver Settings First, set up the sender settings: >> SENDER: Default value SAP_ERP >> ADAPTER TYPE: Default value SOAP >> ADDRESS: Default value /ERP _To_EC_EMPLOYEEl(EYDATAQUERY >> AUTHORIZATION: USER ROLE or CLIENT CERTIFICATE Now, set up the receiver settings: >> RECEIVER: Default value SFSF_EC. >> ADAPTER TYPE: Default value SUCCESSFACTORS. >> ADDRESS: Enter the SAP Successfactors SFAPI base URL here (see following note). >> CREDENTIAL NAME: Enter the name of the SAP Successfactors Employee Central credential artifact you've deployed. Note The SFAPI URL is based on the dat a center hosting your SAP SuccessFactors instance. Refer to SAP Help documentation to determine the correct base URL based on your SAP SuccessFactors data center. See http:// help.sap.com/saphelpiis_cloud4h r/EN/SF _H CMS_ OData_APl_User_en/.
55
I
2
Overview of SAP Cloud Platform Int egration Content by Deployment Model
For PARAMETER settings, navigate to ENABLE_PAYLOAD_LOGGING. Enter "TRUE" to turn on the integration data content logging during message processing. This will enable you to retrieve the payload or integration data content later for troubleshooting purposes. Otherwise, enter "FALSE". Once you've completed both the sender and receiver settings configuration, you can deploy the iFlow as seen in Figure 13. SAP ERP to SAP SuccessFactors Employee Central Generic OData Upsert
Let's explore the iFlow for EMPLOYEE CENTRAL GENERIC ODATA UPSERT, beginning with setting the configuration for the sender, receiver, and parameters. In the following sender fields, input the following values: >> SENDER: Default Value SAP_ERP >> ADAPTER TYPE: Default value SOAP >> ADDRESS: Default value /ERP_TO_EC_GENERICODATAUPSERT >> AUTHORIZATION: USER ROLE or CLIENT CERTIFICATE In the following receiver fields , input the following values: >> RECEIVER: Default value SFSF_EC >> ADAPTER TYPE: Default value HTTP >> CREDENTIAL NAME: Enter the name of the SAP SuccessFactors Employee Central credential artifact you've deployed. Navigate to the PARAMETER tab and input the following values: )) ENABLE_PAYLOAD_LOGGING Enter "TRUE" to turn on the integration data content logging during message processing. This will enable you to retrieve the payload or integration data content later for troubleshooting purposes. Otherwise, enter "FALSE".
I
2
Overview of SAP Cloud Platform Integration Content by Deployment Model
>> SFSF_EC_BASE_URL Enter the SAP SuccessFactors SFAPI base URL here. Once you have completed the configuration, you can deploy the iFlow as seen in Figure 13. Connections
There are two types of communication configuration to be set up for the EMPLOYEE DATA AND ORGANIZATION MANAGEMENT DATA iFlow: connection from SAP ERP to SAP Cloud Platform Integration and connection from SAP Cloud Platform Integration to SAP SuccessFactors. To enable the connection from SAP ERP to SAP Cloud Platform Integration, follow the configuration steps in the following subsections. Because there are two SAP Cloud Platform Integration iFlows delivered for supporting the EMPLOYEE DATA AND ORGANIZATIONAL MANAGEMENT DATA scenarios, there will be two service definitions to be configured and activated in SOAMANAGER. SAP Cloud Platform Integration
In the following configuration example, we will walkthrough only one of the service definition configurations; the two service definition configuration steps are similar, except for the SAP Cloud Platform Integration iFlow sender endpoint URL. However, to complete the full configuration, both service definitions are required. Proceed as follows: 1. Go to WEB SERVICE CONFIGURATION in Transaction SOAMANAGER. 2. Search for service definition CO_ ECPAO_GET_GEN ER IC_ODATA_U PS and
select it. This selects the EMPLOYEE AND ORGANIZATIONAL DATA ODATA UPSERT process. 3. In the CONFIGURATION section, create a new logical port by using manual configuration and set it as the default logical port.
57
I
2
Overview of SAP Cloud Platform Integrat ion Content by Deployment Model
4. In the MANUAL CONFIGURATION section, proceed as follows: - Fill in the SAP Cloud Platform Integration communication username and password. - Fill in the SAP Cloud Platform Integration runtime host URL in COMPUTER NAME OF ACCESS URL. - Enter the SAP SuccessFactors iFlow sender address in URL ACCESS PATH-for example: /cxfl ERP_to_EC_GenericODataUpsert. - Select the HTTPS and SAP Cloud Platform Integration default port 443 options. Once you're done, save and activate the configuration. Repeat the same configuration steps for the remaining service definition- CO_ECPAO_GE T_ EMPLOYEE_KEY_DATA. Note that the URL access path must match the sender address of the iFlow you 're configuring for the related service definition. To make sure you're configuring the correct URL access path, always refer to the related iFlow sender address in SAP Cloud Platform Integration. For example, you're now configuring URL access for ERP TO EMPLOYEE CENTRAL GENERIC ODATA UPSERT, so you should refer to the sender address of iFlow ERP TO EMPLOYEE CENTRAL GENERIC ODATA UPSERT. You should always add the SAP Cloud Platform Integration access path prefix /cxf! to your URL access path. To make sure the configuration is configured correctly or to test the outbound confirmation message connectivity from SAP ERP to SAP Cloud Platform Integration, click PING WEB SERVICE under the logical port you 've created. You should expect error message HTTP Error 405 if the connectivity is tested successfully. For setting up the third type of communication to enable the connection from SAP Cloud Platform Integration to SAP SuccessFactors Employee Central, refer back to the Cost Center Integration Scenario Overview. You can follow the same connection setup.
I
2
Overview of SAP Cloud Platform Int egration Content by Deployment Model
2.3
Talent Hybrid Deployment Model
The talent hybrid deployment model allows customers to manage their core HR data in SAP ERP HCM and deploy talent processes in the cloud using the SAP SuccessFactors Talent Management suite. There are standard integrations delivered in SAP Cloud Platform Integration for those processes that still require HR data to be sent back in SAP ERP HCM. There are seven standard delivered integration scenarios for the talent hybrid model: 1. Employee data integration 2. Compensation process integration 3. Recruiting process integration 4. Variable pay process integration 5. Equity planning process integration 6. Learning process integration 7. Onboarding integration This section describes the necessary settings required in SAP Cloud Platform Integration to enable these integration scenarios . Prerequisites
Before we begin, please ensure the following prerequisites have been met: >> Have access to the SAP Cloud tenant. >> Obtain the SAP Cloud tenant URL. >> Have access to SAP ERP, including access to Transaction SOAMANAGER (to activate the webservices) and Transaction STRUST (Trust Manager; for SSL connection purposes). >> Set up a technical integration (API) user in SAP SuccessFactors Employee Central that SAP Cloud Platform Integration will use to communicate with SAP SuccessFactors Employee Central.
59
I
2
Overview of SAP Cloud Platform Integration Content by Deployment Model
>> Set permissions for the technical API user to use SOAP and OData APis. >> Enable APis in SAP Successfactors provisioning. >> Ensure all certificates are implemented. See the section "SSL Inbound Connection from SAP ERP HCM On-Premise System to SAP Cloud Platform Integration" for setting up SSL inbound connections from the SAP ERP HCM on-premise system to SAP Cloud Platform Integration. >> Have access to the SAP SuccessFactors SFTP site for the Competency Library Learning integration process scenario. >> Install the latest integration add-ons for the talent hybrid model. Let's look at the configuration and the implementation of integration scenarios for talent hybrid cloud deployment model. At the time of writing, there are four main integration packages offered by SAP as pre-delivered integration content for supporting the talent hybrid model: 1. SuccessFactors HCM Suite Talent Management integration with SAP ERP (covering SAP HCM employee data, the compensation process, the recruiting process, the variable pay process, and the equity planning process integration) 2. SAP SuccessFactors LMS Curricula with SAP HCM Qualification SAP Successfactors HCM Suite Competency with SAP HCM Qualification 3. SAP SuccessFactors HCM Suite Onboarding with SAP ERP HCM Discovery and Copy
To start, copy each required integration package from the SAP Cloud Platform Integration DISCOVERY page to your design workspace as follows: 1. Select the COPY icon (see Figure 14) to copy the selected standard integration package to your workspace.
60
I
2
Overview of SAP Cloud Plat form Integrat ion Content by Deployment Model
SuccessFactors HCM Suite Talent Management integration with SAP ERP HCM
®
1
: ;ion. 1508
.------1
Published 3 monttls ago
Figure 14 Copy Integration Package
2. Select CREATE
COPY
to copy the integration package (see Figure 15).
Messages Could not copy integration paci
Overwrde
>
D
Create copy
Figure 15 Creat e Copy
3. Provide a suffix to create your own integration package file name (see Figure 16). Provide suffix create copy with Suffix
2.1.2017 0.28.19
(Leave blank for defa1
Figure 16 Create Integration Copy w ith Suffix
61
I
2
Overview of SAP Cloud Platform Integration Content by Deployment Model
Design
You should have all the relevant integration packages saved in your design workspace now. To check, navigate to DESIGN from the menu. On the left pane, under OVERVIEW on the DESIGN page, you should be able to see all integration packages copied from DISCOVERY (see Figure 17). With the relevant integration packages in place, you're ready to begin the detailed configuration of the integration scenarios, as discussed ahead.
....,, .,, ... ,,,
·•·
.,,
'"
...
Ei:u> 10 SuocessFaaors Empio'Jee Central EmplOyee and Organlzailon . \'•"I l>e updated on 11t03i2017
SAP Se-st Practces tor SuccessFactors Emplo)-tt Central .
SAP ERP lO sueettsFact()fS EmplO)·ee Centttil conlirmaliOn \'NI t>e upoateo on 11 rQ3.·2011 SAP ERP to SoccessFactors Emplo)'ee Central \'1111 be updated on 11f03.'2017
SAP ERP to SoccessFactors EmplO)·ee Central Co~ Center_. _
Welcome to your Customer Workspace Hete, you can eteate and assemble on1taC1s. sueh as lntegratJOn noi.vs. 1n10 a paekage You can also copy be CQnfigured and deployed to fulfil your scenario In the Overview section, you can vie\Y your integration packages, \Vhw;h can contail one or more of the foll • Integration ftcl\vs
• Dala fto\VS • • • •
VakJe mappVlgs OData services (Beta) F"iles URLS
\'.'" l>e updated on 11!()3.'2017
Figure 17 Design Workspace
Employee Data Integration Scenario
In the talent hybrid deployment model, employee master records are always maintained in the source system, SAP ERP HCM. However, the talent management process is run in SAP SuccessFactors Talent Solutions. The employee master record from SAP ERP HCM is required to support SAP SuccessFactors Talent Management processes, and the data creates the employee profile in SAP SuccessFactors. In technical integration design, employee data is transferred from SAP ERP via a SOAP web service to SAP Cloud Platform Integration; the employee data is then mapped and sent to SAP SuccessFactors Talent Solutions through SFAPI web services.
62
I
2
Overview of SAP Cloud Platform Integration Content by Deployment Model
Configurations and Parameter Settings To begin, select SUCCESSFACTORS HCM SUITE TALENT MANAGEMENT INTEGRATION WITH SAP ERP HCM from the integration package list. There are many artifacts delivered within this integration package for the different talent hybrid integration scenarios. We'll only focus on the following iFlow artifacts: )) LOGIN TO SUCCESSFACTORS HCM SUITE TALENT MANAGEMENT (TYPE: PROCESS INTEGRATION) )) USER DATA TO SUCCESSFACTORS HCM SUITE TALENT MANAGEMENT (TYPE: PROCESS INTEGRATION )) LOGOUT OF SUCCESSFACTORS HCM SUITE TALENT MANAGEMENT (TYPE: PROCESS INTEGRATION) Let's start with the first iFlow configuration. Select CONFIGURE from the ACTION dropdown, as shown in Figure 18. Refer to the configuration and parameters listed below to complete the standard configuration settings for the employee data integration process for the talent hybrid model. HANA Cloud Integration
Data ServlCCS
SUccessFactors HCM Suite Talent Management 1ntegrauon Wfl1 SAP ERP HCM_SP_TEST
unmo<11fieo I Update Avauaole
0
Job Application Status Update Reques1 connrmauon Integrates confirmation tnat an update reques11or jOb appt1Cat1on was proeesseo In successraetors HCM sune unmoolfied I Update Available
100
Process Integration
100
Process6
o!i
List to SAP ERP HCM
0
integrates a liSl of o!)jed.S from successFactors HCM SUite Ta1en1 ~1anagement Into SAP ERP HCM.
•
•
unmOdtned I Update Available
•
Login to SUccessfactors HCM Surte latent Management
0
Integrate 10 login to successFactors HCM Suite Talent Management. unmoarr.eo I Update AvallaDle
201
Logout of SuccessFactors HCM Suite Talent Management
Tl'liS lntegratiOn Process is used to get User detailS by queryi'lg user Ob;ect
Unmodified I Update Availaf>le Recruili
to SAP ERP HCM
Figu re 18 Configure Integration Flow
@
C
I
2
Overview of SAP Cloud Platform Int egration Content by Deployment Model
Integration Flow
Login to SAP SuccessFactors Talent Management suite and enter the correct values. For sender values, enter the following: >> SENDER: Default value SAP_HCM >> ADAPTER TYPE: Default value SOAP >> AUTHORIZATION: USER ROLE or CLIENT CERTIFICATE For receiver, enter the following: >> RECEIVER: Default value SFSF_BIZX >> ADDRESS: SAP SuccessFactors SFAPI URL Once you' re finished, you can deploy the iFlow as seen in Figure 13. The same sender and receiver settings apply to the other iFlows for employee data integration. You can repeat the same steps to complete the remaining two iFlows for the employee data integration scenario: 1. USER DATA TO SUCCESSFACTORS HCM SUITE TALENT MANAGEMENT (TYPE:
PROCESS INTEGRATION) 2. LOGOUT OF SUCCESSFACTORS HCM SUITE TALENT MANAGEMENT (TYPE: PROCESS INTEGRATION) Connections
There are two types of communication configuration to set up for the employee data integration: connection from SAP Cloud Platform Integration to SAP ERP and connection from SAP Cloud Platform Integration to SAP SuccessFactors Talent Solution.
I
2
Overview of SAP Cloud Platform Integration Content by Deployment Model
Note
Because t hree SAP Cloud Platform Integration iFlows have been delivered f o r supporting the employee dat a integration scenarios, there will be three service definitions to configure and activate in SOAMANAGER. In the fol lowing configuration example, we'll only walkthrough one of the service defin ition configurations; all three service definition configuration processes are simi lar, except for t he SAP Cloud Platform Integration iFlow sender endpoint URL. However, to complete the full configurat ion, all three service defin itions are requ ired .
To enable the connection from SAP ERP to SAP Cloud Platform Integration, proceed as follows: 1. Go to WEB SERVICE CONFIGURATION in Transaction SOAMANAGER. 2. Search for and select service definition SFS FSessionHandlingLogin Que r yResu l t _Out . This is the session login request for SAP SuccessFactors Talent Solution. 3. In the CONFIGURATION section, create a new logical port by using manual configuration and set it as the default logical port. 4. In the MANUAL CONFIGURATION section, proceed as follows:
- Fill in the SAP Cloud Platform Integration communication username and password. - Fill in the SAP Cloud Platform Integration runtime host URL in COMPUTER NAME OF ACCESS URL. - Enter the SuccessFactors iFlow sender address in URL ACCESS PATHfor example: /cx.flhcm2bizx./SFSFSessionHandlingLoginQueryResult_Out. - Select the HTTPS and SAP Cloud Platform Integration default port 443 options. Once you 're done, save and activate the configuration. The URL access path must match the sender address of the iFlow you're configuring for the related service definition. To make sure you're configuring the correct URL access path, always refer to the related iFlow
I
2
Overview of SAP Cloud Platform Integration Content by Deployment Model
sender address in SAP Cloud Platform Integration. For example, you're now configuring the URL for login to the SAP SuccessFactors iFlow, so you should refer to the sender address of the LOGIN TO SuccEssFACTORS HCM SUITE TALENT MANAGEMENT iFlow. Repeat the same configuration steps for the remaining two service definitions relevant to the employee data integration Scenario:
>> SFSFUSERUPSERTREQUESTCONFIRMATION_OUT: Employee data transfer request to SAP SuccessFactors Talent Solution
>> SFSFSESSIONHANDLINGLOGOUTQUERYRESULT_Our: Session logout request to SAP SuccessFactors Talent Solution For setting up the connection from SAP Cloud Platform Integration to SAP SuccessFactors, refer back to the "Connections" section in the section "Cost Center Integration Scenario Overview". The same connection set up can be followed. Compensation Process Integration Scenario
In the talent hybrid deployment model, employee merit assessment and compensation adjustment is performed in the SAP SuccessFactors Talent Solutions Compensation module, while basic employee pay information is maintained in SAP ERP. To support the end-to-end compensation process, the compensation integration process facilitates the data flow seamlessly between the two systems. In technical integration design, compensation data is transferred from SAP ERP via a SOAP web service to SAP Cloud Platform Integration; the compensation data is then mapped and sent to SAP SuccessFactors Talent Solutions through SFAPI web services.
Configurations and Parameter Settings Compensation data iFlows are delivered as part of the SuCCESSFACTORS HCM SUITE TALENT MANAGEMENT INTEGRATION WITH SAP ERP HCM integration package together with other integration scenarios. Therefore,
66
I
2
Overview of SAP Cloud Platform Integration Content by Deployment Model
we'll focus only on the following iFlow artifacts that are relevant to compensation data integration scenarios: )) LOGIN TO SUCCESSFACTORS HCM SUITE TALENT MANAGEMENT (TYPE: PROCESS INTEGRATION) )) COMPENSATION TO SUCCESSFACTORS HCM SUITE TALENT MANAGEMENT >> DESCRIPTIONS TO SAP ERP HCM >> LIST TO SAP ERP H CM )) SUBMIT JOB QUERY TO SUCCESSFACTORS HCM SUITE TALENT MANAGEMENT >> GET JOB STATUS TO SAP ERP HCM >> GET JOB RESULT TO SAP ERP HCM >> CANCEL JOB TO SUCCESSFACTORS HCM SUITE TALENT MANAGEMENT >> LOGOUT OF SUCCESSFACTORS HCM SUITE TALENT MANAGEMENT (TYPE: PROCESS INTEGRATION)
The integration configuration and parameter setup for compensationrelated integration flows have a similar setup as the employee data integration scenario. To begin, configure and deploy each compensation-related iFlow by referencing to the configuration and parameter setup in the section "Employee Data Integration Scenario." The same configuration steps can be followed. Connections
There are two types of communication configurations to set up for the compensation data integration: connection from SAP Cloud Platform Integration to SAP ERP and connection from SAP Cloud Platform Integration to SAP SuccessFactors Talent Solutions. To enable the connection from SAP ERP to SAP Cloud Platform Integration, follow the configuration steps listed below. Because nine SAP Cloud Platform Integration iFlows have been delivered for supporting compensation data integration scenarios, there will be nine
I
2
Overview of SAP Cloud Platform Integration Content by Deployment Model
service definitions to be configured and activated in SOAMANAGER. The configuration steps are like those for the Employee Data Integration Scenario under the "Connections" section. Therefore, you can configure and activate the nine service definitions by referring to the configuration steps of the SFSFSess i onHandl i ngLogi nOueryResu l t _ Out service definition from the employee data scenario in conjunction with Table 1. Description
SFSF Query Handling Get Job Status Query Response Out
SFSFOueryHandlingGetJobStatusOuery Response_Out
SFSF Query Handling Get Job Resu lt Embedded Q uery Response Out
SFSFOueryHandlingGetJobResu l tEmbeddedOueryResponse_Out
SFSF Query Handling Cancel Job Query Response Out
SFSFOueryHandlingCancelJobOueryResponse_ Out
SF Session Hand ling Logout
SFSFSessionHandlingLogoutQueryResult_Out
Table 1 Compensation Data Service Definition List
For setting up the connection from SAP Cloud Platform Integration to SAP SuccessFactors, refer back to the section "Cost Center Integration Scenario Overview" . The same connection set up can be followed . Recruiting Process Integration Scenario Overview
In the talent hybrid deployment model, the recruiting process is performed through the SAP SuccessFactors Talent Solutions Recruiting module,
68
I
2
Overview of SAP Cloud Platform Integration Content by Deployment Model
while the hiring process is performed in SAP ERP. To support end-to-end process from recruiting to new hire, an integration scenario is delivered to ensure that job vacancy and candidate data are integrated between the two systems. In technical integration design, recruiting data is transferred from SAP ERP via a SOAP web service to SAP Cloud Platform Integration; the recruiting data is then mapped and sent to SAP SuccessFactors Talent Solutions through SFAPI web services.
Configuration for Recruiting Process Integration Sender and Receiver Settings Recruiting data iFlows are delivered as part of the SuccESSFACTORS HCM SUITE TALENT MANAGEMENT INTEGRATION WITH SAP ERP HCM Integration package together with other integration scenarios. For this reason, we'll only focus on the following integration flow artifacts that are relevant to recruiting data integration scenarios: )) LOGIN TO SUCCESSFACTORS HCM SUITE TALENT MANAGEMENT (TYPE: PROCESS INTEGRATION) )) GENERIC UPSERT REQUEST TO SUCCESSfACTORS HCM SUITE TALENT MANAGEMENTDESCRIPTIONS TO SAP ERP HCM )) GENERIC INSERT REQUEST TO SUCCESSFACTORS HCM SUITE TALENT MANAGEMENT )) JOB APPLICATION STATUS UPDATE REQUEST CONFIRMATION >> RECRUITING TO SAP ERP HCM >> LIST TO SAP ERP H CM >> DESCRIPTIONS TO SAP ERP HCM )) SUBMIT JOB QUERY TO SUCCESSFACTORS HCM SUITE TALENT MANAGEMENT >> GET JOB STATUS TO SAP ERP HCM >> GET JOB RESULT TO SAP ERP HCM
69
I
2
Overview of SAP Cloud Platform Integration Content by Deployment Model
>> LOGOUT OF SUCCESSFACTORS
HCM SUITE TALENT MANAGEMENT (TYPE:
PROCESS INTEGRATION)
The integration configuration and parameter setup of recruiting-related iFlows have a similar setup as the employee data integration scenario. To begin, configure and deploy each recruiting-related iFlow by referring to the configuration and parameter setup of "Employee Data Integration Scenario." The same configuration steps can be followed.
Connections
There are two types of communication configuration to setup for the compensation data integration: connection from SAP Cloud Platform Integration to SAP ERP and connection from SAP Cloud Platform Integration to SAP SuccessFactors Talent Solutions. To enable the connection from SAP ERP to SAP Cloud Platform Integration, follow the configuration steps listed below. Because eleven SAP Cloud Platform iFlows have been delivered for supporting recruiting data integration scenarios , there will be eleven service definitions to configure and activate in Transaction SOAMANAGER. The configuration steps are like those for the Employee Data Integration Scenario under the "Connections" section. Therefore, you can configure and activate the eleven service definitions noted in Table 2 by referring to the configuration steps for the SFSFSessionHandlingLoginQueryResult_Out service definition for the employee data scenario. Description
Service Definition
SF Session Hand ling Login
SFSFSessionHandlingLoginOueryResult_Out
Generi c SFSF Insert
SFSFGenericlnsertReq uestConfirmation_Out
Generi c SFSF Upsert
SFSFGenericUpsertRequestConfirmation_Out
SFSF Describe SFObjects Ex
SFSFAPIDictionaryDescribeSFObjectsExResult_Out
Out
Table 2 Recruiting Data Service Definition Li st
70
I
2
Overview of SAP Cloud Platform Integration Content by Deployment Model
Description
Service Definition
SFSF List SFObjects Out
SFSFAPIDictionarylistSFObjectsResu l t _Out
SFSF Query Handling Submit Job Query Response Out
SFSFOueryHandlingSubmitJobOueryResponse_ Out
SFSF Query Handling Get Job Status Query Response Out
SFSFOueryHandlingGetJobStatusOuery Response_Ou t
SFSF Query Handling Get Job Resu lt Embedded Query Response Out
SFSFOueryHandlingGetJobResu l tEmbedded · OueryResponse_Out
Request: Update for Status of SFSFJobApplica t ionStatusUpdateRequestJob Application Confirmation_Out Request: Update for User Id of Candidate
SFSFCandida t eUserldUpdateRequestConfi rma t ion_Out
SF Session Hand ling Logout
SFSFSession Handling LogoutOueryResu l t_Out
Table 2 Recruiting Data Service Definition List (Cont.)
For setting up the connection from SAP Cloud Platform Integration to SAP SuccessFactors, refer back to the "Connections" subsection of the Cost Center Integration Scenario Overview. The same connection set up can be followed. Variable Pay Process Integration Scenario
In the talent hybrid deployment model, employee variable pay and bonus assessment is performed in SAP SuccessFactors Talent Solutions Variable Pay module, while employee bonus pay information is maintained in SAP ERP for further processing. To support the end-to-end variable pay process, the variable pay integration process is delivered to facilitate the data flow seamlessly between the two systems. In technical integration design, variable pay data is transferred from SAP ERP via a SOAP web service to SAP Cloud Platform Integration; the variable data is then mapped and sent SAP SuccessFactors Talent Solutions through SFAPI web services.
71
I
2
Overview of SAP Cloud Platform Integration Content by Deployment Model
Configuration for Variable Pay Process Integration Sender and Receiver Settings Variable pay iFlows are delivered as part of the SuccESSFACTORS HCM SUITE TALENT MANAGEMENT INTEGRATION WITH SAP ERP HCM integration package together with other integration scenarios. To setup the variable pay integration scenario, the following iFlow artifacts need to be configured: )) LOGIN TO SUCCESSFACTORS HCM SUITE TALENT MANAGEMENT (TYPE: PROCESS INTEGRATION) )) GENERIC UPSERT REQUEST TO SUCCESSFACTORS HCM SUITE TALENT MANAGEMENT )) GENERIC INSERT REQUEST TO SUCCESSFACTORS HCM SUITE TALENT MANAGEMENT )) GENERIC DELETE REQUEST TO SUCCESSFACTORS HCM SUITE TALENT MANAGEMENT )) USER DATA TO SUCCESSFACTORS HCM SUITE TALENT MANAGEMENT >> LIST TO SAP ERP H CM >> DESCRIPTIONS TO SAP ERP HCM )) LOGOUT OF SUCCESSFACTORS HCM SUITE TALENT MANAGEMENT (TYPE: PROCESS INTEGRATION) The integration configuration and parameter setup of variable pay-related iFlows have a similar setup as the employee data integration scenario. To begin, configure and deploy each of the variable pay- related iFlows by referring to the configuration and parameter setup of the Employee Data Integration Scenario. The same configuration steps can be followed.
Connections There are two types of communication configuration to set up for variable pay integration: connection from SAP Cloud Platform Integration to SAP
72
I
2
Overview of SAP Cloud Platform Integration Content by Deployment Model
ERP and connection from SAP Cloud Platform Integration to SAP SuccessFactors Talent Solutions. To enable the connection from SAP ERP to SAP Cloud Platform Integration, follow the configuration steps below. Because there are eight SAP Cloud Platform Integration iFlows delivered for supporting variable pay integration scenarios, there will be eight service definitions to configure and activate in SOAMANAGER. The configuration steps are like those for the Employee Data Integration Scenario under the "Connections" section. Therefore, you can configure and activate the eight service definitions listed in Table 3 by referring to the configuration steps for the SFSFSessionHand l i ngLoginQueryResult_Out service definition for the employee data scenario. Usage
Service Definition
SF Session Hand ling Login
SFSFSessionHand l ingLoginQueryResult_Out
Generic SFSF Insert
SFSFGenericlnsertRequestConfirmation_Out
Generic SFSF Upsert
SFSFGenericUpsertRequestConfirmation_Out
SFSF Describe SFObjects Ex Out
SFSFAPIDictionaryDescribeSFObjectsEx Result_Out
SFSF List SFObjects Out
SFSFAPIDictionaryListSFObjectsResult_Out
Generic SFSF Delete
SFSFGenericDeleteReq uestConfirmation_Out
SFSF User Query
SFSFUserQueryRequest_Out
SF Session Hand ling Logout
SFSFSessionHandlingLogoutQueryResult_Out
Table 3 Variable Pay Service Definition List
For setting up the connection from SAP Cloud Platform Integration to SAP SuccessFactors, refer back to the "Connections" section within the Cost Center Integration Scenario Overview. The same connection setup can be followed.
73
I
2
Overview of SAP Cloud Platform Integrat ion Content by Deployment Model
Equity Pay Process Integration Scenario
In the talent hybrid deployment model, employee equity and stock plans allocations are handled in the SAP SuccessFactors Talent Solutions Variable Pay module, while employee equity and stock payment information is maintained in SAP ERP for further processing in payroll. To support the end-to-end equity pay process, the equity pay integration process facilitates the data flow seamlessly between the two systems. In technical integration design, equity pay data is transferred from SAP ERP via a SOAP web service to SAP Cloud Platform Integration; the equity data is then mapped and sent to SAP SuccessFactors Talent Solutions through SFAPI web services. Equity pay integration shares SAP Cloud Platform Integration iFlow objects with compensation data integration for transferring equity pay from SAP ERP to SAP SuccessFactors. If you've already configured and deployed the compensation data- related iFlows in SAP Cloud Platform Integration and activated service definitions in Transaction SOAMANAGER, there are no further steps required for setting up equity pay integration. Otherwise, please refer to the configuration steps discussed in the section "Compensation Process Integration Scenario". Learning Process Integration Scenario
In the talent hybrid deployment model, employee competency assessment, curricula data, and learning curriculum assessments are performed in the SAP SuccessFactors Talent Management learning management system (LMS), while final employee user competency and curriculum statuses are transferred to SAP ERP. To support the end-to-end learning integration process, the integration process facilitates the data flow seamlessly between the two systems. In technical integration design, an employee's related curricula data is transferred from the LMS system via the SAP SuccessFactors REST web service query initiated by SAP Cloud Platform Integration through a timer
74
I
2
Overview of SAP Cloud Platform Integration Content by Deployment Model
event; the curricula data is then mapped and sent as qualification data to SAP ERP through OData web services. However, an employee's related competency data is transferred from SAP SuccessFactors via SFAPI web services and SFTP file transfer depending on the scenarios initiated by SAP Cloud Platform Integration. The competency data is then mapped and sent as qualification data to SAP ERP through OData web services.
Configurations and Parameter Settings To begin, select SUCCESSFACTORS HCM SUITE COMPETENCY WITH SAP HCM QUALIFICATION from the integration package list. There are three artifacts delivered in this integration package for supporting COMPETENCY TO QUALIFICATION integration scenarios: )) EMPLOYEE QUALIFICATION RATING (TYPE: PROCESS INTEGRATION) )) COMPETENCY CATALOG (TYPE: PROCESS INTEGRATION) )) USER COMPETENCY RATING (TYPE: PROCESS INTEGRATION) Let's start with the first iFlow configuration. Select CONFIGURE from the ACTION dropdown to enter iFlow configuration mode. Refer to the configuration and parameters listed below to complete the standard configuration settings.
Configuration for Employee Qualification Rating Integration Sender and Receiver Settings Set up the receiver settings for SFS F_BI ZX _USER as follows: >> RECEIVER: SFSF_BIZX_USERS. )) ADAPTER TYPE: SUCCESSFACTORS. >> ADDRESS: Enter the SAP SuccessFactors SFAPI base URL here. >> CREDENTIAL NAME: Enter the name of the SAP Success Factors credential artifact you've deployed.
75
I
2
Overview of SAP Cloud Platform Integration Content by Deployment Model
Set up the receiver settings for SFS F_BI ZX _Competency as follows: )) RECEIVER: SFSF_BIZX_COMPETENCY. )) ADAPTER TYPE: ODATA. >> ADDRESS: Enter the SAP SuccessFactors OData URL here. >> CREDENTIAL NAME: Enter the name of the SAP SuccessFactors credential artifact you've deployed. Note The OData URL depend on the data center hosting your SAP SuccessFactors instance. Refer to SAP Help documentation to determine the correct base URL based on your SAP SuccessFactors data center.
Set up the receiver settings for SAP HCM as follows: >> RECEIVER: SAP_HCM. )) ADAPTER TYPE: ODATA. >> ADDRESS: Enter the SAP ERP HCM OData URL here. >> CREDENTIAL NAME: Enter the name of the SAP ERP credential artifact you've deployed. Integration Flow
Once you're done, you can save the iFlow. There is a further configuration step required to maintain the qualification data extraction filter in the content modifier iFlow; proceed as follows: 1. Click the iFlow name to enter the iFlow design. 2. Click EDIT to enter edit mode.
3. Maintain the qualification default value on the second CONTENT MODIFIER from the left of the Employee Qualification Rating iFlow (see Figure 19).
I
2
I
Overview of SAP Cloud Platform Integration Content by Deployment Model
Example qualification default values to be maintained in the content modifier as seen in Table 4. These values are provided as examples only and for your implementation these should be reviewed. Name
Value
TYPE
1
SOURCE
2
MODULE
21
Table 4 Qualification Default Values
Note
The value to maintain here depends on your SAP SuccessFactors system competency setup and your business requirements. The values fil led in the table above are t he default competency module values set up during record creation.
77
cancel
Overview of SAP Cloud Platform Integrat ion Content by Deployment Model
Once you're done, save and deploy to complete the configuration.
Configuration for Competency Catalog Integration Sender and Receiver Settings In this section, we'll provide the standard setup for the sender settings that represent the SFTP folder of SAP SuccessFactors and the receiver settings that represent SAP ERP HCM, as well as the qualification extraction filter parameters for the Competency Catalog. Set up receiver settings for SAP SuccessFactors as follows: >> RECEIVER: Default value SFSF_BIZX_USERS >> ADAPTER TYPE: Default value SFTP >> DIRECTORY: SFTP directory containing the common-separated values (CSV) file of Competency Catalog >> ADDRESS: SFTP base URL (sjtp4.successfactors.com) >> USER NAME: SFTP user name Set up receiver settings for SAP HCM as follows: )) RECEIVER: SAP_HCM >> ADAPTER TYPE: 0DATA >> ADDRESS: SAP ERP HCM OData URL (https:/!:/Basic/ ERP/sap/opu!odata/sap!HRSFI_QUALIFICATION_SRV) >> CREDENTIAL NAME: Name of SAP ERP credential artifact you've deployed Note The SAP ERP OData address is the public domain name that is accessible by SAP Cloud Platform Integration. It's usually a public domain that points to SAP Web Dispatcher on you r SAP ERP system. The is the HTIPS port defined by your infrastructure network team for connecting to SAP Web Dispatcher. The default HTTPS port is 443.
I
2
Overview of SAP Cloud Platform Integration Content by Deployment Model
I
2
Once you're done, you can save the iFlow. There's a further configuration step required to maintain the qualification data extraction filter in the CONTENT MODIFIER iFlow: 1. Click the iFlow name to enter the iFlow design.
2. Click EDIT to enter edit mode. 3. Maintain the default Competency value on the CONTENT MODIFIER of Competency Catalog iFlow (see Figure 20).
The example parameters to input into the content modifiers as shown in Figure 20 are as follows: >> SOURCE: Maintain the default qualification source value to be set during qualification creation in SAP ERP HCM. For example: COMPETENCY >> PARENTOBJID: Maintain parent qualification object ID of SAP ERP HCM. For example: 50000232
79
cancel
Overview of SAP Cloud Platform Integration Content by Deployment Model
>> PL VAR: Maintain the default plan version value to be set during qualification creation in SAP ERP HCM. For example: 01 >> SCALEIO: Maintain the default scale ID value to be set during qualification creation in SAP ERP HCM. For example: 00000005 Note The value to maintain here depends on your SAP SuccessFactors system competency setup and your business requirements. The values filled above are for configuration step demonstration purposes only.
Once you're done, save and deploy to complete the configuration.
Configuration for User Competency Rating Integration Sender and Receiver Settings Set up receiver settings for SFSF _Bl ZX _USERS as follows: >> RECEIVER: SFSF_B1zX_USERS )) ADAPTER TYPE: SUCCESSFACTORS >> ADDRESS: SAP SuccessFactors SFAPI base URL, for example, https://
apisalesdemo4.successfactors.com >> CREDENTIAL NAME: Name of the SAP SuccessFactors credential artifact name you've deployed Note The SFAPI URL depends on the data center hosting your SAP SuccessFactors instance. Refer to SAP Help document at ion to determine the correct base URL based on your SAP Success Factors data cent er: http://help.sap.com/ saphelpiis_cloud4hr/EN/SF _HCMS_OData_APl_User_en/.
Set up receiver settings for SFSF _BI ZX_Competency as follows: )) RECEIVER: SFSF_BIZX_COMPETENCY )) ADAPTER TYPE: SUCCESSFACTORS
So
I
2
Overview of SAP Cloud Platform Integration Content by Deployment Model
>> ADDRESS: SAP SuccessFactors SFAPI base URL (for example, https://
apisalesdemo4. successfactors.com) >> CREDENTIAL NAME: Name of the SAP SuccessFactors credential artifact you've deployed Note
The OData URL depends on the data center hosting your SAP SuccessFactors instance. Refer to SAP Help documentat ion to determine the correct base URL based on your SAP Success Factors data center: http://help.sap.com/ saphelpiis_cloud4hr/EN/SF_HCMS_OData_APl_User_en/. Set up receiver settings for SAP HCM as follows: >> RECEIVER: SAP_HCM >> ADAPTER TYPE: ODATA >> ADDRESS: SAP ERP HCM OData URL- for example, https:/!: /Basic/ERP/sap/opu/odata/sap/HRSFl_QUALIFICATI0 N_SRV >> CREDENTIAL NAME: Name of the SAP ERP credential artifact you've deployed Note
The SAP ERP OData address is the publ ic domain name accessible by SAP Cloud Platform Integration. It's usually a public domain that points to SAP Web Dispatcher on your SAP ERP system. The is the HTIPS port defined by your infrastructure network team for connecting to SAP Web Dispatcher. The default HTTPS port is 443. Once you 're done, you can save the iFlow. There's a further configuration step required to maintain the qualification data extraction filter in the CONTENT MODIFIER iFlow: 1. Click the iFlow name to enter the iFlow design. 2. Click EDIT to enter edit mode.
81
I
2
Overview of SAP Cloud Platform Integration Content by Deployment Model
I
2
Maintain the qualification filter values on the first CONTENT MODIFIER from the left of the User Competency Rating iFlow (see Figure 21).
The example qualification extraction filter values to be maintained in the content modifier are seen in Table 5. Name
Default Value
TYPE
1
SOURCE
1
MODULE
1
STATUS
3
Table 5 Qualification Extraction Filter Values
Maintain the qualification filter values on the third CONTENT MODIFIER from the left (see Figure 22).
82
Overview of SAP Cloud Platform Integration Content by Deployment Model
I
2
c.o-Message He.»er
tAessage 8oO)'
•
Exchange Property
Header
Name
D
.,...,.
Type
m
0. ,.
source
CQnSlant
v
e
paraml
Expression
v
S(n.boclj)
g
Qele(e Save sa..-e as \
Figure 22 Maintain Content Modifier
Note The value to maintain here depends on your SAP SuccessFactors system competency setup and your business requirements. The values fil led in the table above are for configuration step demonstration purposes only.
Once you're done, save and deploy to complete the configuration. You've now completed the configuration for the competency integration process. To proceed with the configuration of the LMS Curricula integration process, select SUCCESSFACTORS LMS CURRICULA WITH SAP HCM QUALIFICATION from the integration package list. There are two artifacts delivered in this integration package for supporting LMS Curricula to qualification integration scenarios: )) CATALOG SYNCHRONIZATION (TYPE: PROCESS INTEGRATION) )) CURRICULUM STATUS SYNCHRONIZATION (TYPE: PROCESS INTEGRATION) Let's start with the first integration flow configuration. Select CONFIGURE from the ACTION dropdown to enter iFlow configuration mode. Refer to
Overview of SAP Cloud Platform Integrat ion Content by Deployment Model
the configuration and parameters in the next subsection to complete the standard configuration settings.
Configuration for Curriculum Catalog Integration Sender and Receiver Settings Next, you'll set up the sender settings that represent SAP SuccessFactors LMS and the receiver settings that represent SAP ERP HCM, as well as the qualification extraction filter parameters for the Curriculum Catalog synchronization. Set up the sender settings as follows: >> RECEIVER: Default value SFSF_LMS >> ADAPTER TYPE: Default value SUCCESSFACTORS >> ADDRESS: SAP SuccessFactors LMS API URL-for example, https://. successfactors. com/learning/public-api/rest >> CREDENTIAL NAME: Name of the LMS credential artifact you've deployed Set up the receiver settings for SAP HCM as follows: >> RECEIVER: SAP_HCM >> ADAPTER TYPE: ODATA >> ADDRESS: SAP ERP HCM OData URL-for example, https://: /Basic/ERP/sap/opu/odata/sap/HRSFJ_QUALIFICATION_SRV >> CREDENTIAL NAME: Name of the SAP ERP credential artifact you've deployed Note The SAP ERP OData address is the publ ic domain name accessible by SAP Cloud Platform Integration. It's usually a public domain that points to SAP Web Dispatcher on your SAP ERP system. The is the HTIPS port defined by your infrastructure network team for connecting to SAP Web Dispatcher. The default HTTPS port is 443.
I
2
Overview of SAP Cloud Plat form Integrat ion Content by Deployment Model
I
2
Once you're done, you can save the iFlow.
Maintaining the Qualification Default Value There is a further configuration step required to maintain the qualification data default value in the CONTENT MODIFIER iFlow: 1. Click the iFlow name to enter the iFlow design.
2. Click EDIT to enter edit mode. 3. Maintain the qualification default values on the CONTENT MODIFIER from
the left of the Curriculum Catalog Synchronization iFlow (see Figure 23). < currlCulUm catalOg syncnronizaoon
lntegra1ion Proces.t
(0
0
SFSF_LMS
"
'~=;;;mr.-;;;;;;---tj LMSCt.1rr1Cu&aTo /l urric- m a a ulsts SAPOuaJ.lappi ,__.., ~
Example qualification default values to be maintained in the content modifier as seen in Table 6.
cancel
Overview of SAP Cloud Platform Integration Content by Deployment Model
Name
Value
source
LMS
parentObj id 50000232 (example parent qualification object ID in SAP ERP HCM) PLVAR
0 1 (active version)
scalelD
00000005 (example default scale ID value)
Table 6 Qualificat ion Default Values
Note The values to maintain here depend on your SAP SuccessFactors LMS system curricula setup and your business requirements. The values included here are for demonstration purposes only.
Once you're done, save and deploy to complete the configuration. Configuration for Curriculum Status Synchronization Integration Sender and Receiver Settings
You'll set up the receiver settings that represent SAP Successfactors Talent Solution, SAP Successfactors LMS and SAP ERP HCM, as well as the qualification extraction filter parameters for the Curriculum Catalog synchronization . Set up the Receiver settings for SFSF_BIZX as follows: >> RECEIVER: Default value SFSF_BIZX >> ADAPTER TYPE: Default value SUCCESSfACTORS >> ADDRESS: SAP Successfactors SFAPI base URL >> CREDENTIAL NAME: Name of the SAP SuccessFactors credential artifact you've deployed
86
I
2
Overview of SAP Cloud Platform Integration Content by Deployment Model
Set up the receiver settings for SFSF LMS as follows: )) RECEIVER: SFSF_LMS )) ADAPTER TYPE: SUCCESSFACTORS >> ADDRESS: SAP SuccessFactors LMS API URL - for example, https://
tenant>. successfactors. com/learning/public-api/rest >> CREDENTIAL NAME: Name of the LMS credential artifact you've deployed Set up the receiver settings for SAP HCM as follows: >> RECEIVER: SAP_HCM )) ADAPTER TYPE: ODATA >> ADDRESS: SAP ERP HCM OData URL-for example, https://:
\basic\erp \sap \opu \odata \sap \hrs.fi_quali.fication_srv >> CREDENTIAL NAME: Name of the SAP ERP credential artifact you've deployed Note The SAP ERP OData address is the publ ic domain name accessible by SAP Cloud Platform Integration. It's usually a p ublic domain that points to SAP Web Dispatcher on your SAP ERP system. The is the HTIPS port defined by your infrastructure network team for connecting to SAP Web Dispatcher. The default HTTPS port is 443.
Once you're done, you can save the iFlow. There's a further configuration step required to maintain the qualification data extraction filter in the CONTENT MODIFIER iFlow: 1. Click the iFlow name to enter the iFlow design. 2. Click EDIT to enter edit mode. Maintain the qualification default values on the CONTENT MODIFIER of the Curriculum Status Synchornization iFlow (see Figure 24).
I
2
Overview of SAP Cloud Platform Integration Content by Deployment Model
I
2
CumculUm Status Syncllromzanon
Integration Process
0 FetehUsetsSCri pt_V2
Reques1-Rept/ 1-Jll'I
Content Mod"°'
l-+---01
Cur~ulaR•tng
.........,
ToOu.aRm.gM
'-----""""·
Slut
1--1
Content Modifier Message Heaaer
Message Boay
Excllange Property
m
Heaaer
0 0
Name: source
Type Constant
vaJue LMS
Figure 24 Maintain Qualification Defaul t Source System Name
Note Example qualification default values to be maintained in the content modifier could be SOURCE: Maintain source system name here. For example: LMS. The values to maintain here depend on your SuccessFactors LMS system curricula setup and your business requirements. The values listed here are for demonstration purposes only.
Once you're done, save and deploy to complete the configuration. Connections: Learning Process Integration Scenario
There are only outbound connections to set up 1n SAP Cloud Platform Integration, because it initiates all the iFlows. Therefore, you're only required to set up the credential artifacts for connections from SAP Cloud Platform Integration to its receiver systems, SAP SuccessFactors and SAP ERP. To set up the different credentials, follow the configuration steps ahead.
88
Delete
Overview of SAP Cloud Platform Int egration Content by Deployment Model
SAP SuccessFactors Artifact Setup 1. Go to WEBUI . MENU . MONITOR . SECURITY MATERIAL. Click ADD, select
USER CREDENTIALS, and fill in the following user credential details: - ARTIFACT NAME - USER NAME - PASSWORD - COMPANY ID - Select the SUCCESSFACTORS checkbox option 2. Deploy to complete the setup. SAP ERP Credential Artifact Setup 1. Go to WEBUI . MENU . MONITOR . SECURITY MATERIAL. Click the ADD
button, select USER CREDENTIALS, and fill in the following user credential details: - ARTIFACT NAME - USER NAME - PASSWORD - Leave the SUCCESSFACTORS option unchecked 2. Deploy to complete the setup.
SuccessFactors SFTP Credential Artifact Setup 1. Go to WEBUI • MENU • MONITOR • SECURITY MATERIAL. Click the ADD
button, select USER CREDENTIALS, and fill in the following user credential details: - ARTIFACT NAME - USER NAME - PASSWORD - Leave the SUCCESSFACTORS option unchecked 2. Deploy to complete the setup.
89
I
2
Overview of SAP Cloud Platform Integration Content by Deployment Model
SuccessFactors LMS 0Auth2 Credential Artifact Setup 1. Go to WEBUI . MENU . MONITOR . SECURITY MATERIAL. Click the ADD
button, select OAUTH2 CREDENTIALS, and fill in the following user credential details: - ARTIFACT NAME - AUTHENTICATION URL - CLIENT ID - CLIENT SECRET - SCOPE Note 0Auth2 detai ls, such as AUTHENTICATION URL, CLIENT ID , CLIENT SECRET, and SCOPE, are generated from the LMS system. Please contact your LMS consultant to obtain this information.
2. Deploy to complete the setup.
Onboarding Process Integration Scenario
In the talent hybrid deployment model, employee onboarding is performed in the SAP SuccessFactors Talent Solutions Onboarding module and hiring of the employee is transferred to the SAP ERP system. To support the end-to-end onboarding integration process, the integration process is delivered to facilitate the data flow seamlessly between the two systems. In technical integration design, onboarding data is transferred from SAP ERP via a SOAP web service to SAP Cloud Platform Integration; the onboarding data is then mapped and sent to SAP SuccessFactors Talent Solutions through SFAPI web services. To begin , select SUCCESSFACTORS HCM SUITE ONBOARDING WITH SAP ERP HCM from the integration package list. There are many artifacts delivered with this integration package for supporting onboarding scenarios:
90
I
2
Overview of SAP Cloud Platform Integration Content by Deployment Model
)) BEGIN SESSION (TYPE: PROCESS INTEGRATION) )) CANCEL SESSION (TYPE: PROCESS INTEGRATION) )) DELETE 0N-0FFBOARDING DATA (TYPE: PROCESS INTEGRATION) )) GET NEW HIRE RECORD BY EXPORT ID (TYPE: PROCESS INTEGRATION) >> GET OFFBOARD USER RECORD (TYPE: PROCESS INTEGRATION) >> GETNEWHIRERECORD (TYPE: PROCESS INTEGRATION) >> SEND CONFIRMATION to SuCCESSFACTORS ONBOARDING (TYPE: PROCESS INTEGRATION) )) SFSFONBOARDINGCANIDATEINFO (TYPE: PROCESS INTEGRATION) )) TRIGGER 0FFBOARDING FOR AN EMPLOYEE (TYPE: PROCESS INTEGRATION) )) TRIGGER ONBOARDING FOR AN EMPLOYEE (TYPE: PROCESS INTEGRATION) Let's start with the first iFlow configuration. Select CONFIGURE from the ACTION dropdown to enter the iFlow configuration mode. Refer to the configuration and parameters list below to complete the standard configuration settings for t he onboarding data integration process.
Configuration for Onboarding Process Integration Sender and Receiver Settings Set up the sender parameters as follows: >> SENDER: Default value SAP_HCM >> ADAPTER TYPE: Default value SOAP >> AUTHORIZATION: USER ROLE or CLIENT CERTIFICATE Set up the receiver settings as follows: >> RECEIVER: Default value ONBOARDING >> ADAPTER TYPE: Default value SOAP >> ADDRESS: On boarding access URL-for example, https:/!sales-onboard-
Overview of SAP Cloud Platform Integration Content by Deployment Model
Note
The onboarding URL depends on the data center hosting your SAP SuccessFactors instance. Refer to SAP Help documentation to determine the correct base URL based on your SAP SuccessFactors data center: http:// help.sap.com/saphelpiis_cloud4h r/EN/SF _H CMS_OData_APl_User_en/.
Once you're done, you can deploy the iFlow. The same sender and receiver setting configuration applies to the other iFlows that are relevant to onboarding integration. You can repeat the same steps to complete the remaining eight iFlows and complete the onboarding integration scenarios setup in SAP Cloud Platform Integration.
Connections The onboarding process integration scenario involves a connection from SAP Cloud Platform Integration to SAP ERP and from SAP Cloud Platform Integration to SAP SuccessFactors Talent Solutions. To enable the connection from SAP ERP to SAP Cloud Platform Integration, follow the configuration steps below. Because nine SAP Cloud Platform Integration iFlows have been delivered for supporting on boarding integration scenarios, there will be nine service definitions to configure and activate in SOAMANAGER. The configuration steps are like those for the employee data scenario in the Employee Data Integration Scenario. Therefore, you can configure and activate the nine service definitions in Figure 12 by referring to the configuration steps for the SFSFSess i onHandl i ngLogi nQueryResul t_Out service definition in the Employee Data Integration Scenario under the "Connections" section. Description
Service Definition
Get new Hire Record from On boarding
SFSFOffboardingGetOffboardUserRecord_Out
Table 7 Onboarding Data Service Definition List
92
I
2
SAP SuccessFactors Integration Project Planning Considerations
Description
Service Definition
Offboarding Candidate
SFSFOffboardingPos t OffboardUser Record_Out
Onboarding Begin Session
SFSFOnboard ingBeg i nSession_Ou t
Onboarding Begin Session
SFSFOnboard ingCancelSession_Out
Onboarding Candidate Info
SFSFOnboardingCandidatelnfo_Out
Delete New Hire record in Onboarding
SFSFOnboard i ngDelet e NewHireRecord_Out
Get new Hire Record from
SFSFOnboard i ngGetN ewHireRecord_Out
Onboarding SFSFOnboard ingPostNew-
SFSFOnboard ingPostNewHire Record_Out
HireRecord Outbound Update New Hire
SFSFOnboard ingUpd at e NewHire_Out
Table 7 Onboarding Data Service Defin ition List (Cont.)
For setting up the connection from SAP Cloud Platform Integration to SAP SuccessFactors, refer back to the "Connections" section of the Cost Center Integration Scenario Overview. The same connection set up can be followed.
3
SAP SuccessFactors Integration Project Planning Considerations
SAP SuccessFactors integration projects can increase the complexity of your SAP SuccessFactors implementation in terms of software and technical applications required, increased project plan activities, various resourcing and testing system n eeds, or the need for the involvement of other third-party vendors. This section details project tasks we recommend considering to ensure successful deployment of integrations.
93
I
3
SAP SuccessFactors Integration Project Planning Considerations
3.1
General Integration Considerations
When planning an SAP SuccessFactors implementation project that includes integrations with SAP ERP or third-party vendors, the main areas that require further attention include the design, testing, and data migration work streams. Because the configurations in SAP Cloud Platform Integration are standard and SAP generally doesn't allow any custom changes, the integration points listed in the fallowing subsections cover settings in the SAP ERP and SAP SuccessFactors applications. Note Please refer to the SAP-delivered integration guides available on the SAP Help portal for the complete integration setup required in SAP ERP and SAP SuccessFactors: http://help.sap.com/hr_ecintegrat ion and http://bit.ly/sapsuccessfactorsi ntegration help.
Design
During the design of the SAP SuccessFactors Employee Central module, it's important to include the fields required for the integrations during the initial requirements gathering phases to avoid potential rework later. If there are integrations with third-party vendors, we highly recommend collecting the technical specifications to understand the requirements and ensure they're incorporated into the design of the SAP SuccessFactors Employee Central module. The following subsections include items to consider during the design phase. Full Cloud/ Core Hybrid/ Side by Side Integrations
If implementing a full cloud/core hybrid/side by side deployment model. the following integration design items should be considered:
94
I
3
SAP SuccessFact ors Integration Project Planning Considerations
>> All fields are to be included in SAP SuccessFactors Employee Central for all the SAP infotypes in scope for the integration. If there's a field that isn't included, it will be overridden as part of the standard integration. If there's a need to exclude the field in SAP SuccessFactors Employee Central but retain the value in SAP, then custom BAdI development will be required. >> The SAP SuccessFactors Employee Central LOCATION field on the JOB INFORMATION portlet is to be designed to populate the SAP fields PERSONNEL AREA and PERSONNEL SUB-AREA in combination. >> The SAP SuccessFactors Employee Central DEPARTMENT field on the JOB INFORMATION portlet is the organizational unit assignment that populates Infotype 0001, SAP Organizational Assignment, organizational unit field against the employee. >> The standard SAP employee replication process creates SAP basic pay Infotype 0008, with compensation information from table T510 and not T71 0.
>> For all the standard SAP data replications, check the SAP-delivered standard integration guide for the required field limits. In addition, update the relevant SAP SuccessFactors data models to the required field limits. The integration process replication may fail if the field lengths are longer than the specified limits. >> If the integration involves legacy HR employee master data migrated from SAP ERP to SAP SuccessFactors Employee Central, the legacy employee master history data will be overridden based on the FTSD set in SAP Cloud Platform Integration during employee master data integration. Additional logic development is required through BAdl implementation to avoid history data being overridden. >> For standard employee data replication when transferring between company codes, the employee must be terminated in the current company code and rehired into the target company code. If there's a requirement to perform a transfer without having to execute a termination and rehire transaction, then a custom BAdl can be developed.
95
I
3
SAP SuccessFact ors Integration Project Planning Considerat ions
Talent Hybrid Integrations
If implementing the talent hybrid deployment model, the following integration design items should be considered: >> The TIMEZONE field is a mandatory field and is automatically read from the SAP user master record (Transaction SU01). If this field isn't populated, then a BAdI development can default a value. >> There are some filter values that are required to be set up for learning integration scenarios in SAP Cloud Platform Integration. These filter values are related to SAP SuccessFactors LMS and SAP ERP together. We recommend that the integration consultant work closely with the functional consultant for both SAP SuccessFactors LMS and SAP ERP systems to maintain the desired filter values in SAP Cloud Platform Integration. This is highly recommended to minimize any integration errors.
All Integration Deployment Models
For network infrastructure security concerns , we recommend beginning network infrastructure discussions early with the teams involved in setting up the network infrastructure to enable integration traffic between SAP Cloud and customer on-premise systems. Testing
Testing integrations requires a significant amount of planning and coordination to ensure that source and target testing systems are set up with the correct test data, test integration middleware is set up, testing users and access is set up, and testing scripts are available for execution. The following points highlight areas to consider when planning the project testing phases: >> Ensure testing environments include all necessary integration add-ons and SAP software components are up-to-date, as per the development environment requirements.
96
I
3
SAP SuccessFactors Integration Project Planning Considerations
>> During planning for integration testing, it's recommended that a minimum of two cycles of testing are planned to ensure complete end-toend testing, which can uncover design issues. >> Request and schedule production copies early in the project of your SAP production system to quality assurance environments in order to test on production like data to coincide with testing cycles so that the most current data can be leveraged for testing. >> Availability of a full set of testing data is critical to testing the integrations, so it's important during project planning to align data migration activities. >> For SAP SuccessFactors integrations with SAP ERP, include testing of the baseline integrations as a prerequisite prior to beginning any testing scenarios to ensure the two systems are in sync. >> Include testing of inactive employees, retirees, contractors, and rehires in the testing plan.
Data Migration Migration of data is a major component of the project that's often overlooked. Data migration is a one-off conversion of data from the source to the target system. Migrating to the cloud may not be the same for all customers; some may choose to move all SAP ERP HCM applications to the cloud (full cloud) or some SAP ERP HCM applications with the exception of SAP Time/Payroll (core hybrid), and other customers may choose to move talent solutions to the cloud along with core HR for a small set of employees (side by side), while still others may choose to move only talent solutions to the cloud while keeping core HR on-premise intact (talent hybrid). This section outlines SAP's standard data migration options available for your implementation when migrating data into SAP SuccessFactors. Simple File Loads
SAP SuccessFactors offers an administrator tool for importing and exporting data using CSV files. SAP SuccessFactors provides standard templates
97
I
3
SAP SuccessFactors Integration Project Planning Considerations
that can be exported and manually populated with data. The templates include an import sequence and basic validations. This approach is very labor-intensive and is manual, and thus is susceptible to a high number of errors and security concerns. However, this approach is a good option for handling a small volume of data. SAP Rapid Data Migration
SAP Rapid Data Migration uses SAP Data Services tools and comes with proven best practices and content that follows SAP's best practice methodology for data migration. It covers functionality to manage and complete six key areas that are critical to the transformation and migration of data: 1. Extraction of source data
2. Analyze and profiling of data of source data 3. Cleansing of data 4. Validation of data against target fields
5. Loading of data into the target SAP SuccessFactors system 6. Reconciliation of data between source and target systems
This data migration option can be used with any source system and saves a considerable amount of time and effort by providing predelivered migration content for a customer's migration from SAP ERP HCM to SAP SuccessFactors Employee Central. This approach is best suited for customers with large amounts of data from various sources, which requires extensive cleansing and transformation. Note To download the latest cont ent for SAP Rapid Data Migration to cloud solut ions from SAP at no additional cost, visit http://service.sap.com/rds-dm2cloud.
98
I
3
SAP SuccessFactors Integration Project Planning Considerations
I
3
SAP Migration Add-On Tool
SAP delivers a standard migration using the PA_S E_I N add-on tool for customers migrating data specifically from on-premise SAP ERP HCM to SAP SuccessFactors Employee Central (full cloud/core hybrid model). After the migration of data, SAP SuccessFactors Employee Central becomes the system of record. The tool can be accessed once the SAP integration add-on for SAP ERP and SAP SuccessFactors Employee Central is implemented. The tool allows value and field mappings between SAP ERP and SAP SuccessFactors fields to be defined in the SAP Implementation Guide (IMG). Once the mapping is finalized, generation of the standard SAP SuccessFactors CSV files can be executed, which populates the files with source data from SAP. The populated CSV files are then imported into SAP SuccessFactors using the standard import functionality. An overview of the data migration process is shown in Figure 25 .
I Preparation Export data model from EC .., LU
...
Import EC data model into SA P ERP HCM ..,
•
...
}
Mapping
~ Extraction from
,f
LU
-
Field mapping ..,
•
...
£__
SAP ERP HCM
Value mapping ..,
~ Mapping
Generate CSV files ..,
1U
Import CSV files
-
,-----------,
Mapping tab le 1 : update to prepare : 1 the replication 1 1
I
I
..,
u
#
..,
4
-
Pre~ara~ion of repl1cat1on
)
,..----------, 1 Set up employee 1 1 key I
mapping table'
I
..,
LU
I Employee Data
I I
I
L-----------'
I
I
__________ ..I
I...Organizational Data
Figure 25 Data Migration Process
For further information, please refer to the SAP SuccessFactors Data Migration: SAP ERP HCM to Employee Central SAP PRESS E-Bite (http:// sap-press.com/4324), available for download.
3.2
#
Integration Best Practices
SAP delivers several SAP Rapid Deployment Solutions (RDS) for the various deployment models and SAP SuccessFactors integrations scenario based
99
Summary
on best practices. SAP RDS simplify the implementation of integrations with faster, less costly, reduced-risk , predictable business outcomes, which include best practices content and accelerators. Note To view the latest SAP RDS for SAP SuccessFactors integrati ons, v isit https://rapid .sap .com/bp/#/browse/categories/I i nes_of_busi ness/areas/ human_resources.
4
Summary
In summary, whether you're part of an implementation team or a key decision maker in an organization, this E-Bite will serve as a good source of information to support your company's journey to the cloud using SAP Cloud Platform Integration. We discussed the basics of SAP Cloud Platform Integration, which will help kick start project planning activities. In addition, we covered the full cloud/core hybrid, side by side, and talent hybrid standard integration packages available in SAP Cloud Platform Integration for download, copy, and design. Standard design configuration settings in SAP Cloud Platform Integration have been provided as a guideline , along with steps to run/execute and monitor the integrations in SAP Cloud Platform Integration. Finally, based on extensive real-life project experiences, we provided important project planning considerations and design recommendations to help support a successful deployment of the SAP SuccessFactor integrations. We hope this E-Bite becomes part of your toolkit for future SAP Cloud Platform Integration proj ects with SAP SuccessFactors related integrations!
100
I
4
What's Next?
5
What's Next?
You've learned how to use the SAP Cloud Platform integration service with the deployment model of your choice, scoped your integration with best practices, and now you're ready to deploy your integration content. But SuccessFactors integration doesn't stop there; check out Integrating SuccessFactors with SAP for a comprehensive guide to integrating SuccessFactors with SAP ERP, SAP ERP HCM, and third-party applications! Recommendation from Our Editors
1
Get the ball roll ing on your transition to SuccessFactors with Integrating SuccessFactors with SAP! Begin by mapping an integration strategy and exploring the three deployment models tailored for your HR landscape. Then customize the integration process further using packaged integrations, templates, and APls from SuccessFactors and third-party appl ications. There are many pat hs t o the cloud-let this book help get you there. Visit http://sap-press.com/3723 and get your integration project started today!
In addition to this book, our editors picked a few other SAP PRESS publications that you might also be interested in. Check out the next page to learn more!
101
I
5
More from SAP PRESS SuccessFactors with SAP ERP HCM - Business Processes and Use:
Become a pioneer of SAP's next-generation, cloud-based HR solution with this comprehensive guide to SuccessFactors! From cloud computing basics to implementing processes and transactions, get the know-how you need to simplify your HR operation. 644 pages, 2nd edition, pub. 11/201 4 E- book: $59.99 I Print: $69.95 I Bundle: $79.99 www.sap- press.com/3702
SAP SuccessFactors Employee Central-The Comprehensive Guide: Ce-
ment your foundation in Employee Central concepts and see how it fits into the SAP SuccessFactors HCM Suite. Dig in to position and workforce management, employee data, Employee Central Payroll, reporting, and more. 590 pages, pub. 12/2015 E-book: $69.99 I Print: $79.95 www.sap-press.com/3834
I Bundle:
$89.99
Getting Started with SAP HANA Cloud Platform : Want to extend SAP
SuccessFactors? Develop a native SAP HANA application? Code SAPUI5? Guess what: SAP HANA Cloud Platform can do it all. There's more to cloud than fluff-find out what it is. 519 pages, pub. 04/2015 E-book: $59.99 I Print: $69.95 www.sap- press.com/3638
I Bundle:
$79.99
SAP PRESS E-Bites SAP PRESS E- Bites provide you with a high-quality response to your specific project need. If you're looking for detailed instructions on a specific task; or if you need to become fami liar w ith a small, but crucial sub-component of an SAP product; or if you want to understand all the hype around product xyz: SAP PRESS E-Bites have you covered. Authored by the top professionals in the SAP universe, E-Bites provide the excellence you know from SAP PRESS, in a d igestible electronic format, delivered (and consumed) in a fraction of the time! Luke Marson SAP SuccessFactors Data Migration: SAP ERP HCM to Employee Central ISBN 978-1-4932 -1498- 3
I $24.99 I 92 pages
Venki Krishnamoorthy SAP Success Factors Admin Center: User Management, Security, and Data Maintenance ISBN 978-1-4932-1444-0
I $19.99 I 102
pages
lmran Sajid The Payroll Control Center for SAP ERP HCM and SAP SuccessFactors ISBN 978-1-4932-1440-2
I $19.99 I 102 pages
The Authors of this E-Bite Donna Leong-Cohen is the co-founder and managing director of Coeus Consulting, an SAP consulting partner specializing in SAP on-premise and cloud HR implementations using best practices and rapid -deployment solutions. Prior to founding Coeus, Donna worked for several years with Deloitte Consulting in their Human Capital Division. Donna has more than 16 years of experience in implementing HCM global systems and business consulting specializing in HR business process transformation. Seng-Ping Gan is a technical integration expert with Coeus Consulting. He specializes in SAP ERP HCM and SAP SuccessFactors integrations. Seng- Ping has more than 8 years of functional and technical experience in SAP ERP HCM, working with various global companies in Asia, Europe, and the USA.
·usage, Service, and Legal Notes
Notes on Usage This E-Bite is protected by copyright. By purchasing this E-Bite, you have agreed to accept and adhere to the copyrights. You are entitled to use this E-Bite for personal purposes. You may print and copy it, too, but also only for personal use. Sharing an electronic or printed copy with others, however, is not permitted, neither as a whole nor in parts. Of course, making them available on the Internet or in a company network is illegal. For detailed and legally binding usage conditions, please refer to the section Legal Notes.
Service Pages The following sections contain notes on how you can contact us. Praise and Criticism
We hope that you enjoyed reading this E-Bite. If it met your expectations, please do recommend it. If you think there is room for improvement, please get in touch with the editor of the E-Bite: Will Jobst (willj@ rheinwerk-publishing.com). We welcome every suggestion for improvement but, of course, also any praise! You can also share your reading experience via Twitter, Face book, or email.
Supplements
If there are supplements available (sample code, exercise materials, lists, and so on), they will be provided in your online library and on the web catalog page for this book. You can directly navigate to this page using the following link: http://www.sap-press.com/4371. Should we learn about typos that alter the meaning or content errors, we will provide a list with corrections there, too. Technical Issues
Ifyou experience technical issues with your e-book or e-book account at SAP PRESS, please feel free to contact our reader service: [email protected]. About Us and Our Program
The website http://www.sap-press.com provides detailed and first-hand information on our current publishing program. Here, you can also easily order all of our books and e-books. Information on Rheinwerk Publishing Inc. and additional contact options can also be found at http://www.sappress.com.
Legal Notes This section contains the detailed and legally binding usage conditions for this E-Bite. Copyright Note
This publication is protected by copyright in its entirety. All usage and exploitation rights are reserved by the author and Rheinwerk Publishing; in particular the right of reproduction and the right of distribution, be it in printed or electronic form.
You are entitled to use this E-Bite for personal purposes only. In particular, you may print the E-Bite for personal use or copy it as long as you store this copy on a device that is solely and personally used by yourself. You are not entitled to any other usage or exploitation. In particular, it is not permitted to forward electronic or printed copies to third parties. Furthermore, it is not permitted to distribute the E-Bite on the Internet, in intranets, or in any other way or make it available to third parties. Any public exhibition, other publication, or any reproduction of the E-Bite beyond personal use are expressly prohibited. The aforementioned does not only apply to the E-Bite in its entirety but also to parts thereof (e.g., charts, pictures, tables, sections of text). Copyright notes, brands, and other legal reservations as well as the digital watermark may not be removed from the E-Bite. Digital Watermark
This E-Bite copy contains a digital watermark, a signature that indicates which person may use this copy. If you, dear reader, are not this person, you are violating the copyright. So please refrain from using this E-Bite and inform us about this violation. A brief email to [email protected] is sufficient. Thank you! Limitation of Liability
Regardless of the care that has been taken in creating texts, figures, and programs, neither the publisher nor the author, editor, or translator assume any legal responsibility or any liability for possible errors and their consequences.
All rights reserved. Neither this publicat ion nor any part of it may be copied or reproduced in any form or by any means or translated into another language, without the prior consent of Rheinwerk Publishing, 2 Heritage Drive, Suite 305, Quincy, MA 02171. Rheinwerk Publishing makes no warranties or representations with respect to t he content hereof and specifically disclaims any implied warranties of merchantability or fitness for any particular purpose. Rheinwerk Publishing assumes no responsibility for any errors that may appear In this publication. "Rheinwerk Publishing" and the Rheinwerk Publishing logo are registered trad emarks of Rheinwerk Verl ag GmbH , Bonn, Germany. SAP PRESS is an imprint of Rheinwerk Verlag GmbH and Rheinwerk Publish ing. Inc. All of the screenshots and graphics reproduced in this book are subject to copyright
SAP, the SAP logo, ABAP, Ariba, ASAP, Duet, hybris, SAP Adaptive Server Enterprise, SAP Advantage Database Server, SAP Afaria, SAP Archivelin k, SAP Business ByDesign, SAP Business Explorer (SAP BEx), SAP BusinessObjects, SAP BusinessObjects Web Intelligence, SAP Business One, SAP BusinessObjects Explorer, SAP Business Workflow, SAP Crystal Reports, SAP d-code, SAP EarlyWatch, SAP Fiori, SAP Ganges, SAP Global Trade Services (SAP GTS), SAP Goinglive, SAP HANA, SAP Jam, SAP lumira, SAP MaxAttention, SAP MaxDB, SAP NetWeaver, SAP PartnerEdge, SAPPHIRE NOW, SAP PowerB uild er. SAP PowerDesigner. SAP R/2 , SAP R/3, SAP Repli cation Server, SAP SI, SAP SQL Anywhere, SAP Strategic Enterprise Management (SAP SEM), SAP StreamWork, SuccessFactors, Sybase, TwoGo by SAP, and The Best -Run Businesses Run SAP are registered or un registered trademarks of SAP SE, Walldorf, Germany. All other products mentioned in this book are registered or unregi stered trademarks o f their respective companies .
