012002523100002927442015e-2

SuccessFactors HCM Suite

Q1 2015 Release

Document Version 1.0 – 2015-01-23

CUSTOMER

SuccessFactors Employee Central and Benefitfocus Using SAP HANA Cloud Integration Integration Guide

2

SuccessFactors Employee Central and Benefitfocus Using SAP HANA Cloud Integration

Typographic Conventions

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.

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, F2 or ENTER .


Document History

3

Document History

Version Date Change

1.0 2015-01-23 Initial version

4


Table of Contents

Table of Contents

1 Benefitfocus Integration Overview .............................................................................................................. 5 1.1 Integration Options ................................................................................................................................................. 5 1.2 Benefits Business Process with Benefitfocus ....................................................................................................... 6 1.3 Overview of Payroll Export Process ....................................................................................................................... 7

2 Employee Data Replication ........................................................................................................................... 8 2.1 Prerequisites ............................................................................................................................................................ 8

2.1.1 Configurations for Employee Central Compound Employee API ....................................................... 8 2.1.2 Preparations Required at Third-Party Provider's End ......................................................................... 9

2.2 Integration Specification ......................................................................................................................................... 9 2.2.1 Person Information [EC hris-element-id: personInfo] ....................................................................... 10 2.2.2 Personal Information [EC hris-element-id: personInfo] .................................................................... 10 2.2.3 Address Information ............................................................................................................................. 12 2.2.4 Phone Information [EC hris-element-id: phoneInfo] ......................................................................... 13 2.2.5 Email Information [EC hris-element-id: emailInfo] ............................................................................ 13 2.2.6 Employment Information [EC hris-element-id: employmentInfo] ................................................... 14 2.2.7 Compensation Information [EC hris-element-id: compensationInfo] ............................................. 15 2.2.8 National ID Card .................................................................................................................................... 16 2.2.9 Emergency Contact Information ......................................................................................................... 16

2.3 Getting Access to the Solutions ........................................................................................................................... 17 2.3.1 Common Configuration Steps ............................................................................................................. 18

2.4 Setting Up the Data Integration ........................................................................................................................... 18 2.4.1 Receiver Settings .................................................................................................................................. 19 2.4.2 Parameters ............................................................................................................................................ 23 2.4.3 Value Mappings ..................................................................................................................................... 24

2.5 Extending the Standard Data Integration............................................................................................................ 25

3 Benefits Data Replication ...........................................................................................................................26 3.1 Business Add-In HR_ECPINTEP_BEN_DATE_OR .............................................................................................. 26

3.1.1 Processing Custom Fields Using Business Add-Ins .......................................................................... 26 3.2 Benefits Data Mapping .......................................................................................................................................... 29 3.3 Getting Access to the Solutions ........................................................................................................................... 35

3.3.1 Common Configuration Steps ............................................................................................................. 35 3.3.2 Setting Up the Standard Data Integration .......................................................................................... 36

3.4 Data Replication Details ........................................................................................................................................ 39 3.4.1 Health/Insurance/Credit/Disability/FSA Plan Processing .............................................................. 39 3.4.2 401(k) Saving Plan Processing ........................................................................................................... 40 3.4.3 Pay Code Wage Type Mapping ............................................................................................................ 41

3.5 Configuring the Wage Types ................................................................................................................................ 42

1 Benefitfocus Integration Overview

This guide is intended for Professional Services and SAP or partner consultants to integrate SuccessFactors

Employee Central (EC) with Benefitfocus. Integration is through an SAP HANA Cloud Integration process for

validated third-party benefits providers.

For more information about EC, see the Employee Central Implementation Guide on SAP Service Marketplace at

http://service.sap.com/cloud4hr under Employee Central.

1.1 Integration Options

Use the following steps as a guideline to successfully integrate EC with the benefits providers. This is a simplified

approach to a possible integration process. You have to determine your customer's business requirements.

Based on their requirements, you will have to adjust these processes. To understand how data from EC is mapped

to data in the benefits system, see Employee Data Replication.

1. Set up EC.

2. Make third-party provider-specific settings, for example, SFTP server accessibility.

3. Get access to the catalog in HCI Spaces.

4. Set up the data integration.

5. If required by the customer, extend the data integration.

Benefitfocus provides employers, consumers, insurance carriers and government entities cloud-based

technology to shop, enroll, manage and exchange benefits information. Employees can choose their benefits

plans in an online portal with the integration to EC. Benefitfocus then sends updates to EC Payroll as required for

legal reporting.

For more information about EC Payroll, see the SuccessFactors Employee Central Payroll Implementation Guide

on SAP Service Marketplace at http://service.sap.com/cloud4hr under Employee Central.

EC sends Benefitfocus the complete data about an employee. Benefitfocus then updates the benefits providers

daily about any changes that may have occurred.

Benefitfocus has the following user roles:

Employees: Access Enrollment System

Benefits Administrator: Access Manager Tools

System Administrator: Access Data Exchange

Finance Administrator: Access Billing

http://service.sap.com/cloud4hr

http://service.sap.com/cloud4hr

6


Table of Contents

1.2 Benefits Business Process with Benefitfocus

The Benefitfocus process catalog is available in SAP HCI Spaces. You can copy the process from the Discover

space and adapt it to your requirements in the Design space.

The integration is done via a CSV file on the SFTP Benefitfocus server. This file is called the inbound payMax file.

Inbound payMax files are always full files. A full file contains the employer’s entire employee population and

