13.07.2015 Views

SCT Banner Human Resources / Release Guide / 7.0

SCT Banner Human Resources / Release Guide / 7.0

SCT Banner Human Resources / Release Guide / 7.0

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Section 21 Miscellaneous Enhancements - FunctionalNew Rule Class Override in PTREARN and PHPFEXPNew Rule Class Override in PTREARN and PHPFEXPThis enhancement provides for the ability to override the Rule Class code at theEarnings level to avoid the generation of fringe chargeback encumbrance liquidationon certain earnings when the payroll is interfaced to accounting. In a past release,a similar capability was instituted, where an override Rule Class was made availableat the earning code level to avoid salary encumbrance liquidations. In the case ofsalary items, a rule class can be overridden so that it could be changed from anormal liquidating earn code (e.g., HGRS) to a non-liquidating earn code (e.g.,HGNL), during the payroll expense feed PHPFEXP.With this RPE, a new fringe rule class override has been added to the earnings rule,and is called the Fringe Rule Class. It is located in the Main window of the EarningsCode Rule Form (PTREARN) along with the original rule class override which isused to override earnings.In the case of Fringe Chargeback encumbrance liquidations, the ExpendituresFinance Extract Process (PHPFEXP) will recognize the Fringe Rule Class, when ithas been populated (typically with a non-liquidating earn code such as HFNL), todirect the payroll feed process not to liquidate the fringe encumbrance. Thiscompletes RPE #34233. Resolved in <strong>Human</strong> <strong>Resources</strong> <strong>Release</strong> 6.1.<strong>Human</strong> <strong>Resources</strong>/Position Control <strong>Release</strong> <strong>7.0</strong> January 2005270 <strong>Release</strong> <strong>Guide</strong> Confidential

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!