My Successfactors work at a client

I was an EC consultant I worked on the overall architecture, data mapping and business requirements to implement Employee Central, Rubbermaid had a lot of custom rules that were created in the legacy system, we had to write over 300 rules or propagation of data, event derivation rules and workflow rules.

Following are some examples:

Event Derivation Rules

–

<!– Position transfer and reclassification rules are being set to trigger for the Rubbermaid so typical promotion/transfer type transactions can still be triggered using the usual demo population. Also there needs to be some defensive logic to make sure position field is not blank for position events. Rubbermaid Midwest region will be identified with cost center = 9103000 !–>

POS_XFR

-POS_XFR—POS_RECLASS–

Also configured and setup rule for Lateral job movement

JOBLATRL–

Workflow Rules

–

<!–Supervisor Change Only–>

ChgSuprv—NameChange—

<!–If Change to Employment Dates then EMPLY_CHG–>

EMPLY_CHG—

<!–If Change to Stock Elig then STOCK_CHG–>

STOCK_CHG–

I also worked on Data mapping for interfaces and custom object development.

Sample work for Data mapping

Mapped Country and National ID fields

Custom Object Development for OM and Boomi integration

OM integration from SF EC to SAP using Boomi Atom Sphere

Staging Areas for OM (Objects replication): Once the replication runs using Boomi,

the following staging are tables are populated, then the programs can be used to process them to create info type records.

Program Names:

RH_SFIOM_PROC_EE_ORG_ASS_RPRQ – Replication from Employee Central to ERP Organizational Management

RH_SFIOM_PROC_ ORG_STRUC_RPRQ – Replication of Org. Items from EC to ERP Org Management

Staging area tables.

Table Description

SFIOM_KMAP_OSI Organizational Structure Item Key Mapping

SFIOM_RPRQ_EE Replication Request Employee

SFIOM_RPRQ_ORGAS

Replication Request Organizational

Assignment

SFIOM_RPRQ_OSI Replication Request Organizational Structures

SFIOM_RPRQ_OSIDT Replication Request Organizational Structures

Mapping Tables Success Factors and SAP Integration:

Note: The following tables needs to be maintained for client specific values. By default, SAP uses the standard values that come out of the box.

Table Name Description

PAOCFEC_COUNTRY Replication Countries

PAOCFEC_CURR Currency of Wage Type

PAOCFEC_EEKEYMAP Employee Key Mapping

PAOCFEC_EXTMAP Employee Central Extensibility Mapping Con

PAOCFEC_H_IT_SEL Allowed Infotypes for Wage Type Distributi

PAOCFEC_KMAPCOMC Company Code Key Mapping

PAOCFEC_KMAPCOSC Cost Centre Key Mapping

PAOCFEC_KMAPPEST Permanent Establishment Key Mapping

PAOCFEC_LIST_ID Default List IDs for GDT Codes

PAOCFEC_MAP code mapping

PAOCFEC_MAP_C code mapping (customer specific)

PAOCFEC_MAP_CC code mapping customer client specific

PAOCFEC_MAP_DATE Employee Central Date Type Mapping

PAOCFEC_MAP_MOD Mapping for defaulted ListIDs of GDTs

PAOCFEC_S_DATE Allowed Dates for Date Type Mapping

PAOCFEC_S_INFTY Allowed Infotypes for Extensibility Mapping

PAOCFEC_S_NODE

Allowed Node Names for Extensibility

Mapping

PAOCFEC_V_EXTMAP Employee Central Extensibility Mapping Con

PAOCFEC_WT_PROC Processing of Wage Types in EC Replication

Employee Key Mapping: PAOCFEC_EEKEYMAP :

This is the main table used for SF to SAP integration. This table is used as bridge (linkage) between SF and SAP.

For Hires, the record is created in this table, And for any existing employee, this table is referred whether or not to update the info type records.

This table is the key for Conversion purposes as well. All employees should converted (loaded) into this table before the first replication in order to update the existing employee records.

Note: For New Hires, record will be created in this table as well as Info type 0105 and ST ECUS will be created.

Integration issues/Key points

There were few issues you might encounter during the SF EC-SAP standard replication, some of these

SAP standard and some of client specific. For all the standard issues, SAP addressed through OSS

Notes/Support Pack upgrades and for some, SAP has provided work around solutions for time being. The expectation is that all of these work around should be fixed in future SAP SP releases.

Company Code Transfer:

Currently company transfer in EC, when replicated to SAP, new pernr is generated, which is not acceptable to any (or most) customers. The work around has been provided by SAP. The following step would address the inter-company transfers.

Setup of Employee Central Payroll to support retaining the ERP PERNR in case of

Intercompany Transfers

Scenario

Employee Central Legal Entities US_A, US_B and US_C are in such a relationship that for intercompany transfers between these, no new PERNR shall be created in the ERP system. Nevertheless, they ar represented by different Company Codes (BUKRS).

Prerequisites

1) The company codes US_A, US_B and US_C share one single controlling area.

2) The cost center mapping table PAOCFEC_KMAPCOSC

is not being used.

This means that the Employee Central Cost Center Keys are identical to the cost center keys in

the ERP system.

N.B. The 1308-deliverd BAdI for mapping of Emplyoee Central Cost Centers to ERP Internal Orders

or WBPS Elements can still be used.

Preparation

Identify one of the Legal entities US_A, US_B and US_C to be the leading legal entity. Let us assume US_A is the leading entity.

Setup in Employee Central

1) Activate a custom_string field on JobInformation.

2) Set field length to 4 and change field name to BUKRS.

3) No pick list needed.

4) Configure the field to be invisible to normal employees, visible but read-only to admins and editable to super-admins only.

5) Set up a rule which populates the field with the value of field LegalEntity whenever the latter is changed. N.B. If the Legal Entity Codes in Employee Central do not coincide with the BUKRS values in ERP, then a value mapping must be incorporated in this rule.

Setup in the Payroll System

1) Configure the custom field for BUKRS to be mapped to field BUKRS on infotype 0001 in the field

extensibility settings for replication.

2) In the mapping from legal entities to company codes, map all three entries US_A, US_B and

US_C to company code US_A.

3) Do not use table PAOCFEC_KMAPCOSC for cost center mapping but use identical keys instead.

Defaults values and solutions:

Standard replication defaults few data elements, the identified data elements are Work Contract, Job on Info type 0001, Additional Time indicator on Info type 0007 and there are many other such as Pay scale structures etc. Every time PA IFlow runs, these values are either will be over written with default values or blanks them out. Depends on the customer needs. You can consider either the custom solutions to restore the values or create/change the corresponding configuration. If you choose to custom solution, you can consider enhancing the info types and/or create custom tables and develop ABAP program restores the values.

Currently (as of component PASEIN SP 5 ), the following integration requirements are still in not in place.

These can be address either using the implicit enhancement or by BADI provided by SAP. Please note the

standard BADI is available from PASEIN SP 7.