includes all data for each employee in the payroll/HRIS system. Employers can typically provide full files much

more easily than changes-only files. In the provided HCI integration process, only the required (subset) of the

payMax file fields are mapped.

The Benefitfocus process was designed to detect differences and compare full files to the population stored in

online enrollment.

The inbound payMax file contains two record types that include both file and member identifying information. The

specific record types are included in the following list:

payMax header

Employee detail record

The payMax header record is followed by one or more employee detail records. The file must adhere to the record

type sequencing rules to ensure the file loads properly.

Note

This integration is only for the country US because Benefitfocus does not yet support other countries.

If EC is the system of record, all Benefitfocus fields must be read-only. If one of the mapped fields is not

required, it should not be made visible in the Benefitfocus system.

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


Table of Contents

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 Compound Employee API

The compound employee API for EC extracts employee data from 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

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 some more settings to:

1. Webservice Setup

Follow the standard process for SF APIs to set up SFAPI operations login and log out and to enable the API.

2. Thresholds and Limits

The compound employee API 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.

3. 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 Preparations Required at Third-Party Provider's End

After you opt for a particular third-party provider integration, you should sync on the following points for initial

setup preparations to be done at the third-party provider's end:

Functional Preparation

For example, availability of a document like 'Discovery and Requirements Gathering'

Group and Benefits Plan Setup

o Technical Setup of Employee File

For example, availability of documents like 'Integration and Data Migration Discovery'

o SFTP Server configuration

2.2 Integration Specification

The following tables list the EC fields required to replicate EC data using middleware to Benefitfocus. They also

show which fields you need to map manually and the corresponding value mapping name. Also provided are

descriptions of the mapping activities that are required for different fields.

Note

Categories are used by Benefitfocus to identify different classes or subgroups of employees at the carrier

or employer. Examples of categories can be location, department, division, etc. Categories can be used to

configure rates, enable benefits, or configure administrator permissions.

10


Table of Contents

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. If the data for an

employee does not satisfy the length constraint, the employee is not sent to Benefitfocus.

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.1 Person Information [EC hris-element-id: personInfo]

EC hris Field Description Obligatory

for

Replication

Code

Mapping

Required

Value

Mapping

Benefitfocus

Attribute Max Type

Length

date-of-birth Date of birth X Date of Birth 8 D

person_id_external

External

Person ID

X Employee ID 19 A

No further mapping activities are required for these fields.

2.2.2 Personal Information [EC hris-element-id: personInfo]


for

Replication

Code

Mapping

Required

Constraint

/Constant

Value

Value

Mapping

Benefitfocus

Attribute Max Type

Length

gender Gender X Gender 1 A

firstName

Given

name

X First Name 50 A

lastName

Family

name

X Last Name 50 A

middleName

Middle

name

X Middle

Name

50 A

marital-status Marital X Marital Marital 10 A


for

Replication

Code

Mapping

Required

Constraint

/Constant

Value

Value

Mapping

Benefitfocus

Attribute Max Type

Length

status Status Status

suffix

Suffix X X Name

Suffix

Suffix 10 A

X EEO

Categories

EEOC 50 A

X Current

Date

Name

Change

Date

8 D

gender

The outbound service sends the values M = male and F = female. Do not associate this field with a value mapping.

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.

Marital-status

These values are mapped in SAP HANA Cloud Integration through the value mapping Marital Status. This table is

defined as a value mapping in SAP HANA Cloud Integration and must be filled by the consumer based on the

picklist and the Benefitfocus values. Default mapping values are available.

suffix

The field suffix is mapped to the Benefitfocus field Suffix through a cross-reference look-up. These values are

mapped in SAP HANA Cloud Integration through the value mapping Name Suffix. This table is defined as a value

mapping in SAP HANA Cloud Integration and must be filled by the consumer based on the picklist and the

Benefitfocus values.

EEOC

These values are mapped in SAP HANA Cloud Integration through the value mapping EEO Categories. This table is

defined as a value mapping in SAP HANA Cloud Integration and must be filled by the consumer based on the

picklist and the Benefitfocus values.

Name Change Date

The field Name Change Date of Benefitfocus is currently mapped to be set to the current date.

12


Table of Contents

2.2.2.1 Personal Information USA [EC hris-element-id: personInfo]


for

Replication

Code

Mapping

Required

Value

Mapping

Benefitfocus

Attribute Max Type

Length

genericString1 Ethnicity Ethnicity 20 A

Ethnicity

The field genericString1 is mapped to the Benefitfocus field Ethnicity through a value mapping. These values are

mapped in SAP HANA Cloud Integration through the value mapping Ethnicity. This table must be filled by the

consumer based on the picklist and the Benefitfocus values.

2.2.3 Address Information

EC hris Field Description Obliga-

tory for

Replicat-

ion

Code

Mapping

Required

Constraint

Value

Value

Mapping

Benefitfocus

---------------------------------

Attribute Max Type

Length

address-

type

Address

type

'HOME'

address1

Address

field 1

X Address

Line 1

50 A

address2

Address

field 2

optional Address

Line 2

50 A

city City X City 50 A

state State X X State 2 A

zip-code ZIP code X ZIP Code 10 A

country

Country X Country

Code

3 A

Address Type

A constraint in SAP HANA Cloud Integration 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. No further mapping is

required.

ZIP Code

There is direct mapping to the corresponding field ZIP Code. No further mapping is required.

Country

