Integration Known issues - A

Known Issues

Known Issue: You Have Created or Changed an Organizational Object in Employee Central, but this Change Is Not Reflected in SAP S∕4HANA

Known Issue: After Replication of Organizational Assignment Data from Employee Central to SAP S∕4HANA, the Error "Manager ID not Found" Is Shown

Known Issue: After Replication of Organizational Assignment Data from Employee Central to SAP S∕4HANA, a New Position and a New Assignment to this Position Are Created Although a Position Assignment Already Exists

Known Issue: After You Have Changed the External Code of an Organizational Object in Employee Central, the Organizational Assignments in SAP S∕4HANA Are no Longer Correct

Known Issue: After Data Replication from Employee Central to SAP S∕4HANA Error Messages Related to Positions are Shown in the Application Log

Known Issue: You Have Changed the Job Classification Title or Description in Employee Central, but Your Changes Aren't Replicated to SAP S∕4HANA

Known Issue: Organizational Structure Items Can't Be Replicated Because cust_toDivision and cust_toBusinessUnit Associations Are Missing

Known Issue: "Invalid Property Name" Error Message is Shown for FOBusinessUnit/nameTranslationNav and FODivision/nameTranslationNav

Known Issue: Replication Request Monitor Shows Internal Server Error

Known Issue: Mandatory Field HRP1000-STEXT Was Not Mapped

Known Issue: Deletions Aren't Replicated from Employee Central

Known Issue: Cost Center Assignments Are Deleted When You Use a Default Cost Center in SAP S∕4HANA

Known Issue: Organizational Assignment Change Extends Too Far Into the Past

Known Issue: Staging Area Tables Contain a Large Amount of Data

Known Issue: Employee is Inactive, Rehire to Be Replicated from Employee Central First

Mapping of SuccessFactors Fields for Employee Data to SAP ERP

Mapping of SuccessFactors Fields for Employee Data to SAP ERP

The following list shows which field contents from the SAP ERP system you can extract for which SuccessFactors fields. You define the extraction options on the selection screen of the report that you use to extract the data. For more information, see SAP Library for the add-on and choose Integration Scenario for Employee Data in the Extraction Options section.

Note

You also have the option of defining a customer-specific Business Add-In implementation for each of the fields.

