BIB CONFIGURATION DOCMENT

Contents
ABOUT CPI (Cloud Platform Integration): -.........................................................................................2
BIB CONFIGURATION SET UP......................................................................................................................2
NAVIGATION 01: - Specify Employee Central Instance ID..................................................................2
NAVIGATION 02: - Maintain the Constant Values...................................................................................2
NAVIGATION 03: - Maintain the Constant Values based on Country /Region...............................3
NAVIGATION 04: - Allow Data Replication from EC for payroll Areas in Correction Phase......3
NAVIGATION 05: - Define Additional Foundation Objects for migration Data to EC..................4
NAVIGATION 06: - Import Metadata for Web Service-Based Data Transfer from EC..................5
NAVIGATION 07: - Import Picklists from Employee Central to SAP ERP HCM system...............6
NAVIGATION 08: - Define Value Mapping Entities.................................................................................6
NAVIGATION 09: - Define Value Mapping details...................................................................................7
NAVIGATION 10: - Define Employee Data Settings for Employee Central Instance..................8
NAVIGATION 11: - Define Field Mapping of Employee Data...............................................................8
 BIB CONFIGURATION DOCMENT

ABOUT CPI (Cloud Platform Integration): -

 CPI Means Cloud Platform Integration and it allows to integration between cloud and on-
premises applications with third-party SAP and non-SAP products.
 It is used to Integration between SF EC to SAP Modules Like
A) SAP ERP,
B) S4 Hana
C) SAP Analytics Cloud
D) Third Party Application
 As a Integration Consultant this is the way to use SAP CPI to Integrate with other SAP,
Non SAP and SAP Success Factors do the integration form SAP

About Middleware: -
 It is a 3rd-party tool to connect two or more applications. These applications can be
cloud-based for Eg: -SAP CPI is the Middle Ware of SAP HR to SAP Succes Factors

BIB CONFIGURATION SET UP

There are a few Steps need to do the Configuration.

NAVIGATION 01: - Specify Employee Central Instance ID.

IMG-> Personnel Management -> Integration with SuccessFactors Employee Central ->
Business Integration Builder -> Basic Settings->Specify Employee Central Instance ID
 In This Step we will specify the Employee Central Instance ID and Description

Double Click on Specify Employee Central Instance ID

NAVIGATION 02: - Maintain the Constant Values

IMG-> Personnel Management -> Integration with SuccessFactors Employee Central ->
Business Integration Builder -> Basic Settings->Maintain the Constant Values

 Here we will add the SAP predefined Constant Values, to EC to ERP Replication
Below Constant Value is the Example.
Example 01 Constant Value: -
EC to ERP (BIB) / EC to ERP (Non-BIB): Simulation Mode (Test Mode): - To run the
replication in the test mode where the data is not saved in the data base. This Process is used to non-BIB and
Partial BIB Scenarios While doing the replication in Simulation.
 BIB CONFIGURATION DOCMENT

 Double Click on Maintain the Constant Values.

NAVIGATION 03: - Maintain the Constant Values based on Country /Region

IMG-> Personnel Management -> Integration with SuccessFactors Employee Central ->
Business Integration Builder -> Basic Settings->Maintain the Constant Values based on
Country /Region

 Here we will add the Constant Values based on the Country Specific or Region

NAVIGATION 04: - Allow Data Replication from EC for payroll Areas in Correction
Phase.
IMG-> Personnel Management -> Integration with SuccessFactors Employee Central ->
Business Integration Builder -> Basic Settings->Allow Data Replication from EC for payroll
Areas in Correction Phase.

 As per the above image wise, we will put the Check box in this configuration because
during the Replication from EC to ERP the above-mentioned payroll areas are needed to
allow the Replication.
 BIB CONFIGURATION DOCMENT
NAVIGATION 05: - Define Additional Foundation Objects for migration Data to EC
IMG-> Personnel Management -> Integration with SuccessFactors Employee Central ->
Business Integration Builder -> Basic Settings-> Define Additional Foundation Objects for
Migrating Data to EC

 Double Click on the Define Additional Foundation objects for Migrating Data to EC

 As per the Image, Wise SAP Delivers the Four Lists of Standard Foundation Objects which
are for Work Schedule, Pay Component, Pay Component Group, and Legal Entity.

 In this Table, We Can Define Additional Foundation Objects to Migrate from EC to ECP
using the Report ECPAO_TRANSFER_FO_OBJ_TO_EC.

Then Click on Execute

 Here we will specify foundation Objects in Which Instance, also country Group, WT and
Transport Request
 BIB CONFIGURATION DOCMENT
 After Defining the new Foundation Object, you must implement the BADI
EX_ECPAO_MAP_FOBJ_TRANS_TO_EC mapping the Corresponding EC Filed to the
Corresponding Foundation Object.

 Once we Activate the BADI Implementation, you need to run the

ECPAO_Transfer_FO_OBJ_TO_EC Report to Migrate that Foundation Object to EC