There is direct mapping to the corresponding field Country Code. No further mapping is required.

State

The EC fields state and province are mapped to the field State in the payMax file through an SAP HANA Cloud

Integration function. This function identifies null values and returns only the non-null values.

2.2.4 Phone Information [EC hris-element-id: phoneInfo]

A constraint in SAP HANA Cloud Integration transfers the phone information according to phone_type.

In the SAP HANA Cloud Integration mapping, a phone number with type H (home) is mapped to HomePhone, a

phone number with type C (cellphone) is mapped to CellPhone, and a phone number with type B (business) is

mapped to WorkPhone.


for

Replication

Code

Mapping

Required

Constraint

Value

Value

Mapping

Benefitfocus

------------------------------------

Attribute Max Type

Length

phone_type Phone type X C, H, B

phone_number

Phone

number

X HomePhone

/CellPhone/

WorkPhone

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 function that builds a 10-digit phone number by using both the

area code and phone number.

2.2.5 Email Information [EC hris-element-id: emailInfo]

A constraint in SAP HANA Cloud Integration transfers email information according to email_type.

In the SAP HANA Cloud Integration mapping, a function maps an email address with type P (personal) to Personal

Email, and an email address with type B (business) to Work Email.

14


Table of Contents

EC hris

Field

Description Obligatory

for

Replication

Code

Mapping

Required

Constraint

Value

Value

Mapping

Benefitfocus

Attribute Max Type

Length

email-

address

Email

address

X Personal Email

/Work Email

50 A

email-

type

Email

address

type

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. email-type can have the following values:

P = Personal

B = Business

2.2.6 Employment Information [EC hris-element-id: employmentInfo]


for

Replication

Code

Mapping

Required

Value

Mapping

Benefitfocus

Attribute Max Type

Length

Start Date Start Date X Date of Hire 8 D

End_date End Date X 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), is the field Termination

Date of Benefitfocus directly mapped to EC field end_date, and the field Termination Reason of Benefitfocus set to

value V (Voluntary).

2.2.7 Compensation Information [EC hris-element-id: compensationInfo]


for

Replication

Code

Mapping

Required

Value

Mapping

Benefitfocus

Attribute Max Type

Length

start_date

Start Date Earning Amount

Effective Date

8 D

2.2.7.1 Pay Component Recurring Information [EC hris-element-id: paycomponentRecurring]

EC

hris

Field


for

Replication

Code

Mapping

Required

Constraint/

Constant

Value

Value

Mapping

Benefitfocus

Attribute Max Type

Length

X X Salary 11 M

X Pay Frequency 15 A

ANNUAL Earning Unit of

Measure

20 A

Salary

The following EC fields are mapped to the field Salary in the payMax file through a script that uses the following

elements for calculation:

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 PARAMETERS of the integration

catalog. It has to be set before running the replication process.

16


Table of Contents

2.2.8 National ID Card

EC hris

Element

EC hris

Field


for

Replication

Code

Mapping

Required

Value

Mapping

Benefitfocus

Attribute Max Type

Length

nationalIdCard national-id National

identification

X X 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 through a

function that removes the hyphens '-' from national-id.

Note

national-id is obligatory for replication. No further mapping is required.

2.2.9 Emergency Contact Information

EC hris

Element

EC hris

Field

Description Obligatory for

Replication

Code

Mapping

Required

Value

Mapping

Benefitfocus

Attribute Max Type

Length

name X X 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 50 A

EC hris

Element

EC hris

Field

Description Obligatory for

Replication

Code

Mapping

Required

Value

Mapping

Benefitfocus

Attribute Max Type

Length

Contact

Address

Line 2

city Emergency

Contact

City

50 A

state Emergency

Contact

State

2 A

zip_code Emergency

Contact Zip

Code

10 A

country 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 user-defined function. This function uses Groovy script to identify null values and

return only the non-null values.

2.3 Getting Access to the Solutions

SAP HCI Spaces is a Web-based application that helps you to access the integration content available for a

particular tenant on an on-demand integration infrastructure. In SAP HCI Spaces, you can access integration

packages with artifacts such as value mappings, integration flows, and files. For more information, see Viewing

Integration Flow Configurations in the Developer's Guide for Managing Integration Content.

You can edit and configure a package as follows:

1. On the Discover tab, click the integration package to be configured.

2. Choose Copy (as shown in the following figure).

https://proddps.hana.ondemand.com/dps/d/preview/93810d568bee49c6b3d7b5065a30b0ff/2014.10/en-US/frameset.html?ec104a138bf64c849339a90588dd9f6c.html


https://proddps.prod.jpaas.sapbydesign.com/dps/d/preview/dd250f2e3c2645a8ae327e935071281e/2014.12/en-US/DevGuide_ManageIntContent_External.pdf

18


Table of Contents

On the Design tab, you should now find the copied package.

3. To configure and edit the package, follow Editing Integration Flow Configurations in the SAP HANA Cloud

documentation.

2.3.1 Common Configuration Steps

2.3.1.1 SAP Credential Deployment

To deploy the following artifacts, see Deploying and Editing a User Credentials Artifact in the Operations Guide for

SAP HANA Cloud Integration.

Artifact Description

SuccessFactors EC Credentials These credentials are used to connect to the

SuccessFactors EC system

SuccessFactors EC Payroll Credentials These credentials are used to connect to the

SuccessFactors EC Payroll system

SAP SFTP Server Credentials These credentials are used to connect to the SFTP