SuccessFactors Field	SAP ERP Field	Comment
STATUS	Employment status from the Actions infotype (0000).	The SAP ERP status is mapped to the SuccessFactors status as follows: Active > Active Pensioner > Inactive Left Company > Inactive Inactive > Inactive
USERID	Central person (object type CP) External person ID from the infotype Person ID (0709)
USERNAME	User (object type US) Central person (object type CP)
FIRSTNAME	Infotype Personal Data (0002) Customizing	You make the relevant Customizing settings in Customizing for the integration add-on for SAP ERP HCM and SuccessFactors under Integration Scenario for Employee Data  Define Name Format for Fields FIRSTNAME and LASTNAME
LASTNAME	Infotype Personal Data (0002) Customizing	You make the relevant Customizing settings in Customizing for the integration add-on for SAP ERP HCM and SuccessFactors under Integration Scenario for Employee Data  Define Name Format for Fields FIRSTNAME and LASTNAME
MI	Infotype Personal Data (0002)
GENDER	Infotype Personal Data (0002)
EMAIL	Infotype Communication (0105), subtype E-Mail (0010) Infotype Communication (0105), subtype E-Mail (MAIL) User data
MANAGER	Relationship Is managed by… (B012) between the employee’s organizational unit and the manager’s position Relationship Reports (line) to (A002) between the employee’s position and the manager’s position Entry NO_MANAGER	The option NO_MANAGER is available only for the report Sync Employee Data with SuccessFactors in Pre-Hire Period(RH_SFI_PREHIRE_EMPL_DATA). NO_MANAGER is the default setting.
HR	Administrator for HR master data from the Organizational Assignmentinfotype (0001) Entry NO_HR	The option NO_HR is available only for the report Sync Employee Data with SuccessFactors in Pre-Hire Period(RH_SFI_PREHIRE_EMPL_DATA). NO_HR is the default setting.
DEPARTMENT	Organizational unit from the Organizational Assignment infotype (0001) Cost center from the Organizational Assignment infotype (0001)
JOBCODE	Job from the Organizational Assignmentinfotype (0001)
DIVISION	Company code from the Organizational Assignment infotype (0001)
LOCATION	Personnel area from the Organizational Assignment infotype (0001)
TIMEZONE	User data
HIREDATE	Feature ENTRY
EMPID	Personnel number
TITLE	Position from the Organizational Assignment infotype (0001) Job from the Organizational Assignment infotype (0001) Customer-specific implementation
BIZ_PHONE	Internal telephone number (two fields) from the infotype Internal Data (0032) Infotype Communication (0105), subtype First Telephone Number at Work (0020)
FAX	Infotype Communication (0105), subtype Cell Phone (CELL)
ADDR1	Description of personnel area from the Organizational Assignment infotype (0001)
ADDR2	Street of personnel area from the Organizational Assignment infotype (0001)
CITY	City of personnel area from the Organizational Assignment infotype (0001)
STATE	Region of personnel area from the Organizational Assignment infotype (0001)
ZIP	Zip code of personnel area from the Organizational Assignment infotype (0001)
COUNTRY	Country key of personnel area from the Organizational Assignment infotype (0001) Country key for the employee's country grouping	The SAP ERP country keys are mapped to the country descriptions used in SuccessFactors
REVIEW_FREQ	Customer-specific implementation
LAST_REVIEW_DATE	Customer-specific implementation
CUSTOM01	Personnel subarea from the Organizational Assignment infotype (0001)	You can define how to fill each CUSTOM field
CUSTOM02	Employee group from the Organizational Assignment infotype (0001)	You can define how to fill each CUSTOM field
CUSTOM03	Employee subgroup from the Organizational Assignment infotype (0001)	You can define how to fill each CUSTOM field
CUSTOM04 – CUSTOM15	Customer-specific implementation	You can define how to fill each CUSTOM field
MATRIX_MANAGER	Relationship Reports (line) to (A002) between the employee’s position and the managers' positions	For the report Sync Employee Data with SuccessFactors in Pre-Hire Period(RH_SFI_PREHIRE_EMPL_DATA), the default setting is that no data is transferred for the field MATRIX_MANAGER.
DEFAULT_LOCALE	Communication language (field SPRSL) from the infotype Personal Data (0002)	The SAP ERP languages are mapped to the language labels used in SuccessFactors (for example, DE to de_DE). If there is not corresponding entry in SuccessFactors for the language used in the SAP ERP system, no content is transferred for the field DEFAULT_LOCALE.
CUSTOM_MANAGER	Customer-specific implementation
SECOND_MANAGER	Customer-specific implementation
PROXY	Customer-specific implementation
LOGINMETHOD	Character string SSO: The employees can only use Single Sign-On to log on to the SuccessFactors system Character string PWD: The employees can only use their password to log on to the SuccessFactors system

Field/Entity in Employee Central	Field/Term in SAP ERP HCM systems
Employee Class	Employee Group
Employment Type	Employee Subgroup
Event	Personnel Action
Event Reason	Reason for Personnel Action
Frequency	Period Parameter
Job Classification	Work Contract
Job Location/Custom String	Personnel Area/Personnel Subarea
Pay Component	Wage Type
Pay Group	Payroll Area
Salutation	Form of Address Code
Suffix	Name Supplement Code
Payment Method	Payment Form Code

Key terminology for Organization Management

SF Employee Central term	Description	SAP ERP HCM equivalent
Foundation Objects	The primary objects and data that is used in employee records (e.g. Company, Job Classification, Pay Grade, etc.)	Object Type / Master Data / Transparent table
Assocations	Relationships between objects	Relationship
Generic Objects	Custom objects crated with the Metadata Framework	Object Type
Organization Structure	The organization structure used to manage the enterprise	Organization Structure
Propagation	Auto-population of field values on an employee’s Employment Information from Foundation Objects	Default values set by Features in PE03

Foundation Object	SAP ERP HCM equivalent
Legal Entity	Company Code
Business Unit	Business Area / Organizational Unit (Object type O)
Division	Organizational Unit (Object type O)
Department	Organizational Unit (Object type O)
Location	Personnel Area / Personnel Subarea
Cost Center	Cost Center (Object type K)

Foundation Object	SAP ERP HCM equivalent
Pay Component	Wage Type
Pay Component Group	Wage Type Group
Pay Group	Payroll Area
Pay Grade	Grade
Pay Range	Pay Scale
Pay Calendar	Payroll Calendar
Frequency

Pay Component

A Pay Component is the Employee Central equivalent of a Wage Type. It defines a certain element of an employee’s compensation package, such as salary or a parking allowance. It also defines how the company pays the employee for that specific type of pay. By default, a Pay Component defines:

