HR Query Reporting to Include Payroll Results Tables

Published on January 2017 | Categories: Documents | Downloads: 42 | Comments: 0 | Views: 186
of 2
Download PDF   Embed   Report

Comments

Content

Idea Place > Customer Connection > HCM - Organizational Management/ Personnel Administration > HR Quer...

Up to Ideas in HCM - Organizational Management/ Personnel Administration

HR Query reporting to include Payroll Results tables
Created on Apr 5, 2012 10:39 PM by James Barron - Last Modified: May 10, 2012 3:55 PM [Base Release for The Improvement Request] 600

[Description of the Current Situation] Currently the payroll results tables have very restricted reporting. Wagetype reporter gives restricted Results Table reporting (greatest level of detail is still summarised to PERNR/INPER/FPPER & very little (+ inaccurate as PA based) additional data (PA/PSA, EG/ESG, tax ID & cost centre is basically it). The other tables have no decent reporting. This means HR & payroll staff reporting wanting to report on results either become very adept at excel & vlookup to merge HR data & payroll results or resort to considerable expense to purchase a third party reporting tool

[Detailed Description] Summary: Make payroll results reportable in SAP queries.

Option 1 A new Logical DataBase to report on payroll cluster tables. Reporting on payroll cluster tables can be acheived from SAP Query by building an Infoset with an integrated internal program populating the requisite PCnnn structures vis HRPY_RGDIR selected SEQNR's. I've done this for almost a dozen clients and it's very successful (so the idea is prototyped & proven viable - are able to provide infoset & queries in a file and/or arrange live demonstration). Taking this further with the additional options & flexibility available in a Logical DataBase would improve, standardise and make fast good payroll reporting available without requiring user development.

Option 2 Development of Logical DataBase PNPCE to allow PCnnn cluster tables to be reported as virtual inotypes. There is precidence for this is the way the PersonalWorkSchedule data from cluster B2 is available in PNPCE as infotypes 2600/2601. Note this is simply additional logic in PNPCE rather than inefficient replication of cluster data as PAnnnn tables (eg the current difficult & limited "Payroll Reporting Infotypes" functionality) Virtual rather than real infotypes also eliminates the problem of fitting the FPPER/INPER & varying table keys into the standard PA table key structure.

For both options a mechanism to allow the suppresion of FPPER + splits is desirable. This may be either a selection screen option of splits to suppress (similar to payslip window line layout split options) or an infoset switch that combines RT lines when a split indicator is not output (similar to what PNPCE already does when outputting identical lines)

Why two options? Option 1 is simpler in that it has been prototyped/proven by the infoset I've written that is used by several different companies/organisations and is zero risk in being a new clean development however Option 2 delivers better options in regard to reporting PA data alongside payroll results (eg simply write a query to report name, tax no, address, gender, birthdate, taxable pay in period + employee & employer pension contributions in period for a superannuation report)

Like the idea? - get involved & have your say in the development - the earlier you subscribe the more influence you will have on the outcome

[Additional Comments]

[SAP Decision & Progress Report]

Tags: hr , cluster , query , infoset , payroll , rgdir , sap_query , pnpce , pnp

0 Comments
Leave a comment on this idea. Next

Sponsor Documents

Or use your account on DocShare.tips

Hide

Forgot your password?

Or register your new account on DocShare.tips

Hide

Lost your password? Please enter your email address. You will receive a link to create a new password.

Back to log-in

Close