server

Benefitfocus SFTP Server Credentials These credentials are used to connect to the

Benefitfocus SFTP server

For more information about SFTP-based communication, see the Operations Guide for SAP HANA Cloud

Integration.

2.3.1.2 Value Mapping Maintenance

A value mapping project is delivered along with the iFlows in this integration. It must be deployed in the customer

landscape so that the iFlows can refer to the value mappings. For information about using and editing value

mappings, see the Developer’s Guide for Managing Integration Content.

2.4 Setting Up the Data Integration

In the Discover section, click the SuccessFactors EC with Third-Party Benefits Vendor — Benefitfocus integration

process and configure the SF EC to Benefitfocus integration flow.

https://proddps.hana.ondemand.com/dps/d/preview/93810d568bee49c6b3d7b5065a30b0ff/2014.10/en-US/frameset.html?1e556bced9b84c84889cadb7ccc79dd4.html

http://help.sap.com/cloudintegration/SAP_HCI_OpsGuide.pdf


https://proddps.prod.jpaas.sapbydesign.com/dps/d/preview/fd2a6eae2a4f4d79a10dc8da1a48a034/2014.12/en-US/SAP_HCI_OperationsGuide_External.pdf


http://help.sap.com/cloudintegration/SAP_HCI_DevGuide.pdf

2.4.1 Receiver Settings

2.4.1.1 Query Compound Employee

This receiver helps you to connect to SuccessFactors EC.

Field Description

Address SuccessFactors EC URL, for example,

https://test.successfactors.com

Credential Name Name of artifact that was deployed in Common

https://test.successfactors.com/

20


Table of Contents

Field Description

Configuration Steps

2.4.1.2 SFTP: Test and Production Version

This receiver helps you to connect to the SFTP server using the public certificate of Benefitfocus. You can use

either the test certificate or the production certificate. For more information, see Setting Up an HTTPS Connection

(Certificate-Based Authentication) in Connecting a Customer System to SAP HCI.

Field Description

Directory Directory name on the SFTP server where the resulting

file is to be stored, for example, /Test

Server Host SFTP server host URL, for example, test.sftp.com

User Name Name of the artifact that was deployed in Common

Configuration Steps

2.4.1.3 SFTP: Plain Text

This receiver helps you to send the resulting file of the process to a directory on the SFTP location.

https://proddps.prod.jpaas.sapbydesign.com/dps/d/preview/61b8bd715cf94d9e8234b6e1480aeb53/2014.12/en-US/SAP_HCI_OnboardingGuide_External.pdf

Field Description





Configuration Steps

2.4.1.4 Error Reporting

This receiver helps you to log the failing employees from the payload and to send the relevant information to a

directory on the SFTP location.

Field Description

Directory Directory name on the SFTP server where the log is to

be stored, for example, /Logs



Configuration Steps

2.4.1.5 Exception Message

This receiver helps you to log the exceptions that occur during a process run and to send the relevant information

to a directory on the SFTP location.

22


Table of Contents

Field Description

Directory Directory name on the SFTP server where the

exceptions are to be stored, for example, /Logs



Configuration Steps

2.4.1.6 Employee Data Warning

This receiver helps you to log the payload-related warnings during a process run and to send the relevant

information to a directory on the SFTP location.

Field Description

Directory Directory name on the SFTP server where the

warnings are to be stored, for example, /Logs



Configuration Steps

Note

Currently, SAP HANA Cloud Integration does not expose the SFTP file name and archive directory to be

changed at catalog level. If this is required, see Extending the Standard Data Integration.

2.4.2 Parameters

These parameters contain customizing options. To configure the parameters, you can override the default values.

The process parameters contain customizing options. To configure them, you can override the default values.

Parameter Name Description

Pay Frequency Pay Frequency field of Benefitfocus file

Benefitfocus Client ID Client ID for the Benefitfocus account/tenant

File Encryption Mode Specifies the type of deployment. DEMO sends to a disk connector on

a local atom. Other modes send to the Benefitfocus SFTP server

either encrypted or unencrypted.

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. (This is a

pay_group in job information and not in compensation information.)

This value must be enclosed in single quotes, for example, 'UM', 'UG'.

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. This value

must be enclosed in single quotes.

location Include the foundation object externalCode if you want to include only

employees associated with that foundation object. This value must be

enclosed in single quotes.

company Comma-delimited list (no blank spaces before/after comma) for

specifying the companies to include in the extract. This value must be

24


Table of Contents

Parameter Name Description

enclosed in single quotes, for example, 'ACE_USA', 'ACE_DE'.

company_territory_code Comma-delimited list (no blank spaces before/after comma) for

specifying the single company_territory_codes to include in the

extract. This value must be enclosed in single quotes.

business_unit Include the foundation object externalCode if you want to include only

employees associated with that foundation object. This value must be

enclosed in single quotes, for example, 'ACE_IND'.

Custom Filters Comma-delimited custom filters (no blank spaces before/after

comma) for the CompoundEmployee document in format

"person/national_id_card/country=USA,GRE;person/person_id=117",

etc.

person_id_external Comma-delimited list (no blank spaces before/after comma) for

specifying the person_id_externals to include in the extract. This value

must be enclosed in single quotes.

Terminate Filtered Employees Include newly filtered employees as terminated, one time

Pay Components Comma-delimited list (no blank spaces before/after comma) of pay

component IDs to include in calculating annual salary. If blank, all

