Wagetype Inflow/Outflow example SAP USA

Wagetype Inflow/Outflow example SAP USA 

Example

  In periods 01 and 02, two separate payments in the amounts of $700 and

  $300 were calculated with wage types M001 and M002, respectively.

  o   Period 01/01

      Wage type M001 in the amount of $700

      Wage type M002 in the amount of $300

      Wage type /102 in the amount of $1,000

  o   Period 02/02

      Wage type M001 in the amount of $700

      Wage type M002 in the amount of $300

      Wage type /102 in the amount of $1,000

  Later, in period 03, wage type M001 is retroactively changed to process

  a payment of $800 in period 01. The retrocalculation performed in period

  03 is as follows:

  o   Period 01/03

      Wage type M001 in the amount of $800

      Wage type M002 in the amount of $300

      Wage type /102 in the amount of $1,000

      Wage type /X02 in the amount of $100

  o   Period 02/03

      Wage type M001 in the amount of $800

      Wage type M002 in the amount of $300

      Wage type /102 in the amount of $1,000

      Wage type /X02 in the amount of $200

      Wage type /Z02 in the amount of $100

  o   Period 03/03

      Wage type M001 in the amount of $800

      Wage type M002 in the amount of $300

      Wage type /102 in the amount of $1,300

      Wage type /Z02 in the amount of $200

  In this case, /X02 is the outflow wage type and /Z02 is the inflow wage

  type, and you can calculate the difference by subtracting the amount in

  wage type /Z02 from the amount in wage type /X02.

Employee Data Replication issues

Error:

1)Pers.number already flagged for xx/xx/xxxx

• Position assignment in PA and OM are different and the object is flagged for master data integration. Called as open processes
• To Check , navigate to table T77INT , give the Employee Number number , you should get an entry for that PERNR  in T77INT and a  error message for same person in RHINTECHECK report.
• To resolve the error run the RHINTE* reports

2) Prebooking exists for personnel number

This error is coming from the activation of switch PLOGI EVENB and PLOGI EVEGC. here is the functionality Setting the 'PLOGI EVENB' switch to 'X' enables you to move a person, position or organizational unit within an organizational structure, when these changes lead to a change in company code for the person(s) concerned.

The personnel numbers of the persons concerned are locked in PA. The only personnel action you can now carry out these personnel numbers is Organizational change. You must carry out this action before you can make further changes to the Infotypes for the persons concerned .

Technically the lock what we are getting was caused by entry in the table T77INT.

 .

Workaround : Run the program RPLEVENT to create the action what it demands.

SuccessFactors - Payslip Issue  

- Suresh Kalimahanthi's NOTEs

Symptom

-> Customer is using Standard EC Payroll Pre-packaged Content for Employee Replication.

-> Login to SFSF Instance and navigate to Employee Files -> Payroll Information -> Pay Statement.

-> Now while trying to view their Pay Statement in Successfactors, employees are receiving an error message that says-

There’s a problem with the Employee ID. Check if the employee information was added to the system & try again. If it continues, please contact your Admin.

-> Employee access has already been verified and the employee has all the necessary roles and privileges in order to access the system, and so the issue is not with permissioning.

-> Also checked that the data for this employee was successfully replicated to the SAP ERP System from SFSF via the Standard Employee Replication Content delivered by SAP.

-> And also verified that there is an entry correctly maintained in the key mapping table PAOCFEC_EEKEYMAP. (If not, this can be a potential root cause for the erro

Cause

Go to transaction SFW5 and search for business function 'HCM_SFEC_MDEC2HR' and verify that this business function should not be activated, which in this case is the reason for the error.

Resolution

-> The function HCM_SFEC_MDEC2HR decides what mapping table for the employee is used to access the payslip.

-> If it is activated then the mapping table HRSFEC_D_EEKEYMP of the EA-HR-XX codeline is used for the employee. And if it is deactivated then the table PAOCFEC_EEKEY_MAP of the AddOn is used.

-> So in case you are using the AddOn implementation, you need to check that what was the reason for which this function was activated?

->Because to ensure that the correct mapping table is used for the payslip it needs to be deactivated.

-> And so in order to resolve this issue, if there is no specific reason why it was activated, you can directly go and change the settings for this in your system.

OSS NOTE:  2224933 - Unable to access/view the Pay Statement in Successfactors System

Integration Notes-

Organizational Assignment Replication

2525376 - EE Org Assignment: RH_UPDATE_DATABASE uses new infotype framework

Pasted from <https://launchpad.support.sap.com/#/notes/2525376>

Organizational Assignment Replication

• Application Log

• Transaction SLG1

• Web Service Utilities

• Transaction SRT_UTIL

Employee Org Assignment Replication Requests:

• View Requests: Report RH_SFIOM_VIEW_EE_ORG_ASS_RPRQ

• Transaction SFIOM_VIEW_REQUESTS

• Process Requests: Report RH_SFIOM_PROC_EE_ORG_ASS_RPRQ

• Delete Requests: Report RH_SFIOM_DEL_EE_ORG_ASS_RPRQ

• Check Requests: Report RH_SFIOM_CHECK_EE_ORG_ASS

• Transaction SFIOM_CHK_EE_ORG_ASS

Mapping Tables:

• Organizational Structure Item Key Mapping : Table SFIOM_KMAP_OSI

• Employee Key Mapping : Table PAOCFEC_EEKEYMAP

• Cost Center Key Mapping : Table PAOCFEC_KMAPCOSC

Setting up Organizational Assignment Replication :Pasted from https://help.sap.com/viewer/a7f164924edd4dfe817b7bdc2fc4927a/1711/en-US/cac229cb29e444f982eec0c9bed9c071.html>

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