SAP ERP 6.0
January 2016
English
SAP ERP: Cost Center
Integration to
SuccessFactors EC
(FK9)
Building Block Configuration Guide
SAP SE
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
SAP Best Practices SAP ERP: CC Integr. to SuccessFactors EC (FK9): Config. Guide
Copyright
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the
express permission of SAP SE or an SAP affiliate company.
SAP and other SAP products and services mentioned herein as well as their respective logos are
trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other
countries. Please see http://global.sap.com/corporate-en/legal/copyright/index.epx#trademark for
additional trademark information and notices.
Some software products marketed by SAP SE and its distributors contain proprietary software
components of other software vendors.
National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only,
without representation or warranty of any kind, and SAP SE or its affiliated companies shall not be liable
for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate
company products and services are those that are set forth in the express warranty statements
accompanying such products and services, if any. Nothing herein should be construed as constituting
an additional warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business
outlined in this document or any related presentation, or to develop or release any functionality
mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated
companies’ strategy and possible future developments, products, and/or platform directions and
functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any
time for any reason without notice. The information in this document is not a commitment, promise, or
legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject
to various risks and uncertainties that could cause actual results to differ materially from expectations.
Readers are cautioned not to place undue reliance on these forward-looking statements, which speak
only as of their dates, and they should not be relied upon in making purchasing decisions.
© SAP SE
Page 2 of 12
SAP Best Practices SAP ERP: CC Integr. to SuccessFactors EC (FK9): Config. Guide
Revision
Change Date
Description
0
n/a
Initial creation
© SAP SE
Page 3 of 12
SAP Best Practices SAP ERP: CC Integr. to SuccessFactors EC (FK9): Config. Guide
Icons
Icon
Meaning
Caution
Example
Note
Recommendation
Syntax
Typographic Conventions
Type Style
Description
Example text
Words or characters that appear on the screen. These include field
names, screen titles, pushbuttons as well as menu names, paths and
options.
Cross-references to other documentation.
Example text
Emphasized words or phrases in body text, titles of graphics and tables.
EXAMPLE TEXT
Names of elements in the system. These include report names,
program names, transaction codes, table names, and individual key
words of a programming language, when surrounded by body text, for
example, SELECT and INCLUDE.
Example text
Screen output. This includes file and directory names and their paths,
messages, source code, names of variables and parameters as well as
names of installation, upgrade and database tools.
EXAMPLE TEXT
Keys on the keyboard, for example, function keys (such as F2) or the
ENTER key.
Example text
Exact user entry. These are words or characters that you enter in the
system exactly as they appear in the documentation.
<Example text>
Variable user entry. Pointed brackets indicate that you replace these
words and characters with appropriate entries.
© SAP SE
Page 4 of 12
SAP Best Practices SAP ERP: CC Integr. to SuccessFactors EC (FK9): Config. Guide
Content
1
2
Purpose .............................................................................................................................. 6
Preparation ......................................................................................................................... 6
2.1
Prerequisites ............................................................................................................ 6
3 Configuration ...................................................................................................................... 7
3.1
SuccessFactors Employee Central .......................................................................... 7
3.1.1
Refining Cost Center Object Definition ................................................................ 7
3.2
SAP ERP Finance: Setup Application Link Enabling (ALE) ..................................... 7
3.2.1
Defining Logical Systems .................................................................................... 7
3.2.2
Assigning Logical System to Client ...................................................................... 8
3.2.3
Maintaining Distribution Model ............................................................................. 8
3.2.4
Activating Change Pointer ................................................................................... 9
3.2.5
Maintaining Port ................................................................................................... 9
3.2.6
Creating Partner Profile ....................................................................................... 9
3.2.7
Running Initial Distribution ................................................................................. 10
3.2.8
Configuring / Running Delta Distribution............................................................ 11
© SAP SE
Page 5 of 12
SAP Best Practices SAP ERP: CC Integr. to SuccessFactors EC (FK9): Config. Guide
SAP ERP: Cost Center Integration to
SuccessFactors Employee Central
1 Purpose
The purpose of this document is to describe the general configuration steps required to
manually set up the configuration within the system landscape that has already been installed
using the corresponding installation or configuration guides for installation.
This document supplements the existing configuration documentation and provides additional
information where required.
If you do not plan to replicate cost centers from SAP ERP Finance to Employee
Central this configuration guide is not required.
2 Preparation
2.1 Prerequisites
Before you start installing this scenario, the prerequisite building blocks need to be
configured. Check the sequence of execution in the Building Block Prerequisites Matrix for
this Packaged Solution.
As described in the Configuration Guide – Getting Started:
- For the communication between SAP ERP Finance and SuccessFactors Employee
Central (EC) Company you first need to set up a RFC destination of type ‘G - HTTP
Connection to External Server’.
- You also need to set up the Middleware System (Boomi) as described in the chapter
Setting up the Middleware.
A cost center in SAP ERP has certain control flags to control the behavior of the
cost center in financial processes. Use lock flags to prevent posting to a cost
center.
In Employee Central replication the lock flag actual primary costs is mapped to
the status of the cost center. If the lock flag is not set, the status of the cost center
is Active in Employee Central, if the lock flag is set the status of the cost center is
Inactive in Employee Central.
The integration does not check for dependent data in Employee Central, so
updates can interfere with existing data. For example, a lock flag is set for a cost
center that is still assigned to employees in Employee Central.
Setting of the lock flag sets the Employee Central status to Inactive. This issue is
recognized by the system and an Admin Alert Invalid Cost Center is created. The
issue has to be resolved by the Administrator.
Whenever there are multiple financial systems you have to make sure that the
cost center IDs delivered to Employee Central are unique across your financial
landscape. The translation of cost centers is not supported.
© SAP SE
Page 6 of 12
SAP Best Practices SAP ERP: CC Integr. to SuccessFactors EC (FK9): Config. Guide
See also the handbook for implementing Employee Central on the SAP Service
Marketplace  Employee Central  Replicating Cost Centers from SAP ERP to
Employee Central.
3 Configuration
3.1 SuccessFactors Employee Central
3.1.1 Refining Cost Center Object Definition
1. Log in to your instance and go to Admin Center using the following information:
Link
https://<server>.successfactors.com/login
Menu Path
Home > Admin Center
2. In the Admin Center in the portlet Company Processes and Cycles, select Company
Settings and choose Configure Object Definitions.
3. Choose Search and Object Definition: search for Cost Center and select Take Action 
Make Correction.
4. For the field externalCode (Database Field externalCode) select the Details link and
make the following changes:
Field Name
Value
Maximum Length
20
5. Choose Done.
6. For field name (Database Field externalName) select the Details link and make the
following changes:
Field Name
Value
Maximum Length
40
7. Choose Done.
8. Choose Save.
3.2 SAP ERP Finance: Setup Application Link
Enabling (ALE)
3.2.1 Defining Logical Systems
1. In your SAP ERP Finance system, access the following transaction:
Transaction Code
SALE
2. On the Display IMG screen, access the transaction using the following navigation option:
IMG Path
Idoc Interface / Application Link Enabling (ALE)  Basic
Settings  Logical Systems  Define Logical System
3. On the Logical Systems change view, choose New Entries.
4. On the New Entries: Overview of Added Entries screen, make the following entries:
© SAP SE
Page 7 of 12
SAP Best Practices SAP ERP: CC Integr. to SuccessFactors EC (FK9): Config. Guide
Logical System
Name
Enter logical system of your SAP ERP
Finance system, for example, QI1CLNT600.
Enter a name to identify your SAP ERP
Finance system*.
Enter logical system of your EC Company,
for example, ECPMTEST18.
Enter a name to identify your EC
Company*.
The distribution of data between systems requires that each system in the
network has a unique identification. The logical system is used for this purpose.
5. Save your entries.
6. Create a transport request, if necessary, and choose Continue.
3.2.2 Assigning Logical System to Client
In the following configuration steps you assign the logical system for your SAP ERP system to
the corresponding client.
1. In your SAP ERP Finance system, access the following transaction:
Transaction Code
SALE
2. On the Display IMG screen, access the transaction using the following navigation option:
IMG Path
Idoc Interface / Application Link Enabling (ALE)  Basic
Settings  Logical Systems  Assign Logical System to Client
3. Search for the client you are currently logged in and double-click the entry to see the
details.
4. On the Change View “Clients”: Details screen, check the following entry:
Field Name
Value
Logical System
Logical system name of the system and
client you are logged in for example,
QI1CLNT600
5. Save your entry.
6. Create a transport request, if necessary, and choose Continue.
3.2.3 Maintaining Distribution Model
1. In your SAP ERP Finance system, access the following transaction:
Transaction code
BD64
2. On the Display Distribution Model screen, switch to change mode.
3. Choose Create Model View (Ctrl + F4).
4. In the Create model view dialog box, enter a short text (for example <FIN600 to EC
PMTEST18>) and a technical name (for example <FIN600PM18>). Choose Continue
(Enter). Save your entries.
5. Select your newly created model and choose Add Message Type.
6. In the Add Message Type dialog box, enter the logical system of your SAP ERP Finance
system in the Sender field and the logical system of your EC Company in the Receiver
field. As message type, select ODTF_CCTR.
7. Save your entries.
© SAP SE
Page 8 of 12
SAP Best Practices SAP ERP: CC Integr. to SuccessFactors EC (FK9): Config. Guide
3.2.4 Activating Change Pointer
1. In your SAP ERP Finance system, access the following transaction:
Transaction Code
BD61
2. Make sure that Change Pointers activated-generally is selected.
3. Access the transaction using the following navigation option:
Transaction Code
BD50
4. On the Change View “Activate Change pointers for Message Type” screen, verify that the
activation is set for message type ODTF_CCTR.
3.2.5 Maintaining Port
1. In your SAP ERP Finance system, use one of the following navigation options:
Transaction code
WE21
Menu Path
SAP Menu Tools  ALE  ALE Administration  Runtime
Settings  Port Maintenance
2. On the Ports in IDOC processing screen, select XML HTTP in the navigation panel.
3. Choose Create.
4. On the Add XML HTTP Port screen, make the following entries:
Field Name
Value
Port
<Enter a technical name e.g.
ECPMTEST18>
Description
<Enter a description for your
port name>
Version
IDoc record types SAP Release 4.x
<Enter the technical name of your
RFC destination for the EC
Company>
RFC destination
Content Type
Application/x-sap.idoc
X
X
SOAP Protocol
3.2.6 Creating Partner Profile
1. In your SAP ERP Finance system, access the following transaction:
Transaction code
WE20
2. On the Partner profiles screen, select Partner Type LS in the navigation panel.
3. Choose Create and make the following entries:
Field Name
Value
Partner No.
<Enter the logical system of your
EC Company, for example
ECPMTEST18>
Partn. Type
LS
© SAP SE
Page 9 of 12
SAP Best Practices SAP ERP: CC Integr. to SuccessFactors EC (FK9): Config. Guide
4. On tab Post processing: permitted agent specify the job (person or group of people) to be
notified if processing errors occur.
5. Save the partner profile.
6. In the Outbound parmtrs. section choose Create outbound Parameter.
7. On the Partner profiles: Outbound parameters screen, make the following entries:
Field Name
Value
Message Type
ODTF_CCTR
Receiver Port
<Enter the technical Name of the
created port>
Output Mode
Transfer IDoc Immed.
X
Basic Type
ODTF_CCTR01
Cancel Processing After Syntax Error
X
8. Save your entries.
3.2.7 Running Initial Distribution
1. In your SAP ERP Finance system, use one of the following navigation options:
Menu Path
SAP Menu  Tools  ABAP Workbench  Development 
ABAP Editor
Transaction Code
SE38
2. On the ABAP Editor: Initial Screen, enter ODTF_REPL_CC in the Program field and
choose Execute.
3. On the Replicate Cost Centers into SAP Cloud for Travel screen, define your replication
criteria as required and enter the following value:
Field Name
Value
Settings for Description
…………Replicate all languages (only
supported for replication to Employee
Central)
Field Name
X
Value
Delta Replication Settings
…………Use Variant for Delta Replication
Using Change Pointers
Ignore these settings for initial
replication.
Choose Receiving System
………...Receiver Partner No.
<Enter the logical system of your
EC Company>
Transmission Start
………..Transmission Start Date
<Enter the date. This defines as
of data are replicated.>
4. Choose Execute.
© SAP SE
Page 10 of 12
SAP Best Practices SAP ERP: CC Integr. to SuccessFactors EC (FK9): Config. Guide
3.2.8 Configuring / Running Delta Distribution
To schedule a background job for the delta replication, you need to create a variant of ABAP
program ODTF_REPL_CC and RBDMIDOC first.
1. Use one of the following navigation options:
Menu Path
SAP Menu  Tools  ABAP Workbench  Development 
ABAP Editor
Transaction Code
SE38
2. On the ABAP Editor: Initial Screen, enter ODTF_REPL_CC in the Program field and
choose Execute. On the Replicate Cost Centers into SAP Cloud for Travel screen, define
your replication criteria as required and enter the following value:
Field Name
Value
Settings for Description
…………Replicate all languages (only
supported for replication to Employee
Central)
X
Field Name
Value
Delta Replication Settings
…………Use Variant for Delta Replication
Using Change Pointers
X (Select this to ensure that the
variant is used for change
pointers)
Choose Receiving System
………...Receiver Partner No.
<Enter the logical system of your
EC Company>
Transmission Start
………..Transmission Start Date
<Enter the date. This defines as
of data are replicated.>
Processing Mode
………...Send IDOC
X
3. Choose Save as Variant… to create a new variant.
4. On the Variant Attributes screen, enter the following values:
Field Name
Value
Variant Name
YK_DELTA_CC_EC
Description
<Enter a description for the
variant>
5. Save your entries. A system message confirms the creation.
6. Chose Back.
7. On the ABAP Editor: Initial Screen, enter RBDMIDOC in the Program field and choose
Execute. On the Creating IDoc Type from Change Pointers screen, enter the following
value:
Field Name
Value
Message Type
ODTF_CCTR
8. Choose Save as Variant… to create a new variant.
9. On the Variant Attributes screen, enter the following values:
© SAP SE
Page 11 of 12
SAP Best Practices SAP ERP: CC Integr. to SuccessFactors EC (FK9): Config. Guide
Field Name
Value
Variant Name
YK_ODTF_CCT_EC
Description
<Enter a description for the
variant>
10. Save your entries. A system message confirms the creation.
11. To schedule the job, use one of the following navigation options:
12.
13.
14.
15.
Menu Path
SAP Menu  System  Services  Jobs  Define Job
Transaction Code
SM36
On the Define Background Job screen, proceed as follows:
Choose Define Job using Wizard (Ctrl+F1).
On the Create a Job dialog box, choose Continue.
On the General Job Information dialog box, make the following entries:
Field Name
Value
Job Name
YK_ODTF_DELTA_CC_PY
Job Class
C – Low priority
Job Status
Scheduled
Target Server
16. Choose Continue.
17. In the Job-Definition: Job step dialog box, select ABAP program step and choose
Continue.
18. In the ABAP program step dialog box, make the following entries:
Field Name
Value
ABAP program name
RBDMIDOC
Variant
YK_ODTF_CCT_EC
Execution language
EN
19. Choose Continue.
20. In the Multi-step option dialog box, choose Continue.
21. In the Job Definition: Start conditions screen, choose Immediately. Then choose
Continue.
22. In the Def. of start immediately dialog box, select check the Period checkbox in the
Periodic jobs section and choose Continue.
23. In the Period definition dialog box, choose None of the Above.
24. Select the Other Periods button.
25. In the Other Period dialog box, schedule the service for a convenient time interval.
26. Choose Create.
27. Choose Continue.
28. In the Set job dialog box, choose Complete to finish the setup.
In case the stored variants in report ODTF_REPL_CC are not called/found please
update the navigation index in se80. Call transaction SE80 and select report
ODTF_REPL_CC. Double-click the report in the object list. Then the report is
shown on the right side and you can call menu entry Utilities  Update
Navigation Index.
© SAP SE
Page 12 of 12