(max 6) are included.

Include Terminations Determines how long terminated employees are included in the

payMax file before they are excluded

Custom Category Types You can use these fields to map a particular custom category type to a

particular EC field, for example:

Field: Custom Category Type 1

Value: Location

2.4.3 Value Mappings

The value mappings are translation tables between the EC picklist entries and the Benefitfocus values.

The following fields have been mapped through a value mapping project in SAP HANA Cloud Integration:

Name Suffix

Marital Status

Pay Frequency

Ethnicity

EEO Categories

You can modify the entries in this project to suit your needs.

In the Developer’s Guide for Managing Integration Content, see Developing Value Mappings for general

information about value mappings, and Editing the Value Mapping Project for information about editing value

mappings.


2.5 Extending the Standard Data Integration

This section describes cases where you want to enhance the current solution and to add custom fields.

To make changes, you must be familiar with the following topics:

SAP HANA Cloud Integration process development

SAP HANA Cloud Integration provides integration tools on the Eclipse platform to model integration flows,

configure attributes of the integration flows, and deploy them to the runtime. For more information, see the

Developer’s Guide for Managing Integration Content.

EC compound APIs

Example

You want to enhance the current process to adjust 10 custom fields in the destination file. In this case, the

mapping palette of the SAP HANA Cloud Integration process needs to be changed to adjust the 10 user-

defined fields. Once the fields are introduced, you can choose to map the required field from EC to the

destination fields.


26


Table of Contents

3 Benefits Data Replication

This chapter describes how to export benefits data from Benefitfocus to 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.

In SAP HANA Cloud Integration:

SAP HANA Cloud Integration accesses this SFTP location and transfers the benefits data to EC Payroll using a

web service call.

In EC Payroll:

Web service call to EC Payroll automatically updates the benefits information in EC Payroll.

Note

These specifications apply to the US country version. If a customer implements any other country

version, some adjustments might be necessary.

SAP Note 1935616 describes in detail the custom implementation of a web service in EC Payroll. Please

implement this note in the customer's EC Payroll system, following the instructions carefully to execute the web

service correctly.

From the May 2014 release onwards, we recommend using the standard web service that is available to update

benefits information in EC Payroll. This web service is delivered as standard in the following add-on. The add-on is

a prerequisite for using the standard web service.

SFIECPEP 100 - SuccessFactors Employee Central Payroll, third-party data integration tool

3.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.

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. No default implementation of this BAdI is provided because the implementation

differs from customer to customer based on their requirements. For more information, see the BAdI

documentation.

3.1.1 Processing Custom Fields Using Business Add-Ins

If Benefitfocus enhances the file layout with customer-specific fields requiring processing, or if additional fields

that are part of the file layout, but not part of the standard BAdI parameters, need to be passed to the BAdI for

processing, you can achieve this as follows:

http://service.sap.com/sap/support/notes/1935616

1. Add the new fields in the SAP HANA Cloud Integration maps and map them to custom fields in the profile, or

map the existing fields required for processing inside the BAdI using data map extensions.

2. Implement the BAdI to process the fields according to the customer's requirements.

Example

The following example shows how additional fields that are part of the file layout can be passed to BAdIs

for processing.

1. In the Design space, click the SuccessFactors EC with Third-Party Benefits Vendor — Benefitfocus

integration process and configure the Benefitfocus to EC Payroll integration flow.

2. Under Parameters, maintain the name for the value to be passed in each custom field.

28


Table of Contents

The names in these parameters will be available inside the BAdI with the value.

3. Access this process in the Integration Designer perspective.

For more information, see Developing Integration Content Using the Integration Designer in the

Developer's Guide for Managing Integration Content.

4. Map the required values to the CUST_VALUE fields, making sure the respective values are mapped in

the order of the names specified in step 2 above.

After the additional fields are configured in SAP HANA Cloud Integration, the fields are available in the

BAdI for processing.


3.2 Benefits Data Mapping

The following fields are considered during the replication.

Position

(Delimited)

Field Name Size Type Trigger Description Value Mapping EC Payroll

Field

Mapping

1

(A)

Social

Security

Number

(SSN)

9 A N Employee Social

Security Number

Format: No

punctuation

2

(B)

Employee ID 19 A N Employer-specific

number to identify

the employee

PERSNO

3

(C)

First Name 50 A N Employee First

Name

4

(D)

Middle Name 50 A N Employee Middle

Name

5

(E)

Last Name 50 A N Employee Last

Name

6

(F)

Suffix 10 A N Employee suffix

7

(G)

Benefit Type 30 A N Employee Benefit

Type

Example: If the

benefit type is a

medical plan

“Medical” will be

populated. If the

benefit type is a

dental plan

“Dental” will be

populated.

Benefit Type WAGETYPE

8

(H)

Plan Name 50 A Y Benefit Plan Name.

This shows exactly

what the

application has

stored.

9

(I)

Coverage

Level

30 A Y Benefit Coverage

Levels

Example: If the

coverage level is

30


Table of Contents

Position

(Delimited)


Field

Mapping

Employee and

Spouse, then

“Employee and

Spouse” will be

populated. If the

coverage level is

Employee + 1, then

“Employee + 1” will

be populated.

10

(J)

Coverage

Amount

50 M Y Benefit Coverage

Amount –

Corresponds to

total coverage

amount.

Format:

DDDDD.CC

Note: Primarily

used to report

coverage amounts

for life and

disability benefits.

11

