Benefitfocus_Boomi_1602

Integration GuideSAP SuccessFactors Employee Central Document Version: Q1 2016 – 2016-01-15 CUSTOMER SuccessFactors Employee Central and Benefitfocus Dell Boomi Typographic Conventions Type Style Description Example Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options. Textual cross-references to other documents. 2 Example Emphasized words or expressions. EXAMPLE Technical names of system objects. These include report names, program names, transaction codes, table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE. Example Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools. Example Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation. <Example> Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system. EXAMPLE Keys on the keyboard, for example, F 2 or E N T E R . CUSTOMER © 2016 SAP SE or an SAP affiliate company. All rights reserved. SuccessFactors Employee Central and Benefitfocus Typographic Conventions Document History What's new Description More info Three new features are added, Custom Category Effective Date mapping, Pay Frequency and Termination reason Custom Category Effective Date mapping Employee Central must be implemented to enable SSO connections in Benefitfocus. Single Sign-On (SSO) January 15 2016 Added new features enhancements section Pay frequency Termination Reason August 21 2015 Updated the Prerequisites for Single Sign-On (SSO) SuccessFactors Employee Central and Benefitfocus Document History CUSTOMER © 2016 SAP SE or an SAP affiliate company. All rights reserved. 3 ..................................2 Configuration of Employee Central Identity Provider for Benefitfocus ..................2...........................................................................................1 1..........................................1...5.................................... 17 2...................................7 Compensation Information [EC hris-element-id: compensationInfo ] .............................................................................................................................................................. 39 Business Add-In HR_ECPINTEP_BEN_DATE_OR .................................................................................... 11 2......2........ 29 2..............................2 1......................1......................................5 Email Information [EC hris-element-id: emailInfo] ..............................................1 Integrating the Benefitfocus UI ............. 6 Benefits Business Process with Benefitfocus.................................................................................................................................2 Personal Information [EC hris-element-id: personInfo] .............................................2............2........ 48 Getting Access to the Integration Pack ................................... 39 Benefits Data Mapping ..............................................................3 2...........2..4 Phone Information [EC hris-element-id: phoneInfo] ..3 Address Information .................5 2..................... 35 3........2............................................................................................ 25 2..........4 2.....................................................................................1 Extensions for Connection Settings ..............................................3 4...........................................................................................................................................................................................1.3 Configure My Benefits Link for Benefitfocus . 35 3..................... 35 3.................13 2.....5 Data Maps ............................1.................................2.........35 Single Sign-On (SSO) .........................................................................5.............2 Configurations for Employee Central OData API ............................................... 49 Configuring and Using the Integration Pack ...............................9 Emergency Contact Information ...... 6 Integration Options........................................................1........................................ All rights reserved............................................. 49 Setting Up the Standard Data Integration...... 8 2 2.......1 Employee Data Replication.............................. 10 2.........................................................................4 PGP Encryption .............1......................4 4................................6 3 3....................................................... 22 Setting Up the Standard Data Integration................................................................................ SuccessFactors Employee Central and Benefitfocus Contents ..................2......................................15 2......... 11 2..........................................................................................................................Contents 1 1...... 7 Overview of Payroll Export Process ......................................19 Getting Access to the Integration Pack ...........................16 2...................................1 Employee Central Certification for Benefitfocus .............................. 24 2.. 9 Prerequisites ......................... 10 Integration Specification....................1 Configurations for Employee Central API Compound Employee .........................................................................8 National ID Card . 9 2.................................................................. 50 4.....................2 4.......2 Process Properties................... 42 Integration Process Overview .......................................... 32 2...................................................................... 39 4.1 Processing Custom Fields Using Business Add-Ins.......................................3 Preparations Required at Third-Party Provider's End ..................................12 2...............................................................5 4.....................................................16 2...............5...... 33 2................................14 2...............................5................1........2....18 Integration Process Overview ....................3 Cross-Reference Tables ..................................................................................................................................3 Benefitfocus Integration Overview ............. 9 2........... 32 Extending the Standard Data Integration.......................................2 2..................................................................6 Employment Information [EC hris-element-id: employmentInfo] .....1 Person Information [EC hris-element-id: personInfo] .............. 36 4 4......................1 Benefits Data Replication..............................................................5..... 24 2................6 4 CUSTOMER © 2016 SAP SE or an SAP affiliate company................... ...........................................................................................7..3 Cross-Reference Tables ..........................50 4..................54 4.......................................................................................................56 Configuring the Wage Types ...............................................................................2 401(k) Saving Plan Processing............. 61 Termination Reason ......................................................................................54 4..7 SuccessFactors Employee Central and Benefitfocus Contents CUSTOMER © 2016 SAP SE or an SAP affiliate company................... 55 4.............................................2 5...............7................3 Pay Code Wage Type Mapping................................................................62 4....... 60 Custom Category Effective Date mapping ......6...............58 5 5..............................................1 Health/Insurance/Credit/Disability/FSA Plan Processing .................................................4................................. 60 Pay frequency.............................................................................6...........................................................................................................1 5...........................................................................................6.....8 4............. All rights reserved..2 Process Properties ..........7................1 Extensions for Connection Settings ............................................................ 52 4.......................... 5 .............3 New Features and enhancements ............. 53 Data Replication Details .................................. 2. EC sends Benefitfocus the complete data about an employee. Make third-party provider-specific settings. 1.1 Integration Options Use the following steps as a guideline to successfully integrate EC with the benefits providers. Benefitfocus has the following user roles: · Employees: Access Enrollment System · Benefits Administrator: Access Manager Tools · System Administrator: Access Data Exchange · Finance Administrator: Access Billing Note If the integration does not meet the customer's integration requirements. SuccessFactors Employee Central and Benefitfocus Benefitfocus Integration Overview . Get access to the integration pack.com/hr_ec. you will need to adjust these processes. contact SuccessFactors Integration Customer Support and provide a description of the requirements not met by the integration pack. see the Employee Central Implementation Guide. insurance carriers and government entities cloud-based technology to shop. 3. Benefitfocus then sends updates to EC Payroll as required for legal reporting. · 6 CUSTOMER © 2016 SAP SE or an SAP affiliate company. This is an out-of-box integration that requires no manual data mapping. Set up EC. If a customization can satisfy the specific non-standard requirements. Integration is through a standard integration pack for validated third-party benefits providers. Benefitfocus provides employers. see the Employee Central Payroll Implementation Guide on SAP Help Portal at http://help. Using the Integration Solution As an Integration Pack 1. consumers. enroll. Set up the standard data integration. Depending on your customer's business requirements. and exchange benefits information. for example. single sign-on (SSO). 4. All rights reserved. This is a simplified approach to a possible integration process. For more information about EC. manage.1 Benefitfocus Integration Overview This guide is for Professional Services and SAP or partner consultants to integrate SuccessFactors Employee Central (EC) with Benefitfocus. Employees can choose their benefits plans in an online portal with integration to EC. However. For more information about EC Payroll. Benefitfocus then updates the benefits providers daily about any changes that may have occurred. see the Employee Central Implementation Guide. please note that ongoing updates to the integration pack will not flow into your custom copy. a copy of the process will be made available through the process library.sap. For more information about EC. 2 Benefits Business Process with Benefitfocus The Benefitfocus process template is available in the master Boomi account. the customer’s account manager must notify the production support team at Benefitfocus before generating the additional files. The file must adhere to the record type sequencing rules to ensure the file loads properly.1. The Benefitfocus process was designed to detect differences and compare full files to the population stored in Online Enrollment. Inbound payMax files are always Full Files. This is to ensure that existing files are not overwritten. Note This integration only works for country US since Benefitfocus does not support other countries yet. You can copy the process template from this master account and adapt it to individual client requirements. it should not be made visible on the Benefitfocus system SuccessFactors Employee Central and Benefitfocus Benefitfocus Integration Overview CUSTOMER © 2016 SAP SE or an SAP affiliate company. The integration is done via a CSV file on the SFTP Benefitfocus Server which is called inbound payMax file. there is a need on a single day to send files multiple times to Benefitfocus that need to be processed separately or differently. If EC is the system of record. A Full File contains the employer’s entire employee population and includes all data for each employee in the payroll/HRIS system. The inbound payMax file contains two record types that include both file and member identifying information. In the provided Boomi process template only the required (subset) of the paymax file fields are mapped. then it is required for all the Benefitfocus fields to be read-only. In case one of the mapped fields is not required. for technical or business reasons. Note If. 7 . All rights reserved. Employers are typically able to provide full files much more easily than changes only files. The specific record types are included in the following list: · payMax Header · Employee Detail Record The payMax Header record is followed by one or many Employee Detail records. 1.3 Overview of Payroll Export Process This section details the integration between Benefitfocus and EC Payroll. EC is the system of records for an employee and the required details / eligibility data will flow from EC to the third-party provider (outbound integration). Based on the eligibility information/personal data of an employee, benefits plans are offered to an employee by the benefits provider. An employee elects into a benefits plan by logging into the provider's application through SSO and the provider will completely process the benefits plans based on the election information of an employee and sends the deduction information to the payroll system to be accounted in calculation of remuneration. The deduction coming from the provider for an employee can be a pre-tax contribution or a post-tax contribution and payroll will accordingly process the information as per the legal rules defined for these plans. Some benefits plans, for example, 401(k), need special processing as per the legal rules defined by the federal government, for example, how the pre-tax and post-tax contribution for 401(k) should be handled and how the contribution should be processed for the 401(k) plan once the pre-tax limit is reached. Most of the special processing is to be handled during actual payroll execution, that is, during processing remuneration and tax calculation. So to be compliant with legal rules on processing such plans, we are using benefits engine on EC Payroll to process the plan as per the legal rules and also EC Payroll is already designed to handle such plans. So keeping legal rules and processing in mind, only the following plans will be processed using benefits engine: 401(k) plan (savings plan). For the rest of the plans, that is, health, credit, disability, FSA, and insurance plans, infotype 14 and infotype 15 are used to process benefits plans based on whether it is a periodic deduction or a one-time deduction. Infotype 14 is recurring payments/deductions and infotype 15 is for additional one-time payments/deductions. 8 CUSTOMER © 2016 SAP SE or an SAP affiliate company. All rights reserved. SuccessFactors Employee Central and Benefitfocus Benefitfocus Integration Overview 2 Employee Data Replication The replication of employee master data from EC to Benefitfocus uses the Compound Employee service from EC and the Benefitfocus payMax file which contains the required Benefitfocus elements. For information on Compound Employee Element structure … See EC HRIS-element Person Information Person Information [EC hris-element-id: personInfo] Personal Information Personal Information [EC hris-element-id: personInfo] Address Information Address Information Phone Information Phone Information [EC hris-element-id: phoneInfo] Email Address Information E-mail Information [EC hris-element-id: emailInfo] Employment Information Employment information [EC hris-element-id: employmentInfo] Pay Component Recurring Pay Component Recurring Information [EC hris-element-id: paycomponentRecurring] National ID Card National ID Card 2.1 Prerequisites 2.1.1 Configurations for Employee Central API Compound Employee The Employee Compound Application Programming Interface (API) for EC pulls employee data out of EC. It returns employee data in a hierarchically structured response XML (root node: employee person data). Choose your regional API endpoint from the table below: Location End Point Europe https://api.successfactors.eu/sfapi/v1/soap USA, New Jersey https://api.successfactors.com/sfapi/v1/soap USA, Arizona https://api4.successfactors.com/sfapi/v1/soap Get the generic WSDL by adding ?wsdl to the above addresses. For example, https://api.successfactors.eu/sfapi/v1/soap?wsdl SuccessFactors Employee Central and Benefitfocus Employee Data Replication CUSTOMER © 2016 SAP SE or an SAP affiliate company. All rights reserved. 9 Apart from the endpoints, an XML schema is provided that describes the XML response of the compound API including all substructures and elements. The XML schema is required for integration purposes. It needs to be maintained manually as part of the development process. The new API will only provide the query and the queryMore operation. All other operations such as list, describe, and describeEx are not supported. You may have to make more settings for the following: · Webservice setup Follow the standard process for SF APIs to set up SFAPI operations login and logout and to enable the API. · Thresholds and limits The API compound Employee has similar thresholds and limitations as the other SFAPIs. You can set this number to a value between 1 and 800 by specifying the maxRows parameter in the query method. · API enhancements and compatibility The API response message type can be enhanced with additional elements and attributes. Additional elements and attributes can be supplied by SAP or SuccessFactors and by using custom fields. The external application must be able to process the extended response successfully. The API request message type can be enhanced by new processing and query string parameters (for example, an additional parameter for selecting or filtering data). Enhancements of request message types and parameters are always optional. The system does not require the external application to provide optional values and parameter in the request. 2.1.2 Configurations for Employee Central OData API Some EC data is fetched using the Employee Central OData API. To extract this data, you must enable the OData API. Prerequisites · You have enabled the OData API via Provisioning. · The API user has admin access for the OData API. This permission can be granted in Admin Tools. For more information about OData API configurations, see the SuccessFactors HCM Suite OData API User Guide. Note Currently, location data is fetched via OData API. If you want to use location data, it is mandatory to configure the OData API. 2.1.3 Preparations Required at Third-Party Provider's End Once a customer opts for particular third-party provider integration, he should sync on the following points for initial setup preparations to be done at a third-party provider's end: · Functional Preparation For example, availability of a document like 'Discovery and Requirements Gathering' · 10 Group and Benefits Plan Setup CUSTOMER © 2016 SAP SE or an SAP affiliate company. All rights reserved. SuccessFactors Employee Central and Benefitfocus Employee Data Replication 11 . Examples of categories can be location. the employee is not sent to Benefitfocus. Note Categories are used by Benefitfocus to identify different classes or subgroups of employees at the carrier or employer. or configure administrator permissions. All rights reserved. They also show which fields you need to map manually and the corresponding picklist IDs. If the data for an employee does not satisfy the length constraint. Categories can be used to configure rates.o Technical Setup of Employee File For example. enable benefits. etc. Note The data types used in this document (column Type in the following tables) are as follows: A = Alphanumeric N = Numeric D = Date T = Time M = Monetary 2.2.2 Integration Specification The following tables list the EC fields required to replicate EC data using middleware to Benefitfocus.1 Person Information [EC hris-element-id: personInfo] EC hris Field Description Obligatory for Replication Code Mapping Required Picklist ID Benefitfocus Attribute Type Max Length date-of-birth Date of birth X Date of Birth 8 D External Person ID X Employee ID 19 A person_id_external No further mapping activities are required for these fields. division. department. SuccessFactors Employee Central and Benefitfocus Employee Data Replication CUSTOMER © 2016 SAP SE or an SAP affiliate company. availability of documents like 'Integration and Data Migration Discovery' o SFTP Server configuration 2. Note The length constraints of Benefitfocus specified in the following tables (Max Length column) must be considered on the EC side when maintaining employee data for the respective fields. Also provided are descriptions of the mapping activities that are required for different fields. 2. 12 CUSTOMER © 2016 SAP SE or an SAP affiliate company.2 Personal Information [EC hris-element-id: personInfo] EC hris Field Description Obligatory for Replication Code Mapping Required Constraint /Constant Value Picklist ID/ CrossReference ID Benefitfocus Attribute Max Type Length gender Gender X Gender 1 A X First Name 50 A firstName Given name Family name X Last Name 50 A lastName Middle name X Middle Name 50 A middleName Marital status X ECBFBenefitfocus Marital Status Marital Status 10 A Suffix X X ECBFBenefitfocus Name Suffix Suffix 10 A X ECBFBenefitfocus EEO Categories EEOC 50 A Name Change Date 8 D marital-status suffix X Current Date gender The outbound service sends the values M = male and F=female.2. Don't associate this field with a picklist. The values are automatically mapped to the Benefitfocus CSV File via the XML Profile. In this case. no additional mapping in the middleware or the inbound service is required. Default mapping values are available. All rights reserved. Marital-status These values are mapped in Boomi via the cross-reference table ECBF ECtoBenefitfocus Marital Status. This table is defined as an extension table in Boomi and must be filled by the consumer based on the picklist and the Benefitfocus values. suffix The field suffix is mapped to the Benefitfocus field Suffix via a cross-reference look-up. SuccessFactors Employee Central and Benefitfocus Employee Data Replication . A 13 . Name Change Date The field Name Change Date of Benefitfocus is currently mapped to be set to the current Date.2.2. These values are mapped in Boomi via the cross-reference table ECBF-Benefitfocus Ethnicity.Employee suffix valid values. EEOC These values are mapped in Boomi via the cross-reference table ECBF-Benefitfocus EEO Categories. 2. See also Benefitfocus Payroll Integration Inbound Specifications . This table is defined as an extension table in Boomi and must be filled by the consumer based on the picklist and the Benefitfocus values.3 Address Information EC hris Field Description addresstype Address type address1 Address field 1 Obligatory for Replication Code Mapping Required Constraint Value SuccessFactors Employee Central and Benefitfocus Employee Data Replication Benefitfocus --------------------------------Attribute Max Type Length 'HOME' X Picklist ID/ CrossReference ID addressType Address Line 1 50 CUSTOMER © 2016 SAP SE or an SAP affiliate company.2. All rights reserved.1 Personal Information USA [EC hris-element-id: personInfo] EC hris Field Description Obligatory for Replication Code Mapping Required Picklist ID/ CrossReference ID ECBFBenefitfocus Ethnicity genericString1 Benefitfocus Attribute Max Type Length Ethnicity 20 A Ethnicity The field genericString1 is mapped to the Benefitfocus field Ethnicity via a cross-reference look-up.These values are mapped in Boomi via the cross-reference table ECBF-Benefitfocus Name Suffix.This table is defined as an extension table in Boomi and must be filled by the consumer based on the picklist and the Benefitfocus values. 2. This table is defined as an extension table in Boomi and must be filled by the consumer based on the picklist and the Benefitfocus values. In the Boomi mapping.2.EC hris Field Description Obligatory for Replication Code Mapping Required Constraint Value Picklist ID/ CrossReference ID Benefitfocus --------------------------------Attribute Max Type Length Address field 2 optional Address Line 2 50 A address2 city City X City 50 A state State X State 2 A zip-code ZIP code X ZIP Code 10 A Country X Country 3 A X Code country Address Type In the case of address information. and a phone number with type B (business) to WorkPhone. a phone number with type C (cellphone) to CellPhone. No further mapping is required. a constraint in Boomi only transfers the address type home to Benefitfocus. City The EC field City is mapped directly to the corresponding field City in the payMax file. SuccessFactors Employee Central and Benefitfocus Employee Data Replication . a script maps a phone number with type H (home) to HomePhone. No further mapping is required. All rights reserved. a constraint in Boomi transfers the phone information according to phone_type. 2. No further mapping is required. This user-defined function uses Groovy script to identify null values and return only the non-null values. 14 CUSTOMER © 2016 SAP SE or an SAP affiliate company. State The EC fields state and province are mapped to the field State in the payMax file via a choose non-null field function.4 Phone Information [EC hris-element-id: phoneInfo] In the case of phone information. Country There is direct mapping to the corresponding Country Code. ZIP Code There is direct mapping to the corresponding field ZIP Code. 3. H. This user-defined function builds a 10-digit phone number by using both the area code and phone number. and an email address with type B (business) to Work Email.2. a constraint in Boomi transfers the email information according to email_type. Right Character Trim The phone number is trimmed from the right while keeping the length fixed to 10.5 Email Information [EC hris-element-id: emailInfo] In the case of email information. String Remove Any unwanted characters are removed. 2. 15 . EC hris Field emailaddress emailtype Description Email address Obligatory for Replication Code Mapping Required Constraint Value X Email address type Picklist ID/CrossReference ID Benefitfocus Attribute Type Max Length Personal Email /Work Email 50 A P= Personal B = Business email-type The EC field email-address is mapped to the field Personal Email/Work Email in the payMax file according to email-type. 2.EC hris Field Description phone_type Obligatory for Replication Code Mapping Required Phone type X Phone number X Constraint Value Picklist ID/ CrossReference ID Benefitfocus -----------------------------------Attribute Max Type Length C. In the Boomi mapping. String Append The phone number is appended to the area code. a script maps an email-address with type P (personal) to Personal Email. B HomePhone /CellPhone/ WorkPhone phone_number 10 N Phone Number The EC fields area_code and phone_number are mapped to the fields HomePhone/CellPhone/WorkPhone (depending on phone_type) in the payMax file via a build 10-digit phone number function. This is achieved in 3 steps: 1. All rights reserved. email-type can have the following values: SuccessFactors Employee Central and Benefitfocus Employee Data Replication CUSTOMER © 2016 SAP SE or an SAP affiliate company. Picklist ID Benefitfocus Attribute Max Type Length Earning Amount Effective Date 8 D SuccessFactors Employee Central and Benefitfocus Employee Data Replication .2.· P = Personal · B = Business 2. 2.6 Employment Information [EC hris-element-id: employmentInfo] EC hris Field Description Obligatory for Replication Start Date Start Date X End_date End Date X Code Mapping Required Picklist ID Benefitfocus Attribute Max Type Length Date of Hire 8 D X Termination Date 8 D X Termination Reason 1 A Benefitfocus Termination Reason and Termination Date Only in cases where end_date is maintained and the EC field emplStatus is not active (A). and the field Termination Reason of Benefitfocus set to value V (Voluntary). is the field Termination Date of Benefitfocus directly mapped to EC field end_date.7 Compensation Information [EC hris-element-id: compensationInfo ] EC hris Field Description Obligatory for Replication Code Mapping Required Start Date start_date 16 CUSTOMER © 2016 SAP SE or an SAP affiliate company.2. All rights reserved. 8 National ID Card EC hris Element nationalIdCard EC hris Field nationalid Description National identification Obligatory for Replication Code Mapping Required X X Picklist ID Benefitfocus Attribute Max Type Length Social Security Number (SSN) 9 N National ID Card The EC field nationalIdCard is mapped to the field Social Security Number(SSN) in the payMax file via a string remove function. 17 .2.7. This function removes the hyphens '-' from national-id. 2.2. All rights reserved. SuccessFactors Employee Central and Benefitfocus Employee Data Replication CUSTOMER © 2016 SAP SE or an SAP affiliate company. It has to be set before running the replication process.2.1 EC hris Field Pay Component Recurring Information [EC hriselement-id: paycomponentRecurring] Description Obligatory for Replication Code Mapping Required Constraint/ Constant Value Picklist ID/CrossReference ID X X Salary 11 M X Pay Frequency 15 A Earning Unit of Measure 20 A ANNUAL Benefitfocus Attribute Max Type Length Salary The following EC fields are mapped to the field Salary in the payMax file via a calculate annual salary function: · Pay_component_type · Pay_component · paycompValue · frequency · annualizationFactor Pay Frequency This field is mapped to the process property Pay Frequency that can be set under the ECBF-General Settings extension. All rights reserved. No further mapping is required.9 EC hris Element Emergency Contact Information EC hris Field Description name 18 Obligatory for Replication X Code Mapping Required Benefitfocus Attribute Max Type Length Emergency Contact Name 50 A relationship Emergency Contact Relationship 20 A Phone Emergency Contact Phone 10 N Second_phone Emergency Contact Alternate Phone 10 N address1 Emergency Contact Address Line 1 50 A address2 Emergency Contact Address Line 2 50 A city Emergency Contact City 50 A state Emergency Contact State 2 A zip_code Emergency Contact Zip Code 10 A CUSTOMER © 2016 SAP SE or an SAP affiliate company.Note national-id is obligatory for replication. X Picklist ID SuccessFactors Employee Central and Benefitfocus Employee Data Replication .2. 2. This process property can be used to filter the EC Compound Employee data set (comma-delimited custom filters for the CompoundEmployee document can be supplied in the format "person/national_id_card/country=USA.person/person_id=117". This user-defined function uses Groovy script to identify null values and return only the non-null values.GRE. SuccessFactors Employee Central and Benefitfocus Employee Data Replication CUSTOMER © 2016 SAP SE or an SAP affiliate company. this process creates the Header and Detail records.This process builds the WHERE clause that can be used with any query which is a part of this process.3 Integration Process Overview The mapping of the EC fields to the third-party provider’s field requirements is done via the Boomi process. etc. Combines the header and detail records into a single document (Combine Docs step).EC hris Element EC hris Field Description Obligatory for Replication Code Mapping Required country Picklist ID Benefitfocus Attribute Max Type Length Emergency Contact Country 3 A Emergency Contact State The EC emergency_contact_information fields state and province are mapped to the field Emergency Contact State in the payMax file via a choose non-null field function. All rights reserved. 2. Sets the Custom Filter process property to the process.As the name indicates. The following graphic depicts the overall process to send employee data from EC into the Benefitfocus SFTP Server in Boomi. The file name is set using the set properties component. Broadly. o Sub: ECBF payMax Header and Details: . 3. The following section explains how information is mapped from EC to the third-party provider using Boomi as the middleware. the steps in the main process of Benefitfocus payMax are: 1.) 2. o Sub: ECBF – Build Query Filter: . Calls the following subprocesses. 19 . Finally. all other details of the employee remain the same. CUSTOMER © 2016 SAP SE or an SAP affiliate company. separate documents are generated for each assignment. the PGP Encryption of the file is skipped. It splits the document based on employment information. ECBF Compound Employee to Benefitfocus payMax Details 1. This is done for testing purpose. ECBF payMax Header and Details 1. It filters out future global assignments. It queries EC based on the aforementioned WHERE. All employee detail records are combined into a single document. which is the default behavior. All rights reserved. If no value is passed. 3. After separating the home and host assignments. SuccessFactors Employee Central and Benefitfocus Employee Data Replication . then PGP Encryption takes place. This process makes a call to the subprocess Sub:ECBF Compound employee to Benefitfocus payMax Details to generate the detail records. 20 1. 2.4. This process calls the subprocess Sub: Cache for CompoundEmployee Fixup that queries the required data and caches it in case it is needed further down the process. 2. It makes the subprocess call Sub:Handling Global Assignment to handle global assignment information. only employees with either home or host assignment in USA are accepted. So if an employee has global assignments. only the employment information is different. Thus. If the value TEST is passed. 3. the file is written to a SFTP location. only the assignments with legal entity country USA are accepted and sent for further processing. The header file is also generated and then both these files are returned to its immediate parent process ECBF 1308-Benefitfocus payMax File. 2. In these documents. The process is then routed based on the Process Property File Encryption Mode. 3. SuccessFactors Employee Central and Benefitfocus Employee Data Replication CUSTOMER © 2016 SAP SE or an SAP affiliate company. or the terminations are lost. For such records. Note On the next execution of the process. After the mapping. All rights reserved. and the termination reason is picked from the lookup reference table of Employee Central. Then the record is sent for mapping. 5. For each record returned by the query. the process branches two ways: o For every record. If the record is not found. the records are combined and returned to the immediate parent process Sub:ECBF payMax Header and Details. o The current logic at this step is to detect the employee missing from the payMax file compared with the prior file (the last file is cached each execution). You can check these logs by choosing Manage → Process Reporting. The person_id_external is also logged. The accepted records are checked with the history using the Find Changes component. it is checked if the log_item is not null. Select the executed process and choose View Process Logs. Note If the mapping fails for a particular employee record. the log item along with its message text is logged. this employee is not included with a termination status. the document property EMP_STATUS is set to T. the document properties EMP_STATUS and END_DATE are set to default values as expected from the query. The records are filtered based on all the filter condition values supplied and the document property FILTERMATCH. It makes the subprocess call Sub:CompoundEmployee Filter Matcher. the person_id_external is logged. it is added to the find changes cache and that record is notified to the user as a deleted record. So it is important that each consecutive file runs against Benefitfocus. Here. Only the records that pass the specified criteria are processed and the rest are rejected. If no value in the lookup reference table is maintained then a blank value is picked from the table.4. 21 . with a termination date of today. If true. each consisting of one or more published Boomi processes. Once an integration pack is released. Navigate to Manage → Atom Management 7. In the Deploy tab. It assumes that an environment has been created in the customer account and attached to the Boomi Cloud. configure and monitor an integration pack. Prerequisites · The user account must have the appropriate permissions to deploy. For the current solution. This integration pack contains the required mapping between the EC data fields and the corresponding fields in the inbound structure of the Benefitfocus system. 2. Log into the customer Boomi account at http://platform. lets you install integration packs in your account. Integration pack building and release is performed in a master account. 3. 5. · The customer Boomi account must be provisioned for access to both the integration pack and the Atom Cloud where it will be deployed. SuccessFactors Employee Central and Benefitfocus Employee Data Replication . the user administering the integration pack shares it with selected account groups they manage. 8. which is accessible from the Deploy page in Boomi.boomi.You can then filter the logs by type. Data only travels in one direction. 2. Only the EC data is sent to Benefitfocus. Click the Integration Pack previously added to the account. All rights reserved. Connection Settings for SuccessFactors System 9. Click Environment Extensions on the right-hand side. 4. click the + on the Integration Pack section on the lower left size. Choose the environment on the right-hand side and click << to "attach" the Integration pack to the selected environment. Deploying the Integration Pack 1.4 Getting Access to the Integration Pack Integration packs are packaged integration solutions. Click Environment on the left-hand side. you can attach Atoms or environments to it and then run any of its processes from the Deployed Processes tab in Atom Management. SAP delivers an integration pack for the Boomi middleware.com using the user name and password. The Extensions pop-up appears. 6. CUSTOMER © 2016 SAP SE or an SAP affiliate company. You can monitor the release status of installed integration packs and apply pending updates from the Integration Pack Versions tab in Atom Management. Once you install an integration pack. which handles the mapping for all standard employee data fields. Click the view and navigate through to install the integration pack. 22 Deselect the Use Default? flag to add customer-specific input. The Browse Integration Packs dialog. If accessing a server other than the default. 11. 23 . All rights reserved. Select the Benefitfocus connection from the Connection List. SuccessFactors Employee Central and Benefitfocus Employee Data Replication CUSTOMER © 2016 SAP SE or an SAP affiliate company. enter the WSDL and endpoint URLs.To configure the SuccessFactors connection to Benefitfocus you can fill the following entries: · Endpoint: Datacenter · Company ID: Customer EC Company ID · Username and Password: API User and Password that have the permission to retrieve the data from API Configuring Web Service Connectivity 10. make the following entries: 24 CUSTOMER © 2016 SAP SE or an SAP affiliate company.5.2.1 Extensions for Connection Settings Benefitfocus SF-API Connection To configure the SuccessFactors connection to benefits provider.5 Setting Up the Standard Data Integration 2. SuccessFactors Employee Central and Benefitfocus Employee Data Replication . All rights reserved. fill out the following entries: · Endpoint: Datacenter · Company ID: Customer EC Company ID · Username and Password: API User and Password that have the permission to retrieve the data from API Benefitfocus SFTP Server Connections To configure the process to connect to the Benefitfocus SFTP server. General Settings You can set the following general properties: Property Description Pay Frequency Pay Frequency field of Benefitfocus file Benefitfocus Client ID Client ID for the Benefitfocus account/tenant SFTP Directory Directory on Benefitfocus server where the file is saved SFTP File Name Name of the target Benefitfocus file. The date is automatically appended to the file name along with the . File Encryption Mode Specifies the type of deployment. DEMO sends to a Disk Connector on a local atom. Demonstration mode writes to a local Atom's work file folder. All rights reserved. To configure the process properties.Field Description Host Hostname of Benefitfocus SFTP server Port Port of Benefitfocus SFTP server User/Password User and password for Benefitfocus SFTP server 2. Other modes send to Benefitfocus SFTP server either encrypted or unencrypted.5.2 Process Properties The process properties contain customizing options. SuccessFactors Employee Central and Benefitfocus Employee Data Replication CUSTOMER © 2016 SAP SE or an SAP affiliate company.csv extension. you can override the default values. 25 . ) employee_class Comma-delimited list (no blank spaces before/after comma) for specifying the employee classes to include in the extract regular_temp Include regular or temporary employees employment_type Include employees with a particular employment type location Include the foundation object externalCode if you want to include only employees associated with that foundation object company Comma-delimited list (no blank spaces before/after comma) for specifying the companies to include in the extract company_territory_code Comma-delimited list (no blank spaces before/after comma) for specifying the single company_territory_codes to include in the extract business_unit Include the foundation object externalCode if you want to include only employees associated with that foundation object Custom Filters Comma-delimited custom filters (no blank spaces before/after comma) for the CompoundEmployee document in format CUSTOMER © 2016 SAP SE or an SAP affiliate company. (This is a pay_group in job information and not in compensation information. The following filters are available for the current integration process: 26 Filter Description is_fulltime_employee Include only full-time employees pay_group Include the foundation object externalCode if you want to include only employees associated with that foundation object. you can change the same under the process properties of the Boomi process. SuccessFactors Employee Central and Benefitfocus Employee Data Replication .Filter Options To fetch data based on a particular filter. All rights reserved. All rights reserved. all (max 6) are included. etc. If blank.person/person_id=117" . person_id_external Comma-delimited list (no blank spaces before/after comma) for specifying the person_id_externals to include in the extract Terminate Filtered Employees Include newly filtered employees as terminated. 27 . Include Terminations Determines how long terminated employees should be included in the payMax file before they are excluded SuccessFactors Employee Central and Benefitfocus Employee Data Replication CUSTOMER © 2016 SAP SE or an SAP affiliate company.GRE. one time Pay Components Comma-delimited list (no blank spaces before/after comma) of pay component IDs to include in calculating annual salary.Filter Description "person/national_id_card/country=USA. All rights reserved.28 CUSTOMER © 2016 SAP SE or an SAP affiliate company. SuccessFactors Employee Central and Benefitfocus Employee Data Replication . 3 Cross-Reference Tables The cross-reference tables are translation tables between the EC picklist entries and the Benefitfocus values. and in the second column the Benefitfocus suffix. All rights reserved. For example: · Field: Custom Category Type 1 · Value: Location 2.Custom Category Types You can use this extension to map a particular custom category type to a particular EC field. Navigate to Manage → Atom Management. The Extensions pop-up appears. Click Environment on the left-hand side. Below is an example of how you can customize a gender code mapping. Select the cross-reference to be changed from the dropdown. Click Environment Extensions on the right-hand side. SuccessFactors Employee Central and Benefitfocus Employee Data Replication CUSTOMER © 2016 SAP SE or an SAP affiliate company. 1. 5. enter the EC suffix code. 3. The following cross-reference tables are available: o Suffix: In the first column. 2. 4.5. Fill out the cross-reference tables to add or override the existing values. 29 . Click Cross Reference. o EEOC categories: In the first column. and in the second column the Benefitfocus ethnicity. and in the second column the Benefitfocus EEOC. 30 CUSTOMER © 2016 SAP SE or an SAP affiliate company.o Ethnicity: In the first column. enter the EC ethnicity code. All rights reserved. SuccessFactors Employee Central and Benefitfocus Employee Data Replication . enter the EC EEOC code. and in the second column the EC pay frequency. o Pay Frequency: In the first column.o Marital Status: In the first two columns. and in the next two columns the Benefitfocus marital status and description. enter the Benefitfocus pay frequency. 31 . enter the EC marital status and description. SuccessFactors Employee Central and Benefitfocus Employee Data Replication CUSTOMER © 2016 SAP SE or an SAP affiliate company. All rights reserved. · Mappings cannot be “unmapped”. All function types except user-defined functions are available. only those with single-record formats. that is. and other function-type actions are not supported. · Only mappings using XML or flat file profiles are supported and. · If the original maps contain map functions. However. In other words. 32 CUSTOMER © 2016 SAP SE or an SAP affiliate company.5. Mapping overrides are displayed as black lines. You can see all of the mappings defined in the original map(s). The mapping controls are similar to those in the map component creation interface. SuccessFactors Employee Central and Benefitfocus Employee Data Replication . These field mapping extensions are subject to the following limitations: · You cannot select different source or destination profiles.4 PGP Encryption You can change the following settings to use a certificate for the PGP encryption of the output file of the integration process. · For function types that require a separate component. You can add functions to data map extensions. which is drag-and-drop. replaced. · You cannot add cached data to the source profile. you can view but not change the configuration and default values of the map functions. advanced mapping logic including transformations. For example.5. The Simple Lookup function type can be used to return a single value. All rights reserved. You can map to destinations that have already been mapped in the original maps. they will be displayed in gray indicating they are disabled. you cannot map to a destination that has already been mapped by an override mapping. These mapping lines are displayed in a light orange color. 2.2. conditional scripting. in the case of flat file profiles. destination fields mapped from map functions in the underlying map cannot be customized. or overridden when the process is deployed.5 Data Maps The earlier type of data maps allows field-to-field mapping defined by map components within a process to be augmented. but you cannot change the mappings. such as connection and operation components in connector calls. you can select only components that are defined in the original process. · Only simple field-to-field mappings are supported. This type of extension applies only to the map component for which the extension is defined. 33 . All rights reserved. The second type of data map extension allows the addition of fields to flat file profiles used in map components within a process when the process is deployed. 2. SuccessFactors Employee Central and Benefitfocus Employee Data Replication CUSTOMER © 2016 SAP SE or an SAP affiliate company. followed by functions in the Extensions dialog. The profiles must have single-record formats.6 Extending the Standard Data Integration This section describes the cases where a customer wants to enhance the current solution and to add some custom fields. the Map Step of the Boomi process needs to be changed to adjust the 10 User Defined fields. To make changes. In this case. the customer may choose to map the required field from EC to the destination fields. you must be familiar with the following topics: · Boomi process development · EC compound APIs Example Consider an example where a customer wants to enhance the current process to adjust 10 custom fields in the destination file. as opposed to multiple or nested-record formats. Once the fields are introduced. Functions in the original maps are processed first. other maps that use the same profile are not automatically extended. · The Map Function Ordering dialog is not available.· You cannot add default values to the destination profile. SuccessFactors Employee Central and Benefitfocus Employee Data Replication .34 CUSTOMER © 2016 SAP SE or an SAP affiliate company. All rights reserved. 1 Employee Central Certification for Benefitfocus The following information is used by.1 Single Sign-On (SSO) This section describes how you can configure an SSO connection to Benefitfocus. select the company and choose Authorized SP Assertion Consumer Service Settings. In Provisioning.2 Configuration of Employee Central Identity Provider for Benefitfocus To set up an SSO connection. the following steps must be completed in Employee Central. as a part of the integration to Benefitfocus. Procedure 6. and already in place with Benefitfocus for SSO configuration: · Issuer ID www. Prerequisites A provisioning user for a respective SuccessFactors tenant is needed to maintain the SSO configuration.1. Prerequisites Access to Provisioning is required for the EC company. Employee Central must be implemented to enable SSO connections to Benefitfocus. 3. All rights reserved. SuccessFactors Employee Central and Benefitfocus Integrating the Benefitfocus UI CUSTOMER © 2016 SAP SE or an SAP affiliate company.successfactors.com · SAML metadata and signing certificate This is the signing X509 certificate for SSO communication and can be taken from the X509Certificate tag of the SAML metadata file.3 Integrating the Benefitfocus UI You can enable single sign-on from the EC UI. 3. 35 . 3.1. 1.3 Field Value Assertion Consumer Service https://sp. Enter the following values: 3.7.com:sp SP Mapping Key bf Configure My Benefits Link for Benefitfocus To configure the My Benefits link for Benefitfocus. 36 CUSTOMER © 2016 SAP SE or an SAP affiliate company. This also requires access to Provisioning for the EC company.benefitfocus.com/sp/ACS. All rights reserved. carry out the following steps in EC.saml2 Audience URL benefitfocus. SuccessFactors Employee Central and Benefitfocus Integrating the Benefitfocus UI . 5. Enter the target URL: Error! Hyperlink reference not valid. select the company and choose Import/Export Data Model under Succession Management. Download the data model and add the following (if it is not already there): <tab-element id="ectbenefitsfocus"> <label>My Benefits</label> <label xml:lang="en-GB">My Benefits</label> <label xml:lang="de-DE">Meine Vorteile</label> </tab-element> SuccessFactors Employee Central and Benefitfocus Integrating the Benefitfocus UI CUSTOMER © 2016 SAP SE or an SAP affiliate company. 37 . In Provisioning. For activation. To activate and configure the link to Benefitfocus via jump-to. 4. choose Company → Company Settings → Enable Employee Central V2 My Benefit Link.1. 2. include the authentication via IdP with BF as the mapping key. 3. All rights reserved. Make sure the permission role is assigned to the relevant users. choose Manage Permission Roles under Manage Security. In EC Admin Tools. check that the My Benefits entry is visible. All rights reserved. 9. In Admin Tools. 8. Choose the relevant permission role. 10. Check that the My Benefits entry is visible.6. Under Permission settings. SuccessFactors Employee Central and Benefitfocus Integrating the Benefitfocus UI . 7. click Permission… 11. 38 CUSTOMER © 2016 SAP SE or an SAP affiliate company. choose Configure Employee Files under Employee Files. Under Employee Views. You can implement this BAdI in Customizing for Personnel Management under Personnel Administration → Interfaces and Integration → Integration of SuccessFactors Employee Central with External Providers → BAdI: Override Benefits Provider Data. This web service is delivered as standard in the following add-on.1 Business Add-In HR_ECPINTEP_BEN_DATE_OR You can use Business Add-In (BAdI) HR_ECPINTEP_BEN_DATE_OR to override the date information from the provider and to process customer-specific custom fields from the provider in the EC Payroll system. From the May 2014 release onwards. If a customer implements any other country version. Note These specifications apply to the US country version. you can achieve this as follows: SuccessFactors Employee Central and Benefitfocus Benefits Data Replication CUSTOMER © 2016 SAP SE or an SAP affiliate company. some adjustments might be necessary. SFIECPEP 100 .4 Benefits Data Replication This chapter describes how to export benefits data from Benefitfocus to EC Payroll. or if additional fields that are part of the file layout. All rights reserved. In Boomi: Boomi accesses this SFTP location and transfers the benefits data to EC Payroll using a web service call. see the BAdI documentation. 39 . In EC Payroll: Web service call to EC Payroll automatically updates the benefits information in EC Payroll. need to be passed to the BAdI for processing. The add-on is a prerequisite for using the standard web service. Please implement this note in the customer's EC Payroll system. No default implementation of this BAdI is provided because the implementation differs from customer to customer based on their requirements. SAP Note 1935616 describes in detail the custom implementation of a web service in EC Payroll. It includes the following major steps: In Benefitfocus: Benefits data is extracted from Benefitfocus to a CSV file and saved in an SFTP location.1 Processing Custom Fields Using Business Add-Ins If Benefitfocus enhances the file layout with customer-specific fields requiring processing. we recommend using the standard web service that is available to update benefits information in EC Payroll. third-party data integration tool 4.1. 4.SuccessFactors Employee Central Payroll. following the instructions carefully to execute the web service correctly. but not part of the standard BAdI parameters. For more information. After the process is deployed in Boomi. SuccessFactors Employee Central and Benefitfocus Benefits Data Replication . Implement the BAdI to process the fields according to the customer's requirements. 2. 1. or map the existing fields required for processing inside the BAdI using data map extensions. go to Connection Settings and select the process. The names in the process properties will be available inside the BAdI with the value. Example The following example shows how additional fields that are part of the file layout can be passed to BAdIs for processing. Go to Process Properties and maintain the name for the value to be passed in each custom field.1. All rights reserved. Add the new fields in the Boomi maps and map them to custom fields in the profile. 40 CUSTOMER © 2016 SAP SE or an SAP affiliate company. 2. 3. Go to Data Maps and select the map shown in the screenshot below. Map the required values to the CUST_VALUE fields on the right-hand side. the fields are available in the BAdI for processing. After the additional fields are configured using the data maps extension in Boomi. SuccessFactors Employee Central and Benefitfocus Benefits Data Replication CUSTOMER © 2016 SAP SE or an SAP affiliate company. 4. All rights reserved. 41 . Make sure the respective values are mapped in the order of the names specified in step 2 above. 5. This shows exactly what the application has stored. If the benefit type is a dental plan “Dental” will be populated. Function: Derive pre/post Tax Wage Type WAGETYPE Cross ref: CR Benefitfocus to EC Payroll Plan type to wage type SuccessFactors Employee Central and Benefitfocus Benefits Data Replication . Position Field Name Size Type Trigger Description 9 A N (A) Social Security Number (SSN) Employee Social Security Number Format: No punctuation 2 Employee ID 19 A N Employer-specific number to identify the employee First Name 50 A N Employee First Name Middle Name 50 A N Employee Middle Name Last Name 50 A N Employee Last Name Suffix 10 A N Employee suffix Benefit Type 30 A N Employee’s Benefit Type (Delimited) 1 (B) 3 (C) 4 (D) 5 (E) 6 Function/CrossReference EC Payroll Field Mapping PERSNO (F) 7 (G) Example: If the benefit type is a medical plan “Medical” will be populated. Coverage Level 30 A Y Benefit Coverage Levels Example: If the coverage level is a Employee and Spouse then (H) 9 (I) 42 CUSTOMER © 2016 SAP SE or an SAP affiliate company. 8 Plan Name 50 A Y Benefit Plan Name. All rights reserved.4.2 Benefits Data Mapping The following fields are considered during the replication. Position Field Name Size Type Trigger Description (Delimited) Function/CrossReference EC Payroll Field Mapping “Employee and Spouse” will be populated. 1 = Pre-Tax Note: Setting must be enabled for each health plan in order for the indicator to be included. SuccessFactors Employee Central and Benefitfocus Benefits Data Replication Function: Derive pre/post Tax Wage Type Cross ref: WAGETYPE CR Benefitfocus to EC Payroll Plan type to wage type CUSTOMER © 2016 SAP SE or an SAP affiliate company.CC No Symbols Employee Annual Cost 8 M Y Total Annual Cost to the employee for the year. Formatted to include two decimal places. If the coverage level is a Employee + 1 then “Employee + 1” will be populated. 11 (K) Pre-Tax Premium 1 N Y 0 = Post-Tax. Format: DDDDD. 12 (L) 13 (M) Employer Annual Cost 8 M Y Total Annual Cost to the employer for the year. All rights reserved. 43 . 10 (J) Coverage Amount 50 M Y Benefit Coverage Amount – Corresponds to total coverage amount. Format: DDDDD. Formatted to include two decimal places.CC Note: Primarily used to report coverage amounts for life and disability benefits. All rights reserved. For Flex plans the formula is Annual Cost/Remaining Pay Periods. In the event that Remaining Pay Period is not active.CC No Symbols 17 (Q) Employee Pre Tax Cost 8 N Y Total Annual Employee Pre Tax Cost AMOUNT GOAL_AMOU NT Format: DDDDD.CC No Symbols 14 (N) 15 (O) Pay Frequency 2 Employee Cost Per pay Period 8 N M Y Y Number of pay periods per year. Employee Cost per pay period Cross Ref: CR Benefitfocus payMax to EC Payroll Frequency Code FREQUENCY AMOUNT Format: DDDDD.Position Field Name Size Type Trigger Description (Delimited) Function/CrossReference EC Payroll Field Mapping Format: DDDDD. Total Annual Employee Post Tax Cost SuccessFactors Employee Central and Benefitfocus Benefits Data Replication . 16 Imputed Cost 8 N Y (P) Total Annual Imputed Income Amount Format: DDDDD. the default formula will be applied. This number will remain consistent.CC No Symbols Note: Default formula used is Annual Cost/Pay Frequency.CC No Symbols 18 (R) 44 Employee Post Tax Cost 8 N Y CUSTOMER © 2016 SAP SE or an SAP affiliate company. CC No Symbols 20 (T) Employer Post Tax Cost 8 N Y Total Annual Employer Post Tax Cost AMOUNT Format: DDDDD. EC Payroll Field Mapping TO_DATE Cross Ref: CR Benefitfocus payMax to EC Payroll Negated Election Code NEG_ELECTI ON C = Employee is active but benefit is cancelled. Enrollment records will include a benefit effective start date and a benefit effective end date.Position Field Name Size Type Trigger Description (Delimited) Function/CrossReference Format: DDDDD. Enrollment records will include a benefit effective start date only for active employment records.CC No Symbols 21 (U) 22 (V) 23 (W) Effective Start Date 8 Effective End Date 8 Election Status 1 D D A Y Y Y Benefit Start Date. Date benefit is effective. as a result of the SuccessFactors Employee Central and Benefitfocus Benefits Data Replication CUSTOMER © 2016 SAP SE or an SAP affiliate company.CC No Symbols 19 (S) Employer Pre Tax Cost 8 N Y GOAL_AMOU NT Total Annual Employer Pre Tax Cost AMOUNT Format: DDDDD. All rights reserved. Date benefit ends Format: CCYYMMDD A = Employee is active and benefit is active. 45 . Format: CCYYMMDD FROM_DATE Benefit End Date. T = Employment is terminated and benefit is cancelled as a result. Enrollment records will include a benefit effective end date only for active employment records. Enrollment records will include a benefit effective start date and a benefit effective end date due to a result of the Termination of employment transaction processed either by payroll import or by an online enrollment user. 46 CUSTOMER © 2016 SAP SE or an SAP affiliate company. SuccessFactors Employee Central and Benefitfocus Benefits Data Replication .Position Field Name Size Type Trigger Description (Delimited) Function/CrossReference EC Payroll Field Mapping cancellation transaction processed by an online enrollment user for active employment records. All rights reserved. W = Employment is active but benefit was waived/refused. 24 (X) Remaining Pay Periods 4 N Y Remaining Pay Periods Note: Primarily used in conjunction with the Flex benefit when changes occur mid-year. Payroll Attribute Code 4 25 A Y Please provide a logic table for determining unique Plan Codes. Payroll Attribute Code 2 25 A Y Please provide a logic table for determining unique Plan Codes.5 31 (AE) Deferral Flat Amount 8 SuccessFactors Employee Central and Benefitfocus Benefits Data Replication N N Per pay period flat amount for 401(k) deduction CUSTOMER © 2016 SAP SE or an SAP affiliate company.00 Example: 5% = . Coverage Codes or Deduction Codes if needed. Coverage Codes or Deduction Codes if needed. All rights reserved. Payroll Attribute Code 3 25 A Y Please provide a logic table for determining unique Plan Codes. Coverage Codes or Deduction Codes if needed. Coverage Codes or Deduction Codes if needed. 30 Deferral Pct 8 N N Percent per pay period for 401(k) deduction (Delimited) 25 (Y) 26 (Z) 27 (AA) 28 (AB) 29 (AD) Function/CrossReference EC Payroll Field Mapping Format: 0. 25 A Y (AC) Payroll Attribute Code 5 Please provide a logic table for determining unique Plan Codes. Coverage Codes or Deduction Codes if needed.Position Field Name Size Type Trigger Description Payroll Attribute Code 1 25 A Y Please provide a logic table for determining unique Plan Codes. 47 . ”Sub: Upsert Payroll Request”.4. · This process also reports negated elected records and the records where mandatory fields are missing. Subprocess: Sub: Benefitfocus payMax to EC Payroll Generate Request · This process splits a record for an employee into multiple requests and then maps this data to EC Payroll request.Benefits · This process reads the Inbound flat file and then makes a call to the subprocess. Main Process: iFlow: Benefitfocus payMax to EC Payroll .3 Integration Process Overview The mapping of the Benefitfocus inbound file fields to the EC Payroll field requirements is done via the Boomi process. “Benefitfocus payMax to EC Payroll Processing”. All rights reserved. This process posts valid records to the to a soap request which then updates the payroll system. SuccessFactors Employee Central and Benefitfocus Benefits Data Replication . This process in-turn makes a call to the subprocess. The following information gives you a better understanding of how information gets mapped from thirdparty provider to EC Payroll using Boomi as the middleware. The following graphic depicts the overall process. 48 CUSTOMER © 2016 SAP SE or an SAP affiliate company. is called. · Different reports are generated and sent via an email as a notification to the administrator (only if this feature is activated). · Next. all the requests are combined into a single request and then the subprocess." Benefitfocus payMax to EC Payroll Generate Request" · The subprocess generates the request based on the business logic which is derived from the requirements. boomi. each consisting of one or more published Boomi processes. that is.com. Procedure 1. and monitor an integration pack. SuccessFactors Employee Central and Benefitfocus Benefits Data Replication CUSTOMER © 2016 SAP SE or an SAP affiliate company. In the Deploy tab. Data only travels in one direction. 4. Follow the below procedure to ensure that an environment has been created in the customer account and attached to the Boomi Cloud. 2. 49 .4 Getting Access to the Integration Pack Integration packs are packaged integration solutions. All rights reserved. see the title in upper right. you can install integration packs in your account. Note To verify that you are in the correct account.Subprocess: Sub: Upsert Payroll Request 4. the Boomi user must have the appropriate permissions to deploy. click "+" on the integration pack section at the lower left side. It must be authorized for accessing both the integration pack and the Atom Cloud where the integration pack will be deployed. configure. Log on to the customer Boomi account at http://platform. Prerequisites To deploy an integration pack. choose <Current Account Name> → Select Account… and search for the required account. Once you have installed an integration pack. you can attach Atoms or environments to it and then run any of its processes from the Deployed Processes tab in Atom Management. To switch accounts.5 Configuring and Using the Integration Pack From the Deploy page in Boomi. the integration pack contains the required mapping between the Benefitfocus data fields and the corresponding fields in the inbound structure of EC Payroll. For the current solution. from Benefitfocus to EC Payroll. Note You can monitor the release status of installed integration packs and apply pending updates from the Integration Pack Versions tab in Atom Management. The Extensions pop-up appears. 7. Benefitfocus SFTP Server Connections (Maintain SFTP Details) 50 CUSTOMER © 2016 SAP SE or an SAP affiliate company. 4. 5. 8.6.3. In the Boomi account. Click Environment Extensions on the right-hand side. Click View and navigate through to install the integration pack.1 Extensions for Connection Settings After you have installed the integration pack. Choose the environment on the right-hand side and click << to "attach" the integration pack to the selected environment. it is shared with selected account groups. 4. Choose Manage → Atom Management.6 Setting Up the Standard Data Integration 4. All rights reserved. 6. SuccessFactors Employee Central and Benefitfocus Benefits Data Replication . Select the environment on the left-hand side. you must configure the connection to the EC Payroll instance or SFTP location. Once an integration pack is released. Integration pack building and release is performed in a master account. make the following settings for the integration pack. Click the integration pack previously added to the account. · Benefitfocus paymax to EC Payroll — Errors Records · Benefitfocus paymax to EC Payroll — Ignored Records · Benefitfocus paymax to EC Payroll — Negated Election Records · Benefitfocus paymax to EC Payroll — Mandatory Fields Missing Note After the mail server connections are maintained. All rights reserved. see Web Service for Updating SuccessFactors Employee Central Payroll on SAP Help Portal at http://help. SuccessFactors Employee Central and Benefitfocus Benefits Data Replication CUSTOMER © 2016 SAP SE or an SAP affiliate company. Web Service Connections From the May 2014 release onwards. On this configuration.sap.Mail Connections (Maintain Mail Server Details) Maintain the mail server connection details to receive an email on the status of the Boomi process execution. and no custom solution is required: EmployeeBenefitsVendorDataUpdateRequestConfirmation_In For information about the web service that is delivered to update the EC Payroll system. the following web service is delivered as standard.com/cloud4hr. You can enable it from the process properties. the sender and the receiver email ID has to be configured in the Boomi process to enable the Boomi process to send emails. 51 . Boomi send the following emails to the configured receiver email in the process properties: · Benefitfocus paymax to EC Payroll — Successful Records This is an optional feature to get emails on successful records. 52 CUSTOMER © 2016 SAP SE or an SAP affiliate company. 4. or deleted. Kindly create a ticket to your EC payroll cloud operation team to whitelist the web service.com. modify the process properties of the Boomi process. o APPLOG_OBJECT: Name of the application log object created in EC Payroll for logging error messages o APPLOG_SUBOBJECT: Name of the application log sub-object created in EC Payroll for logging error messages o CURRENCY: Currency in which the amount is processed o SENDER_MAIL_ID: Sender email ID for sending emails from Boomi processes o RECEIVER_MAIL_ID: Recipient's email ID The link ed image cannot be displayed. the web service must be whitelisted.6. Verify that the link points to the correct file and location. renamed. see Configuring a Web Service on SAP Help Portal at http://help. The file may have been mov ed. SuccessFactors Employee Central and Benefitfocus Benefits Data Replication .The WSDL URL and endpoint/binding URL are required to maintain the web service connections. You can set the following general properties: o FILE_NAME: Name of the file from Benefitfocus to be read. o FILE_DIR: Path to the SFTP remote directory. For information about configuring the web service using transaction SOAMANAGER (that is. All rights reserved.2 Process Properties To fetch data based on a particular filter.sap. The following filters are available for the current integration process. creating end points and accessing the WSDL URL). Note To allow access to the web service from the middleware. Verify that the link points to the correct file and location.The link ed image cannot be displayed. Click Cross Reference. SuccessFactors Employee Central and Benefitfocus Benefits Data Replication CUSTOMER © 2016 SAP SE or an SAP affiliate company. 2. 5. By default for all the plans employer contribution is processed per pay period. one-time contribution. in the first column you have to fill the benefit plans for which employer contribution should be processed once. Navigate to Manage → Atom Management. Fill out the cross-reference tables to add or override the existing values. 53 . Click Environment on the left-hand side. or deleted. Select the cross-reference to be changed from the dropdown. 1.6. that is. The file may have been mov ed.3 Cross-Reference Tables The cross-reference tables are translation tables between the Benefitfocus values and EC Payroll values. Click Environment Extensions on the right-hand side. Below is an example of how you can customize a gender code mapping The following cross-reference tables are available: o Employer Contribution Benefit Type Lookup: Maintain benefit plans in this table where employer contribution needs to be processed once. 4. 4. All rights reserved. renamed. 3. The Extensions pop-up appears. Here are some assumptions for this solution · Customers will provide mapping of their benefit deductions (wage types) set up in EC Payroll to benefit codes in Benefitfocus. post-tax contribution. The complete processing. pre-tax contribution. CUSTOMER © 2016 SAP SE or an SAP affiliate company. SuccessFactors Employee Central and Benefitfocus Benefits Data Replication . 4.1 Health/Insurance/Credit/Disability/FSA Plan Processing For Health.7 Data Replication Details Employee benefit deduction data will be sent from Benefitfocus to EC Payroll in CSV format. and employer contribution happens at the third-party provider side and only the deduction amounts are passed to the payroll system. that is. Disability. insurance. then converted into infotypes depending on the plan type category and processed into EC Payroll as an XML file upload. o CR Benefitfocus payMax to EC Payroll Frequency Code: This cross-reference table is to map provider pay frequency code with EC Payroll frequency code. FSA and HSA plans.7. the EC Payroll benefits engine is not used. · 54 EC is the system of master data for all employees. employee contribution. All rights reserved. Credit plans.o CR Benefitfocus payMax to EC Payroll Negated Election Code: This cross-reference table is to map the negated election Benefitfocus code with EC Payroll. 4. · EmployeeCentral is the system of master data for all employees. if an employee didn’t pay the premium. (SSO Enabled) · Benefitfocus sends the percentage contribution for 401(k) plan or the deferred amount per pay period in the file. · Benefitfocus required employees master data and eligibility data is sent from EC to Benefitfocus. For benefit plans where the benefits engine is used for processing. employee contribution. employer contribution) is mapped to the wage type on the EC Payroll side to identify the amount been sent is a pre-tax. 55 . then this information coming from the provider is stored in infotype 14 or infotype 15 based on whether it is a periodic payment or a onetime payment. SuccessFactors Employee Central and Benefitfocus Benefits Data Replication CUSTOMER © 2016 SAP SE or an SAP affiliate company. For example. so that we get the right wage type information in the file from the provider for the respective plans. · Benefits elections and enrollment are done by the provider. that is. employees need to log in to the provider's application/Web site and elect/enroll in benefit plans. · Benefits elections and enrollment are done by the provider. 4. EC Payroll needs to be configured with benefits customizing for that plan and proper benefit area should be assigned to an employee in infotype 0171. · The details of employer contribution configuration in the system should also be communicated to the provider during implementation. All rights reserved. · The payroll results stored in the payroll cluster can be used for reporting to the third-party provider. post-tax contribution. (SSO Enabled) · Benefitfocus does all the benefits processing and sends the employee and employer deduction/contributions to EC Payroll. · Employer contribution can be configured as a part of benefits customizing for the plans and benefit engine will take care of process the same. The details of the wage types for each plan processing is passed over to the provider in advance during implementation. · If in case employer contribution is not configured in the system for 401(k) plans. post-tax.· Benefitfocus requires employees master data and eligibility data is sent from EC to Benefitfocus. · The details of the wage types for each plan processing is passed over to the provider in advance during implementation. the system knows exactly what to do when they come back because they have already committed to the contribution and the benefit administrator will figure out how the payment has to be done. so that we get the right wage type information in the file from the provider for the respective plans. which is update in the infotype 0169 for savings plan. · The pay code information from the provider (that is. employee contribution. so that the employer contribution is not passed if configured in the benefits engine. pre-tax contribution. the EC Payroll benefit engine is used to process the plans because of the legal rules involved in processing of these plans. that is. pre-tax contribution. employee contribution or employer contribution. The complete processing of plan is done by benefits engine. post-tax contribution. by check or some other means. · The payroll processes the information stored in infotype 14 & infotype 15 based on the wage type configuration and the results are stored in payroll cluster PLC2 for all employee. · The pay code information from the provider (that is. employer contribution) is mapped to the wage type on the EC Payroll side.2 401(k) Saving Plan Processing For 401(k) saving plans. · The payroll processes the information and the results are stored in payroll cluster PLC2 for all employee. which is stored in infotype 14 (Recurring payments/deduction) and infotype 15 (Additional Payments) based on whether it is a periodic payment or a one-time payment respectively. for example. employees need to log in to the provider's application/Web site and elect/enroll in benefit plans.7. During implementation.7. the provider and the customer should handshake on the wage type configured on the EC Payroll side for processing benefit plans and mapped to the respective pay code from the provider side. All rights reserved. as an: · Employee contribution · Employer contribution · Pre-tax contribution · Post-tax contribution This information is vital for the payroll to process these amounts in a specific way. that is. SuccessFactors Employee Central and Benefitfocus Benefits Data Replication . the following attributes are derived and updated in the infotypes accordingly: · Employee contribution · Employer contribution · Pre-tax contribution · Post-tax contribution · Infotype to update 56 CUSTOMER © 2016 SAP SE or an SAP affiliate company.· The payroll results stored in payroll cluster can be used for reporting to the third-party provider. The pay code from the provider is mapped to a wagetype on the EC Payroll side which defines how the plan or the amount in the wage type needs to be processed.3 Pay Code Wage Type Mapping Pay code. 4. so that the provider sends the proper wagetype for a record based on the processing required for the plan in the inbound file to the customer. On EC Payroll based on the wagetype passed. on the third-party provider's side. is key to which defining how the plan (amount) should be processed. 1 Employer Contribution for Benefit Plans Employer contribution for plans where the benefits engine is used for processing needs to be configured in the benefits engine and processed accordingly. that is. o Customer will not configure plans other than 401(k) saving plans using benefit engine. insurance plan etc. o Bonus contribution & pension contribution to saving plans are out-of-scope and are not handled through this integration. 401(k) plan. vision plan. the employer contributions will be in the form of an amount ($). SuccessFactors Employee Central and Benefitfocus Benefits Data Replication CUSTOMER © 2016 SAP SE or an SAP affiliate company. for example. and if the third-party provider file contains employer contribution in the form of an percentage for these plans then this information will be ignored and not processed. customers have to configure the same as a part of benefits configuration.3. Assumptions: o Employer contribution in % for plans other than 401(k) savings plan is out-of-scope. For 401(k) saving plans.4. but if you want certain plans employer contribution to be one-time contribution then this can be achieved by maintaining the respective benefit plan name in the cross-reference table Employer Contribution Benefit Type Lookup. The employer contributions can be in the form of an amount ($) or as percentage (%).7. for FSA plan. All rights reserved. for saving plans (401(k) plans). dental plan. HSA plan. for example. 57 . For plans other than savings. Note By default the employer contribution is process per pay period for all the plans. Pre/Post Tax Type Where Used With Goal Info SuccessFactors Employee Central and Benefitfocus Benefits Data Replication . for FSA. Note Employee's imputed income is processed per pay period for all the plans.7. There are no standard wagetypes shipped for this purpose. and customers have to create their custom wage types for this purpose. 58 Wage Type Wage Type Description EE or ER Paid 2C01 Std Medical Employee pre-tax EE Pre Deduction IT 0014 2C02 Std Medical Employer ER Post Deduction IT 0014 2C10 Dental Employee pretax EE Pre Deduction IT 0014 2C11 Dental Employer ER Post Deduction IT 0014 2C15 Opt Life EE after-tax EE Post Deduction IT 0014 CUSTOMER © 2016 SAP SE or an SAP affiliate company. savings plans. IT 0014. the third-party provider will send the annual goal amount or % deduction or per pay period deduction for an employee and the benefits engine will process the plan and calculate the pre-tax & post-tax contribution as per the configuration accordingly.8 Configuring the Wage Types Benefits providers send contribution amounts for benefit plans directly for payroll deduction. 4.2 Employee Contribution · For plans where the benefits engine is not used. Select Personnel Management → Personnel Administration → Payroll Data → Employee Remuneration Information → Wage Types → Create Wage Type Catalog. for example. that is. health. the third-party provider will completely process the plan and send per pay period employee pre-tax and post-tax deduction to EC Payroll. disability. and credit plans. insurance.4. Select copy and enter a country. All rights reserved. · For plans where the benefits engine is used for processing. 4. Select wage type and click Copy. Adapt the wage type as follows: Example Wage type for "Standard Medical Employee pre-tax". This can be done as follows 1. 3.3. 2. 2C01 has to be made permissible for infotype 0014. for example. for example. Wage Type Wage Type Description EE or ER Paid BE31 401(k) Employee pretax EE Pre Benefit IT 0169 BR31 401(k) Employer ER Post Benefit IT 0169 BA31 401(k) Employee after-tax EE Post Deduction IT 0169 2C20/2C21 Health Saving Employee pre-tax EE Pre Deduction IT 0014 2C22 Health Savings Employer ER Post Deduction IT 0014 2C25/2C26 Flex Spending Employee pre-tax EE Pre Deduction IT 0014 2C27 Flex Spending Employer ER Post Deduction IT 0014 2C30 Basic Life Employer Covered ER Post Deduction IT 0014 SuccessFactors Employee Central and Benefitfocus Benefits Data Replication Pre/Post Tax Type Where Used With Goal Info IT 0015 IT 0015 CUSTOMER © 2016 SAP SE or an SAP affiliate company. All rights reserved. 59 . Browse to the data map extension. SuccessFactors Employee Central and Benefitfocus New Features and enhancements . 3. then the latest effective date of these 2 entities is sent to the Custom Category Effective Date field on Benefitfocus paymax inbound file. } CustomCategoryEffDate = max. (for more details refer to section Data Maps) and add a function to the map by clicking +.1 Custom Category Effective Date mapping In this release we talk about the effective dated entities required to compute Custom Category Effective Date field.length. The following effective dated entities are considered to compute Custom Category Effective Date field on Benefitfocus payMax inbound file. i<EffectiveDates. i++) { if (EffectiveDates[i] > max) { max = EffectiveDates[i]. 5. In the Embedded Scripting dialog select the language as JavaScript. 2. Select Custom Script from the Category drop down list. Job_information 4.FourthDate]. In the Script to Execute box paste the following code: var EffectiveDates = [FirstDate. This is achieved using data maps extension where you create a map function and are required to map the effective start date field of Job Information entity and compensation information entity to the map function accordingly. var max = '' .5 New Features and enhancements 5. 1.SecondDate. 60 CUSTOMER © 2016 SAP SE or an SAP affiliate company. All rights reserved. Personal_information 2. for(var i=0. Example If any of the fields from Job Information entity and Compensation information entity are mapped to custom category field on the benefitfocus paymax import file. 4. Address_information 3. Compensation_information The result is the latest date out of all effective dates from above entities that is mapped to Custom Category Effective Date field.ThirdDate. Select Scripting form the Functions textbox and click OK. You need to map "effective start date" of Job information entity to the FirstDate field of the map function and "effective start date" field of compensation information entity to the SecondField of the map function Procedure 1. In the Outputs box. SuccessFactors Employee Central and Benefitfocus New Features and enhancements CUSTOMER © 2016 SAP SE or an SAP affiliate company. In the data map extension map the fields as shown in the screen below. 7. The values in EC Pay Group column are not delivered in the table. In the Inputs box. All rights reserved. add the following Input as Char parameters. FourthDate and click OK. The new lookup reference table is read only if the process property value for pay frequency is “default”. add the following Output as Char parameters. In the following screenshot you can see two columns "BF Pay Frequency" and "EC Pay Group" in the lookup reference table that maintains the mapping between the values of Employee Central and Benefitfocus. 8. Note If no value in the lookup reference table is maintained then a blank value is picked from the table. CustomCategoryEffDate. 61 . 5. ThirdDate. SecondDate.6. It is recommended that you maintain both the columns respectively. A new lookup reference table is shared as a standard to maintain benefits vendor pay frequency code for an employee central pay group.2 Pay frequency In this release the Benefitfocus outbound Boomi integration is enhanced to generate multiple pay frequency in an output file. FirstDate. It is recommended that you maintain both the columns respectively.5. SuccessFactors Employee Central and Benefitfocus New Features and enhancements .3 Termination Reason In this release the Benefitfocus outbound Boomi integration is enhanced to populate the termination reason in addition to the other employee details in an output file based on the values present in the lookup reference table. 62 CUSTOMER © 2016 SAP SE or an SAP affiliate company. In the following screenshot you can see two columns "EC Event Reason" and "BF Termination Reason" in the lookup reference table that maintains the mapping between the values of Employee Central and Benefitfocus. All rights reserved. Note If no value in the lookup reference table is maintained then a blank value is picked from the table. We have a new lookup reference table that maintains Benefitfocus termination reasons for corresponding event reason. . Material Number: .com/contactsap © 2016 SAP SE or an SAP affiliate company.com/corporate-en/legal/copyright/index. All other product and service names mentioned are the trademarks of their respective companies. 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. Please see http://www.www.sap. 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. sap.epx#trademark for additional trademark information and notices.