• Type of the Pay Component
• Whether it is an earning
• Currency of the payment
• Value (if the Pay Component has a pre-defined, fixed value)
• Frequency of payment
• Whether it is recurring
• Whether the value or attributes on the UI can be overridden
• Tax treatment (e.g. taxable or tax exempt)
• Whether it will be displayed in Self-Service access
• Whether it can be used for Compensation planning
• Whether it is a pay target (e.g. a performance-related or target-related bonus)

Pasted from <https://help.sap.com/viewer/f69be9cbab414acdbeb3abdeaa1deed6/1711/en-US/a3217ff088c84966805bea963a14bd3e.html>

Pasted from <https://help.sap.com/viewer/9c2f8380e6d14dd1adb43bfeebfcb2a1/3.0%20SP06/en-US/5b59ee2d162841fda33d5781fcd0b7e3.html>

https://help.sap.com/viewer/9c2f8380e6d14dd1adb43bfeebfcb2a1/3.0%20SP06/en-US/9bc3c6536c474c59e10000000a4450e5.html

Magnetic Media Files are Not getting Generated for US Tax Forms -SAP

 Magnetic Media Files are Not getting Generated for US Tax Forms -SAP

1. Check v_t51t8 in SM34,  select HR_F_941 and then "Issuing of Tax Forms"  The only TEMSE you have selected to generate is HR_F_941_9ADJ .If you want to generate magnetic media , we need to configure in the system here. 

Gross- Up Payroll : USA Notes

What is a gross up?

 A gross up is a type of payment in which a gross amount is calculated so that, after taxes are deducted, an employee receives a specified net payment. The specified net amount is called the "guaranteed net amount" and the calculated gross amount is called the "grossed up amount." 

In SAP payroll, the user enters the guaranteed net amount into master data.  During payroll processing, the system passes the net amount to BSI, which determines the gross amount, that ill yield the net after taxes have been deducted. 

The guaranteed net wage types can be identified by a Processing Class 68 value of 5 (Gross up using regular method) or 6 (Gross up using supplemental method). 

SAP delivers the model wage types M031 and M032 for gross up payments.  M031 is the guaranteed net wage type and M032 is the gross up amount wage type. M031 and M032 are linked in view V_512W_B ( IMG Path : Spro - Payroll USA - Tax - Tax-related Wage types - Maintain Gross up Wage types).  M032 is the first derived wage type of M031. The linked wage type M032 stores the grossed up amount that is calculated by BSI.  Both the guaranteed net and grossed up amounts are stored in the Results Tables.
  

For example, suppose you wish to pay an employee $1000 after taxes has been taken.  In Infotype 15, you could create a record with wage type M031 with a $1000. The $1000 guaranteed net amount is passed to BSI, which determines the gross amount that would result in a net amount of $1000 after taxes.  Suppose that BSI calculates that a gross amount of $1500 will result in a net payment of $1000.  The system creates the wage type M032 with an amount of $1500 and stores this and the M031 wage type in RT. The grossed up amount is affected by several factors, including pay schedule (weekly, bi-weekly, semi-monthly, etc.) and the tax types that are relevant for the employee. 

There are two distinct types of gross ups: cash and non-cash. Cash gross up is one where the employee will receive an actual cash amount.  In this case, the grossed up amount is set to accumulated into /101. The SAP delivered model wage types for gross ups are cash wage types.  In other words, the wage type M032 is set to accumulate into /101. Typically, cash gross ups are used for bonus payments, such as year end bonuses.  Some companies use cash gross ups to pay expatriate employees. 

A second type is gross up payment is non-cash gross up.  In this case, the grossed up wage type is not set to accumulated into /101.  SAP does not currently deliver model wage types for a non-cash gross up. Non-cash gross up is typically used to determine a payment for taxes on a taxable employee benefit. For example, suppose that an employee has the use of a company car.  This benefit is considered to be taxable, so the employee would be liable for taxes on the use of the car.  An employer may decide that the company should make a payment to cover the tax liability for this benefit.  A non-cash gross up would be used to determine the tax owed on this benefit.

Processing

The processing of the gross up calculation is done in the payroll function USTAX. The gross ups are processed before the processing of the gross-to-net wages.  Each gross up payment to be processed in the pay period is done in a separate BSI call. There is minimal processing for the gross up calculation.  All that is needed is the guaranteed net amount along with the relevant tax types.  This information is passed to BSI, which returns the grossed up amount along with the taxes. Deductions are not considered during payroll processing.

Source : http://wiki.scn.sap.com/wiki/display/ERPHCM/Gross+Up 

Taxable Income :

Taxable Income :

Taxable gross is the number of dollars remaining after you reduce your total 
earnings by all of your pre-tax deductions (e.g., TDA and FSA contributions 
and medical and dental insurance premiums) and add any imputed income.