(K)

Pre-Tax

Premium

1 N Y 0 = Post-Tax; 1 =

Pre-Tax

Note: Setting must

be enabled for

each health plan in

order for the

indicator to be

included.

Benefit Type WAGETYPE

12

(L)

Employer

Annual Cost

8 M Y Total Annual Cost

to the employer for

the year.

Formatted to

include two

decimal places.

Format:

DDDDD.CC

No Symbols

13

(M)

Employee

Annual Cost

8 M Y Total Annual Cost

to the employee

for the year.

Formatted to

include two

Position

(Delimited)


Field

Mapping

decimal places.

Format:

DDDDD.CC

No Symbols

14

(N)

Pay

Frequency

2 N Y Number of pay

periods per year.

This number will

remain consistent.

EC Payroll

Frequency Code

FREQUENCY

15

(O)

Employee

Cost Per pay

Period

8 M Y Employee Cost per

pay period

Format:

DDDDD.CC

No Symbols

Note: Default

formula used is

Annual Cost/Pay

Frequency. For

Flex plans the

formula is Annual

Cost/Remaining

Pay Periods. In the

event that

Remaining Pay

Period is not

active, the default

formula will be

applied.

AMOUNT

16

(P)

Imputed Cost 8 N Y Total Annual

Imputed Income

Amount

Format:

DDDDD.CC

No Symbols

AMOUNT

17

(Q)

Employee

Pre Tax Cost

8 N Y Total Annual

Employee Pre Tax

Cost

Format:

DDDDD.CC

No Symbols

GOAL_AMOU

NT

18

(R)

Employee

Post Tax

Cost

8 N Y Total Annual

Employee Post Tax

Cost

GOAL_AMOU

NT

32


Table of Contents

Position

(Delimited)


Field

Mapping

Format:

DDDDD.CC

No Symbols

19

(S)

Employer Pre

Tax Cost

8 N Y Total Annual

Employer Pre Tax

Cost

Format:

DDDDD.CC

No Symbols

AMOUNT

20

(T)

Employer

Post Tax

Cost

8 N Y Total Annual

Employer Post Tax

Cost

Format:

DDDDD.CC

No Symbols

AMOUNT

21

(U)

Effective

Start Date

8 D Y Benefit Start Date.

Date benefit is

effective.

Format:

CCYYMMDD

FROM_DATE

22

(V)

Effective End

Date

8 D Y Benefit End Date.

Date benefit ends

Format:

CCYYMMDD

TO_DATE

23

(W)

Election

Status

1 A Y A = Employee is

active and benefit

is active.

Enrollment

records will include

a benefit effective

start date only for

active employment

records.

C = Employee is

active but benefit

is cancelled.

Enrollment


a benefit effective

start date and a

benefit effective

end date, as a

EC Payroll

Negated

Election Code

NEG_ELECTI

ON

Position

(Delimited)


Field

Mapping

result of the

cancellation

transaction

processed by an

online enrollment

user for active

employment

records.

W = Employment

is active but

benefit was

waived/refused.

Enrollment


a benefit effective

end date only for

active employment

records.

T = Employment is

terminated and

benefit is cancelled

as a result.

Enrollment


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.

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.

34


Table of Contents

Position

(Delimited)


Field

Mapping

25

(Y)

Payroll

Attribute

Code 1

25 A Y Provide a logic

table for

determining

unique plan codes,

coverage codes, or

deduction codes if

needed.

26

(Z)

Payroll

Attribute

Code 2


table for

determining

unique plan codes,

coverage codes, or

deduction codes if

needed.

27

(AA)

Payroll

Attribute

Code 3


table for

determining

unique plan codes,

coverage codes, or

deduction codes if

needed.

28

(AB)

Payroll

Attribute

Code 4


table for

determining

unique plan codes,

coverage codes, or

deduction codes if

needed.

29

(AC)

Payroll

Attribute

Code 5


table for

determining

unique plan codes,

coverage codes, or

deduction codes if

needed.

30

(AD)

Deferral Pct 8 N N Percent per pay

period for 401(k)

deduction

Format: 0.00

Example: 5% = .5

31

(AE)

Deferral Flat

Amount

8 N N Per pay period flat

amount for 401(k)

Position

(Delimited)


Field

Mapping

deduction

3.3 Getting Access to the Solutions

SAP HCI Spaces is a Web-based application that helps you to access the integration content available for a

particular tenant on an on-demand integration infrastructure. In SAP HCI Spaces, you can access integration

packages with artifacts such as, value mappings, integration flows, and files. For more information, see Viewing

Integration Flow Configurations in the Developer's Guide for Managing Integration Content.

You can edit and configure a package as follows:

1. On the Discover tab, click the integration package to be configured.

2. Choose Copy (as shown in the following figure).

On the Design tab, you should now find the copied package.

3. To configure and edit the package, follow Editing Integration Flow Configurations in the SAP HANA Cloud

documentation.

3.3.1 Common Configuration Steps

3.3.1.1 SAP Credential Deployment

To deploy the following artifacts, see Deploying and Editing a User Credentials Artifact in the Operations Guide for

SAP HANA Cloud Integration.


SuccessFactors EC Credentials These credentials are used to connect to the

SuccessFactors EC system

SuccessFactors EC Payroll Credentials These credentials are used to connect to the

SuccessFactors EC Payroll system