NAVIGATION 06: - Import Metadata for Web Service-Based Data Transfer from EC
IMG-> Personnel Management -> Integration with SuccessFactors Employee Central ->
Business Integration Builder -> Basic Settings-> Import Metadata from Employee Central -
>Import Metadata for Web Service-Based Data Transfer from Employee Central

Double Click on

 EC Meta Data File: - Meta Data File Contains such as field names and field descriptions
from SuccessFactors Employee Central into the ERP System. The Same File we will import
in the ERP System
 EC Entity: - It is nothing but to store the object Information

 List of Mandatory Templates and Info types which are required to Replication of Employee
Master Data.
1) WS_2(Biographical Info Template)
2) WS_3(Employment Info Template)
3) WS_4 (Job Info Template)
4) WS_5(Personal Info Template)
5) WS_11(Compensation Template).
Mandatory SAP ERP Info types:
IT0000(Events and Event reasons)
 BIB CONFIGURATION DOCMENT
IT0001(organizational assignments)
IT0002(personal information)

NAVIGATION 07: - Import Picklists from Employee Central to SAP ERP HCM system.
IMG-> Personnel Management -> Integration with SuccessFactors Employee Central ->
Business Integration Builder -> Basic Settings-> Define Value Mapping->Import Picklists
from Employee Central

 Here we will Import the picklist and Picklist Value from Employee Central to SAP ERP

 Double Click on import Picklist from Employee Central

 We must Export Data from EC in an XML File and the Same File needs to be imported into
the ERP System.
 Below is the Procedure: -
A) Select your EC Instance.
B) Choose your EC Picklist File from your local computer
C) Enter the locale of the picklist labels that you want to import.
D) Select the Update Picklist checkbox.
E) Execute it and picklist will be uploaded.

NAVIGATION 08: - Define Value Mapping Entities.

IMG-> Personnel Management -> Integration with SuccessFactors Employee Central ->
Business Integration Builder -> Basic Settings-> Define Value Mapping->Define Value
Mapping Entities

 Value mapping means we must Map the Employee Central field values to SAP ERP
HCM fields.
 BIB CONFIGURATION DOCMENT

 Double Click on Define Value Mappings Entities

Below is the Procedure: -

A) First, we will maintain the Value Mapping Entity and Description
B) Then we will maintain the Value Mapping Type, it means whether it is FO Objects or Picklists or Org Objects
C) ERP Field Value (Eg: - BUKRS, ANSSA)

NAVIGATION 09: - Define Value Mapping details

IMG-> Personnel Management -> Integration with SuccessFactors Employee Central ->
Business Integration Builder -> Basic Settings-> Define Value Mapping->Define Value
Mapping Details.

 In this Navigation we will specify that Define Value Mapping Keys of EC and ERP Keys
 BIB CONFIGURATION DOCMENT
Double Click on Define Value Mapping Details

NAVIGATION 10: - Define Employee Data Settings for Employee Central Instance
IMG-> Personnel Management -> Integration with SuccessFactors Employee Central ->
Business Integration Builder ->Employee Data Integration Define Employee Data
Settings for Employee Central Instance

 Double Click on Employee Data Integration

 As per the above image wise, we will define the EC Instance ID and ID Description then we
will do the Mapping of USER ID, USERNAME, PERSON ID, EMPLOYEMENTINTERNAL
TRANSFER.

NAVIGATION 11: - Define Field Mapping of Employee Data

IMG-> Personnel Management -> Integration with SuccessFactors Employee Central ->
Business Integration Builder –> Employee Data Integration Define field Mapping for
Employee Data.

STEP01: - Create the Transformation Template Group

 BIB CONFIGURATION DOCMENT
A) TRANSFORMATION TEMPLETE GROUP: - As Per the above image wise, we must Create a Transformation
Template Group, it is a Group bundle of all field mappings that we want to use when transferring the data.

B) EC INSTANCE: - Select the EC instance As Beam Production

C) COMMUNICATION CHANNEL: - We want to use the transformation template group for a CSV file-based or a
Web service, here we must Specify

D) SAMPLE CONTENT: - Which is Specified into Three Conditions as per the below image wise

E) EARARLIEST TRANSFER DATE: - You can specify this date to start data replication at a specific time. This
prevents the complete history of data records from being replicated.

STEP 02: - Transformation Template: - We Can define and assign one or more transformation Templates to the
Transformation Group.

As per the below Image wise, we will select Transformation Template ADDRESSES

Double Click on the ADDRESS and below are the Conditions: -

1) Active: - If we put the Tick mark to set the Template to Active and it is using it for Data Extraction Purpose.

2) Based on Hire Date: - If we put the Tick Mark in Based on the Hire DATE, the Template will be set in the Based-on Hire
Date.

3) Don’t Merge Records: - If we put the Tick mark it Indicates that the one employee info type Level Data migrated
Correctly, but the same employee has different Periods to be Merge for Data Transfer.

STEP 03: - Primary Mapping

 BIB CONFIGURATION DOCMENT

Select the EC Field and Double Click on that