sap hr/hcm benefits payroll integration

Benefits Payroll Integration 

Description

Benefits-Payroll Integration has been internationalized for 4.5A. The following changes take effect in this release:

Schema
Sub-schemas UBEN and USAV, rules UB00, UB01, UB02, UB03, UB04, and UB05 have been deleted. The new sub-schemas are UBE1 and UBE2.
Schemas UBE1 and UBE2 use the following functions:

Function	Description
BENPR	Prepare Benefits specific tables and other tasks (required

for all plans)
P0167 Process Health Plans (required for Health Plans)
P0168 Process Insurance Plans (required for Insurance Plans)
UGTLI Process Group Term Life Insurance (required for Insurance
Plans)
P0169 Process Savings Plans (required for Savings Plans)
P0170 Process Spending Accounts (required for Spending Accounts)
P0236 Process Credit Plans (required for Credit Plans)
P0377 Process Miscellaneous Plans (required for Miscellaneous
Plans)
P0379 Process Stock Purchase Plans (required for Stock Purchase
Plans)
BENTB Update Benefit table BENTAB (required for infotypes 0170,
0379)
Sub-schema UBE1 should be called after infotypes 0014 and 0015 are processed. UBE1 is normally included in sub-schema UAP0. It is important that function BENPR is processed before any of the P0xxx Benefits infotype processing functions are called. Check schema U000 to see how UBE1 and UBE1 are called.
The other sub-schema UBE2 has to be called after the proration process when the exact values for the actual salary are available (after rule X023 has been processed). UBE2 is normally included in sub-schema UAL0. Sub-schema XPDD (containing deductions not taken) has to be added after Benefits processing in UBE2.
Function BENTB has to be called in UEND just before the export of payroll tables after the last action on the Result Table RT. This is necessary because in BENTB the Benefits Table BENTAB is being actualized using the amounts from the RT.
Valid Parameters of Benefits functions P0xxx
For the P0xxx function, parameter 1 is the DATES parameter. It determines the cost evaluation date. The possible values for this parameter are:

• BEG (begin date of payroll period)

• END (end date of payroll period)

• CHK (payment date of payroll period)

• PER (day specific throughout the complete period, i.e., proration)

The second parameter, ENTRY, is only used for functions P0236 and P0377. The possible values of parameter ENTRY are '1' and '2' for the first and second call of these functions.
Note: You no longer need the P0xxx constants in table T511K to specify which date you want the calculation to be based upon. Instead, you can configure the parameter DATES to have the desired value.

Change system parameters in customizing

Wage Types
Note the following naming convention for Benefits/Payroll wage types:

WT	Description
BAxx	'A' for employee after-tax (not needed for Credits)
BExx

'E' for employee pre-tax (not needed for Credits)
BPxx 'P' for provider (only needed for Health, Insurance,
and Miscellaneous)
BRxx 'R' for employer contributions (needed for all categories)
BXxx 'X' for reimbursements of claims (only for Spending Accounts)
The following sample wage types were deleted:
BE3A, BE3P, (wage type BE31 does not use these derived wage types anymore), BM40, BM41, /BI1, /BI2, /BP1, /BP2, /BP3, /BP4, /BP5, /BP6, /BP7.
Make sure that your Benefits/Payroll wage types no longer use processing classes 61 and 87. These processing classes are no longer used in Benefits processing. Also make sure you use separate wage types for separate benefits plans.

Constants
Some constants were moved from T511K to T511P because they represent amounts, which require association with a currency.
The following constants are no longer used:
P0xxx (as mentioned in the 'Schema' section), HCASL (401K Post-tax Limit for HCE), HCPSL (401K Pre-tax Limit for HCE).

sub schemas

We provide excellent sap hr/hcm classroom and online trainings with all real time scenarios

for more details
madhupayroll@gmail.com
mobile: 9912223430