https://proddps.hana.ondemand.com/dps/d/preview/93810d568bee49c6b3d7b5065a30b0ff/2014.10/en-US/frameset.html?1e556bced9b84c84889cadb7ccc79dd4.html



36


Table of Contents


SAP SFTP Server Credentials These credentials are used to connect to the SFTP

server

Benefitfocus SFTP Server Credentials These credentials are used to connect to the

Benefitfocus SFTP server

For more information about SFTP-based communication, see the Operations Guide for SAP HANA Cloud

Integration.

3.3.1.2 Value Mapping Maintenance

A value mapping project is delivered along with the iFlows in this integration. It must be deployed in the customer

landscape so that the iFlows can refer to them. For information about using and editing value mappings, see the

Developer’s Guide for Managing Integration Content.

3.3.2 Setting Up the Standard Data Integration

In the Discover section, click the SuccessFactors EC with Third-Party Benefits Vendor — Benefitfocus integration

process and configure the Benefitfocus to EC Payroll integration flow.




3.3.2.1 Receiver Settings

3.3.2.1.1 EC Payroll

This receiver helps you to connect to the SuccessFactors EC Payroll system.

Field Description

Address EC Payroll connection URL

Credential Name Name of the artifact that was deployed in Common

Configuration Steps

3.3.2.1.2 SFTP: Successful Records

This receiver helps you to send the resulting file of the process to a directory on the SFTP location.

Field Description




38


Table of Contents

Field Description


Configuration Steps

3.3.2.1.3 SFTP: Error Records and Invalid Records

This receiver helps you to log the failing employees from the payload and send the relevant information to a

directory on the SFTP location.

Field Description

Directory Directory name on the SFTP server where the logs are

to be stored, for example, /Logs



Configuration Steps

3.3.2.1.4 SFTP: Negated Elections and Mandatory Fields Missing

This receiver helps you to capture negated elected records and the records where mandatory fields are missing

from the payload and to send the relevant information to a directory on the SFTP location.

Field Description

Directory Directory name on the SFTP server where the logs are

to be stored, for example, /Logs



Configuration Steps

Note

Currently, SAP HANA Cloud Integration does not expose the SFTP file name and archive directory to be

changed at catalog level. If this is required, see Extending the Standard Data Integration.

3.3.2.2 Value Mappings

The cross-reference tables are translation tables between the Benefitfocus values and EC Payroll values.

The following fields have been mapped through a value mapping project in SAP HANA Cloud Integration:

Pay Frequency

Negated Elections

Employer Contribution Benefit Type

3.4 Data Replication Details

Employee benefit deduction data will be sent from Benefitfocus to EC Payroll in CSV format, then converted into

infotypes depending on the plan type category and processed into EC Payroll as an XML file upload.

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.

3.4.1 Health/Insurance/Credit/Disability/FSA Plan Processing

For Health, insurance, Disability, Credit plans, FSA and HSA plans, the EC Payroll benefits engine is not used. The

complete processing, that is, pre-tax contribution, post-tax contribution, employee contribution, and employer

contribution happens at the third-party provider side and only the deduction amounts are passed to the payroll

system.

EC is the system of master data for all employees.

Benefitfocus requires employees master data and eligibility data is sent from EC to Benefitfocus.

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. (SSO Enabled)

40


Table of Contents

Benefitfocus does all the benefits processing and sends the employee and employer deduction/contributions

to EC Payroll, 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.

The pay code information from the provider (that is, pre-tax contribution, post-tax contribution, employee

contribution, employer contribution) is mapped to the wage type on the EC Payroll side. The details of the

wage types for each plan processing is passed over to the provider in advance during implementation, so that

we get the right wage type information in the file from the provider for the respective plans.

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 payroll results stored in the payroll cluster can be used for reporting to the third-party provider.

3.4.2 401(k) Saving Plan Processing

For 401(k) saving plans, the EC Payroll benefit engine is used to process the plans because of the legal rules

involved in processing of these plans. For example, if an employee didn’t pay the premium, 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, for example, by check or some other means.

For benefit plans where the benefits engine is used for processing, 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.

EmployeeCentral is the system of master data for all employees.

Benefitfocus required employees master data and eligibility data is sent from EC to Benefitfocus.

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. (SSO Enabled)

Benefitfocus sends the percentage contribution for 401(k) plan or the deferred amount per pay period in the

file, which is update in the infotype 0169 for savings plan. The complete processing of plan is done by benefits

engine.

Employer contribution can be configured as a part of benefits customizing for the plans and benefit engine will

take care of process the same.

If in case employer contribution is not configured in the system for 401(k) plans, 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 one-

time payment.

The pay code information from the provider (that is, pre-tax contribution, post-tax contribution, 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, post-tax, employee contribution or employer contribution.

The details of the wage types for each plan processing is passed over to the provider in advance during

implementation, so that we get the right wage type information in the file from the provider for the respective

plans.

The details of employer contribution configuration in the system should also be communicated to the

provider during implementation, so that the employer contribution is not passed if configured in the benefits

engine.

The payroll processes the information and the results are stored in payroll cluster PLC2 for all employee.

The payroll results stored in payroll cluster can be used for reporting to the third-party provider.

3.4.3 Pay Code Wage Type Mapping

Pay code, on the third-party provider's side, is key to which defining how the plan (amount) should be processed,

that is, 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. 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.

During implementation, 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, 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, the following attributes are derived and updated in the infotypes

accordingly:

Employee contribution

Employer contribution

Pre-tax contribution

Post-tax contribution

Infotype to update

42


Table of Contents

3.4.3.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, for example, for saving plans (401(k) plans).

The employer contributions can be in the form of an amount ($) or as percentage (%). For plans other than

savings, that is, 401(k) plan, the employer contributions will be in the form of an amount ($), for example, for FSA

plan, HSA plan, dental plan, vision plan, insurance plan etc. 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.

Note

By default the employer contribution is process per pay period for all the plans, 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.

Assumption:

Employer contribution in % for plans other than 401(k) savings plan is out-of-scope. For 401(k) saving plans,

customers have to configure the same as a part of benefits configuration.

Customer will not configure plans other than 401(k) saving plans using benefit engine.

Bonus contribution & pension contribution to saving plans are out-of-scope and are not handled through this

integration.

3.4.3.2 Employee Contribution

For plans where the benefits engine is not used, for example, for FSA, health, insurance, disability, and credit

plans, the third-party provider will completely process the plan and send per pay period employee pre-tax and

post-tax deduction to EC Payroll.

For plans where the benefits engine is used for processing, for example, savings plans, 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.

Note

Employee's imputed income is processed per pay period for all the plans.

3.5 Configuring the Wage Types

Benefits providers send contribution amounts for benefit plans directly for payroll deduction. There are no

standard wagetypes shipped for this purpose; and customers have to create their custom wage types for this

purpose. This can be done as follows:

1. Select Personnel Management → Personnel Administration → Payroll Data → Employee Remuneration

Information → Wage Types → Create Wage Type Catalog.

2. Select copy and enter a country.

3. Select wage type and click Copy.

4. Adapt the wage type as follows:

Example

Wage type for "Standard Medical Employee pre-tax", for example, 2C01 has to be made permissible for

infotype 0014, that is, IT 0014.

Wage Type

Wage Type

Description

EE

or

ER

Paid

Pre/Post

Tax Type

Where

Used

With Goal

Info

2C01

Std Medical

Employee pre-tax EE Pre Deduction IT 0014

2C02 Std Medical Employer ER Post Deduction IT 0014

2C10

Dental Employee pre-

tax EE Pre Deduction IT 0014

2C11 Dental Employer ER Post Deduction IT 0014

2C15 Opt Life EE after-tax EE Post Deduction IT 0014

BE31

401(k) Employee pre-

tax 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 IT 0015

2C22

Health Savings

Employer ER Post Deduction IT 0014

2C25/2C26

Flex Spending

Employee pre-tax EE Pre Deduction IT 0014 IT 0015

2C27

Flex Spending

Employer ER Post Deduction IT 0014

2C30

Basic Life Employer

Covered ER Post Deduction IT 0014

www.sap.com/contactsap

44


Table of Contents

Material Number

© 2012 SAP AG. 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 AG. The information contained herein

may be changed without prior notice.

Some software products marketed by SAP

AG and its distributors contain proprietary

software components of other software

vendors.

Microsoft, Windows, Excel, Outlook, and

PowerPoint are registered trademarks of

Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System

ads, System i5, System p, System p5,

System x, System z, System z10, System z9,

z10, z9, iSeries, pSeries, xSeries, zSeries,

eServer, z/VM, z/OS, i5/OS, S/390,

OS/390, OS/400, AS/400, S/390 Parallel

Enterprise Server, PowerVM, Power

Architecture, POWER6+, POWER6,

POWER5+, POWER5, POWER, OpenPower,

PowerPC, BatchPipes, BladeCenter, System

Storage, GPFS, HACMP, RETAIN, DB2

Connect, RACF, Redbooks, OS/2, Parallel

Sysplex, MVS/ESA, AIX, Intelligent Miner,

WebSphere, Netfinity, Tivoli and Informix are

trademarks or registered trademarks of IBM

Corporation.

Linux is the registered trademark of Linus

Torvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript,

and Reader are either trademarks or

registered trademarks of Adobe Systems

Incorporated in the United States and/or

other countries.

Oracle is a registered trademark of Oracle

Corporation.

UNIX, X/Open, OSF/1, and Motif are

registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood,

MetaFrame, WinFrame, VideoFrame, and

MultiWin are trademarks or registered

trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are

trademarks or registered trademarks of

W3C®, World Wide Web Consortium,

Massachusetts Institute of Technology.

Java is a registered trademark of Sun

Microsystems, Inc.

JavaScript is a registered trademark of Sun

Microsystems, Inc., used under license for

technology invented and implemented by

Netscape.

SAP, R/3, xApps, xApp, SAP NetWeaver,

Duet, PartnerEdge, ByDesign, SAP Business

ByDesign, and other SAP products and

services mentioned herein as well as their

respective logos are trademarks or

registered trademarks of SAP AG in Germany

and in several other countries all over the

world. All other product and service names

mentioned are the trademarks of their

respective companies. Data contained in this

document serves informational purposes

only. National product specifications may

vary.

These materials are subject to change

without notice. These materials are provided

by SAP AG and its affiliated companies ("SAP

Group") for informational purposes only,

without representation or warranty of any

kind, and SAP Group shall not be liable for

errors or omissions with respect to the

materials. The only warranties for SAP Group

products and services are those that are set

forth in the express warranty statements

accompanying such products and services, if

any. Nothing herein should be construed as

constituting an additional warranty.

46


Table of Contents

012002523100002927442015e-2

Documents

table names

menu names

names of installation

names of variables

program names

integration options

directory names

field names